0.95.4 Misreporting FSB

joesaiditstrue · Post by **joesaiditstrue** » Fri Sep 07, 2007 9:11 am

system in sig, first time poster, but i've been using coretemp for a long time, i love this program :)

i'm actually running 400x8 FSB (3.2), but coretemp reports 450x8, strange as i've never had this problem before

running the vista x64 driver batch file to get CT to run btw, and it works fine

graysky · Post by **graysky** » Fri Sep 07, 2007 9:08 pm

Does it make the same miscalculation after you close it and reopen it? Mine will do something similar every now and then, but it usually gets it right on the 2nd time though.

joesaiditstrue · Post by **joesaiditstrue** » Sun Sep 09, 2007 6:32 pm

yes, closing / reopening does not solve the problem

this thread can be deleted though, as i was able to find some information via search that this is a problem in 0.95.4 and should be fixed soon

Post by **The Coolest** » Thu Sep 13, 2007 10:44 pm

It is a known problem with Core Temp. It uses an obsolete algorithm to detect clock speed, and it is inaccurate at times. A fix is planned, but currently it's not on the top of the priority list.