How to Fix Blue Screen of Death (BSOD) Errors on Windows
Troubleshooting
6 min readJuly 17, 2026

How to Fix Blue Screen of Death (BSOD) Errors on Windows

A Blue Screen of Death can strike without warning and leave you scrambling for answers. This guide walks you through proven steps to diagnose and permanently fix BSOD errors on Windows 10 and 11.

Share

How to Fix Blue Screen of Death (BSOD) Errors on Windows

Few things are more alarming than watching your screen suddenly turn blue and your PC restart unexpectedly. The **Blue Screen of Death (BSOD)** — officially called a Stop Error — is Windows' way of telling you something has gone seriously wrong at the hardware or driver level. The good news: most BSODs are fixable once you know how to read the clues they leave behind.

In this guide, you'll learn how to identify the root cause of your BSOD, apply targeted fixes, and prevent future crashes — all without needing to reinstall Windows.

---

Free AI Diagnosis

Dealing with this on your own PC?

Describe your problem and get a real AI diagnosis in seconds — no account needed.

What Causes a Blue Screen of Death?

BSODs are triggered when Windows encounters a critical error it cannot safely recover from. Common culprits include:

Faulty or outdated driversespecially graphics, network, or storage drivers

Defective RAMbad memory modules cause random, hard-to-reproduce crashes

Overheating componentsCPUs and GPUs throttle and crash when temperatures spike

Corrupted system filesdamaged Windows files prevent normal operation

Failing hard drives or SSDsstorage errors can destabilize the entire OS

Incompatible software or recent Windows updatesnew installs can conflict with existing drivers

Every BSOD displays a **stop code** (e.g., MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, CRITICAL_PROCESS_DIED). This code is your most important diagnostic clue.

---

Step 1: Record the Stop Code

When a BSOD occurs, Windows displays a stop code on the blue screen. If the restart happens too fast to read it, you can find it in the event log:

1

Press `Win + X` and select **Event Viewer**

2

Navigate to **Windows Logs → System**

3

Filter for **Critical** and **Error** events around the time of the crash

4

Look for entries from source `BugCheck` — these contain the stop code

Alternatively, open **PowerShell** as Administrator and run:

```powershell

Get-EventLog -LogName System -EntryType Error -Newest 20 | Where-Object {$_.Source -eq "BugCheck"}

```

Note the stop code before proceeding — it determines which fix to apply.

---

Step 2: Update or Roll Back Drivers

Outdated or corrupt drivers are the #1 cause of BSODs. Start here:

Update Drivers

1

Press `Win + X` → **Device Manager**

2

Expand each category and look for devices with a **yellow warning icon**

3

Right-click the flagged device → **Update driver → Search automatically**

For graphics drivers, always download directly from **NVIDIA**, **AMD**, or **Intel** rather than relying on Windows Update.

Roll Back a Recent Driver

If the BSOD started after a driver update:

1

In **Device Manager**, right-click the device → **Properties**

2

Go to the **Driver** tab → click **Roll Back Driver**

This reverts to the previously installed version, which is often more stable.

---

Step 3: Run Windows Memory Diagnostic

Faulty RAM is a silent BSOD trigger. Test your memory with the built-in tool:

1

Press `Win + R`, type `mdsched.exe`, press Enter

2

Choose **Restart now and check for problems**

3

Windows will reboot and run a full memory test — this takes 10–20 minutes

4

Results appear after the next login in the **Event Viewer** under **Windows Logs → System** (source: `MemoryDiagnostics-Results`)

If errors are found, try reseating your RAM sticks. If errors persist, the module likely needs replacement.

---

Step 4: Repair Corrupted System Files

Corrupted Windows system files can cause a variety of stop codes. Run these two commands in an **elevated Command Prompt** (cmd as Administrator):

```cmd

sfc /scannow

```

This scans and repairs protected system files. After it completes, run:

```cmd

DISM /Online /Cleanup-Image /RestoreHealth

```

**DISM** (Deployment Image Servicing and Management) repairs the Windows image itself, which sfc relies on. Restart your PC after both commands finish.

---

Step 5: Check Your Hard Drive or SSD Health

Storage failures can cause BSODs with codes like NTFS_FILE_SYSTEM or PAGE_FAULT_IN_NONPAGED_AREA. Check drive health with:

```cmd

chkdsk C: /f /r /x

```

This schedules a disk check on the next reboot (the /r flag scans for bad sectors). For SSDs, also check the manufacturer's health tool (Samsung Magician, Crucial Storage Executive, etc.) for wear indicators and reallocated sector counts.

---

Step 6: Check for Overheating

Thermal throttling and shutdown are common on laptops and desktops with clogged vents or dried-out thermal paste. Signs of overheating include BSODs during heavy workloads (gaming, video rendering) but not during idle use.

Use **HWMonitor** or **Core Temp** to watch CPU and GPU temperatures under load

Safe CPU temps: below **85°C** under full load

If temps exceed this, clean dust from vents and heatsinks, or reapply thermal paste

**PC Diagnostic Analyzer** can surface temperature anomalies and flag components running outside safe ranges — a fast way to confirm whether heat is your culprit without installing multiple third-party tools.

---

Step 7: Uninstall Recent Software or Windows Updates

If your BSOD started after a Windows Update or new software install:

Uninstall a Windows Update

1

Go to **Settings → Windows Update → Update History**

2

Click **Uninstall updates**

3

Sort by **Installed On** and remove the most recent update

Uninstall Recent Software

1

Go to **Settings → Apps → Installed apps**

2

Sort by **Install date**

3

Uninstall any app installed around the time BSODs began

---

Step 8: Use Windows Startup Repair

If your PC BSODs during boot and you can't reach the desktop:

1

Boot from a **Windows installation USB**

2

Select **Repair your computer → Troubleshoot → Advanced options → Startup Repair**

3

Let Windows attempt automatic repair

Alternatively, boot into **Safe Mode** (press F8 or Shift + F8 during startup) to isolate whether a third-party driver or service is causing the crash.

---

Preventing Future BSODs

Once you've resolved the immediate crash, keep your system stable with these habits:

Keep drivers updatedespecially after major Windows feature updates

Monitor hardware health regularlydon't wait for a crash to check temperatures and drive health

Avoid beta driversstick to WHQL-certified drivers for daily use

Run periodic memory testsespecially after adding new RAM

Keep Windows updatedsecurity patches often include stability fixes

**PC Diagnostic Analyzer** makes ongoing health monitoring effortless by scanning your system's hardware, drivers, and performance metrics in one click — giving you early warnings before a minor issue becomes a BSOD.

---

Take Action Before the Next Crash

BSODs are stressful, but they're rarely random — there's always an underlying cause. By following the steps above, you can systematically eliminate each potential culprit and restore stability to your Windows PC.

Don't wait for the next blue screen to take action. Run a free diagnostic with **PC Diagnostic Analyzer** today to get a full health report on your system's drivers, memory, storage, and temperatures — and catch problems before they crash your day.

Found this helpful?

Share it with someone who could use it.

Share

DiagnoseMyPC Team

Expert PC diagnostics and troubleshooting guides to help you keep your Windows system running smoothly.

Free Diagnostic Tool

Having PC Issues? Let AI Diagnose Them

Get an AI-powered analysis of your Windows PC in under 5 minutes — no technical knowledge required, no account to get started.