Disk Health - Thermal Shutdown

UIGeneratedMonitord340fa8ad4184119867975d656c28306 (UnitMonitor)

A computer has shut itself down because one or more disks maintained an overheated or critical temperature for 3 or more consecutive readings.

Knowledge Base article:

Summary

WindowSMART has detected a thermal emergency. At least one disk in the computer has maintained an overheated or critically hot temperature for 3 or more consecutive polling intervals. It is very possible that the disk could be destroyed if it is allowed to continue operating at such an extreme temperature for much longer. Per your configured setting, WindowSMART has shut down the computer to protect the disk(s).

Configuration

WindowSMART will flag a thermal emergency if a disk is overheated or critically hot for 3+ consecutive polling intervals.

Causes

Overheating is typically caused by poor airflow in the computer. Excessive dust, a blocked vent or a failing/failed fan are often causes. If the computer is placed too close to a heat source or in a hot room with poor ventilation, overheating can also occur.

Resolutions

The computer has likely shut down, so the disks should be cooling. Operation at such an extreme temperature, even for just a few minutes or hours can destroy the disk. Before turning on the computer, ensure all vents are free of obstruction and dust, and clean out excessive dust from inside the computer. Ensure the room has adequate ventilation and that no heat sources are too close to the computer.

Additional

N/A

External

N/A

Element properties:

TargetMicrosoft.Windows.Computer
Parent MonitorAggregateMonitor000add34203e4a45bf54c429e630306e
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.SingleEventLogTimer2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Disk Health - Thermal Shutdown
Event Description: {0}
RunAsDefault

Source Code:

<UnitMonitor ID="UIGeneratedMonitord340fa8ad4184119867975d656c28306" Accessibility="Public" Enabled="true" Target="MicrosoftWindowsLibrary6172210!Microsoft.Windows.Computer" ParentMonitorID="AggregateMonitor000add34203e4a45bf54c429e630306e" Remotable="true" Priority="Normal" TypeID="MicrosoftWindowsLibrary6172210!Microsoft.Windows.SingleEventLogTimer2StateMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitord340fa8ad4184119867975d656c28306_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId00ffb7c90aa14104bf629f51d484a0b6" MonitorTypeStateID="TimerEventRaised" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIde6cb1642cdd74a649305e3d624e0471b" MonitorTypeStateID="EventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Property[Type="MicrosoftWindowsLibrary6172210!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">53855</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">TarynHss</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
<TimerWaitInSeconds>7200</TimerWaitInSeconds>
</Configuration>
</UnitMonitor>