I leave my computer running for long stretches because it also acts as a plex server. I turned my monitor on last night to open steam, and the window didnāt render in; I didnāt think much of it, but before I could restart my PC, I got a āmemory managementā BSOD. I turned off XMP, as well as taking out each RAM stick, but I continued to get BSODs. Either āmemory managementā or ācritical process errorā. Some other things Iāve attempted:
I canāt reset the PC; when I try, Iām told āthere was a problem resetting your PCā.
I canāt use a system restore point; that also fails.
When I open the terminal and run
sfc /scannow
it finds and fixes corrupt system files every single time (Iāve attempted 3 times now), but I still get a ācritical process errorā BSOD.
I attempted running
DISM.exe /Online /Cleanup-image /Restorehealth
before āsfcā but this got an error 87 and didnāt work.
When I turn on the PC, my lights for DRAM and VGA stay lit up for maybe 5-10 seconds, but turn off while Iām in BIOS or the windows startup repair screen (and my monitor is plugged into the graphics card; my CPU canāt do display out).
Iām at a bit of a loss here. My next guess would be to attempt to reinstall windows, but I donāt have another windows PC handy to create bootable media, so Iām hoping I have a thumb drive laying around with an ISO on it, or Iāll need to wait to get one from a friend.
Also, in the event that reinstalling windows is the fix, should I disconnect the drives holding my plex media beforehand? Wouldnāt want to risk them getting wiped
An update: I have a drive with installation media for Windows 10 laying around, but when I got to the point where it was installing files on my boot drive, partway through it said it didnāt have the required files and cancelled.
THE FIX: Turns out it was an issue with my RAM. I plugged in a thumb drive containing memtest, and after running the test received a ton of errors. Swapping in a new RAM kit seems to have totally resolved my issues. The PC boots up perfectly fine now
You should run memtest for 24 hours with all ram sticks in.
It definitely looks like your ram is somehow faulty, have you tried resetting CMOS beyond just turning off XMP? It could also be your motherboardās VRM overheating, but i donāt know how you would test that without a bunch of thermocouples.
I havenāt reset the CMOS yet; Iāll give that a try. But I did try booting with a single stick inserted, swapping them out, and both attempts gave me a BSOD (the critical system error one). My CPU cooler has a tiny fan for the VRMs, and my case has excellent airflow, so I think that one is less likely
Running memtest, Iām at over 400 errors before the first pass even completed. I take it thatās probably a RAM issue?
Yes. Your ram is bad and you can throw it in the trash (please do recycle it) and buy new stick. Sorry that happened to you, I know it sucks.
Swapped the new kit in and it works perfectly now. Thanks for the help!
Sounds like memory corruption. Before you do like the other poster said and run memtest, Iād suggest reseating the ram, possibly in different banks if you can, reseat the video card and then try again.
If you still get failures:
- memtest
- update bios
- dive deeper into the windows system logs for clues
- then check your ssd for bad blocks using the SSD vendor tools
Always backup your important files!
Are there vendor tools that run off of a flash drive like memtest? I canāt boot into windows at all
Absolutely! Even memtest has a portable one.
https://www.memtest86.com/tech_creating-window.html
Thereās some to test the hardware and even SSD, but Iād need to know the ssd brand/vendor.
edit: Adding ultimate boot cd as another useful tool that can run on usb
Ultimate boot looks like an extremely useful tool, thanks for mentioning that. After testing each RAM stick in the primary slot for my MOBO, Iām running memtest and getting a lot of errors (now over 500 and still on pass 1)
Most RAM have a lifetime warranty, so please take a picture of the errors and use that to rma (return) to the memory maker for a free replacement.
In the meantime, consider buying new ram (unless you can wait 6 weeks for an rma return lol).
Itās DDR4 so not crazy expensive; I went ahead and got a new kit. Thanks for your help!
This sounds very similar to a problem I had when an NVME drive was failing; it wasnāt writing certain blocks; they had become read only and the only thing I could do was clone the corrupted data off of the drive and do a reinstall.
I ended up moving my data to a more reputable drive, and then RMAād the NVME drive, only to have the replacement be used in my wifeās PC, and the same thing happen 6 months later.
Fwiw, this wasnāt in windows but the problem was a little similar, I once debugged a hardware problem for weeks until I finally found out that the cpu had crapped out for some reason. I managed to have it swapped on warranty and all was well.
Iād even changed the motherboard (and ram, and psu) at one point and was running out of ideas, the cpu was the last possibility.
Just to say that it can be many things.
But the ram is definitely the usual culprit.
Hereās hoping itās RAM (memtest seems to suggest so); thankfully DDR4 is probably as cheap as it will ever be right now
Suggestion: Look up the mobo and download the tested memory modules for it. In there youāll find part numbers compatible with the mobo that you can shop for online.
The QVL! Appreciate the reminder
