Bug 检查 0x9E:USER_MODE_HEALTH_MONITOR
The USER_MODE_HEALTH_MONITOR Bug 检查的值为 0x0000009E。 此 Bug 检查表明一个或多个关键用户模式组件未能满足运行状况检查。
重要
这篇文章适合程序员阅读。 如果您是在使用计算机时收到蓝屏错误代码的客户,请参阅蓝屏错误疑难解答。
USER_MODE_HEALTH_MONITOR 参数
参数 | 说明 |
---|---|
1 | 在配置的超时时间中未能满足运行状况检查的进程 |
2 | 运行状况监视超时,以秒为单位 |
3 | 监视程序源。 结合进程地址有助于识别已创建此监视器的子组件。 其值如下所列。 |
4 | Reserved |
VALUES
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 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 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 created netft watchdog to bugchecked the node. 0xA : WatchdogSourceClussvcIsAlive Cluster service sends heartbeat to netft every 500 milliseconds. By default, netft expects at least 1 heartbeat per second. If this watchdog was triggered that 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.
原因
硬件机制(如监视器计时器)可以检测到基本内核服务未执行。 但是,资源不足问题(包括内存泄漏、锁争用和计划优先级配置错误)可能会阻止关键的用户模式组件,而不会阻止延迟的过程调用 (DPC) 或耗尽非分页池。
内核组件可以通过定期监视关键应用程序将监视器计时器功能扩展到用户模式。 此 Bug 检查表明用户模式运行状况检查失败,从而阻止了正常关闭。 此 Bug 检查通过重启或启用应用程序故障转移到其他服务器来恢复关键服务。
与所有 Bug 检查一样,使用系统事件日志及时查找停止代码之前的事件。 应检查日志中立即执行 Bug 检查的事件,了解可能的原因。