Re: Game crashing often on PC since Season 3 update

Hi

I'm still having crashes without any OC on CPU/GPU/RAM. 

@Rokebo73  thanks for your suggestion, I'm running the game on a clean new Windows 11 install and my CPU usage is around 75% 

Have repaired, reinstalled and downloaded the game a couple of times. System drivers are up to date. Runing Windows in almost safe mode shouldn't be necessary to get a game to work.   

Game is still crashing and have done so for a couple of days. 

update: Turning settings from ULTRA down to HIGH has so far worked for me.

Have not experience DirectX function "GetDeviceRemovedReason" crash in a while. 

Hey,
the game crashes 4 me only on the new map.
I was able to play it like 5 times, since then the game only crashes when loading the new map. DX error.
All drivers up to date, no OVC(xmp on/off crashes both) , all components are compatible.
Win 10
Zotac 3080

ryzen 7 2700x

32GB 3000mhz memory on xmp ( 1866 without, still crashes)
Game on m2 SSD

Greets from Germany

Hello,

i have tried everything that is written here. But nothing worked for me.

The only one thats work, ist set the resolution from 1440p to 1080p + medium details + nvidia reflex off + dlss quality + fpslimit to 165fps in driver

Thats a bad solution for me, but it is enough to next patch that hopefully fix it.

i have now the max clock (default clock, no oc) from my gigabyte windforce rtx4090 24g reduced by 200mhz in msi afterburner. the game runs stable for 30minutes test, before i changed the clock its crashed 2-6 minuter
battlefield 2042 is a little bit sensitive since season 3, i think

@EA_Leeuw almost at my wits end with how my system crashes specifically during 2042 sessions only.

I've run every conceivable stress test with my pre-season 3 undervolt settings and GPU OC and the system keeps chugging along and never once hit an instability. Passed OCCT, AIDA64 Extreme (which I am currently running since 8AM GMT+8 6th December 2022).

I've gone back and forth on a couple of BIOS updates and the system crashes hard (black screen, fans ramp up to 100%, no response from power button having to cut power directly on the PSU). I've also dialed back everything, GPU and CPU back to factory specs only having XMP enabled for my RAM. After doing so, and playing up to three rounds, I thought the problem was solved, but once I attempted to start a fourth the system hard locks as explained. Here's where it really started to bake my noodle; I cannot replicate it consistently! It crashes badly whether it is one game or two or three. 

I've gotten so concerned that it could be a power supply issue that I've gone and purchased a tester, but the results from OCCT and AIDA64 are telling me that my system, that is currently having the CPU pegged at 100% and 76 degrees Celsius is completely fine and there's nothing wrong with it. As I am away from my system, here are the specs for my rig:

Ryzen 9 5900X 
Gigabyte B550M Aorus Elite
32GB Corsair Vengeance RGB RS 3600MHz
EVGA NVIDIA RTX 3070 FTW3 Ultra
EVGA Supernova 850GT 850W 80+ Gold PSU

It's not in the QVL with regards to Gigabyte and specifically this board but for all intents and purposes outside of 2042 it is stable. 

I've tried with a pair of 3200MHz Corsair Vengeance LPX RAM (for Ryzen as advertised on the Corsair box) which I know 100% works and the system still hard locked.

Again I have to stress, I'm running torture test after torture test that can't flippin' crash my system but this game can. Could drive a sane person to self-admit into a loony bin. I have yet to go home for the day and check on the AIDA64 Extreme test I've left running for 8 hours now, but once I do I'll post the results here. 

@EA_Leeuw So the test is still chugging along happily after 10.5 hours. I've attached my DXDIAG info if at all it helps the dev team.

The BIOS is an outdated one, I admit, but I thought of trying it since everything else seemed to not work.

I dont know why you mention him. You`ve seen he says all the time that oc is the problem even while we here proofed its not. I for my part deactivated xmp and my cpu oc and it still crashes....

Now i`ve set up all my oc back to on an xmp on and only by setting my 4080 "STOCK" mhz -150 it works. Its so stupid. Its the game. Same for the new nfs, same crash without the -150 mhz its an engine Problem.

Well, he did also mention to let him know if the crashes are still happening and as sure as the sun rises it is still happening. What's sad is the holidays are fast approaching and I'm afraid we're going to have to put up with the issue(s) until after.

It is a good thing I stayed away from purchasing Unbound from what you're saying. My entire system is rock solid up until the latest 2042 patch with the "performance improvements". 

---

@EA_Leeuw wrote:
The thing is; unfortunately, we can't do anything with crashes that suddenly occur when someone has an overclocked system. Here the crash results are invalid, as it may be due to the general instability of the system. It's also quite common for an OC to work on one game and not another, or from update to update.

It is also very important that you make sure that all your hardware components can work together. If something is not listed in a particular compatibility list, then you can assume that it may cause problems at some point. This often happens with RAM for example.

However, the teams have released Update 3.1.0 today and I am curious to hear if you are still experiencing game crashes.

---

@EA_Leeuw so you're saying that even with an extreme torture test that ran longer and more stable than any of my recent 2042 sessions doesn't mean the system is stable? I'm not sure how to react to that.

With regards to the recent update, I can't quite say because I've tried the user.cfg "fix" to limit the amount of threads being used. I will remove the file and attempt to run the game later. Shall report back if the fixes implemented in update 3.1 have worked. 

---

@Rokebo73 wrote:
@MentalReaperif your mem is not in the QVL list from your motherboard support , then this mem is not test at your motherboard !
So there are no stability report of this.
You should test your mem with a mem test for minimal 4 hours, if possible 24 hours !

hHardware not in the QVL and OC , is not in any support from a game dev. Thats is all at own risk !

Cheers !!

---

I have mentioned that (prior to using the user.cfg "fix") that I tried memory from QVL (a kit of 16GBx2 Corsair Vengeance LPX 3200MHz) for my specific board and the game still crashed my system. With that said, I do get what you and @EA_Leeuw are trying to say.

The only thing that is keeping the system from crashing, update 3.1 not withstanding, is probably the user.cfg file that's currently limiting the threads used to 14 out of 24. I tried 12 prior also stable. Now what's left to do is to remove the user.cfg file and test the game in its "raw" state. That is if I'm up for more troubleshooting. I've honestly had my fill of troubleshooting and not looking forward to doing it again so soon. 🙂

P.S. two nights in a row now, after the user.cfg fix system has yet to crash. Hopefully it continues this way.