WHEA_UNCORRECTABLE_ERROR Mavi Ekran Hatası

ohmyrab · 12 Ağustos 2019

Merhaba,

Şimdi lütfen işin teknik kısmını bir kenara bırakıp zamanı etkin kullanabilmek adına PC'nin başına gelen hikayeyi dinleyin.

Tam bir yıl önce bilgisayarım bozulup sürekli mavi ekran vermeye başladı. Eş zamanlı olarak buzdolabımızın da elektrik aksamı bozuldu (aynı gün diyemem ama o haftalarda), 3 haftalık araştırmam neticesinde hiçbir sonuç alamadım. Ne denediysem olmadı. Ardından sorun ben farkında olmadan ortadan kalktı. 11 ay boyunca bu haftaya kadar sorunsuz bir şekilde kullandım. Ancak önce iki günde bir ve akabinde 10 dakikada bir mavi ekran almaya başladım. Bilgisayarda teknik anlamda hiçbir fizilsel temas olmadı bu süre boyunca, yani el ile dokunmadık, içini açmadık vs. ama ne olduysa yine bu sorun bir şekilde başıma geldi. Ve ne tesadüf ki geçen hafta buzdolabımız bozuldu. Yine benzer sebepten. Tamirci evden çıkarken akım korumalı priz önerdi yine, elektrikten şüphelendi belli ki. Binada jeneratör var, elektrik kesildikten 10 sn sonra devreye giriyor (bu sürede PC kapanıyor tabii).

Şimdi gördüğünüz üzere pek bir değişiklik yapmadığım halde başıma gelen ve sebebini anlayamadığım şekilde geçmişte ortadan kalkan bir sorun var.

Parçalardan biri arızalı olsaydı kendiliğinden düzelip 11 ay kullanmama müsaade etmezdi. O yüzden sorunun tespitinde bu hususa dikkat edelim. Bilgisayar arada güncelleme yapıyordu PC'yi kapatırken görüyordum. PC'yi yeniden kurunca fayda etmiyor. Belki kalıntıları iyi silemiyorumdur. Driverlerim da güncel, BIOS'um da.

O halde, bu sorunu nasıl çözeceğim? Bu anlattıklarım istikametinde sorun hakkında fikir edinebilen varsa yardımlarını bekliyorum.

Hata kodları:

WHEA_UNCORRECTABLE_ERROR
IRQL_NOT_LESS_OR_EQUAL
CLOCK_WATCHDOG_TIMEOUT

Bunlar sırayla geliyor. Normalde sadece oyun yahut browser açıkken gelen mavi ekran, enerji ayarını yüksek performansa getirince dakikada bir vermeye başlıyor.

Recep Baltaş · 12 Ağustos 2019

Hikayenden yapabileceğim tek çıkarım havaların ısınmasının bilgisayarında soruna sebep oluyor olması. Aynı şey soğutma için daha fazla çalışmak zorunda kalan buzdolabın için de geçerli olabilir...

Öte yandan bu uzun hikayeyi anlatana kadar bize bilgisayarının özelliklerini yazmaya ne dersin? Hazır elin değmişken bir de raporları paylaş...

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...

www.technopat.net

ohmyrab · 14 Ağustos 2019

Tekrardan merhaba, bilgisayarı ancak açabildim (bayram falan da girince tabii). Özür dilerim gecikme için.

Bilgisayarın tozunu püsürüğünü kabaca aldık.
Macunu yeniledik.
RAM slotunu değiştirdik.
Memory Test yaptık.
Hem SSD hem de Hard Disk ile sorunu test ettik.
Driverleri güncelledik.

Fakat sorun devam ediyor. En son SSD'yi Secure Erase+ ile sıfırlayıp yeniden Windows kurduk ancak daha masaüstü 2 saniye kadar bile göremedim, şifreyi giresiye mavi ekran veriyor. Bu mesajı Hard Disk'e geçen yıl kurduğum Windows'tan atıyorum. (Bu da veriyor idle'de saatte bir falan).

Bu az önce kurulumunu yaptığımız SSD Windows 10'un minidump'u.
Minidump (SSD)
Bu da 2018'de kurduğumuz Harddiskteki Win10'un minidumpu
Minidump (Harddisk)

Gerçekten tatilim hiç oldu (yaz okulum sorundan 3 gün önce bitmişti). Paraya kıyıp bilgisayarcıya vereyim diyorum ama sorunu anlamayıp parça değiştirip yollayacaklar ve sorun devam edecek. Tespiti yapılmadan elim kolum bağlı. Umarım çözülür, hangi dökümanı isterseniz ivedilikle yollayacağım şu andan itibaren. Parçaları kendimiz toplamıştık, garantiyi son çare olarak görüyorum çünkü süreç çok yavaş işliyor. Minimum 2 ay sürer o şekilde. Sonuçta 11 ay kendiliğinden çözülmüş bir problemden bahsediyoruz.

Anakart: MSI B250M PRO-VD
Ekran kartı: NVIDIA GTX 1050 Ti ( şu an takılı değil, yine de veriyor. )
RAM: HyperX Furry 8 GB
İşlemci: G4560 Intel
SSD: James Monkey 240 GB
Harddisk: Western Digital Blue 1TB

Değerli büyüklerim, yardımcı olacağınızı bilmekle birlikte gözünüzün önünüze düşsün diye etiketliyorum. Nedir bu sorun, nasıl bu beladan kurtulurum. Ben biraz kendi tecrübelerimden elde ettiğim çıkarımları paylaşıp işinizi kolaylaştırayım.

Diğer parçalardan biri fiziksel olarak bozuk olsa, 11 ay kullanmama izin vermezdi. Tamamen önceki ile aynı sorun karşımda.
Bilgisayar gerçekten çok tozlanmıştı, ben de ısınmasının üzerinde duruyordum ama termal macun sürüp tozunu aldıktan sonra SYS, CPU sıcaklıkları doğal seyrinde. Ve yine de mavi ekran yiyorum.
Akım dalgalanması olsa ki önlem için bu defa tunçmatik akım korumalı priz almıştık (sorundan sonra). Yine mavi ekran problemi devam ediyor.
SSD ve HDD'yi ayrı ayrı test ettik. Sorun devam etmekte.
Çok uzun süreler test etme imkanım olmadı ama güvenli modda mavi ekran yemiyor gibiyim.
Ekran kartını söküp onboarddan bağlandık. Sorun devam ediyor.
Ccleaner ile zamanlanmış görevler, regedit temizliği yaptık. Sorun devam etmekte.
Memtest yapıldı ve RAM'de sorun bulunamadı.
Mavi ekran yemeden saliseler önce kasadan ses geliyor. Fanlar hızlanıyor ama böyle saliselik. Hangininin önce olduğunu anlayamıyorsunuz.
Oyun oynarken (metin2) daha sık oluyor. Ayrıca SSD Win10'u açtığım anda mavi ekran yiyorum. İlk hata genelde WHEA_UNCORRECTABLE_ERROR oluyor, reset attıktan sonra %90 ihtimalle CLOCK_WATCHDOG_TIMEOUT hatasını alıyorum.
Driverler güncel dedim ama, Windows Update ve MSI Live Update'e göre dedim. Aygıt yöneticisinden çer-çöp dahil bütün birimlere online güncelleştirmeye tıkladım ama birkaç ufak değişim hariç onlarda da güncel dedi. Buna rağmen bazı driverlar için sitelerine bakmam gerekiyor sanırım. Okumalarıma göre Update, MSI Live Update ve aygıt Update'i güncel sürümü bulamayabiliyormuş sanırım.

@Recep Baltaş
@Claus
@Mikail Fidan
Sorunlar an itibari ile devam etmekte.
@Claus
@Mikail Fidan
@Recep Baltaş

Geçen yıl da çözülememişti. Bu minidumptan cidden hiçbir şey anlaşılamıyor mu sorunun tespitine dair?
Bir yol, bir çıkış kapısı yok mudur bu meretin? Elim kolum bağlı, açıyorum kapanıyor, açıyorum ve kapanıyor.
Sileri beklemekteyim.

Minidump (Win 8.1)

Çakışmadan şüphelenip 8.1 kurdum, ve bu iki hatayı aldım. Elimdeki bütün imkanları az önce tükettim sanırım. Artık kendi araştırmamla deneyebileceğim hiçbir yöntem kalmadı. Tamamen sizin direktiflerinize kaldım, tek şansım onlar. Umarım yakın zamanda çözüm önerinizle birlikte gelirsiniz.
@Recep Baltaş Söylediginiz gibi dump dosyalarini attim. İncelemenizi beklemekteyim. İnternetteki ve technopattaki konularin asagi yukari hepsini okudum. Bekliyorum.
Verdiğiniz cevaplar için sağ olun. Sorunum aynı şekilde devam etmekte. Bilgisayarcılar işgüzarlık yaptığı için şu aşamada onlardan da faydalanamıyorum.
Iyi de ne yapacağim ben? Şu dumplari bir inceleyiverseniz size zahmet.
Konu ile ilgilenebilir misiniz? 1 haftadır bilgisayarı kullanamıyorum @claus @Mikail Fidan. Umarım ilgilenebilirsiniz.

Recep Baltaş · 19 Eylül 2019

Sorunun olası sebepleri:

Yetersiz işlemci güç beslemesi
Arızalı işlemci
Aşırı monte edilmiş soğutucu

Tavsiyelerim:

Soğutucuyu gevşet. Aşırı sıkmadığından emin ol
Anakartın yeterli VRM soğutması var mı kontrol et
Sorun devam ederse anakart değişimi ilk önerim olacak

Kod:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0008f3aa180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 1

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 1

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd0008f3aa180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff800`e5918c88 fffff800`e41acc41 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd000`8f3aa180 : nt!KeBugCheckEx
fffff800`e5918c90 fffff800`e40d10e7 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35d91
fffff800`e5918d20 fffff800`e47b267f : fffffa80`04cd2530 00000000`00000000 fffff800`e47fe9b0 00000000`00000000 : nt!KeClockInterruptNotify+0x787
fffff800`e5918f40 fffff800`e40f84f3 : fffff800`e47fe900 00000000`00000000 ffffd000`8f7a3c80 fffff800`e4167a87 : hal!HalpTimerClockInterrupt+0x4f
fffff800`e5918f70 fffff800`e4167e2a : fffff800`e47fe900 fffff800`e4319180 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
fffff800`e5918fb0 fffff800`e416820f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`8f1e24f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35d91

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  35d91

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!_??_::FNODOBFM::_string_

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {b4258baa-ae9b-6fe3-2d9d-b0f48f872199}

Followup:     MachineOwner
---------
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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe601e03f1028, Address of the 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:
------------------

fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock
fffff8031f15e5a0: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe601e03f1028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT: 
fffff803`212aba08 fffff803`1f71df1f : 00000000`00000124 00000000`00000000 ffffe601`e03f1028 00000000`be000000 : nt!KeBugCheckEx
fffff803`212aba10 fffff80a`0503148a : ffffe601`e03f1028 ffffe601`df68c7d0 ffffe601`df68c7d0 ffffe601`df68c7d0 : hal!HalBugCheckSystem+0xcf
fffff803`212aba50 fffff803`1f090ea1 : ffffe601`e03f1028 00000000`00000000 ffffe601`df68c7d0 ffffe601`df68c7d0 : PSHED!PshedBugCheckSystem+0xa
fffff803`212aba80 fffff803`1f71e460 : 00000000`00000728 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
fffff803`212abae0 fffff803`1f71e7c0 : 00000000`00000010 00000000`00000000 fffff803`212abc88 00000000`00000000 : hal!HalpMcaReportError+0x50
fffff803`212abc30 fffff803`1f71e6ae : ffffe601`de509700 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
fffff803`212abc80 fffff803`1f71e8f2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
fffff803`212abcc0 fffff803`1f71ea80 : ffffe601`de509700 fffff803`212abef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff803`212abcf0 fffff803`1ef7defb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff803`212abd20 fffff803`1ef7dc6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff803`212abe60 fffff803`1ee51379 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1ac
ffffaa81`bb067ad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0xa9


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  10.0.16299.15

BUILDLAB_STR:  rs3_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------
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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8089d7609028, Address of the 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:
------------------

fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8003d0253c8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff8089d7609028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  OneDriveSetup.exe

STACK_TEXT: 
ffffa681`7578ca58 fffff800`3cba4808 : 00000000`00000124 00000000`00000000 ffff8089`d7609028 00000000`be000000 : nt!KeBugCheckEx
ffffa681`7578ca60 fffff800`3f381920 : ffff8089`d59fb7c0 00000000`00000000 ffff8089`d7609028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffa681`7578caa0 fffff800`3cf3d61a : ffff8089`d59fb7c0 ffffa681`7578cb29 00000000`00000000 ffff8089`d7609028 : PSHED!PshedBugCheckSystem+0x10
ffffa681`7578cad0 fffff800`3cba6166 : ffffa681`7578cbf0 00000000`00000001 ffff8089`d59fb810 ffff8089`d59fb7c0 : nt!WheaReportHwError+0x37a
ffffa681`7578cb90 fffff800`3cba65fa : 00000000`00000010 ffff8089`d59fb810 ffffa681`7578cd48 ffffa681`7578cf90 : hal!HalpMcaReportError+0x72
ffffa681`7578ccf0 fffff800`3cba64d4 : ffff8089`d58d7770 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffa681`7578cd40 fffff800`3cba6740 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffa681`7578cd80 fffff800`3cba57e8 : 00000000`00000000 ffffa681`7578d010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffa681`7578cdb0 fffff800`3cba69c7 : ffff8089`d58d7770 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffa681`7578cde0 fffff800`3cea1cb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffa681`7578ce10 fffff800`3cdcb63a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffa681`7578ce40 fffff800`3cdcb2ee : ffffa681`00000000 fffff800`3cdcb22b 00000000`1d42a68f 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa681`7578cf80 fffff800`3cce3370 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26e
ffffbd88`4a267bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushNonGlobalTb+0xe0


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcb0699980028, Address of the 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:
------------------

fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock
fffff8042de253c8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffcb0699980028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

STACK_TEXT: 
ffff9381`f4b8ca58 fffff804`2e4f9808 : 00000000`00000124 00000000`00000000 ffffcb06`99980028 00000000`be000000 : nt!KeBugCheckEx
ffff9381`f4b8ca60 fffff804`30381920 : ffffcb06`955fb7c0 00000000`00000000 ffffcb06`99980028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffff9381`f4b8caa0 fffff804`2dd3d61a : ffffcb06`955fb7c0 ffff9381`f4b8cb29 00000000`00000000 ffffcb06`99980028 : PSHED!PshedBugCheckSystem+0x10
ffff9381`f4b8cad0 fffff804`2e4fb166 : ffff9381`f4b8cbf0 00000000`00000001 ffffcb06`955fb810 ffffcb06`955fb7c0 : nt!WheaReportHwError+0x37a
ffff9381`f4b8cb90 fffff804`2e4fb5fa : 00000000`00000010 ffffcb06`955fb810 ffff9381`f4b8cd48 ffff9381`f4b8cf90 : hal!HalpMcaReportError+0x72
ffff9381`f4b8ccf0 fffff804`2e4fb4d4 : ffffcb06`954d7770 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffff9381`f4b8cd40 fffff804`2e4fb740 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffff9381`f4b8cd80 fffff804`2e4fa7e8 : 00000000`00000000 ffff9381`f4b8d010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff9381`f4b8cdb0 fffff804`2e4fb9c7 : ffffcb06`954d7770 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffff9381`f4b8cde0 fffff804`2dca1cb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffff9381`f4b8ce10 fffff804`2dbcb63a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffff9381`f4b8ce40 fffff804`2dbcb2ee : ffffa407`00000000 fffff804`2dbcb22b 00000000`1d73c99b 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9381`f4b8cf80 fffff804`2daa4e80 : fffff300`03f1e600 ffff9381`f4b80180 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26e
ffffa407`368ed520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa5804ab86180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 6

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffa5804ab86180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff804`72eb5af8 fffff804`6cc0c898 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffa580`4ab86180 : nt!KeBugCheckEx
fffff804`72eb5b00 fffff804`6ca836f4 : 00000000`00000000 00000000`00000000 00000000`00000c03 fffff804`6b6c7180 : nt!KeAccumulateTicks+0x186048
fffff804`72eb5b60 fffff804`6c95e4b7 : 00000000`00000000 ffffcb0f`239da510 ffffcb0f`239da590 00000000`0000000c : nt!KeClockInterruptNotify+0x6c4
fffff804`72eb5f30 fffff804`6ca5e015 : 00000000`1cbb52c0 fffff804`6c9cbcf0 fffff804`6c9cbda0 00000000`00000006 : hal!HalpTimerClockInterrupt+0xf7
fffff804`72eb5f60 fffff804`6cbbe26a : ffffcb0f`239da590 fffff804`6c9cbcf0 00000000`00000000 fffff804`6c9cbcf0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`72eb5fb0 fffff804`6cbbe7b7 : 00000000`092395c5 ffffcb0f`239da590 fffff804`6c9cbcf0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffcb0f`239da510 fffff804`6caa4e80 : 80000001`daf91800 fffff804`6b6c7180 00000000`00000000 fffff804`6c95e848 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffcb0f`239da6a0 fffff804`6cab36cf : fffff880`0590ead0 80000001`daf91821 80000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0
ffffcb0f`239da7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmSetAddressRangeModifiedEx+0x29f


SYMBOL_NAME:  nt!KeAccumulateTicks+186048

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.30

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  186048

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd981599e3180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 11

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd981599e3180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT: 
ffffd981`5999fbc8 fffff801`7979df0c : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd981`599e3180 : nt!KeBugCheckEx
ffffd981`5999fbd0 fffff801`79671ee8 : ffffd981`5992d180 ffffd981`5992d180 00000000`00013626 00000000`00000000 : nt!KeAccumulateTicks+0x12a7bc
ffffd981`5999fc30 fffff801`79eda4c6 : 000003fe`b257751d 00000000`00000000 ffffc383`57b40a30 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8
ffffd981`5999ff40 fffff801`796c1175 : ffff8a89`4ef05300 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x56
ffffd981`5999ff70 fffff801`79769eea : ffffc383`57b40ab0 ffff8a89`4ef05300 00000000`00000000 ffffc383`57b40d68 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd981`5999ffb0 fffff801`7976a337 : 00000000`0d5f2fd0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffc383`57b40a30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+12a7bc

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.16299.15

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  12a7bc

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.16299.15

BUILDLAB_STR:  rs3_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffda8059f86180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffda8059f86180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  wermgr.exe

STACK_TEXT: 
ffffda80`5a172af8 fffff805`3d00c898 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffda80`59f86180 : nt!KeBugCheckEx
ffffda80`5a172b00 fffff805`3ce836f4 : 00000000`00000000 00000000`00000000 00000000`00000929 ffffda80`5a180180 : nt!KeAccumulateTicks+0x186048
ffffda80`5a172b60 fffff805`3cd5e4b7 : 00000000`00000000 fffff88e`5b9602c0 fffff88e`5b960340 00000000`0000000c : nt!KeClockInterruptNotify+0x6c4
ffffda80`5a172f30 fffff805`3ce5e015 : 00000000`15ef35c8 ffffb00f`e52d3500 ffffb00f`e52d35b0 fffff759`e8dc7000 : hal!HalpTimerClockInterrupt+0xf7
ffffda80`5a172f60 fffff805`3cfbe26a : fffff88e`5b960340 ffffb00f`e52d3500 00000000`00000001 ffffb00f`e52d3500 : nt!KiCallInterruptServiceRoutine+0xa5
ffffda80`5a172fb0 fffff805`3cfbe7b7 : 00000000`086c892e fffff88e`5b960340 ffffb00f`e52d3500 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff88e`5b9602c0 fffff805`3cea4e80 : 87000001`cc99f800 ffffda80`5a180180 00000000`00000000 fffff56d`402d5ea8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff88e`5b960450 fffff805`3ceae2f1 : fffff88e`5b9606a0 87000001`cc99f867 fffff88e`5b9606a0 00000000`00000000 : nt!MiFlushTbList+0x3a0
fffff88e`5b9605a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCopyOnWrite+0x761


SYMBOL_NAME:  nt!KeAccumulateTicks+186048

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.30

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  186048

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8f8ffb40b028, Address of the 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:
------------------

fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock
fffff80013c253c8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff8f8ffb40b028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  OneDriveSetup.exe

STACK_TEXT: 
fffff800`186c2918 fffff800`137a4808 : 00000000`00000124 00000000`00000000 ffff8f8f`fb40b028 00000000`be000000 : nt!KeBugCheckEx
fffff800`186c2920 fffff800`16b81920 : ffff8f8f`f909e350 00000000`00000000 ffff8f8f`fb40b028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
fffff800`186c2960 fffff800`13b3d61a : ffff8f8f`f909e350 fffff800`186c29e9 00000000`00000000 ffff8f8f`fb40b028 : PSHED!PshedBugCheckSystem+0x10
fffff800`186c2990 fffff800`137a6166 : fffff800`186c2ab0 00000000`00000000 ffff8f8f`f909e3a0 ffff8f8f`f909e350 : nt!WheaReportHwError+0x37a
fffff800`186c2a50 fffff800`137a65fa : 00000000`00000010 ffff8f8f`f909e3a0 fffff800`186c2c08 fffff800`186c2e50 : hal!HalpMcaReportError+0x72
fffff800`186c2bb0 fffff800`137a64d4 : ffff8f8f`f76d76c0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
fffff800`186c2c00 fffff800`137a6740 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
fffff800`186c2c40 fffff800`137a57e8 : 00000000`00000000 fffff800`186c2ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff800`186c2c70 fffff800`137a69c7 : ffff8f8f`f76d76c0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff800`186c2ca0 fffff800`13aa1cb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff800`186c2cd0 fffff800`139cb63a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff800`186c2d00 fffff800`139cb2ee : fffffd8b`00000000 fffff800`139cb22b 00000000`1d614ea4 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff800`186c2e40 fffff800`138a4e78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26e
fffffd8b`1f57fea0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x398


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001fc77c028, Address of the 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:
------------------

fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock
fffff801b30ace60: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe001fc77c028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffd000`61f39cf8 fffff801`b35d1213 : 00000000`00000124 00000000`00000000 ffffe001`fc77c028 00000000`be000000 : nt!KeBugCheckEx
ffffd000`61f39d00 fffff801`b2fccbed : 00000000`00000001 ffffe001`fafc7a20 ffffe001`fafc7a20 ffffe001`fc77c028 : hal!HalBugCheckSystem+0xcf
ffffd000`61f39d40 fffff801`b35d16a0 : 00000000`00000728 00000000`00000001 ffffd000`61f3a130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`61f39da0 fffff801`b35d1a0d : ffffe001`00000010 ffffe001`fafc7a20 ffffd000`61f39f48 ffffe001`fafc7a20 : hal!HalpMcaReportError+0x50
ffffd000`61f39ef0 fffff801`b35d18f8 : ffffe001`fafc7730 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`61f39f40 fffff801`b35d1b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`61f39f80 fffff801`b35d1ccf : ffffe001`fafc7730 ffffd000`61f3a1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`61f39fb0 fffff801`b2f614bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`61f39fe0 fffff801`b2f61271 : 00000000`00000000 fffff801`b2f611f2 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`61f3a120 fffff800`ed802214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`61f5a7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd98eb0c06028, Address of the 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:
------------------

fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock
fffff803361585a0: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd98eb0c06028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8000`1fbf65c8 fffff803`36717f1f : 00000000`00000124 00000000`00000000 ffffd98e`b0c06028 00000000`be000000 : nt!KeBugCheckEx
ffff8000`1fbf65d0 fffff808`b939148a : ffffd98e`b0c06028 ffffd98e`aed09a20 ffffd98e`aed09a20 ffffd98e`aed09a20 : hal!HalBugCheckSystem+0xcf
ffff8000`1fbf6610 fffff803`3608aea1 : ffffd98e`b0c06028 00000000`00000000 ffffd98e`aed09a20 ffffd98e`aed09a20 : PSHED!PshedBugCheckSystem+0xa
ffff8000`1fbf6640 fffff803`36718460 : 00000000`00000728 00000000`00000001 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
ffff8000`1fbf66a0 fffff803`367187c0 : 00000000`00000010 00000000`00000001 ffff8000`1fbf6848 00000000`00000001 : hal!HalpMcaReportError+0x50
ffff8000`1fbf67f0 fffff803`367186ae : ffffd98e`aed097b0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
ffff8000`1fbf6840 fffff803`367188f2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffff8000`1fbf6880 fffff803`36718a80 : ffffd98e`aed097b0 ffff8000`1fbf6ab0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffff8000`1fbf68b0 fffff803`35f77efb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffff8000`1fbf68e0 fffff803`35f77c6c : 00000000`00000000 fffff803`35f77beb 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffff8000`1fbf6a20 fffff808`bb1013b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1ac
ffffa987`1da296e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OS_VERSION:  10.0.16299.15

BUILDLAB_STR:  rs3_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup:     MachineOwner
---------

MayCrasH · 21 Eylül 2019

Bence sen bir islemci ve anakart degiş bu bahane ile.

WHEA_UNCORRECTABLE_ERROR Mavi Ekran Hatası

Ayrıntılı düzenleme

ohmyrab

Hectopat

Recep Baltaş

Technopat

Minidump Dosyalarını Paylaşın

ohmyrab

Hectopat

Recep Baltaş

Technopat

MayCrasH

Zettapat

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz