BSOD with RAM disk mounted on boot

Hi all,

as seen in subject, I get BSOD with RAM Disks that are mounted on boot

Few system details:
fresh installation of Win 7 x64
RAM Disk v3.4.0 64bit
16GB of RAM

I've tried to create RAM Disk with 2-4 GB in size, mounted on boot. Everything goes smooth with no errors.
However I get BSOD on windows start up.

I've done some more testing so at this point I can confirm that I get BSOD on startup only when I have RAM Disk mounted on boot.

There are no errors in event viewer regarding BSOD
RAM Disk mounted on logon doesn't have this issue.

Is there a crash memory dump available? Look for MEMORY.DMP in the Windows folder.

Hi,

none that I can find

BSOD occurs on a part of windows boot when colorful parts of windows flag spin around and it's for a split of a second so I think it doesn't have time to make a dump.
I can't even read the error.

Hi,

A week without any responses, I find it hard to believe that I'm the only one with this kind of a problem.

So, here are my conclusions regarding the issue:
System is stable if I make and load an image to RAMDisk and set it to save its content.

Since I have only SSD disks in my system, this doesn't reduce any amount of writes to them since all changes are saved eventually.

If I create volatile RAMDisk it has almost no other use except to hold browser temp files.

It is possible to move many other temp files even to this kind of a RAMDisk but that would make sense on „always on“ systems, not on a laptop which gets turned on/off few times a day.

Did anyone manage to successfully create a RAMDisk without image mounted and move most of temp folders (IE, WIN/User TEMP & TMP, cookies, Flash player and Media player temp files) to it without any issues?

Thank you,
Best regards,
Walter

Well, there isn't much we can do without a dump, but here's a couple of thoughts/questions:

1. Does your system have a built-in video card that reserves some amount for RAM for itself?

2. Do you have a paging file enabled? If not, I recommend to turn it on make it at least 16 GB (same as the size of RAM) to see if the problem goes away.

I'm having the same problem on version 3.4.0. (Win8 64, 8G or 2G of memory and accordingly 1G or 100M RAM disk. Integrated video - Intell).
BSOD does not occur immediately after the installation.
As a result, deleted system files (in system32).
With that, it can even occur during working.
At version 3.3.3 is no such problem.
Version 3.4.2 I have not had time to test.

Unfortunately there's not much we can do with this information. We need a kernel memory dump which needs to be tuned on as explained here, or even better try the latest version.