# Windows IRQL_NOT_LESS_OR_EQUAL: Windows Blue Screen Stop Code IRQL_NOT_LESS_OR_EQUAL (0x0000000A)

> **Quick Answer:** 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).

- **URL:** https://faultcodes.org/software/windows-irql-not-less-or-equal
- **Category:** Windows, Gaming & Tech
- **Brand / Standard:** Windows
- **System Area:** Kernel Drivers & Memory
- **Severity:** Critical — Stop Immediately
- **Safe to Operate?:** No — Risk of Damage
- **DIY Difficulty:** Moderate (Intermediate)
- **Updated:** 2026-11-22T00:00:00Z

## 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.

## Technical Thresholds & Specifications
| Parameter / Condition | Factory Spec / Threshold | Note |
| --- | --- | --- |
| Microsoft Learn Bug Check Code | 0x0000000A (Bug Check 0xA) | Indicates invalid/pageable memory touch at raised IRQL |
| Kernel Interrupt Threshold | IRQL >= DISPATCH_LEVEL (Level 2+) | Page faults cannot be serviced safely at or above DISPATCH_LEVEL |
| Crash Dump Triage Path | C:\Windows\Minidump (`!analyze -v` in WinDbg) | Parameter 1 = bad address; Parameter 2 = IRQL level; Parameter 4 = caller instruction |
| Built-In Hardware & Driver Checks | `mdsched.exe` + Windows Optional Driver Updates | Recommended directly by Microsoft Support for BSOD 0xA |

## 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

## Common Symptoms
- Blue Screen crash displaying `IRQL_NOT_LESS_OR_EQUAL`, sometimes naming `ntoskrnl.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\Minidump` pointing 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 `.sys` drivers

## Tools & Parts Reference
- Windows Memory Diagnostic (`mdsched.exe`) or MemTest86
- Microsoft WinDbg (to analyze `C:\Windows\Minidump` via `!analyze -v`)
- Display Driver Uninstaller (DDU) & Admin Command Prompt (`sfc /scannow`)

## Step-by-Step Troubleshooting & Fix
1. Clean-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.
2. Update or temporarily uninstall kernel anti-cheat clients (Riot Vanguard, Easy Anti-Cheat, BattlEye) or legacy RGB/fan tools if named in minidumps.
3. Reset 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.
4. Run `DISM /Online /Cleanup-Image /RestoreHealth` + `sfc /scannow` in Admin Terminal and check motherboard vendor updates for BIOS microcode fixes.

## Estimated Repair Cost Benchmark
| Currency | DIY Parts Only | Professional Repair (Parts + Labor) |
| --- | --- | --- |
| USD | $0–$85 | $85–$190 |
| GBP | £0–£70 | £65–£150 |
| CAD | CA$0–CA$115 | CA$115–CA$250 |
| EUR | €0–€80 | €75–€175 |
| CHF | CHF 0–CHF 95 | CHF 110–CHF 230 |

## 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.


## Verified Official & Engineering References
- [Microsoft Learn: Bug Check 0xA (IRQL_NOT_LESS_OR_EQUAL)](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa--irql-not-less-or-equal) (Official Support)
- [Microsoft Support: Resolving Blue Screen Errors in Windows](https://support.microsoft.com/en-us/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6) (Technical Manual)
