Windows 11 Blue Screen: How to Read the Error Code and Fix the Cause

A blue screen on Windows 11 is a protective measure: Windows stops on purpose because it detected an error it cannot safely fix without risking your files. In most cases the cause is a faulty driver, a damaged system file or failing memory, and it can be fixed without replacing the computer.

The scenario is always the same: everything works, then the screen turns blue with a sad face, a cryptic error code, and the computer restarts. The worst part is the uncertainty: is it a one-off accident or the start of a breakdown? Depending on your Windows 11 version, the screen may even appear black rather than blue: it is the same mechanism.

1. Did it happen only once? An isolated blue screen is nothing alarming: restart, let Windows update and keep an eye on it.
2. Did it happen right after an update, or after installing a driver or program? Then the cause is almost certain: undo that change.
3. Does it keep happening, even with nothing new? Note the error code and follow the method below: the cause is probably hardware (memory, disk, heat).

When the core of Windows hits a situation it cannot handle, for instance a driver writing to the wrong place in memory, it prefers to stop everything rather than risk damaging your data. It then shows a stop code in capital letters and restarts. That code is your best lead: it points to the family of cause.

• DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, KERNEL_SECURITY_CHECK_FAILURE: a faulty driver or system software. Think about what was installed or updated recently.
• MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA: RAM (a failing module) or a driver misusing it.
• CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, NTFS_FILE_SYSTEM: damaged system files or a struggling disk.
• DPC_WATCHDOG_VIOLATION, CLOCK_WATCHDOG_TIMEOUT: a component stopped responding in time, often a storage or graphics driver.

The code alone is not a diagnosis: the same code can have several origins. But it stops you from going in every direction. If you did not have time to read it, Windows keeps it on record, as we will see below.

On Windows 11, the screen shows a message such as "Your device ran into a problem" with a rising percentage, a QR code and the stop code at the bottom. The restart is automatic, which is handy but sometimes stops you from reading the code. To keep it on screen, open Advanced system settings > Startup and Recovery, then untick "Automatically restart". At the next crash, the screen will stay up and you will have time to note or photograph the code.

The QR code leads to a general Microsoft help page. It is rarely more useful than the stop code itself: that is the one you will search for, adding your computer's model.

1. A faulty or incompatible driver

This is the number one cause. A driver is a small program that lets Windows talk to a component (graphics card, Wi-Fi, storage). A badly written, outdated or wrongly installed driver crashes the whole system. Graphics and network drivers are the most frequent culprits after an update.

2. A Windows update that went wrong

An update can replace a driver without warning or leave files half installed. If blue screens start on the day of an update, uninstalling it (Settings > Windows Update > Update history > Uninstall updates) is the first thing to try.

3. Failing RAM

A memory module that makes errors causes seemingly random blue screens, with a different code each time. That is the classic sign: if the codes change from one crash to the next, think memory. Windows includes a test tool (Windows Memory Diagnostic, launched by typing mdsched in search).

4. Damaged system files

After a power cut, a forced shutdown or a struggling disk, Windows files can be corrupted. Two commands, run in an administrator command prompt, fix them in most cases: sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.

5. A disk reaching the end of its life

A disk that struggles to read its data crashes Windows, especially at startup. If the blue screen appears during boot, or comes with slowdowns and freezes, check the disk's health before anything else. Our guide to the signs of a failing hard drive explains how.

6. Heat

An overheating processor or graphics card can cause crashes, often under load (gaming, video editing, a big update). If the fan races just before the blue screen, the cooling lead is serious: dust, worn thermal paste or blocked airflow.

A word on drivers, the first lead. For the graphics card, download the driver straight from its maker's site (NVIDIA, AMD or Intel) rather than through third-party software. For everything else, Windows Update sometimes offers "optional updates" (Settings > Windows Update > Advanced options) containing newer drivers. Beware of programs promising to update all your drivers in one click: they regularly install the wrong one, and that is a good way to create a blue screen rather than fix one.

If you suspect memory and the computer has several modules, remove one and test with the other, then swap. A faulty module causes the crashes, the other does not. Always switch off and unplug the computer before opening the case, and touch a metal part to discharge static electricity.

1. Note the stop code, by photographing the screen at the next crash, or find it in Event Viewer (Windows Logs > System, event 1001 or 41).
2. Think back to the latest change: update, new driver, new program, new device plugged in. Unplug unnecessary devices (USB stick, printer, external drive).
3. Uninstall the recent update or driver, or use System Restore to go back a few days.
4. Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth to repair system files.
5. Test memory with Windows Memory Diagnostic, then check the disk's health.
6. If the crash prevents booting, use Safe Mode (hold Shift while clicking Restart) to carry out these checks.

Windows also saves a dump file at each crash, in C:\Windows\Minidump. Free tools can read it and often name the faulty driver. It is valuable help when the stop code is too vague.

To avoid living through this again, two habits are worth it. The first is to let Windows create restore points before major updates, which lets you roll back in minutes. The second is to back up your files regularly: a blue screen is rarely dangerous for data, but a failing disk always is.

• A single blue screen, then nothing for weeks: do nothing special, just keep Windows and drivers up to date.
• Several blue screens a week, with different codes: test memory and disk, this is the profile of a hardware problem.
• Blue screens at every startup: back up your files without waiting, the disk may be at fault.
• Resetting Windows (Settings > System > Recovery) is the heaviest solution: it fixes a software problem but changes nothing for a failing memory module or disk.

In almost none of these cases is the computer "fit for the bin": a memory module costs a few tens of euros to replace, so does a disk, and most blue screens come from a driver.

Nyctale reads the Windows log for you: how many sudden shutdowns and crashes occurred over the last 30 days, and whether a disk health warning is flagged. It cross-checks these clues with what is occupying the computer, then names the probable cause. When the problem is hardware, it tells you frankly rather than sending you chasing a useless setting.