Why does my PC keep blue screening with different error codes every time?

Varying stop codes almost always indicate a hardware problem rather than a software one. The top two culprits are faulty RAM and a failing or underpowered power supply unit (PSU). Run MemTest86 for at least 2 passes to test RAM. If RAM passes, check the PSU: use a PSU tester or swap in a known-good unit. Also ensure your PSU wattage is sufficient for your components — GPU alone can draw 300-400W under load on high-end cards.

My computer keeps blue screening when I play games like Valorant or other titles — what's the fix?

Gaming BSODs are most commonly caused by: (1) Outdated or corrupt GPU drivers — do a clean reinstall using DDU in Safe Mode, then install the latest driver from your GPU vendor. (2) Overheating — monitor GPU and CPU temps with HWiNFO64 under load; clean dust and reapply thermal paste if temps exceed 90°C. (3) RAM instability with XMP enabled — disable XMP in BIOS and test. (4) For Valorant specifically, make sure Riot Vanguard anti-cheat is up to date, as it runs at the kernel level and can conflict with older drivers.

My PC or laptop keeps blue screening on startup — how do I fix it when I can't even boot into Windows?

If Windows won't boot due to BSODs: Boot from a Windows installation USB (download via Media Creation Tool), choose 'Repair your computer', then go to Troubleshoot > Advanced Options > Startup Repair. If that fails, use Command Prompt from the same menu and run: 'sfc /scannow' and 'chkdsk C: /f /r'. If the drive is healthy and files are repaired but BSODs persist at boot, the Windows installation itself may be corrupted — a clean reinstall is the next step.

My new PC keeps blue screening — is it defective?

Not necessarily defective, but something is wrong. First, ensure all drivers are installed correctly: run Windows Update fully, install chipset drivers from your motherboard manufacturer's site, then GPU drivers. Check BIOS and disable XMP/EXPO (manual RAM overclock profiles) to run RAM at stock speeds. Reseat all RAM sticks. If a specific RAM stick fails MemTest86, it may be DOA and covered under warranty. Contact your retailer or manufacturer for an RMA if hardware testing confirms a defect.

How do I find out what caused my last BSOD if the screen cleared too fast to read?

Windows logs every BSOD automatically. Check these three places: (1) Event Viewer — press Win+R, type 'eventvwr', navigate to Windows Logs > System, filter for Critical events with Source 'BugCheck'. (2) Reliability History — search for 'reliability' in Start Menu, open Reliability Monitor, click on any red X to see details. (3) Minidump files — go to C:\Windows\Minidump\ and open .dmp files with WinDbg Preview (free from Microsoft Store) and run '!analyze -v' to get the exact faulting module and stop code.

PC Keeps Blue Screening (BSOD): Complete Troubleshooting Guide for Windows

Fix blue screening issues on Windows PCs and laptops. Diagnose BSOD causes with WinDbg, Event Viewer, and MemTest86. Step-by-step fixes included.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,190 words

Key Takeaways

The most common causes of repeated BSODs are faulty RAM, corrupted drivers (especially GPU drivers), overheating hardware, corrupted Windows system files, and failing storage drives.
BSODs during gaming (including Valorant) are almost always caused by GPU/CPU overclocking instability, overheating, or outdated/corrupt graphics drivers.
Quick fix path: Check Event Viewer for the stop code, update or roll back drivers, run MemTest86 for RAM, run SFC /scannow and CHKDSK for system/disk integrity, and reseat hardware if BSODs persist.
New PCs blue screening on startup often indicate driver incompatibility or a factory-defective RAM stick — test sticks individually.
BSODs with different error codes each time almost always point to bad RAM or a failing power supply unit (PSU).

Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back GPU Drivers (DDU)	BSOD during gaming or after driver update	15-30 min	Low
Run SFC /scannow + DISM	Random BSODs, corrupted system files suspected	20-40 min	Low
MemTest86 RAM Test	BSODs with varying stop codes, new PC crashing	1-8 hours	None
CHKDSK /f /r	BSOD on startup, storage-related stop codes	30-120 min	Low
Check Temperatures (HWiNFO64)	BSOD during load/gaming, thermal throttling	10-15 min	None
Reseat/Replace RAM Sticks	MemTest86 fails, new PC blue screening	10-20 min	Low
Windows Startup Repair / Reset	BSOD on every startup, unbootable system	30-60 min	Medium
Analyze Minidump with WinDbg	Persistent BSODs with unclear cause	20-45 min	None
PSU Replacement	BSODs under heavy load, multiple error codes	30-60 min	Medium
Clean Windows Reinstall	All other methods exhausted, still blue screening	60-120 min	High

Understanding Blue Screen of Death (BSOD) Errors

A Blue Screen of Death (BSOD) is Windows' safety mechanism that halts the system when it encounters a fatal error from which it cannot safely recover. The screen displays a stop code (e.g., MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) that acts as the primary diagnostic clue.

Common stop codes and their likely causes:

MEMORY_MANAGEMENT — Faulty or misconfigured RAM
IRQL_NOT_LESS_OR_EQUAL — Corrupt or incompatible driver
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — GPU or hardware driver crash
CRITICAL_PROCESS_DIED — Corrupted Windows system files
PAGE_FAULT_IN_NONPAGED_AREA — RAM failure or driver bug
WHEA_UNCORRECTABLE_ERROR — Hardware failure (CPU, RAM, PSU)
CLOCK_WATCHDOG_TIMEOUT — CPU instability, often from overclocking
DPC_WATCHDOG_VIOLATION — Driver or SSD firmware incompatibility
VIDEO_TDR_FAILURE — GPU driver timeout or failing GPU

Step 1: Read the BSOD and Find Your Minidump

Every BSOD writes a crash dump file. By default, Windows saves small memory dumps (minidumps) to C:\Windows\Minidump\. These files contain the exact driver or module that caused the crash.

Enable minidump writing if not already active:

Right-click This PC > Properties > Advanced system settings
Under Startup and Recovery, click Settings
Set Write debugging information to Small memory dump (256 KB)
Set the dump path to %SystemRoot%\Minidump
Click OK and restart

Check Event Viewer for BSOD history:

Press Win + X > Event Viewer
Navigate to Windows Logs > System
Filter for Critical and Error events
Look for events with Source = BugCheck — these log the exact stop code

Step 2: Analyze Minidumps with WinDbg

Download WinDbg Preview from the Microsoft Store (free). Open a .dmp file from C:\Windows\Minidump\ and run:

!analyze -v

This outputs the exact faulting module (e.g., nvlddmkm.sys = NVIDIA driver, ntoskrnl.exe = Windows kernel). Use this information to guide your fix.

Step 3: Update or Roll Back Drivers

Drivers — especially GPU drivers — are the single most common software cause of BSODs. If your BSOD began after a driver update, roll back:

Press Win + X > Device Manager
Expand Display adapters, right-click your GPU
Select Properties > Driver tab > Roll Back Driver

If rolling back is unavailable or the BSOD persists, perform a clean driver reinstall using Display Driver Uninstaller (DDU):

Download DDU from Wagnardsoft.com
Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings)
Run DDU and select Clean and Restart
After restart, download the latest driver from NVIDIA, AMD, or Intel and install

Step 4: Test RAM with MemTest86

If your PC keeps blue screening with different error codes each time, RAM is the prime suspect. MemTest86 is the gold standard test.

Download MemTest86 from memtest86.com
Flash it to a USB drive using the included tool
Boot from the USB (change boot order in BIOS/UEFI)
Run at least 2 full passes (8+ passes for thorough testing)
Any errors = defective RAM

If errors are found:

If you have 2+ sticks, test each individually to isolate the bad stick
Try reseating RAM in different slots (consult motherboard manual for optimal dual-channel slots)
Check that your RAM XMP/EXPO profile is supported by your motherboard
If XMP is enabled and causing instability, try disabling it in BIOS and run at stock speeds

Step 5: Repair Windows System Files

Corrupted system files can cause persistent or startup BSODs. Run these commands as Administrator:

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

After both complete, restart and check if BSODs persist.

Step 6: Check Your Storage Drive

A failing HDD or SSD — especially one with bad sectors — causes startup BSODs (CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE). Run CHKDSK:

chkdsk C: /f /r /x

You'll be prompted to schedule it on next boot. Restart and let it run (can take 30-120 minutes).

Also check drive health with CrystalDiskInfo (free). A drive showing Caution or Bad status needs replacement immediately.

Step 7: Monitor Temperatures

Overheating causes BSODs during load (gaming, rendering, compiling). Download HWiNFO64 or HWMonitor and watch temperatures under load.

Safe temperature ranges:

CPU: Under 90°C during load (ideally under 80°C)
GPU: Under 85°C during gaming
NVMe SSD: Under 70°C

If temperatures are critical:

Clean dust from all fans and heatsinks (compressed air)
Reapply thermal paste on CPU (Arctic MX-4 or Noctua NT-H1)
Ensure your case has adequate airflow (intake fans at front/bottom, exhaust at rear/top)
Undervolt GPU using MSI Afterburner if GPU is thermal throttling

Step 8: Fix Gaming-Specific BSODs (Valorant, Games)

If your PC keeps blue screening while playing games like Valorant:

Update GPU drivers (most common fix) using DDU clean install method above
Disable XMP/EXPO in BIOS if RAM is overclocked
Revert GPU/CPU overclock — even a factory OC can be unstable; test at stock clocks
Check Valorant's anti-cheat (Vanguard) — kernel-level anti-cheat can conflict with drivers. Update Vanguard or reinstall it via the Valorant launcher
Lower in-game settings temporarily to reduce GPU load and confirm it's thermal/stability related
Run FurMark or 3DMark stress test — if it crashes here too, it's a hardware/driver issue not game-specific

Step 9: New PC Keeps Blue Screening

A brand new PC blue screening usually means:

RAM not properly seated — reseat all sticks firmly
XMP/EXPO enabled but unstable — disable in BIOS temporarily
Incorrect driver installation order — run Windows Update fully, then install chipset drivers, then GPU drivers
DOA (Dead on Arrival) component — test RAM sticks individually

Step 10: Last Resort — Reset or Reinstall Windows

If all hardware tests pass and BSODs continue:

Try Windows Reset (Settings > System > Recovery > Reset this PC > Keep my files)
If that fails, perform a clean install of Windows using the Media Creation Tool from microsoft.com
Test hardware with a fresh OS install — if BSODs stop, the old installation was corrupted
If BSODs continue on a clean install, the issue is definitively hardware — likely RAM, PSU, or motherboard

Frequently Asked Questions

powershell

# ============================================================
# BSOD DIAGNOSTIC SCRIPT FOR WINDOWS
# Run PowerShell as Administrator
# ============================================================

# 1. List recent BSODs from Event Log (last 30 days)
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001; StartTime=(Get-Date).AddDays(-30)} |
  Select-Object TimeCreated, Message |
  Format-List

# 2. List all minidump files with timestamps
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
  Select-Object Name, LastWriteTime, @{Name='SizeMB';Expression={[math]::Round($_.Length/1MB,2)}} |
  Format-Table -AutoSize

# 3. Check Windows system file integrity
Write-Host "`n=== Running System File Checker ==="
Start-Process -FilePath "sfc" -ArgumentList "/scannow" -Wait -NoNewWindow

# 4. Run DISM to repair Windows image
Write-Host "`n=== Running DISM Health Restore ==="
Start-Process -FilePath "DISM" -ArgumentList "/Online /Cleanup-Image /RestoreHealth" -Wait -NoNewWindow

# 5. Check disk for errors (schedules on next boot)
Write-Host "`n=== Scheduling CHKDSK on Next Boot ==="
cmd /c "echo y | chkdsk C: /f /r /x"

# 6. Check current driver versions for display adapters
Write-Host "`n=== Display Adapter Drivers ==="
Get-WmiObject Win32_VideoController |
  Select-Object Name, DriverVersion, DriverDate |
  Format-Table -AutoSize

# 7. Check RAM info
Write-Host "`n=== Installed RAM ==="
Get-WmiObject Win32_PhysicalMemory |
  Select-Object Manufacturer, PartNumber, Capacity, Speed, @{Name='SizeGB';Expression={[math]::Round($_.Capacity/1GB,1)}} |
  Format-Table -AutoSize

# 8. Check CPU temperature via WMI (requires hardware support)
Write-Host "`n=== CPU Thermal Zones (if supported) ==="
try {
  Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace root/wmi -ErrorAction Stop |
    Select-Object @{Name='TempC';Expression={[math]::Round($_.CurrentTemperature/10 - 273.15,1)}} |
    Format-Table -AutoSize
} catch {
  Write-Host "Thermal WMI not supported on this system. Use HWiNFO64 or HWMonitor instead."
}

# 9. Export system info to file for review
Write-Host "`n=== Exporting System Info ==="
Get-ComputerInfo | Out-File -FilePath "$env:USERPROFILE\Desktop\SystemInfo_BSODDiag.txt"
Write-Host "System info saved to Desktop as SystemInfo_BSODDiag.txt"

Write-Host "`n=== Diagnostic Complete. Review results above and check minidumps with WinDbg Preview ==="

# ============================================================
# MANUAL COMMANDS REFERENCE
# ============================================================
# Analyze minidump in WinDbg:     !analyze -v
# Check bad sectors:              chkdsk C: /f /r /x
# Verify system files:            sfc /scannow
# Repair Windows image:           DISM /Online /Cleanup-Image /RestoreHealth
# Enable verbose BSOD display:    bcdedit /set {current} bootstatuspolicy displayallfailures
# Disable automatic restart:      bcdedit /set {current} bootstatuspolicy IgnoreAllFailures
# Reset boot config (if needed):  bootrec /fixmbr && bootrec /fixboot && bootrec /rebuildbcd
# ============================================================

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing hardware failures, OS-level crashes, and driver conflicts across enterprise and consumer environments. Our guides are built from real incident post-mortems, Microsoft documentation, and hands-on hardware testing.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.