asked on

MS Server 2003 blue screening.

Hello,
My MS server 2003 box restarted itself randomly over the weekend. Doesn't give much clue why in the event log. I have loaded the memory.dmp into debugger, but doesn't give much clue in there either. Can anyone have a look at the dmp contents?

Many Thanks

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-2240
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Fri May 30 21:25:01.012 2008 (GMT+1)
System Uptime: 2 days 16:20:26.718
WARNING: Process directory table base 67E16000 doesn't match CR3 7FBC1000
WARNING: Process directory table base 67E16000 doesn't match CR3 7FBC1000
Loading Kernel Symbols
...................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 9C, {0, f77352b0, 0, 0}
 
PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
Followup: MachineOwner
---------
 
2: 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: f77352b0
Arg3: 00000000
Arg4: 00000000
 
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
   ----------------------------------------------------------------
   0000000000000000000000000000000000000000000000000000000000000000
 
 
 
 
   Concatenated Error Code:
   --------------------------
   
 
   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.
PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
 
BUGCHECK_STR:  0x9C_GenuineIntel
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
PROCESS_NAME:  inetinfo.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from 80a84154 to 8087c480
 
STACK_TEXT:  
f773d280 80a84154 0000009c 00000000 f773d2b0 nt!KeBugCheckEx+0x1b
f773d3b4 80a7b86f f7737fe0 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
f773d3b4 4edf83fb f7737fe0 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
WARNING: Frame IP not in any known module. Following frames may be wrong.
0af8ff84 00000000 00000000 00000000 00000000 0x4edf83fb
 
 
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_GenuineIntel_ANALYSIS_INCONCLUSIVE
 
BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE
 
Followup: MachineOwner
---------

Open in new window

SOLUTION