Re: DirextX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG

Just an update.  I've managed to stop the game crashing by disabling the XMP profile in bios. It lowers the memory frequency but I managed to play for 3 hours today without an issues.  There were a few "mini lockups" always after I started a round where the game would kind of freeze for a second and the graphics would go crazy. I assume before I disabled XMP that was the point where the game would crash but now it doesn't and each round ran smoothly from there on. If you haven't already tried to disable XMP, please try and see does it work for you.

EDIT.

Played many more hours and still no crashes. XMP was definitely the issue for me.

I've seen people recommend undervolting 6900XT's do not do this for BF2044. It doesn't like it at all. Even I tiny bump down causes the game to crash. You can reduce the max frequency down quite a lot with no performance impact.  I dropped from 2600MHz to 2300 and there's no real difference in frames. Still sitting around the 180 mark average.  The only thing the frequency reduction does is reduce heat on the gpu and the power it's drawing from the wall. Just don't undervolt the card.

give it time it'll crash again just wait and see that "HUNG GET THIS DEVICE REMOVED" is a cold mistress

It's false hope.  Disabling XMP, forcing PCIe 3.0 and dozens of other things people have tried don't completely fix the issue.  I've had it run for a good part of the day then next day it crashes right at start.  Game seems to be speed sensitive with higher end GPUs.

---

@H0telQuebec wrote:

It's false hope.  Disabling XMP, forcing PCIe 3.0 and dozens of other things people have tried don't completely fix the issue.  I've had it run for a good part of the day then next day it crashes right at start.  Game seems to be speed sensitive with higher end GPUs.

---

Well it's day 3 now, played some more today. Zero crashes. I'm sure it won't fix the problem fir everyone but it seems to have fixed the issue for me.

I lowered the target frequency on my ASRock 6900XT Formula from 2600 to 2300Mhz and I saw no impact on frame rates. The card runs a lot cooler now for the same performance.  It was pulling 328W on default settings now it's pulling 220W.

I've played 12 hours plus over 3 days and I've had no crashes to date. It's still doing that weird graphics lock up thing. I noticed it's always when I spot my first enemy in a battle. The  screen goes crazy for maybe half a second after that the game plays normally for me.

Every solution posted is a false hope. A few things may work for a few people, but most of the time it does nothing to help the problem. Disabling XMP did nothing for me either. I wish EA wasn't such a * company and fixed this problem, the game is still unplayable for me. They are doing nothing to compensate all of us who cant play the game and are missing out on weekly and monthly content. They dont give a *, they got our money so we can go * ourselves. They dont even respond in here anymore. Anyone who things EA will ever fix this will be seriously disappointed. 

what I can't understand is why this is happening to us and not others I know ppl who have the exact same PC specs as us and can play freely void of these issues 

Try the steps below if you don't mind.

1.) In windows 10/11 go to SYSTEM>DISPLAY>GRAPHICS and browse for the game file and add it to the list. Then select the application and click the options button and set the Graphics preference to HIGH PERFORMANCE which should be your video card.

2.) In windows 10/11 go to SYSTEM>DISPLAY>GRAPHICS and at the top click the link for 'Change default graphics settings', If the hardware-accelerated GPU scheduling is enabled then try disabling it. If its disabled then try and enable it and test. You need to restart your computer after making the changes.

3.) Just a shot in the dark on this one but you can trying enabling DirectPlay in the 'Windows Features' it add support for old directX code.

Right now game is crashing with this error even before it gets to the lobby. What a complete disaster. Switching to BFV where no such issues at all. RTX3090 + 12900KF + DDR5 6400.

yup....BF5 plays flawlessly with no crashes whatsoever only thing is that GD game is full of hackers 

@CameIToeInspectrSame! Since i can't play 2042 i went back to the older ones, BFV, BF1, BF4 & 3(switching between games).

It just doesn't make sense because there are people with same cpu+gpu as many others and they do not get the error.
I can't seem to figure out what it could be since for some disabling XMP seems to work and others don't.
I even formatted my pc for 2042 and I still get the error.

Imagine if the same crappy Error comes with the next Battlefield.....

I've tried with both my RTX3080Ti and RTX2080Super, the same crashes. 

I've tried underclocking/volting them from their factory overclocks as well (even though other games are 100% stable). 

I've noticed crashes at all sorts of times. 

- Loading into Lobby. 

- Zooming in a vehicles as you say. 

- If I land on the ground fast in the wingsuit, and then turn around to shoot someone

- If theres a huge firefight going on

- When the rocket explodes on Orbital often can cause my game to crash like it did just 5 minutes ago. 

Analyzing the CrashDumps with Windbg, theres also about half a dozen different error messages around Direct X or memory. 

I actually am referring to BF4 I don't play BF 2042 never have I'm having all these crashes on BF4 and BF1 

Nothing about it in the patch notes (yet)….again. Sigh

IDK guys but I installed AMD's latest driver named "AMD Software Preview Driver May 2022" and I've played for the last 3 days of 3 hrs 4hrs and 3hrs again without a single blip of course as I stated before this is for BF4 as I don't even own or ever played 2042 i hope this helps 

@Purrfect89I totally disagree. And Yes, they may have lost the majority of the playerbase and I want them to fix this issue.
Imagine the next BF-game being what it is and what the community wants and imagine You and I being yet again in the same forum, seeing each other and complaining over the same DirectX bug. I may not play 2042 due to core game mechanics, but i want them to fix this for the next BF.

@Arapaima87thats why i wrote gg next. They will eventually fix this at some point, wondering whether this BF will be still latest at that point or not. But in this state of the game and for this particular game, it does not matter anymore.

It's probably two weeks since I had this crash now. 
I don't know if it is due to something DICE did or AMD. 
It worked flawless on the two last GPU drivers (6900XT). 
I even uncapped everything, XMP on, RAM and CPU even have my preferred OC on them now.
It feels weird after dealing with these crashes for the last half-year.

IKR  I keep expecting it to crash but it just keeps rolling on fingers crossed LFG you guys 

Runs a little big longer with update 4.1.1 but still crashes.  Just crashed at start of new game.

Ive had crashes still, to this day, but for the life of me cant figure out what causes it.

Sometimes Ill get it just clicking around the menu or loadouts before even entering a game. Other times its when a game is loading.

Then it also happens randomly while in game. I get into a vehicle, or just switch weapon, or kill someone, all of these things have triggered this DirectX crash :-(

Anyone here have less than 32gb ram of system and get directx error?

So I have had this problem constantly (almost every match) since I started playing BF2042 on my Asus ROG Strix Scar 15 2021 a week or so ago.  I tried many of the suggestions out there for a fix and nothing worked.  That was until yesterday.

Here is what fixed it for me on Windows 10

Open  msconfig>services   

Hide all Microsoft Services (VERY IMPORTANT)

Disable all remaining services apart from Origin and Steam

Reboot

If I could be arsed, I’d turn them back on one by one and identify which one(s) was the culprit but I can’t be.

🙂