Forum Discussion

Seasoned Traveler

5 months ago

DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG

In my experience, turning off overclock is preventing crashes. This does not fix everyone's issue. I can only play for a couple minutes, and I get this error message. Direct function "m_submitFenc...

crashing

Zevered

Seasoned Adventurer

5 months ago

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.

bySkriK

New Rookie

5 months ago

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:

Game passes FSR2 a null resource
DirectX tries to process it
GPU hangs → Windows terminates the process → crash

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.”

PolyMorris
New Novice
5 months ago
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.
- Rixtn
  Seasoned Adventurer
  4 months ago
  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.
budekim
Rising Rookie
5 months ago
Chiming in to say I'm having the same exact error as you on a 9060 XT. And I played fine for an entire week without this happening, just started today.
Rixtn
Seasoned Adventurer
4 months ago
+1
"bf6!ffxFsr2ResourceIsNull"
I'm with you guys... let's hope for a fix soon.
Siegmund99_GER
Seasoned Newcomer
4 months ago
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.
Siegmund99_GER
Seasoned Newcomer
3 months ago
And finally, here are the promised crash texts. Three from 19th November when i could 100% replicate a game crash in the first campain at exactly the same moment every time and two older ones (from 12th october) when he tried to play online. The never ones clearly state fsr2RecourceIsNull while the older one don't have such a clear statement.
19:11.25_3 campaign crash:
ntdll!NtGetContextThread+0x14:
00007ffb`0ef63c14 c3 ret
0:014> !analyze -v
................................................................
................................................................
....................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 437
Key : Analysis.Elapsed.mSec
Value: 1588
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 359
Key : Analysis.Init.Elapsed.mSec
Value: 8331
Key : Analysis.Memory.CommitPeak.Mb
Value: 286
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Failure.Bucket
Value: XAML_887a0006_bf6.exe!Unknown
Key : Failure.Exception.Code
Value: 0x887a0006
Key : Failure.Exception.IP.Address
Value: 0x7ffb0c8680da
Key : Failure.Exception.IP.Module
Value: KERNELBASE
Key : Failure.Exception.IP.Offset
Value: 0xc80da
Key : Failure.Hash
Value: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Key : Failure.ProblemClass.Primary
Value: XAML
Key : Timeline.OS.Boot.DeltaSec
Value: 6344
Key : Timeline.Process.Start.DeltaSec
Value: 367
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 1.0.387.51411

FILE_IN_CAB: CrashDump_2025.11.19_15.58.47.771.mdmp
COMMENT: Frostbite MiniDump. Address: 7ffb0c8680da (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=00007ffb0c653780
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006
rip=00007ffb0c8680da rsp=0000000066d5d310 rbp=0000000000000000
r8=0000000000000000 r9=00000002a3054950 r10=00000000000051b0
r11=0000000000001988 r12=0000000000000044 r13=000000005a696690
r14=0000000000000000 r15=00000000887a0006
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
KERNELBASE!RaiseException+0x8a:
00007ffb`0c8680da 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffb0c8680da (KERNELBASE!RaiseException+0x000000000000008a)
ExceptionCode: 887a0006
ExceptionFlags: 00000080
NumberParameters: 0
PROCESS_NAME: bf6.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - Die GPU antwortet auf keine weiteren Befehle mehr. Dies liegt wahrscheinlich daran, dass von der aufrufenden Anwendung ein ung ltiger Befehl bergeben wurde.
EXCEPTION_CODE_STR: 887a0006
STACK_TEXT:
00000000`66d5d310 00000001`44ab6300 : 00000000`00000bf9 00000000`37c0a080 00000000`39c40820 00000000`00000003 : KERNELBASE!RaiseException+0x8a
00000000`66d5d410 00000001`44ab6994 : 00000000`5a696690 00000000`0d7363b8 0000b498`d44b8cd1 00000001`4501da45 : bf6!ffxFsr2ResourceIsNull+0x22adca0
00000000`66d6f610 00000001`44ab4d13 : 00000000`5a696690 579ef505`b0cb6900 00000002`401be480 21641f81`145beb00 : bf6!ffxFsr2ResourceIsNull+0x22ae334
00000000`66d6f660 00000001`449522b6 : 00010001`40000020 cf1fd39f`624bb4ab 00000000`5a693dd0 00000000`0d7363b8 : bf6!ffxFsr2ResourceIsNull+0x22ac6b3
00000000`66d6f770 00000001`4494f5c8 : 00000000`5a693dd0 00000000`5a693dd0 00000000`0d7363b8 00000000`5a693dd0 : bf6!ffxFsr2ResourceIsNull+0x2149c56
00000000`66d6f920 00000001`43957f61 : 00000002`6bd8c180 00000000`4d16b000 00000000`00000000 00000000`4d16b0bc : bf6!ffxFsr2ResourceIsNull+0x2146f68
00000000`66d6f9c0 00000001`4395f791 : 00000001`49ac54a8 00000001`4395e39d 00000000`00000000 00000000`66d6fbe0 : bf6!ffxFsr2ResourceIsNull+0x114f901
00000000`66d6fab0 00000001`4395ee00 : b498b29d`78310000 00000000`66d6fd80 00000001`49877218 ffffffff`ffffffff : bf6!ffxFsr2ResourceIsNull+0x1157131
00000000`66d6fb30 00000001`4395e969 : 00000000`048d2458 00000000`005c0100 00000000`00000003 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x11567a0
00000000`66d6fc50 00000001`4395cfa3 : 00000000`00000250 00000001`404f63a0 00000001`4975abf0 00000001`4975abf0 : bf6!ffxFsr2ResourceIsNull+0x1156309
00000000`66d6fcb0 00000001`4395c397 : 00000000`00000000 00000000`66d6ff00 00000000`39cc1800 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x1154943
00000000`66d6fe20 00000001`4345476b : 00000000`00000000 00000000`00000000 00000001`4985d340 00007ffb`0c85c91b : bf6!ffxFsr2ResourceIsNull+0x1153d37
00000000`66d6fe70 00000001`43456534 : 00000000`39cc1800 00000000`39cc17c0 00000000`00000003 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4c10b
00000000`66d6fec0 00000001`43064b6c : 00000001`4956a400 00000000`00000003 ffffffff`00000103 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4ded4
00000000`66d6ff00 00007ffb`0c6537b0 : 00000000`048db2a0 00000000`00000000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x85c50c
00000000`66d6ff30 00007ffb`0d4ee8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30
00000000`66d6ff60 00007ffb`0ee8c53c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`66d6ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c

SYMBOL_NAME: bf6+4ab6300
MODULE_NAME: bf6
IMAGE_NAME: bf6.exe
STACK_COMMAND: ~14s; .ecxr ; kb
FAILURE_BUCKET_ID: XAML_887a0006_bf6.exe!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.387.51411
FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Followup: MachineOwner
---------
19.11.25_2 campaign crash:
ntdll!NtGetContextThread+0x14:
00007ffb`0ef63c14 c3 ret
0:014> !analyze -v
................................................................
................................................................
....................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 437
Key : Analysis.Elapsed.mSec
Value: 1588
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 359
Key : Analysis.Init.Elapsed.mSec
Value: 8331
Key : Analysis.Memory.CommitPeak.Mb
Value: 286
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Failure.Bucket
Value: XAML_887a0006_bf6.exe!Unknown
Key : Failure.Exception.Code
Value: 0x887a0006
Key : Failure.Exception.IP.Address
Value: 0x7ffb0c8680da
Key : Failure.Exception.IP.Module
Value: KERNELBASE
Key : Failure.Exception.IP.Offset
Value: 0xc80da
Key : Failure.Hash
Value: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Key : Failure.ProblemClass.Primary
Value: XAML
Key : Timeline.OS.Boot.DeltaSec
Value: 6344
Key : Timeline.Process.Start.DeltaSec
Value: 367
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 1.0.387.51411

FILE_IN_CAB: CrashDump_2025.11.19_15.58.47.771.mdmp
COMMENT: Frostbite MiniDump. Address: 7ffb0c8680da (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=00007ffb0c653780
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006
rip=00007ffb0c8680da rsp=0000000066d5d310 rbp=0000000000000000
r8=0000000000000000 r9=00000002a3054950 r10=00000000000051b0
r11=0000000000001988 r12=0000000000000044 r13=000000005a696690
r14=0000000000000000 r15=00000000887a0006
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
KERNELBASE!RaiseException+0x8a:
00007ffb`0c8680da 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffb0c8680da (KERNELBASE!RaiseException+0x000000000000008a)
ExceptionCode: 887a0006
ExceptionFlags: 00000080
NumberParameters: 0
PROCESS_NAME: bf6.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - Die GPU antwortet auf keine weiteren Befehle mehr. Dies liegt wahrscheinlich daran, dass von der aufrufenden Anwendung ein ung ltiger Befehl bergeben wurde.
EXCEPTION_CODE_STR: 887a0006
STACK_TEXT:
00000000`66d5d310 00000001`44ab6300 : 00000000`00000bf9 00000000`37c0a080 00000000`39c40820 00000000`00000003 : KERNELBASE!RaiseException+0x8a
00000000`66d5d410 00000001`44ab6994 : 00000000`5a696690 00000000`0d7363b8 0000b498`d44b8cd1 00000001`4501da45 : bf6!ffxFsr2ResourceIsNull+0x22adca0
00000000`66d6f610 00000001`44ab4d13 : 00000000`5a696690 579ef505`b0cb6900 00000002`401be480 21641f81`145beb00 : bf6!ffxFsr2ResourceIsNull+0x22ae334
00000000`66d6f660 00000001`449522b6 : 00010001`40000020 cf1fd39f`624bb4ab 00000000`5a693dd0 00000000`0d7363b8 : bf6!ffxFsr2ResourceIsNull+0x22ac6b3
00000000`66d6f770 00000001`4494f5c8 : 00000000`5a693dd0 00000000`5a693dd0 00000000`0d7363b8 00000000`5a693dd0 : bf6!ffxFsr2ResourceIsNull+0x2149c56
00000000`66d6f920 00000001`43957f61 : 00000002`6bd8c180 00000000`4d16b000 00000000`00000000 00000000`4d16b0bc : bf6!ffxFsr2ResourceIsNull+0x2146f68
00000000`66d6f9c0 00000001`4395f791 : 00000001`49ac54a8 00000001`4395e39d 00000000`00000000 00000000`66d6fbe0 : bf6!ffxFsr2ResourceIsNull+0x114f901
00000000`66d6fab0 00000001`4395ee00 : b498b29d`78310000 00000000`66d6fd80 00000001`49877218 ffffffff`ffffffff : bf6!ffxFsr2ResourceIsNull+0x1157131
00000000`66d6fb30 00000001`4395e969 : 00000000`048d2458 00000000`005c0100 00000000`00000003 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x11567a0
00000000`66d6fc50 00000001`4395cfa3 : 00000000`00000250 00000001`404f63a0 00000001`4975abf0 00000001`4975abf0 : bf6!ffxFsr2ResourceIsNull+0x1156309
00000000`66d6fcb0 00000001`4395c397 : 00000000`00000000 00000000`66d6ff00 00000000`39cc1800 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x1154943
00000000`66d6fe20 00000001`4345476b : 00000000`00000000 00000000`00000000 00000001`4985d340 00007ffb`0c85c91b : bf6!ffxFsr2ResourceIsNull+0x1153d37
00000000`66d6fe70 00000001`43456534 : 00000000`39cc1800 00000000`39cc17c0 00000000`00000003 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4c10b
00000000`66d6fec0 00000001`43064b6c : 00000001`4956a400 00000000`00000003 ffffffff`00000103 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4ded4
00000000`66d6ff00 00007ffb`0c6537b0 : 00000000`048db2a0 00000000`00000000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x85c50c
00000000`66d6ff30 00007ffb`0d4ee8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30
00000000`66d6ff60 00007ffb`0ee8c53c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`66d6ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c

SYMBOL_NAME: bf6+4ab6300
MODULE_NAME: bf6
IMAGE_NAME: bf6.exe
STACK_COMMAND: ~14s; .ecxr ; kb
FAILURE_BUCKET_ID: XAML_887a0006_bf6.exe!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.387.51411
FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Followup: MachineOwner
---------
19.11.25_1 campaign crash:
ntdll!NtGetContextThread+0x14:
00007ffb`0ef63c14 c3 ret
0:019> !analyze -v
................................................................
................................................................
.........................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 375
Key : Analysis.Elapsed.mSec
Value: 1460
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 5882
Key : Analysis.Memory.CommitPeak.Mb
Value: 286
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Failure.Bucket
Value: XAML_887a0006_bf6.exe!Unknown
Key : Failure.Exception.Code
Value: 0x887a0006
Key : Failure.Exception.IP.Address
Value: 0x7ffb0c8680da
Key : Failure.Exception.IP.Module
Value: KERNELBASE
Key : Failure.Exception.IP.Offset
Value: 0xc80da
Key : Failure.Hash
Value: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Key : Failure.ProblemClass.Primary
Value: XAML
Key : Timeline.OS.Boot.DeltaSec
Value: 3817
Key : Timeline.Process.Start.DeltaSec
Value: 469
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 1.0.387.51411

FILE_IN_CAB: CrashDump_2025.11.19_15.16.39.989.mdmp
COMMENT: Frostbite MiniDump. Address: 7ffb0c8680da (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=00007ffb0c653780
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006
rip=00007ffb0c8680da rsp=000000006723ca50 rbp=0000000000000000
r8=0000000000000000 r9=000000029992f550 r10=00000000000043e4
r11=0000000000000a50 r12=0000000000000044 r13=000000005a776690
r14=0000000000000000 r15=00000000887a0006
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
KERNELBASE!RaiseException+0x8a:
00007ffb`0c8680da 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffb0c8680da (KERNELBASE!RaiseException+0x000000000000008a)
ExceptionCode: 887a0006
ExceptionFlags: 00000080
NumberParameters: 0
PROCESS_NAME: bf6.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - Die GPU antwortet auf keine weiteren Befehle mehr. Dies liegt wahrscheinlich daran, dass von der aufrufenden Anwendung ein ung ltiger Befehl bergeben wurde.
EXCEPTION_CODE_STR: 887a0006
STACK_TEXT:
00000000`6723ca50 00000001`44ab6300 : 00000000`00000bf2 00000000`37b84120 00000000`39bd0820 00000000`00000024 : KERNELBASE!RaiseException+0x8a
00000000`6723cb50 00000001`44aba06b : 00000000`5a77a5a0 00000000`6724ee50 00000003`393740d0 00000001`491f4368 : bf6!ffxFsr2ResourceIsNull+0x22adca0
00000000`6724ed50 00000001`44955549 : 00000000`4af585c0 00000000`4af5edc0 00000000`0001641c 00000000`0baa6960 : bf6!ffxFsr2ResourceIsNull+0x22b1a0b
00000000`6724f5c0 00000001`44954559 : 00000000`00000000 00000000`5a7732f0 00000000`0baa6960 00000000`4af5ec80 : bf6!ffxFsr2ResourceIsNull+0x214cee9
00000000`6724f910 00000001`43957f99 : 00000000`4afb9300 00000000`4d10ba00 00000000`00000000 00000000`4afb9300 : bf6!ffxFsr2ResourceIsNull+0x214bef9
00000000`6724f9c0 00000001`4395f791 : 00000001`49ac54a8 00000001`4395e39d 00000000`00000000 00000000`6724fbe0 : bf6!ffxFsr2ResourceIsNull+0x114f939
00000000`6724fab0 00000001`4395ee00 : 51777a1a`8c980000 00000000`6724fd80 00000001`498777f8 ffffffff`ffffffff : bf6!ffxFsr2ResourceIsNull+0x1157131
00000000`6724fb30 00000001`4395e969 : 00000000`0491bed8 00000000`01fe0100 00000000`00000007 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x11567a0
00000000`6724fc50 00000001`4395cfa3 : 00000000`00000250 00000001`404f63a0 00000001`4975abf0 00000001`4975abf0 : bf6!ffxFsr2ResourceIsNull+0x1156309
00000000`6724fcb0 00000001`4395c397 : 00000000`00000000 00000000`6724ff00 00000000`39c51800 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x1154943
00000000`6724fe20 00000001`4345476b : 00000000`00000000 00000000`00000000 00000001`4985d340 00007ffb`0c85c91b : bf6!ffxFsr2ResourceIsNull+0x1153d37
00000000`6724fe70 00000001`43456534 : 00000000`39c51800 00000000`39c517c0 00000000`00000007 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4c10b
00000000`6724fec0 00000001`43064b6c : 00000001`4956a700 00000000`00000007 ffffffff`00000103 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc4ded4
00000000`6724ff00 00007ffb`0c6537b0 : 00000000`047cb790 00000000`00000000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x85c50c
00000000`6724ff30 00007ffb`0d4ee8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30
00000000`6724ff60 00007ffb`0ee8c53c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`6724ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c

SYMBOL_NAME: bf6+4ab6300
MODULE_NAME: bf6
IMAGE_NAME: bf6.exe
STACK_COMMAND: ~19s; .ecxr ; kb
FAILURE_BUCKET_ID: XAML_887a0006_bf6.exe!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.387.51411
FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Followup: MachineOwner
---------
12.10.25_2 online crash (one month older but still maybe helpfull?):
ntdll!NtGetContextThread+0x14:
00007ffc`b1a45184 c3 ret
0:025> !analyze -v
................................................................
................................................................
................................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify timestamp for bf6.exe
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 359
Key : Analysis.Elapsed.mSec
Value: 1383
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 312
Key : Analysis.Init.Elapsed.mSec
Value: 11566
Key : Analysis.Memory.CommitPeak.Mb
Value: 110
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Failure.Bucket
Value: XAML_887a0006_bf6.exe!Unknown
Key : Failure.Exception.Code
Value: 0x887a0006
Key : Failure.Exception.IP.Address
Value: 0x7ffcaeb366ca
Key : Failure.Exception.IP.Module
Value: KERNELBASE
Key : Failure.Exception.IP.Offset
Value: 0xc66ca
Key : Failure.Hash
Value: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Key : Failure.ProblemClass.Primary
Value: XAML
Key : Timeline.OS.Boot.DeltaSec
Value: 860
Key : Timeline.Process.Start.DeltaSec
Value: 511
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 6.2.26100.4484

FILE_IN_CAB: CrashDump_2025.10.12_17.09.48.136.mdmp
COMMENT: Frostbite MiniDump. Address: 7ffcaeb366ca (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000000100000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006
rip=00007ffcaeb366ca rsp=000000006b2fca50 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000044 r13=000000005a076690
r14=0000000000000000 r15=00000000887a0006
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
KERNELBASE!RaiseException+0x8a:
00007ffc`aeb366ca 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcaeb366ca (KERNELBASE!RaiseException+0x000000000000008a)
ExceptionCode: 887a0006
ExceptionFlags: 00000080
NumberParameters: 0
PROCESS_NAME: bf6.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - Die GPU antwortet auf keine weiteren Befehle mehr. Dies liegt wahrscheinlich daran, dass von der aufrufenden Anwendung ein ung ltiger Befehl bergeben wurde.
EXCEPTION_CODE_STR: 887a0006
STACK_TEXT:
00000000`6b2fca50 00000001`44aae650 : 00000000`00000c54 00000000`337c6cc0 00000000`361e0820 00000000`00000018 : KERNELBASE!RaiseException+0x8a
00000000`6b2fcb50 00000000`00000c54 : 00000000`337c6cc0 00000000`361e0820 00000000`00000018 00000000`0000030a : bf6+0x4aae650
00000000`6b2fcb58 00000000`337c6cc0 : 00000000`361e0820 00000000`00000018 00000000`0000030a 00000000`887a0006 : 0xc54
00000000`6b2fcb60 00000000`361e0820 : 00000000`00000018 00000000`0000030a 00000000`887a0006 00000002`be886d90 : 0x337c6cc0
00000000`6b2fcb68 00000000`00000018 : 00000000`0000030a 00000000`887a0006 00000002`be886d90 00000000`34f9c940 : 0x361e0820
00000000`6b2fcb70 00000000`0000030a : 00000000`887a0006 00000002`be886d90 00000000`34f9c940 80000044`00000044 : 0x18
00000000`6b2fcb78 00000000`887a0006 : 00000002`be886d90 00000000`34f9c940 80000044`00000044 00000000`00ca0170 : 0x30a
00000000`6b2fcb80 00000002`be886d90 : 00000000`34f9c940 80000044`00000044 00000000`00ca0170 00000000`5a076690 : 0x887a0006
00000000`6b2fcb88 00000000`34f9c940 : 80000044`00000044 00000000`00ca0170 00000000`5a076690 00000000`00000000 : 0x00000002`be886d90
00000000`6b2fcb90 80000044`00000044 : 00000000`00ca0170 00000000`5a076690 00000000`00000000 00000000`00000000 : 0x34f9c940
00000000`6b2fcb98 00000000`00ca0170 : 00000000`5a076690 00000000`00000000 00000000`00000000 00000000`3f800000 : 0x80000044`00000044
00000000`6b2fcba0 00000000`5a076690 : 00000000`00000000 00000000`00000000 00000000`3f800000 00000000`00000000 : 0xca0170
00000000`6b2fcba8 00000000`00000000 : 00000000`00000000 00000000`3f800000 00000000`00000000 00000001`404e9070 : 0x5a076690

SYMBOL_NAME: bf6+4aae650
MODULE_NAME: bf6
IMAGE_NAME: bf6.exe
STACK_COMMAND: ~25s; .ecxr ; kb
FAILURE_BUCKET_ID: XAML_887a0006_bf6.exe!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.386.51964
FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Followup: MachineOwner
---------
25.10.25_1 online crash (one month older but still maybe helpfull?):
ntdll!NtGetContextThread+0x14:
00007fff`94ca5184 c3 ret
0:013> !analyze -v
................................................................
................................................................
................................
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify timestamp for bf6.exe
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 453
Key : Analysis.Elapsed.mSec
Value: 3576
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 1
Key : Analysis.Init.CPU.mSec
Value: 421
Key : Analysis.Init.Elapsed.mSec
Value: 6977
Key : Analysis.Memory.CommitPeak.Mb
Value: 110
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Failure.Bucket
Value: XAML_887a0006_bf6.exe!Unknown
Key : Failure.Exception.Code
Value: 0x887a0006
Key : Failure.Exception.IP.Address
Value: 0x7fff91e366ca
Key : Failure.Exception.IP.Module
Value: KERNELBASE
Key : Failure.Exception.IP.Offset
Value: 0xc66ca
Key : Failure.Hash
Value: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Key : Failure.ProblemClass.Primary
Value: XAML
Key : Timeline.OS.Boot.DeltaSec
Value: 1119
Key : Timeline.Process.Start.DeltaSec
Value: 754
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
Key : WER.Process.Version
Value: 6.2.26100.6584

FILE_IN_CAB: CrashDump_2025.10.12_14.36.18.527.mdmp
COMMENT: Frostbite MiniDump. Address: 7fff91e366ca (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000000100000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006
rip=00007fff91e366ca rsp=000000006a53ca50 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000044 r13=000000005a076690
r14=0000000000000000 r15=00000000887a0006
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
KERNELBASE!RaiseException+0x8a:
00007fff`91e366ca 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007fff91e366ca (KERNELBASE!RaiseException+0x000000000000008a)
ExceptionCode: 887a0006
ExceptionFlags: 00000080
NumberParameters: 0
PROCESS_NAME: bf6.exe
ERROR_CODE: (NTSTATUS) 0x887a0006 - Die GPU antwortet auf keine weiteren Befehle mehr. Dies liegt wahrscheinlich daran, dass von der aufrufenden Anwendung ein ung ltiger Befehl bergeben wurde.
EXCEPTION_CODE_STR: 887a0006
STACK_TEXT:
00000000`6a53ca50 00000001`44aae650 : 00000000`00000bee 00000000`347b10e0 00000000`362c0820 00000000`00000009 : KERNELBASE!RaiseException+0x8a
00000000`6a53cb50 00000000`00000bee : 00000000`347b10e0 00000000`362c0820 00000000`00000009 00000000`00000310 : bf6+0x4aae650
00000000`6a53cb58 00000000`347b10e0 : 00000000`362c0820 00000000`00000009 00000000`00000310 00000000`887a0006 : 0xbee
00000000`6a53cb60 00000000`362c0820 : 00000000`00000009 00000000`00000310 00000000`887a0006 00000002`be4ae0c0 : 0x347b10e0
00000000`6a53cb68 00000000`00000009 : 00000000`00000310 00000000`887a0006 00000002`be4ae0c0 00000000`340a8ac0 : 0x362c0820
00000000`6a53cb70 00000000`00000310 : 00000000`887a0006 00000002`be4ae0c0 00000000`340a8ac0 80000044`00000044 : 0x9
00000000`6a53cb78 00000000`887a0006 : 00000002`be4ae0c0 00000000`340a8ac0 80000044`00000044 00000000`00d90170 : 0x310
00000000`6a53cb80 00000002`be4ae0c0 : 00000000`340a8ac0 80000044`00000044 00000000`00d90170 00000000`5a076690 : 0x887a0006
00000000`6a53cb88 00000000`340a8ac0 : 80000044`00000044 00000000`00d90170 00000000`5a076690 00000000`00000000 : 0x00000002`be4ae0c0
00000000`6a53cb90 80000044`00000044 : 00000000`00d90170 00000000`5a076690 00000000`00000000 00000000`00000000 : 0x340a8ac0
00000000`6a53cb98 00000000`00d90170 : 00000000`5a076690 00000000`00000000 00000000`00000000 00000000`3f800000 : 0x80000044`00000044
00000000`6a53cba0 00000000`5a076690 : 00000000`00000000 00000000`00000000 00000000`3f800000 00000000`00000000 : 0xd90170
00000000`6a53cba8 00000000`00000000 : 00000000`00000000 00000000`3f800000 00000000`00000000 00000001`404e9070 : 0x5a076690

SYMBOL_NAME: bf6+4aae650
MODULE_NAME: bf6
IMAGE_NAME: bf6.exe
STACK_COMMAND: ~13s; .ecxr ; kb
FAILURE_BUCKET_ID: XAML_887a0006_bf6.exe!Unknown
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.386.51964
FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af}
Followup: MachineOwner
---------
- Spring466
  3 months ago
  Можешь это распечатать и повесить у себя дома на стену, потому что им плевать на эти проблемы с игрой.
X71hicks
Seasoned Newcomer
2 months ago
If the solution lies with the supplier, I think we should change the graphics card. The supplier already indicates that the GPU does not meet the minimum requirements, and historically they didn't fix it in BF 2042 either.
I've tried many solutions, even unpublished ones, and even with the weapons zoomed in, the game still crashes. If anyone with RX Vega has solved this problem, it would be great if they could post their solution; it would help many users who are experiencing the same issue. The only way I've been able to play is by using weapons with zoom levels below 2x, and then I can play without crashes. Also, the performance with the latest driver versions is very poor. If you install a 2024 version and modify the Windows registry entry to pass validation, performance improves significantly.
}
- SIDEWINDR666
  Rising Adventurer
  2 months ago
  Try enabling Hardware GPU scheduling and turning off FSR.
Rollum78
Rising Newcomer
2 months ago
I am running into the same issue consistently.
My setup:
AMD Radeon RX Vega 64 (<-- the common denominator?)
AMD Ryzen 5 2600
16GB RAM
Basically the bare minimum...
Additionally I was fighting performance problems on large maps (mostly conquest): infantry combat was like walking through honey. Rush and the other modes on smaller maps were running stable though, probably hinting at the CPU being a bottleneck.
I was able to increase performance to somewhat usable levels by doing a combination of the following:
Disable / uninstall the HD texture packs (either via Steam -> Properties -> DLC -> deselect everything with "HD Textures" in the title, or in game somewhere in the Settings -> System menu)
Tweak the PROFSAVE_profile settings (located in "%USERPROFILE%\Documents\Battlefield 6\settings\steam")
DISCLAIMER: I don't know what I am doing for the most part, use at your own risk
set "GstRender.Dx12Enabled 1" (the game only has a Dx12 renderer AFAIK, but it felt like it made a difference :3)
set "GstRender.Enlighten 0" (this one I do not even know what it does)
Turn the graphics quality down looooow

That left me with the "DXGI_ERROR_DEVICE_HUNG" crashes, which can very reliably be reproduced on my setup:
Load into a match (Operation Firestorm conquest seems to work particularly well)
Equip a sniper with > 3x scope (10x seems to work well)
Aim down sight for a bit

My crash dumps look pretty much identical to the other ones posted here. I doubt that the crash is related to FSR2 though. Addresses like "bf6!ffxFsr2ResourceIsNull+0x22ad1a0" and similar are given relative to the "ffxFsr2ResourceIsNull" symbol, but the offset "0x22ad1a0" is huge. My guess is that they just stripped all / most other symbols from the executable, so "ffxFsr2ResourceIsNull" just happens to be the best WinDbg can get.
You can also just look at the different thread callstacks in WinDbg, which for me mostly look like this:
[0x0] win32u!NtUserGetMessage+0x14 [0x1] user32!GetMessageW+0x22 [0x2] gameoverlayrenderer64!OverlayHookD3D3+0x284f7 [0x3] bf6!ffxFsr2ResourceIsNull+0x274cbfe [0x4] bf6!ffxFsr2ResourceIsNull+0x274b87c [0x5] bf6!ffxFsr2ResourceIsNull+0xc4dc3b [0x6] bf6!ffxFsr2ResourceIsNull+0xc4bf0b [0x7] bf6!ffxFsr2ResourceIsNull+0xc4dc81 [0x8] bf6!ffxFsr2ResourceIsNull+0x274d0ad [0x9] bf6!isGlimpseEnabled+0xb976 [0xa] bf6!ffxFsr2ContextGenerateReactiveMask+0xa03f02 [0xb] kernel32!BaseThreadInitThunk+0x17 [0xc] ntdll!RtlUserThreadStart+0x2c
I highly doubt that "ffxFsr2ResourceIsNull" is a crazy large function that is called recursively.
I also experimented with the settings in the "user.cfg" file (needs to be created in the same directory as "bf6.exe"), with some success at mitigating the problem at the cost of performance and audio issues.
DISCLAIMER: again I have no clue what this does and there is no official documentation, use at your own risk.
The following seemed to suppress the issue on my machine:
Thread.ProcessorCount 6 Thread.MaxProcessorCount 6 Thread.MinFreeProcessorCount 0 Thread.JobThreadPriority 0 GstRender.Thread.MaxProcessorCount 12
Most sources claim to set "Thread.ProcessorCount" and "Thread.MaxProcessorCount" to your number of physical CPU cores and "GstRender.Thread.MaxProcessorCount" to the number of logical ones.
I also played around with "Thread.MinFreeProcessorCount" which seemed to have some effect, though I did not find anything conclusive on what it actually controls. Seemed to kill my game audio when set to the wrong value though.
With above settings the performance dropped considerably on my machine and frame times were a lot more spikey, but in my short test session I was unable to reproduce the crash.