troubleshooting Question

Memory dump on 2003 server

Avatar of kallatech
kallatech asked on
Windows Server 2003Microsoft Legacy OSMicrosoft Server OS
2 Comments1 Solution537 ViewsLast Modified:
This seems to be hardware releated but not 100 percent which piece of hardware.

Please review and let me know
My server has been rebooting on its own it is running now but I don't know for how long.
It has 4 400 gig sata drives and one 250 gig ide drive.
It is running on a gigabyte mb with amd athlon 5300 processor with 1 gig of ram

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) UP Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-2240
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
Debug session time: Mon Jan  5 15:24:14.225 2009 (GMT-5)
System Uptime: 0 days 0:24:50.171
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols

Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 808917a0, b2000000, 70f0f}

Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmStatus+15 )

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

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: 00000004
Arg2: 808917a0
Arg3: b2000000
Arg4: 00070f0f

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:

      - Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
   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
   ----------------------------------------------------------------
   1011001000000000000000000000000000000000000001110000111100001111


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.

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_PCC_BUSCONNERR_30F

   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_AuthenticAMD

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  Idle

CURRENT_IRQL:  9

LAST_CONTROL_TRANSFER:  from 80a54d92 to 80826dc7

STACK_TEXT:  
80891770 80a54d92 0000009c 00000004 808917a0 nt!KeBugCheckEx+0x1b
808918a4 80a4d849 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
808918a4 80a56293 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x71
80894430 f74a894f 0000d402 80894454 f74a89c6 hal!READ_PORT_UCHAR+0x7
8089443c f74a89c6 86753218 8669f89c 8669f898 PCIIDEX!BmStatus+0x15
80894454 f72802b1 86753218 8669f1ac 8669f0e0 PCIIDEX!BmDisarm+0x14
80894478 f7282e1e 0069f898 00000000 8669f1ac atapi!AtapiResetController+0xf9
8089449c 808876a7 0069f028 8669ed02 00000000 atapi!IdeTimeoutSynchronized+0xa8
808944dc 80820740 8669f028 00000000 80820704 nt!KeSynchronizeExecution+0x17
808944f8 8082f402 8089e300 0289e2b4 936f8530 nt!IopTimerDispatch+0x3c
808945b0 8082f8c3 00000000 00000000 0201748a nt!KiTimerExpiration+0x2d0
80894600 80887d97 00000000 0000000e 00000000 nt!KiRetireDpcList+0x65
80894604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x2f


STACK_COMMAND:  kb

FOLLOWUP_IP:
PCIIDEX!BmStatus+15
f74a894f 33c9            xor     ecx,ecx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  PCIIDEX!BmStatus+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  45d69ba4

FAILURE_BUCKET_ID:  0x9C_AuthenticAMD_PCIIDEX!BmStatus+15

BUCKET_ID:  0x9C_AuthenticAMD_PCIIDEX!BmStatus+15

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

Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 2 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros