IRQL_NOT_LESS_OR_EQUAL – How to Fix
The IRQL_NOT_LESS_OR_EQUAL error is a common Windows Blue Screen of Death (BSOD). It occurs when a driver or system process tries to access a memory address at an interrupt request level (IRQL) that it isn’t allowed to. In plain terms, a driver reached into memory it shouldn’t have, causing the system to crash. While alarming, this error is almost always caused by driver conflicts, faulty RAM, or unstable system settings, and it is fixable with systematic troubleshooting.
Have a different error code? Figure out how to fix it with our free Windows error code decoder.
Causes
The most frequent causes of this BSOD include:
- Outdated, corrupted, or incompatible drivers (network, GPU, or storage drivers especially)
- Faulty or unstable RAM modules
- Overclocked or unstable CPU/RAM settings in BIOS
- Recently installed hardware or software that conflicts with the system
- System file corruption or improper driver updates
Fixes
Update or roll back drivers
Drivers are the leading cause of this BSOD. If you recently updated a driver and the crashes started, roll it back to the previous version. If drivers are outdated, update them to the latest manufacturer release:
- GPU drivers: NVIDIA/AMD/Intel support sites
- Network and storage drivers: motherboard or system vendor support pages
- Chipset drivers: system manufacturer or CPU vendor
Device Manager can also be used for quick rollbacks if a recent update caused instability.
Run Memory Diagnostic or MemTest
Since faulty RAM is another frequent trigger, test system memory:
- Press Win + R, type
mdsched.exe, and restart to run Windows Memory Diagnostic. - For deeper testing, use MemTest86 from a bootable USB.
- If errors appear, test each RAM stick individually. Replace faulty modules if necessary.
Remove overclocks and reset BIOS defaults
Overclocked CPU or RAM settings can destabilize Windows. Enter BIOS/UEFI and load default settings. Disable XMP/EXPO memory profiles temporarily to test whether overclocked RAM is the culprit. If the system stabilizes, you may need to fine-tune or abandon the overclock.
Check minidump files
Windows creates crash dump files that help identify the faulty driver. Use tools like BlueScreenView or WinDbg to inspect the minidumps. Look for recurring driver files (e.g., ntoskrnl.exe, nvlddmkm.sys, or tcpip.sys). Updating or replacing the faulty driver usually resolves the crash.
Run SFC and DISM
Corrupted system files can worsen BSOD issues. Repair them using:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
This restores a healthy Windows image and ensures system files are intact.
Additional checks
- Check hardware: Reseat RAM sticks and expansion cards. Poor physical connections can cause memory errors.
- Remove external hardware: Disconnect recently added USB devices or peripherals to test for compatibility conflicts.
- Perform a clean boot: Disable non-essential startup programs and services to see if third-party software is involved.
Conclusion
The IRQL_NOT_LESS_OR_EQUAL BSOD typically points to drivers or RAM trying to access memory they shouldn’t. By updating or rolling back drivers, testing memory, and restoring stable system settings, the error can often be eliminated without a full reinstall. For persistent cases, analyzing crash dumps helps pinpoint the exact driver at fault. With careful troubleshooting, users can restore stability and avoid repeated blue screens.
Have a different error code? Figure out how to fix it with our free Windows error code decoder.