Quick answer: Update your GPU driver, then if it still crashes, increase the TdrDelay registry value to 10 seconds or disable any overclock on your graphics card.
DirectX error 0x887A0006, also known as DXGI_ERROR_DEVICE_HUNG, is that annoying crash that pops up mid-game, usually right in the middle of a firefight or a boss fight. Windows throws this when your GPU stops responding to the driver for too long. The OS thinks the graphics card is frozen, so it resets the driver and kills the game. I've seen this on everything from a GTX 1060 to a RTX 4090, and it's rarely the game's fault. It's your GPU driver, your power settings, or an unstable overclock.
Why does this happen?
Windows has a watchdog timer called TDR (Timeout Detection and Recovery). It gives your GPU about 2 seconds to finish a frame or a command. If the GPU takes longer, Windows assumes it's hung and resets the driver. That reset kills your game. The usual culprits: outdated or corrupted drivers, a bad overclock, a dying PSU, or even a game that pushes the GPU to its limit (like Cyberpunk 2077 with ray tracing on a card that's just not up to it).
Fix 1: Update your GPU driver (the obvious one, but do it right)
- Download the latest driver from NVIDIA or AMD directly. Don't use Windows Update or a generic driver updater—they're often stale.
- Use DDU (Display Driver Uninstaller) to completely remove the old driver in Safe Mode. Yes, it's overkill, but I had a client last month whose error persisted through three driver updates. DDU fixed it in one shot.
- Install the new driver as a clean install. For NVIDIA, check the box for "Perform a clean installation." For AMD, use the factory reset option.
Fix 2: Increase the TDR delay (the real fix for most people)
If your GPU is just slow on a particular frame (not actually hung), giving it more time works. Here's how:
- Press Win + R, type
regedit, hit Enter. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. - Right-click on the right side, choose New > DWORD (32-bit) Value. Name it
TdrDelay. - Double-click it, set the Base to Decimal, and enter
10(that's 10 seconds). - Restart your PC.
I've set this on a bunch of machines that had micro-stutter crashes. It doesn't mask a real hardware problem, but it stops the false positives. If you're running a game that occasionally has a 3-second shader compile hiccup, this is your fix.
Fix 3: Check your overclock and power settings
If you're running MSI Afterburner or EVGA Precision, drop your core clock back to stock and test. Overclocks that pass Furmark can still crash in games because games use the GPU differently. I've seen a +100 MHz overclock be stable for weeks, then suddenly crash in a specific game. Also, go into Windows Power Options > High Performance (or Ultimate Performance). Some laptop GPUs throttle weirdly if you're on Balanced.
Fix 4: If it still crashes, try these
Sometimes the standard stuff doesn't cut it. Here's my backup list, in order of what I've had the most success with:
- Disable hardware-accelerated GPU scheduling in Windows Settings > System > Display > Graphics > Default graphics settings. I've seen this cause the error on Windows 11 with certain drivers.
- Verify game files on Steam/Epic. A corrupt game file can trigger this, especially if the crash always happens in the same spot.
- Lower in-game graphics settings – specifically, turn off ray tracing if it's on. It's not the fix you want, but it's a fix.
- Update your BIOS if you're on an older motherboard. I had a client with a B450 board that fixed it after a BIOS update.
Prevention tips
Don't overclock your GPU beyond what it can handle for gaming. Use a stress test like OCCT for an hour, not just Furmark for 10 minutes. Also, keep your driver updated, but don't install every new one the day it drops—wait a week for others to be the beta testers. And if your PSU is over 5 years old, consider replacing it. I've seen a dying PSU cause this exact error, and it took me a week to figure it out because the voltages looked fine under load but dipped during peak spikes.
Last thing: if you're playing an older game on Windows 11, try compatibility mode. I had a client who couldn't play Civ VI without this error until we forced Windows 8 compatibility. Sometimes the OS gets in the way.
That's it. Start with the driver update, then the TdrDelay tweak, and you'll fix 9 out of 10 cases. The rest usually need the overclock check or a deeper hardware look.