Constant Blue Screen with Error: IRQL_NOT_LESS_OR_EQUAL (Win 10)

[avrona]

I've had my PC crash 5 times now today with this error message. It never happened before and it was behaving completely normally before today. Does anyone know how to fix this?

[Turtle Rig]

6 minutes ago, avrona said:

I've had my PC crash 5 times now today with this error message. It never happened before and it was behaving completely normally before today. Does anyone know how to fix this?

That error means your overclocking or your CPU or RAM is not stable.  I suggest go into BIOS and set to defaults and see if it happens again.

[avrona]

1 minute ago, Turtle Rig said:

That error means your overclocking or your CPU or RAM is not stable.  I suggest go into BIOS and set to defaults and see if it happens again.

Neither of them are overclocked though.

[BobVonBob]

Generally caused by driver issues or failing RAM. Try the solutions on the following pages.

 

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-crashing-on-irql-not-less-or-equal/d864928b-cff7-424c-a917-2002ea6ab9f4

https://neosmart.net/wiki/irql-not-less-or-equal/

[Turtle Rig]

Just now, avrona said:

Neither of them are overclocked though.

Can you check in this BIOS as to your DRAM speed and the DRAM timings ?  If they are set correctly and your still getting that BSOD that usually means RAM issues.  You might want to try a stick of RAM at a time.  I mean it is either CPU or RAM and I doubt its CPU so do the RAM thingie one of the sticks maybe faulty.  Also please let us know your complete system specs so we can help you better.

[dfsdfgfkjsefoiqzemnd]

https://docs.microsoft.com/en-us/previous-versions/ms854226(v=msdn.10)

 

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access.

 

99% of the time this error is caused by a driver issue.  Troubleshooting those isn't always easy. 

Never had to deal with Bluescreens on Win10, but I did on 8.1 when I tried that on my main PC.  There I used a tool called BlueScreenView to read the crash dumps and some Google-fu to find the culprit.

 

 

[avrona]

39 minutes ago, Turtle Rig said:

Can you check in this BIOS as to your DRAM speed and the DRAM timings ?  If they are set correctly and your still getting that BSOD that usually means RAM issues.  You might want to try a stick of RAM at a time.  I mean it is either CPU or RAM and I doubt its CPU so do the RAM thingie one of the sticks maybe faulty.  Also please let us know your complete system specs so we can help you better.

My full specs are:

• CPU: AMD fx-8350
• Graphics card: GTX 1080 Ti
• Motherboard: ASUS M5A97
• RAM: 16GB DDR3 2207 MHz
• Sound card: Sound Blaster Z
• PSU: XFX TS 550W Bronze

[avrona]

So after updating my graphics drivers, it stopped for a few hours, then started up again. Then after doing some weird changes to get devices into MSI mode it also stopped for a while, and now it started again.

[avrona]

And it still hasn't been fixed with manually installing drivers or using an MSI mode utility.

[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
==================================================

[phamvancao]

Have you solved the problem Avrona? Have you tried to reinstall original graphics driver, some drivers were released to work on specific hardware only, the newest version may not compatible with your hardware. That's why a lot of computers still using Windows XP.

 

If you not sure about it, you should run Driver Verifier, it will check for incompatible drivers for you. There some more methods to fix this error if you are not sure the root cause.