ASUS GTX 970 Clock Speed Problems

squirrelybandit

Reputable
Feb 5, 2016
3
0
4,510
Hi everybody!

I have a strange problem with my new ASUS gtx 970 Strix card that I cannot seem to find an answer to. I noticed that every once and a while, the gpu's clock speed will drop. Normally, when I'm gaming, the boost clock maxes at around 1380 MHz. However, there are times when it will max at around 700 MHz. It will continue to do this until I restart my computer, and then it will go back to normal.

When it drops to 700 Mhz, there is a significant drop in FPS. When I'm playing COD Black Ops 3, for example, I will get around 40-45 fps. The gpu also runs significantly cooler, as I can imagine that's a result of the clock speed dropping. Like I said, I have found no way to fix this except for restarting my computer. It then goes back to normal, but after an hour or two or even up to a day it will work fine until something happens and it drops to almost half speed.

I have the latest NVIDIA drivers and an adequate PSU. My following set-up is:

PSU: Cooler Master 800w Gold Pro
Processor: AMD FX 6350
MOBO: ASUS m5a97 r2.0
RAM: 16gb @ 1600MHz

Temps are usually a bit high, around 80 Celsius when maxed, but around 65 Celsius when at around 700 MHz. I do not believe this is throttling, but is maybe due to a power issue, but I have no idea! Please any response would be greatly appreciated, I can run any tests to help you guys out, but I'm hoping maybe somebody out there has had a similar problem and knows what the cause is. Thank you!

 

squirrelybandit

Reputable
Feb 5, 2016
3
0
4,510
Aye so I finally figured out my problem. In case anybody had the same problem, I thought I'd share the solution. In MSI Afterburner, I needed to turn the power limit up to 120%. For some reason, my card's clock would draw more than 100% causing a power limit signal to turn on and then would reduce the clock speed to like 50%. The boost clock was hitting 1380 which is higher than it's rated so perhaps it is stuck overclocking itself without restructuring the power limit. Problem solved tho!