HWINFO64 keep Ecore thermal throttle status instead of clearing it on Intel MTL/ARL

zzwu

New Member
The latest beta has the same symptom.

The SW should look at THERMAL_MONITOR_STATUS [0] instead of THERMAL_MONITOR_LOG [1] of MSR 19C.
a. STATUS tells you it the event is current active or not.
b. LOG tells you that the event happened at least once since last time LOG was cleared


hwinfo_ecore_thermal_throttle.jpg
 
With a polling rate of 2000 ms (or even 100 ms) how big would be the chance that software would catch the non-sticky flag? It would miss 99% of short spikes.
Intel is aware of this issue on latest generations, yet haven't provided any clue why it happens.
 
Last edited:
I think the "Current" column should only display the value at the current sampling moment and should not consider events within the sampling interval.
 
Back
Top