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

When a PC BSODs with multiple different stop codes, it almost always points to a hardware problem rather than a software one. The most common culprits are faulty RAM (test with MemTest86), an unstable overclocked CPU or GPU, a failing power supply that can't deliver stable voltage, or loose hardware connections. Run MemTest86 for 2+ full passes and check S.M.A.R.T. data on your drives. Disable all overclocking (including XMP/EXPO RAM profiles) as a diagnostic step.

Why does my PC only blue screen while gaming (Valorant, or other games)?

Gaming BSODs are typically caused by GPU driver issues (try a clean DDU reinstall), overheating GPU or CPU under load (monitor with HWiNFO64), insufficient PSU power delivery, or RAM instability exposed by high memory bandwidth demands. For Valorant specifically, the kernel-level Vanguard anti-cheat can conflict with certain drivers or security software. Check your GPU temperature stays below 90°C during gameplay and ensure your GPU drivers are up to date. Also verify Secure Boot and TPM 2.0 are properly configured for Vanguard.

My computer keeps blue screening on startup — how do I fix it without booting into Windows?

Boot into Windows Recovery Environment (WinRE) by interrupting startup 3 consecutive times (power button during Windows logo). From WinRE: 1) Try Startup Repair first. 2) If that fails, open Command Prompt and run 'sfc /scannow' and 'chkdsk C: /f /r'. 3) Try System Restore if restore points exist. 4) If a recent driver or update caused it, use 'bcdedit /set safeboot minimal' to force Safe Mode boot and uninstall the problematic driver. As a last resort, reinstall Windows using a bootable USB.

My new PC keeps blue screening — is it defective hardware?

New PC BSODs are common and often solvable without returning hardware. First, check if XMP/EXPO is enabled in BIOS — this factory overclocks RAM and can cause instability on some motherboards. Disable it temporarily and test. Reseat your RAM sticks (try one stick at a time in slot A2). Update your motherboard BIOS to the latest version, and install fresh chipset and GPU drivers directly from manufacturer websites rather than Windows Update. Run MemTest86 to rule out defective RAM modules.

My laptop keeps blue screening constantly — what should I check first?

Laptops have additional thermal constraints that desktops don't. Start by checking if the laptop is overheating — use HWiNFO64 to monitor CPU and GPU temperatures. Laptop cooling systems clog with dust much faster than desktops. If temperatures exceed 90–95°C, clean the vents with compressed air or consider repasting the CPU/GPU (if comfortable doing so). Also update all drivers from your laptop manufacturer's support page (not just Windows Update), check RAM health with Windows Memory Diagnostic, and run 'sfc /scannow' in an Administrator command prompt.

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

Fix a PC that keeps blue screening with step-by-step commands, driver rollbacks, RAM tests, and registry repairs. Works for gaming, startup, and random BSODs.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,213 words

Key Takeaways

Root cause 1: Faulty, outdated, or incompatible device drivers — especially GPU and chipset drivers — are the #1 cause of repeated BSODs, including stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
Root cause 2: Defective or overclocked RAM causes random and game-related BSODs with stop codes such as MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, or PAGE_FAULT_IN_NONPAGED_AREA.
Root cause 3: Corrupted Windows system files, failing storage drives (NTFS_FILE_SYSTEM, CRITICAL_PROCESS_DIED), overheating components, and problematic Windows updates can all trigger persistent blue screens.
Quick fix summary: Run 'winmem' (Windows Memory Diagnostic) and 'sfc /scannow' immediately, check Event Viewer for the stop code, update or roll back GPU drivers, run DISM to repair the Windows image, and test storage with CrystalDiskInfo or chkdsk.

Fix Approaches Compared
Method	When to Use	Time	Risk
Roll back or update GPU/driver	BSOD appears after driver update or while gaming	5–15 min	Low
Windows Memory Diagnostic / MemTest86	Random BSODs or MEMORY_MANAGEMENT stop code	30 min – 8 hrs	None
SFC /scannow + DISM repair	CRITICAL_PROCESS_DIED or corrupted OS files	15–30 min	Very Low
CHKDSK /f /r	NTFS_FILE_SYSTEM or slow/clicking hard drive	1–4 hrs	Low (read-only safe)
Check CPU/GPU temps & disable OC	BSOD only under load or during gaming	10 min	Low
Uninstall recent Windows Update	BSOD started after Windows Update	10 min	Medium
Startup Repair / Reset Windows	PC blue screens on startup, nothing else works	1–3 hrs	High (data loss risk if reset)
Replace RAM or re-seat hardware	MemTest86 shows errors, BSOD after hardware change	30–60 min	Medium

Understanding Blue Screen of Death (BSOD) Errors

A Blue Screen of Death (BSOD) — formally called a Stop Error — occurs when Windows encounters a critical error it cannot recover from. The system halts to prevent data corruption and displays a stop code on a blue (or green on Windows Insider builds) screen. Common stop codes include:

DRIVER_IRQL_NOT_LESS_OR_EQUAL — A driver tried to access memory at too high an IRQL.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — A system thread raised an exception the error handler didn't catch.
MEMORY_MANAGEMENT — RAM or virtual memory corruption detected.
WHEA_UNCORRECTABLE_ERROR — Hardware error, often CPU or RAM related.
PAGE_FAULT_IN_NONPAGED_AREA — Process accessed memory that wasn't available.
NTFS_FILE_SYSTEM — Storage or file system corruption.
CRITICAL_PROCESS_DIED — A critical Windows process terminated unexpectedly.
CLOCK_WATCHDOG_TIMEOUT — CPU core stopped responding, common with overclocks.
DPC_WATCHDOG_VIOLATION — A deferred procedure call exceeded time limits.

If your PC keeps blue screening with different errors, this is a strong indicator of hardware instability — most commonly RAM, storage, or PSU issues.

Step 1: Read the BSOD Stop Code and Check Event Viewer

The first thing you need is the exact stop code. On modern Windows, the BSOD screen displays a QR code and a stop code like MEMORY_MANAGEMENT. Note it down.

Then, boot into Windows and open Event Viewer to find crash details:

Press Win + R, type eventvwr.msc, press Enter.
Navigate to Windows Logs → System.
Filter for Critical and Error events around the time of the crash.
Look for source BugCheck — this contains the exact stop code and parameters.

Alternatively, use WinDbg or WhoCrashed to analyze dump files located at C:\Windows\Minidump\.

Step 2: Check for Overheating

If your computer keeps blue screening while playing games or under load, overheating is a prime suspect. Download HWiNFO64 or Core Temp and monitor temperatures while gaming.

CPU should stay below 95°C (ideally under 85°C).
GPU should stay below 90°C.
Thermal paste older than 3–4 years may need replacing.
Clean dust from fans and heatsinks with compressed air.

If temperatures are fine, disable any CPU or GPU overclocking. Even factory-overclocked RAM (XMP/EXPO profiles) can cause instability — try disabling XMP in BIOS and running RAM at default speed.

Step 3: Update or Roll Back Drivers

Driver issues — especially GPU drivers — are the most common cause of BSODs during gaming. Games like Valorant, which interact deeply with kernel-level anti-cheat (Vanguard), can expose driver conflicts.

To roll back a GPU driver:

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

To do a clean GPU driver reinstall:

Download DDU (Display Driver Uninstaller) from Wagnardsoft.
Boot into Safe Mode (hold Shift while clicking Restart).
Run DDU to fully remove GPU drivers.
Reboot and install the latest driver from NVIDIA or AMD's website.

Also check chipset, network, and audio drivers via your motherboard manufacturer's website.

Step 4: Test Your RAM

Defective RAM causes the widest variety of BSODs and is extremely common in new PC builds.

Quick test (built into Windows): Press Win + R, type mdsched.exe, select Restart now and check for problems. Windows will run a memory test on next boot.

Thorough test: Download MemTest86 (free), create a bootable USB, and run it for at least 2 full passes (8 passes recommended). Any errors = faulty RAM.

If you have multiple RAM sticks, test each stick individually in slot A2 to isolate faulty modules. Also try re-seating the RAM — remove and firmly reinsert each stick.

Step 5: Repair Windows System Files

Corrupted system files cause BSODs like CRITICAL_PROCESS_DIED and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

Run these commands in an Administrator Command Prompt:

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

After DISM completes, run sfc /scannow again. Restart when done.

Step 6: Check Storage Drive Health

A failing hard drive or SSD causes BSODs like NTFS_FILE_SYSTEM and INACCESSIBLE_BOOT_DEVICE.

Run CHKDSK in an Administrator Command Prompt:

chkdsk C: /f /r /x

You'll be prompted to schedule it for the next reboot — type Y and restart.

Also install CrystalDiskInfo to check S.M.A.R.T. data. Any attribute showing Caution or Bad status means the drive needs replacing soon.

Step 7: Uninstall Problematic Windows Updates

If your PC started blue screening after a Windows Update:

Go to Settings → Windows Update → Update History → Uninstall Updates.
Sort by date and uninstall the most recent updates.
Alternatively, use Settings → System → Recovery → Go back (available within 10 days of an upgrade).

Step 8: Fix a PC That Blue Screens on Startup

If Windows won't boot, force your PC into the Windows Recovery Environment (WinRE) by interrupting boot 3 times:

Turn on PC, then hold power button when the Windows logo appears. Repeat 3 times.
Windows will enter Automatic Repair mode.
Navigate to Advanced Options → Troubleshoot → Advanced Options.
Try Startup Repair first, then System Restore if a restore point exists.
Use Command Prompt from Recovery to run sfc /scannow and chkdsk commands on the offline drive.

Step 9: Check PSU and Reseat Hardware (New Builds)

A new PC that keeps blue screening is often suffering from:

Insufficient PSU wattage — Use PCPartPicker's power calculator and add 20% headroom.
Loose connections — Reseat GPU, RAM, and storage cables.
Bent CPU socket pins — Carefully inspect AM5/LGA1700 sockets.
Incompatible XMP profile — Disable XMP/EXPO temporarily to test.

Step 10: Nuclear Option — Reset or Reinstall Windows

If all else fails and hardware checks out, a clean Windows reinstall resolves persistent software-related BSODs:

Go to Settings → System → Recovery → Reset this PC.
Choose Remove everything for a clean slate.
Or, create a bootable Windows USB using the Media Creation Tool and perform a fresh install.

Always back up important data before resetting.

Frequently Asked Questions

powershell

# ============================================================
# BSOD DIAGNOSTIC & REPAIR SCRIPT FOR WINDOWS 10/11
# Run PowerShell as Administrator
# ============================================================

# --- Step 1: Read recent BSOD crash dump info from Event Log ---
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -LogName System -MaxEvents 50 | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 -or $_.Id -eq 6008 } | Format-List TimeCreated, Id, Message

# --- Step 2: List minidump files for analysis with WinDbg/WhoCrashed ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length

# --- Step 3: Check system file integrity ---
Write-Host "`n=== Running SFC Scan ==="
sfc /scannow

# --- Step 4: DISM repair of Windows image ---
Write-Host "`n=== Running DISM Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth
Write-Host "`n=== Restoring Windows Image (may take 10-20 min) ==="
DISM /Online /Cleanup-Image /RestoreHealth

# --- Step 5: Check disk for errors (scheduled for next reboot) ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
# Change C: to your Windows drive letter if different
cmd /c "echo Y | chkdsk C: /f /r /x"

# --- Step 6: Check RAM via Windows Memory Diagnostic (launches on reboot) ---
Write-Host "`n=== Launching Windows Memory Diagnostic ==="
# Uncomment the line below to launch immediately:
# mdsched.exe

# --- Step 7: Check driver verifier status ---
Write-Host "`n=== Driver Verifier Status ==="
verifier /query

# --- Step 8: List recently installed drivers (last 30 days) ---
Write-Host "`n=== Recently Installed Drivers ==="
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 7045 -and $_.TimeCreated -gt (Get-Date).AddDays(-30) } | Format-List TimeCreated, Message

# --- Step 9: Check disk S.M.A.R.T. status via WMIC ---
Write-Host "`n=== Disk S.M.A.R.T. Status ==="
Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus | Select-Object InstanceName, PredictFailure, Reason

# --- Step 10: Export system info for further analysis ---
Write-Host "`n=== Exporting System Info ==="
msinfo32 /report "$env:USERPROFILE\Desktop\SystemInfo.txt"
Write-Host "System info saved to Desktop as SystemInfo.txt"

# --- Step 11: Check CPU temperature (requires OpenHardwareMonitor or LibreHardwareMonitor) ---
Write-Host "`n=== Note: For real-time temperature monitoring, run HWiNFO64 ==="
Write-Host "Download: https://www.hwinfo.com/download/"

# --- Step 12: Disable Driver Verifier if it was accidentally left on (can cause BSODs) ---
# Uncomment if you suspect Driver Verifier is causing BSODs:
# verifier /reset
# Write-Host "Driver Verifier disabled. Reboot required."

Write-Host "`n=== Diagnostic Complete. Review output above for issues. ==="
Write-Host "Next steps: Analyze minidump files with WhoCrashed (free) or WinDbg."
Write-Host "WhoCrashed download: https://www.resplendence.com/whoCrashed"

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems specialists with over a decade of experience diagnosing hardware and software failures in enterprise and consumer environments. Our guides are grounded in real-world troubleshooting, official Microsoft documentation, and community-validated fixes. We specialize in turning cryptic error codes into clear, actionable solutions.

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.