Windows server 2012 R2 "0x0000009E" Stop error when cluster node crashes!

-

hello.

please, help solve problem!

the article did not help. the update not installed.

https://support.microsoft.com/en-us/help/3123595/-0x0000009e-stop-error-when-cluster-node-crashes-in-windows-server-2012-r2

memory dump.

bugcheck 9e, {ffffe00049939080, 4b0, 5, 0}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    either specified unqualified symbol, or debugger   ***
***    doesn't have full symbol information.  unqualified symbol      ***
***    resolution turned off default. please either specify   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols typing ".symopt- 100". note   ***
***    enabling unqualified symbol resolution network symbol     ***
***    server shares in symbol path may cause debugger     ***
***    appear hang long periods of time when incorrect      ***
***    symbol name typed or network symbol server down.     ***
***                                                                   ***
***    for commands work properly, symbol path           ***
***    must point .pdb files have full type information.      ***
***                                                                   ***
***    certain .pdb files (such public os symbols) not      ***
***    contain required information.  contact group      ***
***    provided these symbols if need command    ***
***    work.                                                          ***
***                                                                   ***
***    type referenced: netft!netft_watchdog_source                   ***
***                                                                   ***
*************************************************************************
caused : rhs.exe

followup:     machineowner
---------

3: 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: ffffe00049939080, watchdogsourcerhscleanup
monitors rhs process goes away when
terminating on graceful exit
arg2: 00000000000004b0, watchdogsourcerhsresourcedeadlockbugchecknow
rhs asked bugcheck machine
on resource deadlock
arg3: 0000000000000005, watchdogsourcerhsexceptionfromresource
resource has leaked unhandled exception entry point,
rhs terminating , watchdog monitors that
process go away
arg4: 0000000000000000, watchdogsourcerhsunhandledexception
unhandled exception in rhs.
rhs terminating , watchdog monitors that
process go away
5  - watchdogsourcerhsresourcedeadlock
monitors rhs process goes away when
terminating on resource deadlock
6  - watchdogsourcerhsresourcetypedeadlock
monitors rhs process goes away when
terminating on resource type deadlock
7  - watchdogsourceclussvcunhandledexception
unhandled exception in clussvc.
clussvc terminating , watchdog monitors that
process go away
8  - watchdogsourceclussvcbugcheckmessagerecieved
another cluster node has send message asking bugcheck node.
9  - watchdogsourceclussvcwatchdogbugcheck
user mode watchdog has expired , created netft watchdog
to bugchecked node.
10 - watchdogsourceclussvcisalive
cluster service sends heartbeat netft every 500 millseconds.
by default netft expects @ least 1 heartbeat per second.
if watchdog triggered means clussvc o not getting
cpu send heartbers.
101 - watchdogsourcerhsresourcedeadlockphysicaldisk
102 - watchdogsourcerhsresourcedeadlockstoragepool
103 - watchdogsourcerhsresourcedeadlockfileserver
104 - watchdogsourcerhsresourcedeadlocksodafileserver
105 - watchdogsourcerhsresourcedeadlockstoragereplica
106 - watchdogsourcerhsresourcedeadlockstorageqos
107 - watchdogsourcerhsresourcedeadlockstoragenfsv2
values above subclasses of watchdogsourcerhsresourcedeadlock
for resource types known cause rhs termination hangs
we isolate them separate codes can triage dumps.
201 - watchdogsourcerhsresourcetypedeadlockphysicaldisk
202 - watchdogsourcerhsresourcetypedeadlockstoragepool
203 - watchdogsourcerhsresourcetypedeadlockfileserver
204 - watchdogsourcerhsresourcetypedeadlocksodafileserver
205 - watchdogsourcerhsresourcetypedeadlockstoragereplica
206 - watchdogsourcerhsresourcetypedeadlockstorageqos
207 - watchdogsourcerhsresourcetypedeadlockstoragenfsv2
values above subclasses of watchdogsourcerhsresourcetypedeadlock
for resource types known cause rhs termination hangs
we isolate them separate codes can triage dumps.

debugging details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    either specified unqualified symbol, or debugger   ***
***    doesn't have full symbol information.  unqualified symbol      ***
***    resolution turned off default. please either specify   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols typing ".symopt- 100". note   ***
***    enabling unqualified symbol resolution network symbol     ***
***    server shares in symbol path may cause debugger     ***
***    appear hang long periods of time when incorrect      ***
***    symbol name typed or network symbol server down.     ***
***                                                                   ***
***    for commands work properly, symbol path           ***
***    must point .pdb files have full type information.      ***
***                                                                   ***
***    certain .pdb files (such public os symbols) not      ***
***    contain required information.  contact group      ***
***    provided these symbols if need command    ***
***    work.                                                          ***
***                                                                   ***
***    type referenced: netft!netft_watchdog_source                   ***
***                                                                   ***
*************************************************************************

dump_class: 1

dump_qualifier: 401

build_version_string:  9600.18505.amd64fre.winblue_ltsb.160930-0600

system_manufacturer:  microsoft corporation

virtual_machine:  hyperv

system_product_name:  virtual machine

system_sku:  none

system_version:  hyper-v uefi release v1.0

bios_vendor:  microsoft corporation

bios_version:  hyper-v uefi release v1.0

bios_date:  11/26/2012

baseboard_manufacturer:  microsoft corporation

baseboard_product:  virtual machine

baseboard_version:  hyper-v uefi release v1.0

dump_type:  1

bugcheck_p1: ffffe00049939080

bugcheck_p2: 4b0

bugcheck_p3: 5

bugcheck_p4: 0

process_name:  rhs.exe

image_name:  rhs.exe

debug_flr_image_timestamp:  0

module_name: rhs

faulting_module: 0000000000000000 

cpu_count: 4

cpu_mhz: 960

cpu_vendor:  genuineintel

cpu_family: 6

cpu_model: 3e

cpu_stepping: 4

cpu_microcode: 6,3e,4,0 (f,m,s,r)  sig: ffffffff'00000000 (cache) ffffffff'00000000 (init)

default_bucket_id:  win8_driver_fault

bugcheck_str:  0x9e

current_irql:  2

analysis_session_host:  srv-fs0802iq

analysis_session_time:  03-12-2017 11:11:07.0435

analysis_version: 10.0.14321.1024 amd64fre

stack_text:  
ffffd000`4023a968 fffff801`92273468 : 00000000`0000009e ffffe000`49939080 00000000`000004b0 00000000`00000005 : nt!kebugcheckex
ffffd000`4023a970 fffff801`922730f2 : 00000000`00000000 00000000`00000001 ffffd000`40211180 00000000`00000000 : netft!netftprocesswatchdogevent+0xe4
ffffd000`4023a9b0 fffff802`3703f3c8 : ffffd000`4023ab20 00000000`00000000 ffffd000`4023aae0 ffffd000`00000003 : netft!netftwatchdogtimerdpc+0x36
ffffd000`4023a9e0 fffff802`37154eea : ffffd000`40211180 ffffd000`40211180 ffffd000`4021d2c0 ffffe000`4e40c880 : nt!kiretiredpclist+0x4f8
ffffd000`4023ac60 00000000`00000000 : ffffd000`4023b000 ffffd000`40235000 00000000`00000000 00000000`00000000 : nt!kiidleloop+0x5a


stack_command:  kb

thread_sha1_hash_mod_func:  ceabc0ebf1b805b8b961103c5fc0900d75e10ebd

thread_sha1_hash_mod_func_offset:  dab219cd26072518188cc78a3d85e21a6c5740b9

thread_sha1_hash_mod:  bda3626ee178dac7f74a0a80cfdb2e5d00aa032d

followup_name:  machineowner

failure_bucket_id:  0x9e_5_image_rhs.exe

bucket_id:  0x9e_5_image_rhs.exe

primary_problem_class:  0x9e_5_image_rhs.exe

target_time:  2017-03-11t17:11:02.000z

osbuild:  9600

osservicepack:  0

servicepack_number: 0

os_revision: 0

suite_mask:  400

product_type:  3

osplatform_type:  x64

osname:  windows 8.1

osedition:  windows 8.1 server terminalserver datacenter singleuserts

os_locale:  

user_lcid:  0

osbuild_timestamp:  2016-09-30 17:31:28

builddatestamp_str:  160930-0600

buildlab_str:  winblue_ltsb

buildosver_str:  6.3.9600.18505.amd64fre.winblue_ltsb.160930-0600

analysis_session_elapsed_time: 11c4

analysis_source:  km

failure_id_hash_string:  km:0x9e_5_image_rhs.exe

failure_id_hash:  {da7ed50c-f262-0bf6-2893-26474a787be7}

thanks in advance!

hi,

it not efficient analyze such log in forum. suggest open case microsoft, more in-depth investigation can done more satisfying explanation , solution issue.
here link:
https://support.microsoft.com/en-us/gp/contactus81?audience=commercial&wa=wsignin1.0

best regards,
leo

please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authenticati...
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema ...
Read more

Failed to setup initiator portal. Error status is given in the dump data.

-
hi team, server configured boot san  after booting  facing issue windows server 2008 r2 system logs continuously generating iscsi port error event id 5 failed setup initiator portal. error status given in dump data. eventdata \device\raidport1 000004000100000000000000050000c0000000000000000000000000000000000000000000000000070200c0 binary data: in words 0000: 00040000 00000001 00000000 c0000005 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 c0000207 in bytes 0000: 00 00 04 00 01 00 00 00 ........ 0008: 00 00 00 00 05 00 00 c0 .......À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 02 00 c0 ...À hi, please read through article below troubleshoot issue: error event id 5 logged in system log on computer uses iscsi software initiator connect iscsi target device http://suppo...
Read more