Question I'm getting Random IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis ?

[ConorDuey2000]

Hello. As of recently, my computer is having some big problems. It's been getting IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis. I've tried debugging the BSODs using WinDbg, but they just told me "Process name: System" so that means I have no idea what's causing these BSODs. I've tried reinstalling various drivers, uninstalling various software, updating Windows, updating the BIOS, and everything else that I could do besides reinstalling Windows. I really don't wanna live with these random BSODs, anymore, and I was wondering if any of you could help me stop them from happening.

Here is the kernel dump and here are some minidumps.

PC Specs
Mobo: ASUS TUF GAMING X570-PLUS (WI-FI)
Mobo BIOS Version: American Megatrends Inc. 5021
CPU: AMD Ryzen 7 3800X 8-Core CPU
GPU: Nvidia GeForce RTX 2060
OS: Windows 11 Pro 24H2

UPDATE: I really need help, man. As of writing this, I've gotten at least ten BSODs in a single day and I wasn't even doing anything abnormal with my computer. I ask anybody reading this to try their best to help me stop my computer from getting these BSODs because they're really driving me crazy.

 

[ubuysa]

Hello, and welcome to the forum!

All these dumps show various failures as a processor comes out of the low-power idle state into the high-power running state. What's more, the logical processor involved is either #8 or #9 in every dump - that means they're probably the same physical core. I have seen several (mostly AMD) CPUs that had issues transitioning from the lower-power idle state to the high-power running state. The test (and workaround) for this issue is to go into the BIOS setup and disable all C-States for all processors. This stops the processors from entering a low-power state when they become idle. That avoids this power transition issue when they later come out of idle.

The only downsides in disabling C-States is that the CPU will run a tad hotter at idle, but a decent cooler should have no trouble with that. It also means there will be a slightly higher power draw at idle, but that's probably not measurable.

Let us know whether disabling C-States stops these BSODs.

 

[ConorDuey2000]

Hello, and welcome to the forum!

All these dumps show various failures as a processor comes out of the low-power idle state into the high-power running state. What's more, the logical processor involved is either #8 or #9 in every dump - that means they're probably the same physical core. I have seen several (mostly AMD) CPUs that had issues transitioning from the lower-power idle state to the high-power running state. The test (and workaround) for this issue is to go into the BIOS setup and disable all C-States for all processors. This stops the processors from entering a low-power state when they become idle. That avoids this power transition issue when they later come out of idle.

The only downsides in disabling C-States is that the CPU will run a tad hotter at idle, but a decent cooler should have no trouble with that. It also means there will be a slightly higher power draw at idle, but that's probably not measurable.

Let us know whether disabling C-States stops these BSODs.

I'll try doing that and see if I continue getting these BSODs. I'll be okay with the downsides.

 

[Colif]

So the hypervisor errors stopped?

@ubuysa if you look at his post history here, this PC has been a pain for the user for at least 2 years. So if you can work it out, you doing well

 

[ConorDuey2000]

So the hypervisor errors stopped?

@ubuysa if you look at his post history here, this PC has been a pain for the user for at least 2 years. So if you can work it out, you doing well

I was able to stop the HYPERVISOR_ERROR bluescreens from happening by just simply not using anything involving hypervisor on my computer, anymore such as VMWare and WSL. Now, I'm regularly getting BSODs, again, but this time, it's for a different reason.

 

[Colif]

perhaps ubuysa will find an answer for you.

Wonder if problem is actually the CPU itself.

 

[ConorDuey2000]

Hello, and welcome to the forum!

All these dumps show various failures as a processor comes out of the low-power idle state into the high-power running state. What's more, the logical processor involved is either #8 or #9 in every dump - that means they're probably the same physical core. I have seen several (mostly AMD) CPUs that had issues transitioning from the lower-power idle state to the high-power running state. The test (and workaround) for this issue is to go into the BIOS setup and disable all C-States for all processors. This stops the processors from entering a low-power state when they become idle. That avoids this power transition issue when they later come out of idle.

The only downsides in disabling C-States is that the CPU will run a tad hotter at idle, but a decent cooler should have no trouble with that. It also means there will be a slightly higher power draw at idle, but that's probably not measurable.

Let us know whether disabling C-States stops these BSODs.

I've disabled "Global C-state Control" in my BIOS, but unfortunately, I still got one of those BSODs. Just like the previous BSODs, it was an IRQL_NOT_LESS_OR_EQUAL BSOD and the process name was "System".

Kernel Dump | Minidump

I went back in the BIOS settings and I also disabled the "CPPC" setting. I don't know if doing that will solve my problem, but it's worth a try. I really don't wanna buy a new CPU or power supply.

 

[ConorDuey2000]

Hello, and welcome to the forum!

All these dumps show various failures as a processor comes out of the low-power idle state into the high-power running state. What's more, the logical processor involved is either #8 or #9 in every dump - that means they're probably the same physical core. I have seen several (mostly AMD) CPUs that had issues transitioning from the lower-power idle state to the high-power running state. The test (and workaround) for this issue is to go into the BIOS setup and disable all C-States for all processors. This stops the processors from entering a low-power state when they become idle. That avoids this power transition issue when they later come out of idle.

The only downsides in disabling C-States is that the CPU will run a tad hotter at idle, but a decent cooler should have no trouble with that. It also means there will be a slightly higher power draw at idle, but that's probably not measurable.

Let us know whether disabling C-States stops these BSODs.

Bad news. I've disabled "Global C-state Control", "CPPC", and "CPPC Preferred Cores" and I still get the same BSODs. This shows that I have another problem. We need to find what the real problem is so that I can get rid of those BSODs for good.

Kernel Dump | Minidump

By the way, I get most of those BSODs when my computer's idling.

 

[ConorDuey2000]

I have an update, now. This situation has gotten a lot worse. Now, I can't even leave my computer idle for ten minutes without it getting a BSOD. I could leave my computer to get a drink and when I come back, I'd see that my computer got a BSOD and has restarted. Disabling C-State did absolutely nothing. Luckily, one of those BSODs that I got did tell me which process caused it. In this minidump, I was told that Corsair iCUE caused my computer to get a BSOD. I'd uninstall iCUE, but I've tried that, before, and I still got BSODs. Hopefully, one of you can analyze the minidump and help me get these BSODs to stop.

 

[ConorDuey2000]

I have another update. I got a BSOD, even though my computer wasn't idling. I was just using my computer as normal, but I suddenly got a BSOD. This time, the BSOD was a "DRIVER_IRQL_NOT_LESS_OR_EQUAL" BSOD, but the process name was "System". Here is the kernel dump and here is the minidump. I was thinking that I could change the power settings in my control panel to stop the BSODs, but I don't know if that'll work or not.

 

[ubuysa]

All those dumps still show failures as a processor transitions from idle to running.

I'd now like you to try starting Windows in Safe Mode. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. On the other hand, if it's stable in Safe Mode then your problem is with a third-party driver or service that wasn't loaded in Safe Mode. There is another technique we can use in that case to locate the problem service or driver.

 

[ConorDuey2000]

All those dumps still show failures as a processor transitions from idle to running.

I'd now like you to try starting Windows in Safe Mode. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. On the other hand, if it's stable in Safe Mode then your problem is with a third-party driver or service that wasn't loaded in Safe Mode. There is another technique we can use in that case to locate the problem service or driver.

That should be a good thing for me to do. Next time I leave my computer idle, I could boot it into safe mode and let it stay idle for a while. If several hours have passed and it hasn't gotten any BSODs, I'll confirm that a third party driver or service is causing these BSODs.

As for now, I'm gonna try to change my power options and see if that makes any difference. Another thing that I can do is use Driver Verifier. I know how to use it. After starting Driver Verifier, I'll leave my computer idle until I get a BSOD. I'll create a restore point just before I run it just in case my computer gets stuck in a boot loop.

 

[whatdoitypehere9937982739]

I have had this exact issue before, have you tried reseating, rearranging or replacing ram? That worked from me.

 

[ConorDuey2000]

I have had this exact issue before, have you tried reseating, rearranging or replacing ram? That worked from me.

I should try reseating the RAM and see if that solves the problem.