Re: DirextX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG

Hello, I had the same error with my 6900XT after 1-2 seconds loading into any map. The grafics card was recently underclocked, which worked well in other titles, but not in BF2042. So after trying other options, I have set my performance options in the Radeon software back to stock and it worked, no errors since then. After that I tried to undervolt a little, but it causes the error to pop up again.

I have been playing for weeks without any problems.

My 3080 Xtreme has double BIOS. The silent mode had been working for a while without any issues.

I set it back to factory OC and had the same error again. It seems as soon as that GPU hits 100% GPU load that happens...

Windows 10 latest version

GTX 1070Ti (497.29) 7700K @ 4.7GHz, 32GB DDR4 @ 2400MHz

Crashed right after loading into a match and opening the map.

Your game's highly unstable and that aspect hasn't improved since release. Most of these issues are engine related and date back to older Frostbite engine titles. Not just Battlefield.

The Holiday's are over! Back to work and start patching your broken game! Stop blaming GPU drivers and are our builds for your continued incompetence!

Does EA or Dice have any intention on fixing this issue. This is a downright embarrassment and from a QA perspective it doesn't sound like the game was well tested on a variety of configurations. I have a brand new 5900x/6900xt machine and these DX issues continue to plague what would otherwise be a fun game.

I will never buy another BF title or EA if I can avoid it unless the quality bar goes up. What a joke!

Ive had the same issue after undervolting. I just increades my undervolt settings a little bit (from 850 to 875 mV) and now it works fine. Maybe you can try that aswell.

Thank you, had the same issues after 3-5 minutes in game, so tried your solution. I created a custom Efficency profile for BF2042 and changed Max. Frequency (%) to 75% and Voltage to 90%, the rest of Settings set to stock Settings, see the screenshot attached. Worked for me, played 4 games without crashes.

@7empePLReflex is the next thing that I planned to look at if the error comes again. For now, just turning off RTSS seems to help. I'll turn off reflex just to be sure also and report back if error pop.

@EvanderMegatonoooh nice thanks for advice guys! Also, gpu OCs possibly contributing factor? Something from the past tells me EA doesn't particularly like OC hardware especially cards, but in the last few days I found that also an undervolted cpu will crash games (and the launcher) occasionally. Sucks really but I hope I can continue to OC my 3080 at least according to other suites / games that won't crash and then maybe if I follow your steps (turning off reflex and rtss) the game won't crash even with the OCs? Relatively stable in bf2042 is +50 on the gpu core (with rtss, at least as long as I don't fiddle with it too much while i play) but I can push as much as +110 in Kombustor so hmm. Gonna keep trying things I guess.

Oh yeah, also I don't get why DLSS is so bad in this game, this gpu can pull well over 410w yet when I play with DLSS it's hardly ever 300, and my frames only improve a little bit?

One last thing, and probably my worst issue in the last week or so, is the fact I lost about 25fps overall? Since start of December my frames have been improving on almost weekly basis but I don't know what happened but I am getting way worse performance in game. I am now getting less fps with ultra performance dlss than I did with it off before..

Anyways, I don't know what's happening anymore but it sucks. Like even the last chance I give this game and I can barely play it cause it's becoming increasingly unplayable. I do enjoy it though. Just wish they didn't make it worse, seems kinda counter intuitive

BF2042 is definitely in a bad state right now. Not complete, not optimized, not tested... it's a beta test pretty much at this point. I played whole Halo Infinite, about 30-40 hours on ULTRA, no crashes, not once! Same card, same hardware. Others games, too. Well, let's hope DICE will get to work soon.

UPDATE 07 JAN 22.  I USE THE NVIDIA DRIVER TO CAP 60 FPS (NOT VSYNC. in manager 3d settings, max frame rate limit).   NO problem since then.  Cap with rivatuner, no problem. More than 30 maps. 

----  old ---- v

@EvanderMegatonthis happens using or not Rivatuner or Reflex. I didn't use both and I got errors.
In the beginning, I used both and had no errors.
It started after patch 3.1.

Afterwards I disabled Reflex, but I had error.
And finally, I stopped using Rivatuner.

But many here have not used it and also had errors.

Sometimes it gets to be unpredictable / random.

This Directx error happens  when i use the MAP  of the game.  Random! but just when i open the map!

--- old ---^

Hello just a quick question.

Has the problem been fixed in the meantime or was there an official announcement about it?

Thanks!

Sadly neither

Been struggling with this error since launch. I have nothing new to provide to this topic except that this and similar errors is most likely a BF 2042 software problem.

It's a time-consuming pain to track down faulty hardware when the computer acts up badly as with this game where the game crashes to desktop or even hangs the GPU. When the computer actually could be just fine on an hardware level.
Wish the developers with the proper tools could give us more insight so that we don´t waste so much time to track these errors down, or to find work arounds like the underclock of the cpu/gpu.

It could also be expensive and very stressful if someone turns up with this problem and is not tech savvy or know how to find correct info on the issues. ☹️

I caped my FPS at 100fps in nVidia settings, turned off any overlays, reflex... no crash for a few days now, even with new Nvidia drivers 511.17 from yesterday. RTX3080, 12700K, DDR4. But we can all agree at this point that this is a very luck-based, software problem.