DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG

Update on my case:

Following the advice from EA support, I managed to achieve stability by disabling the NVIDIA High Definition Audio driver in Device Manager. This completely resolved the DXGI_ERROR_DEVICE_HUNG crashes and I was able to play without issues for approximately 2 months.

However, the crashes have now returned without any changes on my end — no Windows updates, no driver updates, no new software installed. The issue has also changed in nature: the error has shifted from DXGI_ERROR_DEVICE_HUNG to DXGI_ERROR_DEVICE_REMOVED, with the following expanded error message:

"DirectX function 'm_submitFencePlat->GetCompletedValue()' failed with DXGI_ERROR_DEVICE_REMOVED. The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. GPU: NVIDIA GeForce RTX 3080, Driver: 59636. D:\dev\InTn\Code\Packages\RenderCore2\RenderCore2\dev\source\platform\Dx12\SubmissionManagerDx12.cpp"

The fact that the error type has changed and that the previously working fix is no longer effective strongly suggests that a recent BF6 update changed something in the RenderCore2 rendering pipeline, inadvertently breaking the workaround without fixing the underlying issue.

I have verified the following to rule out hardware or system causes:

- GPU benchmarks (FurMark, Superposition) run without any crashes or errors

- GPU temperatures are within normal range under load

- NVIDIA audio driver is still disabled

- No new software, drivers or Windows updates installed around the time crashes returned

- Issue remains exclusive to Battlefield 6

The SubmissionManagerDx12.cpp reference in the error points directly to RenderCore2's DX12 fence submission logic, which is EA/DICE code. This is not a hardware issue. I am requesting that this be escalated to the development team for investigation, as this appears to be an engine-level compatibility issue with RTX 3080 configurations that has not been properly resolved.

Hi, sorry to hear the issue has returned, and thank you for all the effort you’ve already put into troubleshooting.

Have you tried doing a clean reinstall of your NVIDIA driver using DDU? Although you mentioned there hadn’t been any driver updates, 596.36 seems to be a very recent release. If the crashing started after updating to 596.36, it may also be worth rolling back to the previous driver version.

You could also try clearing the shader cache to see whether that helps:

• Delete C:\Users\USERNAME\AppData\Local\NVIDIA\DXCache and GLCache folders
• Delete C:\Users\USERNAME\AppData\Local\Battlefield 6\cache
• Clear DirectX Shader Cache via Windows Disk Cleanup
• Delete C:\Users\USERNAME\Documents\Battlefield 6 folder

Then verify the game files.

Hey, perhaps the crash dumps have some clues. You can inspect them with WinDbg (available at the Windows Store). 

Open the crash dump with File -> Open Dump file and then navigate to Documents/Battlefield 6/CrashDumps

Once you open a crash dump, you will need to select symbols with which to make sense of it. We don't have DICE/EA's internal symbols, so just pick the standard microsoft ones. 

In the command line of WinDbg after you open the dump-file, type:

.sympath srv*https://msdl.microsoft.com/download/symbols

Then reload the dump with 

.reload

Then you can run the analysis with 

!analyze -v

It takes a few seconds, but you should get a more detailed report on what went wrong. 

What would be interesting to find out is what the execution stack looks like when it crashes. For my RX 9070 XT, there are a bunch of FSR-calls resulting in null pointers just at the time of crashing, regardless of whether or not I disable FSR (either in the menu or via launch options). 

EA_LunardustCat​ Do you guys have any plans to communicate outwards what the DXGI issues might be? There's a lot of radio silence right now. Looking at the huge thread regarding the DXGI crashes for example. 

https://forums.ea.com/discussions/battlefield-6-technical-issues-en/dxgi-error-device-removed-or-dxgi-error-device-hung/12737991?topicRepliesSort=postTimeDesc

Thanks for offering help to others.

We have been following that megathread while continuing to gather reports and pass information along. If we have not shared anything new, it is because we have not been given a verified update to responsibly pass on to players. The reality is that sometimes the communication around a topic is not a full standalone update, and it may end up being reflected in something as brief as a patch note line like "improved stability".

Hi! Thank you so much for your reply. I tried both the ddu and clearing the shaders without any luck. I updated my drivers after the issue reapeared in hopes it would fix it. In a couple hours when i get home i will post the crash dumps i get

And again, thank you so much for the help!

Hi. I got the same error. Same drivers just a 5080 RTX . Before 596.36 driver update I did not have any crashes . Also getting crashes in other games like World of Tanks. 

I reinstalled the drivers with the DDU app also did that to the intel iGPU drivers as I got a Intel core ultra 285k CPU . Removed shader cache also reinstalled direct X and checked the file integretiy in steam for BF6. Nothing worked.

Update — Crash dump analysis points to FSR2 as root cause

Following advice from another user I analyzed my crash dump using WinDbg. The results are very revealing and I think this will be useful for anyone else experiencing this issue.

The entire call stack traces back to bf6!ffxFsr2ResourceIsNull, meaning the crash is originating directly inside BF6's FSR2 (FidelityFX Super Resolution 2) implementation. This is significant because FSR2 upscaling and FSR Frame Generation are two separate features — disabling Frame Generation alone does not address this.

important details:

- Exception Code: 0x887a0006 (DXGI_ERROR_DEVICE_HUNG)

- Faulting module: bf6.exe

- Crash originates in: bf6!ffxFsr2ResourceIsNull throughout the entire call stack

- Error raised via: KERNELBASE!RaiseException

- Failure Bucket: XAML_887a0006_bf6.exe

full details: KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 609 Key : Analysis.Elapsed.mSec Value: 13840 Key : Analysis.IO.Other.Mb Value: 16 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 45 Key : Analysis.Init.CPU.mSec Value: 515 Key : Analysis.Init.Elapsed.mSec Value: 86408 Key : Analysis.Memory.CommitPeak.Mb Value: 278 Key : Analysis.Version.DbgEng Value: 10.0.29547.1002 Key : Analysis.Version.Description Value: 10.2602.27.2 amd64fre Key : Analysis.Version.Ext Value: 1.2602.27.2 Key : Failure.Bucket Value: XAML_887a0006_bf6.exe!Unknown Key : Failure.Exception.Code Value: 0x887a0006 Key : Failure.Exception.IP.Address Value: 0x7ffb8ba379da Key : Failure.Exception.IP.Module Value: KERNELBASE Key : Failure.Exception.IP.Offset Value: 0xc79da Key : Failure.Hash Value: {823c07cc-a67a-e92f-3480-f4d74ce569af} Key : Failure.ProblemClass.Primary Value: XAML Key : Faulting.IP.Type Value: Paged Key : Timeline.OS.Boot.DeltaSec Value: 511788 Key : Timeline.Process.Start.DeltaSec Value: 276 Key : WER.OS.Branch Value: ge_release Key : WER.OS.Version Value: 10.0.26100.1 Key : WER.Process.Version Value: 1.0.421.43257 FILE_IN_CAB: CrashDump_2026.05.06_18.54.48.238.mdmp COMMENT: Frostbite MiniDump. Address: 7ffb8ba379da (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 CONTEXT: (.ecxr) rax=0000000000000000 rbx=0000000000000000 rcx=00007ffb8b823780 rdx=0000000000000000 rsi=0000000000000000 rdi=00000000887a0006 rip=00007ffb8ba379da rsp=000000007fb7a310 rbp=0000000000000000 r8=0000000000000000 r9=00000010f0a8b830 r10=00000000000074b0 r11=00000000000064f8 r12=0000000000000000 r13=000000006cab55b0 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=00000202 KERNELBASE!RaiseException+0x8a: 00007ffb`8ba379da 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffb8ba379da (KERNELBASE!RaiseException+0x000000000000008a) ExceptionCode: 887a0006 ExceptionFlags: 00000080 NumberParameters: 0 PROCESS_NAME: bf6.exe ERROR_CODE: (NTSTATUS) 0x887a0006 - The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. EXCEPTION_CODE_STR: 887a0006 STACK_TEXT: 00000000`7fb7a310 00000001`44d96d91 : 00000000`00000044 00000000`2f4c9ec0 00000000`32630820 00000000`7fb7a5d9 : KERNELBASE!RaiseException+0x8a 00000000`7fb7a410 00000001`44d97424 : 00000000`6cab55b0 00000000`073ba558 0000a058`d6ebd0c1 00000001`4531ce85 : bf6!ffxFsr2ResourceIsNull+0x22c5431 00000000`7fb8f610 00000001`44d95c03 : 00000000`6cab55b0 00000002`ce98cd80 00000000`3eaaaaab 00000001`40b8c045 : bf6!ffxFsr2ResourceIsNull+0x22c5ac4 00000000`7fb8f660 00000001`44c3e2c6 : 00000000`a1509500 00000000`a1509900 00000000`6cab2cf0 00000000`073ba558 : bf6!ffxFsr2ResourceIsNull+0x22c42a3 00000000`7fb8f770 00000001`44c3b5d8 : 00000000`6cab2cf0 00000000`6cab2cf0 00000000`073ba558 00000000`6cab2cf0 : bf6!ffxFsr2ResourceIsNull+0x216c966 00000000`7fb8f920 00000001`43c06f41 : 00000000`46f0a5bc 00000002`361df080 00000000`00000000 00000002`361df13c : bf6!ffxFsr2ResourceIsNull+0x2169c78 00000000`7fb8f9c0 00000001`43c0e7b1 : 00000001`49f77aa8 00000001`43c0d2e1 00000000`00000000 00000000`7fb8fbe0 : bf6!ffxFsr2ResourceIsNull+0x11355e1 00000000`7fb8fab0 00000001`43c0de20 : a058a953`24210000 00000000`7fb8fd80 00000001`49d1eee8 ffffffff`ffffffff : bf6!ffxFsr2ResourceIsNull+0x113ce51 00000000`7fb8fb30 00000001`43c0d989 : 00000000`4c5215c4 00000000`00b60100 00000000`00000001 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113c4c0 00000000`7fb8fc50 00000001`43c0bf83 : 00000000`00040000 00000000`00001000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113c029 00000000`7fb8fcb0 00000001`43c0b377 : 00000000`00000000 00000000`7fb8ff00 00000000`326b1800 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113a623 00000000`7fb8fe20 00000001`436fcb5b : 00000000`00000000 00000000`00000000 00000001`49d05270 00007ffb`8ba2a9ab : bf6!ffxFsr2ResourceIsNull+0x1139a17 00000000`7fb8fe70 00000001`436fe924 : 00000000`326b1800 00000000`326b17c0 00000000`00000001 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc2b1fb 00000000`7fb8fec0 00000001`4330ddac : 00000001`49a0c900 00000000`00000001 ffffffff`00000103 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc2cfc4 00000000`7fb8ff00 00007ffb`8b8237b0 : 00000000`025db910 00000000`00000000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x83c44c 00000000`7fb8ff30 00007ffb`8db5e8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30 00000000`7fb8ff60 00007ffb`8ee6c3fc : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17 00000000`7fb8ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c IP_IN_PAGED_CODE: KERNELBASE!RaiseException+8a 00007ffb`8ba379da 0f1f440000 nop dword ptr [rax+rax] SYMBOL_NAME: bf6+4d96d91 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.421.43257 FAILURE_ID_HASH: {823c07cc-a67a-e92f-3480-f4d74ce569af} Followup: MachineOwner

This also explains why disabling my NVIDIA High Definition Audio driver fixed the issue for approximately 2 months — it changed how the driver stack initialized, coincidentally reducing the memory pressure that was triggering the FSR2 bug. The audio driver was never the actual cause. FSR2 was the root cause all along.

I am currently testing with FSR2 upscaling switched off entirely and DLSS enabled instead (RTX 3080). Will report back with results.

I am requesting that DICE/EA investigate the FSR2 implementation specifically for compatibility issues with NVIDIA hardware configurations. The crash dump evidence points directly at ffxFsr2 code and this should be reproducible and actionable for the development team.

— lul520

Hei, I noticed in the patch changes for 1.3.1.0 that there weren't explicit mentions of crash fixes apart from something under Portal. I did however see support added for FSR 4.1. Does this imply changes to the rendering pipeline that may address the FSR2 crash issue we're seeing?