Çözüldü WHEA_UNCORRECTABLE_ERROR hatası

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

penisilin

Centipat
Katılım
16 Eylül 2022
Mesajlar
11
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Arkadaşlar bilgisayarı açıyorum ve ardından 2-3 dakika sonra WHEA_UNCORRECTABLE_ERROR hatasını alıyorum. Memtest ile 2 kere test yaptım bir hata çıkmadı. Ayrıca diğer bilgisayarımdaki SSD'yi takmayı denedim sonuç değişmedi. Buraya da minidump dosyalarını bırakıyorum. minidump.rar
 
Çözüm
Hocam hiç overclock yapmadım. Şimdi bir termal macun aldım iyice tozları temizleyip macunu sürdüm fakat yine sorunum düzelmedi.

Hocam hiç overclock yapmadım. Şimdi bir termal macun aldım iyice tozları temizleyip macunu sürdüm fakat yine sorunum düzelmedi.
Daha önce işlemci ile alakalı bir overclock veya undervolt gibi bir şey yaptınız mı? Ayrıca işlemciniz çok ısınıyor olabilir. Toz temizliği, fan temizliği ve termal macun bakımı yapıldı mı yakın zamanda?

Aşağıdaki konuyla epey bir benziyor hatalarınız.


Döküm:

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: ffffc88e6d4e1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000008117a, 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                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6265

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

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

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

    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:  091622-5984-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc88e6d4e1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 8117a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffe000`701cf8e8 fffff802`7e4b44da     : 00000000`00000124 00000000`00000000 ffffc88e`6d4e1028 00000000`be000000 : nt!KeBugCheckEx
ffffe000`701cf8f0 fffff802`7b8415b0     : 00000000`00000000 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 ffffc88e`6d4e1028 : nt!HalBugCheckSystem+0xca
ffffe000`701cf930 fffff802`7e5b662e     : 00000000`00000000 ffffe000`701cf9d9 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 : PSHED!PshedBugCheckSystem+0x10
ffffe000`701cf960 fffff802`7e4b5e01     : ffffc88e`6d81f500 ffffc88e`6d81f500 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 : nt!WheaReportHwError+0x46e
ffffe000`701cfa40 fffff802`7e4b6173     : 00000000`00000002 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 00000000`00000002 : nt!HalpMcaReportError+0xb1
ffffe000`701cfbb0 fffff802`7e4b6050     : ffffc88e`6a6e58c0 00a083f7`00000001 00000000`00000000 0000013f`840ff685 : nt!HalpMceHandlerCore+0xef
ffffe000`701cfc00 fffff802`7e4b62a1     : 00000000`00000004 00000000`00000001 00000000`00000000 89486024`448d4802 : nt!HalpMceHandler+0xe0
ffffe000`701cfc40 fffff802`7e4b550b     : 00000000`00000000 00000000`00000000 ffffe000`701cfed0 48f88b48`ffc71734 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffe000`701cfc70 fffff802`7e4b7d55     : ffffc88e`6a6e58c0 48000001`8825048b 0000a0a7`8348d78b 48004067`83660000 : nt!HalpHandleMachineCheck+0x5f
ffffe000`701cfca0 fffff802`7e50d809     : 878b4800`00009887 004447c6`000000b8 89480109`b840c766 8b48e058`8948e870 : nt!HalHandleMcheck+0x35
ffffe000`701cfcd0 fffff802`7e4080fa     : bb40c6cb`8b48f848 d88bffb9`5f52e8e0 481b7500`0001033d 4c8d4800`20246483 : nt!KiHandleMcheck+0x9
ffffe000`701cfd00 fffff802`7e407db7     : 00000000`00000000 fffff802`7e407cec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe000`701cfe40 fffff802`a8af138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffae8c`e103f5b8 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_MEMORY__UNKNOWN_FATAL_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4a6bacb6-389a-a60e-b7da-1fbf7ba2dc2f}

Followup:     MachineOwner
---------
Bir de ek olarak Windows'u güvenli modda açınca hiç hata vermiyor hocam.

Arkadaşlar uykusuz geçen gecelerin ardından nihayet şu illetten kurtulabildim. Şimdi herkese anlatayım umarım birinize yardımcı olabilirim. Hatanın ana kaynağı entegre grafik kartıymış. Format attıktan sonra direkt olarak bilgisayarınızı internete bağlayıp Windows Update aracılığıyla driverlarınızı güncellediğiniz zaman, bendeki gibi eski laptoplar Whea_uncontrollable hatası veriyor. Hatadan kaçınmak için yapmanız gereken, format atarken ve attıktan sonra asla ama asla internete bağlanmayıp gerekli bütün driverları bilgisayar üreticinizin destek sayfasından başka bir disk ile kendi bilgisayarınıza atıp öyle kurmanız. Ardından Windows Updater'ı normal olarak kullanabilirsiniz. Windows'un kendi kurduğu driverlar son sürüm olduğu için eski bilgisayarlarda hataya sebep olabiliyor.
Daha önce işlemci ile alakalı bir overclock veya undervolt gibi bir şey yaptınız mı? Ayrıca işlemciniz çok ısınıyor olabilir. Toz temizliği, fan temizliği ve termal macun bakımı yapıldı mı yakın zamanda?

Aşağıdaki konuyla epey bir benziyor hatalarınız.


Döküm:

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: ffffc88e6d4e1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000008117a, 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                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6265

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

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

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

    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:  091622-5984-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc88e6d4e1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 8117a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffe000`701cf8e8 fffff802`7e4b44da     : 00000000`00000124 00000000`00000000 ffffc88e`6d4e1028 00000000`be000000 : nt!KeBugCheckEx
ffffe000`701cf8f0 fffff802`7b8415b0     : 00000000`00000000 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 ffffc88e`6d4e1028 : nt!HalBugCheckSystem+0xca
ffffe000`701cf930 fffff802`7e5b662e     : 00000000`00000000 ffffe000`701cf9d9 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 : PSHED!PshedBugCheckSystem+0x10
ffffe000`701cf960 fffff802`7e4b5e01     : ffffc88e`6d81f500 ffffc88e`6d81f500 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 : nt!WheaReportHwError+0x46e
ffffe000`701cfa40 fffff802`7e4b6173     : 00000000`00000002 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 00000000`00000002 : nt!HalpMcaReportError+0xb1
ffffe000`701cfbb0 fffff802`7e4b6050     : ffffc88e`6a6e58c0 00a083f7`00000001 00000000`00000000 0000013f`840ff685 : nt!HalpMceHandlerCore+0xef
ffffe000`701cfc00 fffff802`7e4b62a1     : 00000000`00000004 00000000`00000001 00000000`00000000 89486024`448d4802 : nt!HalpMceHandler+0xe0
ffffe000`701cfc40 fffff802`7e4b550b     : 00000000`00000000 00000000`00000000 ffffe000`701cfed0 48f88b48`ffc71734 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffe000`701cfc70 fffff802`7e4b7d55     : ffffc88e`6a6e58c0 48000001`8825048b 0000a0a7`8348d78b 48004067`83660000 : nt!HalpHandleMachineCheck+0x5f
ffffe000`701cfca0 fffff802`7e50d809     : 878b4800`00009887 004447c6`000000b8 89480109`b840c766 8b48e058`8948e870 : nt!HalHandleMcheck+0x35
ffffe000`701cfcd0 fffff802`7e4080fa     : bb40c6cb`8b48f848 d88bffb9`5f52e8e0 481b7500`0001033d 4c8d4800`20246483 : nt!KiHandleMcheck+0x9
ffffe000`701cfd00 fffff802`7e407db7     : 00000000`00000000 fffff802`7e407cec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe000`701cfe40 fffff802`a8af138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffae8c`e103f5b8 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_MEMORY__UNKNOWN_FATAL_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4a6bacb6-389a-a60e-b7da-1fbf7ba2dc2f}

Followup:     MachineOwner
---------
 
Hocam hiç overclock yapmadım. Şimdi bir termal macun aldım iyice tozları temizleyip macunu sürdüm fakat yine sorunum düzelmedi.

Hocam hiç overclock yapmadım. Şimdi bir termal macun aldım iyice tozları temizleyip macunu sürdüm fakat yine sorunum düzelmedi.
Daha önce işlemci ile alakalı bir overclock veya undervolt gibi bir şey yaptınız mı? Ayrıca işlemciniz çok ısınıyor olabilir. Toz temizliği, fan temizliği ve termal macun bakımı yapıldı mı yakın zamanda?

Aşağıdaki konuyla epey bir benziyor hatalarınız.


Döküm:

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: ffffc88e6d4e1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000008117a, 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                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6265

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

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

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

    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:  091622-5984-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc88e6d4e1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 8117a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffe000`701cf8e8 fffff802`7e4b44da     : 00000000`00000124 00000000`00000000 ffffc88e`6d4e1028 00000000`be000000 : nt!KeBugCheckEx
ffffe000`701cf8f0 fffff802`7b8415b0     : 00000000`00000000 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 ffffc88e`6d4e1028 : nt!HalBugCheckSystem+0xca
ffffe000`701cf930 fffff802`7e5b662e     : 00000000`00000000 ffffe000`701cf9d9 ffffc88e`6d4e1028 ffffc88e`6a9e13f0 : PSHED!PshedBugCheckSystem+0x10
ffffe000`701cf960 fffff802`7e4b5e01     : ffffc88e`6d81f500 ffffc88e`6d81f500 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 : nt!WheaReportHwError+0x46e
ffffe000`701cfa40 fffff802`7e4b6173     : 00000000`00000002 ffffc88e`6a9e1440 ffffc88e`6a9e13f0 00000000`00000002 : nt!HalpMcaReportError+0xb1
ffffe000`701cfbb0 fffff802`7e4b6050     : ffffc88e`6a6e58c0 00a083f7`00000001 00000000`00000000 0000013f`840ff685 : nt!HalpMceHandlerCore+0xef
ffffe000`701cfc00 fffff802`7e4b62a1     : 00000000`00000004 00000000`00000001 00000000`00000000 89486024`448d4802 : nt!HalpMceHandler+0xe0
ffffe000`701cfc40 fffff802`7e4b550b     : 00000000`00000000 00000000`00000000 ffffe000`701cfed0 48f88b48`ffc71734 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffe000`701cfc70 fffff802`7e4b7d55     : ffffc88e`6a6e58c0 48000001`8825048b 0000a0a7`8348d78b 48004067`83660000 : nt!HalpHandleMachineCheck+0x5f
ffffe000`701cfca0 fffff802`7e50d809     : 878b4800`00009887 004447c6`000000b8 89480109`b840c766 8b48e058`8948e870 : nt!HalHandleMcheck+0x35
ffffe000`701cfcd0 fffff802`7e4080fa     : bb40c6cb`8b48f848 d88bffb9`5f52e8e0 481b7500`0001033d 4c8d4800`20246483 : nt!KiHandleMcheck+0x9
ffffe000`701cfd00 fffff802`7e407db7     : 00000000`00000000 fffff802`7e407cec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe000`701cfe40 fffff802`a8af138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffae8c`e103f5b8 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_MEMORY__UNKNOWN_FATAL_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4a6bacb6-389a-a60e-b7da-1fbf7ba2dc2f}

Followup:     MachineOwner
---------
Bir de ek olarak Windows'u güvenli modda açınca hiç hata vermiyor hocam.

Arkadaşlar uykusuz geçen gecelerin ardından nihayet şu illetten kurtulabildim. Şimdi herkese anlatayım umarım birinize yardımcı olabilirim. Hatanın ana kaynağı entegre grafik kartıymış. Format attıktan sonra direkt olarak bilgisayarınızı internete bağlayıp Windows Update aracılığıyla driverlarınızı güncellediğiniz zaman, bendeki gibi eski laptoplar Whea_uncontrollable hatası veriyor. Hatadan kaçınmak için yapmanız gereken, format atarken ve attıktan sonra asla ama asla internete bağlanmayıp gerekli bütün driverları bilgisayar üreticinizin destek sayfasından başka bir disk ile kendi bilgisayarınıza atıp öyle kurmanız. Ardından Windows Updater'ı normal olarak kullanabilirsiniz. Windows'un kendi kurduğu driverlar son sürüm olduğu için eski bilgisayarlarda hataya sebep olabiliyor.
 
Son düzenleme:
Çözüm

Yeni konular

Geri
Yukarı