Blue Screen

[Lowrider20]

Brauchst ja nicht ausbauen. Lass es frei daneben baumeln.

[Quintus14]

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:

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