Windows blue screen: what to do? Causes and solutions

The blue screen of death (BSOD, short for Blue Screen of Death) has a bad reputation, but it isn't a death sentence. In most cases it's a repairable symptom — and often without losing anything. Here's how to understand what's going on and what to do, in order.

What a blue screen means (and doesn't mean)

A blue screen is Windows running into an error so serious that it would rather stop dead than risk damaging your data. It's actually a mechanism of protection, not a terminal failure.

An isolated blue screen, one that happens only once and doesn't come back, is nothing to worry about: a driver had a hiccup, Windows restarted, and that's the end of it. What deserves attention is a blue screen that keeps coming back — every hour, at every start-up, or the moment you launch a certain application.

The number-one reflex: note down the error code

Before you panic, look at the screen. Windows almost always shows a stop code (stop code) at the bottom: for example CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL or VIDEO_TDR_FAILURE. Note it down (or take a photo of it with your phone).

This code is the key to the diagnosis: it points straight to the cause. A code containing ‘MEMORY’ often points to the RAM, a code with ‘VIDEO’ or ‘DXGMMS’ to the graphics card or its driver, a code with ‘DISK’ or ‘NTFS’ to the disk.

The 6 most common causes

• A faulty or badly updated driver — the number-one cause, by far. Often the graphics card, sometimes the Wi-Fi or a printer.
• A recent Windows update that went wrong or clashes with an old driver.
• The RAM (memory): a stick that's wearing out, poorly seated, or incompatible after being added.
• The disk: a mechanical hard drive nearing the end of its life, bad sectors, or an SSD whose firmware urgently needs updating.
• Overheating: clogged-up fans, dried-out thermal paste. The PC protects itself by shutting down, sometimes via a blue screen.
• Intrusive software: an aggressive third-party antivirus, a ‘cleaning’ tool, or malware that meddles with the system.

Solutions, from the simplest to the most technical

Work through them in order. Most blue screens are sorted out within the first two or three steps.

1. Restart, then watch. If the blue screen doesn't come back, it was an isolated incident. Don't touch anything.

2. Undo the last change. Did the blue screen appear after installing a piece of software, a driver, a device, or after an update? Uninstall it, or use System Restore to go back to an earlier point. It's risk-free for your personal files.

3. Update (or reinstall) the suspect driver. Above all the graphics card one: uninstall it cleanly, then reinstall the latest stable version from the manufacturer's website (NVIDIA, AMD, Intel) — not a beta version.

4. Test the memory. Type ‘Windows Memory Diagnostic’ into the Start menu and run the test on restart. If it finds errors, a RAM stick needs reseating or replacing.

5. Check the disk and the system files. In a command prompt run as administrator: sfc /scannow (repairs Windows files) then chkdsk /f (checks the disk). If the disk keeps throwing up errors, back up your data immediately: it may be on its way out.

6. Deal with the overheating. If the blue screens mostly happen while gaming, on video calls or in hot weather, the PC is running too hot: dusting out the fans and replacing the thermal paste often sorts the problem out.

Blue screen on a loop: the PC won't start any more

A more stressful case: the PC shows a blue screen, restarts, shows a blue screen again… on a loop, without ever reaching the desktop. Windows normally ends up offering a recovery environment (a light-blue screen with options).

From there, try in order: Startup Repair, then System Restore, then starting in safe mode (which loads Windows with the bare minimum of drivers — if it boots, a driver is the culprit).

When to call a professional

Get help if: the blue screens persist despite the steps above, the PC no longer starts at all, the error code points to the disk (a risk to your data), or you're simply not comfortable working with system commands. A clean diagnosis is better than a hasty reinstall that wipes everything.