i just bought battlefield 6 as ive allways liked battlefield and finally got myself a pc and the time to play it but every time i try to play, my game runs perfectly fine for about 10 minutes and then it just crashes and gives me the issue stated in the title and below. its not thermal throtelling so im really stumpted on why this is happening. written bellow is all the information about the issue and all the things ive done to try and aliviate the issue. if anyone could help me so i could play that would be great! System Specs:GPU: NVIDIA GeForce RTX 3080CPU: AMDPSU: NZXT C850 (850W)OS: Windows 11Error: DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). Driver: 59597Event Viewer finding: Event ID 153, source nvlddmkm — TDR event (Windows forcibly resetting the GPU driver). Device: \Device\Video3, GPUID: 900.Other error with same sumptoms: DirectX function "Hang Detected in waitForFrameFences. Timed out after 8000 ms. Waiting for Signald: 35990. Last Signaled Fence Value: 35991. Unsignaled Fences: ('Graphics' stopped at 35989)" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: NVIDIA GeForce RTX 3080, Driver: 58142. D:\dev\InTn\Code\Packages\RenderCore2\RenderCore2\dev\source\platform\Dx12\SubmissionManagerDx12.cpp This error is usually caused by the graphics driver crashing; try installing the latest drivers.Everything attempted with no resolution:Drivers:Clean install of latest NVIDIA driversFull DDU wipe in Safe Mode followed by clean install of 581.42 (official BF6 launch driver)Tested driver 572.83 — game refused to launch, requires 581.42 minimumWindows/System settings:Disabled Hardware-Accelerated GPU Scheduling (HAGS)Disabled PCIe Link State Power Management in Power OptionsAdded TdrDelay (value 8) and TdrLevel (value 0) registry entries in GraphicsDriversVerified BF6 is running on dedicated GPU via NVIDIA Control PanelCleared DirectX shader cacheVerified XMP/EXPO — was already disabledBIOS settings checked, no overclock active on GPU or CPUclean bootNVIDIA Control Panel (BF6 profile):Power Management Mode → Prefer maximum performanceLow Latency Mode → OffVertical Sync → Use the 3D application settingOverlays and background tools disabled:GeForce Experience overlay disabledDiscord overlay disabledSteam overlay disabledEA App overlay disabledMSI Afterburner and RivaTuner fully closed from system trayIn-game settings:FSR Frame Generation disabledFramerate cap enabledGame already running in DX11 modeAssault class loadout fix attemptedUndervolted GPU via MSI Afterburner (~900-950mV)Factory overclock removed from GPUGame integrity:Verified game filesReinstalled BF6 completely, clearing all leftover folders in Program Files, Documents, and AppDataPartial resolution noted: After implementing the NVIDIA Control Panel profile changes and fully closing all overlays and monitoring tools (Afterburner/RivaTuner), the crash did not occur for 2 consecutive REDSEC sessions — the longest crash-free period achieved. However the issue has since returned, confirming the fix was incomplete.Key notes:Issue is exclusive to BF6 — no crashes in any other game or applicationCrash occurs after several minutes of gameplay, not immediately on launchHardware stress tests return no errorsPSU is sufficient for the GPUAll standard community fixes for this specific error in BF6 have been exhausted

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.

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

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

Update: I also go to windbg on dump in my crash file and this is what it shows:KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 234 Key : Analysis.Elapsed.mSec Value: 223 Key : Analysis.IO.Other.Mb Value: 12 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 48 Key : Analysis.Init.CPU.mSec Value: 1953 Key : Analysis.Init.Elapsed.mSec Value: 79524 Key : Analysis.Memory.CommitPeak.Mb Value: 102 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: 0x7ffd976579da 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: 37363 Key : Timeline.Process.Start.DeltaSec Value: 5140 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.09_20.55.44.420.mdmp COMMENT: Frostbite MiniDump. Address: 7ffd976579da (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 CONTEXT: (.ecxr) rax=333032007cb796a0 rbx=0000000000000000 rcx=00007ffd9acc0033 rdx=0000e159a884b9bc rsi=0000000000000000 rdi=00000000887a0006 rip=00007ffd976579da rsp=000000007cb7a310 rbp=0000000000000000 r8=0000000144b21a5b r9=000000007cb79608 r10=000000007cb79600 r11=000000000000000d r12=0000000000000000 r13=0000000069db55b0 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: 00007ffd`976579da 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffd976579da (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`7cb7a310 00000001`44d96d91 : 00000000`00000044 00000000`331d9f40 00000000`337e0820 00000000`7cb7a615 : KERNELBASE!RaiseException+0x8a 00000000`7cb7a410 00000000`00000044 : 00000000`331d9f40 00000000`337e0820 00000000`7cb7a615 00000000`7cb8d5b0 : bf6+0x4d96d91 00000000`7cb7a418 00000000`331d9f40 : 00000000`337e0820 00000000`7cb7a615 00000000`7cb8d5b0 00000001`00001000 : 0x44 00000000`7cb7a420 00000000`337e0820 : 00000000`7cb7a615 00000000`7cb8d5b0 00000001`00001000 00000002`4af00460 : 0x331d9f40 00000000`7cb7a428 00000000`7cb7a615 : 00000000`7cb8d5b0 00000001`00001000 00000002`4af00460 00000000`887a0006 : 0x337e0820 00000000`7cb7a430 00000000`7cb8d5b0 : 00000001`00001000 00000002`4af00460 00000000`887a0006 00000000`316f9920 : 0x7cb7a615 00000000`7cb7a438 00000001`00001000 : 00000002`4af00460 00000000`887a0006 00000000`316f9920 80000044`00000044 : 0x7cb8d5b0 00000000`7cb7a440 00000002`4af00460 : 00000000`887a0006 00000000`316f9920 80000044`00000044 00000000`277e0170 : 0x00000001`00001000 00000000`7cb7a448 00000000`887a0006 : 00000000`316f9920 80000044`00000044 00000000`277e0170 00000002`00000001 : 0x00000002`4af00460 00000000`7cb7a450 00000000`316f9920 : 80000044`00000044 00000000`277e0170 00000002`00000001 00000000`7cb7a4f8 : 0x887a0006 00000000`7cb7a458 80000044`00000044 : 00000000`277e0170 00000002`00000001 00000000`7cb7a4f8 00000000`00000000 : 0x316f9920 00000000`7cb7a460 00000000`277e0170 : 00000002`00000001 00000000`7cb7a4f8 00000000`00000000 00000001`4050f970 : 0x80000044`00000044 00000000`7cb7a468 00000002`00000001 : 00000000`7cb7a4f8 00000000`00000000 00000001`4050f970 00000000`00000000 : 0x277e0170 00000000`7cb7a470 00000000`7cb7a4f8 : 00000000`00000000 00000001`4050f970 00000000`00000000 00000000`7cb8d5b0 : 0x00000002`00000001 00000000`7cb7a478 00000000`00000000 : 00000001`4050f970 00000000`00000000 00000000`7cb8d5b0 00000000`7cb8d1b0 : 0x7cb7a4f8 IP_IN_PAGED_CODE: KERNELBASE!RaiseException+8a 00007ffd`976579da 0f1f440000 nop dword ptr [rax+rax] SYMBOL_NAME: bf6+4d96d91 MODULE_NAME: bf6 IMAGE_NAME: bf6.exe STACK_COMMAND: ~18s; .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}Interesting for me, It didn't show any fsr2 problem like in your case.Can someone help me explain where is problem in my case?

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.

Forum Discussion

lul520

Seasoned Novice

1 month ago

DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG

i just bought battlefield 6 as ive allways liked battlefield and finally got myself a pc and the time to play it but every time i try to play, my game runs perfectly fine for about 10 minutes and then it just crashes and gives me the issue stated in the title and below. its not thermal throtelling so im really stumpted on why this is happening. written bellow is all the information about the issue and all the things ive done to try and aliviate the issue. if anyone could help me so i could play that would be great!

System Specs:

GPU: NVIDIA GeForce RTX 3080
CPU: AMD
PSU: NZXT C850 (850W)
OS: Windows 11

Error: DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). Driver: 59597

Event Viewer finding: Event ID 153, source nvlddmkm — TDR event (Windows forcibly resetting the GPU driver). Device: \Device\Video3, GPUID: 900.

Other error with same sumptoms: DirectX function "Hang Detected in waitForFrameFences. Timed out after 8000 ms. Waiting for Signald: 35990. Last Signaled Fence Value: 35991. Unsignaled Fences: ('Graphics' stopped at 35989)" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: NVIDIA GeForce RTX 3080, Driver: 58142. D:\dev\InTn\Code\Packages\RenderCore2\RenderCore2\dev\source\platform\Dx12\SubmissionManagerDx12.cpp This error is usually caused by the graphics driver crashing; try installing the latest drivers.

Everything attempted with no resolution:

Drivers:

Clean install of latest NVIDIA drivers
Full DDU wipe in Safe Mode followed by clean install of 581.42 (official BF6 launch driver)
Tested driver 572.83 — game refused to launch, requires 581.42 minimum

Windows/System settings:

Disabled Hardware-Accelerated GPU Scheduling (HAGS)
Disabled PCIe Link State Power Management in Power Options
Added TdrDelay (value 8) and TdrLevel (value 0) registry entries in GraphicsDrivers
Verified BF6 is running on dedicated GPU via NVIDIA Control Panel
Cleared DirectX shader cache
Verified XMP/EXPO — was already disabled
BIOS settings checked, no overclock active on GPU or CPU
clean boot

NVIDIA Control Panel (BF6 profile):

Power Management Mode → Prefer maximum performance
Low Latency Mode → Off
Vertical Sync → Use the 3D application setting

Overlays and background tools disabled:

GeForce Experience overlay disabled
Discord overlay disabled
Steam overlay disabled
EA App overlay disabled
MSI Afterburner and RivaTuner fully closed from system tray

In-game settings:

FSR Frame Generation disabled
Framerate cap enabled
Game already running in DX11 mode
Assault class loadout fix attempted
Undervolted GPU via MSI Afterburner (~900-950mV)
Factory overclock removed from GPU

Game integrity:

Verified game files
Reinstalled BF6 completely, clearing all leftover folders in Program Files, Documents, and AppData

Partial resolution noted: After implementing the NVIDIA Control Panel profile changes and fully closing all overlays and monitoring tools (Afterburner/RivaTuner), the crash did not occur for 2 consecutive REDSEC sessions — the longest crash-free period achieved. However the issue has since returned, confirming the fix was incomplete.

Key notes:

Issue is exclusive to BF6 — no crashes in any other game or application
Crash occurs after several minutes of gameplay, not immediately on launch
Hardware stress tests return no errors
PSU is sufficient for the GPU
All standard community fixes for this specific error in BF6 have been exhausted

crashing

steam

12 Replies

nothlaj
Seasoned Newcomer
19 days ago
Update: I also go to windbg on dump in my crash file and this is what it shows:
KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 234 Key : Analysis.Elapsed.mSec Value: 223 Key : Analysis.IO.Other.Mb Value: 12 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 48 Key : Analysis.Init.CPU.mSec Value: 1953 Key : Analysis.Init.Elapsed.mSec Value: 79524 Key : Analysis.Memory.CommitPeak.Mb Value: 102 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: 0x7ffd976579da 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: 37363 Key : Timeline.Process.Start.DeltaSec Value: 5140 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.09_20.55.44.420.mdmp COMMENT: Frostbite MiniDump. Address: 7ffd976579da (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 CONTEXT: (.ecxr) rax=333032007cb796a0 rbx=0000000000000000 rcx=00007ffd9acc0033 rdx=0000e159a884b9bc rsi=0000000000000000 rdi=00000000887a0006 rip=00007ffd976579da rsp=000000007cb7a310 rbp=0000000000000000 r8=0000000144b21a5b r9=000000007cb79608 r10=000000007cb79600 r11=000000000000000d r12=0000000000000000 r13=0000000069db55b0 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: 00007ffd`976579da 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffd976579da (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`7cb7a310 00000001`44d96d91 : 00000000`00000044 00000000`331d9f40 00000000`337e0820 00000000`7cb7a615 : KERNELBASE!RaiseException+0x8a 00000000`7cb7a410 00000000`00000044 : 00000000`331d9f40 00000000`337e0820 00000000`7cb7a615 00000000`7cb8d5b0 : bf6+0x4d96d91 00000000`7cb7a418 00000000`331d9f40 : 00000000`337e0820 00000000`7cb7a615 00000000`7cb8d5b0 00000001`00001000 : 0x44 00000000`7cb7a420 00000000`337e0820 : 00000000`7cb7a615 00000000`7cb8d5b0 00000001`00001000 00000002`4af00460 : 0x331d9f40 00000000`7cb7a428 00000000`7cb7a615 : 00000000`7cb8d5b0 00000001`00001000 00000002`4af00460 00000000`887a0006 : 0x337e0820 00000000`7cb7a430 00000000`7cb8d5b0 : 00000001`00001000 00000002`4af00460 00000000`887a0006 00000000`316f9920 : 0x7cb7a615 00000000`7cb7a438 00000001`00001000 : 00000002`4af00460 00000000`887a0006 00000000`316f9920 80000044`00000044 : 0x7cb8d5b0 00000000`7cb7a440 00000002`4af00460 : 00000000`887a0006 00000000`316f9920 80000044`00000044 00000000`277e0170 : 0x00000001`00001000 00000000`7cb7a448 00000000`887a0006 : 00000000`316f9920 80000044`00000044 00000000`277e0170 00000002`00000001 : 0x00000002`4af00460 00000000`7cb7a450 00000000`316f9920 : 80000044`00000044 00000000`277e0170 00000002`00000001 00000000`7cb7a4f8 : 0x887a0006 00000000`7cb7a458 80000044`00000044 : 00000000`277e0170 00000002`00000001 00000000`7cb7a4f8 00000000`00000000 : 0x316f9920 00000000`7cb7a460 00000000`277e0170 : 00000002`00000001 00000000`7cb7a4f8 00000000`00000000 00000001`4050f970 : 0x80000044`00000044 00000000`7cb7a468 00000002`00000001 : 00000000`7cb7a4f8 00000000`00000000 00000001`4050f970 00000000`00000000 : 0x277e0170 00000000`7cb7a470 00000000`7cb7a4f8 : 00000000`00000000 00000001`4050f970 00000000`00000000 00000000`7cb8d5b0 : 0x00000002`00000001 00000000`7cb7a478 00000000`00000000 : 00000001`4050f970 00000000`00000000 00000000`7cb8d5b0 00000000`7cb8d1b0 : 0x7cb7a4f8 IP_IN_PAGED_CODE: KERNELBASE!RaiseException+8a 00007ffd`976579da 0f1f440000 nop dword ptr [rax+rax] SYMBOL_NAME: bf6+4d96d91 MODULE_NAME: bf6 IMAGE_NAME: bf6.exe STACK_COMMAND: ~18s; .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}
Interesting for me, It didn't show any fsr2 problem like in your case.
Can someone help me explain where is problem in my case?
7322eb498828d5c8
New Rookie
18 days ago
Without the internal symbols from DICE, we can't really see what is happening on your stack there. Interestingly, your error is 0x887a0006, which is the hex code for DXGI_ERROR_INVALID_CALL, not DEVICE_REMOVED or DEVICE_HUNG. So this is likely a different error entirely. INVALID_CALL is thrown when a process is sending malformed or illegal instructions to the Dx12 API.

Perhaps this is caused by a corrupt shader cache? That's where I would start at least. Delete all shader caches (game cache, DX cache and AMD/Nvidia caches). Try using the Disk Cleanup utility to delete the Dx cache, as that can somethimes be locked for deletion by different programs not allowing you to do it manually.