Computer Keeps Blue Screening Windows 10: Complete Fix Guide (BSOD Troubleshooting)
Fix Windows 10 blue screen of death (BSOD) errors fast. Step-by-step guide covering driver issues, RAM faults, overheating, and system file corruption.
- Corrupt or incompatible device drivers are the #1 cause of repeated BSODs on Windows 10 — especially after Windows Updates or new hardware installs.
- Faulty RAM modules cause random, unpredictable blue screens — run Windows Memory Diagnostic or MemTest86 to confirm hardware failure.
- Overheating CPUs and GPUs trigger thermal-protection shutdowns that appear as BSODs — clean dust from vents and reapply thermal paste if temps exceed 90°C.
- System file corruption from sudden power loss or disk errors causes BSODs — run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' to repair.
- Quick fix: Boot into Safe Mode, note the stop code on the blue screen (e.g., SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL), check Event Viewer, then target the specific driver or hardware causing the crash.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update/Rollback Drivers | BSOD started after driver or Windows Update | 10-30 min | Low |
| SFC + DISM Repair | BSOD with SYSTEM_SERVICE_EXCEPTION or CRITICAL_PROCESS_DIED | 20-45 min | Low |
| Windows Memory Diagnostic / MemTest86 | Random BSODs with no consistent stop code, especially after RAM upgrade | 30 min – 8 hrs | Low |
| Check Disk (chkdsk) | BSOD with NTFS_FILE_SYSTEM or BAD_SYSTEM_CONFIG_INFO | 15-60 min | Low-Medium |
| Thermal Monitoring + Cleaning | BSOD under load (gaming, rendering), PC feels hot | 30-60 min | Low |
| System Restore | BSOD started recently after software/update install | 15-30 min | Low-Medium |
| Clean Windows 10 Install | All other fixes failed, hardware confirmed healthy | 1-2 hrs | High (data loss) |
Understanding Why Your Computer Keeps Blue Screening on Windows 10
A Blue Screen of Death (BSOD) — officially called a Stop Error — occurs when Windows 10 encounters a fatal system error it cannot recover from safely. The OS halts to prevent data corruption or hardware damage. If your computer or laptop keeps blue screening on Windows 10, it means something is consistently triggering that fatal condition.
The blue screen always displays a stop code (e.g., MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, PAGE_FAULT_IN_NONPAGED_AREA) and typically a QR code linking to Microsoft's support pages. The stop code is your primary diagnostic clue — always write it down or photograph it before rebooting.
Windows 10 also writes a memory dump file to C:\Windows\Minidump\ after every BSOD, which you can analyze with tools like WinDbg or BlueScreenView.
Step 1: Capture the Stop Code and Check Event Viewer
If your screen flashes too quickly, disable automatic restart so you can read the stop code:
- Right-click This PC → Properties → Advanced system settings
- Under Startup and Recovery, click Settings
- Uncheck Automatically restart
- Click OK
After the next BSOD, note the exact stop code displayed. Then boot normally and check Event Viewer:
- Press Win + X → Event Viewer
- Navigate to Windows Logs → System
- Filter for Critical and Error events around the time of the crash
- Look for sources like
BugCheck,Kernel-Power, ordisk
Alternatively, use BlueScreenView (free tool by NirSoft) to parse minidump files and identify the faulting driver or module.
Step 2: Update or Roll Back Device Drivers
Driver conflicts are the single most common cause of repeated Windows 10 BSODs. This is especially true for GPU drivers (NVIDIA, AMD), network adapters, and USB controllers.
To update drivers:
- Press Win + X → Device Manager
- Look for any devices with a yellow warning triangle
- Right-click the device → Update driver → Search automatically
- Also visit your GPU manufacturer's site (nvidia.com or amd.com) for the latest drivers
To roll back a driver (if BSOD started after an update):
- In Device Manager, right-click the device → Properties
- Click the Driver tab → Roll Back Driver
For display drivers specifically, use DDU (Display Driver Uninstaller) in Safe Mode for a completely clean removal before reinstalling.
Step 3: Run System File Checker and DISM
Corrupt Windows system files are a frequent BSOD trigger. Run these commands in an elevated Command Prompt (right-click Start → Windows PowerShell (Admin)):
sfc /scannow
Wait for it to complete — it will report whether it found and repaired corrupt files. Then run DISM to repair the Windows image itself:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
Reboot after both commands complete, even if no errors were found.
Step 4: Test Your RAM
Faulty RAM is a silent killer that causes unpredictable BSODs. Common stop codes indicating RAM issues include: MEMORY_MANAGEMENT, BAD_POOL_HEADER, PAGE_FAULT_IN_NONPAGED_AREA.
Windows Memory Diagnostic (built-in):
- Press Win + R, type
mdsched.exe, press Enter - Choose Restart now and check for problems
- Windows will run the test on reboot and display results
For more thorough testing, use MemTest86:
- Download from memtest86.com, create a bootable USB
- Boot from USB and run for at least 2 full passes (8+ passes recommended)
- Any errors = faulty RAM that needs replacement
If you have multiple RAM sticks, test them one at a time to isolate the faulty module.
Step 5: Check Your Hard Drive / SSD Health
Disk errors cause BSODs with codes like NTFS_FILE_SYSTEM, FAT_FILE_SYSTEM, and BAD_SYSTEM_CONFIG_INFO.
Run Check Disk in an elevated Command Prompt:
chkdsk C: /f /r /x
You'll be prompted to schedule it for the next reboot — type Y and restart. The scan can take 30-60 minutes.
For SSD health, download CrystalDiskInfo (free) to check S.M.A.R.T. data. Any Caution or Bad status means the drive is failing and should be replaced immediately.
Step 6: Monitor for Overheating
Overheating causes BSODs particularly during gaming, video rendering, or heavy CPU load. Download HWMonitor or Core Temp to check temperatures while under load.
- CPU safe range: Under 80°C under load
- GPU safe range: Under 85°C under load
- Danger zone: 90°C+ consistently = thermal throttling and potential BSOD
Fixes for overheating:
- Clean dust from all vents, heatsinks, and fans with compressed air
- Replace dried-out thermal paste on CPU (and GPU if comfortable)
- Ensure good case airflow (check fan directions)
- For laptops: use a cooling pad and elevate the rear
Step 7: Check for Malware
Rootkit-level malware can cause kernel panics that appear as BSODs. Run Malwarebytes (free) and Windows Defender Offline Scan:
- Open Windows Security → Virus & threat protection
- Click Scan options → Microsoft Defender Offline scan
- Click Scan now — this runs before Windows loads, catching deep-rooted malware
Step 8: Use System Restore
If BSODs started recently, System Restore can roll Windows back to a working state:
- Press Win + R, type
rstrui.exe, press Enter - Choose a restore point from before the BSODs started
- Follow the wizard — your personal files are not affected, but recent software and driver installs will be removed
Step 9: Reset or Reinstall Windows 10
If all else fails and hardware checks out, a clean install resolves persistent software-level BSODs:
- Go to Settings → Update & Security → Recovery
- Under Reset this PC, click Get started
- Choose Keep my files for a soft reset, or Remove everything for a full clean install
Alternatively, create a bootable Windows 10 USB from Microsoft's Media Creation Tool and perform a fresh install.
Common Stop Codes and Their Primary Causes
| Stop Code | Most Likely Cause |
|---|---|
| SYSTEM_SERVICE_EXCEPTION | Faulty driver or system file |
| IRQL_NOT_LESS_OR_EQUAL | Driver accessing wrong memory address |
| KERNEL_SECURITY_CHECK_FAILURE | Corrupt driver or RAM failure |
| MEMORY_MANAGEMENT | RAM hardware fault |
| PAGE_FAULT_IN_NONPAGED_AREA | RAM or driver bug |
| CRITICAL_PROCESS_DIED | Core Windows process crashed (often malware or corruption) |
| NTFS_FILE_SYSTEM | Hard drive/SSD failure or corruption |
| WHEA_UNCORRECTABLE_ERROR | Hardware failure (CPU, RAM, PSU) |
| DPC_WATCHDOG_VIOLATION | SSD firmware, driver, or Windows Update issue |
Frequently Asked Questions
# ============================================================
# Windows 10 BSOD Diagnostic & Repair Script
# Run as Administrator in PowerShell
# ============================================================
# --- 1. Get recent BSOD events from Event Log ---
Write-Host "`n=== Recent Blue Screen Events ==="
Get-WinEvent -LogName System -MaxEvents 500 | Where-Object {
$_.Id -eq 41 -or $_.Id -eq 1001
} | Select-Object TimeCreated, Id, Message | Format-Table -AutoSize
# --- 2. List minidump files (BSOD crash dumps) ---
Write-Host "`n=== Minidump Files (BSOD Crash Reports) ==="
if (Test-Path 'C:\Windows\Minidump') {
Get-ChildItem 'C:\Windows\Minidump' | Sort-Object LastWriteTime -Descending |
Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}} |
Format-Table -AutoSize
} else {
Write-Host "No minidump folder found. Ensure small memory dumps are enabled."
}
# --- 3. Run System File Checker ---
Write-Host "`n=== Running SFC (System File Checker) ==="
sfc /scannow
# --- 4. Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth
Write-Host "`n=== Running DISM Scan ==="
DISM /Online /Cleanup-Image /ScanHealth
Write-Host "`n=== Running DISM Restore (may take 10-20 min) ==="
DISM /Online /Cleanup-Image /RestoreHealth
# --- 5. Schedule Check Disk on next reboot ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
echo Y | chkdsk C: /f /r /x
# --- 6. Check for driver issues in Device Manager ---
Write-Host "`n=== Devices with Errors or Warnings ==="
Get-WmiObject Win32_PnPEntity | Where-Object {
$_.ConfigManagerErrorCode -ne 0
} | Select-Object Name, ConfigManagerErrorCode, DeviceID | Format-Table -AutoSize
# --- 7. Check current temperatures (requires Open Hardware Monitor WMI)
# Install OpenHardwareMonitor first, then run as admin to expose WMI
Write-Host "`n=== Temperature Check (requires OpenHardwareMonitor) ==="
try {
$temps = Get-WmiObject -Namespace root/OpenHardwareMonitor -Class Sensor |
Where-Object { $_.SensorType -eq 'Temperature' }
$temps | Select-Object Name, Value | Format-Table -AutoSize
} catch {
Write-Host "OpenHardwareMonitor WMI not available. Download from openhardwaremonitor.org"
}
# --- 8. Check RAM status ---
Write-Host "`n=== RAM Module Information ==="
Get-WmiObject Win32_PhysicalMemory | Select-Object BankLabel, Capacity, Speed, Manufacturer | Format-Table -AutoSize
Write-Host "To test RAM: Press Win+R, type mdsched.exe, choose 'Restart now and check for problems'"
# --- 9. Check disk health via SMART data ---
Write-Host "`n=== Disk Drive Status ==="
Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus |
Select-Object InstanceName, PredictFailure, Reason | Format-Table -AutoSize
# --- 10. List recently installed drivers (last 30 days) ---
Write-Host "`n=== Recently Installed/Updated Drivers (last 30 days) ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WmiObject Win32_PnPSignedDriver | Where-Object {
$_.DriverDate -and ([datetime]::ParseExact(
$_.DriverDate.Substring(0,8), 'yyyyMMdd', $null) -gt $cutoff)
} | Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer |
Sort-Object DriverDate -Descending | Format-Table -AutoSize
Write-Host "`n=== Diagnostics Complete. Check output above for issues. ==="
Write-Host "Next steps: Review BlueScreenView for minidump analysis, run MemTest86 for RAM."Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing and resolving OS-level failures, kernel panics, and hardware faults across enterprise and consumer environments. Our guides are built from real-world incident post-mortems, Microsoft documentation, and hands-on lab testing.
Sources
- https://support.microsoft.com/en-us/windows/troubleshoot-blue-screen-errors-5c62a79a-9b35-f0de-5bd3-2b71c69a6bef
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://answers.microsoft.com/en-us/windows/forum/all/windows-10-blue-screen-of-death-bsod-troubleshoot/
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-image-management-command-line-options-s14
- https://www.memtest86.com/technical.htm