https://forum.rainmeter.net/viewtopic.php?t=19516
However, it seems there is one value that does read correctly...sort of.
http://superuser.com/questions/256921/what-does-the-maximum-frequency-number-mean-in-the-windows-resource-monitor
So if you simply multiply the % maximum frequency by the stock frequency we should get the real frequency.
Code: Select all
[MeasureCPURegistry]
Measure=Registry
RegHKey=HKEY_LOCAL_MACHINE
RegKey=HARDWARE\DESCRIPTION\System\CentralProcessor\0
RegValue=~MHz
[MeasureFrequency]
Measure=Plugin
Plugin=Plugins\PerfMon.dll
PerfmonObject="Processor Information"
PerfmonCounter="% of Maximum Frequency"
PerfmonInstance="0,0"
PerfmonDifference=0
[MeasureCPUMHz]
Measure=Calc
Formula=MeasureFrequency*MeasureCPURegistry/100
I'm guessing it's an issue with update rates. I tried a quick stress test and while resource monitor is displaying the maximum frequency increasing accurate to the OC, no change is being displayed on the skin or performance monitor. I guess that means the post in superuser is wrong. Maybe Maximum Frequency in Resource Monitor is not the same as % of Maximum Frequency in Performance Monitor, so what is? I double checked all the instances under "% of Maximum Frequency" & "Frequency" to be sure, and none of them actually displayed any fluctuations when the clock increased.