"Clock Watchdog Timeout" Mavi Ekran

  • Konuyu başlatan 64502
  • Başlangıç Tarihi
  • Mesaj 10
  • Görüntüleme 24B

64502

Kilopat
Katılım
21 Haziran 2015
Mesajlar
1.338
Makaleler
5
Çözümler
10
Merhaba, sistemi 4 gün önce ben topladım ve orijinal Windows 10 Pro son sürüm kurduk. World of Warcraft Battle for Azeroth oynarken sistem mavi ekran verip bu hata kodunu verdi bugün, 3 gündür bir problem yoktu. MiniDump klasöründe 1 tane dosya vardı o da aşağıdaki. BIOS ve driverların hepsi güncel. Not: İlk önce Driver Booster ile kurduk driverları, sonra sadece ekran kartınınkini güncelledik.


Sistem:
Ryzen 5 1600 12nm
MSI GTX 1660 Super Gaming X
Gigabyte B450 S2H
XPG D30 8x2 3000 MHZ
XPG SX 6000 Pro 256 GB
 
Temiz kurulum yap, sürücülerini elle kendin kur.

Overclock, undervolt yaptıysan kapat, CPB kapattıysan geri aç.
BIOS'a git Exit bölümünden Load Defaults yap kaydet çık.
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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff9c00bc1e4180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9c00bc1e4180

BUGCHECK_P4: 7

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 7

PROCESS_NAME:  Wow.exe

FAULTING_THREAD:  ffffde0e5e2ab080

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-25-2020 19:50:35.0364

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8024abee9b0 to fffff8024abc14e0

STACK_TEXT:
fffff802`4fe75b08 fffff802`4abee9b0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff9c00`bc1e4180 : nt!KeBugCheckEx
fffff802`4fe75b10 fffff802`4aa1f61c : fffff780`00000320 fffff802`48638180 00000000`00bc4273 00000000`00bc4273 : nt!KeAccumulateTicks+0x1cbf50
fffff802`4fe75b70 fffff802`4b4b74b7 : 00000000`00000000 ffff880b`28954b60 ffff880b`28954be0 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff802`4fe75f30 fffff802`4aa02a25 : 000001c0`da131eba fffff802`4b5250e0 fffff802`4b525190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff802`4fe75f60 fffff802`4abc2f7a : ffff880b`28954be0 fffff802`4b5250e0 00000000`00000001 fffff802`4b5250e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`4fe75fb0 fffff802`4abc34e7 : 00000000`81943607 ffff880b`28954be0 fffff802`4b5250e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff880b`28954b60 fffff802`4aab36e0 : 00000000`00000000 fffff802`48638180 00000000`00000000 ffffde0e`5d0ae010 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff880b`28954cf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


THREAD_SHA1_HASH_MOD_FUNC:  dc8736af616fc8dbbe5744546b76f6197d522250

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7dda3d52d42255d77ed77d0c4e195c2d4a7387e4

THREAD_SHA1_HASH_MOD:  77b99fd8d0bba6459fea0474c255a54ffe46d91a

FOLLOWUP_IP:
nt!KeAccumulateTicks+1cbf50
fffff802`4abee9b0 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+1cbf50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cbf50

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

TARGET_TIME:  2020-01-25T16:25:26.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  7ed4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_nt!keaccumulateticks

FAILURE_ID_HASH:  {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Followup:     MachineOwner
---------
 
Temiz kurulum yap, sürücülerini elle kendin kur.

Overclock, undervolt yaptıysan kapat, CPB kapattıysan geri aç.
BIOS'a git Exit bölümünden Load Defaults yap kaydet çık.
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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff9c00bc1e4180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9c00bc1e4180

BUGCHECK_P4: 7

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 7

PROCESS_NAME:  Wow.exe

FAULTING_THREAD:  ffffde0e5e2ab080

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-25-2020 19:50:35.0364

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8024abee9b0 to fffff8024abc14e0

STACK_TEXT:
fffff802`4fe75b08 fffff802`4abee9b0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff9c00`bc1e4180 : nt!KeBugCheckEx
fffff802`4fe75b10 fffff802`4aa1f61c : fffff780`00000320 fffff802`48638180 00000000`00bc4273 00000000`00bc4273 : nt!KeAccumulateTicks+0x1cbf50
fffff802`4fe75b70 fffff802`4b4b74b7 : 00000000`00000000 ffff880b`28954b60 ffff880b`28954be0 00000000`0000000c : nt!KeClockInterruptNotify+0x98c
fffff802`4fe75f30 fffff802`4aa02a25 : 000001c0`da131eba fffff802`4b5250e0 fffff802`4b525190 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
fffff802`4fe75f60 fffff802`4abc2f7a : ffff880b`28954be0 fffff802`4b5250e0 00000000`00000001 fffff802`4b5250e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`4fe75fb0 fffff802`4abc34e7 : 00000000`81943607 ffff880b`28954be0 fffff802`4b5250e0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff880b`28954b60 fffff802`4aab36e0 : 00000000`00000000 fffff802`48638180 00000000`00000000 ffffde0e`5d0ae010 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff880b`28954cf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


THREAD_SHA1_HASH_MOD_FUNC:  dc8736af616fc8dbbe5744546b76f6197d522250

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7dda3d52d42255d77ed77d0c4e195c2d4a7387e4

THREAD_SHA1_HASH_MOD:  77b99fd8d0bba6459fea0474c255a54ffe46d91a

FOLLOWUP_IP:
nt!KeAccumulateTicks+1cbf50
fffff802`4abee9b0 cc              int     3

FAULT_INSTR_CODE:  cb8b48cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KeAccumulateTicks+1cbf50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cbf50

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

TARGET_TIME:  2020-01-25T16:25:26.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  7ed4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_nt!keaccumulateticks

FAILURE_ID_HASH:  {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Followup:     MachineOwner
---------
Öncelikle teşekkürler.
Overclock, undervolt yapmadım sadece RAM'lerin XMP profili açık. CPB nedir bilmiyorum. Windows'u baştan kurmadan aygıt yöneticisinde ki sürücüleri tek tek kaldırıp kendim yüklesem olmaz mı?
 
Öncelikle teşekkürler. Overclock, undervolt yapmadım sadece ramlerin XMP profili açık. CPB nedir bilmiyorum. Windows'u baştan kurmadan aygıt yöneticisindeki sürücüleri tek tek kaldırıp kendim yüklesem olmaz mı ?
İllaki kalıntıları kalır temiz kurulum en iyisi olur. Şu Driver Booster kaç Windows'u aramızdan aldı bi bilsen.
 
Önemli bir sorun görünmüyor.
Sürücü bulucu kullanmayın ve temiz kurulum ile 1909'a geçiş yapın. Ayrıca Gıgabyte, Logitech ve Deomon tools gibi araçları geçici olarak yüklemeyin. Temiz kurulum sonrası güncel GPU'yu yükledikten sonra oyunu yükleyip test edip son durumu belirtin.
 
Sormayın ya sistemi kuzenime topladım da bilgisayarla pek ilgili değil parçaları falan ben seçip, montajladım. Kurarken acele etti kullan gitsin ne olcak dedi ben de maalesef dinlemiş bulundum.
 
Sormayın ya sistemi kuzenime topladım da bilgisayarla pek ilgili değil parçaları falan ben seçip, montajladım. Kurarken acele etti kullan gitsin ne olcak dedi ben de maalesef dinlemiş bulundum.
Evinizde pompalı varsa kullanmanın zamanı gelmiş.(espiri amaçlı yazdım):D
Yani bilgisi yoksa kurcalamasın fazla.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Yeni konular

Geri
Yukarı