i am using nvidia inspector to oc my card, and it works, and when i went to return settings to default it returned to normal values. However, when i recently oc'ed it, after i closed my game and returned settings to normal, the core clock and shader clock idled at a higher value then the current (default) set value. The memory clock is what it should be, but not what is used to idle.
They used to idle at:
core clock: 135
memory: 405
shader: 200 ish, i dont remember exactly
This is what i get now:
http://i.imgur.com/oWxQGZs.png
For some reason when i bring the shader clock to exactly match the current value ( the core clock value is affected directly by the shader value), it jumps up more and if i repeat it jumps up even further. If i default the settings, the values return to those seen in the first picture.
http://i.imgur.com/iAjSXg0.png
Any idea how i can get it to idle at the old values it used to idle at??
thanks in advance
-
King of Interns Simply a laptop enthusiast
Of course the shaders are directly connected with the core clock speed. Raise the core speed raises the shader speed and vice versa.
Hit apply default and clocks will return to normal. -
And as for the shader clock thing please be patient with me, I am a newbie at this. -
King of Interns Simply a laptop enthusiast
Hmm have you checked your clock speeds in GPUz too? Perhaps inspector is giving the wrong clock speed read outs. Worth trying.
-
i checked gpuz before and openhardwaremonitor and i got the same reading.
ok i guess after leaving it for a while it is now idling at:
core clock: 135
memory: 405
shader: 270
if i click apply default it jumps up to the 'default' value, then lowers itself again to the above values.
Seems to not lower itself until i have exited the game and left it for a while.
Ok, i guess thats that, thx for everything! -
Moral of the story: Patience, young grasshopper.
-
haha lesson learned
Overclocking my nvidia gt 630m 2gb
Discussion in 'Gaming (Software and Graphics Cards)' started by justatest, Dec 13, 2014.