| Previous | Next |
| MANUALLY_INITIATED_POWER_BUTTON_HOLD | HYPERVISOR_WATCHDOG_TIMEOUT |
USER_MODE_HEALTH_MONITOR_LIVEDUMP
The USER_MODE_HEALTH_MONITOR_LIVEDUMP bug check has a value of 0x000001C9. It indicates that one or more critical user mode components failed to satisfy a health check.
USER_MODE_HEALTH_MONITOR_LIVEDUMP Parameters
| Parameter | Description |
|---|---|
| 1 | Process that failed to satisfy a health check within the configured timeout. |
| 2 | Health monitoring timeout (seconds). |
| 3 | Watchdog source. In combination with process address this helps to identify the source. See below for possible values. These values are shared with USER_MODE_HEALTH_MONITOR. |
| 4 | Reserved. |
Watchdog Source Values
REM USER_MODE_HEALTH_MONITOR_LIVEDUMP diagnostic command.
0 : WatchdogSourceDefault
Source was not specified
1 : WatchdogSourceRhsCleanup
Monitors that RHS 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_LIVEDUMP 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_LIVEDUMP 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_LIVEDUMP 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_LIVEDUMP.
By default, netft expects at least one heartbeat per second while monitoring USER_MODE_HEALTH_MONITOR_LIVEDUMP.
If this watchdog was triggered, the USER_MODE_HEALTH_MONITOR_LIVEDUMP 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
This live dump is captured when a critical user-mode component misses its configured health check. Resource starvation, lock contention, scheduling problems, or a component-specific hang can prevent the monitored process from responding even while kernel watchdog activity continues.
Use Parameter 1 to identify the monitored process, Parameter 2 for the timeout, and Parameter 3 for the watchdog source. Correlate those values with the process dump state, cluster or service events, and resource usage from the same interval. The watchdog source is more useful than a generic restart recipe because it identifies which health-monitoring path declared the component unhealthy.
USER_MODE_HEALTH_MONITOR_LIVEDUMP identifies a live-dump record; it is not itself evidence that Windows stopped. If recovery or termination later fails and a fatal watchdog path is taken, analyze that stop separately rather than treating this live dump as the crash.
See Also
Troubleshooting a Failover Cluster using Windows Error Reporting
Failover Clustering system log events
Bug Check 0x1C9 USER_MODE_HEALTH_MONITOR
Looking for a different code? Search another status or error code.