Fixing 'Driver IRQL Not Less or Equal' in Games
This BSOD usually means a driver tried to access memory it shouldn't. The fix is almost always updating or rolling back your GPU driver.
The 30-Second Fix: Roll Back Your GPU Driver
You're in the middle of a ranked match and the screen goes blue. The error says DRIVER_IRQL_NOT_LESS_OR_EQUAL (stop code 0x000000D1). I've seen this hundreds of times. The culprit is almost always a bad graphics driver update — Nvidia or AMD, doesn't matter.
First thing to try: roll back to the previous driver. This takes 30 seconds.
- Open Device Manager (right-click Start, pick Device Manager).
- Expand Display adapters, double-click your GPU.
- Go to the Driver tab, click Roll Back Driver.
- If it's greyed out, there's no previous driver saved. Skip to the next fix.
- Follow the prompts, restart your PC, and test your game.
This works about 40% of the time. Nvidia's Game Ready drivers have a bad habit of shipping with new features that break older hardware. AMD's Adrenalin drivers are better but still have hiccups.
The 5-Minute Fix: Clean Install Your GPU Driver
If rollback didn't help or wasn't available, you need a clean install. Don't bother with Windows Update — it usually pulls outdated drivers.
- Download Display Driver Uninstaller (DDU) from Guru3D. Save it to your desktop.
- Boot into Safe Mode: hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart, press 4.
- Run DDU. Pick Clean and Restart for your GPU brand (Nvidia or AMD).
- After reboot, install the latest driver from Nvidia or AMD. Not the beta, not the hotfix — the latest Game Ready or WHQL version.
- Select Custom Installation and check Perform a clean installation.
This nukes any leftover junk from old drivers. I've seen DDU fix issues that a standard uninstall can't touch. Don't skip Safe Mode — regular mode lets Windows fight you during the cleanup.
The 15+ Minute Fix: Check Memory and System Files
If the clean driver install didn't work, the problem isn't the GPU driver. Now we look at system-level stuff.
Run CHKDSK and SFC
Corrupted system files can cause this error. Open Command Prompt as admin and run:
sfc /scannowThen:
chkdsk C: /fYou'll need to restart for CHKDSK. Let it run — it can take 20 minutes on a spinning disk, less on an SSD.
Test Your RAM
Faulty RAM triggers 0x000000D1 more often than most people think. Use Windows Memory Diagnostic:
- Press Win+R, type
mdsched.exe, press Enter. - Pick Restart now and check for problems.
- Let it run. It'll take 30-60 minutes. Go make coffee.
- After reboot, check the results in Event Viewer under Windows Logs > System, filter for MemoryDiagnostics-Results.
If it finds errors, replace the bad stick. Don't bother reseating RAM — if it passes the test, it's fine.
Disable Overclocking
If you're overclocking your CPU, GPU, or RAM, stop. Reset everything to stock. XMP profiles count as overclocking. I've seen unstable RAM timings cause IRQL errors that vanish at stock speeds.
If none of this works, you might have a dying motherboard or GPU. Try swapping the GPU into another PC if you have one. If the error follows the card, it's hardware failure. If it stays on the original PC, check the motherboard's chipset drivers — update them from the manufacturer's website, not Windows Update.
One last thing: some anti-cheat software (EAC, BattlEye) can trigger this error when it conflicts with driver hooks. Temporarily disable any RGB software, Razer Synapse, or Logitech G Hub before gaming. You'd be surprised how often that's the fix.
Was this solution helpful?