IRQL_NOT_LESS_OR_EQUAL: Complete Fix Guide for Windows Blue Screen Error

Understanding the IRQL_NOT_LESS_OR_EQUAL Error

The full stop code you will see on the Windows blue screen is:

Your PC ran into a problem and needs to restart.
Stop code: IRQL_NOT_LESS_OR_EQUAL

The underlying bug check code is 0x0000000A. This means Windows detected that a kernel thread tried to access a memory address that was pageable (or completely invalid) while running at an elevated Interrupt Request Level (IRQL). Because paging is disabled at high IRQLs, the kernel has no choice but to halt the system to prevent data corruption.

In Polish-language Windows environments you may see: "Kod zatrzymania: DRIVER_IRQL_NOT_LESS_OR_EQUAL" — this is the driver-specific variant (bug check 0x000000D1), which pinpoints the problem even more directly to a specific kernel driver.

Step 1: Capture the Crash Dump and Identify the Offending Driver

Before fixing anything, you need to know what crashed. Windows writes a minidump file every time a BSOD occurs.

Enable minidumps (if not already on):

1. Press Win + R, type sysdm.cpl, press Enter.
2. Go to Advanced → Startup and Recovery → Settings.
3. Under Write debugging information, select Small memory dump (256 KB).
4. Note the dump file location (default: %SystemRoot%\Minidump).

Analyze with BlueScreenView (no WinDbg needed):

• Download BlueScreenView from NirSoft: https://www.nirsoft.net/utils/blue_screen_view.html
• Open it and look at the column "Caused By Driver". This will directly name the .sys file responsible.

Analyze with WinDbg (advanced):

• Install WinDbg from the Windows SDK or the Microsoft Store.
• Open the latest .dmp file from C:\Windows\Minidump\.
• Run !analyze -v to get a detailed stack trace and the faulting module.

The output will include lines like:

Probable cause: <driver_name>.sys
IRP Stack Location: ...
Faulting Address: fffff880`04a1b3c0

Note down the exact driver filename — you will need it in Step 2.

Step 2: Boot into Safe Mode (If System Won't Start Normally)

If Windows keeps crashing before you can log in:

1. Force three consecutive hard resets (hold power button until shutdown, then power on). Windows will enter Automatic Repair mode.
2. Navigate to Advanced Options → Startup Settings → Restart.
3. Press 4 for Safe Mode or 5 for Safe Mode with Networking.

In Safe Mode, Windows loads only essential drivers, so you can safely perform the steps below.

Step 3: Update, Roll Back, or Uninstall the Offending Driver

Option A – Update the driver:

1. Press Win + X → Device Manager.
2. Locate the device associated with the .sys file found in Step 1 (e.g., a network adapter, GPU, or storage controller).
3. Right-click → Update driver → Search automatically for drivers.
4. If Windows doesn't find a newer driver, visit the manufacturer's website directly.

Option B – Roll back the driver:

1. In Device Manager, right-click the device → Properties → Driver tab.
2. Click Roll Back Driver if the option is available.

Option C – Uninstall the driver completely:

1. Right-click the device → Uninstall device → check Delete the driver software for this device.
2. Restart. Windows will reinstall a generic driver.

Common culprits by driver filename:

• ndis.sys → Network driver (update NIC firmware/driver)
• ntfs.sys → Disk / filesystem issue (run CHKDSK)
• dxgmms2.sys → GPU driver (update or DDU-clean reinstall)
• tcpip.sys → TCP/IP stack (run netsh winsock reset)
• storport.sys → Storage controller (check SATA/NVMe firmware)

Step 4: Repair System Files with SFC and DISM

Corrupted Windows system files can cause drivers to behave erratically. Run these commands in an elevated Command Prompt (Run as Administrator):

# Step 4a: Run DISM to repair the Windows image first
DISM /Online /Cleanup-Image /RestoreHealth

# Step 4b: Run System File Checker
sfc /scannow

# Step 4c: Check disk for errors on C: drive (schedule for next reboot)
chkdsk C: /f /r /x

After all three complete, reboot and monitor for further crashes.

Step 5: Test Your RAM

Faulty RAM is a silent but common cause of IRQL errors. Two tools are available:

Windows Memory Diagnostic (built-in):

1. Press Win + R → type mdsched.exe → Enter.
2. Choose Restart now and check for problems.
3. The test runs before Windows loads. Results appear after reboot in Event Viewer under Windows Logs → System, source MemoryDiagnostics-Results.

MemTest86 (more thorough):

• Download from https://www.memtest86.com/
• Create a bootable USB and run at least 2 full passes.
• Any errors = RAM is defective. Try removing one DIMM at a time to isolate the bad stick.

Step 6: Check for Overclocking and Reset BIOS/UEFI

Overclocking CPU, RAM (XMP/EXPO profiles), or GPU can push components beyond stable thresholds and trigger IRQL crashes:

1. Restart and enter BIOS/UEFI (typically Del, F2, or F10 on startup).
2. Find AI Tweaker / OC / Overclocking section.
3. Set everything to Auto or load Optimized Defaults (usually F5 or F9).
4. Disable any XMP/EXPO memory profiles temporarily to test stability.

Step 7: Perform a Clean Boot

Third-party software (VPN clients, antivirus, virtualization tools) can install kernel drivers that conflict with Windows:

1. Press Win + R → type msconfig → Enter.
2. On the Services tab, check Hide all Microsoft services → click Disable all.
3. On the Startup tab → click Open Task Manager → disable all startup items.
4. Restart. If the BSOD stops, re-enable services in batches to pinpoint the culprit.

Step 8: Last Resort — System Restore or Windows Reset

System Restore:

• Win + R → rstrui.exe → choose a restore point from before the crashes began.

In-Place Upgrade (keeps files and apps):

• Download the Windows 11/10 ISO from Microsoft, mount it, and run setup.exe.
• Choose Keep personal files and apps. This reinstalls Windows core files without wiping your data.

Full Reset:

• Settings → System → Recovery → Reset this PC.
• Only choose Remove everything as a last resort.