IRQL_NOT_LESS_OR_EQUAL / DRIVER_IRQL_NOT_LESS_OR_EQUAL Windows 10: Complete Fix Guide

Understanding IRQL_NOT_LESS_OR_EQUAL on Windows 10

When Windows 10 displays a Blue Screen of Death (BSOD) with the stop code IRQL_NOT_LESS_OR_EQUAL (0x0000000A) or DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1), it means a software component — almost always a kernel-mode driver — tried to touch a memory address that was paged out to disk at a moment when paging is forbidden. The CPU's interrupt request level (IRQL) was too elevated for that memory access to be safe, so Windows halted the system to prevent data corruption.

The exact error string you see on screen will be one of:

• IRQL_NOT_LESS_OR_EQUAL (stop code 0x0000000A)
• DRIVER_IRQL_NOT_LESS_OR_EQUAL (stop code 0x000000D1)

Both share the same root cause family. The difference is that 0x000000D1 more explicitly blames a specific driver, while 0x0000000A can also be triggered by hardware faults (bad RAM, overclocking).

Common Scenarios and Named Drivers

Step 1: Boot into Safe Mode

If the BSOD prevents normal booting, you must reach Safe Mode first.

1. Force three consecutive hard shutdowns (hold power button) to trigger Windows Recovery Environment (WinRE).
2. Navigate to Troubleshoot → Advanced Options → Startup Settings → Restart.
3. Press 4 or F4 to boot into Safe Mode (press 5 / F5 for Safe Mode with Networking if you need internet access).

Alternatively, from a working session: press Win + R, type msconfig, go to Boot tab, check Safe boot → Minimal, click OK and restart.

Step 2: Read the Minidump File

Windows saves crash data to C:\Windows\Minidump\ as .dmp files. Analyzing these is the fastest way to identify the offending driver.

Option A — WhoCrashed (easiest):

1. Download WhoCrashed from https://www.resplendence.com/whocrashed
2. Run it and click Analyze.
3. The report will show the driver filename, e.g., nvlddmkm.sys caused a BSOD on your system.

Option B — WinDbg (most detailed):

1. Install WinDbg from the Microsoft Store or via Windows SDK.
2. Open WinDbg → File → Open Crash Dump → select the .dmp file.
3. In the command window, type: !analyze -v
4. Look for the FAULTING_MODULE and IMAGE_NAME fields in the output.

A typical WinDbg output for a GPU driver crash looks like:

BugCheck D1, {fffffa8007b3e010, 2, 0, fffff88004d3b000}
Probable cause: nvlddmkm.sys
IMAGE_NAME: nvlddmkm.sys
FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+3b2f0

Step 3: Fix the Identified Driver

3a. NVIDIA GPU Driver (nvlddmkm.sys)

This is the most frequently reported cause on Windows 10 Reddit threads.

1. Boot into Safe Mode.
2. Download Display Driver Uninstaller (DDU) from https://www.wagnardsoft.com/
3. Run DDU, select GPU → NVIDIA, click Clean and Restart.
4. After restart, download the latest NVIDIA driver from https://www.nvidia.com/Download/index.aspx and do a Custom / Clean Install.
5. If the latest driver still causes BSODs, try one version older (NVIDIA archives are at https://www.nvidia.com/en-us/drivers/unix/ and their Windows archive).

3b. Network Drivers (netio.sys, afd.sys, tcpip.sys)

These files point to the TCP/IP stack or network adapter driver.

1. Open Device Manager (devmgmt.msc).
2. Expand Network Adapters, right-click your adapter → Update driver.
3. If updating fails, right-click → Uninstall device (check "Delete driver software"), restart, and let Windows reinstall.
4. If you use a VPN client or antivirus with a network filtering component, temporarily uninstall it — many (Avast, Bitdefender, Cisco AnyConnect) inject kernel drivers that conflict with netio.sys.
5. Run: netsh winsock reset and netsh int ip reset in an elevated Command Prompt, then reboot.

3c. ntoskrnl.exe (Kernel)

When the Windows kernel itself is named, the issue is usually bad RAM, corrupted system files, or overclocking.

Repair system files first:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Run both commands in an elevated Command Prompt. Reboot afterward.

Check RAM:

• Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
• For thorough testing, use MemTest86 (bootable USB) and run at least 2 full passes.
• If you have XMP/DOCP enabled in BIOS for RAM overclocking, disable it and set RAM to its JEDEC default frequency (usually 2133 MHz or 2400 MHz).

Step 4: Check for Windows Updates and Driver Updates Broadly

Some IRQL BSODs on Windows 10 were introduced by Windows Update itself. Check:

1. Settings → Update & Security → Windows Update → View Update History.
2. If the BSOD started after a specific update, click Uninstall updates and remove it.
3. Alternatively, use System Restore to roll back to a point before the BSOD started:
   • Search for "Create a restore point" → System Restore → choose a date before the issue.

Step 5: Disable Overclocking

If your CPU, GPU, or RAM is overclocked:

1. Restart and enter BIOS/UEFI (usually Del, F2, or F10 at POST).
2. Load Optimized Defaults or manually set CPU multiplier and RAM frequency to stock.
3. Disable XMP / DOCP / EXPO profiles for RAM.
4. Save and exit.

Even factory-applied "performance" BIOS profiles can push hardware outside stable margins, especially under thermal stress.

Step 6: Fresh Windows 10 Install (Last Resort)

If the BSOD occurs during a Windows 10 fresh install or persists after all driver fixes:

1. First re-run MemTest86 — a RAM fault will cause install-time BSODs regardless of software fixes.
2. Try installing with only one RAM stick at a time, in slot A2 (refer to your motherboard manual).
3. If RAM tests pass, create a new Windows 10 installation media using the Media Creation Tool from https://www.microsoft.com/en-us/software-download/windows10 and perform a clean install.
4. Install drivers one at a time after the OS is up, starting with chipset, then GPU, then network — this isolates which driver reintroduces the BSOD.