Windbg Minidump analyze after server crash

Loading Dump File [E:\Windows\Minidump.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 1) MP (4 procs) Free
x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp1_gdr.070304-2232
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Mon Oct 29 12:15:46.757 2007 (GMT-5)
System Uptime: 7 days 11:15:19.376
Loading Kernel Symbols
.................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*
*
*                        Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f773d2b0, be000000, 20020189}



Probably caused by : intelppm.sys ( intelppm!AcpiC1Idle+12 )

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: f773d2b0
Arg3: be000000
Arg4: 20020189

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
----------------------------------------------------------------
1011111000000000000000000000000000100000000000100000000110001001


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.

MISCV - IA32_MCi_MISC Register Valid
Indicates that the IA32_MCi_MISC register contains additional
information regarding the error.  When clear, this flag indicates
that the IA32_MCi_MISC register is either not implemented or does
not contain additional information regarding the error.

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.

MEMHIRERR - Memory Hierarchy Error   {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_MISCV_ADDRV_PCC_MEMHIRERR_89

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_GenuineIntel

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME:  Idle

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 80a7ebd7 to 8087b71e

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffff808a082c

STACK_COMMAND:  dds 808A082C-0x20 ; kb

STACK_TEXT:
808a080c  00000000
808a0810  808a3600 nt!KiDoubleFaultStack+0x2d50
808a0814  00000000
808a0818  808a35e4 nt!KiDoubleFaultStack+0x2d34
808a081c  00000000
808a0820  00000202
808a0824  00000000
808a0828  f7619ca2 intelppm!AcpiC1Idle+0x12
808a082c  00000000
808a0830  00000000
808a0834  00000000
808a0838  00301d0c
808a083c  00000000
808a0840  00000000
808a0844  00000000
808a0848  00000000
808a084c  00000000
808a0850  00000000
808a0854  00000000
808a0858  00000000
808a085c  00000000
808a0860  00000000
808a0864  00000000
808a0868  00000000
808a086c  00000000
808a0870  00000000
808a0874  00000000
808a0878  00000000
808a087c  00000000
808a0880  00000000
808a0884  00000000
808a0888  00000000


FOLLOWUP_IP:
intelppm!AcpiC1Idle+12
f7619ca2 6a00            push    0

SYMBOL_NAME:  intelppm!AcpiC1Idle+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42435b38

FAILURE_BUCKET_ID:  0x9C_GenuineIntel_intelppm!AcpiC1Idle+12

BUCKET_ID:  0x9C_GenuineIntel_intelppm!AcpiC1Idle+12

Followup: MachineOwner


I'm not able to understand what causes server crash.
Your hint will be appreciated.

Thank you

3 post for a Machine Check Architecture bugcheck.

3 post for a Machine Check Architecture bugcheck.
Really, MCA events are supposed to behave that way.

Please try to update the microcode on your CPU, by upgrading the BIOS ,
and/or the memory modules.
--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Windbg Minidump analyze after server crash

On 10 nov, 00:41, "Ivan Brugiolo [MSFT]"
.
tp://www.microsoft.com/info/cpyright.htm
ee
...-.....................................
***-****
***-****
***-****
***-****
l
l
t
O
US
n

he



ed
he

Please have a look to the following url:
http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/24/484461.aspx
Microsoft kb 941838

Hope this help

Windbg Minidump analyze after server crash

On Nov 7, 10:56 am, bell_sys <bell_...@>

Hey bell_sys,

there is a website that offers on-line analysis of crashdumps /
minidumps. It shows all symbols, call stack, and threads, and the
reason for a crash automatically. although, it has some limitations on
minidump size, but check it out http://www.bugdump.com
I hope that will help you.