Disk Health - Thermal Emergency

UIGeneratedMonitor6b43b94157df464588fcb5f095771903 (UnitMonitor)

At least one disk in the computer has maintained an overheated or critically hot temperature for 3 or more consecutive readings. Continued operation of disks in this state could permanently damage them.

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.

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

Cool the offending disk(s) immediately. Operation at such an extreme temperature, even for just a few minutes or hours can destroy the disk. 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 PriorityHigh
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.SingleEventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Disk Health - Thermal Emergency
Event Description: {0}
RunAsDefault

Source Code:

<UnitMonitor ID="UIGeneratedMonitor6b43b94157df464588fcb5f095771903" Accessibility="Public" Enabled="true" Target="MicrosoftWindowsLibrary6172210!Microsoft.Windows.Computer" ParentMonitorID="AggregateMonitor000add34203e4a45bf54c429e630306e" Remotable="true" Priority="Normal" TypeID="MicrosoftWindowsLibrary6172210!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitor6b43b94157df464588fcb5f095771903_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId0c957d0025f54e918a0aeeeab02c73e8" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIdff135290a9a94738b47fc1c3db6814d1" 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">53856</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>
</Configuration>
</UnitMonitor>