"WHEA_UNCORRECTABLE_ERROR" hatası

İşletim sistemi
Windows 10

Hakanav

Decapat
Katılım
27 Eylül 2022
Mesajlar
16
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
RAM
DDR4 2400mhz 8gb
SSD veya HDD modeli
128gb m2 ssd
Ekran kartı
Gtx1070
Anakart
p65_67rsrp
İşlemci
İ7 6700Hq
Cihazım Clevo P670RS modeli:
Daha önceden de konu açmıştım cihaz açıldıktan sonra da format atarken de 1.30 dakika kadar sonra;
WHEA_UNCORRECTABLE_ERROR hatası alıyorum.
Memtest86 hata almadım.
Farklı hard disk ile denedim aynı.
Farklı RAM ile denedim aynı.
Normalde minidump dosyası oluşmuyordu bugün flash üzerine Windows kurup oradan boot ettiğimde;
Aynı hatayı aldım ancak bu sefer minidump dosyası oluştu onu paylaşıyorum.
İnternette uzun araştırmalarım sonucu yabancı kaynaklarda da benzer problemi yaşayan yaklaşık 10 kişi buldum.
Onlarda cihaz batarya üzerinden çalışırken sorun yok ancak şarja takıldığında aynı hatayı alıyorlar.
Bataryam maalesef çalışmadığı için deneyemiyorum.
Şimdiden teşekkür ederim.
 
Son düzenleyen: Moderatör:
- WHEA_UNCORRECTABLE_ERROR genelde işlemci güç beslemesi ile alakalı. BIOS üzerinden veya ThrottleStop gibi programlar üzerinden işlemciniz için overclock/undervolt yaptıysanız böyle bir hatayla karşılaşabilirsiniz.

- İlginçtir ki aşağıdaki konuda da benzer çözümler önerilmiş lakin konu sahibi, Monster servisin SSD'yi değiştirmesi ile mavi ekran hatasının çözüldüğünü söylemiş.


- Buradan da i7 6700HQ işlemciniz için grafik sürücülerini indirip kurarsınız.


- Son olarak, BIOS sürümünüz güncel mi? Döküm dosyalarından kontrol ettiğimde sizin verdiğiniz model numarasından başka bir bilgi göremedim. Sadece sürüm ve tarih görünüyor.

Rich (BB code):
BiosVersion = 1.05.07
BiosReleaseDate = 7 Ocak 2017


- Bilgisayarınızın destek sayfasından chipset sürücülerinizi de indirip güncellemenizi tavsiye ederim, bu hata eksik/eski sürücülerden dolayı kaynaklanabiliyor.

- Fan temizliği ve toz temizliği yaptınız mı? Kurumuş / yanlış uygulanmış termal macun uygulaması sebebiyle de problem yaşıyor olabilirsiniz, işlemci çok ısınıyor olabilir. HWiNFO64 gibi bir programla mavi ekran aldığınız zaman işlemci sıcaklığını kontrol edebilirsiniz.


- Yine başka bir konuda işlemci ile alakalı sıkıntı ararken entegre grafik sürücüleri ile alakalı sorun bulduk.



Kod:
*******************************************************************************
*                                                                             *
*                        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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff990fa0717028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000081136, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1781

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3127

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 2

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 186

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5550

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x124

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  100722-21734-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff990fa0717028

BUGCHECK_P3: be000000

BUGCHECK_P4: 81136

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

STACK_TEXT:
ffffc400`5ed548e8 fffff803`76ab448a     : 00000000`00000124 00000000`00000000 ffff990f`a0717028 00000000`be000000 : nt!KeBugCheckEx
ffffc400`5ed548f0 fffff803`74f115b0     : 00000000`00000000 ffff990f`a0717028 ffff990f`9e8f3fd0 ffff990f`a0717028 : nt!HalBugCheckSystem+0xca
ffffc400`5ed54930 fffff803`76bb612e     : 00000000`00000000 ffffc400`5ed549d9 ffff990f`a0717028 ffff990f`9e8f3fd0 : PSHED!PshedBugCheckSystem+0x10
ffffc400`5ed54960 fffff803`76ab5db1     : ffff990f`a0e69910 ffff990f`a0e69910 ffff990f`9e8f4020 ffff990f`9e8f3fd0 : nt!WheaReportHwError+0x46e
ffffc400`5ed54a40 fffff803`76ab6123     : 00000000`00000006 ffff990f`9e8f4020 ffff990f`9e8f3fd0 00000000`00000006 : nt!HalpMcaReportError+0xb1
ffffc400`5ed54bb0 fffff803`76ab6000     : ffff990f`9e8f2030 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffc400`5ed54c00 fffff803`76ab6251     : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffc400`5ed54c40 fffff803`76ab54bb     : 00000000`00000000 00000000`00000000 ffffc400`5ed54ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffc400`5ed54c70 fffff803`76ab7d05     : ffff990f`9e8f2030 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
ffffc400`5ed54ca0 fffff803`76b0d419     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffc400`5ed54cd0 fffff803`76a062fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc400`5ed54d00 fffff803`76a05fb7     : 00000000`00000000 00000000`00000000 00000000`00510022 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffc400`5ed54e40 00007ffe`21b9b7df     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000d7`0bc8c3d0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`21b9b7df


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5371cb52-c3d9-558e-47d4-d31c09567ca2}

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

*******************************************************************************
*                                                                             *
*                        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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc3827f717028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000081136, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2093

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7235

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 2

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 77

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5552

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x124

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  100722-21703-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc3827f717028

BUGCHECK_P3: be000000

BUGCHECK_P4: 81136

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd501`f8fbe8e8 fffff800`798b448a     : 00000000`00000124 00000000`00000000 ffffc382`7f717028 00000000`be000000 : nt!KeBugCheckEx
ffffd501`f8fbe8f0 fffff800`757d15b0     : 00000000`00000000 ffffc382`7f717028 ffffc382`7d8f5140 ffffc382`7f717028 : nt!HalBugCheckSystem+0xca
ffffd501`f8fbe930 fffff800`799b612e     : 00000000`00000000 ffffd501`f8fbe9d9 ffffc382`7f717028 ffffc382`7d8f5140 : PSHED!PshedBugCheckSystem+0x10
ffffd501`f8fbe960 fffff800`798b5db1     : ffffc382`7fe64910 ffffc382`7fe64910 ffffc382`7d8f5190 ffffc382`7d8f5140 : nt!WheaReportHwError+0x46e
ffffd501`f8fbea40 fffff800`798b6123     : 00000000`00000007 ffffc382`7d8f5190 ffffc382`7d8f5140 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffd501`f8fbebb0 fffff800`798b6000     : ffffc382`7d8f30e8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffd501`f8fbec00 fffff800`798b6251     : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffd501`f8fbec40 fffff800`798b54bb     : 00000000`00000000 00000000`00000000 ffffd501`f8fbeed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffd501`f8fbec70 fffff800`798b7d05     : ffffc382`7d8f30e8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
ffffd501`f8fbeca0 fffff800`7990d419     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffd501`f8fbecd0 fffff800`798062fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffd501`f8fbed00 fffff800`79805fb7     : 00000000`00000000 fffff800`79805eec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd501`f8fbee40 fffff800`8fee138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffffe81`62c8f5b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup:     MachineOwner
---------
 
Son düzenleme:
Öncelikle cevabın için teşekkür ederim.
Bios sürümünü ve ec-firmwareyi güncelledim sorun hala devam ediyor.
İşlemcim HQ ibareli olduğu için istesem de overclock yapamayacağım diye biliyorum.
Zaten bir işletim sistemi yok sayılır flashdan boot ettiğimde de veriyor.
Bilgisayarın ısınacak kadar çalıştığını düşünmüyorum flashdan boot edip ekran kartını devre dışı bırakmak için aygıt yöneticisine girmek için 4-5 kez denedim tek bir sürücü vardı detaylarına bakamadan aynı hatayı verdi.
Sürücü güncellemelerini yapacak kadar malesef açık kalmıyor cihaz.

Yarın Hwinfo ile sıcaklık detayı alabilirsem paylaşırım.
Benzer şekilde cihazın güç tüketimini görebileceğim bir program var mı?
Yaşanan bir dalgalanmadan dolayı da kaynaklanabileceğini düşünüyorum.

Vbios güncellemesini dos üzerinden yapabilsem onu da yapacağım ancak windows üzerinden yapılıyor.
 
Yurtdışı girişli cihaz malesef yerel bir bilgisayarcıya vermeyi düşünüyorum ama gereksiz masraf çıkacağından ve hakkıyla yapılmayacağından korkuyorum
Ankara içinde önerebileceğiniz bir yer varmı
 

Technopat Haberler

Yeni konular

Geri
Yukarı