My PC crashed with a MEMORY_MANAGEMENT blue screen and rebooted. Afterward, one of my two RAM modules no longer appears in the BIOS or Windows. I previously got it working by moving it to another motherboard slot, but that no longer helps. The module looks physically fine, and Windows Memory Diagnostic reported no errors on the RAM that is still detected.
I may also have confused the RAM module with a RAM-based virtual disk. The working module is associated with my C: drive, while the missing E: drive contained files and programs. How can I determine whether the problem is the RAM stick, the motherboard slot, or the virtual disk, and is there a safe way to recover the files without losing them?
3 Answers
The E: drive may have been a RAM disk rather than a real disk. A RAM disk stores its data in system memory, although some programs can save an image of it to an SSD or hard drive. Any changes made after the last saved image or before the crash may be gone. First confirm whether there is an image file or RAM-disk software configuration on your normal storage drive. If the RAM stick is dead and the disk existed only in volatile memory, software cannot recover its unsaved contents; avoid initializing or formatting anything until you identify how that virtual disk was created.
Test the hardware systematically: power the PC off, reseat the module, then try the suspected stick by itself in the motherboard’s recommended slot. Test the known-good stick in that same slot, and test the suspected stick in each slot. If the good stick works everywhere but the other stick is never detected in BIOS, the module has probably failed. If both sticks fail in one slot, the motherboard slot or memory channel may be the issue. Also check that the modules are fully latched and that the system is running at default BIOS settings rather than an unstable overclock or memory profile.
A blue screen mentioning memory management does not necessarily mean the RAM itself is defective. It can also result from a motherboard problem, unstable memory settings, a driver, or storage corruption. Once the hardware tests are done, reset BIOS memory settings to their defaults and run a bootable memory test with each module separately. Windows Memory Diagnostic only tests the memory Windows was able to use, so it cannot reliably test a module that the BIOS does not recognize. Crash dump files may also help identify the original blue-screen cause.
I checked the BIOS and the module is not detected there at all. I had mistaken the virtual disk shown in File Explorer for a physical disk, which caused some of the confusion.