Win 8.1 Crashdmp analyse profis gefragt

[CrazyT]

Hi bekomme jetzt seit 2 tagen unregelmßig mal nen BSOD meist beim zocken aber auch 1x auf dem Desktop im IDLE

System steht unten in der Signatur ich hänge auch direkt nen Crashdump an, aus dem ich persönlich nicht schlau werde!

Spoiler: Crashdump

1: 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: ffffe00002207028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff800d488a000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:
ffffd000`201f0d78 fffff800`d4850c9f : 00000000`00000124 00000000`00000000 ffffe000`02207028 00000000`fa000000 : nt!KeBugCheckEx
ffffd000`201f0d80 fffff800`d4a41d41 : 00000000`00000001 ffffe000`001a7fd0 ffffe000`001a7fd0 ffffe000`02207028 : hal!HalBugCheckSystem+0xcf
ffffd000`201f0dc0 fffff800`d485112c : 00000000`00000728 00000000`00000001 ffffd000`201f11b0 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`201f0e20 fffff800`d4851499 : ffffe000`00000010 ffffe000`001a7fd0 ffffd000`201f0fc8 ffffe000`001a7fd0 : hal!HalBugCheckSystem+0x55c
ffffd000`201f0f70 fffff800`d4851384 : ffffe000`001a74a0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalBugCheckSystem+0x8c9
ffffd000`201f0fc0 fffff800`d48515ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0x7b4
ffffd000`201f1000 fffff800`d485174f : ffffe000`001a74a0 ffffd000`201f1230 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0x9fe
ffffd000`201f1030 fffff800`d49e27bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x3f
ffffd000`201f1060 fffff800`d49e2571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x27bb
ffffd000`201f11a0 fffff800`d49dab54 : 00000000`00400a02 00000000`00000002 ffffd000`209f4d70 00001f80`003b00bf : nt!setjmpex+0x2571
ffffd000`225e5d30 fffff800`d492e90e : ffffd000`201e7180 ffffe000`053ba080 fffff901`fffffffe 00000000`fffffffe : nt!KeSynchronizeExecution+0x2264
ffffd000`225e5e70 fffff800`d492e3a7 : 00000000`00000000 ffffc000`021600b0 ffffd000`225e5f68 00000000`00000000 : nt!KeRemoveQueueEx+0xf5e
ffffd000`225e5f10 fffff800`d492c028 : ffffd000`00000000 00000000`00000004 ffffe000`051a6050 ffffffff`fffffffc : nt!KeRemoveQueueEx+0x9f7
ffffd000`225e5f70 fffff800`d4cb85a9 : ffffe000`00000004 ffffd000`225e6100 ffffe000`05678880 00000000`00000006 : nt!KeWaitForMultipleObjects+0x228
ffffd000`225e6030 fffff800`d4cb8306 : 00000000`00000004 00000000`00000001 ffffd000`225e6700 0000002e`00000000 : nt!ObWaitForMultipleObjects+0x289
ffffd000`225e6540 fffff800`d49e34b3 : ffffe000`053ba080 ffffd000`225e69c8 ffffd000`225e67b8 ffffe000`0518acf0 : nt!NtWriteFile+0x36be
ffffd000`225e67a0 fffff800`d49db900 : fffff960`00145abd ffffffff`00000001 ffffffff`000007b0 00000000`00000002 : nt!setjmpex+0x34b3
ffffd000`225e69a8 fffff960`00145abd : ffffffff`00000001 ffffffff`000007b0 00000000`00000002 00000000`00000001 : nt!KeSynchronizeExecution+0x3010
ffffd000`225e69b0 fffff960`001b780e : ffffe000`05678880 00000000`00000000 ffffd000`225e6b39 00000000`000001ec : win32k!EngUpdateDeviceSurface+0x283ad
ffffd000`225e6aa0 fffff960`001b76d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000088`90c5fc40 : win32k!EngIsSemaphoreOwnedByCurrentThread+0x176e
ffffd000`225e6ba0 fffff800`d49e34b3 : ffffe000`053ba080 00000000`00000000 00000000`00000020 00000000`00000000 : win32k!EngIsSemaphoreOwnedByCurrentThread+0x1637
ffffd000`225e6c40 00007ffb`842f49aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x34b3
00000088`90c5fcc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`842f49aa


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

IMAGE_VERSION:

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
---------

1: kd> lmvm nt
start end module name
fffff800`d488a000 fffff800`d500b000 nt (export symbols) ntkrnlmp.exe
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Wed Oct 30 23:52:12 2013 (52718D9C)
CheckSum: 007120D6
ImageSize: 00781000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Edit: mal den DMP als spoiler gemacht das der Post nicht platzt

 

[schumischumi]

haste auch n minidump? die gehten mit bluescreenview meist schneller zu analysieren, auch wenn teilweise ungenauer.

auf den ersten blick seh ich nur GenuineIntel und driver error. evtl wlan oder lan von intel?

 

[unisolblade]

Der Crashdump output ist nutzlos ohne die Symbols. Also entweder Minidump posten oder richtig durch den Debugger jagen.

 

[Kartenlehrling]

Hast du den in den letzt 3 tagen was neues installieren,
mir fällt da zb. intels Rapid software ein und Samsung magician , diese beiden programme beissen sich ?!

 

[CrazyT]

sofern der minidump im windowsordner liegen SOLLTE: nein hab ich keinen

BTW Bluescreenview findet GAR NIX macht nichtmal den Memory.dmp auf daher leider der große

Der Crashdump output ist nutzlos ohne die Symbols. Also entweder Minidump posten oder richtig durch den Debugger jagen.

Wenn du mir sagst wie, mache ich das gerne!

Bin da leider nicht sehr bewandert

 

[unisolblade]

http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CDIQFjAA&url=http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F311503%2Fde&ei=h8QpU-OhLcf8ygO9-IHoDA&usg=AFQjCNH6XWHKrJCev_guRRutrWEgdgBVNg&sig2=Qgx95f5oCPOFBoHGLVvsCQ&bvm=bv.62922401,d.bGQ

 

[Marek72]

Hi,

hast Du da ältere Hardware auf einem neueren Board verbaut?

 

[Tarlon]

Hab das mal überflogen, ganz oben, der WHEA Fehler ist Hardware bedingt.
Recht weit unten taucht oft der Ausdruc "hal" auf, das hat mit der Grafikkarte zu schaffen.

Kann also die GraKa sein, oder eben ein Teil der ganzen Kette, auch Board, oder NT möglich.

 

[AllesPutt]

Hi

Lade die das kostenlose Tool BlueScreenViewer herunter und installiere es.

Starte es und es sollte dir den Ordner der MiniDumps anzeigen auch die dort erstellten.

Nun öffnest Du damit die aktuellste Dump und schaust wer der Verursacher war.

Hast Du irgendwas übertaktet?

Gruß

 

[CrazyT]

Außer den prozessor nix, aber Bluescreenviewer wirft mir nen HAL.dll! Eventuell nen Treiber der dort zerblasen ist.... ich teste mal nen anderen!


Edit erstmal prozz runtergetaktet.... mal sehen ob's hilft

 

[MagicAndre1981]

vergiss Bluescreenview, lad die dmp Datei im Anhang hoch (gepackt als zip)

 

[CrazyT]

Ich gehe von aus du meinst den Minidmp, ok wird getan!

 

[MagicAndre1981]

Du bekommt einen Internal unclassified Fehler, also wenig nützlich:

===============================================================================
Common Platform Error Record @ ffffe00002207028
-------------------------------------------------------------------------------
Record Id : 01cf437d1dcf65ac
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/19/2014 15:41:08 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe000022070a8
Section @ ffffe00002207180
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 : 0x0000000000000001

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffe000022070f0
Section @ ffffe00002207240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000001
CPU Id : a5 06 01 00 00 08 10 01 - 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 @ ffffe00002207240

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe00002207138
Section @ ffffe000022072c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : Internal unclassified (Proc 1 Bank 5)
Status : 0xfa00000000400405

Läuft alles bei weniger Takt? Die 3,8GHz waren bei deinem Intel Core i7 920 wohl etwas zu viel.

 

[CrazyT]

Jo bin mal auf 3.7 runter lief vorher zwar monatelang problemlos auf 3.8 aber man weiß ja nie.... aber mal sehen was die tage bringen!