PC experiences various BSODs?
PC experiences various BSODs?
I'll try to make my post short but also give as many details I can think of.
My PC specs:
AM4 Gigabyte B550 AORUS ELITE AX V2
AMD Ryzen 5900X
Arctic Liquid Freezer 2 240 A-RGB
2x16GB Corsair LPX Vengeance DDR4 3600 C18
ASUS ROG STRIX 1000G 1000 W
Sapphire Nitro+ RX 6800XT
Kingston A2000 M.2 NVME 250GB + Kingston A2000 M.2 NVME 500GB
Toshiba P300 7200RPM 3TB HDD
Windows 10 Pro 22H2
The PC was assembled last year around April, and I would say everything was fine except for 1 thing that I can recall. It randomly froze up after the spinning mouse circle, usually when browsing the Internet but sometimes when opening random programs too. After spinning for a while, it freezes the whole PC, taking Windows Explorer down with it and then coming back to life after about a minute.
This occurred every once in a while at first, then more often after some months. Eventually BSODs popped up in some rare occasions until the BSODs became more frequent as well about maybe 3-4 months ago. That's when I started looking up ways to try and resolve the issue, since it's a self-made PC from parts all over the place.
The BSODs I've so far experienced are as follows, from most often occurring to the ones least occurring:
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_NOT_LESS_OR_EQUAL
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
KMODE_EXCEPTION_NOT_HANDLED
DRIVER_IRQL_NOT_LESS_OR_EQUAL
CLOCK_WATCHDOG_TIMEOUT
ATTEMPTED_WRITE_TO_READONLY_MEMORY
CACHE_MANAGER
DPC_WATCHDOG_VIOLATION
And these programs were only sometimes listed as the cause of the crash:
fltmgr.sys
ntfs.sys
amdkmdag.sys
ntkrnlmp.exe
What I've tried so far:
Uninstall Windows about 3-4 times now, on both the 250GB NVME and most recently the 500GB one, which is where I'm currently at. The BSODs occurred even during some of the Windows installations earlier, so that didn't fix it.
Removed and swapped around my RAM sticks and test them with Memtest86 and Windows Memory Diagnostic. The BSODs kept occurring and the tests came up with not a single issue with however many passes it took.
Removed the HDD and NVMEs, BSODs kept occurring.
Updated BIOS with whatever newest update is available on the MB site, BSODs kept occurring.
Download every single bit of driver software I could scrounge up on both specific manufacturer and MB sites, BSODs kept occurring.
I cleared CMOS on the MB and that came the closest to a fix I could notice, since BSODs were barely occurring shortly after I did this, until they started occurring again so this didn't work either.
The times the BSODs occur the most is when Windows is booting, either during the spinning circle on the BIOS Del/F12 logo screen, or the welcome page to Windows, or just shortly after Windows is started. But also sometimes randomly when installing something (most recently that I noticed it was with audio drivers and Gigabyte's RGB Fusion) or just opening any program on the PC.
Now as far as crash dumps go, the PC only creates 5 files and sometimes it created multiples so older ones get overridden, but I have 2 sets of them from 2 months ago when I first reinstalled Windows on the 250GB NVMe SSD and it BSODed a million times during that process (this one is on the 250GB NVME that I currently have removed, let me know if it's needed as well), and the most recent installation of it on the 500GB NVME. I just threw them all in and hopefully they show absolutely anything worthwhile.
https://www.mediafire.com/file/48tu5s3sb...ps.7z/file
I'm going insane, because even as I still have warranty for all the parts to return for another 6 months or so, I have absolutely no idea what even is the issue to return only that 1 specific part in hopes that resolves it. If anyone has any clue what the problem is and what to do about it, please let me know since the only other last resort I have is taking it to a random repair shop but I have no idea what they'll do and how much worse it'll end up being. Lemme know if anything else is needed.
I completed the DISM and sfc /scannow tasks, though I didn't mention it before, as it was on the old NVME about two months ago. From what I remember, the process concluded with a message saying "corrupt files were fixed," but I kept experiencing BSODs afterward. I'm attempting this again now, but it doesn't seem to resolve the issue.
Regarding the reliability monitor, it's indicating unexpected shutdowns and generating a MEMORY.dmp file around 1GB in size. Should I compress and upload that file?
As for Event Viewer, I'm uncertain what I'm viewing.
I've examined the dumps from the 17th and 18th entries and it seems to indicate a RAM issue. Run a RAM test with Memtest86... Download
Memtest86 (free), use the imageUSB.exe tool extracted from the download to create a bootable USB drive with Memtest86 (1GB is sufficient). Perform this on another PC if possible, since you can't fully rely on your own system right now.
Start the USB drive on your PC and Memtest86 will begin testing immediately.
After completing the four iterations of the 13 different tests in the free version, restart Memtest86 and run another four cycles. Even one bit error means it failed.
Thanks for checking, and the more BSOD errors appearing made me suspect a RAM problem, though it feels different. I tested both sticks together and apart, as they’re a kit, and both Memtest86 and Memory Diagnostic showed no errors during testing. I also ran XMP since the PC was assembled last year, but after reinstalling Windows it’s turned off and still triggers BSODs. The frequency of these errors doesn’t seem to change whether XMP is on or off, which might be relevant.
I can repeat Memtest several times, and if no errors appear with any stick combination, how reliable is that? I just need to be sure before deciding to replace them. Unfortunately, I don’t have any other units to test the setup with right now, to check if the issue continues.
If Memtest86 completes two clean runs, consider disabling the RAM overclock settings (DOCP/XMP) and let the RAM operate at its original speed. Check if the system remains stable then.
It's also important to remember that the highest confirmed RAM clock speed for that CPU is 3200 MHz (refer to https://www.amd.com/en/products/processo...5900x.html). Most CPUs can safely surpass this limit, but stability isn't assured.
You might also want to install the SysnativeBSODCollectionApp, save it to your Desktop, and then upload the generated zip file to a cloud service with a link. This tool aggregates troubleshooting information and does not store personal data. It is trusted by several reputable Windows help forums, including this one. As a senior BSOD analyst on the Sysnative forum, I can confirm its reliability.
Feel free to inspect the contents of the zip file before uploading, though avoid modifying or removing any files. For details on each file, refer to the provided link.
.........MAN, ok that really ****** me off now, I spent like 2 months before I bought it trying to figure out all the configurations of every component I was assembling and everything turned out compatible with each other, but I didn't see that specific bit of information. 🤦♂️ Thanks for pointing it out, now I'm starting to believe it's the RAM after all. It's like the XMP was slowly killing it over the course of the previous year and now it's become too corrupted or something. Since the Memtest that I did showed no errors, it's making me think the sticks themselves are still fine, but their connection with my system (either the CPU or MB) is what's corrupted. You'd think since I turned the XMP back to default it would run fine again but there's still BSODs so it's just weird.
I'm actually seeing so many people online state that 3600MHz CL16 is like a "sweet spot" for the 5900X so I'm just even more confused. It's like a roulette at this point.
🙄
I'll try some more Memtests then and Sysnative soon, but it's looking like I need to consider getting a 3200MHz set instead to comply with the CPU. 🤷♂️
1. I did, can't remember at which point exactly but it didn't result in any errors.
2. Other than XMP being on for a year before the first Windows reinstallation, no. The GPU MIGHT be pre-OC'd though, but there's no way for me to confirm since the sellers of that specific GPU at that time all had "OC" in its description.
3. I haven't checked, but it's doing it so sporadically now that I wouldn't know how to try and "trigger" it at this point. I could try doing a few restarts in succession and see if anything pops up.
If the GPU is factory oclocked ot shouldn't cause a problem. XMP has been ok, so no reason to cause a random problem unless RAM becomes faulty. Being at random times, it does make ot harder to nail. You have had help from others on here and no luck. Could easily be a faulty driver, windows service process at the time or even possibly a windows update causing it ??
And it BSOD during the Sysnative process, PAGE_FAULT_IN_NONPAGED_AREA. I'm planning to finish backing up my files before anything happens, then proceed with the Sysnative process and some tests. In the meantime, if anyone finds a solution, let me know and I'll get back to you with the results. Thanks for the help so far!