Error Medic

PC Blue Screen (BSOD) Troubleshooting Guide: Causes, Fixes & Recovery

Fix PC blue screen errors fast. Learn how to diagnose BSOD causes like memory, drivers, and kernel failures with step-by-step commands and recovery tools.

Last updated:
Last verified:
2,080 words
Key Takeaways
  • Most BSODs are caused by faulty or outdated drivers, bad RAM, corrupted system files, or overheating hardware — especially during gaming sessions.
  • Common stop codes include KERNEL_SECURITY_CHECK_FAILURE, MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, and PAGE_FAULT_IN_NONPAGED_AREA.
  • Quick fix summary: Boot into Safe Mode, run 'sfc /scannow' and 'chkdsk', update or roll back drivers, test RAM with Windows Memory Diagnostic or MemTest86, and check Event Viewer for crash logs.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Update/Roll Back DriversAfter installing new hardware or software updates5–15 minLow
Run SFC & DISMCorrupted Windows system files suspected15–45 minLow
Windows Memory Diagnostic / MemTest86MEMORY_MANAGEMENT or random BSODs30 min – 8 hrsNone
Check Disk (chkdsk)BSODs after startup or during boot15–60 minLow
Boot into Safe ModePC won't boot normally after BSOD5 minNone
System RestoreBSOD started after recent change20–40 minMedium
Reset / Reinstall WindowsAll other fixes failed, persistent BSOD1–3 hrsHigh (data loss possible)
Replace RAM/SSD/GPUHardware diagnostics confirm component failure30–60 minMedium

Understanding the PC Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD), formally called a Stop Error, is a critical Windows failure that causes the operating system to halt to prevent further damage. When a BSOD occurs, Windows displays a blue screen with a stop code and a brief message such as:

  • KERNEL_SECURITY_CHECK_FAILURE
  • MEMORY_MANAGEMENT
  • CRITICAL_PROCESS_DIED
  • PAGE_FAULT_IN_NONPAGED_AREA
  • IRQL_NOT_LESS_OR_EQUAL
  • SYSTEM_SERVICE_EXCEPTION
  • WHEA_UNCORRECTABLE_ERROR

The error is written to a memory dump file (typically located at C:\Windows\Minidump\) that can be analyzed post-crash.


Why Does My PC Blue Screen?

BSODs can be triggered by:

  1. Faulty or incompatible drivers — The #1 cause, especially GPU drivers on gaming PCs.
  2. Corrupted Windows system files — Often after failed updates or malware.
  3. Bad or failing RAM — Causes random BSODs and MEMORY_MANAGEMENT errors.
  4. Overheating — GPUs and CPUs throttle and crash under load, common when gaming.
  5. Failing storage (HDD/SSD) — Triggers BSODs at startup or during file access.
  6. Incompatible software or antivirus — Third-party kernel-level software can conflict.
  7. Overclock instability — Unstable OC settings on gaming/CyberPower PCs cause crashes.
  8. Corrupted Windows Update — Broken update packages trigger CRITICAL_PROCESS_DIED.

Step 1: Record the Stop Code and Boot into Safe Mode

When your PC blue screens, photograph the error screen or note the stop code displayed. If your PC won't boot normally:

  1. Force-restart your PC three times in a row to trigger the Windows Recovery Environment (WinRE).
  2. Go to Troubleshoot > Advanced Options > Startup Settings > Restart.
  3. Press F4 for Safe Mode or F5 for Safe Mode with Networking.

In Safe Mode, Windows loads only essential drivers, making it easier to isolate the cause.


Step 2: Read the Crash Dump with WinDbg or Event Viewer

Open Event Viewer (run eventvwr.msc) and navigate to: Windows Logs > System

Filter for Critical and Error events around the time of the crash. Look for source entries like BugCheck or Kernel-Power.

For deeper analysis, install WinDbg Preview from the Microsoft Store and open the dump file:

  1. Launch WinDbg, go to File > Open Crash Dump.
  2. Navigate to C:\Windows\Minidump\ and open the latest .dmp file.
  3. Type !analyze -v in the command window and press Enter.
  4. Review the MODULE_NAME and FAULTING_MODULE fields to identify the guilty driver or process.

Step 3: Run System File Checker and DISM

Corrupted Windows files are a common BSOD trigger. Open Command Prompt as Administrator and run:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Restart after both complete. SFC will repair any corrupted system files it finds. DISM reaches out to Windows Update servers to download clean replacement files.


Step 4: Test Your RAM

For MEMORY_MANAGEMENT or random BSODs, test your RAM:

Windows Memory Diagnostic (quick):

  1. Press Win + R, type mdsched.exe, press Enter.
  2. Select Restart now and check for problems.
  3. Review results in Event Viewer after reboot under Windows Logs > System, source: MemoryDiagnostics-Results.

MemTest86 (thorough): Download from memtest86.com, create a bootable USB, and run at least two full passes (4–8 hours). Any errors indicate faulty RAM that must be replaced.

If you have multiple RAM sticks, try running with one stick at a time to isolate the bad module.


Step 5: Check Storage Health

A failing drive causes BSODs at startup or during file-heavy operations:

chkdsk C: /f /r /x

This schedules a disk check on next reboot. Also check S.M.A.R.T. data using CrystalDiskInfo (free) — look for "Caution" or "Bad" status on Reallocated Sectors or Pending Sectors.


Step 6: Update or Roll Back Drivers

For gaming PCs and GPU-related BSODs (common with NVIDIA/AMD):

  1. Open Device Manager (devmgmt.msc).
  2. Expand Display Adapters, right-click your GPU.
  3. Select Update driver or Properties > Driver > Roll Back Driver.

For NVIDIA GPUs, use DDU (Display Driver Uninstaller) in Safe Mode to completely remove old drivers before installing a clean version from nvidia.com.


Step 7: Check Temperatures and Disable Overclocking

Install HWMonitor or MSI Afterburner to monitor temperatures during gameplay:

  • CPU should stay below 90°C under load.
  • GPU should stay below 85°C under load.

If overheating is detected:

  • Clean dust from fans and heatsinks.
  • Reapply thermal paste if the CPU is over 2 years old.
  • Ensure case airflow is adequate.

For CyberPower PCs or any pre-built with factory overclocks, reset XMP/EXPO RAM profiles to stock in BIOS if BSODs occur with MEMORY_MANAGEMENT.


Step 8: Handle "PC Blue Screen and Won't Boot" Scenarios

If the PC loops on BSOD and can't reach the desktop:

  1. Enter WinRE via three forced restarts.
  2. Try System Restore (Troubleshoot > Advanced Options > System Restore) to revert to a point before the issue started.
  3. Use Startup Repair from WinRE.
  4. If you see There was a problem resetting your PC blue screen, this indicates the recovery partition is corrupted. You will need a Windows 11/10 USB installation media to perform a repair install.

Create Windows installation media: Download the Media Creation Tool from microsoft.com and create a bootable USB. Boot from it, choose Repair your computer > Troubleshoot > Startup Repair before resorting to a full reinstall.


Step 9: Xbox Game Pass and App-Specific BSODs

Xbox Game Pass PC titles can cause BSODs due to the Xbox app's kernel-level components or anti-cheat integrations. Fix steps:

  1. Open PowerShell as Administrator and run: Get-AppxPackage *Xbox* | Remove-AppxPackage
  2. Reinstall Xbox app from the Microsoft Store.
  3. Ensure Windows is fully updated (winver should show build 19041+).
  4. Check if the game uses kernel anti-cheat (like Easy Anti-Cheat) and verify it's properly installed.

Step 10: Factory Reset as Last Resort

If all else fails and BSODs persist:

  1. Go to Settings > System > Recovery > Reset this PC.
  2. Choose Keep my files first to preserve personal data.
  3. If you see There was a problem resetting your PC, use Windows installation media for a clean install.

Always back up critical data before resetting.

Frequently Asked Questions

bash
# ============================================================
# PC BLUE SCREEN DIAGNOSTIC & FIX COMMANDS
# Run Command Prompt or PowerShell as Administrator
# ============================================================

# --- 1. Check system uptime and last boot (helpful context) ---
systeminfo | findstr /C:"Boot Time"

# --- 2. View recent critical errors in Event Log ---
Get-EventLog -LogName System -EntryType Error,Warning -Newest 50 | Format-Table TimeGenerated, Source, Message -AutoSize

# --- 3. List all minidump files (crash dumps) ---
dir C:\Windows\Minidump\

# --- 4. Scan and repair corrupted Windows system files ---
sfc /scannow

# --- 5. Restore Windows image health (run after SFC) ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- 6. Schedule disk check on next reboot ---
chkdsk C: /f /r /x
# Type Y to confirm, then restart

# --- 7. Launch Windows Memory Diagnostic ---
mdsched.exe

# --- 8. Check RAM details via WMIC ---
wmic memorychip get BankLabel, Capacity, Speed, Manufacturer

# --- 9. View installed drivers (sorted by date, newest first) ---
driverquery /v /fo csv | ConvertFrom-Csv | Sort-Object "Driver Date" -Descending | Select-Object -First 20 | Format-Table "Module Name", "Driver Date", "Inf Name"

# --- 10. Check GPU driver version ---
wmic path win32_VideoController get Name, DriverVersion, Status

# --- 11. Check temperatures via PowerShell (basic CPU temp) ---
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace root/wmi | Select-Object -ExpandProperty CurrentTemperature | ForEach-Object { ($_ - 2732) / 10 }

# --- 12. Check SMART disk health ---
wmic diskdrive get Status, Model, SerialNumber

# --- 13. View recent BugCheck (BSOD) event details ---
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} | Select-Object -First 10 | Format-List TimeCreated, Message

# --- 14. Roll back a specific driver (example: GPU) ---
# In Device Manager: devmgmt.msc
# Right-click GPU > Properties > Driver tab > Roll Back Driver

# --- 15. Reset Windows Update components if BSODs follow updates ---
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

# --- 16. Enable automatic memory dump for future BSOD analysis ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 3 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 1 /f

# --- 17. Open Windows Reliability Monitor for crash history ---
perfmon /rel

# ============================================================
# After running diagnostics, restart and monitor for recurrence
# ============================================================
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing critical system failures, kernel panics, and BSODs across enterprise and consumer environments. We translate complex crash analysis into clear, actionable fixes for everyday users and IT professionals alike.

Sources

Related Articles in Other Pc Blue Screen

Explore More windows Guides