BugCheck, Stop: 0x0000009c [DUMP Data]

Hello,

I have a W2003 server that reboots itself every night. The time it reboots is not the same every time. I see the following Stop error:

Blue Screen Trap (BugCheck, Stop: 0x0000009c (0x000000000, 0xE08A07A0, 0xB6606000, 0x22000800))

The server is an HP DL380 G2

I would greatly appreciate any help with this issue. I am attaching the last memory dump.

Thank you in advance for your help.


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


Loading Dump File [C:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols;c:\windows\symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0xe0800000 PsLoadedModuleList = 0xe08af988
Debug session time: Mon Mar 26 22:37:14.265 2007 (GMT-7)
System Uptime: 0 days 11:04:34.984
WARNING: Process directory table base 81DFD000 doesn't match CR3 8FC41000
WARNING: Process directory table base 81DFD000 doesn't match CR3 8FC41000
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = bd7db00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, e08a07a0, b6606000, 22000800}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: e08a07a0
Arg3: b6606000
Arg4: 22000800

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011011001100000011000000000000000100010000000000000100000000000


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_ADDRV_PCC_BUSCONNERR_0

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_IA32_GenuineIntel

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: sqlservr.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from e0a7ebd8 to e087b6be

STACK_TEXT:
e08a0770 e0a7ebd8 0000009c 00000000 e08a07a0 nt!KeBugCheckEx+0x1b
e08a08a4 e0a7686f e0042000 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
e08a08a4 004079e8 e0042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
WARNING: Frame IP not in any known module. Following frames may be wrong.
04f7e448 00000000 00000000 00000000 00000000 0x4079e8


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_IA32_GenuineIntel_ANALYSIS_INCONCLUSIVE

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

 

Try upgrading to service pack 2 for windows 2003 server.
I have the same problem and I have the same exact server as well as an HP dl580 G2. Service packs did the trick for some reason.

If the problem persists, the proglem could be somewhere in the OS itself (unlikely) Or it could be the memory, hard drives (depending on how your raid is setup) or the raid controller itself.

 

Bugcheck code 9C is hardware error. According to the bugcheck parameter 4 and it is BUSCONNER error.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err

These errors match the format 0000 1PPT RRRR IILL

For your problem they all zero (ie _VAL_UC_EN_ADDRV_PCC_BUSCONNERR_0)

PP 00 Local node originated the request (SRC)
T 0 did not time out
RRRR 0000 Generic error (GEN) when the error cannot be determined
II 00 Memory access (MEM)
LL 00 Level 0

It means your PC encounter undetermined memory access error at Level 0 memory.

Probably it is compatibility problem between M/B or RAM. Do you use mix ram? You had better run memtest to stress test the RAM.