Ryzen 99c in Core Temp 1.17.1

[iron-horse]

Hey all,
I wanted to hit up the brains trust. Today I fired up my pc, to be greeted by a prompt to restart my pc due to a Trend Micro update that I'd delayed on last use, so I said yes. In those seconds before it restarted, I noticed in my system tray that my CPU (Ryzen 3600 with a NOCTUA NH-12) was allegedly at 99c. This meant I had no time to compare it to another monitoring program. As it restarted I entered bios where it was 37c. Now, I know the bios doesn't load the CPU so it will naturally drop. Fortunately the low bios temp tells me that it's not a heatsink issue.

I have logging enabled on core temp and the log is blank!
https://ibb.co/DKnP4Mw
Compare this with the log it created after the next reboot:
https://ibb.co/TKHD0ST
.
My thinking is that it's a glitch for the following reasons:
- It has given a blank log, and the pc went through a clean shutdown and restart, so the log is not corrupted.
- I have core temp set to initiate a warning/shutdown if it gets to a certain temperature, and it didn't.
- Windows didn't appear to be doing anything in the background, given it had just booted up and was sitting at the desktop, but as I noticed it when I hit restart, I didn't have time to consult task manager. PC was completely responsive.

Would it be fair to say that it glitched?

[The Coolest]

This issue was solved in 1.18.

[iron-horse]

After the issue, I realised there was an update and installed 1.18.

So, was this behaviour of a false temperature and a blank log a known issue?

Thanks

[The Coolest]

Wrong temp, yes. Not quite sure why the log is empty.
The log only writes once every 10 seconds, unless you modify that in the settings.

[iron-horse]

I have had it happen before about a year ago where it said my cpu was 91 and 101c, but Ryzen Master said it in its mid 40s - 50s and closing and opening Core Temp fixed it.

The system gave me no reason to believe it was that hot. I did not change the poll time for logging.

Unfortunately, this time around I can't say with absolute certainty that it was incorrect as I didn't have the ability to check with another tool, as I only noticed it as I rebooted it.
If we couple that the desrcibed behaviour and its inability to write a log, it sounds to me as if CT has crashed or errored...?