Error Medic

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

Fix PC blue screen errors fast. Covers KERNEL_SECURITY_CHECK_FAILURE, MEMORY_MANAGEMENT, gaming BSODs & more with step-by-step commands and recovery tips.

Last updated:
Last verified:
2,390 words
Key Takeaways
  • The most common PC blue screen causes are faulty RAM, corrupted drivers (especially GPU drivers), overheating hardware, and damaged Windows system files.
  • Gaming-related BSODs (e.g., Xbox Game Pass, CyberPower PC) are most often triggered by outdated or corrupt GPU/DirectX drivers, insufficient virtual memory, or RAM instability under load.
  • Quick fix summary: Note the STOP code shown on the blue screen, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated command prompt, update or roll back drivers, run Windows Memory Diagnostic, check temperatures with HWMonitor, and as a last resort perform Startup Repair from a Windows boot USB.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Run sfc /scannowCorrupted system files suspected; PC still boots5-15 minLow
DISM RestoreHealthsfc fails or reports unrepairable files15-30 minLow
Update/Roll Back GPU DriverBSOD happens only during gaming or after driver update10-20 minLow
Windows Memory DiagnosticMEMORY_MANAGEMENT or random BSODs30-60 minLow
MemTest86 (bootable)Suspect faulty RAM; need thorough test2-8 hoursLow
Check & Clean Cooling SystemOverheating temps (>90°C CPU/GPU under load)30-60 minMedium
Adjust Virtual Memory / PagefileBSODs under heavy load or with large game assets5 minLow
Startup Repair (WinRE)PC won't boot after BSOD15-30 minLow-Medium
Reset This PC (Keep Files)Persistent BSODs, other fixes failed, PC still accessible1-3 hoursMedium
Clean Windows ReinstallAll else fails or BSOD on first boot of new PC2-4 hoursHigh (data loss risk)

Understanding the PC Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD) is Windows' protective mechanism that halts the system when it encounters a fatal error it cannot safely recover from. You will see a blue or occasionally green screen with a sad face emoji and a STOP code such as:

  • KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
  • MEMORY_MANAGEMENT (0x0000001A)
  • SYSTEM_SERVICE_EXCEPTION (0x0000003B)
  • IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
  • PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)
  • CRITICAL_PROCESS_DIED (0x000000EF)
  • VIDEO_TDR_FAILURE (atikmpag.sys / nvlddmkm.sys)
  • WHEA_UNCORRECTABLE_ERROR (0x00000124)

Always photograph or note the exact STOP code and any file names listed (e.g., ntfs.sys, nvlddmkm.sys) before the screen disappears — this is your primary diagnostic clue.


Step 1: Identify the STOP Code and Collect Crash Dumps

Enable automatic minidump creation (if not already enabled):

  1. Press Win + R, type sysdm.cpl, press Enter.
  2. Go to Advanced → Startup and Recovery → Settings.
  3. Under Write debugging information, select Small memory dump (256 KB).
  4. Confirm the dump directory is %SystemRoot%\Minidump.

Read existing crash dumps with WinDbg or PowerShell:

Use the built-in Get-WinEvent or install WinDbg Preview from the Microsoft Store to open .dmp files in C:\Windows\Minidump.

Alternatively, use the free tool WhoCrashed or BlueScreenView (NirSoft) to parse minidumps without a debugger.


Step 2: Check Windows Event Viewer

  1. Press Win + X → Event Viewer.
  2. Navigate to Windows Logs → System.
  3. Filter by Critical and Error events around the time of the crash.
  4. Look for sources like BugCheck, Kernel-Power, or disk errors.

A Kernel-Power Event ID 41 with Bugcheck code indicates an unexpected shutdown — common with power supply issues.


Step 3: Repair Windows System Files

Open Command Prompt as Administrator and run:

sfc /scannow

Wait for the scan to complete. If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them," follow up with DISM:

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

Reboot after both commands complete, then run sfc /scannow once more to confirm all files are repaired.


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

Gaming BSODs on platforms like Xbox Game Pass, or on CyberPower or custom gaming PCs, are most often caused by GPU driver issues. Common culprit files listed on the BSOD include:

  • nvlddmkm.sys — NVIDIA GPU driver
  • atikmpag.sys / amdkmdag.sys — AMD GPU driver
  • igdkmd64.sys — Intel integrated GPU driver

To update NVIDIA drivers:

  1. Download the latest driver from https://www.nvidia.com/drivers
  2. Run the installer and choose Custom → Clean Install to remove old driver remnants.

To roll back a driver:

  1. Press Win + X → Device Manager.
  2. Expand Display Adapters, right-click your GPU → Properties → Driver → Roll Back Driver.

Use DDU (Display Driver Uninstaller) for a clean slate: Boot into Safe Mode, run DDU to fully remove existing GPU drivers, then reinstall the latest stable version.


Step 5: Test and Diagnose RAM

Memory issues are a leading cause of MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, and random BSODs, especially on new PCs.

Windows Memory Diagnostic (quick test):

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

MemTest86 (comprehensive):

  1. Download MemTest86 from https://www.memtest86.com/
  2. Flash to a USB drive using the provided tool.
  3. Boot from USB and run at least 2 full passes.
  4. If errors are found, reseat RAM sticks; test each stick individually to identify the faulty module.

For new PCs: Verify RAM is seated in the correct slots for dual-channel (typically slots 2 and 4, or A2/B2 — consult your motherboard manual). Also ensure XMP/EXPO profile is enabled in BIOS if your RAM is rated above 2133 MHz.


Step 6: Monitor Temperatures and Check for Overheating

BSODs during gaming often occur because the CPU or GPU hits thermal limits. Download HWMonitor (CPUID) or MSI Afterburner and monitor temperatures under load:

  • CPU safe range: Below 90°C under full load (80°C preferred)
  • GPU safe range: Below 85°C under full load

If temperatures are excessive:

  1. Clean dust from heatsinks and fans using compressed air.
  2. Reapply thermal paste to the CPU (especially if the PC is 3+ years old).
  3. Improve case airflow by ensuring intake/exhaust fans are properly configured.
  4. For laptops, use a cooling pad and ensure vents are unobstructed.

Step 7: Check Storage Health

A failing SSD or HDD can cause NTFS.SYS BSODs and post-startup blue screens.

Check disk health with CrystalDiskInfo (free tool) — look for "Caution" or "Bad" status.

Run CHKDSK from an elevated Command Prompt:

chkdsk C: /f /r /x

Schedule it to run on next reboot if the drive is in use. Review results in Event Viewer (source: Chkdsk) after reboot.


Step 8: Adjust Virtual Memory (Pagefile)

Insufficient virtual memory causes BSODs under heavy gaming load:

  1. Press Win + R, type sysdm.cpl.
  2. Go to Advanced → Performance → Settings → Advanced → Virtual Memory → Change.
  3. Uncheck Automatically manage paging file size.
  4. Set a custom size: Initial = 1.5x your RAM in MB; Maximum = 3x your RAM in MB. (Example: 16 GB RAM → Initial: 24576 MB, Maximum: 49152 MB)

Step 9: Recovery When PC Won't Boot After BSOD

If your PC shows a blue screen and won't boot (or loops on BSOD), use Windows Recovery Environment (WinRE):

Access WinRE:

  • On most PCs, force-power-off 3 times during boot to trigger Automatic Repair.
  • Or boot from a Windows 10/11 USB and select Repair your computer.

In WinRE, go to: Troubleshoot → Advanced Options and try:

  1. Startup Repair — Automatically fixes boot issues.
  2. Command Prompt — Run sfc, DISM, or chkdsk manually.
  3. Uninstall Updates — If BSOD started after a Windows Update.
  4. System Restore — Roll back to a restore point before the issue started.

If "There was a problem resetting your PC" appears as a blue screen error: This indicates the Reset This PC process failed, usually due to a corrupted Windows image or missing recovery partition. Use a bootable Windows USB to perform a clean reinstall instead.


Step 10: BIOS and Hardware-Level Checks

  • Update BIOS/UEFI firmware — Especially on new PCs; manufacturers release stability patches.
  • Disable XMP/EXPO temporarily — If RAM-related BSODs persist, run at stock speeds to isolate.
  • Check for loose hardware — Reseat GPU, RAM, and storage cables.
  • Test with minimal hardware — Remove extra RAM sticks, disconnect non-essential USB devices.
  • Check PSU adequacy — Underpowered PSUs cause random BSODs under gaming load. Verify your PSU wattage meets your GPU's requirements.

Frequently Asked Questions

bash
# ============================================================
# PC BLUE SCREEN (BSOD) DIAGNOSTIC & REPAIR COMMANDS
# Run all commands in an elevated (Administrator) Command Prompt
# or PowerShell unless noted otherwise
# ============================================================

# --- 1. View recent BSOD stop codes via PowerShell ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 41 -or $_.Id -eq 1001} | Select-Object TimeCreated, Message | Select-Object -First 10

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

# --- 3. Repair corrupted Windows system files ---
sfc /scannow

# --- 4. Repair Windows image using DISM ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Run again after DISM to confirm all files repaired ---
sfc /scannow

# --- 6. Check disk for errors (schedule on next reboot) ---
chkdsk C: /f /r /x

# --- 7. Check disk health quickly without repair ---
chkdsk C:

# --- 8. Verify and repair boot records (run from WinRE CMD) ---
bootrec /fixmbr
bootrec /fixbr
bootrec /rebuildbcd

# --- 9. Flush DNS and reset network stack (for network driver BSODs) ---
netsh int ip reset
netsh winsock reset
ipconfig /flushdns

# --- 10. Check RAM via Windows Memory Diagnostic (will reboot) ---
mdsched.exe

# --- 11. View Memory Diagnostic results in Event Viewer after reboot ---
Get-WinEvent -LogName System | Where-Object {$_.ProviderName -eq 'Microsoft-Windows-MemoryDiagnostics-Results'} | Select-Object -First 5 | Format-List

# --- 12. List recently installed drivers (PowerShell) ---
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate | Sort-Object DriverDate -Descending | Select-Object -First 20

# --- 13. List installed Windows Updates (find recently installed patches) ---
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# --- 14. Uninstall a specific Windows Update (replace KB number) ---
wusa /uninstall /kb:5039299 /quiet /norestart

# --- 15. Check system uptime and last boot time ---
(Get-Date) - (gcim Win32_OperatingSystem).LastBootUpTime

# --- 16. Export System Event Log to file for analysis ---
wevtutil epl System C:\BSOD_System_Log.evtx

# --- 17. Enable detailed crash dump if minidump isn't capturing enough ---
# Set via Registry (requires reboot)
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 2 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v MinidumpsCount /t REG_DWORD /d 10 /f

# --- 18. Check for driver verifier issues (advanced — use carefully) ---
# Enable Driver Verifier for all unsigned drivers (triggers BSOD if bad driver found)
# verifier /standard /all
# To disable Driver Verifier:
# verifier /reset

# --- 19. Scan for malware (Windows Defender quick scan) ---
"C:\Program Files\Windows Defender\MpCmdRun.exe" -Scan -ScanType 1

# --- 20. Reset Windows Update components (if BSOD after failed update) ---
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
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing and resolving Windows system failures, kernel errors, and infrastructure incidents. Our guides are built from real-world troubleshooting cases, official Microsoft documentation, and community-validated solutions.

Sources

Related Articles in Other Pc Blue Screen

Explore More windows Guides