Windows & BSOD · critical

How to fix IRQL_NOT_LESS_OR_EQUAL0x0000000A

Windows & BSOD troubleshooting guide

What this error means

Windows stopped because a driver or Windows itself accessed memory at an invalid address while running at a raised priority level (IRQL). The cause is typically a bad memory pointer in a driver. Microsoft notes that it usually appears after installing a faulty driver, system service or BIOS, and that during a Windows upgrade it can be caused by antivirus or backup software. Faulty hardware, including RAM, can produce it too.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Beginner to intermediate
Before changes
Low for steps 1–6; Driver Verifier in step 7 can cause extra crashes until it is turned off

Reviewed by Matyáš Rada · Documentation checked: 2026-10-30 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Photograph the blue screen. If the PC crashes repeatedly, use Safe Mode for the steps below. If a driver file is named, you may also have DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1), which has its own guide on this site. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Note the file named and when the crash happens

The driver name and the situation (gaming, downloading, waking from sleep, a Windows upgrade) narrow the cause down quickly.

  1. Check the blue screen photo for "What failed: name.sys" and search that name to find its device.
  2. Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and look at errors from the same time as the crash.
  3. Write down what you were doing when it happened.
What to expect

You know the likely driver or at least the situation.

If it does not help

If it only happens while installing a Windows upgrade, start with step 2.

Browse related errors
02Undo the most recent change

Microsoft notes this stop code usually follows the installation of a faulty driver, system service or BIOS.

  1. Roll back a recently updated driver: Device Manager > device Properties > Driver > Roll Back Driver.
  2. Temporarily uninstall third-party antivirus, VPN and backup software in Settings > Apps > Installed apps, and test again.
  3. If you added hardware recently, remove it and test again.
  4. For crashes during a Windows upgrade: uninstall third-party antivirus, disconnect non-essential USB devices and update drivers before trying the upgrade again.

Microsoft Defender turns on automatically when you remove another antivirus program; leave it on.

What to expect

The crash stops after the change is undone.

If it does not help

If a program was responsible, check its maker's site for a version that supports your Windows version.

Browse related errors
03Update drivers and the BIOS

Newer drivers fix memory access bugs; network and Wi-Fi drivers are frequent causes of this code.

  1. Install the latest network, Wi-Fi, Bluetooth, chipset, storage and audio drivers from your PC, laptop or motherboard maker for your exact model.
  2. Install the current graphics driver from NVIDIA, AMD or Intel.
  3. Install the latest BIOS/UEFI from the maker's support page.

Do not switch off the PC during a BIOS update. Avoid third-party driver updater programs.

What to expect

The PC runs without crashing.

If it does not help

If the crash began right after a BIOS update, check the maker's page for a newer fixed version.

Browse related errors
04Remove overclocks and check temperatures

Unstable memory or CPU settings produce random invalid addresses that look like driver bugs.

  1. In the BIOS, turn off XMP or EXPO memory profiles and any CPU or GPU overclock, or load the default settings.
  2. Uninstall overclocking tools that apply settings at startup.
  3. Check CPU and GPU temperatures under load with a monitoring tool and clean dust from fans and heatsinks if they run very hot.
What to expect

The PC runs at stock settings without crashing.

If it does not help

If the crashes stop, re-enable the memory profile later and test; if they return, the profile is not stable on your system.

Browse related errors
05Test the memory and the hardware

Microsoft recommends hardware diagnostics, and faulty RAM is a common cause of memory address errors.

  1. Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
  2. Find the result in Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.
  3. Run the hardware diagnostics from your PC or laptop maker, often available from a key at startup.
What to expect

Memory and hardware tests pass.

If it does not help

If the memory test reports errors, follow the memory test errors guide on this site.

Browse related errors
06Repair Windows system files

If crashes continue with stock settings and current drivers, damaged Windows files are the next suspect.

  1. Open Terminal (Admin).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth.
  3. Run sfc /scannow, then restart.
What to expect

SFC reports no integrity violations, or that it repaired them.

If it does not help

If the crash continues, use step 7 to identify the driver.

Browse related errors
07Find the driver with Driver Verifier

Microsoft recommends Driver Verifier to catch the driver that accesses invalid memory.

  1. Create a restore point (search "Create a restore point").
  2. Open Command Prompt (Admin), type verifier, choose Create standard settings > Select driver names from a list, and tick only non-Microsoft drivers.
  3. Restart and use the PC until it crashes; the blue screen then names the driver.
  4. Turn Driver Verifier off with verifier /reset and restart.

Driver Verifier deliberately causes crashes when it finds a problem. Turn it off when you are done.

What to expect

A specific driver is named, which you can update or remove.

If it does not help

If Windows does not start with Driver Verifier on, start in Safe Mode and run verifier /reset.

Browse related errors

Possible causes

  • A faulty or outdated device driver, often network, Wi-Fi, graphics or storage
  • A recently installed driver, system service or BIOS update
  • Antivirus, VPN or backup software, especially during a Windows upgrade
  • Faulty, newly added or overclocked hardware, including RAM
  • Overheating or unstable overclocks

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc
devmgmt.msc
mdsched.exe

Sources & further reading