Wieder mal: blue screen

[Quintus14]

Nachtrag: und hier der nächste (screenshot), unten der minidump

Ich hab' im letzten halben Jahr nun schon das Netzteil, das Board und den RAM ausgetauscht - mittlerweile bin ich ziemlich angesäuert. Kann eine CPU einen Pascher haben? Oder die M4? Oder die ATI?

----

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


Loading Dump File [C:\Windows\Minidump\021513-111244-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`02c51000 PsLoadedModuleList = 0xfffff800`02e96e90
Debug session time: Fri Feb 15 15:44:59.336 2013 (GMT+1)
System Uptime: 0 days 0:26:31.350
Loading Kernel Symbols
....................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b2180, 4}

Unable to load image SCSIPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS
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: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 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:  
fffff800`041b95b8 fffff800`02d28a89 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff800`041b95c0 fffff800`02cdbeb7 : fffff800`00000000 fffff800`00000004 00000000`00002710 fffff800`02dbf0e0 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`041b9650 fffff800`02c12895 : fffff800`02c38460 fffff800`041b9800 fffff800`02c38460 fffff880`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`041b9750 fffff800`02ccdb73 : 00000000`00000010 fffff880`04a2d1c8 00000000`00008000 fffff880`03e072b6 : hal!HalpHpetClockInterrupt+0x8d
fffff800`041b9780 fffff800`02cd7206 : fffff800`02e43e80 fffffa80`00000001 00000000`00000000 fffff800`041b9a38 : nt!KiInterruptDispatchNoLock+0x163
fffff800`041b9910 fffff800`02c6f869 : 00000000`00000014 fffff880`0b9c2000 00000000`00000000 00000000`000000fe : nt!KeFlushMultipleRangeTb+0x266
fffff800`041b99e0 fffff800`02d3ff23 : 00000000`00000001 fffff880`0b9c28c0 fffff6fc`4005ce10 fffff800`00000001 : nt!MiRemoveIoSpaceMap+0xe9
fffff800`041b9b10 fffff880`01059d3e : fffffa80`0b71d978 fffffa80`0a3abcc0 fffffa80`0a3ad760 fffff800`02d7b3d0 : nt! ?? ::FNODOBFM::`string'+0x3703d
fffff800`041b9b60 fffffa80`0b71d978 : fffffa80`0a3abcc0 fffffa80`0a3ad760 fffff800`02d7b3d0 fffffa80`0a3ad700 : SCSIPORT+0x7d3e
fffff800`041b9b68 fffffa80`0a3abcc0 : fffffa80`0a3ad760 fffff800`02d7b3d0 fffffa80`0a3ad700 00000000`00000000 : 0xfffffa80`0b71d978
fffff800`041b9b70 fffffa80`0a3ad760 : fffff800`02d7b3d0 fffffa80`0a3ad700 00000000`00000000 00000000`00000000 : 0xfffffa80`0a3abcc0
fffff800`041b9b78 fffff800`02d7b3d0 : fffffa80`0a3ad700 00000000`00000000 00000000`00000000 fffff800`02ccced6 : 0xfffffa80`0a3ad760
fffff800`041b9b80 fffffa80`0a3abcc0 : fffffa80`0a3ad610 00000000`00000000 00000000`00000000 fffffa80`0a3ad6d8 : nt!IopStartNextPacket+0x40
fffff800`041b9bb0 fffffa80`0a3ad610 : 00000000`00000000 00000000`00000000 fffffa80`0a3ad6d8 fffffa80`0a3ad600 : 0xfffffa80`0a3abcc0
fffff800`041b9bb8 00000000`00000000 : 00000000`00000000 fffffa80`0a3ad6d8 fffffa80`0a3ad600 fffff880`010578c7 : 0xfffffa80`0a3ad610


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