Windows 11 Blue Screen: How to Read the Stop Code and Find the Cause

What a blue screen actually is

A blue screen, officially a stop error, appears when Windows detects a problem it cannot safely recover from, so it halts the system to prevent damage or data loss. The cause may be a driver, memory, storage, overheating, corrupted system files, or a recent update. The screen is a symptom, not a diagnosis.

One blue screen is not a reason to reinstall Windows. A single crash can be a one-off. Repeated crashes, especially with the same code, are worth investigating.

Step 1: write down what the screen says

Modern Windows shows a short message, a QR code, a percentage, and a stop code in capital letters. Some screens also show a line beginning "What failed" followed by a file name that ends in .sys. Photograph the screen with your phone before it restarts.

If the PC restarts too fast to read, turn off automatic restart. Open Settings, go to System, About, Advanced system settings, then under Startup and Recovery choose Settings and clear Automatically restart.

• The stop code, for example MEMORY_MANAGEMENT or CRITICAL_PROCESS_DIED.
• The "what failed" file name, if one is shown.
• What you were doing: gaming, waking from sleep, installing something, or nothing at all.
• Whether it happens every time, at random, or only under heavy load.

Step 2: what common stop codes usually point to

A stop code narrows the field but does not name the culprit. Treat the table as a starting point for where to look first.

Step 3: find the crash record

Windows keeps a record of each crash, which gives you more detail than the screen did. The easiest place to look is Reliability Monitor: press Windows + R, type perfmon /rel, and press Enter. Critical events list the crash time and sometimes the cause.

You can also open Event Viewer, go to Windows Logs, then System, and look for a BugCheck event. If small memory dumps are enabled, Windows saves them in C:\Windows\Minidump. A free tool such as WinDbg from Microsoft can open a dump, and a third-party viewer such as BlueScreenView offers a simpler summary.

• The same driver file named in several crashes is a strong clue.
• Different codes and different files each time often point to hardware, especially memory, power, or heat.
• Treat a driver named in a dump as a suspect, not a proven culprit. A driver can be the victim of a fault elsewhere.

Step 4: work from the cheapest test to the most invasive

Start with the least disruptive checks. Each step is easy to undo, and a fix at an early step saves you from changing things you did not need to.

1. Undo the most recent change. If crashes began after a driver, update, or new program, roll it back or uninstall it. Use Device Manager, Driver, Roll Back Driver, or Settings, Windows Update, Update history, Uninstall updates.
2. Disconnect non-essential devices such as extra USB hardware, then test again.
3. Repair system files. Open Terminal as administrator and run sfc /scannow. If it reports problems it cannot fix, run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow again.
4. Check the drive for errors and review its health with the SSD health guide.
5. Test the memory with Windows Memory Diagnostic or MemTest86, following the RAM testing guide.
6. Watch temperatures under load and make sure fans and vents are clear. Remove any overclock or memory profile and test at default settings.
7. Update the graphics, chipset, and storage drivers from the manufacturer or Windows Update.

If you cannot start Windows

If the PC blue screens before you can reach the desktop, Windows normally offers recovery options after a few failed starts. From there choose Troubleshoot, Advanced options, and try Startup Settings to boot into Safe Mode, or use System Restore if a restore point exists. In Safe Mode you can uninstall a recent driver or update.

If nothing in the recovery options helps, back up your files from a recovery environment or another computer before considering a reset or reinstall.

When to suspect hardware

Hardware moves up the list when crashes are random, the stop codes change, the crash dumps name no consistent driver, and software steps have made no difference. Memory is the most common hardware cause, followed by storage, overheating, and an unstable power supply.

If a memory test passes, the drive is healthy, and temperatures are normal, a failing power supply or motherboard becomes more likely. Those are harder to confirm without swapping parts, so this is the point to get a technician to test them.