Error Medic

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

Fix PC blue screen errors including KERNEL_SECURITY_CHECK_FAILURE & MEMORY_MANAGEMENT. Step-by-step BSOD diagnosis and recovery commands inside.

Last updated:
Last verified:
2,247 words
Key Takeaways
  • Most BSODs are caused by faulty RAM, corrupt drivers, overheating hardware, or incompatible software — especially common on gaming PCs and new builds.
  • Error codes like KERNEL_SECURITY_CHECK_FAILURE and MEMORY_MANAGEMENT point to specific subsystems — reading the stop code is the fastest way to narrow down the fix.
  • Quick fix summary: Boot into Safe Mode, run 'sfc /scannow' and 'chkdsk /f /r', update or roll back drivers, run Windows Memory Diagnostic, and check Event Viewer logs to pinpoint the exact crash cause.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Update/Rollback DriversBSOD after driver update or new hardware install5-15 minLow
Run SFC & DISMCorrupt system files suspected; BSOD after Windows update15-30 minLow
Windows Memory DiagnosticMEMORY_MANAGEMENT or random BSODs during gaming10-20 minLow
Check Disk (chkdsk)BSOD after startup or 'won't boot' after crash20-60 minLow
Uninstall Recent SoftwareBSOD started after installing new app or game (Xbox Game Pass)5-10 minLow
System RestoreBSOD began recently and restore point exists15-30 minMedium
Reset This PC'There was a problem resetting your PC' blue screen1-3 hrsMedium-High
Reseat/Replace RAM or GPUHardware-related BSODs, new PC build, CyberPower PC30-60 minMedium
Reinstall WindowsPersistent BSODs, all software fixes failed1-2 hrsHigh

Understanding the PC Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD) — officially called a Stop Error — occurs when Windows encounters a critical system error it cannot recover from safely. The OS halts all operations to prevent data corruption and displays a blue screen with a stop code. Modern Windows 10/11 BSODs show a sad face emoji, a brief description, and a stop code such as:

  • KERNEL_SECURITY_CHECK_FAILURE
  • MEMORY_MANAGEMENT
  • PAGE_FAULT_IN_NONPAGED_AREA
  • IRQL_NOT_LESS_OR_EQUAL
  • SYSTEM_SERVICE_EXCEPTION
  • CRITICAL_PROCESS_DIED
  • VIDEO_TDR_FAILURE

Each code maps to a specific Windows subsystem, making them invaluable for diagnosis.


Common Scenarios and Their Causes

New PC Blue Screen / CyberPower PC Blue Screen

New builds (including pre-built systems like CyberPower PCs) frequently blue screen due to:

  • RAM not seated properly or running at incorrect XMP/EXPO speeds
  • GPU drivers not installed (system uses generic drivers)
  • Thermal paste not applied correctly, causing overheating
  • Fast Startup causing boot conflicts

PC Blue Screen When Playing Games / While Gaming

Gaming BSODs are almost always caused by:

  • GPU overheating or overclocking instability
  • Faulty or outdated GPU drivers (VIDEO_TDR_FAILURE, SYSTEM_SERVICE_EXCEPTION)
  • Insufficient or faulty RAM (MEMORY_MANAGEMENT)
  • Xbox Game Pass overlay or anti-cheat conflicts

PC Blue Screen After Startup / Won't Boot

  • Corrupt boot sector or MBR
  • Failing hard drive (bad sectors)
  • Windows Update corruption

"There Was a Problem Resetting Your PC" Blue Screen

  • Corrupt Windows installation files
  • USB recovery drive not recognized
  • Damaged system partition

Step-by-Step Troubleshooting

Step 1: Record the Stop Code

When the BSOD appears, note:

  1. The stop code (e.g., MEMORY_MANAGEMENT)
  2. The failed module listed under "What failed:" (e.g., ntoskrnl.exe, nvlddmkm.sys)

If the PC reboots too fast: Open Settings > System > About > Advanced System Settings > Startup and Recovery > Settings, then uncheck Automatically restart.

Step 2: Boot into Safe Mode

If Windows won't load normally:

  1. Force shutdown 3 times to trigger Windows Recovery Environment (WinRE)
  2. Navigate to Troubleshoot > Advanced Options > Startup Settings > Restart
  3. Press 4 for Safe Mode or 5 for Safe Mode with Networking

Step 3: Check Event Viewer

In Safe Mode or after a reboot:

  1. Press Win + X and select Event Viewer
  2. Navigate to Windows Logs > System
  3. Look for Critical or Error events timestamped at the crash time
  4. Note the Source and Event ID for targeted fixes

Step 4: Analyze Minidump Files

Windows saves crash dumps at C:\Windows\Minidump\. Use WinDbg or the free tool WhoCrashed to analyze them:

WinDbg command: !analyze -v

This reveals the exact driver or process that caused the crash.

Step 5: Run System File Checker and DISM

Corrupt system files frequently cause BSODs. Run from an elevated Command Prompt:

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

Restart after completion.

Step 6: Run Windows Memory Diagnostic

For MEMORY_MANAGEMENT or random gaming BSODs:

  1. Press Win + R, type mdsched.exe, press Enter
  2. Choose Restart now and check for problems
  3. For deeper testing, use MemTest86 from a bootable USB (run overnight)

Step 7: Check Disk Health

For BSODs after startup or boot failures:

chkdsk C: /f /r /x

Schedule for next restart if the drive is in use. Also check SMART data:

wmic diskdrive get status

Step 8: Update or Roll Back Drivers

For GPU drivers (most common gaming BSOD cause):

  • Download DDU (Display Driver Uninstaller), boot into Safe Mode, run DDU to fully remove GPU drivers
  • Download the latest driver from NVIDIA or AMD official site and install clean
  • If BSOD started after a driver update, roll back: Device Manager > Display Adapters > right-click GPU > Properties > Driver tab > Roll Back Driver

For all drivers:

pnputil /enum-drivers

Step 9: Disable Fast Startup (New PC / Boot BSODs)

  1. Open Control Panel > Power Options > Choose what the power buttons do
  2. Click Change settings that are currently unavailable
  3. Uncheck Turn on fast startup

Step 10: Fix "There Was a Problem Resetting Your PC"

Boot into WinRE and use the Command Prompt:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

If that fails, boot from a Windows installation USB and choose Repair your computer.

Step 11: Check Temperatures and Hardware

Install HWMonitor or HWiNFO64 to monitor:

  • CPU temperature (should stay under 90°C under load)
  • GPU temperature (under 85°C)
  • RAM temperatures

For CyberPower PCs and new builds, physically reseat RAM sticks — remove them and firmly reinsert, one stick at a time to identify a faulty module.

Step 12: Xbox Game Pass / UWP App BSODs

Xbox Game Pass games have triggered SYSTEM_SERVICE_EXCEPTION and KERNEL_SECURITY_CHECK_FAILURE errors due to:

  • Conflicting anti-cheat drivers
  • WSA (Windows Subsystem for Android) conflicts
  • Corrupt game installation

Fix: Uninstall and reinstall the problematic game, disable Xbox Game Bar (Win + G > Settings > uncheck Enable Xbox Game Bar), or update the Xbox app.


Recovery When Windows Won't Boot

If the PC blue screens before reaching the desktop and won't boot:

  1. System Restore via WinRE: Troubleshoot > Advanced Options > System Restore
  2. Startup Repair: Troubleshoot > Advanced Options > Startup Repair
  3. Command Line Repair (see code block below)
  4. Reset This PC: Troubleshoot > Reset this PC (keep or remove files)
  5. Fresh Windows Install from USB as a last resort

KERNEL_SECURITY_CHECK_FAILURE Deep Dive

This stop code (0x00000139) indicates a critical data structure was corrupted — often caused by:

  • Outdated or incompatible drivers (especially after Windows upgrades)
  • Malware or rootkits
  • Overclocked RAM running at unstable speeds

Fix path: Safe Mode > DDU to remove GPU drivers > fresh driver install > disable XMP in BIOS temporarily to test RAM stability.


MEMORY_MANAGEMENT Deep Dive

Stop code 0x0000001A points to RAM corruption or addressing errors:

  • Run Windows Memory Diagnostic and MemTest86
  • Try running with one RAM stick at a time
  • Ensure RAM is installed in correct slots (check motherboard manual for dual-channel configuration)
  • In BIOS, disable XMP/EXPO to run RAM at stock speeds and test

My PC Blue Screened for the First Time — What Now?

A one-time BSOD is often not cause for alarm. Common triggers:

  • A temporary driver glitch
  • A Windows Update that needed a forced restart
  • A one-time power fluctuation

Actions: Note the stop code, run sfc /scannow, and monitor for recurrence. If it happens again within days, follow the full diagnostic steps above.

Frequently Asked Questions

bash
# ============================================================
# PC Blue Screen (BSOD) Diagnostic & Fix Commands
# Run in elevated Command Prompt (Run as Administrator)
# ============================================================

# --- STEP 1: Check System Files for Corruption ---
sfc /scannow

# --- STEP 2: Repair Windows Component Store (run after sfc) ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- STEP 3: Schedule Disk Check on Next Reboot ---
# Replace C: with your system drive letter if different
chkdsk C: /f /r /x

# --- STEP 4: View Recent Stop Error from Event Log ---
Get-EventLog -LogName System -EntryType Error -Newest 20 | Where-Object {$_.EventID -eq 41 -or $_.EventID -eq 1001} | Format-List
# (Run in PowerShell as Administrator)

# --- STEP 5: List Minidump Files for Analysis ---
dir C:\Windows\Minidump\

# --- STEP 6: Check Disk SMART Status ---
wmic diskdrive get status,model,serialnumber

# --- STEP 7: List All Installed Third-Party Drivers ---
pnputil /enum-drivers | findstr /i "published\|provider\|driver"

# --- STEP 8: Check Memory (RAM) via built-in tool ---
# This launches Windows Memory Diagnostic (requires reboot)
mdsched.exe

# --- STEP 9: Boot Repair Commands (run from WinRE Command Prompt) ---
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

# --- STEP 10: Disable Automatic Reboot on BSOD (so you can read stop code) ---
wmic recoveros set AutoReboot=False

# --- STEP 11: Enable Kernel Memory Dump for Deep Analysis ---
# (Sets dump type to Kernel Memory Dump in registry)
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 2 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f

# --- STEP 12: Analyze dump with WinDbg (run from WinDbg prompt, not CMD) ---
# Open WinDbg, load latest minidump, then run:
# !analyze -v
# !thread
# lmvm <module_name>

# --- STEP 13: Uninstall a Specific Driver by INF Name (Advanced) ---
# Find the published name from Step 7 output, e.g., oem10.inf
# pnputil /delete-driver oem10.inf /uninstall /force

# --- STEP 14: Roll Back a Driver via Command Line ---
# Use Device Manager GUI, or PowerShell:
Get-PnpDevice | Where-Object {$_.FriendlyName -like '*NVIDIA*' -or $_.FriendlyName -like '*AMD*'} | Format-Table FriendlyName, Status, InstanceId
# Then roll back via Device Manager > Properties > Driver tab > Roll Back Driver

# --- STEP 15: Quick Temperature Check (PowerShell + WMI) ---
# Note: Not all systems expose thermal data via WMI; use HWMonitor for full detail
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace root/wmi | Select-Object InstanceName, @{N='Temp_C';E={($_.CurrentTemperature - 2732) / 10}}
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SRE specialists, and Windows system administrators with 10+ years of experience diagnosing hardware failures, kernel panics, and OS-level crashes across enterprise and consumer environments. Our guides are built from real incident post-mortems, manufacturer documentation, and community-validated fixes.

Sources

Related Articles in Other Pc Blue Screen

Explore More windows Guides