How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL on Windows 10/11 (6 Proven Fixes)

Adam LaFoute

May 15, 2026

Getting a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen on Windows? This crash means a driver tried to access memory at a priority level it was not allowed to use at that moment. Windows cannot recover from this on its own, so it forces a full restart.

This error almost always points to a bad or newly updated driver. GPU drivers, network drivers, and chipset drivers are the most common triggers. Antivirus software, VPN clients, and faulty RAM can also cause it. The blue screen often names the exact driver file responsible, such as nvlddmkm.sys for NVIDIA or tcpip.sys for network adapters. That filename is your starting point.

This guide covers the most effective fixes in order from quickest to most thorough. Most people solve it by Fix 2 or Fix 3. If you can see the driver filename on the blue screen, jump straight to Fix 2.

What This Error Means at a Glance

A driver tried to access memory at an interrupt request level that Windows does not allow for that operation.
Most common causes: bad or outdated drivers, antivirus or security software conflicts, newly installed hardware.
Less common causes: faulty RAM, corrupted system files, failed Windows update.
The blue screen often names the driver file directly (e.g. nvlddmkm.sys, tcpip.sys, ntoskrnl.exe). That name tells you where to start.
Affects Windows 10 and Windows 11. Very common after driver updates or new hardware installs.

Error Type

BSOD / Driver Fault

Root Cause

Drivers / RAM / Software

Affects

Windows 10 / 11

Difficulty

Beginner to intermediate

Time to Fix

10 min – several hours

Video: How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL on Windows

Watch the full fix walkthrough for DRIVER_IRQL_NOT_LESS_OR_EQUAL on Windows 10 and 11, covering driver rollback, SFC scan, RAM testing, and antivirus conflict steps shown below.

What Causes DRIVER_IRQL_NOT_LESS_OR_EQUAL?

This error has several possible causes. Knowing which one fits your situation helps you skip straight to the right fix. Check the list below before working through the numbered steps.

Bad or Outdated Drivers (Most Common)

A driver running at the core of Windows triggers this error when it tries to access memory at an interrupt level it is not allowed to use. GPU drivers, network adapter drivers, storage drivers, and chipset drivers are the most frequent offenders. If the crash started after a driver update, rolling it back is usually the fastest fix. If the blue screen named a specific .sys file, that file belongs to the driver you need to address first.

Antivirus or Security Software Conflict

Security tools hook deep into Windows memory and sometimes run operations at priority levels that conflict with system rules. Antivirus programs, VPN clients, and firewall tools are common triggers, especially after a software update that changed how they interact with the kernel. If the error started after installing or updating security software, that is the first thing to disable or remove.

New Hardware Install

Adding new hardware installs new drivers, and those drivers may have compatibility issues with your current Windows version or other drivers already on the system. A network card, GPU, USB hub, or storage adapter added recently is worth investigating if the error started immediately after the install.

Faulty or Improperly Seated RAM

Bad memory can cause drivers to read incorrect data from RAM, which produces this exact crash. RAM problems tend to create random crashes with no predictable trigger. If crashes happen at unpredictable times and other fixes have not helped, testing your RAM is the next step. Loose sticks can also cause this, so reseating them is worth trying before running a full memory test.

Corrupted System Files

A bad Windows update, sudden power loss, or forced shutdown can corrupt system files that drivers rely on. When a driver cannot find or read those files correctly, it may attempt memory access at the wrong level and trigger this crash. SFC and DISM can scan and repair these files without reinstalling Windows.

Failed or Interrupted Windows Update

A Windows update that did not finish cleanly can leave drivers or system files in a broken state. If the error appeared immediately after an update, rolling back that update using Windows Update history or System Restore is worth trying before going further through the fix list.

How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Error

Work through these fixes in order. Most people are done by Fix 2 or Fix 3. If you saw a specific .sys filename on the blue screen, start at Fix 2.

Do a Clean Restart and Check for Software Conflicts

Before anything else, rule out a one-time glitch and third-party software conflicts. A full shutdown and clean boot takes five minutes and sometimes resolves the error entirely.

Step 1. Do a full shutdown (not restart): click Start, hold Shift, and click Shut down. Wait 30 seconds, then power on. This clears the fast startup cache that a regular restart leaves in place.
Step 2. If the crash comes back, open System Configuration by pressing Windows key + R, typing msconfig, and pressing Enter.
Step 3. Go to the Services tab. Check Hide all Microsoft services, then click Disable all. Click OK and restart.
Step 4. If crashes stop with third-party services disabled, re-enable them one group at a time to identify the conflict. Once found, uninstall or update that software.

Tip: Antivirus, VPN clients, and firewall tools are the most common third-party triggers for this error. If you installed or updated any security software recently, disable or uninstall it first and see if the crashes stop before doing anything else.

Update or Roll Back the Problem Driver

Drivers are the most common cause of DRIVER_IRQL_NOT_LESS_OR_EQUAL. If the blue screen named a specific file (like nvlddmkm.sys for NVIDIA or tcpip.sys for network), go straight to that driver. If you are not sure which driver is responsible, check Device Manager for anything flagged with a yellow warning icon.

Step 1. Right-click the Start button and select Device Manager.
Step 2. Look for any devices with a yellow warning icon. Right-click them and select Update driver.
Step 3. For GPU drivers specifically, go to the NVIDIA, AMD, or Intel website and download the latest driver for your graphics card directly from the manufacturer rather than through Windows Update.
Step 4. If the error started after a specific driver update, right-click the device in Device Manager, select Properties, open the Driver tab, and click Roll Back Driver.
Step 5. Restart after any driver change and monitor for crashes.

Common .sys filenames and what they belong to: nvlddmkm.sys = NVIDIA GPU driver. atikmdag.sys / amdkmdag.sys = AMD GPU driver. tcpip.sys = Windows network stack (update network adapter drivers). ntoskrnl.exe = Windows kernel (usually points to a faulty third-party driver interacting with it, not the kernel itself). Search the filename + “driver” to find exactly which device or software it belongs to.

Clean GPU driver reinstall: If you suspect a corrupt GPU driver, download DDU (Display Driver Uninstaller) from Wagnardsoft, boot into Safe Mode, run DDU to strip the old driver completely, then restart and install a fresh driver from the manufacturer’s site.

Run SFC and DISM to Repair System Files

Corrupted system files can cause drivers to behave incorrectly and trigger this blue screen. SFC (System File Checker) scans Windows files and replaces damaged ones. DISM repairs the Windows image that SFC draws replacement files from. Run both, in this order.

Step 1. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
Step 2. Type sfc /scannow and press Enter. Wait for it to finish. This takes 10 to 20 minutes. Do not close the window.
Step 3. Once SFC completes, run this DISM command: DISM /Online /Cleanup-Image /RestoreHealth
Step 4. Restart your PC when both scans finish, then monitor for crashes.

If SFC says it cannot repair files: Run the DISM command first to restore the Windows image, then run SFC again. DISM needs an internet connection to download replacement files from Microsoft.

Uninstall a Recent Windows Update or Use System Restore

If the error appeared right after a Windows update, removing that update is often the fastest fix. System Restore takes your PC back to a saved state before the problem started, without affecting your personal files.

Try System Restore first if you have restore points available.

Search for System Restore in the Start menu and open it. Choose a restore point dated before the error started. System Restore does not delete your personal files, but it will uninstall apps and drivers installed after that date.

Step 1 (Uninstall a specific update). Go to Settings, then Windows Update, then Update History. Click Uninstall updates at the top. Find the most recent update, right-click it, and select Uninstall.
Step 2. Restart your PC after uninstalling the update and check if the error comes back.
Step 3. If the crashes stop but Windows tries to reinstall the same update automatically, use Pause updates in Windows Update settings to give yourself time to check Microsoft’s support pages for a known fix or replacement patch before allowing it back.

Note: Do not leave Windows Update paused permanently. Security patches protect against real threats. Check Microsoft’s release notes for the update that caused the issue before deciding whether to block it long-term.

Test Your RAM for Errors

Faulty RAM is a known hardware cause of DRIVER_IRQL_NOT_LESS_OR_EQUAL. When drivers read corrupted data from bad memory cells, the incorrect priority level access triggers this crash. RAM problems tend to produce random crashes at unpredictable times. If all software fixes have failed, test your memory before looking at anything else.

Step 1 (Quick test). Press Windows key + R, type mdsched, and press Enter. Choose Restart now and check for problems. Windows will reboot and run the memory test automatically.
Step 2 (Thorough test). Download MemTest86 from memtest86.com, write it to a USB drive using the included tool, boot from the USB, and let it run for at least two full passes. One pass takes roughly 30 to 90 minutes depending on how much RAM you have.
Step 3. If MemTest86 reports errors, try removing one RAM stick at a time and re-running the test to find the faulty stick. Replace any stick that fails.
Step 4. Even if RAM passes all tests, try reseating the sticks. Power down, remove each one, and firmly press them back into their slots. A loose connection can produce the same crashes as faulty RAM.

Check Your Hard Drive or SSD for Errors

A drive starting to fail can cause driver files or system files to return bad data when read. This puts the driver into an unexpected state that triggers the IRQL error. A quick health check rules this out before you go deeper.

Step 1. Open This PC, right-click your main drive (usually C:), and select Properties.
Step 2. Go to the Tools tab and click Check under Error Checking. Let Windows scan the drive.
Step 3. Download CrystalDiskInfo (free). It reads the drive’s health data directly and flags drives that are starting to fail. A result of Caution or Bad means the drive needs to be replaced.
Step 4. If the drive shows any Bad health or failing sectors, back up your data immediately and replace the drive before doing anything else.

Quick Checklist: What to Try First

Fix	Time Needed	Best If
Clean restart and check software conflicts	5 – 10 min	Error is new or started after a software install
Update or roll back the problem driver	10 – 20 min	Blue screen named a .sys file or error started after driver update
SFC and DISM scan	15 – 30 min	Any situation. Always worth running
Uninstall Windows update or System Restore	15 – 30 min	Error started right after a Windows update
RAM test (MemTest86)	1 – 3 hours	Random crashes with no obvious trigger
Check drive health (CrystalDiskInfo)	10 – 20 min	PC is old, slow to boot, or making unusual sounds

Still Getting DRIVER_IRQL_NOT_LESS_OR_EQUAL? Advanced Steps

Read the minidump file to identify the exact driver

Every BSOD creates a small crash log called a minidump. Open Event Viewer (search in Start), go to Windows Logs, then System, and look for Critical errors near the crash time. You can also use WhoCrashed (free from Resplendence) to read minidump files in plain language. It usually names the exact driver or file that caused the crash, which tells you exactly where to focus your fix. This is especially useful when the blue screen disappeared too fast to read the filename.

Run a malware scan

Malware can corrupt or replace system drivers, causing them to access memory at the wrong priority level. If no hardware test has found a problem and driver fixes have not helped, run a full scan before going further. Windows Defender is a solid start. For a deeper scan that checks for rootkits and hidden infections inside system processes, Malwarebytes Premium is worth running.

🔧 Tip: If Windows Defender is already running, a second-opinion scan from Malwarebytes Premium can catch threats that Defender misses, especially rootkits that replace or hook into system drivers.

Boot into Safe Mode to isolate the cause

Safe Mode loads Windows with only the minimum required drivers and services. If the crashes stop in Safe Mode, a third-party driver or service is the cause. Restart your PC and hold Shift while clicking Restart, then navigate to Troubleshoot, Advanced Options, Startup Settings, and select Safe Mode. From there, use Device Manager to roll back or uninstall the problem driver, or uninstall the conflicting software.

Use Driver Verifier to catch a misbehaving driver

Driver Verifier is a built-in Windows tool that stress-tests your drivers and forces an immediate crash the moment a driver breaks any rule. This makes it much easier to identify the exact offender. Press Windows key + R, type verifier, and press Enter. Select Create standard settings, then choose Automatically select all drivers installed on this computer. Restart and use your PC normally. When it crashes, read the minidump with WhoCrashed to see exactly which driver failed. Disable Driver Verifier afterward by running verifier /reset in an elevated Command Prompt.

Reset Windows as a last resort

If every software fix has failed and hardware tests come back clean, a Windows reset (Settings, System, Recovery, Reset this PC) with the Keep my files option reinstalls Windows while leaving your personal files in place. This fixes deeply corrupted system files and driver conflicts that no other tool can reach. If crashes continue after a clean install, the fault is hardware and you will need to isolate and replace the failing component.

Frequently Asked Questions

What does DRIVER_IRQL_NOT_LESS_OR_EQUAL mean on Windows?

It means a driver tried to access memory at an interrupt request level (IRQL) that was too high for that operation. IRQL is the priority system Windows uses to decide which processes get access to the CPU and memory at any moment. When a driver breaks that rule, Windows cannot safely continue and forces a restart. The blue screen often names the specific driver file responsible, such as nvlddmkm.sys for NVIDIA or tcpip.sys for network drivers.

What causes DRIVER_IRQL_NOT_LESS_OR_EQUAL most often?

A bad, outdated, or newly updated driver is the most common cause. GPU drivers, network adapter drivers, and chipset drivers are frequent offenders. Antivirus and security software can also trigger it by hooking into memory at the wrong priority level. Faulty or poorly seated RAM is a less common but known hardware cause. If the error started right after a driver update or new hardware install, that is almost certainly where to start.

How do I find which driver is causing DRIVER_IRQL_NOT_LESS_OR_EQUAL?

Look at the blue screen itself. Windows usually prints the driver filename near the bottom of the error screen, for example nvlddmkm.sys (NVIDIA GPU driver), tcpip.sys (network driver), or ntoskrnl.exe (Windows kernel). If you missed it, use WhoCrashed (free from Resplendence) to read the minidump file Windows saved after the crash. It translates the crash log into plain language and names the exact file responsible.

Will DRIVER_IRQL_NOT_LESS_OR_EQUAL delete my files?

No. The blue screen does not delete or damage your files. Windows forces a restart to protect itself. However, if the underlying cause is faulty RAM or a failing drive, your data is at risk from the hardware problem itself. Back up your files before running any hardware tests.

How do I fix DRIVER_IRQL_NOT_LESS_OR_EQUAL if I cannot boot into Windows?

Boot from a Windows installation USB, choose Repair your computer, then open Command Prompt from Advanced Options. From there you can run SFC and DISM, access System Restore, and roll back recent changes. If you can reach Safe Mode by holding Shift while clicking Restart and navigating to Troubleshoot, Advanced Options, Startup Settings, try that first since Safe Mode loads only the minimum drivers and is easier to work in.

Can antivirus software cause DRIVER_IRQL_NOT_LESS_OR_EQUAL?

Yes. Security software runs deep in the system and sometimes hooks into memory at a priority level that conflicts with Windows rules. If the crashes started after installing or updating antivirus software, disable it temporarily or uninstall it and see if the crashes stop. VPN clients and firewall tools can cause the same issue.

Is DRIVER_IRQL_NOT_LESS_OR_EQUAL fixable without reinstalling Windows?

In most cases, yes. Updating or rolling back the problem driver, running SFC and DISM, and removing conflicting software resolve the majority of cases. A full Windows reinstall is only needed when system files are too damaged to repair and no other fix works. Always try the software fixes first before resetting Windows.