Wieder mal: blue screen

[Inzersdorfer]

Wie du schon erkannt hast, im BIOS manuell einstellen.
increase/decrease QPI/VTT first, if not: increase/decrease vcore...have to test to see which one it is

Auch eine Auswertung des Error Record bringt dir nichts
Angehängt hab ich Einen als Beispiel, typisch nichtssagend, es zeigt nur, das im Ersten Kern der CPU ein Fehler im Cache auftrat.
GCACHEL2_ERR_ERR (Proc 0 Bank 5): Generischer Fehler im L2 Cache_Fehler_Generisch (1.Prozessorkern, Speicherbank 6)

[Quintus14]

Danke für die Info. Habe heute ca. 7 Stunden intensiv Videobearbeitung gemacht - kein Problem bis jetzt. Morgen und übermorgen geht's weiter - ich warte auf den nächsten BSOD, dann poste ich den neuen dump (in der Hoffnung, da steht Genaueres drin) und fang' an, an den Spannungen zu schrauben.

Thx

[Quintus14]

So - nach 1,5 Tagen intensivem Videoschnitt ist der nächste BSOD da: er ereignete sich, als der PC grad mal nix zu tun hatte ...:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012613-21060-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`02c58000 PsLoadedModuleList = 0xfffff800`02e9de90
Debug session time: Sat Jan 26 17:01:15.030 2013 (GMT+1)
System Uptime: 0 days 9:05:09.029
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff88003090c70, 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: fffff88003090c70
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 fffff80002c21818 to fffff80002cd8640

STACK_TEXT:  
fffff880`03090c38 fffff800`02c21818 : 00000000`0000009c 00000000`00000000 fffff880`03090c70 00000000`00000000 : nt!KeBugCheckEx
fffff880`03090c40 fffff800`02c20f57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`03090d90 fffff800`02c14e88 : 00000000`00000000 fffff880`03088180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`03090dc0 fffff800`02cd6f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03090df0 fffff800`02cd6d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03090f30 fffff880`03fa09c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`030b0c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`03fa09c2 ??              ???

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

5: kd> !errec fffff88003090c70
No export errec found

Weist die Geschichte immer noch auf ein Spannungsproblem hin (der STOP-Code ist ja jetzt etwas anders)???

Ich hab' jetzt C1E wieder aktiviert (wie es sich standardmäßig gehört) und die CPU-Voltage im BIOS von 'Auto' (= 0,85 lt CPU) auf 1,000 gestellt: PCProbe-II zeigt nun VCore im idle mit 0,98V statt 0,94V an.

Mal schauen, ob/wann sich der nächste BSOD zeigt.

Thx