WHEA_UNCORRECTABLE_ERROR Hatası

ardakcbs

Kilopat
Katılım
25 Ocak 2017
Mesajlar
40
Çözümler
1
Daha fazla  
Sistem Özellikleri
Intel Core i5-14600KF 3.50GHz 14 Çekirdek 20MB L3 Önbellek Soket 1700 İşlemci
MSI PRO H610M-E Intel LGA1700 DDR5 5600MHz mATX
MSI GeForce RTX 4070 Ventus 2X 12G OC
Kingston Fury Beast KF560C40BBK2/32 32GB
Kingston KC3000 SKC300
Cinsiyet
Erkek
Uzun zamandır ve son zamanlarda daha fazla bir şekilde "WHEA_UNCORRECTABLE_ERROR" mavi ekran hatası alıyorum. İnternetten çözümlere baktım, hep 2012-2014 tarihli çözümler ve işe yaramıyor. Yardımcı olursanız çok sevinirim.

Minidump
 
Son düzenleyen: Moderatör:
Bu sisteme en son donanımsal bakım ne zaman yapıldı?
Intel GPU güncelle ama İşlemcide problem veya aşırı ısınma olabilir kontrol edin.
Kod:
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: ffffe206dd576028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110b, Low order 32-bits of the MCi_STATUS value.

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

*** WARNING: Unable to verify timestamp for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-R1MKTM3

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 68

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe206dd576028

BUGCHECK_P3: be000000

BUGCHECK_P4: 100110b

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff802`83c769e8 fffff802`8143ff20 : 00000000`00000124 00000000`00000000 ffffe206`dd576028 00000000`be000000 : nt!KeBugCheckEx
fffff802`83c769f0 fffff808`b61514ba : ffffe206`dd576028 ffffe206`dc8a8a70 ffffe206`dc8a8a70 ffffe206`dc8a8a70 : hal!HalBugCheckSystem+0xd0
fffff802`83c76a30 ffffe206`dd576028 : ffffe206`dc8a8a70 ffffe206`dc8a8a70 ffffe206`dc8a8a70 00000000`00000000 : PSHED+0x14ba
fffff802`83c76a38 ffffe206`dc8a8a70 : ffffe206`dc8a8a70 ffffe206`dc8a8a70 00000000`00000000 fffff802`817503c1 : 0xffffe206`dd576028
fffff802`83c76a40 ffffe206`dc8a8a70 : ffffe206`dc8a8a70 00000000`00000000 fffff802`817503c1 ffffe206`dd576028 : 0xffffe206`dc8a8a70
fffff802`83c76a48 ffffe206`dc8a8a70 : 00000000`00000000 fffff802`817503c1 ffffe206`dd576028 00000000`00000000 : 0xffffe206`dc8a8a70
fffff802`83c76a50 00000000`00000000 : fffff802`817503c1 ffffe206`dd576028 00000000`00000000 ffffe206`dc8a8a70 : 0xffffe206`dc8a8a70


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN

OS_VERSION: 10.0.17134.1

BUILDLAB_STR: rs4_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d4ff8356-accf-463b-abb8-12a20b1a031a}

Followup:     MachineOwner
 

Bakım 1,5 ay önce yapılmıştı. Intel GPU şuan baktım güncel gözüküyor. Önceden bilgisayar aşırı ısınma yapıyordu fakat 1,5 aydır öyle bir sorun yaşamıyorum.
 
Güncel.
 
Son düzenleyen: Moderatör:
Gerçekten bilmiyorum ve anlamıyorum. Windows güncelleştirme yaptığım halde de 1.5 sene önceki sürümü kullanıyorum. Ne yapmam gerektiğini de bilmiyorum @MayCrasH
 
Bilgisayarı formatladım ama halde sorun devam etmekte. Hangi sekmeden donanım kimliklerini istiyorsunuz acaba @claus
 
Son düzenleyen: Moderatör:
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…