A Blue Screen of Death (BSOD) is Windows telling you that something has gone seriously wrong — wrong enough that continuing to run would risk corrupting data or causing further damage. While a single, isolated BSOD after an update or driver change is not necessarily alarming, repeated BSODs are a warning sign that demands investigation. Here is how to read them, diagnose the cause, and fix it.
What the Error Code Is Telling You
Modern Windows BSODs display a stop code — a text string in capital letters such as MEMORY_MANAGEMENT, DRIVER_IRQL_NOT_LESS_OR_EQUAL, or CRITICAL_PROCESS_DIED. This is your starting point. Note it down or photograph it. Each code points to a specific class of problem:
- MEMORY_MANAGEMENT / PAGE_FAULT_IN_NONPAGED_AREA: RAM fault or driver writing to invalid memory addresses
- DRIVER_IRQL_NOT_LESS_OR_EQUAL / SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: A faulty or incompatible driver — often recently installed or updated
- CRITICAL_PROCESS_DIED / SYSTEM_SERVICE_EXCEPTION: A core Windows process has crashed, often due to a corrupt system file or driver conflict
- NTFS_FILE_SYSTEM / BAD_SYSTEM_CONFIG_INFO: File system corruption or a failing drive
- WHEA_UNCORRECTABLE_ERROR: Hardware error — CPU, RAM, or motherboard instability, sometimes caused by overheating
Step 1: Check Event Viewer for the Full Crash Log
Windows saves a minidump file each time a BSOD occurs. To read these, search for Event Viewer in the Start menu, navigate to Windows Logs → System, and filter for Critical events around the time of the crash. The error detail will often name a specific driver file (ending in .sys) or component.
Alternatively, download the free tool WhoCrashed (by Resplendence Software), which reads your minidump files and presents the analysis in plain English, usually identifying the responsible driver by name.
Step 2: Roll Back or Update the Identified Driver
If the crash log identifies a specific driver, that is your first target. In Device Manager, find the device that uses that driver, right-click, and select Properties → Driver → Roll Back Driver if the BSOD started after a recent update. If there is no rollback available, visit the hardware manufacturer’s website and download the latest stable driver version.
Drivers most commonly responsible for BSODs include graphics card drivers (Nvidia/AMD), network adapter drivers, and third-party storage or virtualisation drivers.
Step 3: Run Windows Memory Diagnostic
If the stop code suggests a memory problem, or if no driver is identified, test your RAM. Search for Windows Memory Diagnostic in the Start menu and select Restart now and check for problems. The test runs before Windows loads and checks RAM for errors. Results are shown in Event Viewer under MemoryDiagnostics-Results after the system restarts.
For more thorough testing, run MemTest86 (free, boots from a USB drive) overnight. A single RAM error is grounds for replacing the affected module.
Step 4: Check Drive Health
A failing hard drive or SSD can cause BSODs as Windows fails to read critical system files. Run chkdsk /f /r from an elevated Command Prompt (it will prompt you to schedule it for the next boot on the system drive). Also install CrystalDiskInfo to check your drive’s SMART data for reallocated sectors, pending sectors, or uncorrectable errors — any of these in significant numbers means the drive is failing and should be replaced immediately.
Step 5: Repair Windows System Files
Corrupted system files can cause repeated crashes without any hardware fault. Run these two commands from an elevated Command Prompt, in order:
sfc /scannow— scans and repairs protected Windows system filesDISM /Online /Cleanup-Image /RestoreHealth— repairs the Windows component store used by the system file checker
Run DISM first if sfc reports that it found errors but could not fix them all. Restart after both have completed.
Step 6: Check for Overheating
A CPU or GPU running too hot will cause system instability and BSODs, particularly under load. Install HWMonitor or Core Temp and watch temperatures under normal use. CPU temperatures above 90°C under load, or above 50°C at idle, indicate a cooling problem. Check that vents are clear of dust, that all fans are spinning, and that thermal paste on the CPU has not dried out — particularly on laptops over three years old.
When to Escalate
If BSODs persist after driver updates, memory tests, disk checks, and system file repairs, the problem is likely hardware-level — a failing RAM module, a degrading motherboard, or a failing PSU causing voltage instability. These require physical inspection and component testing. Contact the BIT Tech team if you need hands-on diagnosis.
