Messages

But it isn't HWiNFO where the error is popping up, it is in TThrottle.  When I look at the temperature trend on HWiNFO for the same sensor, it is "normal".

TThrottle is using the AMD driver, it probably stops recognizes it without a monitor, that's not an uncommon problem.

HWiNFO reads the card more directly.
If HWiNFO is running all the time, TThrottle can interface with HWiNFO and can use it's temperature.

Go to the tab external and check HWiNFO and select the right temperature source.

Actually, this is happening with HWinfo engaged.  I have TThrottle reading the Tctrl/Tdie sensor for the CPU, and the GPU thermal diode for the integrated graphics.

I actually had to install HWinfo and read these sensors because if I don't, the temperature it is "reading" is 0 deg C, constant, with no fluctuation.

I have been running TThrottle on a new computer build recently, and I have noticed that the CPU temperature swings wildly when I am away.  It rises and lowers sharply between ~55 deg C and 0 deg C, probably a few dozen times a minute (I can screen cap when I get home tonight).  I think this happens when the monitor goes to sleep, and I know for sure it does this when I lock the computer.  Once the computer "wakes up", the temperature displays like normal.  Keep in mind, BOINC is running the whole time.

However, I am using HWiNFO to reference the Tctrl temp, and when I graph that temperature it stays in the 50s.  I suspect TThrottle is either getting bad information when my computer turns off the display, or it is having difficulty interpreting the data for some reason.  This does not appear to be affecting throttling or performance of the computer, it just looks weird.

My computer is a Ryzen 3 2200G with a ASRock B450 Pro4 mobo, stock cooler, running Windows 10.  No discrete GPU.