Home / Guides / Blue Screen of Death (BSOD)

IRQL_NOT_LESS_OR_EQUAL Blue Screen

Intermediate Blue Screen of Death (BSOD) Applies to: Windows 7, Windows 10, Windows 11

Almost always a driver issue — most often network, audio, or graphics.

Before you start: save any open work and note down what you were doing when the problem started — that context helps if you need to search further or ask for help.
  1. Boot into Safe Mode and check whether the crashes stop — if they do, a third-party driver is the cause, not hardware.
  2. Update or reinstall your network adapter driver first, since it's the single most common culprit for this specific stop code.
  3. Check Device Manager for anything with a yellow warning icon, and update or reinstall that driver.
  4. If the crash started right after a driver update, roll it back: Device Manager > right-click the device > Properties > Driver tab > Roll Back Driver.
  5. If you've overclocked your CPU or RAM, revert to stock settings before troubleshooting further — an unstable overclock produces exactly this stop code, and it's easy to overlook once the overclock has been in place for a while without issue.
  6. Run "sfc /scannow" from an admin Command Prompt to repair any corrupted system files that could be contributing.
  7. Check disk health with "chkdsk C: /f" — bad sectors can trigger this exact stop code if Windows fails to read driver or kernel data cleanly from a failing drive.
  8. If the crash keeps recurring with no clear driver to blame, Driver Verifier (search "verifier" and run it from an admin Command Prompt) is the tool advanced troubleshooters reach for — it deliberately stresses drivers to force a crash that names the actual culprit, rather than waiting for one to happen naturally.
Still not fixed? Send us the details and we'll help you dig further, or browse related guides in Blue Screen of Death (BSOD).

Frequently Asked Questions

Is IRQL_NOT_LESS_OR_EQUAL always caused by a driver?
It's the most common cause by far, but not the only one — overheating, failing RAM, and disk errors can also produce this exact stop code, which is why this guide checks those too rather than assuming it's always a driver.
Do I need to know which driver is at fault before I can fix this?
No — updating all your drivers via Windows Update and checking Device Manager for warning icons resolves this in most cases without needing to identify the specific culprit first.

Related guides

How to Read and Respond to Any Blue Screen

A general framework for any stop code you don't recognize.

Intermediate

MEMORY_MANAGEMENT Blue Screen

Usually points to RAM, a driver conflict, or disk corruption.

Intermediate

CRITICAL_PROCESS_DIED Blue Screen

A core Windows process crashed — often tied to a recent update or corrupted system file.

Intermediate