So you likely ran into a bug, either in the BIOS or active monitor. The problem wasn't with the value, it was the gauge. I wouldn't worry at all unless it recurs and persists across reboot. Then I'd:
1) safe boot & try again.
2) run other monitor software. If they agree then the BIOS is mis-reporting CPU ID. (check for BIOS update?) If other monitor software reports target differently then active monitor is baked.
|