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.”
Adding onto this:
My Crashdump is the following:
FILE_IN_CAB: CrashDump_2025.10.18_22.15.31.828.mdmp
COMMENT: Frostbite MiniDump. Address: 1449567de (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=000000000007025d rbx=0000001e2d90c2b0 rcx=0000001e2d90c2b0
rdx=0000000000000000 rsi=000000007dd8fec8 rdi=3fae40f14109ffff
rip=00000001449567de rsp=000000007dd8fca0 rbp=000000007dd8fda0
r8=0000001e2d90c2b0 r9=0000001e2d90c2b0 r10=0000001e2dc3955b
r11=000000007dd8fe48 r12=000000000007025d r13=3fae40f1410a01a7
r14=0000000000000010 r15=000000007dd8fe98
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
bf6!ffxFsr2ResourceIsNull+0x21534ee:
00000001`449567de 418b4d10 mov ecx,dword ptr [r13+10h] ds:3fae40f1`410a01b7=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00000001449567de (bf6!ffxFsr2ResourceIsNull+0x00000000021534ee)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
PROCESS_NAME: bf6.exe
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
No event log, also no device hung error is reported, the only source here for me is the crashdump, windows itself doesnt even report the crash in the even log.
Sadly I dont have an AMD GPU maybe that is why the crash and logs look a bit different.
In addition to that, if I keep trying to play the game, eventually its a reboot not just a crash to desktop.
I have not payed attention to whether or not it happens during scoping or not sadly.
But it usually happens after the next match loads and then about 15 mins into that second match.
So basically I can play one game plus 15 mins.
PolyMorris It has nothing to do with your GPU not being from AMD.
I’m getting the same crash dump report, and I do have an AMD GPU (7900XTX).
Silent crash to desktop, no error message, no event log.
It’s strange that you can play for a while before it crashes. For me, it crashes as soon as I try to load a map. I’ve never even got my boots on the ground in-game. It was the same issue during the beta weekends. Really thought they would have fixed it by now.
