Windows – How to log a shutdown caused from overheating or overheated components

On a Windows 7 SP1 machine, I would like to know how I could reliably log a shutdown that was caused exclusively from overheated components of the machine.

Since the component that overheats must send some sort of command to the computer in order to shut it down, I would like to be able to view and log every time this command is issued upon turning the machine on again.

If possible, it would be great to see in the log what component of the machine sent the shutdown command, so that further action can be taken. Already having a confirmation that the shutdown procedure was initiated from an overheated component would be a start.

Is this particular kind of event (overheated component -> shut down machine) logged at all, or is there only an event with approximate description that unfortunately does not give a clear indication of the reason for the shutdown?

I have found a similar question here:
https://serverfault.com/questions/415931/how-to-determine-if-the-last-shutdown-was-due-to-power-failure-in-windows

EventID 41 Kernel-Power: The system has rebooted without cleanly
shutting down first. This error could be caused if the system stopped
responding, crashed, or lost power unexpectedly.

Though EventID 41 Kernel-Power does not mention overheating and I am not looking for an unexpected loss of power.

I am also not looking for methods or procedures that could lead to an elimination of overheating. I am also not looking to discuss causes for overheated components. I am really looking for some kind of log that clearly tells me that the shut down procedure was initiated from an overheated component.

If such kind of event log or other kind of log cannot be given, I am interested to hear what other events could approximately indicate that the shut down procedure was most possibly initiated from an overheated component.

If there is software that can log such kind of events (overheated component -> shut down) on a Windows machine besides the Event Log (if Event Log can do this at all), I would like to read about it. I am not interested in temperature monitoring software like RealTemp unless there is a clear log produced that clearly indicates, for example, "component xyz has reached critical temperature and has initiated the system shut down command".

Before posting this, I have read the following similar questions:

• Is it possible to make the motherboard log instant random shutdowns?
• How does Windows 7 determine that a system was not shut down correctly (Kernel-Power Event ID 41)
• Why are there so many unexpected shutdowns in the event log?

I have also made sure to check other sites and sources for a solution to this question and found nothing that clearly indicates a shut down was initiated from an overheated component.