Driver-related Blue Screens (BSOD): identify the culprit

The Blue Screen of Death — short BSOD — is the most dramatic symptom of a driver problem. Windows detects a critical error in kernel mode, halts the system to prevent data corruption, and shows a stop-code on a blue screen. In about 70 % of all BSODs, a faulty or outdated driver is responsible. We show you how to identify the culprit, read the stop-code correctly and avoid future crashes.

Why does a driver cause a BSOD at all?

Drivers run in Kernel Mode — the most privileged level of the operating system. A bug in a driver can therefore crash the entire system, while a bug in a normal application only kills the application itself. The reasons why a driver triggers a BSOD:

• Memory access to invalid addresses (access violation)
• Race conditions between threads
• Hardware errors that the driver doesn't handle
• Incompatibility with current Windows kernel versions
• Corrupted driver files (e.g. after a failed update)

Reading the stop-code correctly

Modern Windows BSODs show a QR code, a text label, and the technical name of the bug-check. The technical name is decisive — examples:

Stop-code	Meaning	Likely cause
DRIVER_IRQL_NOT_LESS_OR_EQUAL	Driver accessed memory at incorrect IRQL	Faulty driver — almost always the cause
SYSTEM_SERVICE_EXCEPTION	System service exception	Often graphics or audio driver
PAGE_FAULT_IN_NONPAGED_AREA	Memory access error	RAM defect or driver bug
KMODE_EXCEPTION_NOT_HANDLED	Unhandled kernel-mode exception	Driver or hardware issue
VIDEO_TDR_FAILURE	Display Driver Stopped Responding	Graphics driver crash (Nvidia/AMD)
WHEA_UNCORRECTABLE_ERROR	Hardware error, uncorrectable	CPU, RAM, mainboard — rarely driver
NTFS_FILE_SYSTEM	File system error	SSD/HDD or storage driver
BAD_POOL_HEADER	Memory pool corrupted	Driver writing to wrong memory area

Finding the driver behind the BSOD

Method 1: WhoCrashed (simplest)

1. Download WhoCrashed (free for private use).
2. Install and run.
3. The tool reads the most recent minidumps and immediately shows the suspect driver.

Disadvantage: WhoCrashed sometimes points only at the immediate trigger, not the actual cause.

Method 2: Event Viewer

1. Press Win + X → Event Viewer
2. Windows Logs → System
3. Filter: Source = BugCheck
4. The filename of the crashing driver appears in the entry

Method 3: WinDbg (most detailed analysis)

For the deepest analysis, use Microsoft WinDbg:

1. Install WinDbg from the Microsoft Store
2. Open the latest minidump from C:\Windows\Minidump\
3. Type the command !analyze -v
4. WinDbg shows you the failing driver, the stop-code and a stack trace

Solving driver-related BSODs

Solution 1: Rollback

If the BSOD started right after a specific driver update: roll back to the previous version.

1. Device Manager → suspect device → Properties
2. Driver tab → Roll back driver
3. If unavailable: Windows didn't keep the previous driver. Then try Solution 2.

Solution 2: Clean install of an older version

1. Download the older driver from the manufacturer's archive (e.g. Nvidia Driver Archive)
2. For graphics: completely uninstall the current driver with Display Driver Uninstaller (DDU) in Safe Mode
3. Install the older version
4. Pause Windows Update for that driver category

Solution 3: Find the culprit with Driver Verifier

For unclear cases use the integrated Driver Verifier (verifier.exe). Note: only run after a backup — it deliberately stresses drivers and triggers more BSODs that then yield clear minidumps.

Preventing future BSODs

• Don't update drivers unnecessarily. "Never change a running system" applies especially to drivers. Only update if there's a real reason (security fix, performance for a specific game, new feature).
• Always create a restore point before driver updates.
• Avoid beta drivers in production systems.
• Watch out for known issues — manufacturer release notes often list known incompatibilities.
• Keep drivers in sync. Don't run a months-old chipset driver alongside the latest GPU driver.