Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen on Windows 11

Before you begin

Match the environmentUse this guide only for Windows 11 23H2, Windows 11 24H2, Windows 10 22H2 or a clearly compatible setup.

Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.

Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

Problem overview

Windows crashes with a blue screen showing DRIVER_IRQL_NOT_LESS_OR_EQUAL (stop code 0xD1). This means a kernel-mode driver accessed pageable memory at an interrupt level that was too high : almost always a buggy or corrupted third-party driver.

Common causes

A recently updated network, GPU, or audio driver
Antivirus or VPN filter drivers conflicting with Windows kernel updates
Corrupted driver files after an interrupted Windows Update
Faulty RAM surfacing as driver faults (rare, but worth ruling out)

Solution 1: Identify the failing driver from the minidump

Boot into Windows. If you cannot, hold Shift while clicking Restart to enter Safe Mode.
Install WinDbg from the Microsoft Store, then open the latest dump:

# List recent crash dumps
Get-ChildItem C:\Windows\Minidump | Sort-Object LastWriteTime -Descending

In WinDbg run !analyze -v and look for the MODULE_NAME line : that is your faulty driver (for example rtwlanu.sys = Realtek Wi-Fi).

Expert Tip

No dumps in the folder? Enable them: System Properties → Advanced → Startup and Recovery → set Write debugging information to ‘Small memory dump’.

Solution 2: Roll back or reinstall the driver

Open Device Manager (Win + X → Device Manager).
Locate the device matching the module you found.
Right-click → Properties → Driver tab → Roll Back Driver. If greyed out, choose Uninstall Device and tick ‘Attempt to remove the driver’.
Reboot : Windows reinstalls a stable driver, or download the previous version from the vendor.

Caution

Avoid third-party ‘driver updater’ utilities. They frequently install mismatched drivers and are a leading cause of this exact stop code.

Solution 3: Rule out RAM faults

If the module name varies between crashes, test memory:

# Schedules a memory test on next boot
mdsched.exe

Two passes with zero errors rules out RAM for practical purposes.

Critical

If errors appear, remove and reseat RAM sticks one at a time to isolate the faulty module before replacing hardware.

Confirm the result

Repeat the exact action that originally triggered the problem.

Confirm the original error or symptom is gone and no new warning has appeared.

If the guide changed a driver, service, package, or system setting, restart once and test again.

If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.

Questions about this fix

Can I just ignore this BSOD if it only happens once?

A single occurrence after a driver update can be transient, but repeated 0xD1 stops indicate a faulty driver that will keep crashing the kernel. Identify it before it corrupts data.

Is it safe to delete the memory dump files afterwards?

Yes. Once the issue is resolved you can delete C:\\Windows\\Minidump contents freely.

Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen on Windows 11

Before you begin

Problem overview

Common causes

Solution 1: Identify the failing driver from the minidump

Solution 2: Roll back or reinstall the driver

Solution 3: Rule out RAM faults

Confirm the result

Questions about this fix

Weighted Consensus Protocol

Did this solution resolve your issue?

Discussion (0)

Join the Discussion