• 22-02-2022, 00:38:25
    #1
    Arkadaşlar.

    Sıfır sistem topladım, whea uncorrectable error şeklinde mavi ekran hatası alıyorum.
    Ne zaman verdiği belli olmuyor genelde format sonrası defalarca veriyor windows 10'da hiç açılmıyor 11'de ise açılıyor zamanı belli olmayan şekilde mavi ekran veriyor.

    CPU, GPU, MEMORY, akla gelebilecek OCCT, Bechmark vs ne test varsa yapıyorum sorun yok ama durduk yere mavi ekran veriyor.

    Minidump kayıtları 2 adet vardı : inceler misiniz ben anlamıyorum

    Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
     
    Loading Dump File [C:\Users\Windows11\Desktop\022222-6453-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
     
     
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 22000 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Edition build lab: 22000.1.amd64fre.co_release.210604-1628
    Machine Name:
    Kernel base = 0xfffff807`34400000 PsLoadedModuleList = 0xfffff807`35029b90
    Debug session time: Tue Feb 22 00:11:23.822 2022 (UTC + 3:00)
    System Uptime: 0 days 0:09:19.422
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff807`348164c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffac80`83b27950=0000000000000124
    14: 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
    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: ffff9c0152353028, Address of the nt!_WHEA_ERROR_RECORD structure.
    Arg3: 00000000bc800800, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000000060c0859, 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_MEMORY_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_MEMORY_ERROR_SECTION                ***
    ***                                                                   ***
    *************************************************************************
     
    KEY_VALUES_STRING: 1
     
        Key  : Analysis.CPU.mSec
        Value: 2202
     
        Key  : Analysis.DebugAnalysisManager
        Value: Create
     
        Key  : Analysis.Elapsed.mSec
        Value: 5909
     
        Key  : Analysis.Init.CPU.mSec
        Value: 250
     
        Key  : Analysis.Init.Elapsed.mSec
        Value: 3679
     
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 98
     
        Key  : WER.OS.Branch
        Value: co_release
     
        Key  : WER.OS.Timestamp
        Value: 2021-06-04T16:28:00Z
     
        Key  : WER.OS.Version
        Value: 10.0.22000.1
     
     
    FILE_IN_CAB:  022222-6453-01.dmp
     
    BUGCHECK_CODE:  124
     
    BUGCHECK_P1: 0
     
    BUGCHECK_P2: ffff9c0152353028
     
    BUGCHECK_P3: bc800800
     
    BUGCHECK_P4: 60c0859
     
    BLACKBOXBSD: 1 (!blackboxbsd)
     
     
    BLACKBOXNTFS: 1 (!blackboxntfs)
     
     
    BLACKBOXPNP: 1 (!blackboxpnp)
     
     
    BLACKBOXWINLOGON: 1
     
    CUSTOMER_CRASH_COUNT:  1
     
    PROCESS_NAME:  System
     
    STACK_TEXT:  
    ffffac80`83b27948 fffff807`3490178b     : 00000000`00000124 00000000`00000000 ffff9c01`52353028 00000000`bc800800 : nt!KeBugCheckEx
    ffffac80`83b27950 fffff807`315d10c0     : 00000000`00000000 ffffac80`83b27a29 ffff9c01`52353028 ffff9c01`52353028 : nt!HalBugCheckSystem+0xeb
    ffffac80`83b27990 fffff807`34a3faa3     : 00000000`00000000 ffffac80`83b27a29 ffff9c01`52353028 ffff9c01`4ad4f6a0 : PSHED!PshedBugCheckSystem+0x10
    ffffac80`83b279c0 fffff807`3490317d     : ffff9c01`519f0900 ffff9c01`519f0900 ffff9c01`4ad4f6f0 178bfbff`7ef8320b : nt!WheaReportHwError+0x393
    ffffac80`83b27a90 fffff807`349035c8     : 00000000`0000000e ffff9c01`00000003 fffffd0c`3952c000 00000000`0000000e : nt!HalpMcaReportError+0xb1
    ffffac80`83b27bf0 fffff807`3490345c     : ffff9c01`4ad53a80 01d8275d`00000000 ffffac80`83b27e00 01d8275d`00000000 : nt!HalpMceHandlerCore+0x138
    ffffac80`83b27c50 fffff807`349028fb     : ffff9c01`4ad53a80 ffffac80`83b27ef0 00000000`00000000 00010018`0000005a : nt!HalpMceHandler+0xe0
    ffffac80`83b27c90 fffff807`3490527b     : ffff9c01`4ad53a80 01d8275d`7374d03a 01d8275d`7374d03a 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
    ffffac80`83b27cc0 fffff807`34965869     : 0043004d`0041020c 007e0035`00340037 005f0031`002e0031 00000000`00000045 : nt!HalHandleMcheck+0x3b
    ffffac80`83b27cf0 fffff807`348260fe     : 00010018`000000e2 00030000`000062f2 01d8275d`7374d03a 01d8275d`7374d03a : nt!KiHandleMcheck+0x9
    ffffac80`83b27d20 fffff807`34825d28     : 00000000`00000010 00000000`00000000 ffff9c01`523b2760 00000000`00000000 : nt!KxMcheckAbort+0x7e
    ffffac80`83b27e60 fffff807`34682815     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
    fffffd0c`39532b30 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAcquirePushLockExclusiveEx+0xa5
     
     
    MODULE_NAME: AuthenticAMD
     
    IMAGE_NAME:  AuthenticAMD.sys
     
    STACK_COMMAND:  .cxr; .ecxr ; kb
     
    FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
     
    OS_VERSION:  10.0.22000.1
     
    BUILDLAB_STR:  co_release
     
    OSPLATFORM_TYPE:  x64
     
    OSNAME:  Windows 10
     
    FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
     
    Followup:
  • 22-02-2022, 00:39:43
    #2
    Sistem bileşenlerini yazar mısın sana zahmet
  • 22-02-2022, 00:41:49
    #3
    aitsizbiri adlı üyeden alıntı: mesajı görüntüle
    Sistem bileşenlerini yazar mısın sana zahmet
    Asus rog strix b550-a anakart
    ryzen 7 5800x işlemci
    980 pro m.2 ssd
    gtx 980ti ekran kartı
    slicon power 8x4 32gb d4 ram
  • 22-02-2022, 00:47:19
    #4
    CtnbsOfficial adlı üyeden alıntı: mesajı görüntüle
    Asus rog strix b550-a anakart
    ryzen 7 5800x işlemci
    980 pro m.2 ssd
    gtx 980ti ekran kartı
    slicon power 8x4 32gb d4 ram
    Şuan pc demol adığım için minidup dosya k inceleyemiyorum lakin sürücü güncelemmelerini herhangi hazır bşr programdan yaptın mı bu birinci soru ikinci soru ana hatayı bulmak için minidup dosyanı incele hangi kısımlarda hata olduğunun ekranını atabilir misin.
  • 22-02-2022, 00:57:28
    #5
    aitsizbiri adlı üyeden alıntı: mesajı görüntüle
    Şuan pc demol adığım için minidup dosya k inceleyemiyorum lakin sürücü güncelemmelerini herhangi hazır bşr programdan yaptın mı bu birinci soru ikinci soru ana hatayı bulmak için minidup dosyanı incele hangi kısımlarda hata olduğunun ekranını atabilir misin.
    Hocam ilgin için çok teşekkür ederim.

    Olaylar şöyle gelişti, sistemin parçalarını tespit ettim sipariş verdim ve geldi. Fakat sıvı soğutmayı unuttum aklımdan çıktı. Elimde AM4 eski bir soğutma vardı onu taktım. Neyse format attım işletim sistemini kurdum zırt pırt mavi ekran veriyordu dayanamadım gittim eski bir am4 işlemci ttaktım dandik soğutmayla 2 gün kullandım.

    Sonra sıvı soğutma bugun geldi sabah. İşlemciyle birlikte tekrar taktım ve mavi ekran vs yoktu, taa ki format atana kadar şimdi format attım bidaha başladı mavi ekranlar. Driverları vs sitesinden kurdum tekrardan(AMD'nin sitesinden B550 Chipset Drivar) sanırım şuan mavi ekran vermiyor ama verir mi bilemem minidump ekran görüntüsü ekte.

    Driver kurmasam da mavi ekran vermemesi lazım değil mi bunun.

    Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Windows11\Desktop\022222-6453-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 22000 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Edition build lab: 22000.1.amd64fre.co_release.210604-1628
    Machine Name:
    Kernel base = 0xfffff807`34400000 PsLoadedModuleList = 0xfffff807`35029b90
    Debug session time: Tue Feb 22 00:11:23.822 2022 (UTC + 3:00)
    System Uptime: 0 days 0:09:19.422
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff807`348164c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffac80`83b27950=0000000000000124
    14: 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
    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: ffff9c0152353028, Address of the nt!_WHEA_ERROR_RECORD structure.
    Arg3: 00000000bc800800, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000000060c0859, 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_MEMORY_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_MEMORY_ERROR_SECTION                ***
    ***                                                                   ***
    *************************************************************************
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 2202
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 5909
    
        Key  : Analysis.Init.CPU.mSec
        Value: 250
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 3679
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 98
    
        Key  : WER.OS.Branch
        Value: co_release
    
        Key  : WER.OS.Timestamp
        Value: 2021-06-04T16:28:00Z
    
        Key  : WER.OS.Version
        Value: 10.0.22000.1
    
    
    FILE_IN_CAB:  022222-6453-01.dmp
    
    BUGCHECK_CODE:  124
    
    BUGCHECK_P1: 0
    
    BUGCHECK_P2: ffff9c0152353028
    
    BUGCHECK_P3: bc800800
    
    BUGCHECK_P4: 60c0859
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    STACK_TEXT:  
    ffffac80`83b27948 fffff807`3490178b     : 00000000`00000124 00000000`00000000 ffff9c01`52353028 00000000`bc800800 : nt!KeBugCheckEx
    ffffac80`83b27950 fffff807`315d10c0     : 00000000`00000000 ffffac80`83b27a29 ffff9c01`52353028 ffff9c01`52353028 : nt!HalBugCheckSystem+0xeb
    ffffac80`83b27990 fffff807`34a3faa3     : 00000000`00000000 ffffac80`83b27a29 ffff9c01`52353028 ffff9c01`4ad4f6a0 : PSHED!PshedBugCheckSystem+0x10
    ffffac80`83b279c0 fffff807`3490317d     : ffff9c01`519f0900 ffff9c01`519f0900 ffff9c01`4ad4f6f0 178bfbff`7ef8320b : nt!WheaReportHwError+0x393
    ffffac80`83b27a90 fffff807`349035c8     : 00000000`0000000e ffff9c01`00000003 fffffd0c`3952c000 00000000`0000000e : nt!HalpMcaReportError+0xb1
    ffffac80`83b27bf0 fffff807`3490345c     : ffff9c01`4ad53a80 01d8275d`00000000 ffffac80`83b27e00 01d8275d`00000000 : nt!HalpMceHandlerCore+0x138
    ffffac80`83b27c50 fffff807`349028fb     : ffff9c01`4ad53a80 ffffac80`83b27ef0 00000000`00000000 00010018`0000005a : nt!HalpMceHandler+0xe0
    ffffac80`83b27c90 fffff807`3490527b     : ffff9c01`4ad53a80 01d8275d`7374d03a 01d8275d`7374d03a 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
    ffffac80`83b27cc0 fffff807`34965869     : 0043004d`0041020c 007e0035`00340037 005f0031`002e0031 00000000`00000045 : nt!HalHandleMcheck+0x3b
    ffffac80`83b27cf0 fffff807`348260fe     : 00010018`000000e2 00030000`000062f2 01d8275d`7374d03a 01d8275d`7374d03a : nt!KiHandleMcheck+0x9
    ffffac80`83b27d20 fffff807`34825d28     : 00000000`00000010 00000000`00000000 ffff9c01`523b2760 00000000`00000000 : nt!KxMcheckAbort+0x7e
    ffffac80`83b27e60 fffff807`34682815     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
    fffffd0c`39532b30 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAcquirePushLockExclusiveEx+0xa5
    
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD.sys
    
    STACK_COMMAND:  .cxr; .ecxr ; kb
    
    FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
    
    OS_VERSION:  10.0.22000.1
    
    BUILDLAB_STR:  co_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}
    
    Followup:     MachineOwner
    ---------

    Ek olarak
  • 22-02-2022, 01:09:02
    #6
    aitsizbiri adlı üyeden alıntı: mesajı görüntüle
    Şuan pc demol adığım için minidup dosya k inceleyemiyorum lakin sürücü güncelemmelerini herhangi hazır bşr programdan yaptın mı bu birinci soru ikinci soru ana hatayı bulmak için minidup dosyanı incele hangi kısımlarda hata olduğunun ekranını atabilir misin.
    sorun devam ediyor