Windows BSOD Error 0x000000B8 — ATTEMPTED_SWITCH_FROM_DPC Fix

What Does This Error Mean?

The 0x000000B8 blue screen is called ATTEMPTED_SWITCH_FROM_DPC. DPC stands for Deferred Procedure Call — a mechanism Windows uses to let drivers schedule work at a high interrupt priority. If a driver tries to wait for something or switch to another task while it is inside a DPC, Windows crashes immediately. This is always a driver bug, never a user error. It typically appears after installing new hardware or updating drivers.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

A device driver contains a bug that attempts to wait or sleep while running inside a DPC routine
A recently installed or updated network, audio, or graphics driver has faulty interrupt handling code
An older driver was written for a previous Windows version and is not compatible with current threading rules
A third-party security or monitoring tool is hooking into interrupt routines incorrectly
Corrupted driver files caused by a failed update or disk error

How to Fix It

Check the blue screen for the name of a driver file ending in .sys. Write it down before the screen disappears. This is the fastest path to identifying the problem driver.

To keep the blue screen visible longer, go to System Properties > Advanced > Startup and Recovery > Settings and uncheck 'Automatically restart.'
Roll back any recently updated drivers. Open Device Manager, right-click a device, choose Properties > Driver tab, and click 'Roll Back Driver' if the button is available.

If the crashes started right after a driver update, rolling back almost always stops them immediately.
Update all device drivers, especially network adapters, audio, and GPU. Visit your PC or motherboard manufacturer's website and download the latest driver package for your specific model.

Driver updates from the manufacturer's own website are more reliable than the ones Windows Update installs automatically.
Use Driver Verifier to find the problem driver. Open the Start menu, type 'verifier,' and run it as Administrator. Choose 'Create standard settings' and let it test all installed drivers.

Driver Verifier will intentionally crash Windows when it catches the misbehaving driver, and the resulting blue screen will name the exact culprit. Disable Verifier after finding the problem.
Run sfc /scannow in an Administrator Command Prompt to check for corrupted Windows files. Then run: DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows component store.

Corrupted system files can cause drivers to malfunction even when the driver itself is not the original source of the problem.

When to Call a Professional

This error always points to a specific driver. If you cannot identify which one it is, a technician can analyze the crash dump file using WinDbg. Crash dumps are stored in C:\Windows\Minidump and contain the exact name of the offending driver. Bring the minidump file to a repair shop or share it with an online support forum for analysis.

Frequently Asked Questions

What is a DPC and why is it so strict?

A DPC (Deferred Procedure Call) is a way for drivers to run code at a very high priority level. When Windows is inside a DPC, it is not allowed to switch tasks, wait, or call code that could block. These rules exist because DPCs can interrupt anything else running on the CPU. If a driver ignores the rules and tries to wait, the entire system deadlocks. Windows crashes immediately to prevent that from happening.

Can antivirus software cause this error?

Yes. Some antivirus and security programs install kernel-level drivers that hook into interrupt routines. If those drivers are poorly written or become outdated, they can trigger this crash. Try temporarily disabling your antivirus and see if the crashes stop. If they do, check the vendor's website for an updated version of the security software.

How do I read a crash dump file?

Crash dump files are stored in C:\Windows\Minidump. A free tool called WhoCrashed (from Resplendence Software) can read these files and explain the crash in plain English. It will usually name the driver responsible and give you a link to search for more information. This is the easiest way to identify the cause without needing technical debugging skills.