WCM Forum - Blue Screen

WCM Forum (http://www.wcm.at/forum/index.php)

- Hardware-Probleme (http://www.wcm.at/forum/forumdisplay.php?f=3)

- - Blue Screen (http://www.wcm.at/forum/showthread.php?t=244967)

Hallo,

zurück aus dem Urlaub den Videoschnitt-PC gestartet - nach relativ kurzer Zeit Blue Screen. Stunden später dann noch einer. Ich hab' im Minidump etwas von Vista driver fault gelesen, dann die MoBo- und den GraKa-Treiber neu installiert. Die Kiste ist dann den ganzen Tag tadellos gelaufen.

Heute Früh in den ersten 5 Minuten - wieder ein Blue Screen.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\082612-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: C:\Windows\System32

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`02c4c000 PsLoadedModuleList = 0xfffff800`02e91e90

Debug session time: Sun Aug 26 07:59:14.625 2012 (GMT+2)

System Uptime: 0 days 0:23:35.845

Loading Kernel Symbols

...............................................................

................................................................

..............................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 101, {19, 0, fffff88003164180, 2}



Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )



Followup: MachineOwner

---------



0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffff88003164180, The PRCB address of the hung processor.

Arg4: 0000000000000002, 0.



Debugging Details:

------------------





BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT



PROCESS_NAME:  System



CURRENT_IRQL:  d



STACK_TEXT:  

fffff880`035ee788 fffff800`02d23a89 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03164180 : nt!KeBugCheckEx

fffff880`035ee790 fffff800`02cd6eb7 : fffff880`00000000 fffff800`00000002 00000000`00026160 fffff880`02635000 : nt! ?? ::FNODOBFM::`string'+0x4e2e

fffff880`035ee820 fffff800`02c0d895 : fffff800`02c33460 fffff880`035ee9d0 fffff800`02c33460 00000000`00000000 : nt!KeUpdateSystemTime+0x377

fffff880`035ee920 fffff800`02cc8b73 : 00000000`51eb244f fffff800`02e3ee80 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d

fffff880`035ee950 fffff800`02cd2206 : fffff800`02e3ee80 fffff800`00000001 00000000`00000000 fffff880`035eebd8 : nt!KiInterruptDispatchNoLock+0x163

fffff880`035eeae0 fffff800`02c8a356 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0b4a1b60 : nt!KeFlushMultipleRangeTb+0x266

fffff880`035eebb0 fffff800`02c8a2d8 : 00000000`00000000 fffff800`00000038 00000000`00000000 fffffa80`09d5d070 : nt!MmOutPageKernelStack+0x56

fffff880`035eec90 fffff800`02d00d68 : 00000000`00000000 00000000`00000080 fffffa80`09d5d070 fffffa80`09d5d000 : nt!KiOutSwapKernelStacks+0x11c

fffff880`035eed00 fffff800`02f69cce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x48

fffff880`035eed40 fffff800`02cbdfe6 : fffff880`009b2180 fffffa80`09d7a580 fffff880`009bd0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`035eed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16





STACK_COMMAND:  kb



SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE



FOLLOWUP_NAME:  MachineOwner



MODULE_NAME: Unknown_Module



IMAGE_NAME:  Unknown_Image



DEBUG_FLR_IMAGE_TIMESTAMP:  0



FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE



BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE



Followup: MachineOwner

---------

Was sagt den Spezialisten der Minidump?

Thx
Quintus

ASUS P6T, i7/950, 12 GB RAM, ATI Radeon 4800 series, Win7/64 auf SSD (Crucial M4), kein Overclocking (im BIOS alles auf automatic)

----

NACHTRAG: ich muss dazu sagen, dass ich auf dem Rechner beim Booten oft einen 2-Minuten-Hänger hab' (wir sprachen andernorts schon darüber). Ich war bis vor ein paar Wochen der Meinung, dass das vom (absichtlich) falschen Gateway her rührt (der Videoschnitt-PC soll nicht ins Internet weil ich hier keine Security-SW möchte). Ich hab' ihm kurz auch das richtige Gateway gegeben - auch da gab's die Boot-Hänger! Dieser Punkt ist also auch ungeklärt.
.

Lt. div. Infos soll es sich dabei um ein Prozessorproblem handeln. Hier würde ich mal raten, die Spannungen zu beobachten, ev. zu korrigieren oder wenn möglich ein anderes NT testen.

Uuuuups..... danke .... hast einen Link für mich, wo Du das gelesen hast? Und das jetzt erst nach knapp 3 Jahren?

PC Probe sagt 11,97V / VCore 0,94-11,97V / 3,31V / 5,02V. Die CPU-Temperatur idle um die 45 Grad, unter Volllast (Rendern) um die 73. Die Blue Screens kamen im Leerlauf.

Hier z.B. http://social.technet.microsoft.com/...e-eec61981797b

Zitat:

Bug Check Code 0x101: http://msdn.microsoft.com/en-us/libr...=VS.85%29.aspx
You have a problem with your processor. Contact your manufacturer Technical Support or replace it.

Erst nach drei Jahren? Kommt auf das Netzteil drauf an. Hier kann die Qualität (unabhängig vom Hersteller) schon mal schwanken. Wäre aber eine kostengünstigere (ev. sogar kostenlose bei einer Möglichkeit zum Ausborgen) Variante der Versuch mit dem Netzteil.

Danke! Ich hab' eh noch ein Reserve-NT am Dachboden - das werde ich die nächsten Tage mal umbauen.

LG

Wegen der Schwierigkeit, das NT auszubauen (wir sprachen an anderer Stelle darüber), hab' ich mich vorläufig einmal davor "gedrückt" - und beschlossen, auf den nächsten Blue Screen zu warten.

Heute war ich Joggen, der Rechner lief im Leerlauf - und als ich zurück kam, war der nächste BSOD da:

Code:

....



0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffff880030f9180, The PRCB address of the hung processor.

Arg4: 0000000000000006, 0.



Debugging Details:

------------------



***** Kernel symbols are WRONG. Please fix symbols to do analysis.

....



************



ADDITIONAL_DEBUG_TEXT:  

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.



MODULE_NAME: nt



FAULTING_MODULE: fffff80002c4a000 nt



DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a



BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT



CURRENT_IRQL:  0



STACK_TEXT:  

fffff800`04094938 fffff800`02d21a89 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`030f9180 : nt+0x80640

fffff800`04094940 00000000`00000101 : 00000000`00000019 00000000`00000000 fffff880`030f9180 00000000`00000006 : nt+0xd7a89

fffff800`04094948 00000000`00000019 : 00000000`00000000 fffff880`030f9180 00000000`00000006 fffff880`016f98ca : 0x101

fffff800`04094950 00000000`00000000 : fffff880`030f9180 00000000`00000006 fffff880`016f98ca 00000006`00000000 : 0x19





STACK_COMMAND:  .bugcheck ; kb



FOLLOWUP_NAME:  MachineOwner



IMAGE_NAME:  ntoskrnl.exe



BUCKET_ID:  WRONG_SYMBOLS



Followup: MachineOwner

Der Mini-Dump sieht also ähnlich aus. Ich versteh' nur nicht, warum es das Netzteil sein soll, wenn PC-Probe II die Spannungen als relativ genau und auch praktisch nicht schwankend ausliest.

Seid Ihr immer noch der Meinung, dass ich das NT tauschen soll...?

Thx
Quintus

Brauchst ja nicht ausbauen. Lass es frei daneben baumeln.

Update: das NT, das ich im Dachboden hatte, hatte zu wenig Anschlüsse und schien auch etwas schwach - ich musste das NT mit jenem einer anderen Kiste tauschen. Ziemliche Äktschn, auch die HDDs hab' ich dabei nun umgedreht.

Ich hab' alle Anschlüsse und Kabel wieder in die Position gebracht, wie sie waren - bis auf eines: die USB-Maus scheine ich an einen anderen USB gestöpselt zu haben - "Maustreiber wurde installiert" - dann ist die Geschichte eingefroren und nach dem Reset-Button hat sich ein neuer Minidump eingefunden:

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\082812-20623-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`02c58000 PsLoadedModuleList = 0xfffff800`02e9de90

Debug session time: Tue Aug 28 15:28:30.524 2012 (GMT+2)

System Uptime: 0 days 0:00:15.539

Loading Kernel Symbols

.....................................................

Loading User Symbols

Mini Kernel Dump does not contain unloaded driver list

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 124, {0, fffffa800a84e038, 0, 0}



Probably caused by : hardware



Followup: MachineOwner

---------



5: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. Parameter 1 identifies the type of error

source that reported the error. Parameter 2 holds the address of the

WHEA_ERROR_RECORD structure that describes the error conditon.

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: fffffa800a84e038, Address of the WHEA_ERROR_RECORD structure.

Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.



Debugging Details:

------------------





BUGCHECK_STR:  0x124_GenuineIntel



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT



PROCESS_NAME:  System



CURRENT_IRQL:  0



STACK_TEXT:  

fffff880`0355b6f0 fffff800`02f1bd29 : fffffa80`0a84e010 fffffa80`09dadb60 fffffa80`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c

fffff880`0355bc10 fffff800`02dfb217 : fffffa80`0a84e010 fffff800`02e75658 fffffa80`09dadb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49

fffff880`0355bc40 fffff800`02d62865 : fffff800`02ed73a0 00000000`00000001 fffffa80`0a5d3b30 fffffa80`09dadb60 : nt!WheapProcessWorkQueueItem+0x57

fffff880`0355bc80 fffff800`02ce2a21 : fffff880`01155e00 fffff800`02d62840 fffffa80`09dadb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25

fffff880`0355bcb0 fffff800`02f75cce : 00000000`00000000 fffffa80`09dadb60 00000000`00000080 fffffa80`09d7b070 : nt!ExpWorkerThread+0x111

fffff880`0355bd40 fffff800`02cc9fe6 : fffff880`0336a180 fffffa80`09dadb60 fffff880`033750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`0355bd80 00000000`00000000 : fffff880`0355c000 fffff880`03556000 fffff880`030c2540 00000000`00000000 : nt!KxStartSystemThread+0x16





STACK_COMMAND:  kb



FOLLOWUP_NAME:  MachineOwner



MODULE_NAME: hardware



IMAGE_NAME:  hardware



DEBUG_FLR_IMAGE_TIMESTAMP:  0



FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV



BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV



Followup: MachineOwner

---------



5: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************



WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. Parameter 1 identifies the type of error

source that reported the error. Parameter 2 holds the address of the

WHEA_ERROR_RECORD structure that describes the error conditon.

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: fffffa800a84e038, Address of the WHEA_ERROR_RECORD structure.

Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.



Debugging Details:

------------------





BUGCHECK_STR:  0x124_GenuineIntel



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT



PROCESS_NAME:  System



CURRENT_IRQL:  0



STACK_TEXT:  

fffff880`0355b6f0 fffff800`02f1bd29 : fffffa80`0a84e010 fffffa80`09dadb60 fffffa80`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c

fffff880`0355bc10 fffff800`02dfb217 : fffffa80`0a84e010 fffff800`02e75658 fffffa80`09dadb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49

fffff880`0355bc40 fffff800`02d62865 : fffff800`02ed73a0 00000000`00000001 fffffa80`0a5d3b30 fffffa80`09dadb60 : nt!WheapProcessWorkQueueItem+0x57

fffff880`0355bc80 fffff800`02ce2a21 : fffff880`01155e00 fffff800`02d62840 fffffa80`09dadb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25

fffff880`0355bcb0 fffff800`02f75cce : 00000000`00000000 fffffa80`09dadb60 00000000`00000080 fffffa80`09d7b070 : nt!ExpWorkerThread+0x111

fffff880`0355bd40 fffff800`02cc9fe6 : fffff880`0336a180 fffffa80`09dadb60 fffff880`033750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`0355bd80 00000000`00000000 : fffff880`0355c000 fffff880`03556000 fffff880`030c2540 00000000`00000000 : nt!KxStartSystemThread+0x16





STACK_COMMAND:  kb



FOLLOWUP_NAME:  MachineOwner



MODULE_NAME: hardware



IMAGE_NAME:  hardware



DEBUG_FLR_IMAGE_TIMESTAMP:  0



FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV



BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV



Followup: MachineOwner

Ist jetzt eine andere Fehlerdiagnose - wars nur die anders angesteckte USB-Maus???

Ich beobachte nun weiter, ob der übliche Fehler wieder kommt.

LG
Quintus

0x124 könnte was mit dem Board zu tun haben.
http://windows7forums.com/blue-scree...ew-days-5.html

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