i9-11900K CLOCK_WATCHDOG_TIMEOUT

Katılım
14 Ağustos 2010
Mesajlar
79.057
Makaleler
289
Çözümler
2.268
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Profil Kapağı
1522743131
Cinebench testi esnasında geldi mavi ekran. Olası sebepler: Aşırı ısınma, Beta BIOS.

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: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd101c95de180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 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: 2687

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 46678

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

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

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

    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


BUGCHECK_CODE:  101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd101c95de180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT: 
fffff806`78e7cc88 fffff806`7363ab42     : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffd101`c95de180 : nt!KeBugCheckEx
fffff806`78e7cc90 fffff806`7347541d     : 00000000`00000000 fffff806`7090a180 00000000`00000246 00000000`0000e653 : nt!KeAccumulateTicks+0x1c8942
fffff806`78e7ccf0 fffff806`734759c1     : 00000000`0000e300 00000000`00008948 fffff806`7090a180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff806`78e7cd40 fffff806`7346f833     : fffff806`7090a180 00000000`00000000 fffff806`73e31b30 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff806`78e7ce80 fffff806`734781f2     : fffff904`7e7e9cd0 fffff904`7e7e9d50 fffff904`7e7e9d00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff806`78e7cf30 fffff806`73527f55     : 00000002`253990b2 fffff806`73ef3ba0 fffff806`73ef3c50 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff806`78e7cf60 fffff806`735f76fa     : fffff904`7e7e9d50 fffff806`73ef3ba0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`78e7cfb0 fffff806`735f7c67     : 00000000`149b934a fffff806`7090a180 00000000`00000002 fffff806`7090d130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff904`7e7e9cd0 fffff806`73493680     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`c0000225 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff904`7e7e9e60 fffff806`73493498     : 81000001`57f25121 ffff8e80`0407d600 fffff806`73e4f200 00000000`00000004 : nt!KeFlushMultipleRangeTb+0x160
fffff904`7e7e9f00 fffff806`734e0871     : fffff904`7e7ea030 00000000`00000000 81000001`57f25121 ffff945f`c3ed4698 : nt!MiFlushTbList+0x88
fffff904`7e7e9f30 fffff806`734dfb0c     : ffffbf87`da8d3000 000099b9`c4d379f4 00000000`00000000 00000000`00000001 : nt!MmProtectPool+0xd2d
fffff904`7e7ea160 fffff806`73898262     : 00000000`00000000 ffffbf87`da8d3fff 00000000`00000000 00000000`00000000 : nt!ExProtectPoolEx+0x148
fffff904`7e7ea1c0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvpSetRangeProtection+0x106


SYMBOL_NAME:  nt!KeAccumulateTicks+1c8942

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c8942

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
---------
 
Bu hata yalnızca işlemci ile alakalı birtakım sorunlarda gerçekleşir. Microsoft'ta aynısını demiş. Ya Beta sürüm BIOS olduğu için (dendiği gibi) bu hata oluştu ya da sistem aşırı ısındı. Gerekli dokümantasyonları incelediğimde de sadece @Recep Baltaş hocanın dedikleri benim de aklıma geldi. Başka bir olanak olacağını sanmıyorum yani.
 
Kafamda deli sorular ? Gerçekten merak ettiğim bir inceleme oldu bu, Intel'in verdiği vaatlerden sonra.
En çok merak edilen herhalde sıvı soğutma - hava soğutma kısmı ve Ryzen 5900X ile olan karşılaştırma.
 

Geri
Yukarı