How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) in Windows 11

Experiencing an abrupt Blue Screen of Death (BSOD) displaying the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL (bugcheck 0x000000D1) interrupts critical work, streaming, or gaming in Windows 11. Often accompanied by a specific driver filename (such as kbdclass.sys, storport.sys, ndis.sys, nvlddmkm.sys, or tcpip.sys), this stop code indicates that a kernel-mode device driver attempted to access a pageable or invalid memory address at an Interrupt Request Level (IRQL) that was too high. In Windows kernel architecture, when an interrupt occurs at elevated IRQL, the memory management subsystem cannot perform disk paging operations. If a driver references memory that has been paged out to disk or contains an invalid pointer, Windows triggers bugcheck 0x000000D1 to prevent corrupted data from overwriting system files. This comprehensive technical guide details how to read memory dumps, isolate the failing driver, and resolve the error permanently.

What Causes DRIVER_IRQL_NOT_LESS_OR_EQUAL?

The error represents a driver-level memory addressing violation. Common triggers include:

  • Faulty or Incompatible Device Drivers: Network adapter drivers (ndis.sys, netwtw10.sys), graphics drivers (nvlddmkm.sys, amdkmdag.sys), or storage controllers (storport.sys) containing unhandled null pointers.
  • Corrupted Kernel Memory or Driver Cache: Damaged system driver binaries inside C:\Windows\System32\drivers caused by sudden power cuts or failed updates.
  • Third-Party Antivirus or VPN Virtual Network Adapters: Filter drivers (such as those installed by NordVPN, OpenVPN, or security suites) mismanaging packet buffers at high IRQL.
  • Physical Memory (RAM) Faults: Defective memory sectors causing valid memory addresses to return corrupt pointer addresses.
  • Outdated Motherboard Chipset Firmware: Incompatible bus controller drivers failing to manage device power state transitions.

Method 1: Identify the Failing Driver via Minidump Analysis

Finding the exact .sys file responsible for the crash eliminates guesswork during driver troubleshooting.

  1. If the blue screen itself listed a file ending in .sys (e.g., nvlddmkm.sys), note down the filename immediately.
  2. If no file was displayed, download the free, lightweight utility BlueScreenView (by NirSoft) or WinDbg from the Microsoft Store.
  3. Launch BlueScreenView. It automatically scans your C:\Windows\Minidump directory.
  4. Click on the latest crash dump record at the top.
  5. Examine the lower pane. The driver highlighted in pink or red is the offending binary:
    • nvlddmkm.sys or amdkmdag.sys = Graphics card driver.
    • ndis.sys, tcpip.sys, or netwtw10.sys = Wi-Fi or Ethernet network driver.
    • storport.sys or storahci.sys = Storage controller / NVMe SSD driver.
    • kbdclass.sys or mouclass.sys = Keyboard / Mouse input filter driver.

Method 2: Roll Back or Reinstall the Problematic Driver

Restoring a previously working driver or performing a clean reinstallation resolves driver memory addressing bugs.

  1. Press Windows Key + X and choose Device Manager.
  2. Locate the hardware device identified in Method 1:
    • For graphics: Expand Display adapters.
    • For networking: Expand Network adapters.
    • For storage: Expand Storage controllers.
  3. Right-click the device and select Properties.
  4. Go to the Driver tab:
    • If the option is available, click Roll Back Driver to revert to the previous version.
    • If Roll Back is greyed out, click Update driver > Search automatically for drivers.
  5. For graphics drivers, download the latest official package directly from NVIDIA, AMD, or Intel and select “Perform a clean installation” during setup.
  6. Restart your computer.

Method 3: Repair Corrupted Windows System Files via DISM and SFC

Ensuring core kernel driver frameworks (like ndis.sys and ntoskrnl.exe) are authentic and undamaged.

  1. Press Windows Key + X and select Terminal (Admin) or Command Prompt (Admin).
  2. Run the DISM image health restoration command:
    dism /online /cleanup-image /restorehealth
  3. Once DISM verification finishes, run System File Checker:
    sfc /scannow
  4. Wait for the scan to reach 100%. If corrupted files were repaired, reboot your PC to apply clean binaries.

Method 4: Uninstall Virtual Network Adapters and VPN Clients

Virtual TAP/TUN network adapters frequently cause high-IRQL deadlocks in the Windows TCP/IP networking stack.

  1. Open Settings > Apps > Installed apps.
  2. Locate any installed VPN clients (NordVPN, ExpressVPN, Surfshark, OpenVPN) or virtual machine platforms (VirtualBox, VMware).
  3. Temporarily uninstall the software.
  4. Press Windows Key + R, type ncpa.cpl, and press Enter.
  5. If any orphaned virtual network adapters remain, right-click and delete them.
  6. Restart your PC.

Method 5: Test RAM for Physical Memory Corruption

If the blue screen occurs with varying driver names on each crash, failing physical RAM is the root cause.

  1. Press Windows Key + R, type mdsched.exe, and press Enter.
  2. Select Restart now and check for problems.
  3. Allow the Windows Memory Diagnostic to perform a complete hardware scan.
  4. If errors are reported, enter your UEFI/BIOS and disable any active memory overclocks (XMP, DOCP, or EXPO).
  5. If instability persists at stock JEDEC memory speeds, test individual memory sticks one by one to isolate and replace the damaged module.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.