Really odd issue with Core Temp 0.96

[Jay_2]

look at this image

you will see that 0.96 is saying the CPU is running at 2137MHz where as everything else says its 2404MHz

I have no powersaving on so its not auto clocking back down. Even the BIOS says 2.4GHz

 

[DaNotoriousDOM]

0.95 only seems to work when I just boot up my PC and start it soon thereafter. If the PC has been running for a while, it will always reboot my system. And yes, it shows the CPU frequency as stock so it doesn't know you overclocked.

 

[DaNotoriousDOM]

Just got 0.96 and it's even worse. Now instead of showing me at 2GHz, it shows me at 1.6GHz. This program is really bad. If I get one more reboot with 0.96 I'm never using it again.

 

[Mithent]

And yes, it shows the CPU frequency as stock so it doesn't know you overclocked.

It's actually showing it as underclocked for a Q6600. 0.95.4 shows the correct speed for my Q6600, anyway.. I've not tried 0.96.

 

[Jay_2]

the multi was set to 8 in the bios (auto)

I set it to 9 and now coretemp shows 2404MHz

Very odd that none of the others picked this up!

 

[DaNotoriousDOM]

My multi isn't on auto. When I overclocked I made sure to turn all those energy saving features off.

 

[Falkentyne]

This is an old problem, as far as I know, but i thought this was fixed.
The author made a post about it, saying that coretemp calculated the frequency by reading some sort of formula or something, but it could fail in certain situations with certain changed multipliers. All I remember clearly is him saying that he doesn't have access to the data that CPU-Z uses to get the 100% correct frequency readout.