Constant Blue Screen with Error: IRQL_NOT_LESS_OR_EQUAL (Win 10)

[avrona]

So I just reset the CMOS and after fighting with some weird CPU fan errors that prevented me from booting to Windows, I got everything working again just for it to not solve the issue.

 

[EarthDog]

Let me guess... you dont have a fan plugged into the CPU header and you needed to disable monitoring for it..

 

[avrona]

Let me guess... you dont have a fan plugged into the CPU header and you needed to disable monitoring for it..

I mean I do have a CPU fan plugged in somewhere, but probably not the CPU header seeing how it wasn't detected. So yeah I had to ignore its motoring.

 

[EarthDog]

Maybe plug it in there so you do not have to disable it every time you reset the BIOS.

 

[eidairaman1]

I mean I do have a CPU fan plugged in somewhere, but probably not the CPU header seeing how it wasn't detected. So yeah I had to ignore its motoring.

Read your board manual foe the cpu fan header and plug it in there.

 

[avrona]

Read your board manual foe the cpu fan header and plug it in there.

I don't have a manual for it so I'm just looking for it online now. Besides I found a way round it anyway, so I'll try to find some more potential solutions to my bigger problem first.

 

[eidairaman1]

I don't have a manual for it so I'm just looking for it online now. Besides I found a way round it anyway, so I'll try to find some more potential solutions to my bigger problem first.

Asus.com has your manuals for your specific board

 

[avrona]

Asus.com has your manuals for your specific board

Ok good, because I don't have a manual for that or any other parts of my PC.

 

[EarthDog]

Ok good, because I don't have a manual for that or any other parts of my PC.

We've mentioned previously to go to the website and DL the manual. If not on this PC, another PC... a phone... etc.

So long as you are not literally blind, there is a label on the fan header for the CPU. It is typically found................. wait for it.................. around the CPU (upper right corner typically). Just look for it, and plug it in there and the problem goes away.

 

[Aaron_Henderson]

I would try a fresh install of a different OS...and do some error checking / load testing there...potentially from a live usb os with SSd/HDD disconnected...one thing you can do to test your PSU without swapping...underclock your CPU and GPU heavily, and do some load tests...also...run one stick of Ram and try it in several different slots.

 

[avrona]

I would try a fresh install of a different OS...and do some error checking / load testing there...potentially from a live usb os with SSd/HDD disconnected...one thing you can do to test your PSU without swapping...underclock your CPU and GPU heavily, and do some load tests...also...run one stick of Ram and try it in several different slots.

That's actually similar to what I am doing now. I underclocked my CPU from its stock speeds of 4GHz it normally runs on to 3GHz to see if it's something to do with VRMs.

 

[avrona]

So I ran Blue Screen View and here is the error log from that:

==================================================
Dump File : 022719-13921-01.dmp
Crash Time : 27/02/2019 13:35:36
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0000003b`fc5ff910
Parameter 2 : 00000000`0000000f
Parameter 3 : 00000000`00000001
Parameter 4 : fffff802`5c2978b7
Caused By Driver : hal.dll
Caused By Address : hal.dll+178b7
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.194 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1b3440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\022719-13921-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 17763
Dump File Size : 444,201
Dump File Time : 27/02/2019 13:36:21
==================================================

 

[lexluthermiester]

So I ran Blue Screen View and here is the error log from that:

==================================================
Dump File : 022719-13921-01.dmp
Crash Time : 27/02/2019 13:35:36
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0000003b`fc5ff910
Parameter 2 : 00000000`0000000f
Parameter 3 : 00000000`00000001
Parameter 4 : fffff802`5c2978b7
Caused By Driver : hal.dll
Caused By Address : hal.dll+178b7
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17763.194 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1b3440
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\022719-13921-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 17763
Dump File Size : 444,201
Dump File Time : 27/02/2019 13:36:21
==================================================

Given that information, it seems very likely to be a PSU problem. ntoskrnl.exe and hal.dll are two of the most stable and well refined parts of Windows. For them to be crashing and throwing out those errors is a strong indication of a brown-out(voltage droop) situation being present in the system. Replace your PSU with a decent quality 600w or better unit and this problem will very likely go away.

 

[Shambles1980]

you should use the pool command to check the address(s) that the bsod has told you about, it could be a page file issue.
i would also use driver verifier as a sanity checker.
crashes under load are usually a psu issue. but could be an addressing issue.

 

[avrona]

you should use the pool command to check the address(s) that the bsod has told you about, it could be a page file issue.
i would also use driver verifier as a sanity checker.
crashes under load are usually a psu issue. but could be an addressing issue.

For now I just reinstalled Windows to see if that could fix those broken files.

 

[Final_Fighter]

you need to up the voltage to the ram. Bones is probably spot on. also, what does the board report the 12v, 5v, and 3.3v rails at? sometimes a bad power supply can be checked by just reading these voltages. try running something like hwinfo and put the pc under a load while monitoring the voltages to see how far they dip.

but seriously try raising the memory voltage to 1.65v it should be fine.

 

[PsychoCaseFansCocainCrazy]

This is indeed a voltage issue. You should check the voltage requirement your ram runs on, and make sure that it's voltage doesn't drop below that. For example, I have Corsair Vengeance LPX 2x 8gb sticks, at 3200Mhz. Their voltage requirement is 1,35V.

If I set this to 1,34V, Windows10 will instantly BSoD with this error. Running them at 1,36V-1,40V is no problem.

One of the ways to do this is to use your motherboards chipset application, in my case AMD Command Center, and manually set the DRAM Voltage slider on atleast the required voltage. This is not a persistent way to do it(resets on restart), but I'm sure there's a guide somewhere that'll explain how to make it persistent. Probably in your BIOS.

 

[Jetster]

Have you played with the registry at all? Tweaked any other system settings?

 

[avrona]

Have you played with the registry at all? Tweaked any other system settings?

No I haven't changed any of that before it started happening.

Ok I've reinstalled Windows, and that seems to have potentially solved the issue.