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

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
ConorDuey2000

ConorDuey2000

Reputable
Dec 21, 2021
174
3
4,585
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.

UPDATE 2: My situation has gotten much worse as of writing this. Now, my computer can't even make it past an hour without getting a BSOD. I'm currently doing everything I can to get these to stop. I've tried searching for these problems I have on Google, DuckDuckGo, and other search engines, but I haven't gotten any results. It seems like nobody else has this problem except for me. I'm calling for anybody who reads this to try and help me get these BSODs to stop happening as long as they're able to do so because at this point, my computer's almost unusable.
 
Last edited:
Sort by date Sort by votes
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.
 
Upvote 0 Downvote
ubuysa said:
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.
Click to expand...
I'll try doing that and see if I continue getting these BSODs. I'll be okay with the downsides.
 
Upvote 0 Downvote
Colif said:
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 :)
Click to expand...
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.
 
Upvote 0 Downvote
ubuysa said:
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.
Click to expand...
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.
 
Upvote 0 Downvote
ubuysa said:
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.
Click to expand...
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.
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
ubuysa said:
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.
Click to expand...
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.
 
  • Like
Reactions: ubuysa
Upvote 0 Downvote
Here's an update. My computer just crashed, again, but this time, there was no BSOD and my computer wasn't idle. I was using my computer as normal, but suddenly, it just randomly restarted. No BSOD showed up and Windows didn't give me any memory dumps.

At this point, I don't want anybody to ignore this thread because I'm running out of potential fixes. If I don't find a fix for this, I'm gonna have to deal with these BSODs forever until I buy a new computer. I need your help finding a way to fix this because these daily BSODs have been driving me crazy.
 
Upvote 0 Downvote
Since there are about 5 threads on this PC, I don't believe the problem is software.

Have you replaced any parts at all in this time? Not blaming them but just wondering.

I am curious if cause is actually the CPU or maybe Motherboard, two parts that aren't easily tested. No real tests at all for motherboard but you could run Primte95 on CPU though I am not sure that would prove anything.

ubuysa said:
All those dumps still show failures as a processor transitions from idle to running.
Click to expand...

Current errors started by a core not waking? can you tell if its the same core each time?

Previously it was:
  • Hypervisor errors make up most of it.
  • previous to that it was page faults and IRQ
  • 2022 it was crashing without dumps
  • then hypervisor again
 
Upvote 0 Downvote
Colif said:
Have you replaced any parts at all in this time? Not blaming them but just wondering.
Click to expand...
The only part I've replaced was the RAM which I replaced last year.
Colif said:
Current errors started by a core not waking? can you tell if its the same core each time?
Click to expand...
I don't know how I can tell if the core that doesn't wake up is the same core each time.

Anyway, I'm not sure if it's guaranteed to be a hardware problem because there are long periods of time where my computer doesn't suffer from regularly occurring BSODs. My motherboard, CPU, and GPU are five years old so I'm not sure if they've developed problems that quickly.
 
Upvote 0 Downvote
ConorDuey2000 said:
I don't know how I can tell if the core that doesn't wake up is the same core each time.
Click to expand...
I quoted ubuysa, I was asking him as he might be able to tell from the dumps.
ConorDuey2000 said:
My motherboard, CPU, and GPU are five years old so I'm not sure if they've developed problems that quickly.
Click to expand...

you been having problems since 2022. It might be one bad part that has caused all of them. It might just be a small fault that trips up other things occasionally. Two different versions of windows...
just trying to help
 
Upvote 0 Downvote
Colif said:
I quoted ubuysa, I was asking him as he might be able to tell from the dumps.
Click to expand...
Sorry. My bad.
Colif said:
you been having problems since 2022. It might be one bad part that has caused all of them. It might just be a small fault that trips up other things occasionally. Two different versions of windows...
just trying to help
Click to expand...
If that's the case, how can I tell which is causing these BSODs? I also only have one version of Windows on my computer. The "Windows.old" folder is a backup automatically made by Windows 11 when I updated it to version 24H2.
 
Upvote 0 Downvote
Colif said:
I quoted ubuysa, I was asking him as he might be able to tell from the dumps.
Click to expand...
Yes, it was logical processor 8 or 9 in each dump, and they will both be on core 5 (probably).

@ConorDuey2000 is it stable in Safe Mode as I suggested on post #11? Safe Mode will tell us whether this is hardware or software. I do tend to agree with @Colif that a hardware cause seems more likely, but I've also seen people constantly reinstalling the problem software/driver too.

Please let us know what happens in Safe Mode.
 
  • Like
Reactions: Colif
Upvote 0 Downvote
ubuysa said:
is it stable in Safe Mode as I suggested on post #11? Safe Mode will tell us whether this is hardware or software. I do tend to agree with @Colif that a hardware cause seems more likely, but I've also seen people constantly reinstalling the problem software/driver too.

Please let us know what happens in Safe Mode.
Click to expand...
I haven't tried safe mode, yet, but I should try it to see if it's either a software problem or a hardware problem that's causing the BSODs. I'm still thinking that it's a software problem because the BSODs are associated with Corsair iCUE and sometimes ASUS Armory Crate.
 
Upvote 0 Downvote
Icue is a painful program but not had any BSOD caused by it. Its so fun I went from having 3 parts made by Corsair to one. I only use it still as other RGB programs don't seem to see my ram. What do you use it for?

Armory Crate is so annoying I refuse to buy any Asus hardware with it.

both could be cause. What do you use Armoury crate for?
 
Upvote 0 Downvote
Colif said:
Icue is a painful program but not had any BSOD caused by it. Its so fun I went from having 3 parts made by Corsair to one. I only use it still as other RGB programs don't seem to see my ram. What do you use it for?

Armory Crate is so annoying I refuse to buy any Asus hardware with it.

both could be cause. What do you use Armoury crate for?
Click to expand...
I use iCUE for the lights on my keyboard and my RAM sticks. I don't use Armory Crate, but I think that the few BSODs that told me the process was Armory Crate were mainly iCUE's fault.
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom