Home / Windows & PowerShell

How to Fix Critical Blue Screen of Death (BSOD) Errors in Windows

Systematic methodology to identify Stop Codes, verify kernel event logs, and apply recovery commands for severe system failures.

01. Initial Diagnosis and Stop Codes

When a Blue Screen of Death (BSOD) occurs, Windows halts the operating system to prevent physical damage or data corruption. The critical piece of data is the Stop Code (e.g., CRITICAL_PROCESS_DIED or MEMORY_MANAGEMENT).

If your computer restarts too quickly, you can disable automatic restart by right-clicking This PC -> Properties -> Advanced system settings -> Startup and Recovery, and unchecking "Automatically restart".

02. Querying Kernel Errors from PowerShell

You can query critical system events and unexpected shutdown failures directly by running the following command in PowerShell with administrator privileges:

Get-WinEvent -LogName System -FilterXPath "*[System[(EventID=41 or EventID=1001)]]" -MaxEvents 10 | Select-Object TimeCreated, Id, Message

* Event ID 41 indicates that the system rebooted without cleanly shutting down first, and Event ID 1001 shows memory dump details (Minidump).

03. Repairing Corrupted System Files

Many BSODs are caused by corruption in DLL files or kernel drivers. Open a Command Prompt console (cmd) as administrator and sequentially run the following native tools:

# 1. Check and repair the operating system image

DISM.exe /Online /Cleanup-image /Restorehealth

# 2. Scan and replace damaged Windows files

sfc /scannow

04. RAM and Disk Integrity Verification

RAM failures and bad sectors on storage drives are the most common causes of recurring blue screens. Run these tests:

Memory Diagnostics: Press Windows + R, type mdsched.exe, and select restart to check for errors in RAM modules.
Disk Check (CHKDSK): In CMD as administrator, run chkdsk C: /f /r to isolate bad sectors on the primary drive.