Overclock.net banner

GTX 1060 downclocking

4K views 17 replies 5 participants last post by  fido 
#1 ·
Hey guys just a quick question for you brainy bunch out there...
I have watercooled gtx 1060 overclocked to 2.1ghz. My temps never go over 60c on a summers day with heaven running for an hour... One thing i am wondering tho...
I know gpus slowly underclock themselves as they increase in it.. Is there anyway i could turn this feature off?
my gpu downclocks it self from 2101mhz to 2088mhz at 53c and again to 2076mhz at 58c...
As i mentioned my gpu is fully watercooling and the fans are the 240mm rad are currently only at 30-40% to achieve these temps. I know for sure im not going to exceed 60c at any point but is there anyway to turn off this feature i can have 2.1ghz and for it not to downclock at the temps above? If possible i want the card to ofcourse downclock when not gaming and casually browsing the web but whilst game i want the full 100% 2.1ghz at all times..
Any thoughts?
Many thanks
browny2911
 
#2 ·
Why would you want to underclock if you have a water-cool'd setup?
 
#3 ·
thats the opposite of what i want. The gpu underclocks itself at certain temp increments. Knowing ill never go over 60c or hit a dangerous temp i want it to run at 2.1ghz all the time whilst gaming not underclock at certain points.. However i dont want it to run 2.1
ghz constant whilst just casually browsing the web
 
#4 ·
Ah okay, what program are you using to overclock? Let's see a screenshot, have you tried raising the voltage? Power Limit? Temp Limit?
 
#5 ·
Untitled.png 548k .png file


im using MSI afterburner
settings all displayed there
card runs at 1607mhz when doing nothing... which is fine...
card runs at 2101mhz until it hits 53c then downclocks to 2088mhz to prevent it overheating.. I know for a fact being watercooled it wont overheat and like i say never exceeds 60c i just want to stop this happening basically
its not a huge deal it would just be nice
 

Attachments

#6 ·
Turn your voltage up to 85-90%
Your core clock between 130-200. (not sure what your card can handle)
Go to gpuz and look under memory type. If you have Samsung memory, you can likely overclock your ram to 4500, or higher. So that would be +500 instead of 300 in after burner under memory clock.

Try to run a game, see what clocks you're pulling after 15-30 minutes.
 
#10 ·
AFAIK, I don't think you can bypass the temperature induced down-clocking. Your best bet would be to turn those fans up/get better fans if you want better temps at the same rpms/noise levels. I will say, 53*C seems high for a 1060 on a water loop (even if it is on one 240mm rad).
 
#11 ·
wait what 53c is high for a 1060 at 2.1ghz on watercooling? thats lower than what my card would idle at with the stock evga fan and thats after 30mins stress testing at max overclock. i dont think thats particually that hot. i have ek vardar fans on the rad i could up a little bit i enjoy a quiet machine
 
#12 ·
I can get 2088 on air..He can definitely get at least 2100....Just have to overclock it correctly. I promise. My GPU runs at 2100 sometimes until it reaches 60-62c...
mad.gif
 
#14 ·
Quote:
Originally Posted by browny2911 View Post

wait what 53c is high for a 1060 at 2.1ghz on watercooling? thats lower than what my card would idle at with the stock evga fan and thats after 30mins stress testing at max overclock. i dont think thats particually that hot. i have ek vardar fans on the rad i could up a little bit i enjoy a quiet machine
That temp is high for WATERCOOLING (and clearly too high to hold your card at 2100). My 1060 used to max out in the low 40's on a single 240mm rad w/ 2 GT 1450's @ 50% speed. My 1080 tops out around 35*c, but I have more rad-space now (600mm + cools a 3930k @ 4.4). Personally I would set a more aggressive curve and see what your temps are like and if it can maintain the clocks you want.

I was able to clock the 1060 to around that on air, but had the same issue where anything over 50*c would start dropping the clocks more and more. Put a universal block on and put it in my CPU loop and clocks never dropped after that.
 
#15 ·
when i test this it was 27c in the room it was tested in.. also i have connected the cpu in the same loop. The fans are the rad are running pretty low but i dont like a noisy system. From what ive seen online under my conditions 53c seems totally fine. Plus its not clearly to high to keep my card at 2100mhz because it already does that just fine. it only downclocks by 13mhz from 2114 to 2101mhz in total. I just wanted to know if it was possible to stop this in general but as pointed out by another uses its nearly impossible to stop gpu boost 3.0.

Plus this system is cheaply built with a cheap gpu block and pump.

My old temps would reach up to 80-85c with an ambient temp of 27c and downclock to 2012mhz
Now with a cheap block its gone down too 53c with an ambient temp of 27c and downclocks to 2101mhz from 2114mhz

So theres roughly 30c lower temps and a higher clock

The card currently idles around 35c and takes 30-45min at 100% to get it to 53c

Sure i could up my fan speed on the rads but there near silent at the moment and i prefer that over a noisy system
 
#16 ·
I thought you were having problems with 2101 dropping to 2088? Another user and I were the ones saying you cannot bypass the temp throttling. It is literally the most headache inducing thing about Nvidia cards.

While your temps are good/great, they are too high for boost 3.0, that was all I meant by that.
 
#18 ·
Quote:
Originally Posted by paulerxx View Post

Turn your voltage up to 85-90%
Your core clock between 130-200. (not sure what your card can handle)
Go to gpuz and look under memory type. If you have Samsung memory, you can likely overclock your ram to 4500, or higher. So that would be +500 instead of 300 in after burner under memory clock.

Try to run a game, see what clocks you're pulling after 15-30 minutes.
u mean by voltage ( power usage )
voltage is in x.x like 1.3 etcc
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top