How to Fix Blue Screen Error (BSOD) on Windows 10 and 11 — Complete Guide

A blue screen error — officially a Stop Error, universally known as the Blue Screen of Death — is Windows' way of telling you something has gone wrong at a level the operating system cannot safely recover from. It halts everything, dumps diagnostic information, and restarts, which is either responsible behavior from a cautious operating system or a deeply inconvenient way to spend a Tuesday afternoon, depending on your perspective. The good news is that most blue screen errors are fixable without replacing hardware, reinstalling Windows, or surrendering your computer to a repair shop. This guide walks through every major cause, the step-by-step fixes in the order you should try them, and how to tell when the problem is actually hardware — because running software fixes on a failing RAM stick is a reliable way to accomplish nothing at length.

What a blue screen error actually means

When Windows encounters a critical failure — a driver writing to the wrong memory address, a hardware component returning corrupted data, a kernel process crashing — it immediately halts the operating system rather than allowing the damage to spread. The blue (or occasionally black on Windows 11) screen displays a stop code that identifies the failure category, then collects a memory dump file for diagnostics before restarting.

The stop code is the most useful piece of information on the screen. Write it down, photograph it, or find it in Event Viewer after the fact. Every fix in this guide starts from the stop code or the circumstances of the crash, because "blue screen" alone could mean a dozen different problems with different solutions.

Common BSOD stop codes and what they mean

Step 1: Try the simple fixes first

Step 2: Boot into Safe Mode

If Windows will not boot normally, or if you want a clean diagnostic environment, Safe Mode loads only essential drivers and services — which means if the BSOD stops in Safe Mode, the cause is almost certainly a driver or startup application, not hardware.

To enter Safe Mode when Windows boots normally: Go to Settings > System > Recovery > Advanced startup > Restart now. Then select Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 or F4 for Safe Mode.

If Windows will not boot: Interrupt the startup process three times by holding the power button as Windows begins to load. On the third attempt, Windows enters the Automatic Repair screen automatically. Select Advanced Options > Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 or F4.

Step 3: Update or roll back drivers

Faulty or incompatible device drivers are the single most common cause of BSODs. This step covers both directions — sometimes the fix is updating an outdated driver, and sometimes it is rolling back a driver that was updated right before the crashes started.

Step 4: Run System File Checker (SFC)

Corrupted Windows system files are a common BSOD cause, particularly after incomplete updates, power cuts during file operations, or malware. SFC scans all protected system files and repairs any that are corrupted or missing.

Open Command Prompt as Administrator (search for cmd, right-click, select Run as administrator) and run:

The scan takes 10–20 minutes. If it finds and repairs corrupted files, restart and test. If SFC reports that it found corrupted files but could not repair all of them, follow up with DISM.

Step 5: Run DISM to repair the Windows image

DISM (Deployment Image Servicing and Management) repairs the Windows component store that SFC draws from. If SFC failed to fix everything, DISM often can. Run these three commands in sequence in an Administrator Command Prompt:

The RestoreHealth command downloads replacement files from Windows Update, so you need an internet connection. It can take 20–30 minutes. Restart after it completes, then run sfc /scannow again to catch anything DISM's repairs now allow SFC to fix.

Step 6: Test your RAM

Bad RAM is responsible for a significant proportion of BSODs, and it is particularly likely when your stop codes change between crashes — PAGE_FAULT_IN_NONPAGED_AREA one day, MEMORY_MANAGEMENT the next — because corrupted memory contents end up in different places each time.

Press Windows + R, type mdsched.exe, and press Enter. Select Restart now and check for problems. Windows restarts and runs a memory diagnostic before loading. Results are shown after Windows restarts. If errors are found, you likely have a faulty RAM stick. To identify which one, remove all but one stick and test — then swap in the other sticks one at a time.

Step 7: Check your hard drive or SSD for errors

A failing storage drive — developing bad sectors on a hard drive, or NAND degradation on an SSD — can cause BSODs by returning corrupted data when Windows reads critical files. Open Command Prompt as Administrator and run:

You will be prompted to schedule the check for the next restart (type Y then restart). The check can take anywhere from 20 minutes to several hours depending on drive size and condition. If it reports bad sectors or cannot complete, the drive is failing and needs to be replaced before data loss occurs. This is one of those situations where the comfortable conclusion is rarely the correct one.

Step 8: Check for overheating

BSODs that occur consistently under load — gaming, video rendering, running multiple applications — and not during light use often indicate thermal throttling or component failure due to heat. Download a free temperature monitoring tool such as HWMonitor or Core Temp. CPU temperature should stay under 90°C under full load; GPU under 85°C. Sustained temperatures above these thresholds cause BSODs and, eventually, hardware damage.

If temperatures are high: clean dust from vents and fans (compressed air, not a vacuum), ensure adequate airflow around the machine, and check that all fans are spinning. On a laptop, overheating BSODs often indicate the thermal paste between the CPU and heatsink has dried out and needs replacing — a task that is straightforward for a technician but invasive enough that most users prefer professional help.

Step 9: Use System Restore

If BSODs started after a specific change — a software installation, a driver update, a Windows feature update — System Restore can revert your system to a point before that change without affecting your personal files.

Search for "Create a restore point" in the Start menu and click System Restore. Select a restore point dated before the crashes started. Windows will show what programs and drivers will be affected. Confirm and let the restore complete — the process takes about 15 minutes and the system restarts.

Step 10: Reset or reinstall Windows

If none of the above has resolved the issue and Safe Mode testing suggests a software rather than hardware cause, a Windows Reset is the nuclear option for software-based BSODs. Go to Settings > System > Recovery > Reset this PC. Choose Keep my files to preserve personal data while reinstalling Windows — this option removes all apps and settings but leaves your documents, photos, and downloads intact.

A reset fixes BSODs caused by corrupted system files, conflicting software, or bad updates. It does not fix hardware problems — a system reset on a computer with failing RAM will be followed by another BSOD as soon as the RAM fault triggers again.

When to call a professional

Most software-caused BSODs are resolvable with the steps above. The situations that warrant professional diagnosis are: crashes that continue in Safe Mode after driver and system file repairs, Memory Diagnostic errors indicating faulty RAM, chkdsk results showing bad sectors on a drive, BSODs that persist after a clean Windows reinstall, and any situation where the crashes are accompanied by unusual sounds from the PC (clicking drives, grinding fans) or visual artifacts on screen.

Remote computer support handles the majority of BSOD cases without requiring you to bring your computer anywhere — a technician can access your system, review Event Viewer and minidump files, run diagnostics, and fix driver and system file issues in a single session. If you are in New Jersey, New York, California, Texas, or Florida, our remote computer support service covers exactly this kind of diagnosis and repair. For ongoing maintenance that prevents these issues from developing in the first place, our maintenance support plan includes regular driver updates, disk health monitoring, and system health checks.