I also have this same issue. I tried to open my ramdisk PassMark OSFMount with offset of 4096 bytes but it does not open, How ever it does open my other ramdisks, I am left thinking that it's somehow corrupt itself to the point of unable to being opened again, I do need some data off of it, if there's any solution it'd be great. Thanks.

More likely, for some reason your image file size had grown twice, and after that became unmountable. We have received a few reports where image file grew in size, but it's barely possible through the normal operation of the RAM Disk software. Quite possibly it's a result of a conflict with third-party software.

Could you please list what other software you have installed on this computer? Especially applications that might filter file operations, like antivirus and security software.

Hi, folks!
I got that C00...098 error today. The disk was created using an image file with a size of 8 GB (raw). The image file's size now is 12,2 GB.

I changed some windows settings yesterday and maybe that has an influence.
Changes:
- Enabled services "Superfetch" and "Disk Defragmenter" and set their startup type to "Automatic" (both were stopped and disabled)
- Changed value of registry key "EnableBootTrace" from 0 to 3

I forgot to provide information as to my own experience with this issue. I created a 3GB disk, and had it set to save every 5 minutes. I got this error, and was confused, so I looked it up and found this thread. I went back to the file and noticed that it now registers 3.03GB

Hi, I've got a similar problem.
Ramdisk fails to load an image after reboot. It happens only to one ramdisk, the other works well. It also happens every time I un-mount it and then try to mount it again.
It only happens to images created using Image Type: Hard Disk (and not volume), with hard disk emulation flag enabled. Image size doesn't change (2GB).

I have the "save to image" flag, and the "save periodically" flag (20 mins).

I do backup my files using a file copy, but it is a pain to rebuild the disk everytime, and I've also lost some files because I can't do a continuous backup.

Maybe this will help you to find and fix the bug. It would be great if RamDisk could cycle image between 2 files, so if one gets corrupted there always is a working copy.

The same old bug...
I faced this issue again 2 days ago on Windows 10 when I started my PC. Image size size was increased. Original disk size was 300MB. Periodic save is turned on.
Couldn't mount it with OSF mount with offset, I mean it didn't show any filesystem on it, and recovery programs can't help at all. All datas RIP!
This ramdisk is unreliable we have to admit that, so a built in backup function would be very helpful whatever the bug can't be resolved.

It worked previously without any problem for months. But one thing that I found is that I turned on a scheduled disk cleanup before on all drives (I don't remember any other changes), but I have to test that possible issue further.