Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
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 ?
Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
It's readout error. Are you maybe running some other monitoring/OC tools together with HWiNFO ? It could be a conflict between them...
Posts: 6
Threads: 2
Joined: Dec 2015
Reputation:
0
Only rivatuner and MSI Afterburner, did you saw in debug log
That it is readout or how do you do?
Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
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.
Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
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.
Posts: 6
Threads: 2
Joined: Dec 2015
Reputation:
0
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?
Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
Don't worry everything is OK with your system.
It's different on Skylake, because it uses a different method to read the BCLK.
Posts: 6,524
Threads: 396
Joined: Feb 2010
Reputation:
193
A workaround for this issue has been released in v5.11-2712 Beta.