The Blue Screen of Death has been a fixture of Windows for thirty years, and the name does it dirty. A BSOD doesn’t mean your computer is dead. It means Windows ran into something it couldn’t recover from and shut itself down to protect your data and hardware.

That’s actually a feature, not a bug. The frustrating part is figuring out what caused it. Here’s how we approach it at the shop.

Read the screen before it disappears

Modern BSODs (Windows 10 and 11) show a sad face, a short error message, and a stop code at the bottom. Take a phone photo of it before the machine restarts. The stop code is the most useful piece of information you can give us — or feed into a search engine.

Some common ones we see weekly:

• CRITICAL_PROCESS_DIED — usually corrupted system files or a failing drive.
• MEMORY_MANAGEMENT — almost always RAM-related, sometimes a driver issue.
• PAGE_FAULT_IN_NONPAGED_AREA — RAM, driver, or storage.
• IRQL_NOT_LESS_OR_EQUAL — driver problem, often after a Windows update.
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — usually a specific driver, often graphics-related.
• WHEA_UNCORRECTABLE_ERROR — hardware-level fault, usually CPU, RAM, or motherboard.
• INACCESSIBLE_BOOT_DEVICE — your storage drive is failing or has come loose.

How often is it happening?

One blue screen out of nowhere is not a crisis. Windows occasionally hiccups, especially right after an update. If it happens once and never again, you can probably ignore it.

If it’s happening multiple times a week, every time you launch a specific program, or in a regular pattern (always when waking from sleep, always when plugging in a particular USB device), that’s a real problem and worth diagnosing.

Things to try yourself

Before bringing it to us, here’s the no-cost checklist:

1. Run Windows Update. Sometimes the fix is already published.
2. Restart and let it sit at the desktop for a few minutes. Windows runs background repair tasks after a crash and may fix itself.
3. Open Event Viewer (search for it in the Start menu) and look under Windows Logs → System for “Critical” entries around the time of the crash. The detail there can be more specific than the BSOD itself.
4. Run the built-in memory test: search “Windows Memory Diagnostic” and let it reboot and test your RAM. Takes about 15 minutes.
5. Check disk health: open a Command Prompt as administrator and run chkdsk /f. It’ll schedule a check on next boot.
6. Roll back recent changes. If the BSODs started after installing new software or a hardware driver, uninstall it.

When the pattern points to hardware

If you’re getting different stop codes randomly, or the same one repeatedly across totally unrelated activities, hardware is usually the culprit. The two most common we see:

Failing RAM. A bad stick of memory will cause apparently random crashes that look unrelated. Memory tests catch most of these. Reseating the RAM (taking it out and putting it back in) sometimes solves it for free.

Failing storage. Old hard drives and even some SSDs throw blue screens when they can’t read sectors fast enough. SMART data tells the story, and we run it on every machine that comes in for crash issues. If your drive is failing, the most important step is backing up your data before it gets worse.

Don’t ignore a pattern

BSODs that get more frequent over time almost always mean a hardware component is in the early stages of failure. Catching it now — while the drive can still be cloned, the RAM can be tested, and the data can still be pulled — saves you a much bigger headache later.

Bring It By

If your machine is blue-screening more than occasionally, walk it in to our 9th Street shop and we’ll diagnose it (usually within 24 hours of check-in). We don’t charge to tell you it’s not worth fixing, and we’ll always show you what we found. Open Monday through Friday, 10AM to 6PM. Call (919) 314-3327 with questions.