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.”
My Brother has the same issue (also with Vega64) and appart from multiplayer crashes after ~5-15 min in, it also 100% crashes in the first campain, when the main character gets out of the car. So load the first campain, skip the intro, move through the short shoot out, enjoy the car ride, and then the moment you get out of the car and look at a tree to the middle left of the screen it crashes every time for him (takes about 5:40min to get there). FSR on or off doesn't matter. I will add the screenshot i have send him and also some crash dump files if possible. When I analyse them on my PC however, (different CPU but also vega GPU) i don't get the same StackText so i will add the actual crash text in a later answer from his pc soon.
His System:
GPU: AMD RX Vega64 (Stock Speed with the current 25.8.1 driver)
CPU: AMD Ryzen 9 5950X (Actual slightly underclocked and higher voltages as its an early Zen3 the shows clear aging signs at stock voltages ...)
OS: Win11 24H2
The crashfiles from 19.11.2025 happend during the first campain i restarted with different settings. The earlier ones are mostly multiplayer. Hope they are also uploaded and visible for atleast ea.
The screenshot i have send him.
