Unreally big clock values

Used program for 1 month, but seen this bug for first time (after 11-hour stress-test of RAM, RAM is ok). See picture.

Win7 x64, Ryzen 7 1700, no any overclocking. Standard settings in program.
 

Attachments

This must have been a one-time glitch in the measurement logic, which can sometimes happen on some systems especially under high load.
If you want to avoid such glitches you can disable the "Periodic polling" option in the "CPU Clock Measurement" safety section.
 
Back
Top