As for the cause, most likely interference from an another app, which does not implement the mutex to synchronize the hardware accesses. Many of the hardware accesses are indexed and an another app changing the index between HWiNFO specifying the correct index to access and actually reading the data out of it, can and will cause issues such as this.
DDR5 telemetry is read through the SMBUS from the SPDHUB. With an another app changing e.g., the SMBUS address or the index while HWiNFO is reading the data is likely to cause insane readouts such as this one. However, this can affect basically ANY of the monitoring values.
In most cases, the best place to start looking would be any other monitoring, CAM, RGB, etc. tools from third parties or the motherboard manufacturer.
As for the cause, most likely interference from an another app, which does not implement the mutex to synchronize the hardware accesses. Many of the hardware accesses are indexed and an another app changing the index between HWiNFO specifying the correct index to access and actually reading the data out of it, can and will cause issues such as this.
DDR5 telemetry is read through the SMBUS from the SPDHUB. With an another app changing e.g., the SMBUS address or the index while HWiNFO is reading the data is likely to cause insane readouts such as this one. However, this can affect basically ANY of the monitoring values.
In most cases, the best place to start looking would be any other monitoring, CAM, RGB, etc. tools from third parties or the motherboard manufacturer.