Overview
DRIVER_IRQL_NOT_LESS_OR_EQUAL is one of the most common BSOD codes. It means a driver tried to access memory at an interrupt request level (IRQL) it shouldn't have. In plain English: a driver crashed Windows.
The fix is identifying which driver did it. Sometimes Windows tells you (filename in parentheses on the BSOD), sometimes you need to investigate. Network and graphics drivers are the most common offenders.
This guide is structured around finding and fixing the bad driver, with hardware checks as backup.
Before you start
- ✓Try to note the driver filename from the BSOD
- ✓Administrator access
5-step guide
Read time: ~20-45 min
Identify the Failing Driver
Same approach as KMODE_EXCEPTION — check the BSOD filename in parentheses. Most common offenders:
Netwtw0X.sys→ Intel Wi-Fi (X = version)tcpip.sys→ Windows network stacknvlddmkm.sys→ NVIDIA graphicsUSBPORT.SYS→ USB driverfltMgr.sys→ Filter Manager (often hijacked by AV)
If no name shown, check Event Viewer (eventvwr.msc) → System → most recent BugCheck around the crash time.
Update or Reinstall the Driver
Once identified, get the latest driver from the device manufacturer (not Windows Update — manufacturer drivers are usually newer and more stable for power users).
Steps:
- Visit the device manufacturer's support page (Intel, NVIDIA, AMD, Realtek, etc.).
- Download the latest driver for your exact Windows version.
- Uninstall the old driver first: Device Manager → right-click device → Uninstall device → tick "Delete the driver software for this device".
- Restart.
- Run the manufacturer installer.
Disable Fast Startup
Fast Startup keeps Windows in a hibernation-like state, which sometimes corrupts driver state across reboots. Disabling it resolves intermittent driver IRQL crashes.
Steps:
- Press
Windows + R, typepowercfg.cpl, press Enter. - Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Untick Turn on fast startup (recommended).
- Save and restart.
Run System File Checker and DISM
Standard system integrity check.
bashsfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthBoot in Safe Mode and Test
Safe Mode loads only essential Microsoft drivers. If BSODs stop in Safe Mode, you've confirmed the culprit is a third-party driver.
Steps:
- From boot screen, hold Shift while clicking Restart.
- Choose Troubleshoot → Advanced options → Startup Settings → Restart.
- Press 4 for Safe Mode (or 5 for Safe Mode with Networking).
Use the PC for 1-2 hours in Safe Mode. If no BSOD: third-party driver issue. Uninstall recently added software (especially security tools, VPNs, virtual drives) one at a time.
Still seeing DRIVER_IRQL_NOT_LESS_OR_EQUAL?
If the guide is not enough, describe the issue first. We will explain whether remote help is appropriate before any access is granted.
No automatic remote access.
- DIY steps first
- Permission before access
- Hardware limits explained
Common questions
Why is this BSOD so common?
Is it safe to keep using my PC?
I uninstalled the suspect driver but Windows reinstalled it automatically. What now?
Could it be malware?
What if the BSOD doesn't show a filename?
Written by PCDoc Team
Tested on a real Windows machine on 2026-05-20. Found a mistake? Tell us.