This is still on-going for thousands of players EA, can we get an update?
Happened twice during the first 35 hours of play, that I can live with.
Then 5 times over 4 hours.
Now it's every 2-20 minutes. I can't play the game anymore. I can't finish a match.
Tried every solution Ive come across so far, reinstalled the game, direct X, swapped drivers,
installed/uninstalled windows updates, resizable bar on/off, DCOP/XMP on/off, PBO fiddling and on/off, page file sizes, shader caches both for the game and dx, all in-game settings wiped, from off/low to overkill etc. etc.
Im at my wits end here and I put in a refund request to Steam and I suggest others do as well until this is fixed since the game is just broken on a technical level at the moment.
Hi everyone,
I'm creating my own post about the DXGI error because, although I've seen others mentioning it, I want to share my specific case and findings. After (maybe) 100 crashes since launch — and even back in the Beta — I think I’ve gathered enough consistent data that might help identify what’s happening.
While this issue may vary slightly from player to player, my crashes are 100% reproducible under certain conditions. I believe it’s worth documenting here, hoping it might reach the devs at EA/DICE for further investigation.
Short summary
It seems there’s a potential bug in the FSR2 implementation, where the game passes a null or invalid texture/buffer to FSR2. When FSR2 tries to access that invalid resource, DXGI triggers a crash.
Why I believe this:
1. Crashes usually occur when swapping sights quickly or when there’s a zoom event — e.g., 3x scopes, RPGs, vehicle weapons, etc. Not always, but ~99% of the time.
2. Every crash dump shows the same call stack reference:
bf6!ffxFsr2ResourceIsNull+0x22ad1a0 bf6!ffxFsr2ResourceIsNull+0x22ad834
The crash is always a Device Hung (0x887A0006), suggesting the GPU is processing invalid data coming from FSR2.
So in summary:
Things I’ve tested (none fixed it)
- Disabled FSR as much as possible → tried TAA, no upscaling, no AMD frame generation → same crash.
- Launch options: -dx12 -noasync → no effect.
- Re-tested FSR on/off and various AA modes → crashes happen faster with FSR enabled.
- Cleared shader/cache files between tests.
- Disabled all overlays (Radeon, Discord, Steam, etc.).
- Edited TDR registry values (Delay and DdiDelay) → no stable improvement.
- Underclocked GPU core frequency → no change.
- Many more smaller tests with same results.
Key debug extract (WinDbg !analyze -v)
EXCEPTION_CODE: 0x887A0006 (DXGI_ERROR_DEVICE_HUNG) PROCESS_NAME: bf6.exe MODULE_NAME: bf6 FAULTING_FUNCTION: bf6!ffxFsr2ResourceIsNull STACK (top frames): bf6!ffxFsr2ResourceIsNull+... KERNELBASE!RaiseException+...
Failure indicates FSR2 attempted to access an invalid/null resource during frame reconstruction.
System
GPU: AMD RX Vega 64
Driver: Adrenalin 25.8.1 (clean install via DDU, last driver available for the Vega)
CPU: Ryzen 5 3600X
OS: Windows 10 22H2
API: DirectX 12
If anyone else is facing the same issue, especially with AMD GPUs, please share your crash stack or reproduction pattern — the more data we gather, the better the chances EA/DICE can identify it.
Summary
“This is a consistent, reproducible crash seemingly caused by an invalid FSR2 resource being passed to DirectX during zoom/scope transitions. Requires dev-side fix.”
