PC shuts off at times when playing Dying Light

[ZombieHunter]

My PC has been shutting off randomly when playing Dying Light.

EVGA Precision X is reporting 3100 MB usage, 69C - 76C temps and I'm getting anywhere between 85 to 160 FPS depending on the area.

FOV is at 97, Chromatic aberration is off, blur is off, motion blur is off and depth of field is off b/c those 'features' make the game ugly and make we want to hurl after playing for ten minutes. The game as it is now is barely taxing my system.

CPU: AMD FX-8350 8 core @ 4.01GHz (as reported by Windows)
CPU Cooler: Liquid - Corsair H50
PSU: 1000W Antec PSU
RAM: 16GB Corsair Dominator 2300 @ 1800 b/c of limit set by AMD FX-8350
Mobo: ASUS Crosshair V Formula Z with CPU AI overclock set
GPU: EVGA 970 GTX FTW 4GB - stock cooler
Displays: Dual Samsung 1600x900
Drives: 5 - (1 WD 300 GB, 1 WD 1 TB, 2 WD 2 TB, 1 CD / DVD - RW).
OS: Windows 7 64 Ultimate 64-bit

CPU temps: 45 - 47C idle, 50 - 60C under load
GPU temps: 55 to 63C idle, 65 - 76C under load, heat limit set to 75C

I've stressed the system with Prime95 and with the EVGA Precision X stress test and cannot duplicate the problem.

None of my other Steam games do this and I have way too many of them so the sample size here is quite large. One would think at least one or two other games would duplicate the issue.
This one game out of the 478 in my library causes my PC to shut off.

Any ideas?

[Zodasaur]

Have you ever run memtest86 before?

[Tarc Novar]

Originally posted by Viper74:

My PC has been shutting off randomly when playing Dying Light.

EVGA Precision X is reporting 3100 MB usage, 69C - 76C temps and I'm getting anywhere between 85 to 160 FPS depending on the area.

FOV is at 97, Chromatic aberration is off, blur is off, motion blur is off and depth of field is off b/c those 'features' make the game ugly and make we want to hurl after playing for ten minutes. The game as it is now is barely taxing my system.

CPU: AMD FX-8350 8 core @ 4.01GHz (as reported by Windows)
CPU Cooler: Liquid - Corsair H50
PSU: 1000W Antec PSU
RAM: 16GB Corsair Dominator 2300 @ 1800 b/c of limit set by AMD FX-8350
Mobo: ASUS Crosshair V Formula Z with CPU AI overclock set
GPU: EVGA 970 GTX FTW 4GB - stock cooler
Displays: Dual Samsung 1600x900
Drives: 5 - (1 WD 300 GB, 1 WD 1 TB, 2 WD 2 TB, 1 CD / DVD - RW).
OS: Windows 7 64 Ultimate 64-bit

CPU temps: 45 - 47C idle, 50 - 60C under load
GPU temps: 55 to 63C idle, 65 - 76C under load, heat limit set to 75C

I've stressed the system with Prime95 and with the EVGA Precision X stress test and cannot duplicate the problem.

None of my other Steam games do this and I have way too many of them so the sample size here is quite large. One would think at least one or two other games would duplicate the issue.
This one game out of the 478 in my library causes my PC to shut off.

Any ideas?

Based on your description, my educated guess is that your CPU is overheating which then shuts down the computer before it is damaged. I've seen the exact same thing before when an issue existed with my cooling fan.

[Dragonway]

Your idle temps for both cpu and gpu are pretty high. I'd suggest taking a look at your cooling solutions, maybe clean your computer and get rid of dust or apply new thermal paste to cpu and gpu to see if it makes a difference

[leandro]

AMD get easy very hot 'c so you need get watercooling system that will help heat gone and low heat

[Box]

reseat the cpu, may need thermal paste. or bad memory. Good luck :)

[the_lone_ran9er]

Temps look fine for both hardware, you can run the FX - 8350 24/7 @ anywhere under 61c. The GTX 970 can go higher still, 70c-80c is a non issue and standard operating temperature on my GTX980Ti. If your confident that is the temperature @ the point of shutdown. Plus if you haven't messed with the bios it should simply throttle before shutting down.

In almost all cases like this I would look to the PSU as the first most likely culprit, it doesn't even matter if it's a good quality platinum rated PSU way above spec for your PC's power draw, I've had countless PSU's die over the years causing these symptoms, even really good ones. How old is the PSU ?

[Jacqueline]

what Power Supply Unit do you have?
what bios do you have?
what is the heat of your north bridge?
this the tree hugger and nanny thingy in the bios enabled? (aka power saving and turn of if heat get to X)

[Jacqueline]

ups he did "PSU: 1000W Antec PSU" the small h50 takes you eyes away from it, but he should be asking for help on https://rog.asus.com/forum

I'm running a 9590 with 2x 390x on high @1080p (waitting for benq 4k 1ms monitor)
and with 60 to 120 fps and cpu is at 94% just the game.

oh this is a pc combo that needs big case if air cooled.

laak of cooling is a killer and mx-2 thermal paste heat in time turns it to dust

[*D4rKsKy*]

Originally posted by Gregory:

55-63C idle is ♥♥♥♥♥♥♥ awful for a GPU, I get close to these values under heavy load.
You should reconsider your cooling solutions.

Thats still fine u talking bs now, its his load temps what counts.

@ OP try to use MSI afterburner then check your temps while u play, then u know for sure.

[crazymike]

Originally posted by motherboard11:

Temps look fine for both hardware, you can run the FX - 8350 24/7 @ anywhere under 61c. The GTX 970 can go higher still, 70c-80c is a non issue and standard operating temperature on my GTX980Ti. If your confident that is the temperature @ the point of shutdown. Plus if you haven't messed with the bios it should simply throttle before shutting down.

In almost all cases like this I would look to the PSU as the first most likely culprit, it doesn't even matter if it's a good quality platinum rated PSU way above spec for your PC's power draw, I've had countless PSU's die over the years causing these symptoms, even really good ones. How old is the PSU ?

I agree. I think the factory limit on the 970's and 980/980ti's are 86c, then they handicap the core clock to cool back down, not shut the pc off. Running 2 980ti's in SLI OC'ed and never had the pc shut off. For sh@ts and giggles, try running Afterburner (like mentioned.. if the overlay will work in game, if not I know the CAM monitoring overlay from NZXT works in game). You might even try verifying your game cache to see if you've got some bad files causing problems.

[Erebus]

Originally posted by *D4rKy*:

Thats still fine u talking bs now, its his load temps what counts.

@ OP try to use MSI afterburner then check your temps while u play, then u know for sure.

With those idle temps for the actively cooled components there is the potential that the passively cooled parts of his comp are getting baked.

His mobo might be getting "baked".

[ZombieHunter]

Originally posted by Erebus the Indolent:

Originally posted by *D4rKy*:

Thats still fine u talking bs now, its his load temps what counts.

@ OP try to use MSI afterburner then check your temps while u play, then u know for sure.

With those idle temps for the actively cooled components there is the potential that the passively cooled parts of his comp are getting baked.

His mobo might be getting "baked".

Those temps were after a night of gaming anyways. At idle without having played any games and my temps are CPU 27C and GPU 40C.

It is not the temps. Please only respond if you are familiar with gaming motherboards and understand cooling and the components I have. AMD chips don't triple fault when hot they throttle cores to cool down. NVIDIA GTX 970's don't use the fan until 60C. The case is a full tower case and well ventilated. If either the CPU or GPU were hot Dying Light would not be pulling 60 to 160 FPS consistently. It would stutter endlessly as the cores were throttled or it would have tons of artifacts. NVIDIA GPUs will still render when extremely hot they just render crazy stuff because the vertices and matrices get all out of wack due to bad values caused by components being too hot.

I ran every stress test except memtest86 which might be something to try. I have seen Dominator RAM modules fault before and often times its the one you almost never use. As soon as an application begins to use it, it fails. This normally does not cause a shutdown but will cause applications to fault.

I'm also leaning towards PSU. It is around 3 years old and still under warranty so that is an easy fix. Since I don't have any equipment to test it I may just have to send it back under warranty. Also my GPU fans are on their own rail, hard drives are split between 2 rails, CPU water cooler is off the mobo power and 1 rail on the PSU isn't even being used.

One nagging question remains. If Dying Light is taxing my system to shutdown...which I verified its not taxing my system...why do games that do tax my system not also cause a shutdown? Something is amiss.

[Erebus]

Originally posted by Viper74:

Those temps were after a night of gaming anyways. At idle without having played any games and my temps are CPU 27C and GPU 40C.

So basically the idle temps in the OP aren't actually the idle temps.

One nagging question remains. If Dying Light is taxing my system to shutdown...which I verified its not taxing my system...why do games that do tax my system not also cause a shutdown? Something is amiss.

Check the event viewer.

[ZombieHunter]

Originally posted by Erebus the Indolent:

Originally posted by Viper74:

Those temps were after a night of gaming anyways. At idle without having played any games and my temps are CPU 27C and GPU 40C.

So basically the idle temps in the OP aren't actually the idle temps. :conwayfacepalm:
Those were the idles but after playing for a bit. Doesn't matter. Its not the temps.

One nagging question remains. If Dying Light is taxing my system to shutdown...which I verified its not taxing my system...why do games that do tax my system not also cause a shutdown? Something is amiss.

Check the event viewer.

Nothing in the event viewer.

[Erebus]

Originally posted by Viper74:

Originally posted by Erebus the Indolent:

So basically the idle temps in the OP aren't actually the idle temps.
Those were the idles but after playing for a bit. Doesn't matter. Its not the temps.


Check the event viewer.

Nothing in the event viewer.

Nothing at all?