Weird clock speed bug since driver 30x.x driver installs

CPC_RedDawn

Right, I have a vanilla GTX480 with an arctic cooling accelero xtreme plus 2 slapped on it for some amazing temps.

Overclocked to 850,1700,2000 and since I upgraded to the 300 series drivers I have seen that my clock speeds have changed. They now show in afterburner as 851,1701,and the weirdest is the memory as it shows 1998MHz.

The sliders in afterburner still show the correct overclock settings (850,1700,2000). Even if I change the sliders to say the memory to 2005, and click apply it sets the clocks wrong to 2010MHz. Very weird.

I am currently on 301.24 as it is the lastest beta for my card on Nvidia.com when I installed from 296.x drivers I did a fresh install and restarted when it completed. But I still have this weird bug.

It is not too worrying as temps are still perfectly fine, and games still work well too.

Just wondered if this was a known bug as I can not find anything about it on google, just stories about 2d and 3d clock bugs, which I do not get at all.

Anyone know a work around? Do I need to revert back to 296.x drivers? Does afterburner need updating (I am using the latest beta version).

Mufflore · 04-30-2012, 01:10 | posts: 9,520 | Location: UK

Rounding errors.
It might be reporting the actual speed now oir the reporting may have gained a bug.
Have you seen in your BIOS that some frequencies fluctuate slightly or that Bclk isnt exactly 100MHz.

Same thing on the gfx card, dont worry about it.
Frequencies dont go up in single increments, they jump a certain amount.

---TK--- · 04-30-2012, 01:42 | posts: 14,696 | Location: New Jersey, USA

thats due to the new kepler series. I ran 875/1750/4400 since launch now its 878/1756/4410. afterburner is now showing the actual clocks and not what we set them at. normal

IcE · 04-30-2012, 02:58 | posts: 6,989 | Location: Toledo, Ohio

Fermi always rounded clocks didn't it? Since shader and core are linked.

TechFreaK · *Last edited by TechFreaK; 04-30-2012 at 18:11.*

Yes i thought there was something strange with 300 drivers..

I have Overclock 850mhz/ram 2200mhz and in MSI afterburner it shows 851mhz/2198mhz., Gpu-z 0.60 and Nv inspector 1.9.6.5 display it correctly 850mhz/ 2200mhz.

Maybe its a glitch in MSI afterburner?

silis · 04-30-2012, 04:52 | posts: 71

Noticed the exact same thing with gtx 570, i sold the bitch.

Seb1 · 04-30-2012, 10:56 | posts: 34

MSI:AB shows the generated clock speed which is derived from the 27Hz oscillator × multiplier. The new NV drivers have a new API for clock monitoring, THERE'S NOTHING WRONG with your clock speed.

CPC_RedDawn · 04-30-2012, 17:36 | posts: 4,417 | Location: Wolverhampton/United Kingdom

Thank you all for the replies, gives me peace of mind that nothing is wrong

Mda400 · 04-30-2012, 21:52 | posts: 318 | Location: Minnesota

BUT I WANT PERFECT NUMBERS THAT ARE DIVISIBLE BY 4!... (lol 925/1850/2200)

I WANT PERFECT THINGS

Mufflore · 04-30-2012, 21:59 | posts: 9,520 | Location: UK

You'd best drop computing as a hobby/career then

---TK--- · 04-30-2012, 22:13 | posts: 14,696 | Location: New Jersey, USA

Quote:

Originally Posted by Mda400

BUT I WANT PERFECT NUMBERS THAT ARE DIVISIBLE BY 4!... (lol 925/1850/2200)

I WANT PERFECT THINGS

use the older drivers then, the numbers you see now are the real clocks not approxamations like before

viren · *Last edited by viren; 05-01-2012 at 02:00.*

I noticed that clocks would stay the same even after ocing unless i restarted the pc. But thats not the problem you stated, i hope you checked the clocks in gpuz and also i would not worry if there were minor fluctuations in the clock speeds. Just on a second thought try reverting back to driver 290 to see if the problem persists then we would know for sure that it is a problem with the new drivers.

viren · 05-01-2012, 01:57 | posts: 2,326 | Location: Pune, India

Quote:

Originally Posted by silis

Noticed the exact same thing with gtx 570, i sold the bitch.

I pity the Gtx 570 but atleast now im happy that it has gone in the right hands.

IKnowJack · 05-02-2012, 04:02 | posts: 176 | Location: darkside of the moon

i cant beleive this question came from an "ancient guru"...

firstly...RTFM..and 2nd..the change is negligable 1mhz should not be an issue, its not like ya gonna gain/loose even 1fps

so +1mhz on the core, +1mhz on the shader, -2mhz on the mem = same as previous!...

and really...shader increasing by 1mhz when the core increases 1mhz...WRONG!..shader is double pumped core..so shader can ONLY increase by 2mhz increments...UNLESS the card is actually pumping half a core clock faster! then the shader can double to 1mhz!

sapo_joe · 05-02-2012, 13:38 | posts: 172 | Location: Brazil

I'm using the 301.32's and there seems to be no problem with the clocks anymore. It used to get stuck with 3d or 2d clocks for no reason before, now problem is gone.

FXAA is great with these, adaptive vsync, not so much...