What is a BSOD and why does it happen?

A Blue Screen of Death (BSOD) is a critical Windows kernel error from which the system cannot safely recover. It is triggered when a driver, hardware component, or kernel process encounters a fatal condition — such as accessing invalid memory, a hardware failure, or a corrupted system file. Windows halts immediately to prevent data corruption and logs a minidump file for diagnosis.

Is a BSOD a sign of hardware failure?

Not always. BSODs can be caused by software (drivers, corrupted system files) or hardware (faulty RAM, failing SSD, overheating). If BSODs are random and not tied to a specific action, run Windows Memory Diagnostic and check disk health with CrystalDiskInfo. If they happen under GPU load, suspect a GPU driver issue or overheating.

Most Common BSOD Codes – Complete Stop Code Guide

The Blue Screen of Death (BSOD) is Windows' last line of defense — a controlled crash that prevents deeper system damage. While the sudden blue screen is alarming, every stop code carries a specific meaning that points directly at the root cause. This guide covers the most frequent BSOD stop codes encountered on Windows 10 and 11, explains what each one means, and provides actionable step-by-step fixes so you can get back to a stable system quickly.

🔵 Where to Find Your Minidump Files

Windows saves a crash log every time a BSOD occurs. Navigate to C:\Windows\Minidump and open the .dmp file with WhoCrashed (free tool) or WinDbg to identify the exact driver or module responsible. Always start diagnosis here before replacing hardware.

Most Common Causes of BSOD Errors

Corrupted, outdated, or incompatible device drivers (GPU, network, storage)
Faulty or failing RAM modules — bad sectors or incompatible XMP profiles
Corrupted Windows system files or a damaged Windows Registry
Failing or incompatible SSD/HDD — bad sectors on the system partition
CPU or GPU overheating causing hardware-level errors
Malware or rootkits tampering with kernel-level processes
Incompatible software running in kernel mode (antivirus, VPN drivers)
Failed Windows Update or a partially applied system patch

How to Diagnose and Fix a BSOD – Step by Step

Record or photograph the stop codeWrite down the exact error name (e.g., MEMORY_MANAGEMENT) and any file name shown below it (e.g., ntfs.sys). If the PC reboots too fast, go to Settings → System → About → Advanced system settings → Startup and Recovery → uncheck "Automatically restart".
Analyse the minidump with WhoCrashedDownload and run WhoCrashed (free). It reads C:\Windows\Minidump\*.dmp and displays a plain-English summary of which driver caused the crash. This is the single most effective first step.
Update or roll back the guilty driverOpen Device Manager (devmgmt.msc). If WhoCrashed named a driver (e.g., nvlddmkm.sys = NVIDIA), right-click the device → Properties → Driver tab → Roll Back Driver. If rolling back isn't available, download the latest stable driver from the manufacturer's website.
Run Windows Memory DiagnosticPress Win + R, type mdsched.exe, and choose "Restart now and check for problems". After reboot, Windows scans RAM. If errors are found, test each RAM stick individually by removing others. Replace any faulty stick.
Repair system files with SFC and DISMOpen Command Prompt as Administrator and run: sfc /scannow — wait for completion, then run DISM /Online /Cleanup-Image /RestoreHealth. Reboot and re-run SFC. These commands repair corrupted Windows kernel files that cause many stop errors.
Check disk healthRun chkdsk C: /f /r in an elevated prompt and restart. Also check your SSD/HDD health with CrystalDiskInfo — a drive showing "Caution" or "Bad" status needs to be replaced immediately.
Boot into Safe Mode for persistent BSODsIf Windows won't boot, press F8 during startup (or boot from Windows USB → Repair → Troubleshoot → Advanced → Startup Settings → Safe Mode with Networking). In Safe Mode, uninstall the most recently installed software or driver before the crashes began.

Most Common BSOD Stop Codes Reference Table

Stop Code	Error Name	Severity
`0x0000001A`	MEMORY_MANAGEMENT – RAM error or driver memory corruption	Critical
`0x0000000A`	IRQL_NOT_LESS_OR_EQUAL – driver accessed invalid memory address	Critical
`0x0000003B`	SYSTEM_SERVICE_EXCEPTION – kernel service threw unhandled exception	Critical
`0x00000050`	PAGE_FAULT_IN_NONPAGED_AREA – invalid memory reference	Critical
`0x0000007E`	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED – driver or system thread crash	High
`0x0000007F`	UNEXPECTED_KERNEL_MODE_TRAP – hardware failure or overclocking	Critical
`0x000000EF`	CRITICAL_PROCESS_DIED – essential Windows process terminated	Critical
`0x0000009F`	DRIVER_POWER_STATE_FAILURE – driver not handling power state changes	High
`0x000000D1`	DRIVER_IRQL_NOT_LESS_OR_EQUAL – network or storage driver bug	High
`0x0000001E`	KMODE_EXCEPTION_NOT_HANDLED – kernel-mode code raised exception	High
`0x00000024`	NTFS_FILE_SYSTEM – NTFS driver error, often a failing drive	High
`0x0000012B`	FAULTY_HARDWARE_CORRUPTED_PAGE – hardware-level memory corruption	Critical
`0x00000101`	CLOCK_WATCHDOG_TIMEOUT – CPU core not responding, often heat/OC	Critical
`0x00000124`	WHEA_UNCORRECTABLE_ERROR – hardware exception (CPU, RAM, PCIe)	Critical
`0x000000C4`	DRIVER_VERIFIER_DETECTED_VIOLATION – Driver Verifier caught a bad driver	Medium
`0x000000C5`	DRIVER_CORRUPTED_EXPOOL – driver corrupted kernel memory pool	High
`0x000000BE`	ATTEMPTED_WRITE_TO_READONLY_MEMORY – driver writing to read-only memory	Medium
`0x000000F4`	CRITICAL_OBJECT_TERMINATION – critical system object terminated unexpectedly	Critical

Frequently Asked Questions

What is a BSOD and why does Windows crash?

A Blue Screen of Death is a critical kernel-level error from which Windows cannot safely recover. It occurs when a driver, hardware component, or core system process encounters a fatal condition — such as invalid memory access or a hardware exception. Windows halts immediately to prevent data corruption and saves a minidump file for diagnosis.

How do I find my BSOD stop code if Windows reboots too fast?

Go to Settings → System → About → Advanced system settings → Startup and Recovery → uncheck "Automatically restart". This keeps the blue screen on screen until you manually reboot. Alternatively, open Event Viewer (eventvwr.msc) → Windows Logs → System and look for Critical events at the time of the crash.

Can a faulty driver cause a BSOD?

Yes — buggy drivers are the most common cause of BSODs on modern Windows. A driver running in kernel mode can corrupt memory or access invalid addresses, triggering a stop error. Use WhoCrashed or WinDbg to read the minidump file. It will identify the offending .sys file, usually pointing directly to the problematic driver.

Is a BSOD always a sign of hardware failure?

No. Many BSODs are caused by software issues — corrupt drivers, failed Windows Updates, or malware. However, stop codes like WHEA_UNCORRECTABLE_ERROR, MEMORY_MANAGEMENT, and CLOCK_WATCHDOG_TIMEOUT often indicate hardware problems (RAM, CPU overheating, failing SSD). Run memory diagnostics and disk health checks before assuming a hardware replacement is needed.

What tools should I use to diagnose BSODs?

The essential toolkit: WhoCrashed (free minidump reader), WinDbg (advanced crash analysis), Windows Memory Diagnostic or MemTest86 (RAM testing), CrystalDiskInfo (drive health), HWiNFO64 (temperature monitoring), and the built-in Event Viewer. Start with WhoCrashed — it provides the fastest path to identifying the cause.