Computer Keeps Blue Screening Windows 10: Complete Fix Guide (BSOD Troubleshooting)
Fix Windows 10 blue screen of death (BSOD) crashes fast. Step-by-step guide covering driver issues, RAM faults, disk errors, and more — with real commands.
- Outdated, corrupt, or incompatible device drivers are the #1 cause of repeated BSOD crashes on Windows 10 — especially after updates or new hardware installs.
- Faulty RAM, overheating hardware, corrupt system files, and failing hard drives are other leading hardware-level root causes of persistent blue screens.
- Quick-fix sequence: note the STOP error code on the BSOD, run 'sfc /scannow' and DISM to repair system files, update or roll back recent drivers, run Windows Memory Diagnostic, check disk health with CHKDSK, then review Event Viewer and minidump files for pinpoint diagnosis.
- Laptop-specific causes include thermal throttling due to blocked vents, faulty battery firmware, and aggressive power-saving driver conflicts — check temperatures first on portable devices.
- If software fixes fail, resetting Windows 10 or performing a clean install is the nuclear option that resolves nearly all persistent BSOD scenarios.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Run SFC & DISM (system file repair) | Corrupt or missing Windows system files after update or malware | 10–30 min | Low |
| Update or roll back drivers | BSOD started after Windows Update, driver install, or new hardware | 5–20 min | Low |
| Windows Memory Diagnostic / MemTest86 | Random BSODs with MEMORY_MANAGEMENT or IRQL errors, no clear pattern | 30 min – 8 hrs | None |
| CHKDSK disk scan | BSODs related to disk I/O, boot failures, or storage-related STOP codes | 15–60 min | Low (read-only by default) |
| Check & clean cooling system | Laptop keeps blue screening under load, high CPU/GPU temps, thermal BSOD | 10–30 min | Low |
| Uninstall recent Windows Update | BSOD began immediately after a specific Patch Tuesday update | 5–15 min | Medium |
| Boot into Safe Mode | Cannot reach desktop at all due to BSOD boot loop | 5 min | None |
| Reset Windows 10 (keep files) | All software fixes failed, BSODs persist across driver reinstalls | 1–2 hrs | Medium |
| Clean install Windows 10 | Suspected deep OS corruption, persistent BSOD even after Reset | 2–4 hrs | High (data loss risk) |
Understanding Why Your Computer Keeps Blue Screening on Windows 10
A Blue Screen of Death (BSOD) — technically called a Stop Error or Bug Check — occurs when Windows 10 encounters a fatal system error from which it cannot safely recover. Instead of risking data corruption by continuing, the OS halts completely and displays a blue screen with a sad face emoji and a STOP code like:
CRITICAL_PROCESS_DIEDSYSTEM_THREAD_EXCEPTION_NOT_HANDLEDIRQL_NOT_LESS_OR_EQUALMEMORY_MANAGEMENTPAGE_FAULT_IN_NONPAGED_AREAKERNEL_SECURITY_CHECK_FAILUREVIDEO_TDR_FAILURENTFS_FILE_SYSTEMDRIVER_POWER_STATE_FAILURE
If your computer or laptop keeps blue screening on Windows 10 repeatedly — especially at boot, under load, or at random intervals — it signals an underlying hardware or software problem that needs systematic diagnosis.
Step 1: Read and Record the STOP Error Code
The most important first step is capturing the exact error code displayed on the blue screen. Windows 10 BSODs show:
- A large sad-face emoji
- A plain-English description (e.g., "Your PC ran into a problem and needs to restart")
- A STOP code in ALL_CAPS format (e.g.,
DRIVER_IRQL_NOT_LESS_OR_EQUAL) - Sometimes a specific file name causing the crash (e.g.,
nvlddmkm.sys— Nvidia driver)
If the screen disappears too fast, go to Settings → System → About → Advanced system settings → Startup and Recovery → Settings, and uncheck "Automatically restart" under System Failure. This keeps the BSOD on screen until you manually restart.
Alternatively, after the crash, open Event Viewer (run eventvwr.msc) and navigate to Windows Logs → System, filtering for Critical or Error events to find the BSOD record.
Step 2: Analyze Minidump Files
Every BSOD generates a small memory dump file. These are your diagnostic goldmine.
Location: C:\Windows\Minidump\
Use Microsoft's free WinDbg Preview tool (available via Microsoft Store) or the BlueScreenView utility (NirSoft — free) to analyze these .dmp files. BlueScreenView instantly shows:
- The date/time of each crash
- The exact STOP code
- The driver or module that caused the crash
- The crash address in memory
This single step often pinpoints a specific .sys file — usually a driver — responsible for the repeated BSOD.
Step 3: Repair Windows System Files (SFC & DISM)
Corrupt Windows system files can trigger persistent BSODs, especially after failed updates or malware infections.
Run System File Checker first:
sfc /scannow
This scans all protected system files and replaces corrupted ones. Run from an elevated Command Prompt (right-click Start → Windows PowerShell (Admin)).
If SFC reports it cannot fix all errors, run DISM to repair the Windows image itself:
DISM /Online /Cleanup-Image /RestoreHealth
Then run SFC again after DISM completes.
Restart and monitor for BSODs.
Step 4: Update, Roll Back, or Reinstall Drivers
Drivers are the leading software cause of BSOD crashes. If your computer started blue screening after a Windows Update or a new hardware installation, a driver conflict is highly likely.
To roll back a driver:
- Right-click Start → Device Manager
- Expand the category (e.g., Display adapters, Network adapters)
- Right-click the device → Properties → Driver tab → Roll Back Driver
To update drivers: Use Device Manager's Update Driver option, or go directly to your hardware manufacturer's website:
- Nvidia: https://www.nvidia.com/drivers
- AMD: https://www.amd.com/support
- Intel: https://www.intel.com/content/www/us/en/download-center/home.html
Critical: If BlueScreenView identified a specific .sys file (e.g., nvlddmkm.sys for Nvidia, iaStorA.sys for Intel storage), target that driver specifically.
For display driver issues, try a clean reinstall using DDU (Display Driver Uninstaller) in Safe Mode before installing fresh drivers.
Step 5: Test Your RAM
Faulty RAM is a notoriously difficult-to-diagnose cause of random, pattern-less BSODs — especially errors like MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, and PAGE_FAULT_IN_NONPAGED_AREA.
Windows Memory Diagnostic (built-in):
- Press Win+R → type
mdsched.exe→ Enter - Choose "Restart now and check for problems"
- Windows will run the test during the next boot and report results
MemTest86 (more thorough): Download from https://www.memtest86.com, create a bootable USB, and run at least 2 full passes (8+ passes recommended for complete confidence).
If errors are found:
- If you have 2 RAM sticks, remove one at a time and test each stick individually
- Reseat RAM sticks (remove, clean contacts gently, reinsert firmly)
- Replace faulty RAM module(s)
Step 6: Check Disk Health with CHKDSK
A failing hard drive or SSD with bad sectors can cause BSODs like NTFS_FILE_SYSTEM, CRITICAL_PROCESS_DIED, or disk I/O related errors.
chkdsk C: /f /r /x
This command requires a restart to run on the active drive. It will scan for and attempt to repair bad sectors, fix file system errors, and flag failing disk areas.
For SSD health, also check with the manufacturer's tool:
- Samsung: Samsung Magician
- WD/SanDisk: WD Dashboard
- Crucial: Crucial Storage Executive
- Or use CrystalDiskInfo (free) for all drive brands
Step 7: Check Temperatures (Critical for Laptops)
If your laptop keeps blue screening — especially during gaming, video editing, or other intensive tasks — thermal throttling and overheating are prime suspects.
Download HWMonitor or Core Temp and monitor:
- CPU temperature: Should stay below 90°C under load (ideally under 80°C)
- GPU temperature: Should stay below 85°C under load
If temperatures are high:
- Clean the laptop vents with compressed air
- Ensure the laptop is on a hard, flat surface (not a bed or cushion)
- Consider repasting the CPU/GPU thermal compound if the laptop is 3+ years old
- Use a laptop cooling pad
Step 8: Uninstall Problematic Windows Updates
If blue screens started after a specific Windows Update, roll it back:
- Settings → Update & Security → Windows Update → View Update History
- Click "Uninstall updates"
- Sort by date, find the most recent update, right-click → Uninstall
For cumulative updates that won't uninstall through the GUI, use DISM:
dism /online /get-packages
dism /online /remove-package /packagename:[PackageName]
Step 9: Reset or Clean Install Windows 10
If all the above steps fail to resolve persistent BSODs, a Windows Reset or clean install is the definitive software-level fix.
Reset (keeps personal files option available): Settings → Update & Security → Recovery → Reset this PC → Keep my files
Clean install: Download the Windows 10 Media Creation Tool from Microsoft, create a bootable USB, and perform a fresh installation. Back up all data first.
When Hardware Replacement is Required
If BSODs persist after a clean Windows install, the problem is definitively hardware:
- Failed RAM → Replace the affected DIMM
- Dying hard drive/SSD → Replace storage device
- Failing GPU → Replace or use integrated graphics
- Motherboard fault → Professional repair or replacement required
- Overheating CPU → Professional repaste or cooler replacement
Boot Loop: How to Reach Safe Mode When You Can't Boot
If the BSOD occurs before Windows loads, interrupt the boot process 3 times (by holding the power button during startup) to trigger Windows Recovery Environment (WinRE). Then navigate to:
Troubleshoot → Advanced Options → Startup Settings → Restart → Press 4 for Safe Mode or 5 for Safe Mode with Networking
From Safe Mode, you can uninstall drivers, run SFC/DISM, and perform most of the fixes listed above.
Frequently Asked Questions
# ============================================================
# Windows 10 BSOD Diagnostic & Fix Script
# Run from elevated PowerShell (Run as Administrator)
# ============================================================
# --- 1. Display recent BSOD events from Event Log ---
Write-Host "=== Recent BSOD Events (Last 30 days) ==" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001; StartTime=(Get-Date).AddDays(-30)} |
Select-Object TimeCreated, Id, Message |
Format-List
# --- 2. List minidump files for analysis ---
Write-Host "
=== Minidump Files Found ==" -ForegroundColor Cyan
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
Get-ChildItem $dumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending |
Select-Object Name, LastWriteTime, @{N="SizeMB";E={[math]::Round($_.Length/1MB,2)}}
} else {
Write-Host "No minidump folder found. Ensure small memory dumps are enabled." -ForegroundColor Yellow
}
# --- 3. Enable small memory dumps (if not already enabled) ---
Write-Host "
=== Enabling Small Memory Dumps ==" -ForegroundColor Cyan
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl"
Set-ItemProperty -Path $regPath -Name "CrashDumpEnabled" -Value 3 # 3 = Small memory dump
Set-ItemProperty -Path $regPath -Name "AutoReboot" -Value 0 # Disable auto-restart on BSOD
Set-ItemProperty -Path $regPath -Name "MinidumpDir" -Value "%SystemRoot%\Minidump"
Write-Host "Small memory dumps enabled. Auto-restart disabled." -ForegroundColor Green
# --- 4. Run System File Checker ---
Write-Host "
=== Running SFC (System File Checker) ==" -ForegroundColor Cyan
Write-Host "This may take 10-20 minutes..."
sfc /scannow
# --- 5. Run DISM to repair Windows image ---
Write-Host "
=== Running DISM Health Restore ==" -ForegroundColor Cyan
Write-Host "This may take 10-30 minutes and requires internet..."
DISM /Online /Cleanup-Image /RestoreHealth
# --- 6. Check disk for errors (schedules on next reboot) ---
Write-Host "
=== Scheduling CHKDSK on next reboot ==" -ForegroundColor Cyan
# Uncomment the line below to schedule (requires restart to run on C:)
# chkdsk C: /f /r /x
Write-Host "To run CHKDSK, execute: chkdsk C: /f /r /x (requires restart)"
# --- 7. Check for driver verifier issues ---
Write-Host "
=== Current Driver Verifier Status ==" -ForegroundColor Cyan
verifier /query
# --- 8. List recently installed drivers ---
Write-Host "
=== Drivers Installed in Last 30 Days ==" -ForegroundColor Cyan
Get-WinEvent -LogName System | Where-Object {
$_.Id -eq 7045 -and $_.TimeCreated -gt (Get-Date).AddDays(-30)
} | Select-Object TimeCreated, Message | Format-List
# --- 9. Check system temperatures via WMI (basic check) ---
Write-Host "
=== CPU Temperature Check (WMI) ==" -ForegroundColor Cyan
try {
$temp = Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace "root/wmi" -ErrorAction Stop
foreach ($t in $temp) {
$celsius = ($t.CurrentTemperature - 2732) / 10
Write-Host "Thermal Zone: $($t.InstanceName) -- $celsius C"
}
} catch {
Write-Host "WMI thermal query not supported on this hardware. Use HWMonitor or Core Temp app instead." -ForegroundColor Yellow
}
# --- 10. Export full system info for analysis ---
Write-Host "
=== Exporting System Info to C:\BSODReport.txt ==" -ForegroundColor Cyan
Get-ComputerInfo | Out-File "C:\BSODReport.txt" -Encoding UTF8
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-7)} |
Select-Object TimeCreated, Id, ProviderName, Message |
Export-Csv "C:\BSODEvents.csv" -NoTypeInformation
Write-Host "Report saved to C:\BSODReport.txt and C:\BSODEvents.csv" -ForegroundColor Green
Write-Host "
=== Diagnostic Complete. Review output above and check C:\ for saved reports. ==" -ForegroundColor Cyan
# ============================================================
# MANUAL STEPS REMINDER:
# 1. Open BlueScreenView (NirSoft) to analyze .dmp files
# 2. Check Device Manager for driver warnings (yellow !/red X)
# 3. Run Windows Memory Diagnostic: mdsched.exe
# 4. Update BIOS/UEFI from manufacturer website
# 5. Run MemTest86 from bootable USB for deep RAM testing
# ============================================================Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SRE professionals, and Windows system administrators with 10+ years of hands-on experience diagnosing and resolving operating system failures across enterprise and consumer environments. Our guides are built from real-world incident postmortems, manufacturer documentation, and validated diagnostic workflows — not generic advice. We specialize in Windows internals, hardware fault diagnosis, and practical recovery procedures that work without specialized tools.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-bsod-b53d1b38-8be9-48a0-8b0b-bd22ddf8e62d
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/download-the-wdk
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-bsod-on-windows-10/
- https://www.memtest86.com/
- https://stackoverflow.com/questions/tagged/windows-10+bsod