Guten Morgen,
bis nach 22 Uhr ist der Rechner gestern ohne Probleme gelaufen. Heute früh ca. 15 Minuten nach dem Booten im Leerlauf der nächste BSOD:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\082912-20685-01.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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e93e90
Debug session time: Wed Aug 29 07:06:36.217 2012 (GMT+2)
System Uptime: 0 days 0:25:45.232
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, fffff88003290c70, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )
Followup: MachineOwner
---------
5: 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: 0000000000000000
Arg2: fffff88003290c70
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
LAST_CONTROL_TRANSFER: from fffff80002c17818 to fffff80002cce640
STACK_TEXT:
fffff880`03290c38 fffff800`02c17818 : 00000000`0000009c 00000000`00000000 fffff880`03290c70 00000000`00000000 : nt!KeBugCheckEx
fffff880`03290c40 fffff800`02c16f57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`03290d90 fffff800`02c0ae88 : 00000000`00000000 fffff880`03288180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`03290dc0 fffff800`02cccf2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03290df0 fffff800`02cccd93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03290f30 fffff880`02fb99c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`032b0c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm+39c2
fffff880`02fb99c2 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: intelppm+39c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd
FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+39c2
BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+39c2
Followup: MachineOwner
Fassen wir zusammen:
- Der Rechner wurde vor ca. 1 Jahr neu installiert (als die SSD neu kam, vorher ist er mit denselben Treibern mit einer WD Raptor als System-HDD gelaufen) - seither keine wesentlichen Veränderungen. SW-Fehler (Treiber) schließe ich daher eher aus. Kein Internet, keine Security-SW, nix.
- Bis vor 6 Wochen lief der Rechner problemlos (bis auf die gelegentliche Wartepause beim Booten).
- Nach der 6 Wochen Sommerpause, in der das Teil nicht in Betrieb war, hat die Sache mit den BSODs angefangen.
- Windows-Memorytest ging OK, chkdsk auf der System-SSD ging OK. Netzteiltausch hat nichts gebracht.
Soll ich mich mit dem Gedanken anfreunden, dass das MoBo eine Lettn hat? Noch ein ASUS P6T aus dem Ausland zu ca. 190,- anfordern oder auf ein aktuelles System umsteigen (da reden wir dann von 800,-)?
Thx