Random blues screening update: no POST required.
Random blues screening update: no POST required.
Hi, I set up a new machine on the AM5 platform with the 7950x chipset. I’m facing some stability problems, especially random bluescreens. Initially, I replaced the RAM and it improved things for a short time, but after roughly three hours—longer than the three minutes I usually wait before reseating—I still encountered another screen issue. I tried reinstalling Windows, assuming corrupted drivers might be the cause, and after about three more hours of troubleshooting it worked again, only to repeat the problem. Now I’m stuck again. Following the BSOD guidance, I’ve recorded my system details and attached a minidump (the first few files are missing since I wiped the drive during the Windows reinstall). Here’s what I have: OS version 11, 7 days old, installed 6 days ago, CPU Ryzen 9 7950x, GPU RX 6800XT, RAM Teamgroup CTCWD532G6000HC30DC01 at DDR5-6000. Perfmon took too long to finish and isn’t generating a report yet. I’ve saved everything as 010124-8640-01.zip.
Yes, I understand those codes. They represent specific system errors:
- SYSTEM_THREAD_EXCEPTION – general thread exception
- IRQL_NOT_LESS_OR_EQUAL – interrupt request not within valid range
- WHEA_EXCEPTION – Windows kernel exception
These indicate different types of hardware or software failures.
These are usually old drivers or faulty hardware. Consider using Windows Memory Diagnostic or memtest86 to check for RAM problems. Determine how many RAM modules you have (2 or 4 DIMMs). Test the system at default speeds without XMP enabled to see if the issue continues. Also, note that this RAM isn’t listed in the motherboard’s QVL, which is the manufacturer’s test list confirming compatibility.
I'm testing two DIMMs and Windows Memory Diagnostic showed no problems. The minidump indicates the NT kernel is the problem, which seems odd since it's meant to handle drivers. I might disable EXPO and run memtest86 for a few hours to check. Regarding the QVL list, do you think returning your current RAM and getting a new one that's in the QVL could be the cause if you're still seeing bluescreens?
That's satisfactory so far. I found the dumpfile mentioning ntkrnlmp.exe, which points to the Windows NT kernel, but they didn't clearly identify the problem. IRQL might indicate a hardware failure, often related to memory. Memtest86 will perform a deeper check and take longer, providing either a [PASS] or [FAILED] result. Given it's a memory issue, it likely resolves on its own.