Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen

Before you begin

Match the environmentUse this guide only for Windows 10, Windows 11 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

Your computer suddenly crashes to a Blue Screen of Death (BSOD) displaying the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL. This error indicates that a hardware driver attempted to access a memory address it did not have permission to access, forcing Windows to shut down to prevent data corruption.

Common causes

Faulty or outdated third-party drivers (antivirus, network adapters, peripheral software)
Corrupted system files following an aborted update
Defective RAM sticks or unstable XMP/EXPO memory overclocks
Overheating CPU or GPU causing memory access errors

Solution 1: Identify the faulty driver with WinDbg

Download and install WinDbg Preview from the Microsoft Store.
Open WinDbg as an administrator.
Go to File > Open dump file and navigate to C:\Windows\Minidump.
Select the most recent .dmp file.
Once the dump loads, click on the blue !analyze -v link in the command window.
Scroll down through the analysis output and look for MODULE_NAME and IMAGE_NAME. This will tell you the exact driver (e.g., rtwlane.sys for Realtek Wi-Fi) that caused the crash.

Expert Tip

Once you identify the .sys file, search online to find which hardware or software it belongs to. You can then update, uninstall, or roll back that specific driver in Device Manager.

Solution 2: Use Driver Verifier

If the minidump is inconclusive, Windows can stress-test drivers to catch the culprit.

Press Win + R, type verifier, and press Enter.
Select Create standard settings and click Next.
Select Automatically select all drivers installed on this computer and click Finish.
Restart your computer. Use the PC normally until it crashes.
Boot into Safe Mode, open Command Prompt, type verifier /reset to disable the tool, and then check the new minidump with WinDbg.

Solution 3: Test memory stability

Since IRQL errors are memory-related, bad RAM might be the real issue.

Turn off any RAM overclocks (XMP/EXPO) in your BIOS.
Download MemTest86 and create a bootable USB drive.
Boot from the USB and allow MemTest86 to run at least 4 passes. If any red errors appear, you have a faulty RAM stick that needs to be replaced.

Critical

Using Driver Verifier forces your PC to crash if it detects a bad driver. Ensure you have backups and know how to boot into Safe Mode to disable it before enabling this tool.

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

What causes an IRQL error?

It occurs when a kernel-mode driver attempts to access memory at an unauthorized IRQL (Interrupt Request Level), usually due to bad coding or memory corruption.

Do I need to be a developer to use WinDbg?

No, while it is a developer tool, you only need to run a single command (!analyze -v) to see which driver caused the crash.

Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen

Before you begin

Problem overview

Common causes

Solution 1: Identify the faulty driver with WinDbg

Solution 2: Use Driver Verifier

Solution 3: Test memory stability

Confirm the result

Questions about this fix

Weighted Consensus Protocol

Did this solution resolve your issue?

Discussion (0)

Join the Discussion