Bellringer
Lieutenant
- Registriert
- Mai 2006
- Beiträge
- 803
Hi
Hab seit einigen Wochen ein BSOD mit Machine_Check_Exception.
Hab mal das Dump-File ausgewertet.
Ich weiß echt nicht mehr weiter.
Habe schon alles mögliche ausprobiert.
Was meint ihr zu der Auswertung? Vielleicht werdet ihr draus schlauer.
[Edit]
Sorry, hier noch mein System:
Core 2 Duo E6400
Asus P5NSLI
250GB Samsung IDE-HD
MSI 7900 GTO
2 GB GeIL DDR2-800mhz Ram im DualChannel
Win XP Prof SP2
Hab seit einigen Wochen ein BSOD mit Machine_Check_Exception.
Hab mal das Dump-File ausgewertet.
Ich weiß echt nicht mehr weiter.
Habe schon alles mögliche ausprobiert.
Was meint ihr zu der Auswertung? Vielleicht werdet ihr draus schlauer.
[Edit]
Sorry, hier noch mein System:
Core 2 Duo E6400
Asus P5NSLI
250GB Samsung IDE-HD
MSI 7900 GTO
2 GB GeIL DDR2-800mhz Ram im DualChannel
Win XP Prof SP2
Code:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini122906-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Dec 29 21:09:08.812 2006 (GMT+1)
System Uptime: 0 days 0:05:19.525
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, bab44050, b2000040, 800}
Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+14 )
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: bab44050
Arg3: b2000040
Arg4: 00000800
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
----------------------------------------------------------------
1011001000000000000000000100000000000000000000000000100000000000
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_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
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 806e8bff to 804f9c37
STACK_TEXT:
bab44028 806e8bff 0000009c 00000000 bab44050 nt!KeBugCheckEx+0x1b
bab44154 806e3c52 bab40d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
bab44154 80544d30 bab40d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a
bacd7d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x14
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiIdleLoop+14
80544d30 90 nop
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e
SYMBOL_NAME: nt!KiIdleLoop+14
FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KiIdleLoop+14
BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KiIdleLoop+14
Followup: MachineOwner
---------
Zuletzt bearbeitet:
