Çözüldü CLOCK_WATCHDOG_TIMEOUT hatası

afy · 7 Aralık 2020

Merhabalar. Bilgisayarım 5 yıllık herhangi bir değişiklik yapmadım sadece son zamanlarda VMware Player kullanıyorum ve bunu kullanırken CLOCK_WATCHDOG_TIMEOUT hatası alıyorum.
Minidump dosyasını sizinle paylaşıyorum, umarım doğru paylaşabilmişimdir.
Dosyayı aldıktan sonra Windows 10 son sürüme yükselttim, bu daha da eski sürüm olabilir.

Sistem AMD A10 7870K
Ram 8GB dual channel
Anakart MSİ
Sürücüler güncel
BIOS güncel ayarlar default

Kod:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffb700973d6180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 11046

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 17281

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

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb700973d6180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`6d278c88 fffff803`67a59362     : 00000000`00000101 00000000`00000030 00000000`00000000 ffffb700`973d6180 : nt!KeBugCheckEx
fffff803`6d278c90 fffff803`678cef5d     : 00000000`00000000 fffff803`65546180 00000000`00000246 00000000`00064da4 : nt!KeAccumulateTicks+0x18bee2
fffff803`6d278cf0 fffff803`678c8651     : 00000000`00064b00 00000000`0003c1ce fffff803`65546180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff803`6d278d40 fffff803`678ca4eb     : 00000000`00000000 ffffd900`ded17000 fffff803`682318e8 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff803`6d278e80 fffff803`678c7722     : ffffd900`ded16fb0 ffffd900`ded17030 ffffd900`ded17030 00000000`00000000 : nt!KeClockInterruptNotify+0x2bb
fffff803`6d278f30 fffff803`67808705     : 0000000f`074efed6 fffff803`682f3820 fffff803`682f38d0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff803`6d278f60 fffff803`679df4ca     : ffffd900`ded17030 fffff803`682f3820 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`6d278fb0 fffff803`679dfa37     : 00000000`728a5e78 fffff803`65546180 00000000`00000002 fffff803`65549130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd900`ded16fb0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+18bee2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  18bee2

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffb700973d6180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9421

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11109

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

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb700973d6180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`6d278c88 fffff803`67a59362     : 00000000`00000101 00000000`00000030 00000000`00000000 ffffb700`973d6180 : nt!KeBugCheckEx
fffff803`6d278c90 fffff803`678cef5d     : 00000000`00000000 fffff803`65546180 00000000`00000246 00000000`00064da4 : nt!KeAccumulateTicks+0x18bee2
fffff803`6d278cf0 fffff803`678c8651     : 00000000`00064b00 00000000`0003c1ce fffff803`65546180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff803`6d278d40 fffff803`678ca4eb     : 00000000`00000000 ffffd900`ded17000 fffff803`682318e8 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff803`6d278e80 fffff803`678c7722     : ffffd900`ded16fb0 ffffd900`ded17030 ffffd900`ded17030 00000000`00000000 : nt!KeClockInterruptNotify+0x2bb
fffff803`6d278f30 fffff803`67808705     : 0000000f`074efed6 fffff803`682f3820 fffff803`682f38d0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff803`6d278f60 fffff803`679df4ca     : ffffd900`ded17030 fffff803`682f3820 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`6d278fb0 fffff803`679dfa37     : 00000000`728a5e78 fffff803`65546180 00000000`00000002 fffff803`65549130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd900`ded16fb0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+18bee2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  18bee2

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Ma'at · 7 Aralık 2020

Harici bir ağ kartı kullanıyorsanız Bluetooth ve Wi-Fi sürücülerinizi güncelleyin. Donanım kimliği ile güncel sürücüleri bulabilirsiniz.
- Donanım Kimliği ile sürücüleri bulun
SFC rehberini uygulayın.
- SFC /scannow komutu nedir? Ne işe yarar?
Ekran kartı sürücüsünü DDU ile kaldırın, WHQL sertifikalı güncel bir sürüm kurun.
- DDU ile Sürücü Kaldırma Rehberi

afy · 7 Aralık 2020

Ma'at dedi:
Siz yine de kontrol edin.

Şu anda sürücüler yükleniyor. Ardından BIOS da inceleyeceğim. Şimdiden bu noktaya kadar olan tüm desteğiniz için de teşekkür ederim.
VMware'ı şu an kullanıyorum. 1 saattir hata almadım. Gelişme olursa buradan iletirim, teşekkürler hocam.
Şimdilik yapılanların özeti:
-Sürücüleri temiz şekilde yeniden kurdum.
-VMware'de 3D Accelaration kapattım.
-Sabit disk alanını değişken değil, sabit olarak belirledim.
-VMware'ı yeniden kurdum.
-BIOS'dan kontrol ettim. Sanallaştırma açık. Bu konuyu sonradan okuyan arkadaşlar için Advanced settings içinde CPUconf. Sekmesinde SVM ya da SMV gibi bir ayar var onun açık olması gerekli.

Konuda belirtilen işlemler yapılmış, hata çözülmüştür sonradan okuyan arkadaşlar için bilgilendirici olsun.

Çözüldü CLOCK_WATCHDOG_TIMEOUT hatası

Ayrıntılı düzenleme

afy

Hectopat

Ma'at

afy

Hectopat

Benzer konular