How to Fix IRQL_NOT_LESS_OR_EQUAL Error in Windows

The `IRQL_NOT_LESS_OR_EQUAL` blue screen means a driver or hardware component accessed memory in a way Windows could not allow. The usual fixes are to undo recent changes, check the likely driver, test memory, and repair Windows system files; Safe Mode helps separate startup-driver problems from deeper hardware faults. Avoid changing BIOS settings or replacing hardware until those checks point there.

Is your PC stuck in an IRQL_NOT_LESS_OR_EQUAL crash loop?

Windows may show this error before restarting:

IRQL_NOT_LESS_OR_EQUAL

It often appears during startup, shortly after you sign in, or while Windows is using a particular device. A one-time crash can result from a temporary driver fault, but repeated crashes need investigation.

If Windows reaches the desktop, save your work and restart once. Disconnect any USB device, expansion card, dock, or other hardware that you added shortly before the problem began. Leave the keyboard, mouse, display, and network connection attached if you need them to troubleshoot.

If the crash started after a driver or Windows update, record what changed before installing anything else. If possible, use System Restore or roll back the driver. If the system crashes shortly after login, start Windows in Safe Mode:

1. Hold Shift while selecting Restart from the Windows power menu.
2. Select Troubleshoot, then Advanced options, then Startup Settings.
3. Select Restart and press 4 for Safe Mode or 5 for Safe Mode with Networking.

If you cannot reach the sign-in screen, interrupt startup by holding the power button only after Windows begins loading. Repeat this process until Windows Recovery Environment appears, then choose Troubleshoot and Advanced options. Forced shutdowns can risk unsaved data, so use this only when normal startup is impossible.

Safe Mode loads a smaller set of drivers. If the crashes stop there, a normal-startup driver or service is more likely than Windows' basic files. If the crash continues in Safe Mode, faulty memory, storage, firmware, or another hardware problem becomes more likely.

What usually causes this blue screen, and does the fix apply to your case?

This error is a symptom, not a diagnosis. Common causes include a defective or incompatible driver, failing RAM, corrupted Windows files, an unstable overclock or memory profile, and hardware that is beginning to fail.

The timing can narrow the search. A crash that begins immediately after installing a graphics driver points first to the graphics driver or its interaction with the GPU. A crash after connecting a new dock or Wi-Fi adapter points toward that device's driver. Crashes during games may involve graphics, chipset, power, or memory instability. Crashes during file transfers may involve storage or network drivers.

Before changing anything, note the exact stop-code text, when the crash happens, and any file name shown on the blue screen. A name such as nvlddmkm.sys, igdkmdn64.sys, or a network-driver file is a clue, not proof. The named file may be the component that detected the bad memory access rather than the original cause.

This process applies to supported editions of Windows 10 and Windows 11. You need an Administrator account for driver changes, DISM, SFC, and some diagnostic tools. Restarting is required after many driver changes. Back up important files before hardware work, BIOS changes, or a Windows reset. Do not download drivers from random driver-update sites; use Windows Update or the computer, motherboard, graphics, network, or storage manufacturer's support page.

Before troubleshooting, do two safe checks: disconnect recently added hardware and write down any driver, Windows, or hardware change that came before the crashes. These clues help you choose the first reversible fix.

Try these fixes in the safest order

Start with reversible changes and keep a record of each one. Apply one change at a time so you can tell what fixed the crash.

1. Undo a recent driver change

Open Device Manager while Windows is running normally or in Safe Mode.

Right-click Start > Device Manager > device category > device > Properties > Driver

Look especially at Display adapters, Network adapters, Storage controllers, and System devices. A warning icon, a recently changed driver date, or a device that disappears and reappears is worth investigating. A warning icon does not prove that device caused the blue screen, but it makes that device a reasonable suspect.

If Roll Back Driver is available and the problem began after an update, use it and restart. If it is unavailable, choose Uninstall device only for the suspected device, then restart. Windows may reinstall a basic driver. For a graphics driver, use the manufacturer's supported installer and select its clean-install option if offered. For chipset, storage, and network drivers, prefer the PC or motherboard manufacturer's package because those drivers can depend on the system's firmware and hardware configuration.

If the crash began after installing hardware, shut down, unplug the computer, and remove or disconnect the new component according to the manufacturer's instructions. If the crash stops, install its current compatible driver before reconnecting it.

The expected result is that the crashes stop after the rollback, removal, or hardware disconnection. If they continue, restore the previous setup if practical and move to the memory and system-file checks rather than removing unrelated drivers.

2. Check memory

Windows includes a basic memory test. Save your work first because the computer will restart.

1. Press the Windows key, type Windows Memory Diagnostic, and open it as Administrator.
2. Select Restart now and check for problems.
3. Let the test finish before Windows starts again.

The result may appear after login as a notification. You can also inspect it in Event Viewer.

Event Viewer > Windows Logs > System > Find > MemoryDiagnostics-Results

A reported memory error is strong evidence of a RAM, memory-slot, or memory-configuration problem. Test RAM modules individually, reseat them, or have the computer serviced. If the test reports no errors, RAM is not proven good: intermittent faults, a motherboard slot, a memory profile, or a longer-running test can still be involved.

The expected result is a diagnostic result with no reported memory errors. If errors appear, stop treating the problem as a driver-only issue and test the RAM and slots before continuing normal use.

3. Repair Windows system files

Open Terminal (Admin) or Command Prompt (Admin). These commands need Administrator privileges and may require internet access for DISM to obtain repair files from Windows Update. Run DISM first, then SFC.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM normally reports that the restore operation completed successfully. SFC may say it found no integrity violations, repaired corrupted files, or found files it could not repair. Restart after repairs and run sfc /scannow again if Windows reports that corruption was repaired.

If DISM fails, record the error rather than repeatedly running unrelated repair commands; the component store, Windows Update, or the installation itself may need attention. If SFC cannot repair all files, the blue screen may have another cause, but Windows corruption has not been ruled out.

The expected result is successful DISM repair followed by SFC reporting no remaining integrity violations or reporting that it repaired the files. If the commands complete without finding corruption but crashes continue, focus on drivers, RAM, and hardware instead.

4. Install a known-compatible driver

If rolling back stops the crashes, stay on that working driver rather than immediately accepting the newest version. If no rollback exists, download a stable driver for your exact Windows version and hardware model from the manufacturer's support page. Install one driver family at a time, restart, and test before changing another. Graphics drivers deserve special attention, but network, storage, and chipset drivers can produce the same stop code.

A successful installation should leave the device present in Device Manager without a warning icon and should not reproduce the crash during the workload that previously triggered it. If the warning remains or the crash returns, remove or roll back that driver and investigate the device or its hardware connection.

How to confirm the error is really gone

A single successful restart does not prove the fix. Use the computer in the same way that previously triggered the crash: connect the dock, open the affected game, transfer files, or resume the workload that exposed the problem. Keep the machine running through several normal restarts and sleep or wake cycles.

Check Windows' reliability history for a pattern of failures.

Control Panel > System and Security > Security and Maintenance > Maintenance > View reliability history

A successful repair should stop new blue-screen events. Older failures remain in the history, so focus on their dates and whether new entries appear after the change.

Windows usually saves small crash reports in this folder:

C:\Windows\Minidump

A new .dmp file after another crash confirms that Windows recorded a dump, but the file name alone does not identify the cause. Repeated dumps naming the same third-party driver are useful evidence; repeated crashes with different names may point to memory or hardware corruption. Keep the newest dumps and the exact crash time if you seek support. Do not delete them before analysis.

If crashes stop only while a device is disconnected or only in Safe Mode, the fix is incomplete. Re-enable or reconnect one suspect at a time and test again. If no new crashes occur after the original workload and the relevant driver remains installed, the change is more convincing than simply leaving the computer idle.

What to do when none of the standard fixes works

Return firmware settings to a stable baseline before assuming the motherboard or processor has failed. Enter BIOS or UEFI during startup using the key shown by the computer manufacturer, load default settings, and save. Temporarily disable memory overclocking profiles such as XMP or EXPO and any CPU or GPU overclock. Do not flash BIOS as a first response; use a BIOS update only when the manufacturer's notes indicate a relevant compatibility or stability fix, and follow its exact recovery precautions.

Driver Verifier can expose a badly behaved third-party driver, but it can also force repeated crashes. Use it only if you can reach Windows Recovery Environment and know how to disable it. Do not enable verification for every driver without a recovery plan. If it causes a boot loop, open Advanced options, start Safe Mode, and run:

verifier /reset

A clean Windows installation is a last resort, not the first fix. Back up personal files, confirm that you have installation media and activation information, and install only the required hardware drivers at first. If the blue screen returns on a clean installation with default BIOS settings, software is less likely to be responsible.

At that point, test RAM modules and slots separately, inspect storage health, and have the power supply, motherboard, GPU, or other suspected component tested. Replace a part only when testing or a reproducible isolation result supports it. Seek professional help sooner if the computer cannot stay on long enough to back up files, shows data corruption, overheats, smells burnt, or crashes during memory testing.

Bring the exact stop code, crash times, recent changes, Device Manager observations, memory-test result, and newest minidumps to a technician. That information can distinguish a driver problem from a failing component without requiring unnecessary replacement.

Conclusion

Undo the most recent change, use Safe Mode if necessary, then check the likely driver, memory, and Windows system files. If the error returns, preserve the minidumps and crash times; move to BIOS and hardware testing only when those results justify it, or seek professional help if the computer is unstable or showing physical symptoms.

Frequently Asked Questions

Can a graphics driver cause IRQL_NOT_LESS_OR_EQUAL?

Yes. A faulty, incompatible, or damaged graphics driver can trigger the stop code, especially when crashes begin after a graphics-driver installation or during GPU-heavy work. Roll back first if possible, then install a compatible driver from the graphics or computer manufacturer's support page.

Does this error always mean my RAM is bad?

No. Drivers are a common cause, and corrupted system files or unstable firmware settings can produce the same error. A memory-test failure is strong evidence of a RAM, slot, or memory-configuration problem, but a clean basic test does not rule out every intermittent hardware fault.

Should I use Driver Verifier to find the problem?

Only after safer checks fail and you have a recovery plan. Driver Verifier can deliberately expose driver faults by causing more blue screens. If you use it, verify third-party drivers selectively and know how to enter Safe Mode and run `verifier /reset`.