Right, it seems like the forums had a bit of a lie down and forgot some stuff (including my entire account, as I’d only just registered…). So I’m going to post something that’s probably similar to what I posted before, but obviously I can’t recall this one-for-one.
Basically, I have the same issue as @BeepBoopImAComputa. My Gigabyte X570 I motherboard also has some sensors that always read as 16.8°C with a cutoff at 20.8°C, and sometimes when resuming from suspend these sensors get tripped. As the room the computer is in is typically at 21°C, a quick check on the rules of thermodynamics suggest that the 16.8°C being reported is unlikely to be a real temperature. Further, while it was for a different issue, I notice that a user on the L1Techs forum posted a log for their Gigabyte X50 Aorus Master with the same temperature/critical values reported in 2020 (edited once I regained link privileges).
Therefore, all things considered, I think this is likely to be a quirk of the Gigabyte X570 platform. Perhaps some places where thermistors were supposed to be just have resistors on them? Who knows.
On my machine, it should be possible to disable the offending behaviour by running
echo disabled > /sys/class/thermal/thermal_zone1/mode
as root. From the logs, this should also work for @BeepBoopImAComputa. For others, you should check which thermal_zone triggers the critical temperature error in the logs and update the command accordingly.
Note that this command has some risk attached to using it - it relies on this error actually being a hardware quirk rather than actual overheating of some component. If it’s the latter, disabling the protection could cause a problem. Further, I can’t verify that it’s a guaranteed fix, as for me the behaviour is quite intermittent.
In terms of why this behaviour isn’t more widely known, it’s probably because it does not manifest on Ubuntu, or at least when I was using it. This likely means that either Ubuntu knows about this behaviour and has patched it out themselves, or there is some difference between Ubuntu and Manjaro (for example, Manjaro using a newer kernel version) that causes the problem to manifest on Manjaro.