"WHEA_UNCORRECTABLE_ERROR!" mavi ekran hatası

çağatay baydar

Yoctopat
Katılım
8 Ekim 2022
Mesajlar
2
Daha fazla  
Cinsiyet
Erkek
RAM
gskill 4x8 12 gb 1600 mhz
SSD veya HDD modeli
kıoxia 250 gb
Ekran kartı
nividia gtx1660 super
Anakart
asus m5a97 2.0
İşlemci
FX 8350
Eskiden kullandığım R7 250 ekran kartım yandığı için yerine 1660 Super almayı tercih ettim ama sorun şu ki ekran kartını bilgisayara taktığımda sürekli olarak olmadık yerlerde veyahut zamanda mavi ekran hatası alıyorum. (WHEA_UNCORRECTABLE_ERROR)
4 kere format attım SSD değiştirdim HDD değiştirdim farklı RAM'ler ile testler yaptım ama ne yaptıysam bu sorunu çözemedim ana kartımda çift ekran kartı slotu bulunmakta ikisini de denediğimde sonuç gene aynı oldu driverlerimi ve BIOS sürümümü en güncel sürümde tutuyorum örneğin, masaüstünde fareye dokunmadan bilgisayarda herhangi bir işlem yapmıyor iken saatlerce kapanmadığına şahit oldum ama aynı zamanda Chrome yüklerken ve hatta sadece masaüstünü yenile tuşuna bastığımda aynı zamanda formatta bile mavi ekran yedim minidump dosyalarını sizinle paylaşıyorum. Şimdiden teşekkür ederim 😀

minidump.rar
 
Son düzenleyen: Moderatör:
Minidump dosyasını herkese açık paylaşmanız gerekiyor. Erişim yok.

1665302217806.png



WHEA_UNCORRECTABLE_ERROR genelde işlemci ile alakalı oluyor. Undervolt/overclock gibi bir işlem yaptıysanız başınıza geliyor olabilir. İşlemciniz yeteri kadar güç çekemiyor olabilir.

Fan temizliği, toz temizliği ve termal macun bakımı yapıldı mı?

Direk ekran kartı değişiminden sonra başınıza gelmesi ilginç bir olay.
 
Minidump dosyasını herkese açık paylaşmanız gerekiyor. Erişim yok.

Eki Görüntüle 1539352


WHEA_UNCORRECTABLE_ERROR genelde işlemci ile alakalı oluyor. Undervolt/overclock gibi bir işlem yaptıysanız başınıza geliyor olabilir. İşlemciniz yeteri kadar güç çekemiyor olabilir.

Fan temizliği, toz temizliği ve termal macun bakımı yapıldı mı?

Direk ekran kartı değişiminden sonra başınıza gelmesi ilginç bir olay.
direk ekran kartından sonra başıma gelmeye başladı dosyaları tekrardan paylaştım sizinle.minidump.rar 2
 
Format attım demişsiniz, attıktan sonra AMD ile alakalı herhangi bir şey kurmadınız değil mi? Kurduysanız DDU yardımıyla AMD ile alakalı ne var ne yok her şeyi silin. Windows 10 otomatik olarak eski sürücüleri yüklemiş olabilir, yeni ekran kartınızla alakası nedir onu bilemiyorum.

Sonrasında şuradan Win 10 64-bit için chipset (yonga seti) sürücülerinizi indirip kurarsınız.


Daha sonrasında Windows'u Windows Update üzerinden en son çıkan sürüme güncelleyin.

Ayrıca, şuna benzer bir şeyler kullanıyor musunuz sisteminizde? (GPU cable extension)

1665320556213.png
1665320694025.png



Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff807662c0dce, Address of the instruction which caused the BugCheck
Arg3: fffff8076b483920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 781

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2562

    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: 5966

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x3b

    Key  : Bugcheck.Code.Register
    Value: 0x3b

    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:  100822-8218-01.dmp

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff807662c0dce

BUGCHECK_P3: fffff8076b483920

BUGCHECK_P4: 0

CONTEXT:  fffff8076b483920 -- (.cxr 0xfffff8076b483920)
rax=0000000000000000 rbx=fffffd820659c360 rcx=fffffd820659c360
rdx=2000000000000000 rsi=0000000000000000 rdi=ffff8981d839d7f0
rip=fffff807662c0dce rsp=fffffd820659c300 rbp=fffffd820659c389
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=ffffb88de047ab30 r12=ffffffffffffffff r13=0000000000000000
r14=0000000000000000 r15=ffff8981daef0080
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KxWaitForLockOwnerShip+0xe:
fffff807`662c0dce 48890a          mov     qword ptr [rdx],rcx ds:002b:20000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64-Shipping.exe

STACK_TEXT:
fffffd82`0659c300 fffff807`662098b7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0xe
fffffd82`0659c330 fffff807`662090f4     : ffff8981`daef0080 ffff8981`d839d790 ffff8981`dca83080 00000000`00000000 : nt!ExpAcquireResourceSharedLite+0x707
fffffd82`0659c3f0 fffff807`6c4fcf48     : ffff8981`d8ba9000 ffff8981`d8ba9000 00000000`00000000 fffffd82`0659c900 : nt!ExAcquireResourceSharedLite+0x44
fffffd82`0659c430 fffff807`6c4f12cc     : ffff8981`d8ba9000 fffffd82`0659cb80 fffffd82`0659c900 00000000`00000000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0xf8
fffffd82`0659c5d0 fffff807`6c4f07cd     : fffff807`663f0f34 ffff8981`00501802 ffffb88d`de949de0 00000048`db09f000 : dxgkrnl!DxgkSubmitCommandInternal+0xabc
fffffd82`0659cac0 fffff807`664090f1     : ffff8981`daef0080 00000000`00000000 00000000`00000000 ffff8981`00000000 : dxgkrnl!DxgkSubmitCommand+0x5d
fffffd82`0659cb00 00007ff9`d0b55ae4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000048`db09ef38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`d0b55ae4


SYMBOL_NAME:  dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+f8

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.1288

STACK_COMMAND:  .cxr 0xfffff8076b483920 ; kb

BUCKET_ID_FUNC_OFFSET:  f8

FAILURE_BUCKET_ID:  AV_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ea68fb24-d507-488d-00b3-5dce3c196ff6}

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: ffffe6046932e028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, 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: 1078

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5032

    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: 4285

    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:  100822-3187-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe6046932e028

BUGCHECK_P3: b6000000

BUGCHECK_P4: 100153

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT:
ffffd181`9873f938 fffff804`19cb448a     : 00000000`00000124 00000000`00000000 ffffe604`6932e028 00000000`b6000000 : nt!KeBugCheckEx
ffffd181`9873f940 fffff804`15c915b0     : 00000000`00000000 ffffe604`6932e028 ffffe604`651fb960 ffffe604`6932e028 : nt!HalBugCheckSystem+0xca
ffffd181`9873f980 fffff804`19db612e     : 00000000`00000000 ffffd181`9873fa29 ffffe604`6932e028 ffffe604`651fb960 : PSHED!PshedBugCheckSystem+0x10
ffffd181`9873f9b0 fffff804`19cb5db1     : ffffe604`691ccb50 ffffe604`691ccb50 ffffe604`651fb9b0 ffffe604`651fb960 : nt!WheaReportHwError+0x46e
ffffd181`9873fa90 fffff804`19cb6123     : 00000000`00000007 ffffe604`651fb9b0 ffffe604`651fb960 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffd181`9873fc00 fffff804`19cb6000     : ffffe604`650a6118 00000000`00000001 ffffd181`9873fe00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffd181`9873fc50 fffff804`19cb5545     : ffffe604`650a6118 ffffd181`9873fef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffd181`9873fc90 fffff804`19cb7d05     : ffffe604`650a6118 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffd181`9873fcc0 fffff804`19d0d419     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffd181`9873fcf0 fffff804`19c062fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffd181`9873fd20 fffff804`19c05fb7     : ffffe604`00000000 fffff804`19c05eec 00000000`00000004 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd181`9873fe60 fffff804`19ba6b39     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffff9485`f8fd22f0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwpLogContextSwapEvent+0x69


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

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: ffffbd0721a7d028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, 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: 1453

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2303

    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: 62

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

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

    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:  100822-8031-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffbd0721a7d028

BUGCHECK_P3: b6000000

BUGCHECK_P4: 100153

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT:
ffff9d00`2d73f938 fffff803`594b448a     : 00000000`00000124 00000000`00000000 ffffbd07`21a7d028 00000000`b6000000 : nt!KeBugCheckEx
ffff9d00`2d73f940 fffff803`581315b0     : 00000000`00000000 ffffbd07`21a7d028 ffffbd07`20dfa960 ffffbd07`21a7d028 : nt!HalBugCheckSystem+0xca
ffff9d00`2d73f980 fffff803`595b612e     : 00000000`00000000 ffff9d00`2d73fa29 ffffbd07`21a7d028 ffffbd07`20dfa960 : PSHED!PshedBugCheckSystem+0x10
ffff9d00`2d73f9b0 fffff803`594b5db1     : ffffbd07`25208bd0 ffffbd07`25208bd0 ffffbd07`20dfa9b0 ffffbd07`20dfa960 : nt!WheaReportHwError+0x46e
ffff9d00`2d73fa90 fffff803`594b6123     : 00000000`00000007 ffffbd07`20dfa9b0 ffffbd07`20dfa960 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffff9d00`2d73fc00 fffff803`594b6000     : ffffbd07`20ca6118 00000000`00000001 ffff9d00`2d73fe00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffff9d00`2d73fc50 fffff803`594b5545     : ffffbd07`20ca6118 ffff9d00`2d73fef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffff9d00`2d73fc90 fffff803`594b7d05     : ffffbd07`20ca6118 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffff9d00`2d73fcc0 fffff803`5950d419     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffff9d00`2d73fcf0 fffff803`594062fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff9d00`2d73fd20 fffff803`59405fb7     : ffffbd07`00000000 fffff803`59405eec ffff9801`f4d02330 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9d00`2d73fe60 fffff803`59280c56     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffff9801`f4d022b0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x6


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Followup:     MachineOwner
---------
 
Son düzenleme:

Yeni konular

Geri
Yukarı