Why does my Windows 11 PC keep getting BSODs after a Windows Update?

Windows Updates can push new driver versions or patch kernel components that conflict with existing hardware or third-party software. After a BSOD caused by a Windows Update, open Settings → Windows Update → Update History → Uninstall Updates, and remove the most recently installed cumulative update or driver update. Alternatively, use Device Manager to roll back updated drivers. You can also pause updates temporarily via Settings → Windows Update → Pause Updates while waiting for Microsoft to release a fix.

What does the stop code IRQL_NOT_LESS_OR_EQUAL mean on Windows 11?

Stop code 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) means a driver or kernel process tried to access pageable memory at a raised IRQL (Interrupt Request Level) where only non-pageable memory is allowed. The most common causes are a newly installed or updated device driver, incompatible antivirus software, or failing RAM. To fix it: use WinDbg or WhoCrashed to identify the faulting .sys file from a minidump in C:\Windows\Minidump, then uninstall or roll back that driver. Also run Windows Memory Diagnostic to rule out bad RAM.

How do I fix BSOD on Windows 11 if the PC won't boot at all?

If your PC loops into a BSOD on every boot, force-power-cycle it three times to trigger Windows Recovery Environment (WinRE). From WinRE, go to Troubleshoot → Advanced Options and try: (1) Startup Repair — automatically fixes bootloader issues, (2) System Restore — reverts to a known good state, (3) Command Prompt — run 'sfc /scannow', 'chkdsk C: /f /r', or 'bootrec /fixmbr' and 'bootrec /fixboot' if BCD is corrupted. If none work, boot from a Windows 11 USB and perform a clean install.

Is WHEA_UNCORRECTABLE_ERROR a hardware problem on Windows 11?

Yes, WHEA_UNCORRECTABLE_ERROR (0x00000124) almost always indicates a hardware-level fault. It is reported by the Windows Hardware Error Architecture when the CPU, RAM, or motherboard encounters an uncorrectable error that cannot be resolved in software. Common causes include: CPU overclocking instability, failing RAM sticks, dying power supply delivering inconsistent voltages, or a faulty CPU. Steps: disable any overclocking in BIOS/UEFI, reseat RAM sticks (try one stick at a time), run MemTest86 overnight, and check PSU output with a multimeter or PSU tester. If the error persists after all of that, the CPU or motherboard may need replacement.

Do the same BSOD fixes work for Windows 8 and Windows Vista?

Most diagnostic approaches (Event Viewer, minidump analysis, SFC, CHKDSK, driver rollback, memory testing) apply across Windows Vista, 8, and 11. However, Windows Vista and Windows 8 reached End of Life and no longer receive security patches from Microsoft, which means many BSODs on those systems may be caused by unpatched vulnerabilities or driver incompatibilities that have no official fix. The DISM tool is available in Windows 8 but not Vista. For Vista, use the System File Checker (sfc /scannow) and the built-in Memory Diagnostic. The strongest recommendation for Vista and Windows 8 users is to upgrade to Windows 10 or 11 on supported hardware.

BSOD Windows 11: How to Fix Blue Screen of Death Errors (Stop Codes, Causes & Fixes)

Fix BSOD errors on Windows 11, 8, and Vista. Learn stop codes, root causes, and step-by-step fixes including driver rollback, memory tests, and SFC scans.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,323 words

Key Takeaways

Most BSODs in Windows 11 are caused by faulty, outdated, or incompatible device drivers — particularly GPU, NIC, and storage drivers updated after a major Windows feature update.
Hardware faults (bad RAM sticks, failing NVMe/SSD drives, overheating CPU) are the second most common root cause, especially when the stop code is MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, or CRITICAL_PROCESS_DIED.
Quick fix summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', check Event Viewer for the faulting module, roll back or uninstall the suspect driver, and run Windows Memory Diagnostic or MemTest86 if crashes persist.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM System File Repair	Corrupted Windows system files suspected; BSOD after Windows Update	15–30 min	Low
Driver Rollback / Uninstall	BSOD started after a driver or Windows Update; stop code references a .sys file	5–15 min	Low
Windows Memory Diagnostic / MemTest86	Stop code is MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, or random BSODs	30 min – 8 hrs	None
Startup Repair via WinRE	System won't boot at all; stuck in BSOD loop before login screen	10–20 min	Low
System Restore	BSOD began after a specific date; restore point exists before the issue	20–40 min	Medium (reverts software changes)
CHKDSK Drive Scan	Stop codes like NTFS_FILE_SYSTEM or BAD_SYSTEM_CONFIG_INFO; SSD/HDD suspected	20 min – 2 hrs	Low
Clean Boot / Safe Mode Isolation	Suspect a third-party service or startup app is causing the crash	10–30 min	Low
Reset This PC / Reinstall Windows	All other methods failed; system is critically unstable	1–3 hrs	High (data loss risk without backup)

Understanding BSOD Errors on Windows 11

A Blue Screen of Death (BSOD), technically called a Stop Error, occurs when Windows encounters a critical fault it cannot recover from. The operating system halts to prevent damage to hardware or data. On Windows 11, the screen typically displays a sad face emoji, a brief message like "Your PC ran into a problem and needs to restart", a stop code (e.g., CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL), and a QR code linking to Microsoft support.

The same fundamental BSOD architecture applies across Windows Vista, Windows 8, and Windows 11, though the visual presentation differs. Vista and 8 show a dense block of text with hexadecimal addresses, while Windows 10/11 simplify the screen for readability.

Common Windows 11 BSOD Stop Codes and Their Meanings

CRITICAL_PROCESS_DIED (0x000000EF) — A critical system process (e.g., smss.exe, csrss.exe, wininit.exe) terminated unexpectedly. Often caused by corrupted system files or malware.
IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — A driver attempted to access memory at an invalid IRQL level. Typically caused by a buggy third-party driver.
MEMORY_MANAGEMENT (0x0000001A) — Serious memory subsystem error. Points to bad RAM, corrupted page file, or driver memory mismanagement.
SYSTEM_SERVICE_EXCEPTION (0x0000003B) — Exception from a system service, commonly triggered by antivirus software or graphics drivers.
WHEA_UNCORRECTABLE_ERROR (0x00000124) — Windows Hardware Error Architecture detected an uncorrectable hardware error. CPU, RAM, or motherboard-level fault.
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — Invalid memory address accessed. Can be RAM, drivers, or antivirus interference.
NTFS_FILE_SYSTEM (0x00000024) — NTFS driver encountered an error, often indicating a failing drive.
BAD_SYSTEM_CONFIG_INFO (0x00000074) — Registry corruption or missing BCD (Boot Configuration Data) entries.
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — Specific driver attempted invalid memory access at elevated IRQL.
VIDEO_TDR_FAILURE (atikmpag.sys / nvlddmkm.sys) — GPU driver timeout; common with AMD (atikmpag.sys) or NVIDIA (nvlddmkm.sys) drivers.

Step 1: Find the Stop Code and Faulting Module

Before applying any fix, identify the exact stop code and, if possible, the faulting .sys file.

Method A — From the crash screen: Write down or photograph the stop code shown on the blue screen.

Method B — Event Viewer:

Press Win + X → select Event Viewer.
Navigate to Windows Logs → System.
Filter for Critical and Error events.
Look for events from source BugCheck or Kernel-Power around the time of the crash.
The event details will show the stop code in hexadecimal (e.g., 0x0000000A).

Method C — WinDbg or WhoCrashed: Download WhoCrashed (free) or use WinDbg from the Microsoft Store. Point it to your minidump files located at C:\Windows\Minidump\. These files reveal the exact faulting driver or module name.

Step 2: Boot Into Safe Mode (If System Won't Start)

If Windows 11 is stuck in a BSOD loop:

Force shut down your PC three times in a row during boot — Windows will automatically enter Windows Recovery Environment (WinRE).
Choose Troubleshoot → Advanced Options → Startup Settings → Restart.
Press F4 for Safe Mode or F5 for Safe Mode with Networking.

In Safe Mode, only essential Microsoft drivers load, which helps isolate third-party driver issues.

Step 3: Run SFC and DISM to Repair System Files

Open Command Prompt as Administrator and run the following commands in sequence:

sfc /scannow

Wait for the scan to complete. If it reports found and repaired integrity violations, restart and monitor. If SFC cannot repair files, run DISM:

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 4: Check and Roll Back Drivers

If the faulting module identified in Step 1 is a driver file (ends in .sys):

Press Win + X → Device Manager.
Look for devices with a yellow warning triangle.
Right-click the suspect device → Properties → Driver tab.
Click Roll Back Driver if available, or Uninstall Device and download the previous driver version from the manufacturer's website.

For GPU crashes showing nvlddmkm.sys (NVIDIA) or atikmpag.sys (AMD):

Use DDU (Display Driver Uninstaller) in Safe Mode to completely remove the GPU driver.
Download and install the previous stable driver version from nvidia.com or amd.com.

Step 5: Test RAM with Windows Memory Diagnostic or MemTest86

Windows Memory Diagnostic (built-in):

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
After restart, the tool runs automatically. Results appear in Event Viewer under Windows Logs → System — search for source MemoryDiagnostics-Results.

For deeper testing, run MemTest86 from a bootable USB (free from memtest86.com). Run at least 2 full passes. Any errors = faulty RAM that must be replaced.

Step 6: Scan the Drive with CHKDSK

For stop codes related to file system or storage:

chkdsk C: /f /r /x

You will be prompted to schedule the scan on next restart since the C: drive is in use. Type Y and restart. CHKDSK will scan for bad sectors, file system errors, and attempt repairs. For NVMe/SSD drives, also run the manufacturer's diagnostic tool (Samsung Magician, Crucial Storage Executive, etc.).

Step 7: Check for Overheating

Use HWiNFO64 or Core Temp to monitor CPU and GPU temperatures. Critical thresholds:

CPU: Should stay below 95°C under load (AMD) or 100°C (Intel with thermal velocity boost).
GPU: Should stay below 90°C under load.

If temperatures are excessive:

Clean dust from CPU heatsink, GPU fans, and case vents.
Reapply thermal paste to the CPU (especially if PC is 3+ years old).
Ensure case fans are functioning and airflow is adequate.

Step 8: Perform a System Restore

If the BSOD started after a specific date and a restore point exists:

Boot into WinRE → Troubleshoot → Advanced Options → System Restore.
Select a restore point dated before the issue began.
Follow the prompts. This will not delete personal files but will remove software and driver changes made after that restore point.

Step 9: Reset This PC or Reinstall Windows 11

If all above steps fail:

Go to Settings → System → Recovery → Reset this PC.
Choose Keep my files for a soft reset, or Remove everything for a clean reinstall.
For the most thorough fix, perform a clean install from a Windows 11 USB bootable drive created with the Media Creation Tool from Microsoft.

Important: Back up all critical data to an external drive or cloud storage before resetting.

Windows 8 and Vista BSOD Notes

On Windows 8, BSODs show less detail by default. Enable verbose BSOD output via:

bcdedit /set {current} bootstatuspolicy ignoreallfailures

On Windows Vista, the most common BSODs involve ntoskrnl.exe corruption, failing IDE/SATA drivers, or incompatible third-party antivirus. Vista reached End of Life in April 2017 — Microsoft no longer releases patches, so a hardware upgrade and OS migration is strongly recommended.

Frequently Asked Questions

powershell

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

# --- 1. Display the last 10 BugCheck events from Event Viewer ---
Write-Host "=== Recent BugCheck / BSOD Events ==="
Get-WinEvent -LogName System -MaxEvents 200 | Where-Object { $_.Id -eq 1001 -and $_.ProviderName -eq 'Microsoft-Windows-WER-SystemErrorReporting' } | Select-Object -First 10 TimeCreated, Message | Format-List

# --- 2. List all minidump files (feed these into WinDbg or WhoCrashed) ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, @{Name='SizeMB';Expression={[math]::Round($_.Length/1MB,2)}}

# --- 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 Restore ==="
Dism /Online /Cleanup-Image /RestoreHealth

# --- 5. Check disk for errors (schedules on next reboot for C:) ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
echo Y | chkdsk C: /f /r /x

# --- 6. Check recently installed drivers (last 30 days) ---
Write-Host "`n=== Drivers Installed in 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, InfName | Sort-Object DriverDate -Descending | Format-Table -AutoSize

# --- 7. Check temperatures via WMI (basic; use HWiNFO64 for detailed readings) ---
Write-Host "`n=== CPU Thermal Zone Temperatures (Celsius) ==="
Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace root/wmi -ErrorAction SilentlyContinue | ForEach-Object { [math]::Round(($_.CurrentTemperature / 10 - 273.15), 1) } | ForEach-Object { Write-Host "$_ C" }

# --- 8. List top memory-consuming processes (potential cause of memory BSODs) ---
Write-Host "`n=== Top 10 Processes by RAM Usage ==="
Get-Process | Sort-Object WorkingSet64 -Descending | Select-Object -First 10 Name, Id, @{Name='RAM_MB';Expression={[math]::Round($_.WorkingSet64/1MB,2)}} | Format-Table -AutoSize

# --- 9. Export system info for manual review ---
Write-Host "`n=== Exporting System Info to Desktop ==="
$desktop = [System.Environment]::GetFolderPath('Desktop')
Get-ComputerInfo | Out-File "$desktop\SystemInfo_BSOD_Report.txt"
Write-Host "Report saved to $desktop\SystemInfo_BSOD_Report.txt"

Write-Host "`n=== Diagnostics Complete. Review output and minidumps. ==="

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, Windows system administrators, and SRE professionals with a combined 40+ years of experience diagnosing OS-level failures, BSOD stop errors, kernel panics, and critical system faults across Windows Vista through Windows 11 enterprise environments. Our guides are tested against real crash dumps and validated against Microsoft's official documentation and community bug trackers.

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.