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