whea_uncorrectable_error

[ShowItBaby]

Hallo an alle
ich bekomme gehäuft diese Fehlermeldung. Treiber habe ich nach bestem Wissen aktualisiert ohne Erfolg. Kann mir vielleicht jemand dabei helfen dem ganzen auf die Spur zu kommen bin am Ende.

 

[3murmeln]

Also ich bekomme diese Fehler, wenn ich meiner CPU zu wenig V-Core gebe...

 

[ShowItBaby]

Es scheint mir als sei dies eine allgemeine Hardware Fehlermeldung aber ich hab keine Ahnung wie ich rausfinden soll/kann was die Ursache dafür ist.

 

[weissnichalles1]

Welches Betriebssytem?
Schon mal bei Microsoft nachgeschaut: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321%28v=vs.85%29.aspx

 

[SPY72]

Hier ist was zum Thema WHEA fehler ..... mit ansätzen zur lösung :

https://www.computerbase.de/forum/threads/bluescreen-seit-einer-woche.1256210/

Zudem kann hier jeder nur raten weil deine Angaben zum System etc fehlen ....

Bitte angeben :

- dein System
- seit wann tritt der Fehler auf und wie äussert er sich
- hast du übertaktet?
- Betriebssystem

 

[ShowItBaby]

CooMas Silencio 550 bk ATX
Seag 1TB ST1000NC001 Const CS SA3
SSD 120GB 480/535 V+200 7mm SA3 KIN
Teac BD-W512GSA 12x SA XL bk R
D316GB 1600-10 Vengeance K2 COR
Asus2GB D5 X GTX770-DC2OC R
Asus Z87-A Z87 RG SA
Int Core i5-4670K 3400 1150 BOX
Scythe Mugen 4 SCMG-4000
MS Windows 8 64bit DE
be quiet! POWERZONE 850W ATX23

Ich habe mir den Pc erst vor kurzem zusammengestellt und seit dem bekomme ich meistens die Fehlermeldung gehäuft beim zocken.Übertaktet habe ich nicht

Ergänzung (4. Oktober 2013)

Hier ist auch noch die Auswertung der minidump file:

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: fffffa800cf9b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Diablo III.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff800`7ea61a28 fffff800`7ec3a965 : 00000000`00000124 00000000`00000000 fffffa80`0cf9b028 00000000`bf800000 : nt!KeBugCheckEx
fffff800`7ea61a30 fffff800`7edd9ef9 : 00000000`00000001 fffffa80`0c7df3a0 00000000`00000000 fffffa80`0cf9b028 : hal!HalBugCheckSystem+0xf9
fffff800`7ea61a70 fffff800`7ec3a703 : 00000000`00000728 00000000`00000000 fffff800`7ea61bd0 fffffa80`0c7df3a0 : nt!WheaReportHwError+0x249
fffff800`7ea61ad0 fffff800`7ec3a020 : 00000000`00000010 fffffa80`0c7df3a0 fffff800`7ea61c88 fffffa80`0c7df3a0 : hal!HalpMcaReportError+0x53
fffff800`7ea61c30 fffff800`7ec39f1b : fffffa80`0c7e63d0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff800`7ea61c80 fffff800`7ec39d78 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff800`7ea61cc0 fffff800`7ec3af0f : fffffa80`0c7e63d0 fffff800`7ea61ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff800`7ea61cf0 fffff800`7ecd177b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`7ea61d20 fffff800`7ecd152e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff800`7ea61e60 fffff880`038c4fe2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff880`055d38f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0xb6e


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner

Ergänzung (4. Oktober 2013)

Keiner ne Idee bin echt am Ende

 

[SPY72]

Hast du dich durch den Link dort oben durchgearbeitet ?

Tests versucht ?

 

[ShowItBaby]

Ja keine fehler gefunden. Der error tritt auch meist bzw eigentlich nur beim zocken auf. Gibts da nicht ne Möglichkeit auszulesen was dafür verantwortlich oder so? Bin halt kein Fachmann leider

 

[weissnichalles1]

Windows Ereignisanzeige

 

[MagicAndre1981]

tippe in windbg bei der obigen dump noch !errrec fffffa800cf9b028 ein, führe das aus und poste die Ausgabe

 

[ShowItBaby]

Das versteh ich leider nicht direkt :8 wie gesagt bin leider kein Fachmann kannste mir vielleicht genauer erklären wie bzw was ich genau machen muss
Sry für meine Inkompetenz^^

 

[MagicAndre1981]

du öffnest wieder die gleiche dmp mit Windbg und tippst meinen Befehl unten ein und drückst ENTER

 

[ShowItBaby]

0: kd> !errrec fffffa800cf9b028
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Invalid error record
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Error Record @ FFFFFA800CF9B028 has 0 sections
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Severity : Recoverable
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Validation Bits : 0x00000000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Total Length : 0x0
Timestamp : n/a
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Creator : Unknown Creator 6C697542-B028-0CF9-80fa-FFFF00000000
Notify Type : 6C697542-B028-0CF9-80fa-FFFF00000000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Record ID : 0x0000000000000000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
Flags : 0x00000000*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************

 

[MagicAndre1981]

hm. Probiere mal das neuste BIOS/UEFI:

http://www.asus.com/de/Motherboards/Z87A/#support


Ist der Scythe Mugen 4 richtig montiert? Wie wohl ist die CPU Temperatur?

 

[ShowItBaby]

Ja habe sowohl Graphikkarte als auch Prozessor schon mittels eines Programmes auf ihre Leistungsfähigkeit überprüft alles ok auch von der temperatur.
Es sieht so aus als würde eine hal.dll datei Abstürzen bzw den Fehler auslösen!????
Mainboarddriver is auch schon aktualisiert.

 

[MagicAndre1981]

nein die DLL is ok, die Fehlererkennung kommt von Windows Hardware Error Architecture (http://msdn.microsoft.com/en-us/library/windows/hardware/gg463286.aspx).

Wie hoch ist die Temperatur?