Bsod Driver_Irql_Not_Less_or_Equal Windows 11
On Windows 11, DRIVER_IRQL_NOT_LESS_OR_EQUAL usually points to one bad kernel driver, so fix the driver class first: if the crash began after an update, roll it back; if it follows sleep, gaming, or a USB dock, update or remove that device’s driver. Ignoring it can turn one repeatable BSOD into data loss, broken sleep, and random reboots. This guide shows how to read the crash pattern, identify the likely driver, and choose update, rollback, or removal.
What the stop code means
That stop code means a kernel-mode driver tried to touch pageable or invalid memory while the system was at too high an IRQL, so Windows stopped to protect the kernel. In plain terms, a driver asked for memory at a moment when that memory could not be safely reached. Microsoft documents the bug check as 0x000000D1, and it is a driver-isolation problem first, not a generic Windows fault.

Why IRQL matters
IRQL is the kernel’s priority level. At higher levels, Windows blocks some memory access and paging because the system must keep timing predictable. If a driver dereferences a bad pointer, touches pageable data, or runs pageable code at or above DISPATCH_LEVEL, the machine can crash immediately instead of corrupting memory silently.
How this differs from 0xA
Do not blur this with IRQL_NOT_LESS_OR_EQUAL, which is bug check 0xA. The two are related but not interchangeable. Here, the driver path and timing matter more than a generic memory label, so the first job is to match the crash pattern to the most likely driver class.
Which driver is most likely?
The strongest clue is timing. A crash on boot usually points to the startup driver stack; a crash after a driver or Windows Update often points to the newest change; a crash during gaming, sleep, or a dock handoff often points to GPU, network, chipset, or security software. Start with the driver class that matches the pattern, not with random repair steps.
Crash pattern guide
Say your PC blue-screens the moment the desktop appears. That often means a startup driver or a device that loads early. Suppose the machine is stable until you launch a game, then it crashes under GPU load. That makes display drivers or a related filter driver more likely than RAM.
Driver triage matrix
This matrix gives you the fastest safe move first, then the evidence to check if the guess is wrong. Use it before you begin broad repairs. If the same class keeps appearing in Device Manager, logs, or dumps, treat that as stronger evidence than the blue screen text alone.

| Trigger pattern | Likely driver class | Fastest safe action | Evidence to check | Log or dump clue |
|---|---|---|---|---|
| Crashes during boot or just after sign-in | Chipset or storage filter driver | Boot Safe Mode and roll back the last driver change | Device Manager warning icon, recent install date | Minidump shows a storage or boot-related module |
| Crashes right after a driver update | GPU, Wi‑Fi/Ethernet, or VPN/security software driver | Roll back that specific driver in Device Manager | Recent driver version change or Windows Update history | Dump names the updated module or a related filter driver |
| Crashes while gaming or under heavy graphics load | GPU/display driver | Update from the OEM package, or roll back one version if the issue started after an update | Display adapter entry, Event Viewer display errors | Dump points to a display module or video stack component |
| Crashes on sleep or wake | Chipset, power-management, or Wi‑Fi driver | Disable the suspect device, then test wake again | Sleep-related events, device reconnect failures | Logs show resume failure or a device timeout |
| Crashes when a USB dock or hub is attached | USB controller, dock firmware, or network adapter driver | Unplug the dock, then update or remove the dock-related driver | Device disconnect/reconnect pattern in Event Viewer | Dump references USB, network, or dock stack modules |
How do I start the fix in Windows 11?
A common starting point is Safe Mode, then Device Manager can be used to focus on the device class that best matches the crash pattern. If Windows is stable enough, also check Windows Update optional updates, because Microsoft recommends looking there after recurring restarts. Remove any newly added hardware before you go deeper.
- Open Settings > System > Recovery > Advanced startup > Restart now.
- Choose Troubleshoot > Advanced options > Startup Settings, then enter Safe Mode. Use Safe Mode with Networking only if you need to download a driver.
- Open Device Manager, find devices with a warning icon, and check the most likely class first: GPU, network, chipset, or security software.
- Right-click the suspect device and choose Properties > Driver to use Roll Back Driver if the problem began after an update, or Update driver if the driver is old.
- If rollback is unavailable, choose Uninstall device, then reboot and let Windows reinstall it.
- Open Settings > Windows Update > Advanced options > Optional updates and install hardware-specific driver updates if they are offered.
- If the system still loops, disconnect new peripherals, USB docks, and add-in adapters before the next boot.
Safe Mode entry: Settings > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings Driver rollback path: Device Manager > (device) > Properties > Driver tab > Roll Back Driver / Uninstall device
How do you check dumps and logs?
The blue screen can show the stop code and a module name, and that module often gives you the first useful clue. If the machine reboots too fast to read it, inspect the minidump and Event Viewer after restart. Microsoft also notes that the blue screen may show the module name running at the time of the crash. (Microsoft Support)
What to extract from a minidump
Look for four things: the bug check code, the parameter values, the named module, and the stack trace around the fault. Advanced users can use WinDbg commands such as !analyze, dx KiBugCheckDriver, .trap, k, kb, kc, kd, kp, kP, kv, !irql, and ln on parameter 4. If the dump shows the same driver more than once, that is stronger evidence than a single on-screen name.
Where to find the records
Check C:\Windows\Minidump\ for the recent dump files after reboot. Then open Event Viewer and look under Windows Logs > System for crash-related events. Event Viewer also shows Windows Memory Diagnostic results after a reboot, which helps if RAM is part of the picture.
Could RAM or storage be the cause?
Yes, but treat memory and storage as secondary checks after the driver class is narrowed down. Faulty RAM can still trigger this stop code, and storage problems can make a driver fault look worse. Run a memory check if the crash pattern is inconsistent, the dump points nowhere useful, or you see errors across different driver classes.
Run Windows memory diagnostic
Use the standard test first, then repeat with a longer test if the first pass finds errors or if the crashes keep changing shape. The built-in tool is mdsched.exe, and Event Viewer later shows the result. If you need a deeper pass, a bootable tool such as memtest86 is the next step.
- Press Win + R, type mdsched.exe, and press Enter.
- Choose Restart now and check for problems.
- After the restart, open Event Viewer and review the memory test result in Windows Logs > System.
- If the test reports errors, back up files, reseat or replace the DIMMs, then retest.
Microsoft recommends keeping 10% to 15% of free disk space available. Low free space will not usually cause this stop code by itself, but it can make paging, driver installs, and recovery work less reliably.
Still not working?
If the same crash keeps returning, move from recovery to isolation. First, use System Restore or other recovery options to step back from a recent driver or update change. Then try a clean reinstall of the suspected driver class. If the system still fails, the remaining suspects are hardware, firmware, or a deeper driver conflict that needs dump analysis.

If that did not work, try this next
Disable the suspect device in Device Manager and test a cold boot. If that helps, reinstall the driver from the hardware maker rather than from a generic package. If the problem began after a recent Windows Update or OEM driver push, roll back that exact change before trying anything broader.
- Open Device Manager, right-click the suspect device, and choose Disable device for a quick isolation test.
- If the system becomes stable, reopen the same device entry and choose Uninstall device, then reboot.
- Use System Restore or Reset This PC only if the loop continues after driver rollback and removal.
- If crashes persist across Safe Mode, normal boot, and different driver versions, hand the minidump to vendor support or an advanced debugger.
Keep the driver version that matches the crash pattern until you have a known-good replacement, and avoid stacking a new GPU, Wi‑Fi, or VPN driver on top of a fresh Windows Update on the same day.
Frequently asked questions
How do I fix driver_irql_not_less_or_equal in Windows 11?
Start in Safe Mode, open Device Manager, and act on the device class that matches the crash timing. If it began after an update, choose Roll Back Driver; if it began after sleep, gaming, or a dock change, update or uninstall that driver. Then check Optional updates in Windows Update.
What is driver_irql_not_less_or_equal blue screen?
It is a stop code that appears when a kernel driver touches memory at the wrong IRQL and Windows halts the system. The fastest practical response is to identify the driver class from the crash pattern, then use Device Manager or dump analysis to confirm the module before changing anything else.
How do I tell which driver caused the crash?
Read the module name on the blue screen, then confirm it in C:\Windows\Minidump\ or Event Viewer. If you use WinDbg, !analyze and dx KiBugCheckDriver are the first commands to check. Repeat crashes that name the same module are the best clue.
Should I update or roll back the driver for this BSOD?
Use the crash timing to decide. If the stop code started after a driver or Windows Update, roll back first. If the driver is old, missing, or tied to a dock, GPU, or network issue, update it from the device maker or uninstall it and let Windows reload it.
Can bad RAM cause driver_irql_not_less_or_equal on Windows 11?
Yes, but RAM is not the first assumption. Run mdsched.exe first, then check the result in Event Viewer. If the memory test fails, confirm with a longer test or a bootable tool, and inspect the affected DIMMs before reinstalling drivers again.
Is DRIVER_IRQL_NOT_LESS_OR_EQUAL the same as IRQL_NOT_LESS_OR_EQUAL?
No. The related 0xA stop code is a different bug check. For this one, the key detail is the 0x000000D1 path and the kernel-driver access at a too-high IRQL, so the fix should start with driver isolation, not a generic memory-only repair.
How do I use Safe Mode to fix a repeated BSOD in Windows 11?
Go to Settings > System > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings. Boot Safe Mode, then remove, roll back, or disable the suspect driver in Device Manager. Use Safe Mode with Networking only if you need to fetch the replacement driver.






