DXGI_DEVICE_HUNG at “Find Match” — Began v1.0.1.6, Persists in v1.1.1.0
After successfully playing in early/mid October, a week ago and continuing after updating to 1.1.1.0:
DXGI_ERROR_DEVICE_HUNG "The GPU will not respond to more commands."
whenever I press “Find Match” in the Multiplayer menu.
The game boots normally, passes shader installation, and runs all menus without issue — but the GPU driver resets exactly when matchmaking begins.
System:
- NVIDIA GTX 1080 Ti (11 GB)
- Windows 11 x64, fully updated
- Driver versions tested: 552.44 → 581.57 (clean DDU installs)
What I’ve tried:
- Full DDU reinstall of NVIDIA drivers in Safe Mode
- Forced DX11 (-dx11), disabled Ray Tracing / DLSS / Reflex
- Cleared shader & NVIDIA caches, disabled all overlays
- Applied TdrDelay=10, lowered power limit & clocks, verified files
- Stress-tested GPU (Heaven / 3DMark) → no instability
The crash occurs 100% reproducibly at the same step when clicking "Find Match" in multiplayer menu. This looks like a DX12 resource-init bug in the Frostbite engine on Pascal GPUs (1080 Ti / 1070 Ti).
I just saw a post from another player describing a simple workaround that also worked for this bug. Sending this so the Community Manager can help flag the underlying issue to the dev team as it's pretty telling about the root cause:
“Hello friends, I'm not sure how similar our problems are. I'd start the game, be able to get to the main menu, and when I would select multiplayer it would crash with the DirectX Hung error. If you have this problem, go to Loadouts, select Assault, then go to Multiplayer and click your desired game mode. I'm not sure why this works — I’d assume it's something with the character model on the multiplayer home screen. I tried most things prior: uninstalling/reinstalling drivers, different launch options (-dx12, -dx11, etc.), changing graphics settings. But this one simple thing fixed it. Hope this helps someone.”
After trying this myself (selecting Assault before entering Multiplayer), the game loaded into a match successfully for the first time since the issue started.
It seems likely that something in the character model or loadout initialization on the multiplayer screen is causing the DXGI crash, especially post-v1.0.1.6 → v1.1.1.0.
