Re: Game crashing often on PC since Season 3 update

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.

We unfortunately also can't help if players themselves made changes to a settings- or some sort of cfg file.

I recommend that you undo any changes you made to the settings file, or cfg file (if you can still do that), undo any overclock or XMP, make sure that all your hardware components are compatible with each other, and then check if you are still experiencing any crashes.

---

@EA_Leeuw wrote:

We unfortunately also can't help if players themselves made changes to a settings- or some sort of cfg file.

I recommend that you undo any changes you made to the settings file, or cfg file (if you can still do that), undo any overclock or XMP, make sure that all your hardware components are compatible with each other, and then check if you are still experiencing any crashes.

---

I managed to bring myself to test the system without overclock and the game ran fine. 

Now my only question is how this is so after season 3 performance update came about. Prior there weren't any issues to speak of (hard locks, crashing of any kind).

Kind of defeats the purpose of having hardware that is more than capable of holding its own whether at stock or what was known to be a stable overclock before the patch. Just thinking out loud here. 

---

@MentalReaper wrote:

---

@EA_Leeuw wrote:

We unfortunately also can't help if players themselves made changes to a settings- or some sort of cfg file.

I recommend that you undo any changes you made to the settings file, or cfg file (if you can still do that), undo any overclock or XMP, make sure that all your hardware components are compatible with each other, and then check if you are still experiencing any crashes.

---

I managed to bring myself to test the system without overclock and the game ran fine. 

Now my only question is how this is so after season 3 performance update came about. Prior there weren't any issues to speak of (hard locks, crashing of any kind).

Kind of defeats the purpose of having hardware that is more than capable of holding its own whether at stock or what was known to be a stable overclock before the patch. Just thinking out loud here. 

---

Agreed. 
If our systems are more than capable to run any other game maxed out how can we be told "it's you not us" regarding our systems. 
That's a bad route to take, especially since these issues arose after the latest update. 

Agreed. 
If our systems are more than capable to run any other game maxed out how can we be told "it's you not us" regarding our systems. 
That's a bad route to take, especially since these issues arose after the latest update. 

---

To alay any fears of corrupt RAM (on my system at least) I ran memtest86. Results as attached. 

So far:

1. AIDA64 for 11.5 hours --> no crash (attached photo shows 10.5 hours at the time I saved the screenshot, let it run for another hour more)
2. memtest86 (ran with XMP and undervolted CPU which technically goes against their guidelines of having only XMP enabled) --> no errors

Color me baffled but I'll say this though; without the user.cfg file in the Battlefield 2042 game folder, game runs at 16 threads and this seems to crash the system. With user.cfg capping threads at 14 it crashes also although previously I stated that it seemed stable. 12 threads seems to be the magic number that my system is happy with when it comes to this game.

---

@Rokebo73 wrote:
@MentalReapercould you post the brand and partnumber of your mem please ? Thanks

---

It's right there in the memtest86 results.

Anyway it's a Corsair Vengeance RGB RS 32GB kit. I will admit that this kit isn't part of the QVL for my B550M Aorus Elite BUT works flawlessly with my system. Gigabyte's QVL is hardly up-to-date anyway.

https://www.corsair.com/us/en/Categories/Products/Memory/VENGEANCE-RGB-RS/p/CMG32GX4M2D3600C18

---

@Rokebo73 wrote:
@MentalReaperHey man !
13 pages of VERMEER CPU compatible memory and you got the wrong partnumbers.
I bet with you , mem is causing you GPU errors !
You got other mem you told before, is this part number in the MEMORY VERMEER QVL ?

You cant fix those issues you got now with any setting. Even memtest doesnt show up errors, cause it works different at cpu/memory then bf2041 does !

Best way is sell all old ram and buy a set of new ram in the memroy qvl VERMEER !

Cheers man !

@Rokebo73 I think you're not getting what I'm trying to say here, so to reiterate:

 

1. I know the memory isn't in the QVL

2. The QVL is outdated, has yet to be updated which means the current set that I have could very well work, and IS working as intended for everything else, gaming included, outside of 2042

3. memtest86 shows NO ERROR despite the fact that I have XMP And a CPU undervolt applied contrary to what memtest says to do and it still passed all thirteen tests and four passes

4. No amount of stress testing has brought my PC to its knees.

 

 

After 3.1 update, my game began to crash.😞

@MentalReapermem test need to run for 24 hours or more, not just those few minutes you probarly did.
And you need to keep in mind that memtest or any other stress test not always display any errors.
Most of the erros accure when software is running, something as BF2042!
Also the MEM QVL at the website from your motherboard is UPDATE , with mem that is TESTED at youre motherboard !!!!

And you dont need to convince me from what you have or think.
My advise is go to a PRO PC STORE and ask them what they think and advise about your current mem !

And remember , mem doesnt always show errors even if it is broken or NOT COMPATIBLE with your cpu !!

Cheers , no hard feelings ! Peace

Dear @EA_Leeuw ,

Here is my PC:

CPU: i5 12600KF (OC 4.8Ghz)

MB: MSI Z690-A PRO DDR4 with BIOS 7D25v19

RAM: KLEVV BOLT X DDR4 3600 (XMP)  16G x2

GPU: GTX 2070S with 527.56

POWER: Corsair AX760I

System: Windows 11 Version 22623.1037

Before the update 3.1, everything worked fine, no crashing, and no screen freezing. 

After update 3.1, the game crashed every round, with dark screen and sound froze, then the only way is to reboot the pc.

In the beginning, I thought about the memories, so I tried to raise the RAM voltage from 1.35V to 1.42V. The frequency of crashes has eased but still will crash.

Then I am trying your suggestion, just dismiss all the OC, now the CPU working with the default at 3.7Ghz, and the memories are working at 2666Mhz. The game will still crash my PC.

and this situation is only happening when playing the BF2042.

@Rokebo73 

Here is the dxdiag. I had to try to reinstall the game. It's no help. But it will not crash every round, sometimes I can finish the round(25-30mins).