Hallo Leute kann mir Bitte einer behilflich sein?
Wir haben bei einem Kunden das Problem das der eine neue Software entwickelt hat und seit dem diese Software verwendet wird friert das System immer ein!
Allerdings soll das ganze laut dem Kunde ein Speicherfehler oder ähnliches sein!
Folgende Dump Datei wurde mir zugesendet, ich kann damit aber leider überhaupt garnichts anfangen! Evtl. hängt es mit der intelppm.sys zusammen? Aber was löst den freeze aus?
Können mir evtl. Intel, der Mainboardhersteller (Supermicro) oder Speicerhersteller helfen?
Vielen Dank schonmal
MfG
************************************************************************************************************************************************
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\__Marktplatz__\Temp\100929_ORL412_LOGS\DumpFiles\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0xe0ba3000 PsLoadedModuleList = 0xe0c29720
Debug session time: Mon Sep 27 16:34:08.171 2010 (GMT+2)
System Uptime: 1 days 9:07:53.188
WARNING: Process directory table base 00176000 doesn't match CR3 08780020
WARNING: Process directory table base 00176000 doesn't match CR3 08780020
Loading Kernel Symbols
...............................................................
......................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, f62c4050, b2000000, a0000800}
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+2162 )
Followup: MachineOwner
---------
1: 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: f62c4050
Arg3: b2000000
Arg4: a0000800
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
----------------------------------------------------------------
1011000111111111111111111111111110100000000000000000100000000000
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.
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_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_GenuineIntel
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from e0b87bfb to e0bc5f33
STACK_TEXT:
f62c4028 e0b87bfb 0000009c 00000000 f62c4050 nt!KeBugCheckEx+0x1b
f62c4154 e0b82c52 f62c0d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
f62c4154 f62a2162 f62c0d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a
WARNING: Stack unwind information not available. Following frames may be wrong.
f645bd50 e0c11d3c 00000000 0000000e 00000000 intelppm+0x2162
f645bd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm+2162
f62a2162 6a00 push 0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: intelppm+2162
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025183
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_intelppm+2162
BUCKET_ID: 0x9C_GenuineIntel_intelppm+2162
Followup: MachineOwner
---------
************************************************************************************************************************************************[
Wir haben bei einem Kunden das Problem das der eine neue Software entwickelt hat und seit dem diese Software verwendet wird friert das System immer ein!
Allerdings soll das ganze laut dem Kunde ein Speicherfehler oder ähnliches sein!
Folgende Dump Datei wurde mir zugesendet, ich kann damit aber leider überhaupt garnichts anfangen! Evtl. hängt es mit der intelppm.sys zusammen? Aber was löst den freeze aus?
Können mir evtl. Intel, der Mainboardhersteller (Supermicro) oder Speicerhersteller helfen?
Vielen Dank schonmal
MfG
************************************************************************************************************************************************
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\__Marktplatz__\Temp\100929_ORL412_LOGS\DumpFiles\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0xe0ba3000 PsLoadedModuleList = 0xe0c29720
Debug session time: Mon Sep 27 16:34:08.171 2010 (GMT+2)
System Uptime: 1 days 9:07:53.188
WARNING: Process directory table base 00176000 doesn't match CR3 08780020
WARNING: Process directory table base 00176000 doesn't match CR3 08780020
Loading Kernel Symbols
...............................................................
......................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, f62c4050, b2000000, a0000800}
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+2162 )
Followup: MachineOwner
---------
1: 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: f62c4050
Arg3: b2000000
Arg4: a0000800
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
----------------------------------------------------------------
1011000111111111111111111111111110100000000000000000100000000000
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.
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_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_GenuineIntel
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from e0b87bfb to e0bc5f33
STACK_TEXT:
f62c4028 e0b87bfb 0000009c 00000000 f62c4050 nt!KeBugCheckEx+0x1b
f62c4154 e0b82c52 f62c0d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
f62c4154 f62a2162 f62c0d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a
WARNING: Stack unwind information not available. Following frames may be wrong.
f645bd50 e0c11d3c 00000000 0000000e 00000000 intelppm+0x2162
f645bd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm+2162
f62a2162 6a00 push 0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: intelppm+2162
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025183
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_intelppm+2162
BUCKET_ID: 0x9C_GenuineIntel_intelppm+2162
Followup: MachineOwner
---------
************************************************************************************************************************************************[
