0x0000000A

Fix IRQL_NOT_LESS_OR_EQUAL (0x0000000A) After Driver Update

The IRQL_NOT_LESS_OR_EQUAL BSOD with code 0x0000000A typically occurs after a faulty driver update. This guide explains symptoms, root causes, and step-by-step fixes including safe mode rollback and driver verification.

Symptoms

  • Blue Screen of Death (BSOD) with stop code IRQL_NOT_LESS_OR_EQUAL and error code 0x0000000A.
  • System crashes shortly after booting or during normal operation.
  • Error occurs immediately after installing a new driver update (e.g., graphics, network, or chipset driver).
  • Possible automatic restart loop making it difficult to access Windows normally.

Root Causes

  • Faulty or incompatible driver: The updated driver attempts to access a memory address at an incorrect interrupt request level (IRQL).
  • Corrupted driver files: Incomplete installation or corrupted download leads to instability.
  • Conflicting drivers: New driver conflicts with existing drivers or system services.
  • Memory or hardware issues: Though less common, faulty RAM or hardware can trigger this error, especially after driver changes.

Step-by-Step Fix

1. Boot into Safe Mode

  1. Restart your PC. When the Windows logo appears, press and hold the power button to force shutdown. Repeat 3 times to trigger Automatic Repair.
  2. On the Automatic Repair screen, click Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
  3. After restart, press 4 or F4 to enable Safe Mode.

2. Roll Back the Problematic Driver

  1. In Safe Mode, right-click the Start button and select Device Manager.
  2. Expand the category of the device you updated (e.g., Display adapters, Network adapters).
  3. Right-click the device and select Properties.
  4. Go to the Driver tab and click Roll Back Driver (if available). Follow the prompts.
  5. Restart the PC normally.

3. Use Driver Verifier to Identify the Culprit

  1. If rollback is not available, open Command Prompt as Administrator (in Safe Mode).
  2. Type verifier and press Enter.
  3. Select Create standard settings > Next.
  4. Choose Select driver names from a list.
  5. Click Unsigned drivers and then Add to select all unsigned drivers (or manually select suspect drivers).
  6. Click Finish and restart. If a BSOD occurs, the faulty driver will be identified in the crash log.
  7. To disable Verifier, boot into Safe Mode, run verifier /reset in Command Prompt.

4. Uninstall the Problematic Driver

  1. In Device Manager, right-click the device and select Uninstall device.
  2. Check Delete the driver software for this device if prompted.
  3. Restart. Windows will reinstall a generic driver automatically.

Alternative Fixes

  • System Restore: Use a restore point created before the driver update. Boot into Safe Mode and search for "System Restore" in Control Panel.
  • Use Last Known Good Configuration: During boot, press F8 repeatedly before Windows loads and select Last Known Good Configuration (advanced).
  • Check for Windows Updates: Sometimes Microsoft releases a fix for known driver issues. In Safe Mode, run Windows Update and install all updates.
  • Run Memory Diagnostics: Type mdsched.exe in Run (Win+R) and restart to test RAM. Replace faulty sticks if errors are found.

Prevention

  • Always create a system restore point before installing any driver update.
  • Download drivers only from official manufacturer websites or use Windows Update for critical drivers.
  • Use driver update tools cautiously; prefer manual installation.
  • Keep a backup of the previous driver version by noting the version number before updating.
  • Test new drivers on a non-production machine if possible.
  • Regularly update Windows to ensure system stability and compatibility.

By following these steps, you can resolve the IRQL_NOT_LESS_OR_EQUAL error and prevent future occurrences. If the issue persists, consider hardware diagnostics or contacting the device manufacturer for support.

Related Errors in Windows Errors
0X00000FD6 PEERDIST_ERROR_NOT_INITIALIZED (0X00000FD6) – A Fix That Actually Works 0X000003F5 Reg key write fails: 0X000003F5 fix 0X4000002B STATUS_RESUME_HIBERNATION (0X4000002B) explained 0XC00D1071 NS_E_WMX_ITEM_DOES_NOT_EXIST (0XC00D1071) Fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.