Mass Effect Andromeda - CPU running at 100%, crashing

Alyanova

Prominent
Mar 24, 2017
3
0
510
Relevant Specs?
CPU: Intel i5 3570k Ivy
GPU: Nvidia GTX 980
16gb RAM

So immediately when I start Andromeda, it jumps my CPU up to 100%, and the CPU temp goes from 30c idling to 85c in game before it crashes. I know my processor is listed as the minimum requirement, but this doesn't seem normal. I've never had this issue with any other games in the past. I've also never overclocked my CPU, if that's worth mentioning.

What can I do to resolve this? Can it be fixed? Is this a problem with my game, or is it a problem with my CPU?
 
Solution
i have an i7 6700 , gtx 1080 xtreme gaming, 16 gb ram, 850 w psu . and i get 100% cpu usage with temps reaching 83 degrees (that was the point where is shut down the game to prevent shity situations).THE fps were pretty constant so no problems there but it freaks me out. Tomorrow i shoudl get a new cooler for the cpu so maybe that will fix my temps
85 C? If i remember well, Ivys temperature should not exceed 67 C. It is a miracle that you didnt crash earlier than 80. You shouldn't have this issue anyway. Have you checked in task manager if any third party applications are running when you start up the game? Apart from that, the game is probably not yet optimized.
 

Alyanova

Prominent
Mar 24, 2017
3
0
510
Yeah, no 3rd party programs running, nothing CPU intensive anyway (CPU runs around 0-1% idle before I open Origin and launch the game). I was actually able to keep the game going for about half an hour just now before it crashed, at which point the CPU got to 94 degrees. Feels like I'm playing with fire even trying that, though, and I'd rather not push it. With everything wrong with the game, I'm not sure if an optimization patch is even going to happen.
 


Are you overclocking your cpu? Yes or no, check if you need to apply new thermal paste and maybe buy a better cooler until you have it resolved. It's a shame to fry your processor. Even running at 100% should not raise your temps that much. Have you stressed your CPU using a software to check whether this happens only in-game, or particularly this game?
 

Alyanova

Prominent
Mar 24, 2017
3
0
510
No overclocking. I ordered some thermal paste and a new heat sink so I'll see if that makes a difference. I haven't stress-tested it yet, but I did test several other games. Playing the Witcher 3 ran it around 75 degrees, Fallout 4 around 70, and none of my other games push it past 65-ish. Likely a cooling issue mixed with Andromeda being horribly un-optimized (wouldn't surprise me one bit).
 


Make sure your cpu is in full contact with the heat snik. If you had a stock intel cooler, those four button arms are sometimes tricky. Good luck
 

Demon_2

Prominent
Apr 5, 2017
1
0
520
i have an i7 6700 , gtx 1080 xtreme gaming, 16 gb ram, 850 w psu . and i get 100% cpu usage with temps reaching 83 degrees (that was the point where is shut down the game to prevent shity situations).THE fps were pretty constant so no problems there but it freaks me out. Tomorrow i shoudl get a new cooler for the cpu so maybe that will fix my temps
 
Solution

flyinggoatman

Prominent
Jun 16, 2017
1
0
510
Turn down your settings to Medium and resolution to 1080p. If your PC crashes then hold down the power button for 40 seconds. Make sure to unplug power before you do. After you've done that it should boot back up and may run slower for a bit while the driver cools down.

This issue seems to be with your graphics card. The menus have a problem where fps has no cap. This means means the game cuases the graphics card to poop. This is a issue with one of two things.

1. Mass Effect Andromeda.
2. Nvidia Drivers.


Normally the game will crash at certain points in the story. After you've passed the mission where you crashed you can turn settings back to high but sooner or later it will come across a point where it'll crash again. Sorry I can't be of more help. I'm contacting EA and Nvidia to report this issue. I'd advise you do the same.

Please note my information was from some info I saw a few weeks back and may be incorrect when it comes to what is causing the issue. However the fixes do work for me still.