Server Lockup: Where do I start to diagnose?


okay, yesterday main dc/file server spontaneously rebooted. , know why happened , how can prevent in future. i've never seen windows server act @ all.
server hp ml350 g5, quad core intel e5410, single cpu @ 2.33 tghz, 4 gb ram. windows server 2003 r2, standard edition x64, sp2. patches date. ca etrust 8.1.

when came limping badly, wouldn't let me login, kept getting error; "application popup: windows - application error : application failed initialize (0xc0000034). click on ok terminate application."

finally blue screened , powerd server off. when came let me login , seemed okay. has ran little on 15 hours no problems. no new errors.
there plenty of errors in event log none seem definitive initial problem - nothing there @ before dying.

after came there couple of popups , couple of entries in system event log:

event type: error
event source: system error
event category: (102)
event id: 1003
date:  3/19/2009
time:  4:59:54 pm
user:  n/a
computer: decsdc1
description:
error code 000000000000003b, parameter1 00000000c0000005, parameter2 fffff80001295394, parameter3 fffffadf8db989f0, parameter4 0000000000000000.

data:
0000: 53 79 73 74 65 6d 20 45   system e
0008: 72 72 6f 72 20 20 45 72   rror  er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 30 30 30 30 30 30 30    0000000
0020: 30 30 30 30 30 30 30 33   00000003
0028: 62 20 20 50 61 72 61 6d   b  param
0030: 65 74 65 72 73 20 30 30   eters 00
0038: 30 30 30 30 30 30 63 30   000000c0
0040: 30 30 30 30 30 35 2c 20   000005,
0048: 66 66 66 66 66 38 30 30   fffff800
0050: 30 31 32 39 35 33 39 34   01295394
0058: 2c 20 66 66 66 66 66 61   , fffffa
0060: 64 66 38 64 62 39 38 39   df8db989
0068: 66 30 2c 20 30 30 30 30   f0, 0000
0070: 30 30 30 30 30 30 30 30   00000000
0078: 30 30 30 30               0000   

event type: error
event source: system error
event category: (102)
event id: 1003
date:  3/19/2009
time:  5:00:42 pm
user:  n/a
computer: decsdc1
description:
error code 00000000002e067f, parameter1 ffffffffc0000005, parameter2 fffff800011a9eba, parameter3 fffffadf910b0840, parameter4 fffffadf910b0250.

data:
0000: 53 79 73 74 65 6d 20 45   system e
0008: 72 72 6f 72 20 20 45 72   rror  er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 30 30 30 30 30 30 30    0000000
0020: 30 30 30 32 65 30 36 37   0002e067
0028: 66 20 20 50 61 72 61 6d   f  param
0030: 65 74 65 72 73 20 66 66   eters ff
0038: 66 66 66 66 66 66 63 30   ffffffc0
0040: 30 30 30 30 30 35 2c 20   000005,
0048: 66 66 66 66 66 38 30 30   fffff800
0050: 30 31 31 61 39 65 62 61   011a9eba
0058: 2c 20 66 66 66 66 66 61   , fffffa
0060: 64 66 39 31 30 62 30 38   df910b08
0068: 34 30 2c 20 66 66 66 66   40, ffff
0070: 66 61 64 66 39 31 30 62   fadf910b
0078: 30 32 35 30               0250
   

i tried follwing these didn't turn definitive. doesn't appear hardware errors. there no power disruptions (my other server in same power circuits fine). nothing @ obvious.
can please me out in diagnosing this? i'm very, concerned. root of forest, main dc, dns server, file server, print server, etc. did create dump log i've never analyzed before - don't know how start.

dan reynolds
network administrator
bldd architects, inc.


 

hello,

          

    download debugging tools windows package and download requisite symbols os (in case, windows server 2003). should find comprehensive documentations , how-tos  link:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

ttp://support.microsoft.com/kb/315263

http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/

and important thing don't forget see kewwwwwllll video mark russinovich

http://www.microsoft.com/emea/spotlight/sessionh.aspx?videoid=722


syed khairuddin


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file