HP Rx2660 ia64 machine BSOD on Plug and Play Device test under Server2008R2 ia64

-

does find same issue?
======================
whea_uncorrectable_error (124)
a fatal hardware error has occurred. parameter 1 identifies type of error
source reported error. parameter 2 holds address of the
whea_error_record structure describes error conditon.
arguments:
arg1: 0000000000000009, itanium machine check abort
arg2: e000012662ad6028, address of whea_error_record structure.
arg3: 0000000000000000, length in bytes of sal log.
arg4: 0000000000000000, address of sal log.

additional_debug_text: 
use '!findthebuild' command search target build information.
if build information available, run '!findthebuild -s ; .reload' set symbol path , load symbols.

faulting_module: e000000088110000 nt

debug_flr_image_timestamp:  0

bugcheck_str:  0x124_9

default_bucket_id:  vista_driver_fault

current_irql:  0

stack_text: 
e0000126`61cb67c0 e0000126`61cba680 e0000000`88423700 : 00000000`00000124 e0000000`88663288 e0000126`61cb6804 e0000000`88663280 : nt!ntshutdownsystem+0x302b40
e0000126`61cb7320 e0000126`61cba648 e0000000`880a3150 : 00000000`00000124 00000000`00000009 e0000126`62ad6028 00000000`00000000 : nt!ntshutdownsystem+0x303f10
e0000126`61cb7320 e0000126`61cba5d8 e0000106`02015460 : 00000000`00000000 e0000126`62ad6028 00000000`00000000 00000000`00000000 : hal!halinitsystem+0x1db40
e0000126`61cb7320 e0000126`61cba5b0 e0000000`884af460 : e0000126`62638c89 e0000126`62ad6028 e0000000`884af460 00000000`00000998 : pshed!pshedregisterplugin+0x12d0
e0000126`61cb7320 e0000126`61cba518 e0000000`880a4d40 : e0000126`61cc2000 00000000`00000000 e0000126`62638c30 e0000126`62ad6000 : nt!ntshutdownsystem+0x38fc70
e0000126`61cb7330 e0000126`61cba4b8 e0000000`880f5940 : 00000000`00000000 00000000`00000000 e0000126`61cc2011 e0000126`61cc2000 : hal!halinitsystem+0x1f730
e0000126`61cb7330 e0000126`61cba328 e0000000`880c3d80 : e0000126`61ccc000 e0000126`61cb7e20 00000000`00000000 e0000126`61cb7340 : hal!halfpemulate+0x113c8
e0000126`61cb7340 e0000126`61cba328 e0000106`0c2a9740 : e0000126`61ccc000 e0000126`61cb7e20 00000000`00000000 e0000126`61cb7340 : hal!halinitsystem+0x3e770
e0000106`06651ac0 e0000106`06652a40 e0000106`0c2792e0 : e0000126`62ea03b8 e0000126`62ea08b8 e0000106`06651a10 e0000126`62ea0898 : b57nd60i+0x4b740
e0000106`06651ad0 e0000106`06652930 e0000106`0c280680 : e0000106`06651680 00000000`7fffffff 00000000`00000011 e0000126`638ee750 : b57nd60i+0x1b2e0
e0000106`06651ae0 e0000106`066528c0 e0000106`022c5100 : e0000126`637e1420 e0000106`03585330 00000000`00000b1b e0000000`887a0000 : b57nd60i+0x22680
e0000106`06651ae0 e0000106`066527c8 e0000106`021ae6b0 : e0000126`62ea01b0 00000000`00000000 e0000126`62e766f0 e0000126`62e76738 : ndis!ndissendnetbufferlists+0x53e00
e0000106`06651b30 e0000106`06652738 e0000106`021c4810 : 00000000`00000000 e0000126`62e766f0 00000000`00000001 00000000`00000000 : ndis+0x86b0
e0000106`06651b30 e0000106`066526d0 e0000106`040b65b0 : e0000126`629d3890 e0000126`62e766f0 ffffffff`c0000001 00000000`000000ec : ndis+0x1e810
e0000106`06651bb0 e0000106`06652680 e0000106`022c46c0 : e0000126`62c585b0 e0000126`62ab8240 00000000`00000103 e0000126`62c585d8 : pacer+0x125b0
e0000106`06651bc0 e0000106`066525f0 e0000106`021ae2d0 : e0000126`629d3890 e0000000`ffff0b20 e0000126`629d3a98 e0000126`629d38a8 : ndis!ndissendnetbufferlists+0x533c0
e0000106`06651c30 e0000106`06652560 e0000106`021c4810 : 00000000`00000000 e0000126`62ab8240 00000000`00000001 e0000126`629d3890 : ndis+0x82d0
e0000106`06651c30 e0000106`066524f8 e0000106`05028fd0 : e0000126`629bec70 e0000126`62ab8240 ffffffff`c0000001 00000000`000000ec : ndis+0x1e810
e0000106`06651cb0 e0000106`06652498 e0000106`022c46c0 : e0000126`6203fc00 e0000106`06651dc0 e0000126`6203fc18 e0000106`06651dc4 : wfplwf+0x2fd0
e0000106`06651cc0 e0000106`06652410 e0000106`021aec20 : e0000126`629bec70 e0000000`ffff0b20 e0000126`629bee78 e0000126`629bec88 : ndis!ndissendnetbufferlists+0x533c0
e0000106`06651d30 e0000106`06652368 e0000106`0234ac90 : e0000126`62ea01b0 e0000106`06651dc0 00000000`00000000 e0000126`629bec70 : ndis+0x8c20
e0000106`06651d30 e0000106`066522e8 e0000106`02348040 : e0000126`62a7a800 e0000106`06651dc0 e0000126`62ea01b0 e0000106`06651e28 : ndis!ndissendnetbufferlists+0xd9990
e0000106`06651db0 e0000106`066522c0 e0000106`05091230 : e0000126`62a7a800 e0000106`06651dc0 e0000106`05091230 00000000`00000c9e : ndis!ndissendnetbufferlists+0xd6d40
e0000106`06651db0 e0000106`066521f0 e0000106`05190610 : e0000106`06651dc2 00000000`00000001 00000000`01010103 00000000`00000000 : tcpip+0x55230
e0000106`06651ed0 e0000106`066521c8 e0000106`0518fc10 : e0000126`629d0d40 e0000126`629d1040 e0000106`0535b0e8 e0000106`0518fc10 : tcpip+0x154610
e0000106`06651ee0 e0000106`06652190 e0000000`886c5a80 : e0000126`62ccc0c0 e0000126`629d0d40 e0000126`62ccc0d0 e0000126`629d0d98 : tcpip+0x153c10
e0000106`06651f00 e0000106`06652168 e0000000`8815d670 : e0000126`629d2210 e0000126`625697f0 e0000000`8815d670 00000000`00000fa5 : nt!kibugcheckdata+0x62800
e0000106`06651f00 e0000106`06652070 e0000000`886846e0 : 00000000`00000000 e0000126`61d3c6f0 e0000106`06651f30 e0000000`ffff0b20 : nt!ntshutdownsystem+0x3de80
e0000106`06651f30 e0000106`06652010 e0000000`88228d60 : e0000000`8811f828 00000000`00000001 e0000106`06651f40 e0000126`61d3c6f0 : nt!kibugcheckdata+0x21460
e0000106`06651f50 e0000106`06652000 00000000`00000000 : 00000000`00000000 00000000`00000000 e0000000`8811f828 00000000`00000001 : nt!ntshutdownsystem+0x109570


stack_command:  kb

followup_name:  machineowner

module_name: hardware

image_name:  hardware

bucket_id:  wrong_symbols

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

hi vincent


according description, seems server crash issue, may need analyze crash dump file analysis root cause of issue. please contact microsoft customer service directly memory dump file can analyzed , issue can resolved efficiently.

 

you may obtain phone numbers specific technology request please take @ web site listed below:

 

https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1

 

for reference:

 

here steps temporally make system not automatically restart when issue occurs.

 

steps.

 

1. right-click "my computer" , select "properties" on desktop

2. click on "advanced"

3. click "settings" in area of "startup , recovery"

4. in prompt dialog box, uncheck "automatically restart" in area of "system failure"

5. click ok.

 

thanks understanding.

sainath !analyze


Windows Server  >  Windows Server General Forum



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

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering ...
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