🚀 NEW in v2.4.29: 35+ Speed Optimizations added today!Download Now →

Home/Fix/IRQL_NOT_LESS_OR_EQUAL Blue Screen

How to Fix the IRQL_NOT_LESS_OR_EQUAL Blue Screen

IRQL_NOT_LESS_OR_EQUAL means a driver tried to access memory at the wrong privilege level and Windows halted to stay safe. The good news: it is overwhelmingly a driver fault, and there are tools (Driver Verifier, the crash dump) that name the culprit instead of leaving you guessing.

Run the Stability FixSee What RescuePC Checks
  • ✓Identifies the offending driver via the crash dump and Driver Verifier
  • ✓Rolls back or reinstalls the network/GPU/USB drivers that most often cause 0x0A
  • ✓Tests RAM to rule out the secondary hardware cause

Best for 0x0000000A / 0x000000D1 crashes after a driver or hardware change, on wake from sleep, or during network/GPU activity.

📖

Main Troubleshooting Guide

How to Fix Blue Screen of Death (BSOD) →

Complete symptoms, causes, and step-by-step solutions

Symptoms

You might be experiencing this problem if you notice:

  • •Blue screen reading "IRQL_NOT_LESS_OR_EQUAL"
  • •Stop code 0x0000000A, or 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
  • •Crashes began after installing new hardware or a driver
  • •BSOD when waking from sleep or hibernation
  • •Crashes during network activity or under graphics load
  • •Random crashes during normal use with no clear pattern
  • •A specific device name or .sys file appears on the BSOD
  • •Crashes after a Windows feature update replaced drivers

If the blue screen shows a "what failed: xxx.sys" filename, that points directly at the driver — note it. The DRIVER_ variant (0xD1) is even more explicitly a driver fault. No filename? Driver Verifier will force one to appear.

What RescuePC checks for IRQL crashes

RescuePC focuses on the driver-first nature of this stop code: reading the crash dump, reviewing recent driver changes, and testing memory to rule out the hardware runner-up.

  • →Reads the minidump to surface the faulting .sys driver where one is recorded
  • →Reviews recently updated/installed drivers as rollback candidates
  • →Updates the network, GPU, and USB drivers most associated with 0x0A/0xD1
  • →Runs a memory test to rule out faulty RAM
  • →Repairs corrupted system files that can also trigger the stop code

This is most useful when the BSOD does not name a driver and you need Driver Verifier + dump analysis to find the culprit safely.

When These Fixes Resolve It

  • ✓The BSOD names a .sys file or began after a driver/hardware change
  • ✓Rolling back or reinstalling a driver stops the crashes
  • ✓Driver Verifier identifies a faulty third-party driver
  • ✓Disabling an XMP/overclock profile stabilizes the system

These target the driver-first nature of 0x0A/0xD1 — dump analysis, rollback, Verifier, and overclock cleanup — plus memory testing for the hardware runner-up.

When It's Failing Hardware

A minority of IRQL crashes are hardware:

  • ⚠A memory test reports errors that persist after reseating
  • ⚠Crashes continue after a clean Windows install with no third-party drivers
  • ⚠The crash follows a specific failing device regardless of driver version
If memory testing fails or crashes survive a clean install, replace the faulty RAM (or the failing device). Driver fixes cannot compensate for bad hardware.

Common Causes

  • ⚠An incompatible, buggy, or corrupted device driver (the dominant cause)
  • ⚠A driver replaced by a Windows feature update with an incompatible version
  • ⚠Faulty or failing RAM
  • ⚠An unstable memory/CPU overclock (including XMP/EXPO)
  • ⚠Corrupted Windows system files
  • ⚠Aggressive antivirus or VPN drivers hooking the kernel
  • ⚠A newly installed device whose driver conflicts with existing ones
  • ⚠A failing storage driver/controller

Solutions

Solution 1: Read the Crash Dump to Name the Driver

  1. 1If the BSOD shows "what failed: xxx.sys", write that filename down — it is your culprit
  2. 2Install a dump reader (WhoCrashed or BlueScreenView)
  3. 3Open the most recent dump in C:\Windows\Minidump
  4. 4Note the driver/module flagged in the bugcheck
  5. 5Map the .sys name to its device/app (a quick web search of the filename works) and update or remove it

Solution 2: Roll Back or Reinstall the Suspect Driver

  1. 1Boot into Safe Mode if the system is unstable (hold Shift while clicking Restart > Troubleshoot > Advanced options > Startup Settings)
  2. 2Open Device Manager and check Network adapters, Display adapters, and USB controllers first (the usual offenders)
  3. 3For a device that recently updated: right-click > Properties > Driver tab > Roll Back Driver
  4. 4Otherwise update the driver (prefer the vendor's site over Windows Update), or uninstall and reinstall it cleanly
  5. 5Restart and watch for the crash

Solution 3: Run Driver Verifier to Force the Culprit Out

  1. 1Create a System Restore point first (Driver Verifier can cause boot loops if a bad driver is present — that is the point)
  2. 2Open Command Prompt as Administrator and run: verifier /standard /all
  3. 3Restart; if a bad driver exists it will BSOD and record the offending .sys in the dump
  4. 4Boot into Safe Mode and run: verifier /reset to turn Verifier off
  5. 5Read the new dump (step 1) to identify and fix the named driver

Solution 4: Test RAM and Clear Overclocks

  1. 1Press Windows + R, type mdsched.exe and run the memory test (use the Extended option, F1, for thoroughness)
  2. 2For a deeper test, run MemTest86 from USB for several passes
  3. 3If you enabled XMP/EXPO or overclocked, disable it in BIOS and run at default speeds
  4. 4If memory errors appear, reseat the sticks and test one at a time, replacing any faulty stick
  5. 5Re-test under load

Solution 5: Repair System Files

  1. 1Open Command Prompt as Administrator
  2. 2Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. 3Run: sfc /scannow and restart
  4. 4If crashes only began after a feature update, consider rolling that update back
  5. 5Monitor for further BSODs

Fix IRQL_NOT_LESS_OR_EQUAL — the exact commands

IRQL_NOT_LESS_OR_EQUAL (0xA) is a kernel-mode driver touching memory it should not — almost always a driver bug, sometimes RAM. The crash record usually names the driver.

wevtutil qe System /c:3 /rd:true /f:text /q:"*[System[(EventID=1001)]]"

Prints the last BugCheck records — the parameters + named module identify the faulting driver.

pnputil /enum-devices /problem

Lists devices with driver problems — cross-reference against the crash record.

mdsched.exe

Tests RAM — bad memory produces random 0xA crashes that no driver update fixes.

sfc /scannow

Repairs corrupted system files including in-box drivers.

devmgmt.msc

Device Manager: update or roll back the named driver (network and GPU drivers are the usual 0xA offenders).

Minidumps in C:\Windows\Minidump name the exact driver at fault. RescuePC reads them and maps the named module to the vendor driver that needs updating or rolling back.

What Triggered the IRQL Crash?

BSOD names a .sys file (e.g. on the DRIVER_ 0xD1 variant)

Likely cause: That specific driver — update, roll back, or remove it

Read the guide →Run automated fix →

Started after installing hardware or a driver

Likely cause: The new/updated driver is incompatible

Read the guide →

No driver named, random crashes

Likely cause: Unknown driver (use Driver Verifier) or faulty RAM

Read the guide →

Memory test reports errors

Likely cause: Failing RAM — reseat/replace

Read the guide →
FIXES THIS IN 5 MINUTES

Fix IRQL_NOT_LESS_OR_EQUAL Blue Screen Automatically

RescuePC Toolkit includes 109+ automated repairs that fix this problem with one click. No command line knowledge required.

Download Now - Free Trial

No credit card required • Works on Windows 10 & 11

Name the Driver, End the Crash

IRQL crashes feel random but they almost always have a named cause — the tools just have to surface it.

  • →BSOD names a .sys = fix that driver
  • →No name = Driver Verifier forces one out
  • →After an update = roll the driver back
  • →Memory test fails = it's the RAM

Related Error Codes

0x000000D1DRIVER_IRQL_NOT_LESS_OR_EQUAL0x0000000AIRQL_NOT_LESS_OR_EQUAL

Browse More Crashes & Blue Screens Guides

💥Windows Crashes & Blue Screens

Fix Blue Screens, Freezes, and System Crashes — 183 guides, 2 repairs

IRQL_NOT_LESS_OR_EQUAL — FAQ

What does IRQL_NOT_LESS_OR_EQUAL mean?▼
A kernel-mode driver tried to access a memory address at an incorrect IRQL (interrupt request level) — essentially touching memory it had no right to — so Windows halts to prevent corruption. In plain terms: a driver misbehaved. That is why the fix is almost always identifying and replacing the offending driver.
How do I find which driver is causing it?▼
Three ways: (1) the BSOD itself often shows "what failed: xxx.sys"; (2) open the minidump in WhoCrashed/BlueScreenView to see the flagged module; (3) run Driver Verifier (verifier /standard /all), which deliberately crashes on the bad driver and records its name. Then update, roll back, or remove that driver.
What is the difference between 0x0A and 0x0D1?▼
0x0000000A is the general IRQL_NOT_LESS_OR_EQUAL; 0x000000D1 is DRIVER_IRQL_NOT_LESS_OR_EQUAL, which specifically blames a driver and usually names the .sys file. Both are fixed the same way — find and fix the responsible driver — but 0xD1 hands you the culprit more directly.
Is Driver Verifier safe to run?▼
Yes, but create a System Restore point first, because Verifier intentionally crashes the system when it catches a bad driver (that is how it identifies it). If it causes a boot loop, boot into Safe Mode and run "verifier /reset" to turn it off. Used carefully, it is the most reliable way to name an elusive driver.
Could bad RAM cause IRQL_NOT_LESS_OR_EQUAL?▼
Yes — it is the second most common cause after drivers. If driver fixes don't help, run Windows Memory Diagnostic or MemTest86. Disable any XMP/overclock first, since unstable memory speeds produce the same symptom. Reported errors mean reseat or replace the RAM.
Share this:XRedditLinkedInEmail