This guide walks you through fixing the Windows 10 blue screen error “DRIVER_IRQL_NOT_LESS_OR_EQUAL” (stop code 0x000000D1). This error usually means a driver accessed memory at too high an interrupt request level, often caused by outdated, buggy, or incompatible drivers. We’ll cover the most effective fixes, from simple restarts to driver rollbacks and hardware checks.
What You’ll Need
- Windows 10 PC with administrator access
- Internet connection (for downloading drivers or updates)
- Optional: Windows installation media or recovery drive (for advanced troubleshooting)
Step-by-Step
- Restart your computer. A simple reboot can clear temporary glitches that cause the error. If the error appears again, proceed to the next step.
- Boot into Safe Mode. Safe Mode loads only essential drivers, which helps you troubleshoot. To enter Safe Mode: restart your PC, and as it boots, press F8 (or Shift + F8) repeatedly until the Advanced Boot Options appear. If that doesn’t work, force shutdown (hold power button) three times to trigger Automatic Repair, then go to Advanced options > Startup Settings > Restart, and press 4 or F4 for Safe Mode.
- Uninstall recently installed software or drivers. If the error started after installing new hardware or software, uninstall it. In Safe Mode, go to Settings > Apps, or Device Manager, and remove the suspect item. Restart normally and check if the error is gone.
- Update your drivers. Outdated drivers are the most common cause. In normal mode (or Safe Mode with networking), press Win + X and select Device Manager. Expand categories, right-click each device (especially display adapters, network adapters, and chipset), and select “Update driver” > “Search automatically for drivers.” Repeat for all devices. Alternatively, visit your PC manufacturer’s website and download the latest drivers for your model.
- Roll back a problematic driver. If the error began after a driver update, roll back to the previous version. In Device Manager, right-click the device, select Properties > Driver tab > Roll Back Driver (if available). Confirm and restart.
- Run Windows Memory Diagnostic. Faulty RAM can cause this error. Press Win + R, type “mdsched.exe”, and press Enter. Choose “Restart now and check for problems.” Windows will run a memory test and show results after restart. If errors are found, replace the faulty RAM stick.
- Check for disk errors. Run Check Disk to repair file system issues. Open Command Prompt as administrator and type:
chkdsk /f /r. You’ll be prompted to schedule it for next restart; type Y and restart. Let the scan complete. - Run System File Checker (SFC) and DISM. Corrupted system files can trigger the error. In Command Prompt (admin), run
sfc /scannow. After it finishes, runDISM /Online /Cleanup-Image /RestoreHealth. Restart afterward. - Check for Windows Updates. Go to Settings > Update & Security > Windows Update and click “Check for updates.” Install all pending updates, including optional driver updates, then restart.
- Disable fast startup. Fast Startup can cause driver issues. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable. Uncheck “Turn on fast startup” and save changes.
- Perform a System Restore. If the error persists, restore your PC to a point before the issue started. In Safe Mode, search for “Create a restore point,” click System Restore, and follow the wizard to choose a restore point.
- Reset your PC. As a last resort, you can reset Windows 10. Go to Settings > Update & Security > Recovery > Reset this PC. Choose “Keep my files” to preserve personal data, but reinstall apps. This often resolves driver conflicts.
Common Mistakes
- Skipping Safe Mode: Trying to fix drivers in normal mode when the system crashes repeatedly is inefficient. Always start in Safe Mode.
- Using third-party driver updaters: These tools often install wrong or beta drivers. Stick to Windows Update or manufacturer websites.
- Ignoring hardware issues: The error can be caused by faulty RAM or a failing hard drive. Don’t assume it’s always a driver problem.
- Not uninstalling old drivers before installing new ones: When updating a driver, use Display Driver Uninstaller (DDU) for graphics drivers, or at least uninstall the old driver first to avoid conflicts.
- Overlooking overclocking: If you’ve overclocked your CPU or GPU, revert to stock settings. Unstable overclocks can trigger this error.
Tips
- Always create a system restore point before making major driver changes.
- Keep a list of your hardware components (motherboard, GPU, network card) to quickly find the correct drivers.
- If you recently added new hardware, reseat it properly (remove and reinsert) to ensure a good connection.
- Use the Blue Screen View tool to analyze minidump files (C:\Windows\Minidump) to identify the exact driver causing the error.
- Update your BIOS/UEFI firmware from the manufacturer’s website, but only if you’re comfortable; a failed BIOS update can brick your PC.
Troubleshooting
If the error still appears after trying all the steps above:
- Check the minidump files: Use a tool like BlueScreenView to see which driver is named in the error. Search that driver name online for known issues and fixes.
- Test your hardware: Use MemTest86 to thoroughly test your RAM. Run a hard drive diagnostic tool from your drive manufacturer. Overheating can also cause crashes, so check your CPU and GPU temperatures.
- Remove all non-essential peripherals: Disconnect USB devices, external drives, and extra monitors. Boot with the minimum hardware to isolate the issue.
- Check for malware: Run a full system scan with Windows Defender or a reputable antivirus. Malware can corrupt drivers.
- Use Windows Recovery Environment: If you cannot boot at all, use a Windows installation USB to access Advanced Options and try Startup Repair, or open Command Prompt from there to run the SFC/DISM commands.
- Seek professional help: If you suspect faulty hardware and are not comfortable replacing components, take your PC to a certified technician.
Frequently Asked Questions
What does “IRQL_NOT_LESS_OR_EQUAL” mean?
It means a kernel-mode driver accessed memory at an invalid interrupt request level (IRQL). This typically happens when a driver is buggy, incompatible, or has a memory issue.
Can this error be caused by a virus?
Yes, malware can modify or corrupt drivers, leading to this blue screen. Running a full antivirus scan is recommended.
Will resetting Windows 10 definitely fix it?
It often does, as it reinstalls the OS and removes problematic drivers. However, if the cause is faulty hardware, the error will return.
How do I know which driver is causing the error?
Check the minidump files in C:\Windows\Minidump using a tool like BlueScreenView. It will show the driver name (e.g., nvlddmkm.sys) that caused the crash.
Is it safe to update all drivers at once?
It’s safer to update them individually and restart after each one. Updating all at once can make it harder to identify the culprit if a problem occurs.
Can overclocking cause this error?
Yes, unstable overclocking of the CPU, GPU, or RAM can cause memory access errors. Reset your BIOS to default settings to test.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- MacBook Charger Not Working? Fix It Now
- Fix Windows Cannot Be Installed to This Disk
- Zoom on iPhone & iPad: Host or Join a Meeting
- Fix iPhone SE 4 Unable to Activate: Step-by-Step
- Keep Important Emails From Getting Buried in iPhone Mail Categories
- How to Clear RAM on iPhone: Speed It Up