Drivers · critical

How to fix DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)

Drivers troubleshooting guide

What this error means

Windows stopped because a kernel-mode driver tried to access memory at an invalid address while running at a raised priority level. Microsoft says this bug check is usually caused by drivers that used improper memory addresses, and when Windows identifies the driver, it names it on the blue screen. Network and Wi-Fi drivers are frequent examples, along with VPN, antivirus and other software that installs drivers. Unlike IRQL_NOT_LESS_OR_EQUAL (0xA), this code always points to a driver rather than Windows itself.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Beginner to intermediate
Before changes
Low for steps 1–6; Driver Verifier in step 7 can cause extra crashes until it is turned off

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Photograph the blue screen, especially the file after "What failed". If Windows crashes at startup, use Safe Mode (recovery menu > Troubleshoot > Advanced options > Startup Settings > Restart > 4). If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Note the driver file on the blue screen

Microsoft explains that when the driver is identified, its name is shown on the blue screen.

  1. Look for "What failed: name.sys" and search the file name to find its device or program.
  2. Examples: Netwtw*.sys or rtwlan*.sys (Wi-Fi), rt640x64.sys or e1d*.sys (Ethernet), ndis.sys or tcpip.sys (Windows network components, usually triggered by a network driver or VPN).
What to expect

You know which driver or device is involved.

If it does not help

If no file is shown, continue with step 2.

Browse related errors
02Check Event Viewer

Microsoft recommends the System log for messages that identify the device or driver.

  1. Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System.
  2. Look at errors and warnings just before the BugCheck event (ID 1001), especially from network adapters or drivers.
What to expect

You find the device or driver that logged problems before the crash.

If it does not help

Continue with step 3 for that driver.

Browse related errors
03Update, roll back or remove the driver

Microsoft's advice for a named driver is to disable it or get an update from the maker.

  1. If the crashes began after a driver update, open Device Manager > device Properties > Driver > Roll Back Driver.
  2. Otherwise install the latest driver from the device or PC maker (for Wi-Fi and Ethernet, the laptop maker or Intel, Realtek, Killer).
  3. If the device is not needed, disable it in Device Manager to confirm it is the cause.

Avoid driver updater programs.

What to expect

The crashes stop.

If it does not help

If the named file is a Windows network file such as ndis.sys or tcpip.sys, update the network adapter driver and check step 4.

Browse related errors
04Remove VPN and security software that adds drivers

VPN clients, firewalls and antivirus programs install network and filter drivers that commonly trigger this stop code.

  1. Uninstall recently installed or updated VPN, firewall, antivirus or network monitoring software in Settings > Apps > Installed apps.
  2. Restart and use the PC normally.

Keep Microsoft Defender on while another antivirus is removed.

What to expect

The crashes stop without the program.

If it does not help

Install the newest version later and check whether the crash returns.

Browse related errors
05Check new hardware compatibility

Microsoft recommends confirming that newly installed hardware is compatible with your Windows version.

  1. If you added a device recently (Wi-Fi card, USB adapter, capture card), disconnect it and test.
  2. Check the maker's website for drivers for your exact Windows version.
What to expect

You know whether the new device causes the crash.

If it does not help

Replace devices that have no driver for your Windows version.

Browse related errors
06Test the memory

Faulty RAM can corrupt the data a driver works with, which looks like a driver bug.

  1. Turn off XMP or EXPO in the BIOS for testing.
  2. Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
What to expect

The memory test passes.

If it does not help

If it fails, follow the memory test errors guide on this site.

Browse related errors
07Find the driver with Driver Verifier

Microsoft recommends Driver Verifier, verifying as few drivers as possible, to catch the faulty driver.

  1. Create a restore point (search "Create a restore point").
  2. Open Command Prompt (Admin), type verifier, choose Create standard settings > Select driver names from a list, and tick only non-Microsoft drivers.
  3. Restart and use the PC until it crashes; the blue screen names the driver. Then run verifier /reset and restart.

Driver Verifier deliberately crashes the PC when it finds a problem. Turn it off when you are done.

What to expect

A specific driver is named for you to update or remove.

If it does not help

If Windows does not start with Driver Verifier on, start in Safe Mode and run verifier /reset.

Browse related errors

Possible causes

  • A faulty or outdated driver, often network, Wi-Fi, USB or audio
  • VPN, antivirus, firewall or other software with kernel drivers
  • A driver installed or updated shortly before the crashes
  • New hardware that is not compatible with your Windows version
  • Faulty RAM making a driver read bad data

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc
devmgmt.msc
mdsched.exe

Sources & further reading