Problem: Call of Duty (Warzone / Black Ops 6 / Black Ops 7 integration) PC “DirectX encountered an unrecoverable error” crashes (0x887A0005 / 0x887A0006)
Published: 2025-12-30 13:10 (local time)
Quick Summary
- Many PC players report Call of Duty hard-crashing to desktop with “DirectX encountered an unrecoverable error,” commonly 0x887A0005/0x887A0006.
- Reports spike after major CoD updates/integrations; a recent example is posts following the Warzone + Black Ops 7 integration in late December 2025.
- There is no single universal fix; multiple causes appear plausible (drivers, shader/pipeline cache corruption, unstable OC/XMP, Windows graphics scheduling, or game-side bugs).
- Workarounds that help real players include clearing specific CoD config/cache files, rebuilding shaders, driver rollbacks/clean installs, disabling HAGS, and stability-first BIOS/RAM settings.
What’s happening
Across recent Call of Duty titles on PC (including Warzone and Black Ops entries), players are hitting sudden crashes that throw a DirectX dialog (often “DirectX encountered an unrecoverable error”) and then close the game. The most commonly reported error codes in these recent threads are 0x887A0005 and 0x887A0006, sometimes appearing mid-match, during loading, or even while sitting in menus.
The problem is widespread in the sense that it shows up across different hardware configurations (NVIDIA and AMD GPUs; desktop PCs and handheld Windows devices), and across multiple launchers (Battle.net, Steam, and Microsoft Store/Game Pass). Players frequently describe trying “everything” (reinstalls, settings changes, updates) without a reliable, permanent fix.
A very recent example: following the Warzone integration with Call of Duty: Black Ops 7, users posted that the issue started “after this new integration” and persisted despite OS reinstalls and driver changes, suggesting a current wave of the same long-running crash pattern. While this is not definitive proof of a single root cause, it does show the issue is actively affecting players in December 2025.
Likely causes (what research suggests)
- Game update + shader/config conflicts: Multiple players report the crashes begin immediately after a CoD update, and some regained stability by forcing the game to regenerate certain local config/shader-related files (a strong hint that corrupted/invalid cached data can be involved).
- Driver instability or bad interactions with specific driver branches: Some users report stability only after rolling back to a known-good GPU driver, while others improve after updating or doing a clean install. This inconsistency suggests the “right” driver can vary by GPU model and system.
- System-level stability (XMP/EXPO, CPU/GPU boosts, undervolt/overclock): Players sometimes report improvements after disabling XMP or otherwise reducing instability. That doesn’t mean the PC is “bad,” but CoD can be unusually sensitive to borderline instability.
- Windows graphics stack features (HAGS): Disabling Hardware-Accelerated GPU Scheduling helps some users in other DX-heavy games, and at least some CoD players report fewer crashes with similar changes. This is a “try it and see” lever rather than a confirmed root cause.
Solutions & Workarounds
1) Force CoD to regenerate local config files (delete the specific “s.1.0.cod…” files)
Who it helps: PC players (all GPUs) whose crashing started right after a CoD update/integration and persists despite reinstalls.
Steps:
- Close the game completely.
- Open your Call of Duty “Documents” configuration folder (commonly inside your user Documents for CoD).
- Locate files with names similar to: s.1.0.cod24.m, s.1.0.cod24.txt0, s.1.0.cod24.txt1 (the exact prefix can vary by title/version).
- Back them up (copy to a safe folder), then delete the originals.
- Launch CoD again; it should rebuild fresh files. Re-apply your graphics settings carefully.
Risks/tradeoffs: You may lose stored graphics/settings presets; the game may behave like “first launch” until reconfigured.
Stop & contact support when: Crashes continue after one full regeneration cycle and shader rebuild (see next fix), especially if you can reproduce it reliably in the same scenario.
2) Rebuild shaders and avoid “too low” settings if they trigger instability on your build
Who it helps: Players who crash shortly after entering a match, and players who notice crashes correlate with certain graphics presets (some report low settings being worse).
Steps:
- In CoD graphics settings, look for a Shader (Re)Compilation / Restart Shader Preloading option and run it.
- After shader rebuild, test a “Medium/High” baseline preset instead of extremely low settings.
- Restart the game and test multiple matches without changing settings mid-session.
Risks/tradeoffs: Higher settings can raise GPU load/temps; watch thermals and stability.
Stop & contact support when: Crashes persist even on conservative, stable settings and after shader rebuild.
3) Clean-install GPU drivers (DDU) and then try a rollback OR a known-stable branch
Who it helps: NVIDIA/AMD players where the crashes began after a driver update (or where many driver versions have been layered over time).
Steps:
- Use a driver-cleaning method (commonly DDU in Safe Mode) to remove the current GPU driver completely.
- Install a stable driver version (either the newest WHQL, or a commonly-reported stable older version for your GPU).
- Reboot, then launch CoD and test stability for at least a few matches.
Risks/tradeoffs: Rolling back can reduce performance in other games; new drivers can introduce new bugs. You may need to iterate.
Stop & contact support when: You’ve tested at least two driver versions (newest + one older) with clean installs and still crash consistently.
4) Disable Hardware-Accelerated GPU Scheduling (HAGS) in Windows
Who it helps: Windows 11/10 users seeing unexplained DX crashes across DX12-heavy titles, including CoD.
Steps:
- Windows Settings → System → Display → Graphics.
- Open “Default graphics settings” (or advanced settings, depending on Windows version).
- Turn off Hardware-accelerated GPU scheduling.
- Reboot and retest CoD.
Risks/tradeoffs: May slightly impact performance/latency in some setups; results vary (“YMMV”).
Stop & contact support when: Disabling HAGS changes nothing and you can reproduce crashes reliably.
5) Remove instability variables: disable XMP/EXPO, revert GPU OC/UV, and (if needed) gently underclock
Who it helps: Players on aggressive RAM profiles (XMP/EXPO), GPU undervolts, or high boost clocks who only crash in CoD.
Steps:
- Enter BIOS and temporarily disable XMP/EXPO (run RAM at JEDEC defaults) for testing.
- Reset GPU tuning to stock in NVIDIA/AMD control software.
- If still crashing, try a small negative core clock offset (or cap max boost) and test again.
Risks/tradeoffs: Performance loss; underclocking is a workaround, not a true fix.
Stop & contact support when: Stock settings still crash and you have evidence it started after a specific CoD patch/integration.
6) If you’re on PC Game Pass/Microsoft Store, test another launcher install (or vice versa)
Who it helps: Players who suspect a launcher-specific file/permissions issue (some reports indicate different stability between Battle.net and Game Pass setups).
Steps:
- If you’re on Game Pass, test Battle.net (or Steam) if you have access; keep settings identical.
- Do not copy config files between installs at first—start clean.
- Retest stability before reintroducing custom config tweaks.
Risks/tradeoffs: Large download sizes; requires access to another platform/entitlement.
Stop & contact support when: The game crashes across multiple launchers on the same machine.
Prevention (so it doesn’t come back)
- After major CoD updates, rebuild shaders once and avoid rapidly flipping many graphics settings in one session.
- Keep a record of your “known stable” GPU driver version so you can roll back quickly.
- Avoid stacking multiple overlays/tuners at once (FPS overlays, capture tools, RGB utilities) until stability is confirmed.
- Prefer stability-first BIOS settings (especially RAM) when troubleshooting CoD; re-enable XMP/EXPO only after several stable sessions.
FAQ
Q: Is this definitely a game bug?
A: Not definitively. Evidence suggests multiple contributing factors: some fixes are purely local (cache/config regeneration), while others point to drivers or system stability. The pattern of “it started after an update/integration” strongly suggests at least part of it is game-side.
Q: Why does CoD crash but other games don’t?
A: Some engines are more sensitive to borderline GPU/RAM instability, shader cache issues, or specific driver paths. CoD appears to be unusually sensitive for many users.
Q: I reinstalled the game—why didn’t it help?
A: Reinstalls don’t always clear user Documents config/shader-related files or underlying driver/cache issues. That’s why deleting specific local files and doing clean driver installs can matter.
Q: Should I switch to DX11?
A: Some players try DX11 options, but results are inconsistent. If available, it’s worth testing, but it’s not a guaranteed fix.
Q: When should I stop tweaking and open a ticket?
A: If you can reproduce the crash consistently after trying: (1) config regeneration + shader rebuild, (2) one clean driver install + one rollback, and (3) stock stability settings (no XMP/EXPO/OC), it’s time to contact official support with logs and exact error codes.
Q: Could my GPU be defective?
A: It’s possible but not the first assumption. Try software/driver/cache steps first. If CoD-only crashes persist across clean OS/driver baselines and other demanding games also start failing, then hardware diagnostics become more likely.