Computer Keeps Blue Screening Windows 10: Complete BSOD Fix Guide

Understanding Why Windows 10 Keeps Blue Screening

A Blue Screen of Death (BSOD) — technically a STOP error — occurs when Windows encounters a critical failure it cannot recover from safely. The system halts to prevent data corruption or hardware damage. On Windows 10, the blue screen typically displays:

• A sad face emoji and the message: "Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you."
• A STOP code such as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, or KERNEL_SECURITY_CHECK_FAILURE.
• A QR code (on newer builds) linking to Microsoft support for that specific code.
• A fault module name (e.g., ntoskrnl.exe, nvlddmkm.sys, ataport.sys).

If your computer keeps blue screening on Windows 10, the first step is always to capture the STOP code and the faulting module. Everything else flows from that information.

Step 1: Capture and Decode the STOP Code

During the BSOD, photograph the screen with your phone before the PC restarts. You need:

1. The STOP code (e.g., 0x0000001E or the text version like KMODE_EXCEPTION_NOT_HANDLED).
2. The faulting file name (listed after the STOP code, e.g., nvlddmkm.sys = NVIDIA driver).

After restart, check the Windows Event Log and minidump files:

1. Press Win + X → select Event Viewer.
2. Navigate to Windows Logs → System.
3. Filter by Error and look for events with Source BugCheck or Kernel-Power (Event ID 41).
4. Minidump files are stored at C:\Windows\Minidump\ — these are the gold standard for BSOD analysis.

Common STOP codes and their primary causes:

Step 2: Run System File Checker and DISM

Corrupted Windows system files are a very common cause of recurring BSODs. Run these commands in an elevated Command Prompt (right-click Start → Command Prompt (Admin) or Windows PowerShell (Admin)):

sfc /scannow

Wait for the scan to complete (5-15 minutes). If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them", run DISM first to repair the repair source:

DISM /Online /Cleanup-Image /RestoreHealth

Then re-run sfc /scannow. Restart the PC after completion.

Step 3: Update or Roll Back Drivers

Drivers are the #1 software cause of Windows 10 BSODs. The faulting .sys file name on the blue screen tells you which driver to target:

• nvlddmkm.sys → NVIDIA graphics driver
• atikmdag.sys / amdkmdag.sys → AMD graphics driver
• iaStorA.sys → Intel Rapid Storage Technology driver
• ntoskrnl.exe → Usually RAM, overclocking, or a driver conflict (not the kernel itself)
• win32kfull.sys → Windows graphics subsystem (often a display driver issue)

To roll back a driver:

1. Press Win + X → Device Manager.
2. Right-click the suspect device → Properties → Driver tab.
3. Click Roll Back Driver if available.

To update all drivers, use Windows Update (Settings → Update & Security → View Optional Updates → Driver Updates) or download directly from the manufacturer's website (NVIDIA, AMD, Intel, Dell, HP, Lenovo, etc.).

Step 4: Test Your RAM

If the STOP code is MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, or the BSODs are completely random with different codes each time, RAM is a prime suspect.

Built-in Windows Memory Diagnostic:

1. Press Win + R → type mdsched.exe → Enter.
2. Choose Restart now and check for problems.
3. The tool runs on reboot. Check results in Event Viewer → Windows Logs → System, filtering for Source MemoryDiagnostics-Results.

For more thorough testing, boot from a USB drive running MemTest86 (free, open-source) and run at least 2 full passes. Any errors = faulty RAM that needs replacement.

Step 5: Check Your Hard Drive or SSD

Storage failures cause BSODs with codes like NTFS_FILE_SYSTEM, PAGE_FAULT_IN_NONPAGED_AREA, and 0x0000007A (KERNEL_DATA_INPAGE_ERROR).

Run Check Disk:

chkdsk C: /f /r /x

(You'll be prompted to schedule this on next restart — type Y and restart.)

Also check your drive's S.M.A.R.T. status using CrystalDiskInfo (free) or in PowerShell:

Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, ReadErrorsTotal, WriteErrorsTotal, Temperature

Step 6: Check for Overheating

Thermal issues cause WHEA_UNCORRECTABLE_ERROR and random BSODs under load. Use HWMonitor or Core Temp to monitor CPU/GPU temperatures. Safe operating ranges:

• CPU: below 85°C under full load
• GPU: below 90°C under full load

If temperatures are too high: clean dust from vents and fans, reapply thermal paste (for laptops that are 2+ years old), and ensure the device is on a hard flat surface.

Step 7: Analyze Minidump Files with WinDbg

For recurring BSODs with no obvious cause, minidump analysis with WinDbg gives definitive answers:

1. Install WinDbg from the Microsoft Store or Windows SDK.
2. Open WinDbg → File → Open Crash Dump → navigate to C:\Windows\Minidump\ → open the most recent .dmp file.
3. In the command window, type: !analyze -v
4. Look for MODULE_NAME, FAULTING_MODULE, and STACK_TEXT in the output.

This output will directly name the driver or process responsible for the crash.

Step 8: Perform a System Restore or Reset

If BSODs started after a Windows Update or software installation:

1. Press Win + R → type rstrui.exe → follow the wizard to a restore point before the BSODs began.

If no restore point is available and nothing else works:

1. Go to Settings → Update & Security → Recovery.
2. Under Reset this PC, click Get started.
3. Choose Keep my files (safest option) or Remove everything for a clean slate.

Special Case: Laptop Keeps Blue Screening on Battery

If your laptop keeps blue screening specifically on battery power, the issue is often:

• A failing battery causing voltage fluctuations (replace the battery).
• Power management driver conflicts — update the ACPI driver via Device Manager.
• Fast Startup causing hibernation corruption: disable via Control Panel → Power Options → Choose what the power buttons do → uncheck Turn on fast startup.