DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG

Hey guys, 

Dont re-install Windows - thats gonna be a **bleep** mare!!!! If your PC is already stable with all other games with no issues - its down to BF6. I cant speak for AMD as I am a NVIDIA guy. I had weeks with no crashes and then days when it crashed pretty much on every game on Breakthrough that Istarted. Like 20 times a day. Getting corrupt profiles and everything. 

Like others have said. Dont overclock your CPU. Standard XMP memory profiles should be OK. The whole idea of XMP memory is to run sync'd with the CPU - so that shouldnt matter. 

I installed the latest Nvidia driver last week - 596.21-desktop-win10-win11-64bit-international-dch-whql. It started crashing again. I went back to - 581.42-desktop-win10-win11-64bit-international-dch-whql

Look somehow BF6 is very sensitive with graphics and PSU's. I dont understand why - but...

THIS FIXED IT FOR ME on a Nvidia RTX4090 - in BF6 drop the FPS frames from 249 to 100. Test it... leave it for a week. Maybe up it to 120... leave for a week and so on. You may find its stable at 100 FPS or 150FPS????

I changed my BF6 Graphics to performance and lower the spec a little. I kept textures high but lowered others. I basically followed this guide ( https://www.youtube.com/watch?v=8Qo9kPt9YoU&t=523s )

I made sure the following was set in GRAPHICS > ADVANCED SETTINGS:

Fixed Resolution Scale 100 

Frame Rate limiter In Game ON

Frame Rate Limit in Game 240  ##### - I DROPPED IT to 100 and stayed on that. So far All OK!

Frame Rate Limiter - In Menu ON

Frame Rate Limit - In Menu 60

Frame Rate Limiter - in Background OFF

NVIDIA Reflex Low Latency ENABLED + BOOST

Upscaling Technique DLSS

Upscaling Quality QUALITY

DLSS Model 4.0

NVIDIA Frame Generation OFF

Future Frame Rendering OFF

Performance Overlay OFF

and yeah so far its OK. I cant say this will work for others. Nothing worse that having a game crash on you - so I hope this helps somebody. Its been a week so far and I play everyday and so far it seems stable.

Good Luck Guys.

So right now, there is a very large thread on this forum related to the DXGI crashes happening with Frostbite. 

It's really difficult to debug for regular users as it happens randomly, and most commonly in REDSEC (at least for me) meaning I am risking ruining the games of my friends by constantly joining and crashing every game. Without even so much as a rejoin button playing with me becomes more of a burden than anything else. 

This issue got a lot worse after Season 2 started and despite the huge amount of feedback from the community on this issue, there appears to be very little response from EA, DICE, Nvidia and AMD on the issue. 

At the very least an acknowledgement about the issue and some general pointers as to what is more likely to cause it allowing users to take some mitigating steps would be enormously helpful, but instead we get radio silence. 

DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG | EA Forums - 12737991

There is the thread in question. 

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`7fbfa310 00000001`44d96671     : 00000000`00000044 00000000`3229b180 00000000`326d0820 00000000`7fbfa615 : KERNELBASE!RaiseException+0x8a
00000000`7fbfa410 00000001`44d96d04     : 00000000`6cc355b0 00000000`06f3e9f8 00004990`1d66e54b 00000001`4531c765 : bf6!ffxFsr2ResourceIsNull+0x22c5431
00000000`7fc0f610 00000001`44d954e3     : 00000000`6cc355b0 460f5dcf`36555f00 00000000`7bf1d2f0 c3c3bfa7`1bb45900 : bf6!ffxFsr2ResourceIsNull+0x22c5ac4
00000000`7fc0f660 00000001`44c3dba6     : 00010001`40000020 3a6a99de`20ce91f2 00000000`6cc32cf0 00000000`06f3e9f8 : bf6!ffxFsr2ResourceIsNull+0x22c42a3
00000000`7fc0f770 00000001`44c3aeb8     : 00000000`6cc32cf0 00000000`6cc32cf0 00000000`06f3e9f8 00000000`6cc32cf0 : bf6!ffxFsr2ResourceIsNull+0x216c966
00000000`7fc0f920 00000001`43c06821     : 00000000`7fc0fa00 00000001`dfd33900 00000000`00000000 00000001`dfd339bc : bf6!ffxFsr2ResourceIsNull+0x2169c78
00000000`7fc0f9c0 00000001`43c0e091     : 00000001`49f77a98 00000001`43c0cbc1 00000000`00000000 00000000`7fc0fbe0 : bf6!ffxFsr2ResourceIsNull+0x11355e1
00000000`7fc0fab0 00000001`43c0d700     : 499062a6`11ab0000 00000000`7fc0fd80 00000001`49d1ed80 ffffffff`ffffffff : bf6!ffxFsr2ResourceIsNull+0x113ce51
00000000`7fc0fb30 00000001`43c0d269     : 00000000`4c6e5c44 00000000`00c60100 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113c4c0
00000000`7fc0fc50 00000001`43c0b863     : 00000000`00040000 00000000`00001000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113c029
00000000`7fc0fcb0 00000001`43c0ac57     : 00000000`00000000 00000000`7fc0ff00 00000000`32751800 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x113a623
00000000`7fc0fe20 00000001`436fc4ab     : 00000000`00000000 00000000`00000000 00000001`49d052d0 00007fff`be75a9ab : bf6!ffxFsr2ResourceIsNull+0x1139a17
00000000`7fc0fe70 00000001`436fe274     : 00000000`32751800 00000000`327517c0 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc2b26b
00000000`7fc0fec0 00000001`4330d68c     : 00000001`49a0c800 00000000`00000000 ffffffff`00000103 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0xc2d034
00000000`7fc0ff00 00007fff`bf7e37b0     : 00000000`4c5c98b0 00000000`00000000 00000000`00000000 00000000`00000000 : bf6!ffxFsr2ResourceIsNull+0x83c44c
00000000`7fc0ff30 00007fff`c11ee8d7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x30
00000000`7fc0ff60 00007fff`c1e2c3fc     : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`7fc0ff90 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c

Clearly there is one or more FSR calls happening despite FSR being disabled. This is not reflected in the DXGI error dialog for me by the way, only when analyzing the dump file. 

This issue seems to be with BF6, the AMD drivers (in my case) or both in that FSR seems to be asked to handle one or more resources that don't exist. Given that Nvidia users also have reported crashes in the thread linked above, I am inclined to believe this is a bug in Frostbite (assuming their dump has a similar stack trace)

The question is what causes these null pointers? That's where we are in the dark, and perhaps the devs could provide some insight. Is there any way to completely force the FSR2 pipeline not to be involved in the rendering at all? Could it be resources the rendering pipeline needs are unavailable due to external tools like overlays, hooks, Javelin etc?

Just... any feedback. Anything at all. An acknowledgement of the issue. Heck, I'd settle for a "Calm down, love."

6 Months later and this is still happening. Send my Crashdumps directly to a DICE Dev. Told everybody I could about this. No fix what so ever. We just started to play the game together again after months and my gf's rig is STILL crashing only in BF6 with an RX 9060 XT. They fixed nothing and there is no actual response or fix for this.

I spoke too soon. Crashed again, this time in multiplayer. EA really needs to get on top of this. It's getting ridiculous. 

To anyone who is facing this issue on 'obscure' GPUs/CPUs. If by some miracle you are able to change your hardware that is the only fix I have found. Switching from Intel Core Ultra 7 265KF with a Titan V to the same CPU but instead paired with an Arc B580 was the only solution.
I have no idea why this kind of problem occurs, nor do I know why the Arc B580 fixed it. My only guess is that in my case the Titan V was just "too old" (There are people I know using 1080Tis and Radeon RX 580s that DON'T have this problem, so it really is a mystery).

Do not use this game to justify buying new hardware, It is not and never will be worth it; the Titan V outperforms the B580 by a significant margin, and planned obsolescence through drivers SHOULD be criminalized.

Probably BF6. The lastest Adrenalin driver was released on March 19, and I had regular crashes in REDSEC. 

Right now I've played several rounds of multiplayer without crashing, so I am curious about what happens when I play REDSEC again. 

Well I have the 9060xt 16gb and since the latest amd graphics driver update and bf6 update I’ve had 0 crashes so something has helped but don’t know if it’s EA or AMD as they both updated at the same time 🤷‍♂️

I literally can't believe that AMD users are still having DIGI crash issues. I bought a 9060xt 16gb in September and since release kept crashing. Switched to NVIDIA 5060ti 16gb running native, no DLSS or whatever and not a single DIGI crash in 4 months. 

AMD is trashhhhhhhhhhhhhhhh. CPU and GPU. 

No wonder this thread was marked as solved from day 1. It's probably got something to do deep within the development code. Probably can't be fixed easily and not worth doing. 

For anyone saying I am on NVIDIA and still having crash, your in the minority this thread is like 95% AMD. Try a clean windows install and fresh game install.

Never ever going to buy AMD again. Should change the company name to AMT, T for trash. 

Funny thing is that in single player story i have 0 issues. Its crashing only in MP :( 

Well you can have this problem with every Game that uses the Frostbite Engine. It happend in every single one of them... never to that extent but never 0. There is no Solution and it will never be. If you are one of those who have the Problem try to get youre money back. There is nothing else you can do than just look for other games to enjoy