58 GHz? I wish!

[shiny_red_cobra]

Using 0.99.7.1 64-bit, I get random readings, some as high as this one! The fsb often changes between 133 and 266, and the multiplier varies between many different values. The CPU is supposed to have a top speed of 2.8GHz, and 1.6GHz idle speed. I just wanna point out that the speeds were shown correctly in version 0.99.5. Ever since then, they have been way off.

[The Coolest]

I was afraid that this was going to happen.
I know what the cause of this problem in general, but at this time, not sure what I have to do to fix it.
I've noticed this on my laptop as well, but after a reboot it went away, so I though it was just a glitch.
Now I see that it isn't, so I'll need to look into it some more.

Thanks for the report.

[The Coolest]

Does the new release work any better?

[shiny_red_cobra]

The new release "sort of" works better. The multiplier is a lot more accurate and it doesn't give those random readings any more, however the bus speed still changes for some reason. Take a look at the screenshot to see what I mean, it still goes to 133 MHz when idle.

[The Coolest]

That is called SLFM.
The Core and Core 2 series' multiplier can only go as low as 6. When your CPU is idle it halves the FSB frequency to reduce clock speed.
For example on my laptop, where the default FSB is 200MHz, 6x200 would result in a too high a frequency for idle, at 6x100 it's too low. My CPU actually increases the multiplier to 8 while halving the FSB to 100. That way I get 100 x 8 = 800MHz, so I'm happy to report that this time, the FSB changing is no mistake/bug of Core Temp
As for the CPU-z shot, it is easier to simply keep reporting the FSB at it's full speed because it can be tricky to get SLFM detection to work correctly 100% and Core Temp is still not perfect in that department, especially when speed goes back up, you may see the FSB double and the multiplier lowered.
But I'm attempting to provide as accurate reading as possible, as much of the time that I can.