Thuml News

This site has affiliate links.

Try This
All Recent News
Gaming Problem: Call of Duty (PC) “DirectX encountered an unrecoverable error” crashes (0x887A0005 / 0x887A0006 / 6068 / 6070) that many players can’t reliably fix (2026-01-03 23:00)
Jan 3, 2026 11:00 p.m.

Problem: Call of Duty (PC) “DirectX encountered an unrecoverable error” crashes (0x887A0005 / 0x887A0006 / 6068 / 6070) that many players can’t reliably fix

Published: 2026-01-04 12:00 (local time)

Quick Summary

  • Many PC players report Call of Duty titles (especially Warzone / Black Ops-era builds) crashing to desktop with “DirectX encountered an unrecoverable error,” often showing codes like 0x887A0005, 0x887A0006, 6068, or 6070.
  • It’s widespread across different CPUs/GPUs (NVIDIA and AMD), and it can appear “out of nowhere” after an update or driver change.
  • There is no single official, universal fix; multiple competing root causes are plausible.
  • However, several workarounds are repeatedly reported to improve stability (driver rollback/hotfixes, removing overlays, reducing VRAM targets, BIOS/XMP changes, and Windows repairs).
  • If the crash persists after the steps below, you’ll likely need to open an official ticket (and include logs + dxdiag) because you may be hitting a game-side bug or a specific hardware/driver interaction.

What’s happening

Players on PC report that Call of Duty will abruptly crash during matches, in menus, or after a predictable amount of playtime (for some, around 30–120 minutes). The crash often displays a message like “DirectX encountered an unrecoverable error,” along with error codes (commonly 0x887A0005 and 0x887A0006, and sometimes 6068/6070). In community reports, the problem affects both Steam and Battle.net installs and appears across a range of hardware, including high-end systems.

Recent examples include players reporting recurring DirectX crashes in early January 2026 community posts (suggesting the issue is still actively affecting users right now). Users frequently note they’ve already tried common steps (shader cache deletion, Windows updates, GPU driver updates, reinstalls) without a clear solution.

Likely causes (what research suggests)

  • Driver/game build incompatibility (or a regression): Community troubleshooting repeatedly points to certain driver versions being unstable with specific CoD builds, while rolling back to an older WHQL or installing a vendor hotfix improves stability for some users.
  • Instability from CPU/RAM boosting profiles: Some players report improvements after disabling XMP/EXPO or aggressive CPU boost features (suggesting borderline memory/IMC instability can surface specifically under CoD’s load pattern).
  • Overlays / capture / monitoring hooks: Multiple reports indicate reducing background hooks (FPS overlays, monitoring, RGB tools) can prevent crashes, implying conflicts with how the game, anti-cheat, and DirectX present frames.
  • Corrupted game files or Windows component corruption: Verifying game files and repairing Windows system components (SFC/DISM) are standard, evidence-backed steps and have helped some users eliminate recurring DirectX-related failures.
  • VRAM pressure / streaming behavior: Some users report fewer crashes after lowering VRAM targets or reducing texture/streaming settings, consistent with instability triggered by memory pressure or allocation behavior.

Solutions & Workarounds

1) Roll back your GPU driver (or try an official hotfix if available)

Who it helps: PC players on NVIDIA or AMD who started crashing after a driver update (or after a CoD update while on newer drivers).

  • Steps:
    • Note your current driver version.
    • Download a known-stable older driver (one release earlier is a good start). If NVIDIA has published a hotfix for a known crashing issue, test that hotfix as an alternative.
    • Install the older/hotfix driver (clean install is recommended when switching branches).
    • Reboot, then test 3–5 matches (or at least 60–90 minutes if your crashes are time-based).
  • Risks / tradeoffs: Older drivers can reduce performance in newer games or miss security fixes; hotfix drivers can be less validated than WHQL.
  • Stop & contact official support when: You can reproduce the crash across multiple driver versions (including a rollback) and it happens on a “fresh” driver install.

2) Verify/repair the game installation (Steam or Battle.net)

Who it helps: Anyone who updated recently, migrated install locations, or has repeated crashes shortly after launch.

  • Steps (Steam example):
    • Open Steam Library → right-click the game → Properties.
    • Go to Installed Files/Local Files → choose “Verify integrity of game files”.
    • Reboot after verification completes, then test again.
  • Risks / tradeoffs: Minimal; it may re-download large files.
  • Stop & contact official support when: Verification repeatedly finds issues every run, or the game continues crashing even after a clean reinstall.

3) Disable overlays and “hooking” software (temporarily, for testing)

Who it helps: Players using Discord overlay, GeForce/AMD overlays, Windows Game Bar, Rivatuner/MSI Afterburner overlays, recording tools, or RGB/monitoring utilities.

  • Steps:
    • Turn off Discord overlay for CoD.
    • Disable Xbox Game Bar and background recording features.
    • Disable NVIDIA/AMD in-game overlays and performance HUDs.
    • Close monitoring apps (RTSS, Afterburner overlay, hardware polling tools) and retest.
  • Risks / tradeoffs: You lose overlays, capture convenience, and monitoring while testing.
  • Stop & contact official support when: Crashes occur even on a “clean boot” style test (minimal startup apps + overlays off).

4) Reduce VRAM pressure (lower VRAM target / textures / streaming)

Who it helps: Systems with 6–10GB VRAM (or anyone seeing crashes correlate with certain maps/modes, or after a few matches).

  • Steps:
    • Lower texture resolution and texture streaming settings.
    • If the game offers a VRAM usage target/slider, reduce it (many players report stability improvements around 60–65% versus higher targets).
    • Restart the game after changing these settings and test for at least an hour.
  • Risks / tradeoffs: Reduced visual quality.
  • Stop & contact official support when: Crashes persist even at conservative settings and capped framerate.

5) Remove “borderline” overclocks: disable XMP/EXPO (test) and revert CPU/GPU to stock

Who it helps: Players running XMP/EXPO, PBO/boost tweaks, undervolts, or GPU/RAM overclocks (even mild ones), especially if only CoD crashes.

  • Steps:
    • In BIOS/UEFI, disable XMP/EXPO (test at default RAM speeds).
    • Disable aggressive CPU boost tuning (or restore “Optimized Defaults”).
    • Set GPU to stock clocks/voltage (no undervolt/OC) and retest.
  • Risks / tradeoffs: Performance may drop; changing BIOS settings carries some risk if done incorrectly.
  • Stop & contact official support when: The game crashes even at full stock settings, suggesting a game/driver bug rather than instability.

6) Repair Windows system components (SFC + DISM)

Who it helps: Players who see multiple games/apps behaving oddly, Windows update issues, or unexplained DirectX-related errors.

  • Steps:
    • Open Command Prompt as Administrator.
    • Run: sfc /scannow and let it complete.
    • If issues are found (or if SFC can’t fix everything), run DISM health/repair commands (CheckHealth/ScanHealth/RestoreHealth) and reboot.
    • After DISM, run sfc /scannow again.
  • Risks / tradeoffs: Low risk, but repairs can take time; DISM may require internet access for component retrieval.
  • Stop & contact official support when: Windows repairs succeed but CoD still crashes consistently (provide your dxdiag and crash timestamps).

Prevention (so it doesn’t come back)

  • Delay “day-one” GPU driver updates if your system is stable; wait for feedback or hotfixes when a new driver drops.
  • Keep one known-stable driver installer saved locally so rollback is quick.
  • Limit overlays and hardware polling while playing competitive shooters (especially after major updates).
  • Keep BIOS current if your platform vendor lists stability/memory compatibility fixes.
  • After big CoD updates, retest stability before re-enabling overclocks/undervolts.

FAQ

Q: Is this only an NVIDIA issue (or only an AMD issue)?
A: Reports show it can happen on both. Some users see improvement with specific driver versions, which suggests driver-game interactions rather than one vendor alone.

Q: I reinstalled the game and it still crashes. What’s next?
A: Test a driver rollback/hotfix, disable overlays, and temporarily remove XMP/EXPO and any undervolts/overclocks to rule out instability.

Q: Why does only Call of Duty crash while other games are fine?
A: Some engines/stacks stress hardware and drivers differently; a “stable” undervolt or memory profile in other games can still fail in CoD.

Q: Should I switch from Steam to Battle.net (or vice versa)?
A: It’s not a guaranteed fix, but if you suspect file/launcher issues, it can be a useful isolation test. Try verify/repair first.

Q: When should I stop tweaking and open a support ticket?
A: If you can reproduce the crash on stock CPU/GPU/RAM settings, overlays off, verified files, and at least two driver versions, it’s time to contact official support with full system details and logs.

Q: What should I include in a support ticket?
A: Your dxdiag output, GPU driver version, Windows build, exact error code, when it happens (match start, mid-game, menus), and what you already tried.

Sources & References

Back to Blog