My PC recently crashed with a memory-management blue screen and rebooted. Afterward, one of my two RAM modules stopped appearing in the BIOS or Windows. The working module is still installed, but the other one is not detected even after I moved it to another motherboard slot. I previously got it working by changing slots, so I'm unsure whether the module itself is damaged, the slot or connection is faulty, or the crash exposed another hardware problem. Windows Memory Diagnostic reported no errors, although that test may only be checking the RAM that is currently detected.
I also had a virtual RAM-backed disk that appeared in File Explorer as another drive and contained files and programs. I may have confused that virtual disk with a physical drive. Is there a reliable way to determine whether the RAM stick or motherboard slot is at fault, and is it possible to mount or recover the virtual disk without losing its data?
4 Answers
Test the hardware separately before worrying about the virtual disk. Power the PC off, remove the module that is currently working, and test the questionable stick by itself in the motherboard’s recommended slot. Then test the known-good stick in that same slot. If the good stick works but the other one never appears in the BIOS, the RAM module is probably defective. If neither stick works in that slot, inspect and clean the contacts carefully and suspect the slot, motherboard, or CPU memory channel. Also verify that the module is fully latched on both ends and that the memory settings are at their defaults rather than using an overclocked profile.
The extra “disk” was likely a RAM-backed or virtual disk, not storage physically located on the RAM stick. These disks normally use an image file stored on an SSD or hard drive, but some setups only preserve changes when configured to do so. First look for the virtual-disk software and its image file on your actual storage drives. If an image exists, it may be possible to mount it again after reinstalling or reconfiguring the software. Anything that existed only in volatile memory, or changes made after the last saved image, may have been lost in the crash. Avoid writing to or formatting any suspected image file until you identify its format and make a backup.
The built-in memory test cannot tell you much about a module the system no longer detects. Once you isolate the stick and slot, run a bootable memory test such as MemTest86 with each module separately. If the suspect module produces errors or prevents the system from starting in multiple known-good slots, replace it. If it works alone but fails when both modules are installed, reset BIOS settings and check that the modules are a matched kit and supported by the motherboard.
For the blue screen, check whether Windows saved files in C:WindowsMinidump. Those crash dumps can help identify whether the original failure was caused by faulty memory, a driver, or another hardware problem. Since the machine crashed, back up important files now and avoid relying on the questionable module until it passes testing.
That makes sense. I was calling the virtual disk a drive because it appeared in File Explorer, but the missing item really is a physical RAM module and it doesn’t show up in the BIOS at all.