Blue Screen of Death on Windows 11 (Now It's Black)? What the Stop Code Means and How to Fix It

Everything is fine, and then the screen fills with a solid color, a line of text, a "stop code," and a message that your PC ran into a problem and needs to restart. A few seconds later it reboots on its own. That's the Blue Screen of Death — the BSOD — and despite the scary nickname, it's not your computer dying. It's Windows hitting an error it can't safely recover from and choosing to stop rather than risk your data, then handing you a clue about what went wrong. One of them now and then, after which the PC boots fine, is usually nothing to lose sleep over. The same crash over and over is what you actually need to chase down — and the screen itself tells you where to start.

One twist trips people up in 2026: as of a 2025 update the screen isn't blue anymore — Microsoft redesigned it and made it black. Same crash, same purpose, different color, and it now restarts faster (about two seconds), so it can flash by before you read it. We'll cover how to catch it when it's too quick, how to read the part that matters, and how to fix the cause — first for a PC that still boots, then for one stuck in a crash loop. This is the kind of thing we sort out for homes and small businesses across Southern California and the Coachella Valley all the time.

Blue, black, and which "black screen" you actually have

First, clear up the color confusion, because it matters for what you search and what you do. For decades the crash screen was blue. In 2025 Microsoft rolled out a redesigned, streamlined version that is black — it dropped the old frowning face and the QR code, but it kept the two things that matter for troubleshooting: the stop code and the name of the component that failed. So if you see a black screen with a "stop code" and a "your device ran into a problem" message, that is the Blue Screen of Death, just in its new clothes. Nothing extra is wrong; the name simply hasn't caught up to the color.

That said, "black screen" gets used for two completely different problems, and it's worth knowing which you've got. A black screen with text, a stop code, and an automatic restart is a crash report — the BSOD — and this article is for that. A black screen with nothing on it — no text, no cursor, the machine seems on but the display is blank — is a different issue entirely: a display, graphics, or boot problem, not a crash. If that's what you're seeing, our guides on a monitor that won't turn on and a laptop that won't turn on are the right place to start instead. The presence or absence of that stop-code text is how you tell them apart.

The one thing to do when you see it: write down the stop code

Almost everyone's instinct is to panic and restart. The far more useful instinct is to grab a single detail off the screen first: the stop code. It's the short, all-capitals phrase or hex value near the bottom — things like SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT, or PAGE_FAULT_IN_NONPAGED_AREA. Just as valuable is the failing module name if one is shown — usually a file ending in ".sys", which is the actual driver or system component that triggered the crash. That file name often points straight at the culprit (a graphics, network, or storage driver, for example).

Snap a photo of the screen with your phone, or jot the code and the .sys name on paper. Those two strings are what turn "my computer crashed" into "my computer crashed because of this," and they're what any tech — including us — will ask for first. Without them you're guessing; with them, half the diagnosis is done. If the screen vanishes before you can read it, the next section is for you.

When it reboots too fast to read — how to catch the crash

Because the redesigned crash screen restarts in roughly two seconds, a lot of people never actually see it. To them it just looks like the PC "randomly restarts" on its own — no warning, no message, suddenly back at the login screen. If that's you, there's a good chance you're getting a BSOD that's simply too quick to catch, and Windows keeps a record of it either way. Two built-in tools recover the detail after the fact. The friendlier one is Reliability Monitor: click Start, type "reliability," and open "View reliability history." You'll get a timeline with red X marks on the days things crashed — click one and it shows the stop code and the file involved. For more depth, Event Viewer (right-click Start > Event Viewer > Windows Logs > System) logs the same critical errors with timestamps.

You can also slow the screen down so you catch it live next time. Press the Windows key, type "advanced system settings," open it, and under "Startup and Recovery" click Settings, then uncheck "Automatically restart." Now the crash screen stays put until you choose to restart, giving you all the time you need to read and photograph the stop code. This one setting turns a baffling "it just reboots" mystery into a readable, searchable error — and it's the first thing we change on a machine that reboots without explanation.

One crash, or a loop? How worried to be

Context decides how seriously to take it. A single blue (black) screen that you've never seen before, after which the PC boots normally and behaves, is often a one-time hiccup — a driver glitch, a momentary hardware fluke, a bad moment for one program. Note the stop code in case it comes back, install any pending updates, and carry on; there's no need to tear the machine apart over one. The pattern that demands attention is repetition: the same stop code again and again, a crash every time you do a particular thing (plug in a device, open a certain app, wake from sleep), or a true loop where the PC crashes, restarts, and crashes again before you can use it.

A repeating crash is your computer telling you something specific is broken, and the good news is that "specific" usually means findable. The two biggest clues are the stop code (what kind of failure) and timing (what changed right before it started). If the crashes began right after a Windows update, a new driver, a newly installed program, or a piece of new hardware, you've very likely found your suspect — and undoing that recent change is often the whole fix. Hold that thought; it drives the fix order below.

What the common stop codes are telling you

You don't need to memorize these, but a rough translation helps you aim. A large share of crashes come down to a driver — the small piece of software that lets Windows talk to a specific piece of hardware. Codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and KMODE_EXCEPTION_NOT_HANDLED usually mean a driver misbehaved, and the .sys file named on the screen often tells you which one (a display, Wi-Fi, or storage driver, typically). VIDEO_TDR_FAILURE points specifically at the graphics driver — if your crashes happen mainly in games, our guide to game crashes and a clean GPU-driver reinstall is the targeted fix.

Other codes lean toward hardware or the disk. MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA frequently involve RAM or a driver poking at memory it shouldn't, which makes a memory test worthwhile (below). INACCESSIBLE_BOOT_DEVICE and CRITICAL_PROCESS_DIED point at the system drive or essential Windows files — often after a botched update, and sometimes a sign of a failing drive, so make sure your backups are current. WHEA_UNCORRECTABLE_ERROR is a hardware-level fault, classically tied to overheating, an unstable overclock, or aging components. None of these are a diagnosis on their own, but they tell you whether to look at software (a driver, an update) or hardware (memory, drive, heat) first.

The fix order on a PC that still boots

If Windows still starts between crashes, work through this from safest and cheapest to more involved. First, undo what changed: if the crashes started after a new app or driver, uninstall it; if they started after a Windows update, you can remove that specific update under Settings > Windows Update > Update history > Uninstall updates. Then, paradoxically, also make sure everything is fully up to date — install all pending Windows updates and grab the latest drivers from your PC or component maker (graphics and chipset drivers especially), because crashes are just as often caused by an old, buggy driver as a new one. Microsoft's own first moves for these errors are exactly this: update drivers, install Windows updates, and remove recently added hardware.

If that doesn't settle it, repair Windows' own files: open Command Prompt or Terminal as administrator and run "sfc /scannow", and if it finds problems it can't fix, follow with "DISM /Online /Cleanup-Image /RestoreHealth", then restart. Free up disk space too — Microsoft suggests keeping 10–15% of the drive free, and a stuffed system drive genuinely causes instability. Check temperatures and airflow if the crashes come under load (a dusty, overheating machine throws hardware errors — our summer-overheating guide explains why and what to clear). And run a quick malware scan, since infections can crash a system; Windows Security's full scan is enough. If a specific stop code keeps coming back, search that exact code plus your PC model — you'll often find it's a known issue with one driver and a known fix.

If it won't boot or is stuck in a crash loop

When the PC crashes before you can get to the desktop, you need the recovery environment. If Windows fails to start a few times in a row, it usually drops into "Automatic Repair" / the recovery screen on its own; you can also force it by holding Shift while you click Restart, or by switching the PC off with the power button during boot three times in a row. From there, Troubleshoot > Advanced options gives you the tools that matter: Startup Repair (let Windows try to fix the boot automatically), System Restore (roll the machine back to a restore point from before the trouble — the single most effective option if the crashes are recent), Uninstall Updates (remove a bad quality or feature update), and Safe Mode via Startup Settings (a minimal Windows with basic drivers — if it's stable in Safe Mode, the cause is almost certainly a driver or a startup program you can then remove).

Windows 11 also added a newer safety net called Quick Machine Recovery. On 24H2 and later (it arrived for Home and Pro PCs with the August 2025 security update), if a PC repeatedly fails to boot it can enter the recovery environment, connect to the internet on its own, and pull a targeted fix from Microsoft — useful when a bad update breaks a whole class of machines at once. It needs a network connection to do its thing, and you can confirm it's enabled under Settings > System > Recovery. If none of the recovery options stick and the machine keeps looping, that points more toward failing hardware or a corrupted Windows install — the next section and a proper repair are the move, not endless retries.

When it's the hardware

Some crashes are physical, and a few quick tests narrow it down. For memory, run the built-in Windows Memory Diagnostic — press Start, type "Windows Memory Diagnostic," and let it test on the next restart; errors there mean a RAM stick is bad (and reseating or replacing it is a straightforward fix). For the drive, repeated INACCESSIBLE_BOOT_DEVICE crashes, long freezes, or strange noises suggest the system drive is failing — check its health and make sure your files are backed up now, before it gets worse, because a dying drive rarely gives much notice. Heat is a classic cause of random crashes under load: if the machine is hot, the fans are screaming, and it crashes during games or video, clearing dust and improving airflow often stops it.

Less common but real are a failing power supply (random reboots with no stop code at all, often worse under load) and an unstable overclock or a loose component. These are harder to pin down at home, which is exactly where a hands-on diagnosis pays off — swapping in a known-good part is often the fastest way to a definite answer. If a single component turns out to be the cause and the PC is otherwise healthy, replacing that one part is usually far cheaper than a new machine; our Repair-or-Replace calculator helps you weigh it.

How we can help

You can get a long way on your own with the stop code and the steps above, and most one-off crashes never come back. But if your PC keeps blue-screening (or black-screening), if it's stuck in a loop you can't break, if the same stop code returns no matter what you try, or if you'd rather not risk a fix that touches the boot drive, that's a good call to make. We read the stop code and the crash logs, identify whether it's a driver, an update, memory, the drive, or heat, roll back the change that started it, test the hardware properly, and — if a part has failed — replace it with the right component, all while protecting your data first.

We help homes and small businesses across Southern California and the Coachella Valley, in person or by remote support, and we'll always tell you honestly whether it's a five-minute driver fix or a sign the machine is wearing out. Bring it in or have us come to you, and we'll get to the bottom of the crashes instead of just restarting and hoping.