No. While the CPU is operating C-States greater than C0 the clock will be stopped and not running at all. Higher than C1 and power saving measures will be taken. When the CPU is woken it is at the LFM and it takes time for the voltage to ramp up before it can switch to the higher clocks. So if CPU-z polls the CPU while in the higher C-State then it reads the LFM before the clock has increased. Latency can be reduced with fixed voltage.
Try this for W7. Open an admin cmd box and enter the following 2 lines.
Code:
powercfg -setacvalueindex scheme_max sub_processor 5d76a2ca-e8c0-402f-a133-2158492d58ad 1
powercfg -s scheme_max
You can cut and paste to make it easier. This will disable all C-States including C1 (not the same as C1E) so expect high idle temps. Your clocks at idle workload should be maximum 100% unless you have changed the Windows high performance power plan minimum processor state from 100%. To go back to standard enter the 2 commands again but change the 1 to a 0.
If while in this state with heavy load your clocks are dropping to 16x then it is most likely Bi-Directional PROCHOT that is causing it.