I'm out of office until Aug-24. Will respond to all requests upon my return. Thanks, Martin

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bus clock value too high on first measurement
#1
When I run sensors Bus Clock based and turn off periodic polling then I often have to restart HWinfo once or twice. The problem is that it very often reads/calculates the bus clock as a few MHz too high (2-3). With periodic polling this also happens, but then is corrected by the next poll.

This is on an AMD Ryzen 1800X + Asus Crosshair VI.
Reply
#2
Unfortunately this is still happening in the latest release, so I have to keep periodic polling active to get proper numbers.
Reply
#3
Yes, it's possible that especially during high system load the bus clock measurement can return values with lower precision.
Reply
#4
But it mostly always happens when HWinfo is started (with periodic polling disabled). I hardly ever get a proper reading from the get go and thus always have to enabled periodic polling at least for a second to get a correct value. So maybe HWinfo should do something like read 3 polls at startup before stopping periodic polling.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)