Windows Error 0x0000000A — IRQL NOT LESS OR EQUAL
About Windows Error 0x0000000A
Windows BSOD IRQL_NOT_LESS_OR_EQUAL (0x0000000A) occurs when a driver or kernel process accesses invalid memory at too high an IRQL. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: Stop code: 0x0000000A — one of the most common BSODs. Often caused by faulty drivers or incompatible hardware. Can appear during startup, shutdown, or normal use. Memory corruption or race conditions trigger this error. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Incompatible or outdated device drivers. Faulty RAM modules. Overclocked hardware causing memory instability. Corrupted Windows system files. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Boot into Safe Mode and uninstall recently added drivers. Run Windows Memory Diagnostic (mdsched.exe). Update all device drivers from manufacturer websites. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
What causes IRQL_NOT_LESS_OR_EQUAL?
Usually a driver trying to access memory it should not, often due to outdated or incompatible drivers.
Overview
Windows BSOD IRQL_NOT_LESS_OR_EQUAL (0x0000000A) occurs when a driver or kernel process accesses invalid memory at too high an IRQL.
Key Details
- Stop code: 0x0000000A — one of the most common BSODs
- Often caused by faulty drivers or incompatible hardware
- Can appear during startup, shutdown, or normal use
- Memory corruption or race conditions trigger this error
Common Causes
- Incompatible or outdated device drivers
- Faulty RAM modules
- Overclocked hardware causing memory instability
- Corrupted Windows system files
Steps
- 1Boot into Safe Mode and uninstall recently added drivers
- 2Run Windows Memory Diagnostic (mdsched.exe)
- 3Update all device drivers from manufacturer websites
- 4Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth