How to Fix: DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen Error

Quick Fix

In most cases this crash is caused by one specific driver (often GPU, network/Wi-Fi, or chipset). Try this first:

1. Restart the PC — if it boots normally, open Settings > Windows Update > Advanced options > Optional updates and install any pending driver updates.
2. If the crash started right after installing/updating a driver, open Device Manager, right-click that device, go to the Driver tab, and click Roll Back Driver (or Uninstall device, then let Windows reinstall it).
3. If it started after a GPU driver update, download the latest driver directly from NVIDIA/AMD/Intel and do a clean install.

Step-by-Step Guide

What DRIVER_IRQL_NOT_LESS_OR_EQUAL Means

DRIVER_IRQL_NOT_LESS_OR_EQUAL is a Windows Blue Screen of Death (BSOD) with the stop code 0x000000D1. The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. In plain terms, a driver reached into a piece of memory it wasn’t allowed to touch while Windows was running at a priority level (IRQL, or Interrupt Request Level) that doesn’t permit that kind of access, so Windows immediately halts to prevent deeper corruption. This is distinct from but closely related to the more general IRQL_NOT_LESS_OR_EQUAL (0xA) error — 0xA is IRQL_NOT_LESS_OR_EQUAL; 0xD1 is DRIVER_IRQL_NOT_LESS_OR_EQUAL and is more directly tied to a driver accessing pageable memory at too high an IRQL. Either way, the practical troubleshooting is nearly identical: chase down the misbehaving driver, and rule out memory and system file problems.

Common triggers include: faulty or outdated drivers, memory issues, or hardware problems. Specific culprits reported repeatedly in crash dumps include graphics drivers, network/Wi-Fi adapter drivers, storage controller drivers, chipset drivers, VPN or antivirus filter drivers, and occasionally corrupted system files or bad RAM. Overclocking and unstable RAM timings/XMP profiles are also frequently implicated. This guide covers fixes roughly in order from quickest to most advanced — work through them in order and reboot/test after each change.

Step-by-Step Fixes

1. Note the driver name on the crash screen (if shown)

Windows sometimes prints a specific file name on the blue screen or in the crash dump, such as a graphics driver, a network driver, or a Microsoft framework file. Windows usually prints the driver filename near the bottom of the error screen, for example nvlddmkm.sys (NVIDIA GPU driver), tcpip.sys (network driver), or ntoskrnl.exe (Windows kernel). If a third-party file name is shown, that vendor’s driver is your prime suspect — skip ahead to Step 3 or 4 for that device. If only ntoskrnl.exe or Wdf01000.sys (Kernel Mode Driver Framework) is listed, don’t assume Windows itself is broken — these are often just the component that caught another driver’s mistake, and deeper analysis (Step 6) is needed to find the real cause.

2. Restart and check Windows Update

Reboot the PC normally first. Then check for updates, since on Windows 11, the error IRQL_not_less_or_equal can be caused by drivers, memory, or security software, and Microsoft periodically ships fixes and driver updates this way. Go to Settings > Windows Update > Advanced options > Optional updates, and install anything listed there, as this section often contains hardware-specific driver updates not delivered automatically. Restart afterward even if not prompted.

3. Update or roll back the suspect driver

Open Device Manager (right-click Start menu). Look for any device with a yellow warning icon, or go straight to the device implicated by the crash dump (commonly network adapter, GPU, or storage controller). Right-click it, choose Properties > Driver tab. If the problem began right after a driver update, click Roll Back Driver. If not, try Update Driver, and if that doesn’t help, uninstall the device (check “Attempt to remove the driver” if offered) and let Windows reinstall it on reboot, or download the latest version directly from the manufacturer’s website (AMD/NVIDIA/Intel for GPUs, or your motherboard/laptop maker’s support page for chipset and network drivers) rather than relying solely on Windows Update.

4. Do a clean GPU driver reinstall

Graphics drivers are one of the single most common causes of this crash. In all but one instance, the cause was a buggy Nvidia GeForce graphics driver, according to one long-time troubleshooter’s experience, though AMD and Intel drivers can also be responsible. Download the latest driver package from the manufacturer’s site, and during installation choose the clean install / custom install option to remove leftover files and configuration from the previous driver before installing fresh.

5. Rule out third-party software conflicts (clean boot)

Services from other non-Microsoft programs can also cause conflicts that might trigger the “IRQL” error. Perform a clean boot to start Windows with only essential drivers and services: run msconfig, go to the Services tab, check “Hide all Microsoft services,” then disable everything remaining, and restart. If the crashes stop, re-enable services in batches to find the offender — security software, VPN clients, and antivirus filter drivers are common suspects here.

6. Check system files and disk integrity

Open an administrator Command Prompt and run sfc /scannow to detect and repair corrupted Windows system files. If issues are found and not fully fixed, follow up with DISM /Online /Cleanup-Image /RestoreHealth, then run SFC again. You can also run chkdsk C: /f to check the drive for file system errors (this will require a restart to complete).

7. Test your RAM

Faulty or incompatible memory is a well-documented cause: one experienced troubleshooter noted they “found out through process of elimination that it was a bad stick of RAM” after ruling out drivers. Run the built-in Windows Memory Diagnostic Tool (search for it in the Start menu, or press Win+R and type mdsched.exe), selecting the Extended test mode (press F1, then arrow to “Extended,” then F10) for a more thorough scan. If you recently enabled XMP/EXPO or manually set RAM timings, try reverting to default JEDEC speeds and timings to see if that stabilizes the system, since manually configured or out-of-spec memory settings are a known contributor to this error.

8. Disconnect peripherals and check for overheating/overclocking

Unplug non-essential USB devices (docks, capture cards, external drives, controllers) and reboot to see if the crash stops, since faulty peripherals and their drivers can trigger this bug check. If you have any CPU or GPU overclock, undervolt, or “performance/turbo” BIOS profile active, revert it to default/stock settings, as instability from overclocking is a recognized cause. Also verify your CPU and GPU aren’t overheating, especially if crashes cluster around gaming or heavy load.

9. Advanced: analyze the minidump or use Driver Verifier

If the above steps don’t resolve it, check C:WindowsMinidump for .dmp files created at each crash. These can be opened with the free WinDbg tool or a simpler dump reader to identify the exact faulting driver. For a more aggressive diagnostic, Windows includes Driver Verifier (run verifier from the Run box), which stress-tests drivers and forces a crash that names the true offending driver rather than a downstream symptom — the verified drivers will be bounds checked, and the machine will Bugcheck on the cause (rather than the effect). Create a System Restore point first, since Driver Verifier can make an unstable system crash more often while enabled, then disable it afterward and review the new minidump.

10. When to seek more specialized help

If you cannot boot into Windows at all, or the crash happens even during a fresh Windows installation from USB, this points toward a hardware or firmware issue (motherboard, RAM, or storage controller) rather than a software fix, and may require testing components on different hardware or consulting a repair technician. If minidump analysis clearly names a manufacturer-specific driver (e.g., a laptop OEM’s chipset or fingerprint reader driver) that has no newer version available, contact that manufacturer’s official support. If you suspect failing hardware (RAM, SSD, or motherboard), swapping components one at a time or testing on a bench, as some forum troubleshooters have done, is the most reliable way to confirm before replacing parts. This entire process applies to Windows 10 and Windows 11 desktop and laptop PCs; it is not applicable to macOS, consoles, or mobile devices, which do not use this Windows-specific stop code.