USER_MODE_HEALTH_MONITOR_LIVEDUMP
Code: 0x1c9 (457)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x01c9 (457)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x01c9 (457)
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. |
Description
The USER_MODE_HEALTH_MONITOR_LIVEDUMP live dump has a value of 0x000001C9. It indicates that one or more critical user mode components failed to satisfy a health check.
Cause
One or more critical user mode components failed to satisfy a health check.
Hardware mechanisms such as watchdog timers can detect that basic kernel services are not executing. However, resource starvation issues, including memory leaks, lock contention, and scheduling priority misconfiguration, may block critical user mode components without blocking DPCs or draining the nonpaged pool.
Kernel components can extend watchdog timer functionality to user mode by periodically monitoring critical applications. This livedump indicates that a user mode health check failed in a manner such that we will attempt to terminate this application and will keep monitoring if termination completes in time. If termination does not complete in time, then the machine will be bugchecked It restores critical services by rebooting and/or allowing application failover to other servers.
(This code can never be used for a real bugcheck; it is used to identify live dumps.)
See Also
Troubleshooting a Failover Cluster using Windows Error Reporting
Failover Clustering system log events
Bug Check 0x1C9 USER_MODE_HEALTH_MONITOR
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| ESENT.dll | 0x1c9 | 8.11011 | %1 (%2) %3The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed unless all signatures match. |
| EventCreate.exe | 0x1c9 | 78.11011 | %1 |
| kernel32.dll | 0x1c9 | 1011 | None of the authorized entity elements in the SCCD matched the app being installed; either the PFNs don't match, or the element's signature hash doesn't validate. |
| webservices.dll | 0x1c9 | 78.11011 | The value type (%1) is not valid. |
| 4 entries | |||