Çözüldü Legion Y540 Kioxia Exceria Pro SSD Değişimi Sonrası Mavi Ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Fornaks

Uzman
Katılım
8 Mart 2024
Mesajlar
12
Beğeniler
6
  • Anakart:
  • İşlemci: i7 9750H
  • Ekran Kartı: GTX 1660 Ti
  • İşletim Sistemi: Windows 11

Merhaba. Legion Y540 laptopuma Kioxia Exceria Pro SSD satın aldım ve bugün temiz yükleme ile kullanmaya başladım. Tüm güncellemeleri yaptıktan sonra 2 defa mavi ekran hatası aldım. Bunun nedeni ne olabilir? Minidump dosyası linktedir.

 
Çözüm
Chipset sürücüsünü güncelleyin.

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
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: ffffb80fa4213028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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: 2203

    Key  : Analysis.Elapsed.mSec
    Value: 7413

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb80fa4213028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB:  032524-15625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

STACK_TEXT: 
ffffa681`c10578e8 fffff804`324ff80b     : 00000000`00000124 00000000`00000000 ffffb80f`a4213028 00000000`be000000 : nt!KeBugCheckEx
ffffa681`c10578f0 fffff804`2f7d10c0     : 00000000`00000000 ffffa681`c10579c9 ffffb80f`a4213028 ffffb80f`9a1505e0 : nt!HalBugCheckSystem+0xeb
ffffa681`c1057930 fffff804`3260ed3f     : 00000000`00000000 ffffa681`c10579c9 ffffb80f`a4213028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffffa681`c1057960 fffff804`3250123a     : ffffb80f`a42d5a10 ffffb80f`a42d5a10 ffffb80f`9a150630 fffff804`3237df3e : nt!WheaReportHwError+0x38f
ffffa681`c1057a30 fffff804`32501690     : 00000000`00000004 ffffb80f`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffa681`c1057ba0 fffff804`32501524     : ffffb80f`9a14dfc0 ffffffff`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffa681`c1057c00 fffff804`325017c9     : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffa681`c1057c40 fffff804`32500982     : 00000000`00000000 00000000`00000000 ffffa681`c1057ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa681`c1057c70 fffff804`3250314b     : ffffb80f`9a14dfc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
ffffa681`c1057ca0 fffff804`32569769     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffa681`c1057cd0 fffff804`3242997e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffa681`c1057d00 fffff804`32429593     : 00000000`00000000 00000000`00000000 00000000`003cccf4 ffffa681`c1057ed0 : nt!KxMcheckAbort+0x7e
ffffa681`c1057e40 00000000`6fce0340     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
00000000`00b5ed4c 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6fce0340


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Chipset sürücüsünü güncelleyin.

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
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: ffffb80fa4213028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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: 2203

    Key  : Analysis.Elapsed.mSec
    Value: 7413

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb80fa4213028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB:  032524-15625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

STACK_TEXT: 
ffffa681`c10578e8 fffff804`324ff80b     : 00000000`00000124 00000000`00000000 ffffb80f`a4213028 00000000`be000000 : nt!KeBugCheckEx
ffffa681`c10578f0 fffff804`2f7d10c0     : 00000000`00000000 ffffa681`c10579c9 ffffb80f`a4213028 ffffb80f`9a1505e0 : nt!HalBugCheckSystem+0xeb
ffffa681`c1057930 fffff804`3260ed3f     : 00000000`00000000 ffffa681`c10579c9 ffffb80f`a4213028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffffa681`c1057960 fffff804`3250123a     : ffffb80f`a42d5a10 ffffb80f`a42d5a10 ffffb80f`9a150630 fffff804`3237df3e : nt!WheaReportHwError+0x38f
ffffa681`c1057a30 fffff804`32501690     : 00000000`00000004 ffffb80f`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffa681`c1057ba0 fffff804`32501524     : ffffb80f`9a14dfc0 ffffffff`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffa681`c1057c00 fffff804`325017c9     : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffa681`c1057c40 fffff804`32500982     : 00000000`00000000 00000000`00000000 ffffa681`c1057ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa681`c1057c70 fffff804`3250314b     : ffffb80f`9a14dfc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
ffffa681`c1057ca0 fffff804`32569769     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffa681`c1057cd0 fffff804`3242997e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffa681`c1057d00 fffff804`32429593     : 00000000`00000000 00000000`00000000 00000000`003cccf4 ffffa681`c1057ed0 : nt!KxMcheckAbort+0x7e
ffffa681`c1057e40 00000000`6fce0340     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
00000000`00b5ed4c 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6fce0340


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 
Çözüm

Intel güncelleme denetleyiciyi kullandığımda sadece Wi-Fi ve Bluetooth güncellemesi yapıyor. Manual driver indirdiğimde ise graphic driver indiriyor. Yüklenebilecek bir sürücü bulunamadı hatası alıyorum.
 

Dosya Ekleri

  • Adsız.webp
    20,6 KB · Görüntüleme: 83
Aldığın hata Microsoft tarafından donanımsal olarak gösteriliyor. Whea yapısı (Windows Hardware Error Architecture) yani sistemdeki donanım hatalarını raporlayan işlemler olarak geçer kısaca. nt!WheaReportHwError+0x38f

[CODE highlight="6,7"] kd> k
# Child-SP RetAddr Call Site
00 ffffa681`c10578e8 fffff804`324ff80b nt!KeBugCheckEx
01 ffffa681`c10578f0 fffff804`2f7d10c0 nt!HalBugCheckSystem+0xeb
02 ffffa681`c1057930 fffff804`3260ed3f PSHED!PshedBugCheckSystem+0x10
03 ffffa681`c1057960 fffff804`3250123a nt!WheaReportHwError+0x38f // sorun bulundu
04 ffffa681`c1057a30 fffff804`32501690 nt!HalpMcaReportError+0xb2 // raporlama
05 ffffa681`c1057ba0 fffff804`32501524 nt!HalpMceHandlerCore+0x138
06 ffffa681`c1057c00 fffff804`325017c9 nt!HalpMceHandler+0xe0
07 ffffa681`c1057c40 fffff804`32500982 nt!HalpMceHandlerWithRendezvous+0xc9
08 ffffa681`c1057c70 fffff804`3250314b nt!HalpHandleMachineCheck+0x62
09 ffffa681`c1057ca0 fffff804`32569769 nt!HalHandleMcheck+0x3b
0a ffffa681`c1057cd0 fffff804`3242997e nt!KiHandleMcheck+0x9
0b ffffa681`c1057d00 fffff804`32429593 nt!KxMcheckAbort+0x7e
0c ffffa681`c1057e40 00000000`6fce0340 nt!KiMcheckAbort+0x2d3[/CODE]

Bu hata başlığı altında çok fazla makale vardır ve artmaya da devam ediyor. Şöyle ki donanım diyoruz ama bu donanım hatası her şeyden dolayı olabilir. Sistemine taktığın USB'ler, mouse, klavye gibi cihazlar da buna dahil. Bu yüzden çözümlemesi zordur. Hata veren şey işlemci vendorudur. Bu da hiçbir işimize yaramaz. Ancak verilen bilgiler işimizi kolaylaştırırsa sorunun altından kolayca kalkabilecek duruma geliriz.


Dediğim gibi format attığın zaman kullandıysan USB bile sorun açabilecek durumda olduğu için beklemek bile sorunu çözebilir. Hocamızın dedikleri de sorunu çözebilir. Şu anlık sistem kayıt aldı mı ona bakmamız belki sorunu buldurabilir. Bunun için olay logu yönetim olayları kısmı iş görür.
Yapılmış olan işlemler iş görürse ne mutlu sisteminizi kullanırsınız. Ama hatalar devam ederse SSD'yi sistemden çıkarıp sistemi test etmeniz gerekebilir. Sırf bu donanım sorunlarını bulma çabası bile insanı yoruyor.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…