Common Blue Screen Errors and How to Fix Them Fast

That screen. You know the one. Everything freezes, the display goes that flat shade of blue, and a hex code stares back at you while Windows quietly restarts itself before you can write the number down.

I keep a running note of every stop code I've met on my own machines and on friends' laptops, and the pattern is almost boring: five or six codes account for most blue screens people actually hit. The rest are rare enough that you'll likely never see them. So instead of a giant list you'll never use, here's the short version of the common Blue Screen of Death errors and how to fix them, split by what the code is really telling you.

One thing before you touch anything. The moment a BSOD appears, the code is usually gone in under a second. The next time it happens, photograph the screen with your phone. That single hex value — something like 0x0000007E or 0x00000050 — narrows the problem from "it's broken" to a specific subsystem in about ten seconds.

Common blue screen errors and how to fix them

Not all codes are equal. Some point straight at hardware, some at drivers, some at the storage layer. The trick is grouping them, because codes in the same family usually share a fix. Here's how I split them.

The hardware family is the one people fear most, and usually for no reason — RAM problems are far more common than a dying CPU, and RAM is cheap to test. The driver family is the largest and the most annoying, because a driver can work for months and then break after an update you didn't ask for. And then there's the storage family: file system corruption, a failing disk, or a boot configuration that lost its way.

Hardware-related codes

0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) is the one I see most often on aging desktops. Windows asked for a chunk of memory that wasn't there when it went looking. Nine times out of ten it's a bad RAM module; the tenth time it's a driver writing to memory it doesn't own.

0x0000001A (MEMORY_MANAGEMENT) sits right next to it — same neighborhood, same suspect list. Run Windows Memory Diagnostic before you replace anything. It ships with Windows, it's free, and it takes about twenty minutes. If it flags errors, reseat the sticks first (dust and a loose contact cause more "dead RAM" than actual dead RAM), then test again one stick at a time.

Driver-related codes

0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) and 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL) are almost always drivers. An .sys file overstepped its authority and took the system down with it.

The fast way in: open Driver Verifier, enable standard verification, reboot, and let it stress your drivers. When a bad one fails, it names itself in the next crash — often in the filename on the blue screen itself, something like nvlddmkm.sys for graphics or rtwlane.sys for Wi-Fi. Then roll that driver back in Device Manager, or grab a clean installer from the maker's site rather than relying on the generic Windows update.

0x0000009F (DRIVER_POWER_STATE_FAILURE) is the one that only appears when you sleep, hibernate, or shut down. It's a driver that can't handle the power transition. Check your chipset drivers first, then anything with a USB connection.

Storage and file system codes

0x0000007B (INACCESSIBLE_BOOT_DEVICE) means Windows lost the disk it was booting from. It showed up constantly back when people flipped the SATA mode in BIOS from AHCI to IDE, or moved a drive to a new motherboard. If it appears after a hardware change, go back into BIOS and undo that setting before you reinstall anything.

0x00000024 (NTFS_FILE_SYSTEM) points at the file system itself. This is where chkdsk earns its keep. From an elevated Command Prompt, chkdsk C: /f /r will scan and repair. But — and this matters — if chkdsk keeps finding errors on the same drive, the drive is dying. Stop running it and back up your data.

How to fix blue screen on Windows 10

Windows 10 still has the most blue screens in the wild, simply because more machines run it. The good news is that its recovery environment is mature and predictable. The bad news is that automatic restart is on by default, so most people never see the code in the first place.

Turn off automatic restart, then read the code

1. Right-click This PC and choose Properties.
2. Open Advanced system settings.
3. Under Startup and Recovery, click Settings.
4. Uncheck Automatically restart.

Now the next crash holds the screen long enough to read. This one checkbox has saved me more diagnostic time than any tool I've installed.

How to fix blue screen error in Windows 10 using Command Prompt

Boot into the Windows Recovery Environment (hold Shift while clicking Restart, or boot from your install media), then open a Command Prompt from Troubleshoot → Advanced options. Run these in order and let each finish:

• sfc /scannow — checks and repairs corrupted system files
• DISM /Online /Cleanup-Image /RestoreHealth — repairs the component store sfc depends on; run it if sfc reports files it can't fix
• chkdsk C: /f /r — repairs file-system errors and bad sectors on the system drive

If the machine won't boot at all, boot from a USB install drive instead of the internal disk and run the same commands against the offline Windows image. One caveat I learned the hard way: don't run multiple repair commands at once and don't interrupt chkdsk. A half-finished repair turns a fixable problem into an unbootable one.

How to fix blue screen on Windows 11

Windows 11 changed two things that trip people up. First, starting with the 24H2 release, many crashes now show a black screen with the same wording and the same stop code. It is exactly the same failure underneath — the background color just changed. If your screen went black with a stop code, treat it as a blue screen.

Second, the recovery paths moved. The old Shift+Restart trick still works, but the clean route is Settings → System → Recovery → Advanced startup → Restart now.

How to fix blue screen error in Windows 11 using Command Prompt

Same commands, same order, same patience. From the recovery environment, open Command Prompt and run sfc /scannow, DISM /Online /Cleanup-Image /RestoreHealth, and chkdsk C: /f /r exactly as in Windows 10. The tools didn't change. What changed is where you find them and the fact that Windows 11 is stricter about unsigned or mismatched drivers, which is actually a gift — it refuses to load more of the bad ones.

Windows 10 vs Windows 11 — what actually differs

Behavior	Windows 10	Windows 11
Screen color on crash	Blue	Blue, or black from 24H2 onward
Recovery path	Shift + Restart, or install media	Settings → System → Recovery, or install media
Driver signing enforcement	Lenient	Stricter — blocks more bad drivers up front
Command-line repairs	sfc, DISM, chkdsk	Same tools, same commands

The part everyone skips: map the code to the cause

Here's where most "fix it" lists fail you. They tell you to update drivers and run a scan and hope for the best. That's guesswork. The stop code already did the triage for you. Read it, group it, fix the matching family.

• 0x00000050 / 0x0000001A → suspect RAM. Test memory before touching anything else.
• 0x0000007E / 0x000000D1 → suspect a driver. Run Driver Verifier, find the named .sys file, roll it back.
• 0x0000009F → power-state driver. Check chipset and USB drivers.
• 0x0000007B → boot device. Undo any BIOS storage-mode change.
• 0x00000024 → file system. Run chkdsk — but watch for repeat errors.

A minute ago I told you five or six codes cover most real-world crashes. These are them. If your code isn't on the list, the same triage logic still applies: is it memory, a driver, or storage?

Keeping the blue screen away

Most fixes are reactive. A little prevention goes a long way, and none of it is complicated.

1. Let Windows install signed drivers, and get graphics and chipset drivers from the hardware maker rather than a random download site.
2. Run Windows Memory Diagnostic once a year — it's painless and catches failing RAM early.
3. Keep a recent system image. When all else fails, restoring in twenty minutes beats a day of troubleshooting.
4. Don't install two antivirus tools at once. They fight over the same kernel hooks and cause crashes you'll never trace.

I'll be honest: I ignored that last one for years, ran two security suites side by side, and spent a full weekend chasing a stop code that vanished the moment I uninstalled one of them. Lesson learned.

What if the same code keeps coming back after every fix?

Then it isn't a software problem. A recurring stop code on the same machine usually means failing hardware — RAM, the drive, or occasionally the power supply. Back up your data first, then test each component individually. Software fixes can't cure a dying stick of RAM.

The blue screen isn't the enemy. It's Windows throwing its hands up because it can't safely continue — which is, frankly, more honest than quietly corrupting your files. The next time that screen appears, don't panic and don't mash the power button. Grab your phone, photograph the code, and let it tell you which family of problem you're actually in.