Server DL380 G5 shutdown unexprectly

[khanhhoa]

Dear all,
We have one HP DL380 G5 server that is running Windows 2003 Enterprise edition. But lately it was frequently shut down unexpected. When the server was restarted, there is error in system log as follow :

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 4/22/2008
Time: 9:24:27 AM
User: N/A
Computer: CHEMICAL_SVR
Description:
Error code 0000000a, parameter1 00000000, parameter2 d0000002, parameter3 00000001, parameter4 80830126.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 64 30 30 30 30 30 30 32 d0000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 38 33 01, 8083
0050: 30 31 32 36 0126

And also in "HP Proliant Intergrated Management Log viewer" show some error log :

"POST Error: 1785-Drive Array not Configured",POST Messages,Caution,1,12/19/2007 7:10 AM,12/19/2007 7:10 AM
"Network Adapter Link Down (Slot 0, Port 2)",Network Adapter,Critical,3,3/6/2008 1:24 PM,1/8/2008 7:37 AM
"ASR Detected by System ROM",Automatic Server Recovery,Repaired,1,4/1/2008 9:21 AM,3/7/2008 2:28 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Repaired,1,4/1/2008 9:21 AM,3/12/2008 1:41 AM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Repaired,1,4/1/2008 9:21 AM,3/12/2008 6:55 AM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Repaired,1,4/1/2008 9:21 AM,3/12/2008 7:24 AM
"Blue Screen Trap (BugCheck, STOP: 0x00000024 (0x0019033D, 0xB856E6EC, 0xB856E3E8, 0x00000000))",Operating System,Repaired,1,4/1/2008 9:21 AM,3/21/2008 6:24 AM
"ASR Detected by System ROM",Automatic Server Recovery,Repaired,1,4/1/2008 9:21 AM,3/27/2008 10:19 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Repaired,1,4/1/2008 9:21 AM,3/29/2008 4:53 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000008E (0xC0000005, 0x80833CD6, 0xB8028CF0, 0x00000000))",Operating System,Critical,1,4/4/2008 12:35 PM,4/4/2008 12:35 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Critical,1,4/7/2008 12:43 AM,4/7/2008 12:43 AM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x40000024, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Critical,1,4/14/2008 11:19 PM,4/14/2008 11:19 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0x000000FF, 0x00000001, 0x80833CD6))",Operating System,Critical,1,4/17/2008 12:43 AM,4/17/2008 12:43 AM
"ASR Detected by System ROM",Automatic Server Recovery,Critical,1,4/21/2008 9:51 PM,4/21/2008 9:51 PM
"Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x00000000, 0xD0000002, 0x00000001, 0x80830126))",Operating System,Critical,1,4/22/2008 2:36 AM,4/22/2008 2:36 AM

So anyone please help me to solve this problem, it is very urgent
Thank you so much

[James ~ Happy Dude]

Hello,

For Stop code 0xA .. refer:
http://support.microsoft.com/kb/836049
you can request a hotfix.

:) Regards.

[KarloChacon]

hi

check this

http://support.microsoft.com/kb/836049

regards

[KarloChacon]

oh man James

almost at the same time jejje

[khanhhoa]

Dear all,
Thank you for your reply.
But our server is using Windows 2003 SP1 and the hotfix that your provide is just released for Windows 2k3 SP1.
How should I do ?

[KarloChacon]

hi

so your server applies right?


"But our server is using Windows 2003 SP1 and the hotfix that your provide is just released for Windows 2k3 SP1."


???

regards

[khanhhoa]

Yes, it was applied most hotfix and service patch by using window update service

[James ~ Happy Dude]

Hi,
If you are not ready to install the hotfix;
Then Collect the memory dump files & call HP Support; They should guide you after analysis.

;) Regards.




____________________________________________
Yo Karlo !
____________________________________________

[khanhhoa]

Dear all,
I analys my dump file and is says as below, please tell me what should I do ?
Thanks

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols\*.*
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Sun May 18 16:37:54.368 2008 (GMT+7)
System Uptime: 1 days 5:16:14.343
Loading Kernel Symbols
............................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, ff, 1, 80833cd6}

Probably caused by : ntkrnlmp.exe ( nt!KiServiceExit+a2 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80833cd6, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 0

FAULTING_IP:
nt!KiServiceExit+a2
80833cd6 0f84c1000000 je nt!KiSystemCallExit3+0x60 (80833d9d)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xA

PROCESS_NAME: FrameworkServic

TRAP_FRAME: b984acf0 -- (.trap 0xffffffffb984acf0)
ErrCode = 00000002
eax=00000000 ebx=86fe7b40 ecx=00000001 edx=ffffffff esi=86fe7b40 edi=b984ad64
eip=80833cd6 esp=b984ad64 ebp=b984ad64 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006
nt!KiServiceExit+0xa2:
80833cd6 0f84c1000000 je nt!KiSystemCallExit3+0x60 (80833d9d) [br=0]
Resetting default scope

LAST_CONTROL_TRANSFER: from 80833cd6 to 80836de5

STACK_TEXT:
b984acf0 80833cd6 badb0d00 ffffffff 00000001 nt!KiTrap0E+0x2a7
b984ad64 7c8285ec badb0d00 02cdfefc 00000000 nt!KiServiceExit+0xa2
WARNING: Frame IP not in any known module. Following frames may be wrong.
02cdff5c 00000000 00000000 00000000 00000000 0x7c8285ec


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiServiceExit+a2
80833cd6 0f84c1000000 je nt!KiSystemCallExit3+0x60 (80833d9d)

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiServiceExit+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45d6a0af

FAILURE_BUCKET_ID: 0xA_W_nt!KiServiceExit+a2

BUCKET_ID: 0xA_W_nt!KiServiceExit+a2

Followup: MachineOwner
---------

3: kd> .trap 0xffffffffb984acf0
ErrCode = 00000002
eax=00000000 ebx=86fe7b40 ecx=00000001 edx=ffffffff esi=86fe7b40 edi=b984ad64
eip=80833cd6 esp=b984ad64 ebp=b984ad64 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006
nt!KiServiceExit+0xa2:
80833cd6 0f84c1000000 je nt!KiSystemCallExit3+0x60 (80833d9d) [br=0]

[KarloChacon]

hi

previous post in thread you say server has SP1

I would start update to SP2, after that I would reapply HP proliant support pack 8.0 again and test

I think blue screens have too any different flavors (stop codes)

so try that, something else let us know the server configuration I mean
number of Processors, memory dimms, any PCI card, attached to something (tape, storage, ...), power supplies.

thanks