HWINFO CPU Core Clock 1MHZ - Minimum Bug or?

[raveya]

Hey there, another point that I noticed, 
what does this here mean:


Current Clock ist 4500MHZ, but sometimes it shows that the CPUs minimum clock on one/two cores is around 1MHZ or 1.8MHZ?

   


or is this just a reading error of HWINFO that can occure?


EDIT:  Debug File added

   

[Martin]

Well, it looks like a reading error. Can you please catch this situation while Debug Mode is enabled and then attach here the resulting HWiNFO64.DBG file for analysis ?

[raveya]

yes, running Prime 95 right now and HWINFO in Debug mode, I will asap upload it then.

File added in main post



  HWiNFO64.DBG (Size: 1.31 MB / Downloads: 0)

[Martin]

It's readout error. Are you maybe running some other monitoring/OC tools together with HWiNFO ? It could be a conflict between them...

[raveya]

Only rivatuner and MSI Afterburner, did you saw in debug log
That it is readout or how do you do?

[Martin]

Can you try to test without MSI Afterburner to see if the issue happen too ?
I'll also try to filter-out such invalid values in the next build of HWiNFO.

[raveya]

closed all these applications.

getting on all 4 cores these reading error bug?

adding a new debug file, maybe you can tell me what that is



  HWiNFO64.DBG (Size: 4.43 MB / Downloads: 1)

[Martin]

It's a bug in BCLK readout, something seems to be interfering with HWiNFO, but I don't know what exactly is that (maybe BIOS, or OS).
I'll try to filter-out such invalid values in the next build of HWiNFO.

[raveya]

ah its ok that you can confirm its a Bug. did other users reported this before?

on my Haswell System it is not happening, there it runs minium never below 4400MHZ.

only on the Skylake System as you saw on the screenshot and the 2 debug files.

thought my CPU is damaged?

[Martin]

Don't worry everything is OK with your system.
It's different on Skylake, because it uses a different method to read the BCLK.

[Martin]

A workaround for this issue has been released in v5.11-2712 Beta.