I disagree with the new method you are using to determine the multiplier. Here's an example.



On a Core 2 mobile CPU when you disable SpeedStep / EIST, the multiplier will get locked at whatever value it is presently at. In the picture, EIST is disabled and the multiplier is locked at 11.5. It doesn't matter whether the CPU is at full load or idle or anywhere in between. The multiplier is locked and is not changing.

The value in Model Specific Register (MSR) 0x198 confirms that the multiplier is at 11.5. The timers you are using may indicate that the CPU is idle which it is but that doesn't mean the multiplier has dropped down to 6.0 because it hasn't. It can't. It's physically impossible when the EIST bit has been disabled.

The method RealTemp and ThrottleStop use is based on the Intel Turbo White Paper.

http://download.intel.com/design/pro...ots/320354.pdf

It recommends that you use the timers in MSR 0x30A and MSR 0x30B and compare those two timers to determine the multiplier. This method is for the Core i7 but it also works very well on most Core 2 CPUs. It doesn't work on the Atom CPUs because the one's that I've seen don't have these timers. This method also needs a slight modification to work correctly on the QX CPUs which ThrottleStop should handle correctly and the next version of RealTemp will get this fix too.

If you are using the MPERF and APERF timers then I don't think that is the best way to determine the actual multiplier. The results go against what is being reported by the method outlined in the Turbo White Paper.

If you need some more information about this method then just ask.