Windows 10 WHEA_UNCORRECTABLE_ERROR mavi ekran hatası

Bone Doctor

Kilopat
Katılım
10 Mart 2014
Mesajlar
28
Herkese selam. Uzun zamandır çok nadir de olsa belirli aralıklarla mavi ekran hatası alıyordum.(WHEA_UNCORRECTABLE_ERROR) Her seferinde bu mavi ekran hatasını aldım. Oyun oynarken yaşamadım ancak sürekli masaüstünde denk geldim. RAM test yaptım ve sorun çıkmadı. SSD HDD taraması yaptım yine sorun çıkmadı. Son olarak format attım ancak bugün tekrar başıma geldi. Bunun öncesinde de formattan sonra sadece 1 kere hatasız bir kilitlenme oldu mavi ekran olmadan.
935.4 KB folder on MEGA bu da minidump.
 
Son düzenleyen: Moderatör:
Sorunun olası sebepleri:
  • Yetersiz işlemci güç beslemesi
  • Arızalı işlemci
  • Aşırı monte edilmiş soğutucu
*******************************************************************************
* *
* 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
WHEA_ERROR_RECORD structure that describes the error conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffad81e7b9c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200151, Low order 32-bits of the MCi_STATUS value.

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

*** WARNING: Unable to verify timestamp for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3202

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5DL7M86

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 13843

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

Key : Analysis.System
Value: CreateObject

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

Key : WHEA.MCiStatus.Code
Value: 0xbe00000000200151

Key : WHEA.MCiStatus.McaError
Value: 0x0151

Key : WHEA.MCiStatus.ModelError
Value: 0x0020

Key : WHEA.MCiStatus.Reserved
Value: 0x00000000


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffad81e7b9c028

BUGCHECK_P3: be000000

BUGCHECK_P4: 200151

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff800`4ba958e8 fffff800`45ec000a : 00000000`00000124 00000000`00000000 ffffad81`e7b9c028 00000000`be000000 : nt!KeBugCheckEx
fffff800`4ba958f0 fffff800`44a015b0 : 00000000`00000000 ffffad81`e7b9c028 ffffad81`e75f92e0 ffffad81`e7b9c028 : nt!HalBugCheckSystem+0xca
fffff800`4ba95930 00000000`00000000 : ffffad81`e7b9c028 ffffad81`e75f92e0 ffffad81`e7b9c028 fffff800`4ba959d9 : PSHED+0x15b0


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0020_MCACOD0151_PCC_UC_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {6a9665ba-e793-598a-a159-0d8e3dd8c88b}

Followup: MachineOwner
---------
 
Öncelikle cevabınız için çok teşekkür ederim hocam. İşlemci soğutucusunu sonradan değiştirmiştim Dark Freezer x124 kullanıyorum. Montaj sırasında çok sıkmamaya özellikle dikkat etmiştim. Cevabınıza bakaraktan sorun yazılımsal falan değil sanırım.
 
Overclock yaptıysanız kaldırın ve BİOS'u default ayarlarına getirin. Ayrıca İntelle alakalı bir sürücünüz varsa güncelleyin veya kaldırıp tekrar kurun. Ayrıca çok ısınma da bu soruna sebebiyet veriyor olabilir ısı değerlerinizi paylaşın.

İntel: registered: Processor Diagnostic Tool'u indirin ve çalıştırın bir sorun çıkacak mı bakalım.
https: //downloadcenter.intel.com/download/19792
 
Herhangi bir hız aşırtma işlemi yapmadım ve ek olarak BİOS'u default haline getirmeyi denedim. Tool'a hemen bakıyorum. Isılar konusunda İşlemci yükte 55-65 ekran kartı ise max 75 gördüm. Odamda herhangi bir klima yok bu yüzden ısılar normalden daha yüksek.
 

Yeni konular

Geri
Yukarı