Skip to content
PCDecoder
0x0000000AIRQL_NOT_LESS_OR_EQUALStop codeWidely reported

IRQL_NOT_LESS_OR_EQUAL (0xA): what it means and how to fix it

By Gaurav Rawat · Updated Oct 2, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

IRQL_NOT_LESS_OR_EQUAL means a driver tried to use memory it wasn't allowed to touch at that moment, usually because of a driver bug or faulty RAM. Update or roll back recently changed drivers, then test your memory.

What it means

Windows runs code at different priority levels, called IRQLs. At high priority, code isn't allowed to touch memory that might be swapped out to disk. Bug check 0xA means something running at high priority, almost always a driver, tried to access memory it shouldn't have, or an address that wasn't valid at all.

In practice this points to one of two things: a driver with a bug, or memory that's returning wrong values, so a perfectly good driver reads a bad address. Network, graphics and antivirus drivers are frequent offenders, and so are unstable memory settings.

Clues on the blue screen

If the screen shows What failed with a file name ending in .sys, search for that name to see which driver it belongs to. That's your first suspect.

Common causes

  • A buggy or outdated driver, often network, graphics or third-party antivirus.
  • A driver installed or updated just before the crashes began.
  • Faulty RAM, or an unstable XMP/EXPO memory profile.
  • Overclocking.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Update or roll back the likely driver

    First step, especially if the blue screen named a .sys file.

    1. Note the .sys file name if the blue screen showed one, and search for it to find which device it belongs to.
    2. Update that device's driver from the manufacturer's site, or roll it back in Device Manager > Properties > Driver > Roll Back Driver if the crashes began after an update.
    3. If no file was named, update your network and graphics drivers first.
    Did this fix it?

  2. Test your RAM

    If the crashes are random, or this stop code alternates with other memory-related ones.

    1. Save your work, press Win + R, type mdsched.exe and press Enter.
    2. Choose Restart now and check for problems, and let the test run to the end.
    3. When Windows starts, check the result notification, or Event Viewer > Windows Logs > System, filtered for MemoryDiagnostics-Results.
    4. Any errors mean a memory problem. Reseat the sticks, test them one at a time, and replace any that fail.
    Did this fix it?

  3. Undo overclocks and memory profiles

    If you've enabled XMP/EXPO, overclocked or undervolted anything, or the crashes happen under load.

    1. Restart into your BIOS/UEFI setup (usually Delete or F2 as the PC starts).
    2. Load optimised defaults, or turn off XMP/EXPO and any CPU or GPU overclock or undervolt.
    3. Close or uninstall GPU tuning tools that apply settings at startup.
    4. Use the PC for a few days on stock settings to see if the crashes stop.
    Did this fix it?

  4. Remove third-party security software

    If you run an antivirus or VPN alongside Microsoft Defender.

    1. Uninstall the third-party antivirus or VPN from Settings > Apps > Installed apps, using the maker's removal tool if they provide one.
    2. Restart. Microsoft Defender turns on automatically.
    3. If the crashes stop, reinstall the latest version only if you need it.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What causes IRQL_NOT_LESS_OR_EQUAL?

Usually a driver accessing memory at the wrong time, or faulty RAM making a driver read a bad address.

Is IRQL_NOT_LESS_OR_EQUAL a RAM problem?

It can be. Run Windows Memory Diagnostic, and turn off XMP or EXPO if you use it, to rule memory out.

How is it different from DRIVER_IRQL_NOT_LESS_OR_EQUAL?

They describe the same kind of fault. The DRIVER_ version (0xD1) is raised when Windows can tell a driver made the bad access.

Written by

Gaurav Rawat

Gaurav Rawat is a full-stack developer from Jaipur with a B.Tech in Information Technology. At PC Decoder, he writes practical guides on Windows 11 updates, error codes, and fixes for apps that stop working after an update, with an emphasis on clear steps that actually solve the problem.

More from Gaurav Rawat

More stop codes decoded