I'm sorry for disagreeing with TMonitor but when you follow the Intel recommended method, neither CPU-Z or TMonitor shows a multiplier that agrees with that method.
Intel® Turbo Boost Technology in Intel® Core™ Microarchitecture (Nehalem) Based Processors
http://download.intel.com/design/pro...ots/320354.pdf
You're right, I don't know how it works. All I know is that at times it displays multiplier information that is completely different from the method that Intel recommends, I have to conclude that it is wrong. What else can I conclude? All that does is mislead users so they have no idea what's right and what's wrong.hum hum, you don't know how TMonitor works, do you?
At least you're willing to admit that CPU-Z is not correct at idle. Everyone trusts that program to be 100% accurate and during some situations, it's not even close to that at idle. Once again, it is misleading and users that don't know how to read through the documentation are left wondering what the truth really is. Do you have any documentation from Intel to support the methods you're using for TMonitor?
Edit: Here's an example of what TMonitor tells me for my T8100.
This CPU presently has EIST disabled. When you disable EIST in a Core 2 based CPU, the CPU gets locked at a fixed frequency. The multiplier reported in MSR 0x198 never changes from idle to full load.
Using Intel's recommended method to determine the multiplier, RealTemp and ThrottleStop correctly show that the CPU is locked at the 11.5 multiplier.
TMonitor is telling me that at idle the multiplier is at 6.0 and when I apply a load to the CPU, the multiplier goes up and down. That's wrong. The multiplier does not change when EIST is disabled. It can't. If you want to argue, that's great but you need to argue with Intel. TMonitor is just as inaccurate when run on Core i CPUs. It draws a nice graph but the information it is graphing is fundamentally wrong and inaccurate so it's pointless. TMonitor would be a very useful tool if it followed Intel's methods but there's no point in telling users that their CPU is doing something that it isn't.




Reply With Quote

Bookmarks