bugcheck error 0x0000009E Issues on windows server 2012
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
use !analyze -v detailed debugging information.
bugcheck 9e, {ffffe801a9c3c900, 4b0, 5, 0}
caused : netft.sys ( netft!netftprocesswatchdogevent+e4 )
followup: machineowner
---------
16: kd> !analyze -v
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
user_mode_health_monitor (9e)
1 or more critical user mode components failed satisfy health check.
hardware mechanisms such watchdog timers can detect basic kernel
services not executing. however, resource starvation issues, including
memory leaks, lock contention, , scheduling priority misconfiguration,
may block critical user mode components without blocking dpcs or
draining nonpaged pool.
kernel components can extend watchdog timer functionality user mode
periodically monitoring critical applications. bugcheck indicates
user mode health check failed in manner such graceful
shutdown unlikely succeed. restores critical services by
rebooting and/or allowing application failover other servers.
arguments:
arg1: ffffe801a9c3c900, process failed satisfy health check within the
configured timeout
arg2: 00000000000004b0, health monitoring timeout (seconds)
arg3: 0000000000000005
arg4: 0000000000000000
debugging details:
------------------
process_object: ffffe801a9c3c900
customer_crash_count: 1
default_bucket_id: driver_fault_server_minidump
bugcheck_str: 0x9e
process_name: system
current_irql: 2
last_control_transfer: from fffff800d31e2c08 fffff803585d2fa0
stack_text:
ffffd000`8f4b6938 fffff800`d31e2c08 : 00000000`0000009e ffffe801`a9c3c900 00000000`000004b0 00000000`00000005 : nt!kebugcheckex
ffffd000`8f4b6940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : netft!netftprocesswatchdogevent+0xe4
stack_command: kb
followup_ip:
netft!netftprocesswatchdogevent+e4
fffff800`d31e2c08 cc int 3
symbol_stack_index: 1
symbol_name: netft!netftprocesswatchdogevent+e4
followup_name: machineowner
module_name: netft
image_name: netft.sys
debug_flr_image_timestamp: 5215f788
failure_bucket_id: x64_0x9e_netft!netftprocesswatchdogevent+e4
bucket_id: x64_0x9e_netft!netftprocesswatchdogevent+e4
followup: machineowner
---------
* *
* bugcheck analysis *
* *
*******************************************************************************
use !analyze -v detailed debugging information.
bugcheck 9e, {ffffe801a9c3c900, 4b0, 5, 0}
caused : netft.sys ( netft!netftprocesswatchdogevent+e4 )
followup: machineowner
---------
16: kd> !analyze -v
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
user_mode_health_monitor (9e)
1 or more critical user mode components failed satisfy health check.
hardware mechanisms such watchdog timers can detect basic kernel
services not executing. however, resource starvation issues, including
memory leaks, lock contention, , scheduling priority misconfiguration,
may block critical user mode components without blocking dpcs or
draining nonpaged pool.
kernel components can extend watchdog timer functionality user mode
periodically monitoring critical applications. bugcheck indicates
user mode health check failed in manner such graceful
shutdown unlikely succeed. restores critical services by
rebooting and/or allowing application failover other servers.
arguments:
arg1: ffffe801a9c3c900, process failed satisfy health check within the
configured timeout
arg2: 00000000000004b0, health monitoring timeout (seconds)
arg3: 0000000000000005
arg4: 0000000000000000
debugging details:
------------------
process_object: ffffe801a9c3c900
customer_crash_count: 1
default_bucket_id: driver_fault_server_minidump
bugcheck_str: 0x9e
process_name: system
current_irql: 2
last_control_transfer: from fffff800d31e2c08 fffff803585d2fa0
stack_text:
ffffd000`8f4b6938 fffff800`d31e2c08 : 00000000`0000009e ffffe801`a9c3c900 00000000`000004b0 00000000`00000005 : nt!kebugcheckex
ffffd000`8f4b6940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : netft!netftprocesswatchdogevent+0xe4
stack_command: kb
followup_ip:
netft!netftprocesswatchdogevent+e4
fffff800`d31e2c08 cc int 3
symbol_stack_index: 1
symbol_name: netft!netftprocesswatchdogevent+e4
followup_name: machineowner
module_name: netft
image_name: netft.sys
debug_flr_image_timestamp: 5215f788
failure_bucket_id: x64_0x9e_netft!netftprocesswatchdogevent+e4
bucket_id: x64_0x9e_netft!netftprocesswatchdogevent+e4
followup: machineowner
---------
these ones might help.
https://support.microsoft.com/en-us/kb/2916993
https://support.microsoft.com/en-us/kb/3130902
and if you're debugging one;
regards, dave patrick ....
microsoft certified professional
microsoft mvp [windows server] datacenter management
disclaimer: posting provided "as is" no warranties or guarantees, , confers no rights.
Windows Server > File Services and Storage
Comments
Post a Comment