A sudden blue screen crash displaying the error code: ‘IRQL_NOT_LESS_OR_EQUAL’ or bug check code 0x0000000A is one of the most infamous Windows kernel stop errors. In Windows operating system architecture, the Interrupt Request Level (IRQL) determines the hardware priority of running code. When a kernel-mode process or device driver attempts to access pageable memory addresses at an IRQL that is too high (an illegal operation), the Memory Manager cannot satisfy the page fault. Because continuing would risk severe data corruption, the Windows kernel halts immediately. In Windows 11, this error is typically caused by incompatible device drivers, unstable RAM timings, or corrupted system files.
What Causes IRQL_NOT_LESS_OR_EQUAL in Windows 11?
Bug check 0x0000000A indicates an illegal memory reference from an elevated interrupt priority. Triggers include:
- Faulty Device Drivers: Outdated network (Wi-Fi/Ethernet), audio, or graphics drivers referencing invalid memory pointers.
- Unstable Physical RAM or Overclocking Profiles: Defective memory sticks, mismatched RAM timings, or unstable XMP/EXPO memory profiles.
- Corrupted Windows Virtual Memory Paging File: Bad sectors or fragmentation within
pagefile.sys. - Conflicting Antivirus Kernel Drivers: Low-level third-party security software improperly intercepting system interrupts.
- Outdated Motherboard BIOS/UEFI Microcode: Voltage instability across CPU cores or memory controllers during power state transitions.
Step 1: Check Driver Attribution in the BSOD Screen
Identify whether a specific driver filename is cited on the blue screen or in memory minidumps.
- Review the crash screen for filenames ending in
.sys(e.g.rtwlane.sysfor Realtek Wi-Fi,nvlddmkm.sysfor NVIDIA, orstorport.sysfor storage). - If no file is displayed, open File Explorer and browse to
C:\Windows\Minidump\. - Analyze the minidump file using BlueScreenView or WinDbg to pinpoint the exact driver module that initiated the illegal memory request.
Step 2: Update or Roll Back Problematic Device Drivers
Once the offending hardware category is identified, updating or rolling back the driver resolves memory pointer faults.
- Press Win + X and open Device Manager.
- Expand the corresponding hardware category (e.g. Network adapters or Display adapters).
- Right-click the device and select Properties > Driver.
- If the error began immediately after a recent update, click Roll Back Driver.
- Otherwise, click Update driver and install the latest WHQL driver directly from the hardware manufacturer.
Step 3: Disable Memory Overclocking (XMP / EXPO)
Aggressive memory profiles can cause memory controller instability and bit-flips under load.
- Restart your computer and press Del or F2 during boot to enter the motherboard UEFI BIOS.
- Navigate to the Overclocking / Memory settings (e.g. Ai Tweaker, OC, or Extreme Tweaker).
- Locate XMP (Extreme Memory Profile), DOCP, or EXPO.
- Set the profile to Disabled or Auto to run your RAM at standard JEDEC frequencies.
- Save changes and reboot into Windows.
Step 4: Test Hardware Memory Using Windows Memory Diagnostic
Physical memory defects are a primary cause of non-paged memory addressing violations.
- Press Win + R, type
mdsched.exe, and press Enter. - Select Restart now and check for problems (recommended).
- Allow the diagnostic passes to complete. If errors are detected, reseat your RAM sticks or replace defective modules.
Step 5: Run DISM and SFC System File Repairs
Repairing corrupted Windows system files restores core kernel dynamic libraries.
- Open Command Prompt (Admin).
- Execute:
DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow - Wait for verification to complete and confirm corrupt files were repaired.
- Restart your computer.
Updating faulting drivers, disabling unstable XMP memory overclocks, and running memory diagnostics eliminates IRQL_NOT_LESS_OR_EQUAL crashes in Windows 11.