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

Understanding the PC Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD) is Windows' last-resort safety mechanism. When the OS kernel detects a fatal, unrecoverable error — such as a hardware failure, driver corruption, or memory fault — it halts all processes and displays a blue screen with a stop code. On Windows 10 and 11, you'll see a message like:

Your PC ran into a problem and needs to restart.
Stop code: MEMORY_MANAGEMENT

Common stop codes include:

• KERNEL_SECURITY_CHECK_FAILURE — A data structure integrity violation, often from a buggy driver or malware.
• MEMORY_MANAGEMENT — RAM errors, faulty memory modules, or driver conflicts.
• IRQL_NOT_LESS_OR_EQUAL — A driver accessed an invalid memory address.
• PAGE_FAULT_IN_NONPAGED_AREA — Memory referencing error, often RAM or SSD-related.
• SYSTEM_SERVICE_EXCEPTION — A system service triggered an exception, frequently GPU or antivirus drivers.
• WHEA_UNCORRECTABLE_ERROR — Hardware error, often CPU overheating or overclocking instability.
• CRITICAL_PROCESS_DIED — A critical Windows process terminated unexpectedly.
• VIDEO_TDR_FAILURE — GPU driver crash, very common during gaming.

Step 1: Record the Stop Code and Check Event Viewer

Before doing anything else, note the stop code displayed on the blue screen. If your PC reboots too fast:

1. Go to Settings > System > About > Advanced system settings.
2. Under Startup and Recovery, click Settings.
3. Uncheck Automatically restart under System failure.
4. Set Write debugging information to Small memory dump (256 KB).

Minidumps are saved to C:\Windows\Minidump\. Use WinDbg Preview (available in the Microsoft Store) to analyze them. Open Event Viewer (eventvwr.msc) and navigate to Windows Logs > System, filtering for Critical and Error events around the crash time.

Step 2: Boot into Safe Mode

If your PC blue screens after startup or won't boot normally:

1. Interrupt the boot process three times by holding the power button during startup. Windows will enter Automatic Repair mode.
2. Navigate to Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
3. Press 4 to boot into Safe Mode or 5 for Safe Mode with Networking.

From Safe Mode, you can uninstall recent drivers or software that may be causing the BSOD.

Step 3: Repair System Files with SFC and DISM

Corrupted Windows system files are a frequent BSOD trigger. Run these commands in an elevated Command Prompt:

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

Restart after completion and test for stability.

Step 4: Update or Roll Back GPU Drivers (Critical for Gaming BSODs)

If your PC blue screens when playing games or while gaming (common on CyberPower PCs, gaming rigs, and Xbox Game Pass sessions), the GPU driver is the #1 suspect.

Using Display Driver Uninstaller (DDU) for a clean reinstall:

1. Boot into Safe Mode.
2. Download DDU from Wagnardsoft.
3. Run DDU and select Clean and restart.
4. After restart, download the latest driver from NVIDIA or AMD and install.

If the BSOD started after a driver update, use Device Manager > Display Adapters > Right-click GPU > Properties > Driver tab > Roll Back Driver.

Step 5: Test RAM with Windows Memory Diagnostic and MemTest86

For MEMORY_MANAGEMENT or random BSODs with no clear pattern:

1. Open Windows Memory Diagnostic (mdsched.exe) and select Restart now and check for problems.
2. For a thorough test, download MemTest86 and run it from a USB drive for at least 2 full passes.

If errors are found, try reseating your RAM modules. If you have multiple sticks, test each one individually to isolate the faulty module.

New PC BSODs are very commonly caused by XMP/EXPO memory profiles in the BIOS. These overclock your RAM beyond JEDEC spec. Enter your BIOS (press Del/F2 on boot) and disable XMP or EXPO to run RAM at stock speed. If stability returns, your RAM may not support the XMP profile reliably.

Step 6: Check Temperatures and Power Delivery

For gaming PC blue screens under load:

1. Install HWiNFO64 or HWMonitor to monitor CPU and GPU temperatures.
   • CPU should stay below 90°C under load; GPU below 85°C.
   • If temperatures spike before the BSOD, clean dust from heatsinks and reapply thermal paste.
2. A weak or failing PSU (Power Supply Unit) can cause BSODs under gaming load. Check that your PSU wattage meets your GPU's requirement (e.g., RTX 4080 recommends an 800W PSU).
3. Check BIOS for CPU/GPU power limit warnings or voltages out of spec.

Step 7: Fix 'PC Blue Screen and Then Won't Boot'

If Windows is stuck in a BSOD restart loop:

1. Boot from a Windows 11/10 installation USB.
2. Select Repair your computer > Troubleshoot > Startup Repair.
3. If Startup Repair fails, try:
   • System Restore (if restore points exist)
   • Command Prompt and run: bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd

Step 8: Address 'There Was a Problem Resetting Your PC' BSOD

This error appears during a Windows Reset and often indicates:

• A corrupted Windows Recovery Environment (WinRE).
• A damaged system partition.

Fix via installation media:

1. Boot from Windows USB.
2. Open Command Prompt and run: reagentc /enable
3. Retry the reset. If it fails again, perform a clean Windows install.

Step 9: KERNEL_SECURITY_CHECK_FAILURE Specific Fixes

This stop code often points to:

• Incompatible or outdated drivers (especially older antivirus, VPN, or virtualization drivers).
• Memory integrity issues (RAM errors or overclocking).
• Malware corrupting kernel structures.

Fixes:

1. Disable Memory Integrity in Windows Security > Device Security > Core Isolation temporarily to identify conflicting drivers.
2. Run verifier.exe (Driver Verifier) to stress-test drivers and identify the offender — only do this on a secondary test session as it can trigger more BSODs.
3. Run a full malware scan with Windows Defender or Malwarebytes.
4. Check C:\Windows\Minidump files in WinDbg for the specific module that failed.

Step 10: Kernel Security Check Failure via Driver Verifier

If you want to pinpoint the exact faulty driver:

verifier /standard /all

Restart and reproduce the crash. Analyze the resulting minidump in WinDbg with !analyze -v. To disable Driver Verifier afterward:

verifier /reset