Aorus 1080 ti, restarting pc. NEED HELP!

dmccabe186

Prominent
Aug 18, 2017
13
0
520
Just got a 1080 ti Aorus, put it in my pc this morning just to try some different games and see the improved performance. Just to find when it get to graphically intense areas it restarts my pc with no crash just instant restart. I played a game on low for maybe an hour and it was fine, But tried the witcher on ultra, tomb raider on very high and it will restart after 5 mins max. I have ruled out the following.

1. I have done clean install of all drivers
2. Used DDU to try install clean drivers again
3. Used my old Gtx 970 to run the exact same games with no restarts, which worked
3. Used different PCI slot and different cables to power the card.
4. Took pc apart and checked for loose connections

My Specs are :

Processor: Intel 4690k @4.3

GPU: Aorus 1080 ti

Motherboard: Gigabyte GA-Z97X-GAMING3

PSU: Corsair CX 750M

Storage:
3TB HDD
1TB HDD
120GB SDD

RAM: G.Skill RipjawsX 2x8gb (1600 MHz)

Monitor: 1440 144hrtz acer xb270hu
 
Solution

dmccabe186

Prominent
Aug 18, 2017
13
0
520


1. Yes I deleted the old drivers and used DDU to make sure they were gone.

2. I have a Corsair CX 750M and it is 2 years old next month.

 


Use software like SpeedFan to monitor psu output, also CPU-Z, GPU-Z to monitor all components and performance. Please report what do you see right before restart :)
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Ok, I done this and I took a video of it as I can't screenshot in time to catch restart. So this is a screengrab from the video right before restart. Not sure if I have the info needed on screen though.
n0BlHx3.jpg


 
If those measurements are accurate, voltage seems fine for both GPU and CPU. Temperatures are good as well. Only thing is CPU is bottlenecking your GPU, but running at 100% shouldn't restart your pc automatically... Do this first and then we may have better idea about what is going on:

To see what the error was you can change the default behavior by right clicking on “My Computer” and choosing “Properties”. Goto the “Advanced” Tab and under “Startup and Recovery” press the “Settings” button.

Under the “System Failure” box there will be a checkbox saying “Automatically Restart”. Untick this box and click Ok. This time we may see some error code in BSOD.

BTW, what is CPU usage when idle?
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


My idles usage is 3-15%. I also turned off the automatic restart and it still just instantly restarted. No error or BSOD. It actually restarted much faster than usual. Within 1 second of benchmark.

 

EpIckFa1LJoN

Admirable
Aorus cards have had a reputation for being too highly OC'd out of the box and being unstable.

I assume you wanted a really fast card out of the box, you should have gotten a Zotac AMP! Extreme.

In any case it sounds like the OC is bad and you need to cut it down. There are plenty of people with this problem and that GPU.

Do a little research and see what settings people are using. If it does end up being the GPU OC I would get my money back and get the cheaper and faster Zotac. (Be warned I've heard of the same problem on the Zotac AMP Extreme but the prevalence is much lower)
 

EpIckFa1LJoN

Admirable


It's most likely the GPU OC. If he were OCing the CPU, the voltage would be too low and he would see a freezing crash and possibly BSOD.

With the GPU OC too high (and it looks to be on the factory default) he would get the restart crash that is happening.
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Yeah I will try downclock and run tests again and see what happens, thanks.
 
If that's the CX750M with a green label which I think it must be if its 2 years old they are crap quality. Don't risk a high end gpu and pc on a low quality psu. What you describe is typical of a psu fault and installing a high end gpu has increased the load on the psu.
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Yeah I plan on getting a better one soon, any suggestions on one?

 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Downclocked the gpu to close to reference 1080ti's and even more problems. After a 2 benchmarks I started getting this on screen
RzfFI6D.png


Then my fps tanked from Average of 160 to 26 in tomb raider.
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


I do have a oc on my cpu from 3.5 to 4.3, but it's stable and used prime95 to test this. The gpu was on stock but even clocked down it had more problems, like white lines across the screen in games and on the windows log in screen. I will link pic of white lines that appear every now and again. These lines also cannot be my monitor. Because it happens on both of my monitors.
RzfFI6D.png


 

EpIckFa1LJoN

Admirable
Yeah if that GPU isn't running well on reference 1080 Ti levels its just no good.
If its not crashing but is giving off artifacts that means you are closer to being stable but it sounds like you would have to clock it down to reference levels.

You did adjust the voltage though right? If you just clocked it down the voltage could also be too high for the clock speed. I'm not sure if over-voltage can cause artifacts by itself if its in the safe range but that might be worth checking out.

Also lower the memory clock to the standard 11,000MHz. Set everything as close to the reference specs as possible.

In any case it is not running as advertised obviously.

I would return it and get something with a better track record of reliability.

Like I said the Zotac AMP Extreme is a fantastic card, and is actually faster and cheaper than the Aorus. But I guess that also depends on your location. And if you like LED's there are none better.
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Yeah I clocked it all down right like you said, but I think I will try another power supply from a friend and if that doesn't work I will return it and see about the card you mentioned above. Thanks

 

EpIckFa1LJoN

Admirable


Let us know if it works out for you.
 

dmccabe186

Prominent
Aug 18, 2017
13
0
520


Replaced my psu from a CM750m to a RM850x and it worked perfectly, no crashes or stuttering like before. It was the power supply.

 
Solution