How to fix the IRQL_NOT_LESS_OR_EQUAL (0x0000000A) blue screen
This stop code means a driver or the system tried to access memory it was not allowed to, at a level it should not. A faulty driver or bad RAM is almost always behind it. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~11 min Updated Jun 2026 88% found this helpful
Error message
IRQL_NOT_LESS_OR_EQUAL. Stop code 0x0000000A. A driver accessed memory at an invalid process level.
Summary
IRQL_NOT_LESS_OR_EQUAL (stop code 0x0000000A) means a kernel-mode driver, or sometimes the system, tried to access a memory address at an interrupt level it was not permitted to. In plain terms, a piece of software touched memory it should not have, and Windows stopped to protect itself. The overwhelmingly common cause is a faulty, outdated or incompatible driver, with bad or unstable RAM the next most likely. It often starts after a driver update, a new device, or a memory overclock. The fix is to identify and update or roll back the problem driver (the crash often names the failing .sys file), test your memory, reset any overclock to stock, and repair system files. Reading the minidump with a tool like BlueScreenView quickly points at the offending driver.
What this error means
Windows runs work at different interrupt request levels, or IRQLs. Code running at a high level may only touch memory that is always resident. When a driver running at a high IRQL reaches for memory that has been paged out or is simply invalid, Windows cannot safely continue and raises this stop code.
That is why it points at drivers and memory. A buggy driver makes an illegal access, or failing RAM returns the wrong data so a valid access lands somewhere invalid. Fixing the driver and verifying the memory removes both causes.
Common causes
A faulty, outdated or incompatible device driver.
Bad or failing RAM modules.
An unstable memory or CPU overclock.
A recent driver update that introduced a bug.
A newly installed device with a bad driver.
Corrupt system files.
Conflicting low-level software such as antivirus.
Expert insight
“IRQL_NOT_LESS_OR_EQUAL is almost a synonym for bad driver. Something touched memory it had no business touching, and nine times out of ten it is a driver that was just updated or a new gadget that brought a rough driver with it. I read the minidump with BlueScreenView to see which .sys file blew up, update or roll back that one, and if nothing is obvious I test the RAM, because failing memory produces the exact same crash. Reset any overclock to stock while you are at it.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Read the crash to find the driver
1Note any module named on the blue screen (a .sys file).
2Or open the minidump in C:\Windows\Minidump with a free tool such as BlueScreenView to see the driver that caused the fault.
3That tells you exactly which driver to fix.
Method 2
Update or roll back the driver
1Update the named driver, or your storage, graphics, network and chipset drivers, from the device or PC maker.
2If the crash started right after a driver update, roll that driver back in Device Manager.
3Remove a newly added device to test.
Method 3
Test your memory
1Run Windows Memory Diagnostic (type mdsched.exe), or MemTest86 for a thorough test.
2If a stick fails, reseat or replace it.
3Bad RAM produces this exact stop code.
Method 4
Reset any overclock
1If you overclock the CPU or memory, set everything back to stock or default in the BIOS.
2Unstable overclocks frequently cause this crash.
3Test at stock speeds.
Method 5
Repair system files
1Run DISM /Online /Cleanup-Image /RestoreHealth then SFC /scannow from an elevated prompt.
2This repairs corrupt system files that can trigger the stop code.
3Reboot and watch for the crash.
Method 6
Boot into Safe Mode if it keeps crashing
1If the PC will not stay up, let it fail twice so it enters the Recovery environment, then choose Troubleshoot, Advanced options, Startup Settings, and pick Safe Mode with Networking.
2Safe Mode loads only basic drivers, so you can work on the fix without the crash recurring.
3From there, update or roll back drivers and run the repairs below.
Treat IRQL_NOT_LESS_OR_EQUAL as a driver problem first: read the minidump to find the failing module, then update or roll it back. If no driver stands out, test the RAM and reset any overclock, since unstable or failing memory causes the identical crash. Repair system files last if the driver and memory check out.
Frequently asked questions
What does IRQL_NOT_LESS_OR_EQUAL mean?
Stop code 0x0000000A means a driver or the system tried to access memory at an interrupt level it was not allowed to. A faulty driver or bad RAM is almost always the cause.
How do I find which driver caused it?
Note any .sys file named on the blue screen, or open the minidump in C:\Windows\Minidump with a tool like BlueScreenView, which names the driver that caused the fault.
Could bad RAM cause this?
Yes. Failing or unstable memory returns wrong data and produces this exact stop code. Run Windows Memory Diagnostic or MemTest86, and reseat or replace any failing stick.
It started after a driver update
Roll that driver back in Device Manager. A buggy driver update is one of the most common triggers for IRQL_NOT_LESS_OR_EQUAL.
Can an overclock cause it?
Yes. An unstable CPU or memory overclock often triggers this crash. Reset everything to stock in the BIOS and test at default speeds.
What if it crashes before Windows loads?
Let it fail twice to enter the Recovery environment, then boot into Safe Mode with Networking to update or roll back drivers without the crash recurring.
Still not working?
If no single driver stands out, enable Driver Verifier on third-party drivers to force the culprit to reveal itself in the next crash dump, then disable Verifier once you have the name. Be ready to boot into Safe Mode, since Verifier can increase crashes until the bad driver is fixed. You can also submit your error to us for a tailored fix.
