Blue screen. Out of nowhere. One second you’re mid-email or mid-game, the next your PC is frozen with IRQL_NOT_LESS_OR_EQUAL and stop code 0x0000000A plastered across the display. Yeah. That one stings.
First time it happens, you reboot and shrug it off. Second time, you start sweating a little. Third time you’re quietly shopping for a new laptop at 2am. Been there. And I’ve fixed this exact crash on hundreds of machines, so trust me when I say it’s rarely the death sentence people assume it is.
So what’s actually going on? Windows moves everything through something called an IRQL — an Interrupt Request Level. Picture it as a priority lane at the CPU. When a driver or a kernel process tries to grab memory it has no business grabbing at that priority level, Windows panics and slams the brakes. That’s your blue screen. And 0x0000000A? That’s Windows essentially shouting “you don’t get access to that” at full volume.
What Causes IRQL_NOT_LESS_OR_EQUAL (0x0000000A)?
Before you start clicking around, let’s talk suspects. Knowing the “why” makes the “how” way less painful:
- Rotten or outdated drivers: The big one. A graphics, network, or chipset driver that doesn’t play nice with your Windows build can set this off. Freshly installed drivers are prime suspects.
- Failing RAM: If your memory modules are going bad, Windows reads and writes to the wrong addresses. Boom. Straight to 0x0000000A.
- Damaged system files: Kernel files get corrupted sometimes. A botched update or an unexpected power cut can do it.
- New hardware or an aggressive overclock: That extra RAM stick you just popped in, or a voltage setting pushed too far, can shove the system past what it can handle.
Step-by-Step Solutions to Fix IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
Method 1: Update or Roll Back Your Device Drivers
Start here. Drivers cause most of these crashes, and this is the least invasive thing you can do. I always open Device Manager first, because a yellow exclamation mark points you straight at the troublemaker.
- Press Windows + X and pick Device Manager from the menu.
- Hunt for any device showing a yellow triangle. Expand those categories.
- Right-click the problem device and hit Update driver.
- Choose Search automatically for drivers. Let Windows poke around.
- Nothing found? Head to the manufacturer’s site yourself. Grab the newest driver for your graphics card, network adapter, and chipset.
- Install it manually, then reboot.
Oh, and one more angle here. If the crashes started right after a driver update, don’t update — roll back. Right-click the device, open Properties, jump to the Driver tab, and click Roll Back Driver. Sounds too easy, I know. But that single click has saved me more times than I can count.
Method 2: Run SFC and DISM Scans for Corrupted System Files
Corrupted Windows files make the kernel act drunk, and this error is often the result. Lucky for you, Microsoft built two repair tools right into Windows. System File Checker (SFC) goes first. DISM cleans up afterward if SFC can’t finish the job.
- Click Start, type Command Prompt, right-click it, and choose Run as administrator.
- Type this in and hit Enter:
- sfc /scannow
- Wait it out. Ten to fifteen minutes, usually. Do not close that window.
- If SFC says it fixed some stuff but couldn’t handle the rest, run this next:
- DISM /Online /Cleanup-Image /RestoreHealth
- Let DISM do its thing. It might sit at 62.3% looking frozen. That’s normal. Walk away, make tea, come back.
- Reboot and see if the blue screen returns.
Boring? Absolutely. Effective? Almost every time.
Method 3: Test Your RAM with Windows Memory Diagnostic
Drivers updated, system files repaired, still crashing? Now your physical memory is the prime suspect. Bad RAM doesn’t always announce itself either. Sometimes it just silently corrupts things until Windows throws a 0x0000000A in your face.
- Press Windows + R, type mdsched.exe, and hit Enter.
- Pick Restart now and check for problems. Your PC reboots and tests memory before Windows even loads.
- Let it run. Twenty to forty minutes, depending on how much RAM you’ve got.
- When it’s done, Windows restarts and shows you the verdict.
Errors reported? You found it. RAM is cheap, so swap out the bad stick and you’re set. Got multiple sticks? Test them one at a time to figure out which one is the dud.
Method 4: Use Driver Verifier to Pinpoint the Faulty Driver
Sometimes Windows clams up. The BSOD says IRQL_NOT_LESS_OR_EQUAL and blames ntoskrnl.exe — which is the kernel itself, not the actual culprit. Useless. That’s when I break out Driver Verifier. It’s built into Windows and it stresses every driver until the guilty one finally rats itself out.
- Press Windows + R, type verifier, and hit Enter.
- Choose Create standard settings and click Next.
- Select Select driver names from a list and click Next.
- Click Providers at the top to sort by manufacturer. Uncheck every Microsoft driver. Leave only third-party ones ticked. Hit Finish.
- Restart. Windows now runs with Driver Verifier watching everything.
- Use your PC like normal. Next crash, the error screen names the exact .sys file behind it.
- Got the filename? Boot into Safe Mode, open Device Manager, and uninstall or roll back that driver.
Heads up, though. Driver Verifier makes your system unstable on purpose. That’s the whole point. So don’t leave it running forever. Once you’ve caught the bad driver, open Command Prompt as administrator and run verifier /reset to switch it off.
Final Thoughts
Blue screens look terrifying. They really do. But IRQL_NOT_LESS_OR_EQUAL is one of the more forgiving ones you’ll run into. Most of the time it’s a driver that needs updating or a RAM stick that’s given up the ghost.
Work through it in order. Check drivers. Run SFC and DISM. Test your memory. And if you’re still chasing ghosts, let Driver Verifier play detective for you. No certification required. Just a bit of patience and the right sequence. Take it one step at a time — you’ll have a stable machine again sooner than you think.