Fix 'DirectX function failed' in Call of Duty: Warzone (getDeviceRemovedReason)

When this error hits

You're mid-match in Call of Duty: Warzone (Season 3 or later) and suddenly the screen freezes for 3-5 seconds. Then it kicks you to desktop with a black box: DirectX function 'GetDeviceRemovedReason' failed with DXGI_ERROR_DEVICE_HUNG. This happens most often during intense firefights near downtown Caldera or Al Mazrah, when the GPU is under heavy load with smoke, shadows, and distant draw calls.

What's actually going on

Your graphics driver sent a command to the GPU, but the GPU didn't respond within a timeout (Windows default is 2 seconds). Windows then resets the driver state, and Warzone doesn't handle that reset gracefully. The error isn't about DirectX being broken—it's about the GPU stalling. Common triggers: unstable overclocks, VRAM running at 95%+ constantly, or driver version that doesn't play nice with Warzone's renderer.

The fix that works 90% of the time

I've seen this on both Nvidia (RTX 3070, 3080, 4060) and AMD (RX 6700 XT, 7900 XTX). Skip reinstalling Windows or buying a new PSU—try these steps first, in order.

Step 1: Lower render worker count

Warzone by default sets rendererWorkerCount to your logical cores. On a 6-core CPU with hyperthreading, that's 12 workers—too many, often causing the GPU to wait. Drop it to your physical core count minus 1.

1. Go to Documents > Call of Duty > players > options.3.cod (or options.4.cod for Warzone 2.0).
2. Open with Notepad. Find rendererWorkerCount:0.0 = "4" (your number will differ).
3. Change it to "5" for a 6-core CPU, "6" for 8-core, "4" for 4-core. For hyperthreaded 6-core (12 threads), use 5.
4. Save the file, right-click it > Properties > check Read-only so the game doesn't revert it.

This gives the GPU breathing room.

Step 2: Increase TdrDelay in the registry

The default 2-second timeout is too tight for Warzone's heavy draws. Raise it to 8 seconds.

1. Press Win + R, type regedit, hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers.
3. Right-click in the right pane > New > DWORD (32-bit). Name it TdrDelay.
4. Double-click it, set Base to Decimal, enter 8.
5. Also create TdrDdiDelay as a DWORD, set to 8 decimal.
6. Close regedit, restart.

This tells Windows to wait up to 8 seconds before thinking the GPU hung. Real crashes still happen—you don't want to hide those—but transient stutters won't kick you out.

Step 3: Disable GPU overclock (even factory OC)

I know this one hurts. But 90% of Warzone's GPU hang errors I've debugged trace back to instability at high clock speeds. Even factory-overclocked cards (like an EVGA FTW3 or ASUS Strix) push too close to the edge for Warzone's shader compilations.

• Nvidia: Open MSI Afterburner (or Precision X1). Drop core clock by -50 MHz, memory by -100 MHz. Apply and test.
• AMD: Open Adrenalin > Performance > Tuning. Set GPU clock to -100 MHz, VRAM clock to -50 MHz.
• Also disable XMP/DOCP in BIOS temporarily. Warzone is sensitive to unstable RAM timings—I've seen it fix the error on Ryzen 5600X + DDR4-3600 systems that were rock solid in other games.

Step 4: Use a stable driver version

Cutting-edge drivers often break Warzone. For Nvidia, 537.58 (October 2023) is widely reported as the most stable for Warzone 2.0. For AMD, 23.11.1 (November 2023) works best. Use DDU (Display Driver Uninstaller) in Safe Mode to clean old drivers, then install these specific versions.

• Nvidia 537.58 download: link
• AMD 23.11.1: link

Still crashing? Check these

• VRAM usage: In Warzone's settings, turn Texture Resolution from High to Normal. High uses 6-8GB VRAM, which on an 8GB card leaves no room for spikes. Monitor with MSI Afterburner OSD.
• Power supply: If your PSU is 600W or less and you're on an RTX 3080 or RX 6800 XT, you're hitting transient spikes that trip OCP. Undervolt the GPU (-300mV core) instead of overclocking.
• Windows Graphics Settings: Turn off Hardware-accelerated GPU scheduling (Settings > System > Display > Graphics > Default graphics settings). Some users report it causes the same error.

I've fixed this error on five different rigs now. Start with the render worker count and TdrDelay—that alone stops the crash for most people. The registry edit looks scary but it's safe and reversible. You've got this.