Hi,
spät, aber doch:
Zitat:
Zitat von Inzersdorfer
... Du könntest noch einmal kurz WinDbg anwerfen, und den 082812-20623-01.dmp öffnen, gib !errrec fffffa800a84e038 ein, es wird der Error Record angezeigt.
|
Ich tat, wie mir geheißen:
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> !errrec fffffa800a84e038
===============================================================================
Common Platform Error Record @ fffffa800a84e038
-------------------------------------------------------------------------------
Record Id : 01cd8520fb645264
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 8/28/2012 13:28:30
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800a84e0b8
Section @ fffffa800a84e190
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x00000000000106a5
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa800a84e100
Section @ fffffa800a84e250
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : a5 06 01 00 00 08 10 00 - bd e3 98 00 ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ fffffa800a84e250
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800a84e148
Section @ fffffa800a84e2d0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : Internal timer (Proc 0 Bank 5)
Status : 0xfe00000000800400
Address : 0x0000388004007f8e
Misc. : 0x0000000000007fff
Was sagt uns das jetzt?
Zitat:
Zitat von Lowrider20
|
Es schaut mir so aus, als hätte das Foxconn jetzt keinen zusätzlichen (JMicron-)Controller, d.h. ich hab' derzeit intern 6 + 2 SATA in Verwendung.
Ich muss morgen noch die in Frage kommenden MoBos genauer beäugen - ausm Bauch heraus würd ich zum
P6T Workstation-Board greifen und vielleicht noch eine USB 3.0-I/O-Card rein stecken, wenn ich schon dabei bin.
Thx