Windows Blue Screen Stop Code IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
Bug Check 0xA: Windows or a kernel-mode driver attempted to access pageable or invalid memory at a raised Interrupt Request Level (IRQL >= DISPATCH_LEVEL)—commonly traced to faulty drivers, corrupted pointers, RAM instability, or CPU undervolts.
Stop code IRQL_NOT_LESS_OR_EQUAL (Bug Check `0x0000000A`) occurs when Windows or a kernel-mode .sys driver tries to touch pageable or invalid memory while operating at a raised Interrupt Request Level (IRQL). Save work promptly because sudden BSOD reboots risk NTFS file corruption. Per Microsoft Learn and Windows Support guidance, inspect C:\Windows\Minidump (!analyze -v in WinDbg) to isolate the offending .sys driver, update/clean-install chipset, GPU, network, or anti-cheat drivers (Settings -> Windows Update -> Optional updates), run Windows Memory Diagnostic (`mdsched.exe`), and reset aggressive BIOS RAM XMP/EXPO or CPU undervolts ($0 DIY software/BIOS fix; $85–$190 PC shop).
- Safe to Operate?
- No — Risk of Damage
- DIY Difficulty
- Moderate (Intermediate)
- System
- Kernel Drivers & Memory
- Professional Repair
- $85 – $190
What This Fault Code Means
Microsoft's kernel assigns Interrupt Request Levels (IRQLs) to prioritize hardware execution; code executing at DISPATCH_LEVEL (2) or above cannot safely handle page faults from paged memory. When a buggy device driver dereferences a null/invalid pointer, touches paged pool at raised IRQL, or unstable RAM/CPU voltage flips an address bit, Bug Check 0x0000000A triggers immediately.
Common Symptoms
- Blue Screen crash displaying
IRQL_NOT_LESS_OR_EQUAL, sometimes namingntoskrnl.exe, GPU (nvlddmkm.sys), Wi-Fi, or anti-cheat drivers - Reboots concentrated during multiplayer game launches, GPU/network spikes, or right after driver updates
- Dumps written to
C:\Windows\Minidumppointing to bad pointer dereferences (0x0000000A)
Most Likely Root Causes
- Faulty or outdated kernel device driver (GPU, Realtek/Intel LAN/Wi-Fi, audio, chipset, or kernel anti-cheat such as Vanguard/EAC)
- Unstable CPU undervolt / PBO Curve Optimizer offset or motherboard overclock corrupting kernel addresses
- Unstable DDR4/DDR5 XMP/EXPO overclock or physically defective RAM stick failing under load
- Corrupted Windows kernel files or legacy hardware RGB/fan utilities loading incompatible
.sysdrivers
Technical Thresholds & Specifications
| Parameter / Condition | Factory Spec / Threshold |
|---|---|
| Microsoft Learn Bug Check Code Indicates invalid/pageable memory touch at raised IRQL | 0x0000000A (Bug Check 0xA) |
| Kernel Interrupt Threshold Page faults cannot be serviced safely at or above DISPATCH_LEVEL | IRQL >= DISPATCH_LEVEL (Level 2+) |
| Crash Dump Triage Path Parameter 1 = bad address; Parameter 2 = IRQL level; Parameter 4 = caller instruction | C:\Windows\Minidump (`!analyze -v` in WinDbg) |
| Built-In Hardware & Driver Checks Recommended directly by Microsoft Support for BSOD 0xA | `mdsched.exe` + Windows Optional Driver Updates |
Commonly Affected Models & Service Bulletins
- Windows 10 & Windows 11 Desktops/Laptops after buggy GPU, chipset, or network driver updates
- Gaming PCs running kernel-level anti-cheat drivers (Vanguard, EAC, BattlEye)
- Systems running aggressive DDR4/DDR5 XMP/EXPO overclocks or PBO Curve Optimizer CPU undervolts
Diagnostic Checks Before Replacing Parts
Verify the exact faulty component before ordering replacements.
- 1Inspect crash dumps in
C:\Windows\Minidumpwith Microsoft WinDbg (!analyze -v) to read the exact faultingMODULE_NAMEand Bug Check0xAparameters (Parameter 1= memory address referenced,Parameter 2= IRQL level). - 2Boot into Safe Mode with Networking: if Blue Screens disappear completely in Safe Mode, a third-party kernel driver or startup utility is confirmed.
- 3Run Windows Memory Diagnostic (`mdsched.exe`) and check Settings -> Windows Update -> Advanced options -> Optional updates for pending driver fixes.
Interactive Symptom Triage
Answer 3 quick checks to narrow down the faulty component before spending money on parts.
Does WinDbg (!analyze -v) or the crash screen name a specific third-party .sys driver (e.g., GPU, Wi-Fi, or anti-cheat)?
Step-by-Step Troubleshooting & Fix
Tools & Parts Reference
mdsched.exe) or MemTest86Microsoft WinDbg (to analyze C:\Windows\Minidump via !analyze -v)Display Driver Uninstaller (DDU) & Admin Command Prompt (sfc /scannow)- 1Clean-uninstall GPU drivers in Safe Mode using Display Driver Uninstaller (DDU) and install the latest WHQL release alongside official motherboard chipset, Wi-Fi/LAN, and Optional Windows driver updates.
- 2Update or temporarily uninstall kernel anti-cheat clients (Riot Vanguard, Easy Anti-Cheat, BattlEye) or legacy RGB/fan tools if named in minidumps.
- 3Reset BIOS CPU Curve Optimizer / undervolt and DDR4/DDR5 XMP/EXPO memory profiles to stock defaults to rule out silicon/RAM timing corruption, and run
mdsched.exe/ MemTest86. - 4Run
DISM /Online /Cleanup-Image /RestoreHealth+sfc /scannowin Admin Terminal and check motherboard vendor updates for BIOS microcode fixes.
Estimated Repair Cost Benchmark
Typical DIY parts and certified technician labor ranges. Select a currency below.
| Repair Path | USD |
|---|---|
| DIY Parts Only | $0 – $85 |
| Professional Repair (Parts + Labor) | $85 – $190 |
Recommended Diagnostic Tools & Replacement Parts
Check OEM specifications and compatible tools for this repair.
Frequently Asked Questions
Why does WinDbg or the BSOD blame ntoskrnl.exe on IRQL_NOT_LESS_OR_EQUAL?
ntoskrnl.exe is the core Windows kernel—it shows up on the stack whenever another driver passes an invalid pointer into kernel functions or when unstable RAM/CPU voltage flips kernel instructions (Bug Check 0xA).
What do the four parameters of Bug Check 0xA mean?
Per Microsoft Learn, Parameter 1 is the invalid memory address referenced, Parameter 2 is the raised IRQL level (>= 2), Parameter 3 indicates read (0) vs write (1) access, and Parameter 4 points to the instruction address attempting access.
Related Searches & Questions
Verified Official & Engineering References
Related Fault Codes
Tech & OS →Windows Error Code 0x80070005 (E_ACCESSDENIED)
Windows Update, Microsoft Store, OneDrive folder backup, activation, or an installer hit `E_ACCESSDENIED`—blocking access to required system files, registry hives, or DCOM permissions (`SELF`).
Windows Blue Screen Stop Code MEMORY_MANAGEMENT (0x0000001A)
Windows Update Error 0x80070643 (ERROR_INSTALL_FAILURE / KB5034441)
Windows CRITICAL_PROCESS_DIED (0x000000EF): Critical OS Process Terminated
Windows Update Error 0x800f0922: Full System/EFI Partition or CBS Failure