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

Random BSODs with no consistent stop code usually point to faulty or intermittently failing RAM, an unstable power supply (desktop), or a driver that crashes under specific but unpredictable conditions. Run MemTest86 overnight to rule out RAM, check PSU voltage rails with HWiNFO64, and use WhoCrashed or WinDbg to identify the faulting driver module from the minidump files in C:\Windows\Minidump\.

My laptop keeps blue screening on Windows 11 after sleep or hibernate — what causes this?

This is almost always caused by Fast Startup, a driver that does not properly support Windows 11 Modern Standby (S0ix), or a corrupted hibernation file. Disable Fast Startup in Control Panel → Power Options, update your chipset and storage drivers, and if needed delete the hibernation file with 'powercfg /h off' in an elevated PowerShell, then re-enable it with 'powercfg /h on'. Also ensure your BIOS is on the latest version.

Windows 11 blue screening with DRIVER_IRQL_NOT_LESS_OR_EQUAL — how do I fix it?

This stop code (0x000000D1) means a driver accessed memory at an invalid IRQL. Open the minidump with WinDbg and run '!analyze -v' to see the exact .sys file responsible. Common culprits are network adapter drivers (especially Realtek and Killer Wi-Fi), VPN clients, and antivirus kernel drivers. Update or uninstall the offending driver. If it is a Windows Update-pushed driver, use Device Manager to roll it back.

Can a Windows 11 update itself cause blue screens?

Yes. Cumulative Updates occasionally ship with driver incompatibilities. If BSODs started within days of an update, open Settings → Windows Update → Update History, identify the update KB number, and uninstall it via Settings → Windows Update → Advanced Options → Recover. You can also use 'wusa /uninstall /kb:XXXXXXX' in an elevated command prompt. After uninstalling, pause updates for 7 days while Microsoft issues a fix.

My PC keeps blue screening on Windows 11 with WHEA_UNCORRECTABLE_ERROR — is my hardware dying?

WHEA_UNCORRECTABLE_ERROR (0x00000124) indicates a hardware-level machine check exception from the CPU, RAM, or motherboard. First try updating your BIOS, resetting XMP/EXPO RAM profiles to stock speeds in BIOS, and running MemTest86. If the error persists after those steps, the CPU or motherboard may have a hardware fault. Check for bent CPU socket pins (on Intel platforms) and run CPU stress tests with Prime95. If under warranty, contact the manufacturer.

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

Fix Windows 11 blue screen crashes fast. Learn how to diagnose BSOD stop codes, update drivers, run memory tests, and stop random restarts for good.

Last updated: March 1, 2026

Last verified: March 1, 2026

1,908 words

Key Takeaways

Faulty or outdated device drivers (especially GPU, NIC, and storage drivers) are the #1 cause of repeated BSODs on Windows 11.
Corrupted system files, bad RAM sticks, and incompatible third-party software (antivirus, overclocking tools) are the next most common root causes.
Quick fix path: note the stop code shown on the blue screen, run 'winget upgrade --all' to update drivers, execute 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated PowerShell, then run Windows Memory Diagnostic to rule out hardware issues.

Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back Drivers	BSOD started after a driver or Windows Update install	15-30 min	Low
SFC + DISM Scan	Random BSODs with no clear trigger, corrupted OS files suspected	20-45 min	Low
Windows Memory Diagnostic	BSODs under load, errors include MEMORY_MANAGEMENT or PAGE_FAULT	30-60 min	None
Check Event Viewer + WinDbg	Need to identify exact stop code and faulting module	15-30 min	None
Disable Fast Startup	BSODs happen only at boot or resume from hibernate	2 min	None
System Restore / Reset	All other fixes failed, system is unstable	30-120 min	Medium (data risk if Reset chosen)
BIOS/UEFI Firmware Update	BSODs tied to hardware init, ACPI, or NVMe/USB stop codes	20-40 min	Medium

Understanding Windows 11 Blue Screen of Death (BSOD)

A Blue Screen of Death (BSOD) — officially called a Stop Error — occurs when Windows 11 detects a fatal condition it cannot recover from. The system halts all operations to prevent further damage, dumps memory to disk, and restarts. On Windows 11 the screen shows a sad-face emoji, a stop code such as IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION, and a QR code.

Common stop codes and their typical causes:

IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — driver accessing invalid memory address
SYSTEM_SERVICE_EXCEPTION (0x0000003B) — faulty driver or system service crash
MEMORY_MANAGEMENT (0x0000001A) — RAM hardware fault or driver memory corruption
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — driver or software referencing freed memory
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — network or storage driver bug
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — data structure corruption, often AV software
DPC_WATCHDOG_VIOLATION (0x00000133) — SSD firmware or storage driver timeout
WHEA_UNCORRECTABLE_ERROR (0x00000124) — hardware-level CPU/RAM error

Step 1: Record the Stop Code

When the blue screen appears, photograph it or note the stop code at the bottom. If the PC restarts too fast to read it:

Open Settings → System → About → Advanced system settings.
Under Startup and Recovery click Settings.
Uncheck Automatically restart under System failure.
This keeps the blue screen visible until you manually reboot.

Alternatively, Windows writes a minidump to C:\Windows\Minidump\ after each BSOD. You can read these with WinDbg or the free tool WhoCrashed.

Step 2: Identify the Faulting Module via Event Viewer

Press Win + X → Event Viewer.
Navigate to Windows Logs → System.
Filter by Event ID 41 (unexpected shutdown) and Event ID 1001 (WerFault / BSOD details).
The BugcheckCode field (in hexadecimal) maps directly to the stop code.

For deeper analysis, open WinDbg (available free from the Microsoft Store):

!analyze -v

This command automatically points to the faulting driver file (e.g., nvlddmkm.sys for NVIDIA, ntfs.sys for file-system issues).

Step 3: Update or Roll Back Drivers

Update all drivers at once (PowerShell):

winget upgrade --all

Roll back a specific driver (e.g., if BSOD started after a GPU update):

Open Device Manager (devmgmt.msc).
Expand Display adapters (or the relevant category).
Right-click the device → Properties → Driver tab → Roll Back Driver.

If Roll Back is greyed out, download the previous driver version directly from the manufacturer (NVIDIA, AMD, Intel) and install it manually with the current one first uninstalled via DDU (Display Driver Uninstaller) in Safe Mode.

Step 4: Run SFC and DISM to Repair System Files

Open PowerShell as Administrator and run:

# Step 4a: System File Checker
sfc /scannow

# Step 4b: DISM health restore (run if SFC finds unfixable errors)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

Reboot after both complete. SFC logs results to C:\Windows\Logs\CBS\CBS.log.

Step 5: Test RAM with Windows Memory Diagnostic

Press Win + R → type mdsched.exe → Enter.
Choose Restart now and check for problems.
The tool runs on next boot and logs results to Event Viewer under Windows Logs → System, Event Source MemoryDiagnostics-Results.

For a more thorough test, use MemTest86 (bootable USB, free) which runs outside Windows and catches intermittent RAM errors that mdsched misses.

Step 6: Check Storage Health

A failing SSD or HDD can cause DPC_WATCHDOG_VIOLATION and NTFS_FILE_SYSTEM BSODs.

# Check SMART data for all drives
Get-PhysicalDisk | Get-StorageReliabilityCounter | Select DeviceId, ReadErrorsTotal, WriteErrorsTotal, Temperature

# Run CHKDSK on C: drive (schedules on next reboot)
chkdsk C: /f /r /x

For NVMe drives, install CrystalDiskInfo (free) to read vendor-specific SMART attributes.

Step 7: Disable Fast Startup

Fast Startup can cause driver state corruption on resume, leading to BSODs at boot:

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

Step 8: Boot into Safe Mode to Isolate Third-Party Software

If BSODs stop in Safe Mode, a third-party driver or startup program is the cause.

Hold Shift while clicking Restart from the Start menu.
Go to Troubleshoot → Advanced options → Startup Settings → Restart.
Press 4 to boot into Safe Mode.

In Safe Mode, use msconfig (System Configuration) to disable startup items one group at a time until you isolate the culprit.

Step 9: Update BIOS/UEFI Firmware

Outdated BIOS can cause ACPI_BIOS_ERROR, WHEA_UNCORRECTABLE_ERROR, and NVMe-related BSODs. Visit your motherboard or laptop manufacturer's support page, download the latest BIOS update, and follow their flashing instructions carefully. Never interrupt a BIOS update.

Step 10: System Restore or Reset as Last Resort

System Restore (if enabled) rolls Windows back to a known-good state without affecting personal files:

Press Win + R → rstrui.exe → Enter.
Pick a restore point dated before BSODs began.

Reset this PC (keeps or removes files, reinstalls Windows 11):

Settings → System → Recovery → Reset this PC.
Choose Keep my files for a less destructive option.

If Windows cannot boot, access both options from Windows Recovery Environment (WinRE) by pressing F8 at boot or booting from a Windows 11 USB installation media.

Laptop-Specific Tips (Windows 11 Laptop Keeps Blue Screening)

Overheating: Laptops throttle and can BSOD under thermal stress. Clean vents, repaste CPU/GPU, and use HWiNFO64 to monitor temps.
Battery/Power driver: DRIVER_POWER_STATE_FAILURE is common on laptops. Update the battery and ACPI drivers.
Thunderbolt/USB-C docks: Disconnect external docks and test — faulty dock firmware causes repeated BSODs.

When to Suspect Hardware Failure

If you see WHEA_UNCORRECTABLE_ERROR, MACHINE_CHECK_EXCEPTION, or BSODs survive a clean Windows reinstall, the issue is hardware:

Reseat RAM sticks and try one stick at a time.
Reseat GPU (desktop PCs).
Test with a different PSU (desktop PCs) — an unstable power supply causes random BSODs.
Contact manufacturer for warranty replacement.

Frequently Asked Questions

powershell

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

# 1. List recent BSOD events from Event Log
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=41,1001} -MaxEvents 20 |
    Select-Object TimeCreated, Id, Message |
    Format-List

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

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

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

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

# 6. Schedule CHKDSK on next reboot
Write-Host "`n=== Scheduling CHKDSK on C: ==="
echo Y | chkdsk C: /f /r

# 7. Check driver versions for common problematic drivers
Write-Host "`n=== Driver List (Display, Network, Storage) ==="
Get-WmiObject Win32_PnPSignedDriver |
    Where-Object { $_.DeviceClass -in ('Display','Net','DiskDrive','SCSIAdapter') } |
    Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer |
    Sort-Object DeviceClass |
    Format-Table -AutoSize

# 8. Disable Fast Startup via registry
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."

# 9. Export full System log for manual review
$logPath = "$env:USERPROFILE\Desktop\SystemEvents_$(Get-Date -Format yyyyMMdd_HHmm).evtx"
wevtutil epl System $logPath
Write-Host "`nSystem event log exported to: $logPath"

Write-Host "`n=== Diagnostics Complete. Reboot recommended. ==="

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with a combined 40+ years of experience diagnosing OS-level failures, kernel panics, and hardware faults across enterprise and consumer environments. Our guides are built from real-world minidump analysis, vendor documentation, and community-validated fixes.

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.