Do not make Driver Verifier the first step
Driver Verifier deliberately stresses kernel drivers and can create boot loops. Use dump evidence, recent-change rollback and Safe Mode first. If Verifier is ever used, create recovery media, know how to disable it from recovery and follow Microsoft guidance precisely.
Use the crash clues
| Clue | Priority |
|---|---|
| Same driver named repeatedly | Inspect that driver, device and software. |
| Crash began after device installation | Disconnect device and roll back driver. |
| Network activity triggers it | Network, VPN, firewall or filter driver. |
| Gaming triggers it | Graphics, audio, anti-cheat, RAM, tuning. |
| Codes and drivers keep changing | RAM or broader instability. |
1. Reverse the specific recent change
Disconnect the newly added device and roll back its driver in Device Manager. If the crash followed a VPN, antivirus, RGB, monitoring or virtualisation tool, uninstall that specific application using its official process and restart.
Avoid changing several unrelated drivers at once.
2. Enter Safe Mode when crashes happen early
Use Windows Recovery Environment and select Startup Settings → Restart → Safe Mode. If stable, remove or roll back the suspected third-party driver. If Safe Mode also crashes, memory, storage, core drivers and hardware become stronger suspects.
3. Inspect the dump without overclaiming
Preserve files in C:\Windows\Minidump. A debugger can reveal the bugcheck parameters, active process and modules on the stack. Compare multiple crashes: the same third-party driver across dumps is stronger evidence than one appearance.
Do not delete dump files before diagnosis or upload them publicly if usernames or sensitive paths may appear.
4. Install stable, model-specific drivers
Prioritise chipset, network, graphics, audio, storage and device-filter drivers. Use Windows Update or the PC/component manufacturer. If the latest version caused the crash, use Roll Back Driver or the prior stable package.
5. Test VPN, antivirus and filter software
Security, VPN, backup and disk tools install kernel filter drivers. Update them first. When timing strongly implicates one product, remove it temporarily using the vendor’s official uninstaller and keep Microsoft Defender active during the test.
6. Test RAM at default settings
Disable XMP/EXPO, overclocking and undervolting. Run Windows Memory Diagnostic and an extended supported memory test if needed. Changing stop codes, random named drivers and failures under load increase suspicion of RAM corruption.
7. Repair Windows files
Run DISM.exe /Online /Cleanup-Image /RestoreHealth and then sfc /scannow from an elevated Terminal. These repair Windows components but cannot correct a defective driver or memory module.
8. Use Driver Verifier only in controlled diagnosis
Driver Verifier is for advanced troubleshooting when dumps and rollback have not identified a third-party driver. Ensure recovery access first. Select only suspected non-Microsoft drivers rather than indiscriminately stressing everything.
If Windows loops, enter recovery or Safe Mode and run verifier /reset. Seek professional analysis when you are not comfortable recovering an unbootable system.
9. Escalate when software isolation fails
Run manufacturer memory, storage and motherboard diagnostics. Restore firmware defaults, check temperatures and remove recent hardware. Crashes in recovery or during a clean installation strongly point beyond ordinary application software.
Avoid these common mistakes
- Do not run Driver Verifier without a recovery plan.
- Do not download individual driver files from unofficial sites.
- Do not permanently disable security to stop crashes.
- Do not ignore changing stop codes and memory-test errors.
Frequently asked questions
What causes IRQL_NOT_LESS_OR_EQUAL?
Common causes are faulty kernel drivers, incompatible security or hardware software, unstable RAM, overclocking and occasionally damaged system files.
Does a named .sys file identify the bad driver?
It is an important lead, but memory corruption can make an innocent driver appear at the crash point. Confirm with repeated dumps and recent changes.
Can Safe Mode fix this stop code?
Safe Mode helps isolate non-essential drivers and lets you roll back or remove the likely cause; it is not itself the permanent fix.
Technical steps align with Microsoft guidance for bug check 0xA, Startup Settings, Device Manager, Driver Verifier, DISM and System File Checker.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.