DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG

Try enabling Hardware GPU scheduling and turning off FSR.

This won't really resolve the issue, you will still have timeouts and the DXGI card removed error will still happen, it just extends the time the system takes to detect the issue.

I tried these settings when I was having the issue, I am back to defaults now.

Try turning XMP back on, faster RAM speeds are always better ;)

Some DXGI issues appear to be related with the upscaling/FSR functions.

The TDR reg values do not resolve the issue they just basically kick the can down the road.  When I was having the DXGI errors I tried the TDR reg settings and they improved thing marginally but it did not resolve the crashes.  I am now running the default TDR values.

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:

1. Load into a match (Operation Firestorm conquest seems to work particularly well)
2. Equip a sniper with > 3x scope (10x seems to work well)
3. 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.

So far everything is fine, no crashes yet.

4 days for me without a crash.... I'm starting to believe 🤘

Unfortunately no, you can't be sure you won't be getting the error. We're discussing the fixes but they are various right now for everyone... 

Yea... 

It's averages at around 70.000 players everyday according to steam, plus the console players. They already profited from all the game sales, so the only incentive to keep players in the game was to turn it into a COD/Fortnite/CS money machine by selling skins and other stuff. But they are probably realizing that BF players are not that type of audience. 

At this point it just seems like the developers are lost on what to do with the game... hence why season 2 just got delayed.

Anyway, every creator i come across always ask for "more content" to keep players online, but i remember putting 1000+ hours into bf3 basically playing metro, caspian, firestorm and TDM noshahr canals... no new guns or skins every week, the game was just fun to play... maybe bf6 is lacking the "funniness" of it. Like, is something like the video below even possible in BF6? Is there even a community for the players? Every game is a new lobby, no server search, people just don't build connections...

https://www.youtube.com/watch?v=uJJzoF3GSYI

ANYWAY, sorry for the rant. HAS THIS P.O.F.S DIRECTX ERROR BEEN FIXED? CAN I REBUY THE GAME? I'm sure i won't be getting another refund, so i need to be sure before i spend my money again