Question Random restarts and "IRQL_NOT_LESS_OR_EQUAL" crash?
Question Random restarts and "IRQL_NOT_LESS_OR_EQUAL" crash?
Hi, I've experienced intermittent PC crashes and BSODs over the past while using the same hardware setup. My system runs an R7 2700X with a GTX 1070, and I've kept it running for quite some time. I sold my GTX 1070 about a year ago, but I suspect this issue occurred before too.
Initially, I suspected a faulty CPU, especially after upgrading to newer models like the R7 5700X and RX 6800. I returned the old CPU and received an R7 5800X instead, yet the problems continued. I conducted multiple RAM tests using MemTest86 and even ran it for a full day without any shutdowns. I also upgraded my power supply from a 650W Corsair to an 850W XPG Core Reactor, hoping for better stability, but the issue persisted.
Recently, I reinstalled Windows on a new M.2 SSD I just purchased. Previously, Windows was installed on another SSD, so I assumed that was the cause. After disconnecting the old SSD and using only the new one, the problem still occurred. I tested both M.2 slots on my motherboard, but it didn't help.
I attempted to flash the RX 6800 BIOS to an older version to see what might be causing the issue. As a workaround, I disabled C-states in the BIOS, but this didn't resolve the problem. I haven't noticed any unusual temperatures on the CPU or GPU, and I've tried various BIOS updates and chipset drivers.
Given these challenges, I'm considering replacing the motherboard since it's the only component that has changed significantly. Here are my current specs along with the minidump files for reference:
- R7 5800X
- 4x8 GB XPG Spectrix d50 at 3200MHz
- X470 Aorus Wi-Fi Gaming 5
- RX 6800 Sapphire Nitro
- 500GB Gigabyte SSD (current boot drive)
- 500GB Adata SSD
- 2TB Toshiba HDD
- Deepcool 240mm LT520
Minidump files: [link to files]
Please let me know if you need anything else.
Memtest64 is functioning properly now, try it and aim for no errors in the blue bar below the runners. Eight passes should suffice. "Unusual" temperatures aren't a specific value; most PC parts handle up to 65°C without issues. At 75°C manufacturers stopped your computer from shutting down or rebooting, but that doesn't mean it's safe to operate. After all, they aim to sell you more components. If the PSU is missing, consider running stability tests with suitable software for CPU, GPU, and RAM together.
Are you adjusting the RAM to XMP 3200MT/s? If yes, consider disabling XMP and returning to the standard JEDEC speed of 2133 or 2400MT/s.
I owned a 2600X system that completed two full MemTest cycles without issues, yet it began black screening within 15 minutes after launching Windows. I adjusted the CL (CAS) timings at XMP 3000MT/s by a few clock cycles, and normal performance returned.
It’s true the 2600X (and your 2700X) are only certified for DDR4-2933, so operating these CPUs at 3000 or 3200MT/s may slightly exceed their specifications unless you’re ready to tweak the automatic XMP settings manually.
The 5700X is labeled as DDR4-3200, but stability at that speed with various RAM and motherboard combinations isn’t guaranteed.
If lowering the RAM speed to 2133MT/s doesn’t work, consider removing two of the four DIMMs. The IMC has a tougher job handling four DIMMs compared to two, so ensure the remaining ones fit in the slots suggested in the motherboard manual, likely A2 or B2.
I have executed the dump files and the complete reports are available via the provided link.
If you encounter a prompt asking to "Run only if trusted," simply click play/run and the HTML will display. This caution is consistently shown.
JSFiddle
jsfiddle.net
Findings summary:
Points to consider:
Bug check 0xA typically stems from kernel mode device drivers using incorrect addresses. This may result from a corrupted memory pointer or an issue with the device driver code itself. Investigate third-party drivers and consult the System Log in Event Viewer for more detailed error information that could help identify the problematic device or driver. This issue is generally linked to faulty drivers, not defective hardware.
WinRing0x64.sys was detected in all analyzed dumps. This driver is recognized as a known BSOD cause in certain operating systems—various applications relying on WinRing libraries such as RealTemp, Corsair Link2, Razer GameBooster, Intel Processor Diagnostic Tool, etc. It may be beneficial to disable or update it, as it was released around 2008.
You might find the linked resource useful for reviewing potentially outdated drivers and determining which ones need updating.