| Previous | Next |
| MACHINE_CHECK_EXCEPTION | DRIVER_POWER_STATE_FAILURE |
USER_MODE_HEALTH_MONITOR
USER_MODE_HEALTH_MONITOR indicates that a critical user-mode component failed its health check and the watchdog could not recover through the nonfatal path.
USER_MODE_HEALTH_MONITOR Parameters
| Parameter | Description |
|---|---|
| 1 | The process that failed to satisfy a health check in the configured time-out |
| 2 | The health monitoring time-out, in seconds |
| 3 | Watchdog source. In combination with process address helps to identify what sub-component has created this watchdog. Values listed below. |
| 4 | Reserved |
VALUES
REM USER_MODE_HEALTH_MONITOR diagnostic command.
0 : WatchdogSourceDefault
Source was not specified
1 : WatchdogSourceRhsCleanup
Monitors that RHS (Resource Hosting Subsystem) process goes away when
terminating on graceful exit
2 : WatchdogSourceRhsResourceDeadlockBugcheckNow
RHS was asked to immediately bugcheck machine
on resource deadlock
3 : WatchdogSourceRhsExceptionFromResource
Resource has leaked unhandled exception from an entry point,
RHS is terminating and this USER_MODE_HEALTH_MONITOR watchdog monitors that
process will go away
4 : WatchdogSourceRhsUnhandledException
Unhandled exception in RHS.
RHS is terminating and this watchdog monitors that
process will go away
5 : WatchdogSourceRhsResourceDeadlock
Monitors that RHS process goes away when
terminating on resource deadlock
6 : WatchdogSourceRhsResourceTypeDeadlock
Monitors that RHS process goes away when
terminating on resource type deadlock
7 : WatchdogSourceClussvcUnhandledException
Unhandled exception in clussvc.
clussvc is terminating and this USER_MODE_HEALTH_MONITOR watchdog monitors that
process will go away
8 : WatchdogSourceClussvcBugcheckMessageRecieved
Another cluster node has sent message asking to bugcheck this node.
9 : WatchdogSourceClussvcWatchdogBugcheck
User mode watchdog has expired and the USER_MODE_HEALTH_MONITOR path created a netft watchdog
to bugchecked the node.
0xA : WatchdogSourceClussvcIsAlive
Cluster service sends heartbeat to netft every 500 milliseconds for USER_MODE_HEALTH_MONITOR.
By default, netft expects at least one heartbeat per second while monitoring USER_MODE_HEALTH_MONITOR.
If this watchdog was triggered, the USER_MODE_HEALTH_MONITOR condition means clussvc is not getting
CPU to send heartbeats.
0x65 : WatchdogSourceRhsResourceDeadlockPhysicalDisk
A subclass of WatchdogSourceRhsResourceDeadlock.
0x66 : WatchdogSourceRhsResourceDeadlockStoragePool
A subclass of WatchdogSourceRhsResourceDeadlock.
0x67 : WatchdogSourceRhsResourceDeadlockFileServer
A subclass of WatchdogSourceRhsResourceDeadlock.
0x68 : WatchdogSourceRhsResourceDeadlockSODAFileServer
A subclass of WatchdogSourceRhsResourceDeadlock.
0x69 : WatchdogSourceRhsResourceDeadlockStorageReplica
A subclass of WatchdogSourceRhsResourceDeadlock.
0x6A : WatchdogSourceRhsResourceDeadlockStorageQOS
A subclass of WatchdogSourceRhsResourceDeadlock.
0x6B : WatchdogSourceRhsResourceDeadlockStorageNFSV2
A subclass of WatchdogSourceRhsResourceDeadlock.
0xC9 : WatchdogSourceRhsResourceTypeDeadlockPhysicalDisk
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCA : WatchdogSourceRhsResourceTypeDeadlockStoragePool
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCB : WatchdogSourceRhsResourceTypeDeadlockFileServer
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCC : WatchdogSourceRhsResourceTypeDeadlockSODAFileServer
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCD : WatchdogSourceRhsResourceTypeDeadlockStorageReplica
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCE : WatchdogSourceRhsResourceTypeDeadlockStorageQOS
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
0xCF : WatchdogSourceRhsResourceTypeDeadlockStorageNFSV2
A subclass of WatchdogSourceRhsResourceTypeDeadlock.
Cause and diagnosis
A critical user-mode process failed to satisfy its health check within the configured timeout. The underlying condition can be a process hang, resource starvation, lock contention, scheduling starvation, or a failure in the subsystem represented by the watchdog source.
Anchor the analysis on Parameter 1 (the monitored process), Parameter 2 (the timeout), and Parameter 3 (the watchdog source). Examine the process and system state at the stop time, then correlate nearby service, cluster, and resource events. Events that precede the bug check are relevant; unrelated generic event-log errors are not evidence of the watchdog cause.
Compare with USER_MODE_HEALTH_MONITOR_LIVEDUMP when available. A preceding live dump can show the same monitored component before recovery failed and the fatal watchdog path was taken.
See Also
Troubleshooting a Failover Cluster using Windows Error Reporting
Failover Clustering system log events
Bug Check 0x1C9 USER_MODE_HEALTH_MONITOR_LIVEDUMP
Looking for a different code? Search another status or error code.