How to fix the DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) blue screen
This stop code points directly at a driver: one tried to access memory it was not allowed to. Network and wifi drivers are common offenders, and the screen usually names the file. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~10 min Updated Jun 2026 88% found this helpful
Error message
DRIVER_IRQL_NOT_LESS_OR_EQUAL. Stop code 0x000000D1. A driver tried to access pageable memory at too high an interrupt level.
Summary
DRIVER_IRQL_NOT_LESS_OR_EQUAL (stop code 0x000000D1) is the driver-specific cousin of IRQL_NOT_LESS_OR_EQUAL: a device driver tried to access memory at an interrupt level it was not permitted to. The advantage is that this stop code almost always names the failing driver file (a .sys) right on the screen, so you usually know exactly what to fix. Network and wifi drivers are among the most common offenders, along with graphics and other device drivers. The fix is to identify that driver, then update it, roll it back if the crash started after an update, or remove and reinstall the device. Testing memory and repairing system files cover the rare cases where no single driver is to blame.
What this error means
Like the general IRQL stop code, this means code touched memory at an interrupt level where that memory was not safe to access. The difference is in the name: Windows has pinned the blame on a driver specifically, and usually tells you which file.
Because a driver is named, the fix is unusually direct. Network and wifi drivers show up a lot here, partly because they are updated often and partly because they run at sensitive levels. Update, roll back or remove the named driver and the crash typically stops.
Common causes
A faulty network or wifi driver.
A buggy graphics or other device driver.
A recent driver update that introduced a bug.
A newly installed device with a bad driver.
An outdated driver incompatible with the OS version.
Bad RAM (less common for this code).
Corrupt system files.
Expert insight
“This is the friendliest blue screen in the family, because it usually prints the guilty driver right there, look for the .sys file after the stop code. Network and wifi drivers are repeat offenders. So I do not guess, I read the name, then update that driver, or roll it back if a recent update started the crashes, or pull the device and reinstall it clean. Knowing the file turns this from a mystery into a five-minute job.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Read the named driver
1Note the .sys file named on the blue screen after the stop code.
2Or open the minidump in C:\Windows\Minidump with BlueScreenView to confirm it.
3That is the driver to fix.
Method 2
Update or roll back that driver
1Update the named driver from the device or PC maker.
2If the crash started after an update, roll the driver back in Device Manager.
3Match the driver to your exact hardware and Windows version.
Method 3
Reinstall the network or wifi driver
1If a network or wifi .sys is named, uninstall the adapter in Device Manager (tick to remove the driver) and reinstall the latest driver.
2Network drivers are a frequent cause of this stop code.
3Restart and test.
Method 4
Remove a recently added device
1Disconnect or uninstall a device added just before the crashes began.
2Test without it.
3Reinstall with a current driver if it is the cause.
Method 5
Test memory and repair files
1If no driver is named, run Windows Memory Diagnostic and then SFC and DISM.
2This covers the rarer memory and system-file causes.
3Reboot and watch.
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.
DRIVER_IRQL_NOT_LESS_OR_EQUAL usually names the failing driver on the screen, so read that file first and update, roll back or reinstall it. Network and wifi drivers are frequent offenders. Only fall back to memory tests and system-file repair when no single driver is named.
Frequently asked questions
What does DRIVER_IRQL_NOT_LESS_OR_EQUAL mean?
Stop code 0x000000D1 means a device driver tried to access memory at an interrupt level it was not allowed to. The blue screen usually names the failing driver file.
How do I find the driver?
Read the .sys file named on the blue screen after the stop code, or confirm it by opening the minidump in C:\Windows\Minidump with BlueScreenView.
Why are network drivers blamed so often?
Network and wifi drivers are updated frequently and run at sensitive levels, so a buggy one commonly triggers this stop code. Reinstalling the latest network driver usually fixes it.
It started after a driver update
Roll that driver back in Device Manager. A buggy driver update is one of the most common causes once a driver is named.
How is this different from IRQL_NOT_LESS_OR_EQUAL?
They mean the same kind of illegal memory access, but DRIVER_IRQL_NOT_LESS_OR_EQUAL specifically blames a driver and usually names it, making the fix more direct.
What if no driver is named?
Run Windows Memory Diagnostic to rule out RAM, then SFC and DISM to repair system files, which cover the rarer causes when no driver is identified.
Still not working?
If the named driver is current and the crash continues, the device hardware itself may be failing, or two drivers may be conflicting. Test with the device removed, and use Driver Verifier on the remaining third-party drivers to catch a second offender. You can also submit your error to us for a tailored fix.
