How to Fix the Blue Screen of Death in Windows 11

A blue screen, also called a stop code error, a bug check or a BSOD, happens when Windows hits a problem it can't safely recover from, so it shuts down and restarts to protect itself from data loss. Microsoft says it can be caused by a hardware device, its driver, or related software. Most one-off restarts don't need any action. If the same error keeps coming back, work through the checks below in order.

On Windows 11 version 24H2 and later, the error screen may be black instead of blue. The checks are the same.

1. Write Down the Stop Code

Back to guide

The error screen shows a stop code near the bottom, such as PAGE_FAULT_IN_NONPAGED_AREA, MEMORY_MANAGEMENT or CRITICAL_PROCESS_DIED. When it's available, it also shows the name of the file that was running, often a driver ending in .sys.

1. Take a photo of the screen with your phone, or write the stop code down.
2. Note what you were doing when it happened, and anything you installed or plugged in recently.
3. Search for the stop code and the file name. They often point straight at the device or driver involved.

Expected result: you have the stop code, and possibly a driver name, to guide the rest of the checks.

2. Remove New Hardware and Start in Safe Mode

Back to guide

If the errors started after you added a device, shut down your PC, remove the device and restart. Check with the device maker for updates before you try it again.

If Windows keeps crashing before you can fix anything, start it in safe mode, which loads only the minimum drivers and services. You get there through the Windows Recovery Environment:

1. If you can reach the desktop, select Start > Settings > System > Recovery, and next to Advanced startup select Restart now. On Windows 10, it's Settings > Update & Security > Recovery.
2. If Windows can't start, it opens the recovery environment on its own after it fails to start correctly several times.
3. Select Troubleshoot > Advanced options > Startup Settings > Restart.
4. When the list appears, press 4 or F4 for safe mode, or 5 or F5 for safe mode with networking.

Expected result: Windows starts in safe mode, so you can run the next checks without it crashing.

3. Update, Roll Back or Reinstall Drivers

Back to guide

Microsoft estimates that about three quarters of stop code errors are caused by faulty drivers, so this is the most important check.

1. Right-click Start and select Device Manager.
2. Look for devices marked with an exclamation point (!), and for the device named in your stop code, if there was one.
3. Right-click the device, select Update driver > Search automatically for updated driver software.
4. If the errors started after a driver update, right-click the device, select Properties > Driver > Roll Back Driver, choose a reason and select Yes.
5. If neither helps, select Uninstall device, confirm, and restart. Windows tries to reinstall the driver when it starts.

Expected result: no devices show an exclamation point, and the device linked to your stop code has a working driver.

4. Install Windows Updates, or Remove a Bad One

Back to guide

Select Start > Settings > Windows Update > Check for updates and install what's available. On Windows 10, the path is Settings > Update & Security > Windows Update.

If the blue screens started right after an update, you can remove it instead. In the recovery environment, select Troubleshoot > Advanced options > Uninstall Updates. Microsoft says this removes the update without affecting your files or apps.

Expected result: Windows Update shows you're up to date, or the update that caused the problem is gone.

5. Free Up Disk Space

Back to guide

Windows needs free space to work. Microsoft suggests keeping 10% to 15% of your drive free. Select Start > Settings > System > Storage > Cleanup recommendations, review each category and select Clean up. On Windows 10, search for Disk Cleanup instead.

Expected result: at least 10% of your system drive is free.

6. Repair System Files and Check the Drive

Back to guide

Damaged Windows files and file system errors can both cause stop codes. Search for cmd, right-click Command Prompt and select Run as administrator, then run these one at a time:

1. DISM.exe /Online /Cleanup-image /Restorehealth (this can take several minutes).
2. sfc /scannow, and leave the window open until it reaches 100%.
3. chkdsk C: /f. Because Windows is using drive C, chkdsk asks whether to check it the next time you restart. Type Y and restart.

For what each System File Checker message means, see our guide to repairing system files with System File Checker.

Expected result: SFC reports no integrity violations or says it repaired the files, and chkdsk finishes its check.

7. Test Your Memory

Back to guide

Memory (RAM) errors are one of the hardware problems Microsoft lists as a cause of stop codes. Windows includes a tool to test it.

1. In Control Panel, search for Memory and select Diagnose your computer's memory problems.
2. Save your work, then follow the prompts to run the test.
3. After the test runs, open Event Viewer, go to the System log and look for the MemoryDiagnostics-Results entry.

Expected result: the results report no memory errors. If they do, run your PC maker's hardware diagnostics or contact the maker.

8. Scan for Malware

Back to guide

Malware can damage system files and disks, which can lead to stop codes. Open Windows Security from the Start menu and select Virus & threat protection > Quick scan.

Expected result: the scan finishes with no current threats, or tells you what it found and removed.

9. Use System Restore

Back to guide

System Restore takes Windows back to a restore point from before the problem began, without changing your personal files.

1. From Windows, press Windows logo key + R, type rstrui.exe and press Enter. From the recovery environment, select Troubleshoot > Advanced options > System Restore.
2. Select Next and pick a restore point from before the errors started.
3. Select Scan for affected programs to see what will change, then Next > Finish.

System Restore can only use restore points that already exist. Windows can create them automatically during events such as software installs or updates, and you can make them yourself before big changes. For a step-by-step walkthrough, see how to use a Windows 11 system restore point.

Expected result: Windows restarts at the earlier point and the blue screens stop.

Still Getting Blue Screens? What to Try Next

Back to guide

• Check Event Viewer: look in the System log for critical errors from the same time as the crash. They can name the device or driver.
• Run your PC maker's hardware diagnostics, and ask the maker whether a BIOS or UEFI firmware update is available.
• Check connections: on a desktop PC, make sure cards are seated properly and cables are firmly connected.
• Reset this PC: as a last resort, this reinstalls Windows. You can choose to keep your personal files, but your apps and settings are removed.