Rainmeter Forums

Having some trouble getting the correct units to display for clock speeds using HWiNFO.

Current code for CPU:
This is the sensor from HWiNFO.


And this is how my dashboard is displaying the sensor readings


Looks to me like the sensor is reading in MHz, but the dashboard is displaying in GHz. Also, the GHz reading is totally wrong as Task Manager is showing 3.xx GHz at idle.

Did you read about the Effective Clock by the HWiNFO autohr? From this explanation, it is normal that the EC value is different from traditional clock values.

And...you are wondering that the value is displayed as GHz, but you have specified by yourself in the line Text=CPU Clock: %1 GHz?

Further, two lines of MinValue and MaxValue are not necessary?

mak_kawa wrote: ↑March 20th, 2020, 9:05 pm And...you are wondering that the value is displayed as GHz, but you have specified by yourself in the line Text=CPU Clock: %1 GHz?

Right, what is seen in the posted image (CPU Clock: 836.43 GHz) is definitely not a value in GHz. So there is a simple solution, just have to replace the GHz in the Text option of the [CPUspeed] meter with MHz: Text=CPU Clock: %1 MHz

Hi Kermit51

If you want to get traditional CPU clock values and their average, you have to get Core X Clock for each core and calculate average from them using Calc measure, such as; Ps. HWiNFO parameters may be different by your hardware.

mak_kawa wrote: ↑March 20th, 2020, 9:05 pm Did you read about the Effective Clock by the HWiNFO autohr? From this explanation, it is normal that the EC value is different from traditional clock values.

And...you are wondering that the value is displayed as GHz, but you have specified by yourself in the line Text=CPU Clock: %1 GHz?

Further, two lines of MinValue and MaxValue are not necessary?

I had not read that. So basically just change it to MHz and assume this read out will never agree to the speed clock in Task Manager.

Kermit51 wrote: ↑March 20th, 2020, 9:49 pm assume this read out will never agree to the speed clock in Task Manager.

I'm not using HWiNFO, so can't say extremely precisely, but I suppose it won't. The plugin and the Task Manager are not reading the values absolutely simultaneously and this can give a small difference between the two values.
Again, this might be wrong, it is just my assumption. Sorry if I am indeed wrong.

Hi balala and Kermit51

The difference between the effective clock and traditional(real) clock is huge. The HWinFO author has explained about it in the thread sited above as;

The Effective frequency does not represent a particular real clock, but the average clock value where sleeping states do not contribute to clock.
So for example when a core is running: 800 MHz, 0 (sleep), 0 (sleep), 0 (sleep)
the average value (effective clock) is: (800 + 0 + 0 + 0) / 4 = 200 MHz

mak_kawa wrote: ↑March 20th, 2020, 10:13 pm The difference between the effective clock and traditional(real) clock is huge. The HWinFO author has explained about it in the thread sited above as;

Yep, make sense...