So what you are saying is Tmonitor reports duty clock speed as opposed to physical clock speed. And duty clock speed is basically activity on cores translated into multi hence mhz. It would be useful to add that explanation to the download site.

So when all cores are at 100% load, the duty clock speed will EQUAL physical clock speed.

If I enable EIST/C states then duty clock speed should still EQUAL physical clock speed, since physical clock will then drop with activity as well as duty clock.

However when I disable EIST/C states, duty clock speed will then NOT EQUAL physical clock speed, since duty clock speed is translating activity into multi, but physical clock speed I locked the multi in place by disabling EIST/C states.

As for the reported values of Tmonitor being closer to what is happening than CPU-Z, that part I would disagree with. Tmonitor is almost nonsensical when turning off EIST/C states, since duty cycle speed is "zeroing" at 12 multi though physical clock speed is not "zeroed" there. I could argue why not report zero activity as 0 mhz ie "0" multi. You could say a 0 multi does not exist, but I could say neither does a 12 multi when EIST/C states are disabled.

thanks for taking the time to explain