Battlefield 2042 restart whole pc
Guys! Please help me! I upgrade my bios I have newest graphic drivers I repaired battlefield 2042 in ea app And still have crashes while playing in BF2042 long time (few months) so please help me...
Forum Discussion
Sorry for wall of text, just wanted to post an update.
The game has been restarting the PC again ever since the 5.3.0 update. I've since just given up and updated to newer nvidia drivers for newer games since the old driver wasn't helping anymore. The GPU downclock wasn't helping anymore either (hey, at least it worked for like 2 months).
Though, like I've said before, there's something about the smoke in this game that makes my PC restart itself. 99% of the time, there has been some type of smoke on the screen (whether it's vehicle smoke, smoke grenades, smoke grenade launcher smoke it doesn't matter). My own smokes don't seem to be a problem, but as soon as another player uses smoke it's a tossup on whether it would crash or not. An example would be a CO-OP breakthrough round on orbital (the one with the rocket launch iirc) where I was pretty much only using the smoke grenade launcher as Angel to resupply myself (one of the few things I can still get ranks on in solo/co-op), and it was fine all the way till the end when i noticed my friend fire his smoke grenade launcher once (i heard it) and immediately restarted my PC. We only play on 64 player servers since one of my friends runs on older hardware (at least they don't crash though they do sometimes get stuck with a black loading screen in between rounds).
I wouldn't be surprised if this game was what bricked my previous M.2 drive. I'm just tired of jumping through hoops trying to deal with this issue that only affects this game.
A thought just occurred to me while writing this rant in frustration... I need to start keeping track of whether the guns I'm using have IR scopes or not... No promises, though, since I've stopped playing unless my friends are playing and I've crashed at least once every other time we play.
Edit: update 5.3 , not 5.2
@blckbird2002 wrote:Sorry for wall of text, just wanted to post an update.
The game has been restarting the PC again ever since the 5.3.0 update. I've since just given up and updated to newer nvidia drivers for newer games since the old driver wasn't helping anymore. The GPU downclock wasn't helping anymore either (hey, at least it worked for like 2 months).
Though, like I've said before, there's something about the smoke in this game that makes my PC restart itself. 99% of the time, there has been some type of smoke on the screen (whether it's vehicle smoke, smoke grenades, smoke grenade launcher smoke it doesn't matter). My own smokes don't seem to be a problem, but as soon as another player uses smoke it's a tossup on whether it would crash or not. An example would be a CO-OP breakthrough round on orbital (the one with the rocket launch iirc) where I was pretty much only using the smoke grenade launcher as Angel to resupply myself (one of the few things I can still get ranks on in solo/co-op), and it was fine all the way till the end when i noticed my friend fire his smoke grenade launcher once (i heard it) and immediately restarted my PC. We only play on 64 player servers since one of my friends runs on older hardware (at least they don't crash though they do sometimes get stuck with a black loading screen in between rounds).
I wouldn't be surprised if this game was what bricked my previous M.2 drive. I'm just tired of jumping through hoops trying to deal with this issue that only affects this game.
A thought just occurred to me while writing this rant in frustration... I need to start keeping track of whether the guns I'm using have IR scopes or not... No promises, though, since I've stopped playing unless my friends are playing and I've crashed at least once every other time we play.
Edit: update 5.3 , not 5.2
My PC used to crash and power cycle. It's usually caused by RAM timing issues or CPU voltage issues.
HCI Memtest is a good ram memory tester.
This is clearly a bad set of coding. I doubt it will ever be resolved.
