Why does my Windows 11 PC keep blue screening randomly with no pattern?

Random, unpredictable BSODs with varying stop codes usually point to failing RAM, a failing power supply delivering unstable voltage, or a corrupted Windows installation. Start by running Windows Memory Diagnostic (mdsched.exe) and MemTest86 for RAM. Check your PSU by testing with a known-good unit if possible. Run SFC /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair corrupted system files. Check Event Viewer (Event ID 41 and 1001) to see if any pattern exists in timing or specific process names.

My laptop keeps blue screening on Windows 11 — is it different from a desktop BSOD?

The diagnostic process is the same, but laptops have additional risk factors: overheating is more common due to compact designs and dust accumulation in slim vents, and laptop RAM is often soldered making replacement impossible. On a laptop, prioritize thermal checks using HWiNFO64 and clean vents with compressed air. Also check for manufacturer-specific driver updates (Dell, HP, Lenovo, ASUS all have their own driver update utilities). Battery driver issues can also cause BSODs on laptops — try running plugged in only and see if crashes stop.

Windows 11 started blue screening after an update — how do I fix it?

Go to Settings → Windows Update → Update History → Uninstall updates. Identify the most recently installed Cumulative Update or driver update by date and uninstall it. If the update cannot be uninstalled from Settings, boot into Windows Recovery Environment (WinRE) by holding Shift while clicking Restart, then go to Troubleshoot → Advanced Options → Uninstall Updates. You can also use the command: wusa /uninstall /kb:XXXXXXX (replace XXXXXXX with the KB number). After uninstalling, pause Windows Update temporarily while Microsoft releases a fix.

What does WHEA_UNCORRECTABLE_ERROR mean in Windows 11?

WHEA_UNCORRECTABLE_ERROR (stop code 0x00000124) stands for Windows Hardware Error Architecture Uncorrectable Error. It indicates a hardware-level failure — most commonly CPU instability (often from overclocking or failing silicon), RAM errors, or a failing PCIe device. Steps to fix: (1) Disable any overclocking in BIOS and reset to default settings. (2) Run MemTest86 for RAM. (3) Check CPU temperatures and reapply thermal paste if the CPU is old. (4) Update BIOS/UEFI firmware from your motherboard manufacturer. (5) Test with one RAM stick at a time.

How do I read a Windows 11 minidump file to find what caused the BSOD?

Minidump files are stored at C:\Windows\Minidump\ with .dmp extensions. Install WinDbg from the Microsoft Store (free). Open WinDbg, go to File → Open crash dump, select the .dmp file. Type the command: !analyze -v in the command window and press Enter. Look for FAILURE_BUCKET_ID and IMAGE_NAME fields — these typically name the responsible driver or module. Alternatively, use the free tool WhoCrashed (by Resplendence) which analyzes minidumps automatically and provides human-readable summaries without needing to use WinDbg manually.

Windows 11 Keeps Blue Screening (BSOD): Complete Fix Guide

Fix Windows 11 blue screen of death errors fast. Diagnose drivers, RAM, and corrupt files using built-in tools and PowerShell commands. Step-by-step guide.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,276 words

Key Takeaways

Faulty or incompatible device drivers are the #1 cause of repeated BSODs in Windows 11, especially after major updates or new hardware installation.
Corrupted system files, failing RAM, and overheating hardware are other primary root causes of persistent blue screen crashes.
Quick fixes include running SFC /scannow and DISM commands, updating or rolling back drivers, checking Event Viewer for the stop code, and running Windows Memory Diagnostic to rule out RAM failure.
If BSODs started after a Windows Update, rolling back the update or performing a clean driver install via Device Manager resolves the issue in most cases.
Persistent BSODs with hardware-related stop codes (e.g., WHEA_UNCORRECTABLE_ERROR, MEMORY_MANAGEMENT) may indicate failing hardware requiring physical inspection or replacement.

Fix Approaches Compared
Method	When to Use	Time	Risk
Run SFC & DISM scans	Corrupted system files suspected; Windows Update recently failed	10-20 min	Low
Update or roll back drivers	BSOD started after driver or hardware change; stop code names a driver file	5-15 min	Low
Windows Memory Diagnostic	Random BSODs with MEMORY_MANAGEMENT or PAGE_FAULT stop codes	30-60 min	None
Check Event Viewer / minidump	Unknown stop code; need to identify root cause before acting	5-10 min	None
Disable Fast Startup	BSODs occur mainly on cold boot or wake from sleep/hibernate	2 min	None
Uninstall recent Windows Update	BSODs began after a specific Cumulative Update (CU)	10-15 min	Low
Reset Windows 11 (keep files)	All software fixes exhausted; system unstable; no hardware fault found	60-120 min	Medium
Replace hardware (RAM/SSD)	MemTest86 or hardware diagnostics confirm physical failure	Varies	High if DIY

Understanding Windows 11 Blue Screen Errors

A Blue Screen of Death (BSOD) — technically called a Stop Error — occurs when Windows 11 encounters a critical fault it cannot safely recover from. The system halts completely to prevent data corruption and displays a blue screen with a stop code (also called a bug check code), a brief description, and sometimes a QR code. Common stop codes you might see include:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — usually a faulty driver
KMODE_EXCEPTION_NOT_HANDLED — kernel-mode driver or hardware conflict
WHEA_UNCORRECTABLE_ERROR — hardware error, often CPU, RAM, or overclocking instability
MEMORY_MANAGEMENT — RAM issues or driver memory corruption
PAGE_FAULT_IN_NONPAGED_AREA — driver or RAM accessing invalid memory
DRIVER_IRQL_NOT_LESS_OR_EQUAL — driver using incorrect interrupt levels
CRITICAL_PROCESS_DIED — essential Windows process terminated unexpectedly
NTFS_FILE_SYSTEM — storage driver or disk integrity issue

If your computer, laptop, or PC keeps blue screening on Windows 11, the first priority is capturing the exact stop code so you can narrow down the cause before applying fixes.

Step 1: Capture the Stop Code and Read the Minidump

From the Blue Screen itself: Note the stop code displayed in large text (e.g., MEMORY_MANAGEMENT) and any listed driver file (e.g., nvlddmkm.sys points to NVIDIA drivers).

From Event Viewer:

Press Win + X → select Event Viewer
Navigate to Windows Logs → System
Filter by Event ID 41 (unexpected shutdown) or Event ID 1001 (BugCheck)
Look for the BugCheck string, e.g., BugcheckCode 116 — convert hex to decimal or search the code directly

Read minidump files with WinDbg or PowerShell: Minidump files are saved at C:\Windows\Minidump\. Install WinDbg from the Microsoft Store to analyze them. Alternatively, use the PowerShell commands in the code block below.

Step 2: Run System File Checker and DISM

Corrupt Windows system files are a frequent cause of recurring BSODs. Run these commands in an elevated PowerShell or Command Prompt:

sfc /scannow

If SFC reports corruption it could not fix, follow up with DISM:

DISM /Online /Cleanup-Image /RestoreHealth

Restart the PC after both complete, then observe if the BSODs continue.

Step 3: Update or Roll Back Device Drivers

Drivers are the most common cause of Windows 11 BSODs. If the stop code names a .sys file, search for that filename to identify its associated driver.

To update drivers:

Press Win + X → Device Manager
Expand categories, right-click any device with a yellow warning icon → Update driver
For GPU drivers, always download directly from NVIDIA, AMD, or Intel rather than Windows Update
For a clean GPU driver install, use DDU (Display Driver Uninstaller) in Safe Mode before installing the new driver

To roll back a driver:

In Device Manager, right-click the device → Properties → Driver tab
Click Roll Back Driver if available
This is especially useful when BSODs started immediately after a driver update

Common problematic driver files and their sources:

nvlddmkm.sys → NVIDIA GPU driver
atikmpag.sys / atikmdag.sys → AMD GPU driver
igdkmd64.sys → Intel integrated graphics
ndis.sys → Network drivers
storport.sys → Storage controller drivers

Step 4: Check RAM with Windows Memory Diagnostic

For stop codes like MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, or WHEA_UNCORRECTABLE_ERROR, test your RAM:

Press Win + R, type mdsched.exe, press Enter
Choose Restart now and check for problems
The tool runs on next boot — let it complete two full passes
Results appear in Event Viewer under Windows Logs → System (Event ID 1201)

For more thorough testing, use MemTest86 (boot from USB) which runs independent of Windows and performs 13 different memory test algorithms.

If RAM errors are found:

Try reseating RAM sticks (power off, remove, reinsert firmly)
Test sticks individually if you have multiple
If one stick fails consistently, it needs replacement

Step 5: Check Storage Health

A failing SSD or HDD can cause NTFS_FILE_SYSTEM or CRITICAL_PROCESS_DIED BSODs. Use built-in SMART diagnostics:

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

Alternatively, download CrystalDiskInfo for a detailed SMART health report. Any attribute showing Caution or Bad status indicates a failing drive.

Step 6: Check for Overheating

Thermal throttling and overheating cause WHEA_UNCORRECTABLE_ERROR and CLOCK_WATCHDOG_TIMEOUT BSODs. Use HWiNFO64 or Core Temp to monitor temperatures under load. Safe temperature ranges:

CPU: below 90°C under load (85°C or lower is ideal)
GPU: below 85°C under load

If temperatures exceed safe limits:

Clean dust from heatsinks and fans (compressed air)
Reapply thermal paste on CPU (every 3-5 years)
Ensure proper case airflow
On laptops, use a cooling pad and avoid soft surfaces that block vents

Step 7: Disable Fast Startup

Windows 11's Fast Startup feature can cause driver state issues leading to BSODs on boot:

Open Control Panel → Power Options
Click Choose what the power buttons do
Click Change settings that are currently unavailable
Uncheck Turn on fast startup
Save changes and restart

Step 8: Uninstall Problematic Windows Updates

If BSODs began after a specific Windows Update:

Go to Settings → Windows Update → Update History
Click Uninstall updates
Identify the most recent update by date and uninstall it
Alternatively, use: wusa /uninstall /kb:XXXXXXX replacing XXXXXXX with the KB number

To temporarily pause future updates while troubleshooting: Settings → Windows Update → Pause updates

Step 9: Reset Windows 11 (Last Resort Software Fix)

If all software-based fixes fail and hardware checks out clean:

Go to Settings → System → Recovery
Click Reset this PC
Choose Keep my files to preserve personal data
Select Cloud download for fresh Windows files
Complete the wizard — this takes 1-2 hours

After reset, install drivers fresh before restoring any third-party software to establish a clean baseline.

When Is It a Hardware Problem?

Consider hardware replacement when:

MemTest86 shows RAM errors across multiple test passes
SMART data shows drive wear at 100% or read/write errors accumulating
BSODs occur even on a clean Windows install with minimal drivers
System crashes with WHEA_UNCORRECTABLE_ERROR even at stock clock speeds after thermal checks pass
The system is 5+ years old and has never had RAM or thermal paste serviced

Frequently Asked Questions

powershell

# ============================================================
# Windows 11 BSOD Diagnostic & Fix Script
# Run PowerShell as Administrator
# ============================================================

# --- 1. Check for recent BSODs in Event Log ---
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 1001 -and $_.Message -like '*BugCheck*'} | Select-Object TimeCreated, Message | Format-List

# --- 2. List minidump files with timestamps ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, @{N='Size_KB';E={[math]::Round($_.Length/1KB,1)}}

# --- 3. Run System File Checker ---
Write-Host "`n=== Running SFC Scan ==="
sfc /scannow

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

# --- 5. Check disk health via SMART ---
Write-Host "`n=== Storage SMART Health ==="
Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, ReadErrorsTotal, WriteErrorsTotal, Temperature, Wear | Format-Table -AutoSize

# --- 6. List all installed drivers with version info ---
Write-Host "`n=== Installed Drivers (sorted by date) ==="
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer | Sort-Object DriverDate -Descending | Select-Object -First 20 | Format-Table -AutoSize

# --- 7. Check for recently updated/installed drivers (last 30 days) ---
Write-Host "`n=== Drivers Updated in Last 30 Days ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DriverDate -gt $cutoff.ToString('yyyyMMdd000000.000000+000')} | Select-Object DeviceName, DriverVersion, DriverDate | Format-Table -AutoSize

# --- 8. Check system uptime and last boot ---
Write-Host "`n=== System Uptime ==="
$os = Get-CimInstance Win32_OperatingSystem
$uptime = (Get-Date) - $os.LastBootUpTime
Write-Host "Last Boot: $($os.LastBootUpTime)"
Write-Host "Uptime: $($uptime.Days)d $($uptime.Hours)h $($uptime.Minutes)m"

# --- 9. Check CPU temperature via WMI (may not work on all systems) ---
Write-Host "`n=== CPU Thermal Info (if supported) ==="
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace root/wmi -ErrorAction SilentlyContinue | ForEach-Object {
    $tempC = ($_.CurrentTemperature / 10) - 273.15
    Write-Host "Thermal Zone: $([math]::Round($tempC, 1)) C"
}

# --- 10. Disable Fast Startup via registry ---
# Uncomment to apply the fix:
# Write-Host "`n=== Disabling Fast Startup ==="
# Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power' -Name 'HiberbootEnabled' -Value 0
# Write-Host "Fast Startup disabled. Restart to apply."

# --- 11. Uninstall a specific Windows Update by KB number ---
# Replace KB5031354 with your target KB number
# Uncomment to apply:
# Write-Host "`n=== Uninstalling KB5031354 ==="
# wusa /uninstall /kb:5031354 /quiet /norestart

# --- 12. Export full event log for analysis ---
Write-Host "`n=== Exporting System Event Log to Desktop ==="
$exportPath = "$env:USERPROFILE\Desktop\SystemEvents_BSOD.evtx"
wevtutil epl System $exportPath
Write-Host "Log exported to: $exportPath"

Write-Host "`n=== Diagnostic Complete. Review output above. ==="

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of hands-on experience diagnosing and resolving operating system failures, BSOD errors, and hardware instability issues. Our guides are written using real diagnostic data, official Microsoft documentation, and community-validated solutions to give you the most accurate and actionable troubleshooting steps available.

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.