Error Medic

PC Keeps Blue Screening (BSOD): Complete Fix Guide for Windows 10 & 11

Fix constant blue screen of death errors on PC or laptop. Covers random BSODs, gaming crashes, startup loops, and different error codes. Step-by-step solutions.

Last updated:
Last verified:
2,110 words
Key Takeaways
  • Faulty or incompatible RAM is the most common cause of random BSODs with different error codes — run Windows Memory Diagnostic or MemTest86 first.
  • Outdated, corrupt, or incompatible drivers (especially GPU drivers) cause the majority of blue screens during gaming in titles like Valorant.
  • Overheating, failing storage (HDD/SSD), corrupted system files, and bad Windows updates are the next most frequent culprits — each has a specific diagnostic command.
  • Quick fix summary: Boot into Safe Mode → run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' → update or roll back GPU driver → run MemTest86 → check temperatures with HWMonitor → scan disk with 'chkdsk C: /f /r'.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC / DISM System File RepairBSOD on startup or after Windows Update15–30 minLow
Driver DDU Clean ReinstallBSOD during gaming, after GPU driver update, Valorant crashes20–40 minLow
Windows Memory Diagnostic / MemTest86Random BSODs with different error codes, new PC1–8 hoursNone
CHKDSK Disk ScanBSOD on startup, after sudden power loss, old HDD/SSD30–120 minLow
Thermal Paste & CleaningBSOD during load, high CPU/GPU temps, laptop constantly crashing30–60 minMedium
Windows Update RollbackBSOD started after a specific Windows Update15–20 minLow
BIOS/UEFI Firmware UpdateNew PC BSOD, hardware compatibility issues10–20 minMedium
Windows Reset / ReinstallAll other fixes failed, persistent BSOD loop1–3 hoursHigh (data loss risk)

Understanding Blue Screen of Death (BSOD) Errors

A Blue Screen of Death (BSOD), formally called a Stop Error, occurs when Windows encounters a fatal system error it cannot recover from. The screen displays a STOP code such as MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, PAGE_FAULT_IN_NONPAGED_AREA, IRQL_NOT_LESS_OR_EQUAL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, or CRITICAL_PROCESS_DIED. If your PC keeps blue screening with different error codes, that strongly points to hardware instability — typically RAM or power delivery.


Step 1: Read the BSOD Error Code

Before fixing anything, identify the exact stop code. Modern Windows 10/11 BSODs show a QR code and a stop code like:

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

If the PC reboots too fast to read it:

  1. Open Start → Settings → System → About → Advanced system settings.
  2. Under Startup and Recovery, click Settings.
  3. Uncheck Automatically restart under System failure.
  4. Click OK.

Now the PC will halt on the blue screen so you can read the stop code.


Step 2: Analyze Minidump Crash Logs

Windows saves a minidump file every time it BSODs. Use WinDbg or the free tool WhoCrashed to read them.

Minidump location: C:\Windows\Minidump\

With WhoCrashed, open the tool and click Analyze — it will display the faulty driver or component in plain English. Common findings include nvlddmkm.sys (NVIDIA driver), ntoskrnl.exe (kernel/RAM), dxgkrnl.sys (DirectX/GPU), or ataport.sys (disk controller).


Step 3: Fix Corrupt System Files

If your computer keeps blue screening on startup or after a Windows Update, corrupted system files are likely. Boot into Windows (Safe Mode if necessary — press F8 or Shift+F8 during boot) and run:

sfc /scannow

If SFC finds unrepairable files, run DISM:

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

Reboot after completion.


Step 4: Update or Roll Back GPU/Display Drivers

This is the #1 fix for BSODs during gaming (Valorant, other games). Stop codes like TDR_FAILURE, SYSTEM_SERVICE_EXCEPTION, or dxgkrnl.sys all point here.

Clean install NVIDIA/AMD drivers using DDU:

  1. Download Display Driver Uninstaller (DDU) from guru3d.com.
  2. Boot into Safe Mode (Settings → Recovery → Advanced startup → Troubleshoot → Startup Settings → Safe Mode).
  3. Run DDU, select your GPU brand, and click Clean and Restart.
  4. After reboot, download and install the latest driver from nvidia.com or amd.com.

If the BSOD started after a driver update, roll back instead:

  • Open Device Manager → Display Adapters → right-click GPU → Properties → Driver tab → Roll Back Driver.

Step 5: Test Your RAM

If your PC keeps blue screening with different error codes or a new PC keeps blue screening, RAM is the prime suspect. Stop codes like MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, and PAGE_FAULT_IN_NONPAGED_AREA are strong indicators.

Quick test with Windows Memory Diagnostic:

  • Press Win+R, type mdsched.exe, press Enter, choose Restart now and check for problems.

Thorough test with MemTest86:

  1. Download MemTest86 (memtest86.com) and create a bootable USB.
  2. Boot from the USB and run at least 2 full passes (8 passes recommended).
  3. Any errors = bad RAM. Try each stick individually to find the faulty module.
  4. Also try reseating RAM sticks and testing in different slots.

XMP/EXPO profiles: If you enabled XMP or EXPO in BIOS, try disabling it temporarily. Aggressive memory overclocks on new PCs are a frequent BSOD cause.


Step 6: Check Storage Health

A failing SSD or HDD causes BSODs on startup. Stop codes: CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, BAD_SYSTEM_CONFIG_INFO.

Run CHKDSK from an elevated command prompt:

chkdsk C: /f /r /x

This requires a reboot to run before Windows loads. It will find and repair bad sectors.

Also check SMART health:

wmic diskdrive get model,status

Or use CrystalDiskInfo (free) for a detailed health report. Any status other than Good means the drive is failing and needs replacement.


Step 7: Check for Overheating

Laptops that constantly blue screen during load often overheat. Games push GPU and CPU to 100%, and thermal throttling or emergency shutdown triggers a BSOD. Stop codes: THERMAL_RUNAWAY, WHEA_UNCORRECTABLE_ERROR.

  1. Download HWMonitor or Core Temp and monitor temperatures under load.
  2. CPU should stay below 90°C; GPU below 85°C for sustained gaming.
  3. If temps are too high: clean dust from vents, repaste CPU/GPU (especially on laptops 3+ years old), ensure adequate case airflow on desktops.

Step 8: Check Power Supply

A failing or underpowered PSU causes random BSODs under load. If you recently added new hardware (GPU upgrade) or the PC blue screens only when gaming or under stress, test the PSU with a tool like OCCT which runs stress tests and monitors voltage rails. Voltages should be within 5% of nominal (12V should read 11.4V–12.6V). A failing PSU needs to be replaced.


Step 9: Roll Back or Pause Windows Updates

If BSODs started immediately after a Windows Update:

  1. Go to Settings → Windows Update → Update History → Uninstall Updates.
  2. Uninstall the most recent cumulative update.
  3. To pause future updates temporarily: Settings → Windows Update → Pause Updates.

Step 10: Reset or Reinstall Windows (Last Resort)

If all else fails and BSODs persist:

  1. Settings → System → Recovery → Reset this PC.
  2. Choose Keep my files for a soft reset or Remove everything for a clean install.
  3. For a fully clean install, download the Windows 11 Media Creation Tool from microsoft.com and install fresh from USB.

Before doing this, back up all data to an external drive.

Frequently Asked Questions

bash
# ============================================================
# BSOD DIAGNOSTIC & FIX COMMANDS FOR WINDOWS 10/11
# Run PowerShell or Command Prompt as Administrator
# ============================================================

# --- 1. Disable auto-restart to read BSOD stop codes ---
wmic recoveros set AutoReboot = False

# --- 2. Repair corrupted system files ---
sfc /scannow

# --- 3. Repair Windows image with DISM ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- 4. Quick RAM test (built-in, requires reboot) ---
mdsched.exe

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

# --- 6. Check disk SMART status ---
wmic diskdrive get model,status

# --- 7. List recent BSOD events from Event Log (PowerShell) ---
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 -or $_.Id -eq 6008 } | Select-Object TimeCreated, Id, Message | Format-List

# --- 8. List all minidump files for analysis ---
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length

# --- 9. Check CPU and system temperatures via WMI ---
# (Note: more reliable tools are HWMonitor/Core Temp for accurate readings)
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace "root/wmi" | Select-Object InstanceName, @{Name='TempC';Expression={($_.CurrentTemperature - 2732) / 10}}

# --- 10. Check for pending Windows Updates ---
Get-WindowsUpdate
# If module not installed: Install-Module PSWindowsUpdate -Force

# --- 11. List recently installed Windows Updates (to identify bad update) ---
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# --- 12. Uninstall a specific Windows Update by KB number ---
# Replace KB5034441 with the actual KB from crash timeline
wusa /uninstall /kb:5034441 /quiet /norestart

# --- 13. View installed drivers and their dates (find old/suspect drivers) ---
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate | Sort-Object DriverDate | Format-Table -AutoSize

# --- 14. Run Windows built-in Blue Screen troubleshooter ---
msdt.exe -id DeviceDiagnostic

# --- 15. Check system uptime since last crash ---
(get-date) - (gcim Win32_OperatingSystem).LastBootUpTime

# --- 16. Force memory dump on next BSOD (useful for analysis) ---
# Sets complete memory dump in registry
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl" -Name "CrashDumpEnabled" -Value 1
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl" -Name "AutoReboot" -Value 0

# ============================================================
# SAFE MODE BOOT COMMANDS
# ============================================================

# Boot into Safe Mode on next restart
bcdedit /set {current} safeboot minimal

# Restore normal boot (run after troubleshooting in Safe Mode)
bcdedit /deletevalue {current} safeboot
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems specialists with 10+ years of experience diagnosing and resolving critical system failures. We specialize in translating cryptic error codes and kernel panic logs into actionable, human-readable fixes for developers, IT administrators, and everyday users. Our guides are tested against real hardware and real Windows environments before publication.

Sources

Related Articles in Other Blue Screening

Explore More windows Guides