Fixes / Windows · Checked September 30, 2026

Windows IRQL_NOT_LESS_OR_EQUAL stop code: meaning and fixes

Short answer

IRQL_NOT_LESS_OR_EQUAL (bug check 0x0000000A) means Windows or a driver tried to read or write an invalid memory address while running at a high priority level, so Windows stopped to protect your data. Usually a bad or recently updated driver is to blame. The most likely fix is to roll back or update that driver (often graphics, network or antivirus) and install all Windows updates.

What this message means

Windows runs drivers at different priority levels called IRQLs. At high levels, code may only use memory that is guaranteed to be in RAM. IRQL_NOT_LESS_OR_EQUAL (stop code 0xA) appears when Windows or a kernel-mode driver touches a memory address that is invalid, or that may be paged out, while running at such a level. Microsoft says the cause is typically a bad memory pointer in driver code, and that it usually follows installing a faulty driver, system service or BIOS. Faulty or overclocked RAM can produce the same crash because it corrupts memory addresses. The PC restarts, and the crash is logged so you can trace it.

Common causes

Cause	How to tell
A faulty, outdated or newly updated device driver (graphics, Wi-Fi/Ethernet, audio, USB or chipset)	The crash started after a driver or Windows update, the blue screen shows a 'What failed:' line naming a .sys file (for example nvlddmkm.sys, rtwlane.sys, netwtw10.sys), or crashes happen during gaming, video playback or heavy network use.
Third-party antivirus, VPN, backup, RGB/fan control or anti-cheat software that installs kernel drivers	The crash began after installing or updating such a program, happens at startup or when that program starts, and stops when you boot in Safe Mode or do a clean boot.
Bad RAM, loose memory modules, or unstable memory overclocking (XMP/EXPO profiles)	The stop code changes between crashes (IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA), different drivers get blamed each time, crashes happen under load, or Windows Memory Diagnostic reports errors.
Incompatible software or drivers after a Windows feature upgrade	The crash began right after moving to a new Windows version (for example Windows 10 to 11, or a new 24H2/25H2 update), or it appears during the upgrade itself and the upgrade rolls back.
Newly added hardware or an outdated BIOS/firmware	The crash started after adding a card, drive, dock or USB device, or after a BIOS update, and stops when that device is unplugged or the BIOS is updated.
Corrupted Windows system files	Running sfc /scannow reports that it found corrupt files, and other Windows components are also misbehaving.

How to fix it

1. Find the driver that crashed

If the blue screen shows a line starting 'What failed:', write down the .sys file name. Search that name to find which device or program it belongs to (for example nvlddmkm.sys is the NVIDIA graphics driver).
If you missed it, right-click Start, select Event Viewer, then go to Windows Logs > System.
Look for an error with Event ID 1001 (source BugCheck) that says 'The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a', and check the other critical errors logged just before it.
Alternatively, search the Start menu for 'View reliability history' and click the 'Windows' critical event on the day of the crash for details.
Crash dump files are saved in C:\Windows\Minidump. An IT person can open them in WinDbg and run !analyze -v to name the faulting driver.

2. Roll back or update the suspect driver

Right-click Start and select Device Manager.
Expand the category of the suspect device (Display adapters, Network adapters, and so on). Any device with a yellow exclamation mark is also a suspect.
If the crash started after a driver update: right-click the device, select Properties > Driver tab > Roll Back Driver.
If the driver is old: download the latest driver from the PC maker or chip maker (NVIDIA, AMD, Intel, Realtek) rather than relying on 'Update driver'.
For graphics drivers that keep crashing, a clean reinstall (the 'Clean install' option in the NVIDIA or AMD installer) often helps.
Restart and use the PC normally to see if the crash comes back.

3. Install Windows updates, or uninstall the one that started it

Windows 11: Settings > Windows Update. Windows 10: Settings > Update & Security > Windows Update.

Windows 11: select Start > Settings > Windows Update > Check for updates. Windows 10: Start > Settings > Update & Security > Windows Update > Check for updates.
Install everything offered, including optional driver updates under Advanced options > Optional updates (Windows 11) or 'View optional updates' (Windows 10).
If crashes began right after a specific update, go to Update history > Uninstall updates (Windows 11) or View update history > Uninstall updates (Windows 10) and remove the most recent one.
Restart the PC.

4. Test your RAM and turn off memory overclocking

Press Windows key + R, type mdsched.exe and press Enter.
Select 'Restart now and check for problems (recommended)'. Save your work first, the PC restarts and runs the test.
After Windows starts again, open Event Viewer > Windows Logs > System and look for the MemoryDiagnostics-Results entry to see the result.
If you enabled XMP (Intel) or EXPO (AMD) in the BIOS, or overclocked the CPU or GPU, set them back to default and see if the crashes stop.
If errors are found, reseat the memory sticks, then test one stick at a time to find the bad one and replace it.

5. Rule out third-party software with Safe Mode and a clean boot

Windows 11: Settings > System > Recovery. Windows 10: Settings > Update & Security > Recovery.

Open Recovery settings (path above) and next to Advanced startup select Restart now.
Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4 for Safe Mode (5 or F5 for Safe Mode with Networking).
If the PC is stable in Safe Mode, a third-party driver or service is the cause. Uninstall recently added antivirus, VPN, RGB, fan-control or overclocking tools.
To narrow it down in normal mode, search for msconfig, open System Configuration, go to the Services tab, tick 'Hide all Microsoft services', click Disable all, and restart.
Re-enable services a few at a time until the crash returns, then remove or update that program.

6. Repair system files, then use System Restore

Search for cmd, right-click Command Prompt and select Run as administrator.
Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
Run sfc /scannow and restart when it completes.
If crashes continue, search for 'Create a restore point', open it, click System Restore, and pick a restore point from before the crashes started.
Also unplug any hardware added recently and check your PC maker's site for a BIOS/firmware update.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the crash keeps coming back after these steps, run your PC maker's built-in hardware diagnostics (for example Dell SupportAssist, HP PC Hardware Diagnostics, or Lenovo Diagnostics) to test RAM, storage and motherboard. If the crash names a different driver each time, faulty hardware is more likely than software. Advanced users can run Driver Verifier (type verifier in an admin Command Prompt) on third-party drivers to catch the culprit, but it can make the PC crash on startup, so know how to reach Safe Mode first. As a last resort, back up your files and use Settings > System > Recovery > Reset this PC (Windows 11) or Settings > Update & Security > Recovery (Windows 10). If crashes continue on a clean install, the problem is hardware, so contact the PC maker or a repair shop and bring the files from C:\Windows\Minidump.

Questions people ask

Is IRQL_NOT_LESS_OR_EQUAL a hardware or software problem?

Usually software. Microsoft attributes about 70% of stop errors to third-party drivers and about 10% to hardware. If different drivers or different stop codes show up each time, suspect RAM or other hardware instead.

Can bad RAM cause IRQL_NOT_LESS_OR_EQUAL?

Yes. Faulty RAM or an unstable XMP/EXPO memory profile can corrupt memory addresses and trigger this crash. Test with Windows Memory Diagnostic (mdsched.exe) and set memory to default speed in the BIOS to rule it out.

What is the difference between IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL?

Both mean invalid memory was accessed at a raised priority level. DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1) points specifically at a driver, often a network driver, while IRQL_NOT_LESS_OR_EQUAL (0xA) can come from a driver or Windows itself. The fixes are largely the same.

Is IRQL_NOT_LESS_OR_EQUAL dangerous for my PC?

The crash itself does not damage hardware. Windows stops on purpose to prevent data corruption, but you can lose unsaved work, and frequent crashes can point to failing RAM that should be replaced.

Will resetting Windows fix IRQL_NOT_LESS_OR_EQUAL?

It fixes software and driver causes, but not faulty RAM or other hardware. Try rolling back drivers, updating Windows and testing memory first, because a reset takes longer and removes your apps.

Sources

Related errors