Çözüldü Valorant oynarken "CLOCK_WATCHDOG_TIMEOUT" mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 11
Burak Temelkaya

Burak Temelkaya

Kilopat
Katılım
13 Ekim 2016
Mesajlar
1.157
Makaleler
1
Çözümler
5
Yer
İstanbul
Daha fazla  
Sistem Özellikleri
İŞLEMCİ: AMD Ryzen 5 7600
İŞLEMCİ SOĞUTUCU: Cooler Master Hyper 212 Spectrum Rainbow LED 120mm Hava Soğutucu
ANAKART: MSI Pro B650M-A WiFi AM5
EKRAN KARTI: MSI Radeon RX 6800 Gaming Z Trio 16G V1 16GB
RAM: Kingston Fury Beast 16 + 8 GB 6000MHz CL40 DDR5 Ram
SSD: Samsung 980 1TB + Kingston KC3000 2TB
KASA: VENTO Neptune VG07F RGB Siyah Mid Tower Gaming Kasa
PSU: FSP Hyper Pro H3-650 650W 80+ Bronze
Cinsiyet
Erkek
Meslek
Yazılım Geliştirici
RAM
CORSAİR VENGEANCE 16 GB DDR4 2400 MHZ
SSD veya HDD modeli
Corsair Force Le 240 GB
Ekran kartı
MSI ARMOR GTX 1060 6 GB
Anakart
MSI B350M GAMING PRO
İşlemci
Ryzen 5 3600
Valorant oynarken bu hatayı aldım. Yeni ekran kartımı güncelledim ve çekirdek yalıtımı özelliğini kapattım. Hatanın bunlar ile bir alakası olabilir mi? Art arda 2 kez hata aldım o yüzden 2 minidump dosyası atıyorum.

Minidump dosyaları: https://eduselcuk-my.sharepoint.com...hEltPiRDVv85MBdYXjeiYxWyUGrGrIXwEkrw?e=IICtIn

Minidump dosyasını analiz ettiğimde şöyle bir sonuç alıyorum.

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1859

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10004

    Key  : Analysis.IO.Other.Mb
    Value: 25

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 31

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101

    Key  : Bugcheck.Code.Register
    Value: 0x101

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  032523-9484-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffde004d1d1180

BUGCHECK_P4: a

FAULTING_PROCESSOR: a

PROCESS_NAME:  System

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
ffffde00`4cd359a8 fffff802`4b479bd2     : 00000000`00000101 00000000`00000010 00000000`00000000 ffffde00`4d1d1180 : nt!KeBugCheckEx
ffffde00`4cd359b0 fffff802`4b226984     : ffffde00`4cdd1180 00000001`da472399 00000000`0000c92e 00000000`00000000 : nt!KeAccumulateTicks+0x2522d2
ffffde00`4cd35a10 fffff802`4b226863     : 00000000`0000000c 00000000`00000000 ffffde00`4cdd1180 00000001`dfa85d00 : nt!KiUpdateRunTime+0xf4
ffffde00`4cd35bd0 fffff802`4b224a8e     : 00000000`00000000 ffffde00`4cdd1180 ffffffff`ffffffff 00000000`0000000c : nt!KiUpdateTime+0x13e3
ffffde00`4cd35e90 fffff802`4b22429a     : fffff802`4bc5fee8 ffffb587`13736230 ffffb587`13736230 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
ffffde00`4cd35f40 fffff802`4b3453fe     : 00000001`dfabccae ffffb587`13736180 ffffde00`4cdd1180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
ffffde00`4cd35f70 fffff802`4b42b55a     : ffffc605`d3740050 ffffb587`13736180 ffffde00`4cdd1180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
ffffde00`4cd35fb0 fffff802`4b42bdc7     : 00000000`1fcbc119 ffffc605`d3742000 00000000`00000000 fffff802`4b057d8c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc605`d373ffd0 fffff802`4b216f1a     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`4b3a9fa0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc605`d3740160 fffff802`4b216e05     : 00000000`c0000004 ffffc605`00000001 ffffc605`d3741630 ffffc605`d3742000 : nt!KiIpiStallOnPacketTargetsPrcb+0x2a
ffffc605`d3740190 fffff802`4b6aab8c     : 00000000`c0000004 ffffc605`d37410e0 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0xd9
ffffc605`d37401e0 fffff802`4b6ba895     : 00000000`00000000 ffffc605`00000000 fffff802`6259231b 00000000`00000000 : nt!ExpGetProcessInformation+0x17c
ffffc605`d37407f0 fffff802`4b6b9a69     : ffffc605`d3741578 ffffc605`d3741bb8 00000000`00000000 000ffff7`f7ffffff : nt!ExpQuerySystemInformation+0xcf5
ffffc605`d3741020 fffff802`4b43e1e8     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc605`d3741220 : nt!NtQuerySystemInformation+0x79
ffffc605`d3741060 fffff802`4b42ec90     : fffff802`625939ad 00000000`00000110 00000000`00000088 00000000`000001a0 : nt!KiSystemServiceCopyEnd+0x28
ffffc605`d37411f8 fffff802`625939ad     : 00000000`00000110 00000000`00000088 00000000`000001a0 00000000`00000040 : nt!KiServiceLinkage
ffffc605`d3741200 00000000`00000110     : 00000000`00000088 00000000`000001a0 00000000`00000040 00000000`00000000 : vgk+0x1739ad
ffffc605`d3741208 00000000`00000088     : 00000000`000001a0 00000000`00000040 00000000`00000000 00000000`00000001 : 0x110
ffffc605`d3741210 00000000`000001a0     : 00000000`00000040 00000000`00000000 00000000`00000001 00000000`00000001 : 0x88
ffffc605`d3741218 00000000`00000040     : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000101 : 0x1a0
ffffc605`d3741220 00000000`00000000     : 00000000`00000001 00000000`00000001 00000000`00000101 ffffc605`d3741bb8 : 0x40


SYMBOL_NAME:  nt!KeAccumulateTicks+2522d2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1413

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2522d2

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

5: 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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffde004d1d1180, The PRCB address of the hung processor.
Arg4: 000000000000000a, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1374

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1729

    Key  : Analysis.IO.Other.Mb
    Value: 25

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 31

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101

    Key  : Bugcheck.Code.Register
    Value: 0x101

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  032523-9484-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffde004d1d1180

BUGCHECK_P4: a

FAULTING_PROCESSOR: a

PROCESS_NAME:  System

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
ffffde00`4cd359a8 fffff802`4b479bd2     : 00000000`00000101 00000000`00000010 00000000`00000000 ffffde00`4d1d1180 : nt!KeBugCheckEx
ffffde00`4cd359b0 fffff802`4b226984     : ffffde00`4cdd1180 00000001`da472399 00000000`0000c92e 00000000`00000000 : nt!KeAccumulateTicks+0x2522d2
ffffde00`4cd35a10 fffff802`4b226863     : 00000000`0000000c 00000000`00000000 ffffde00`4cdd1180 00000001`dfa85d00 : nt!KiUpdateRunTime+0xf4
ffffde00`4cd35bd0 fffff802`4b224a8e     : 00000000`00000000 ffffde00`4cdd1180 ffffffff`ffffffff 00000000`0000000c : nt!KiUpdateTime+0x13e3
ffffde00`4cd35e90 fffff802`4b22429a     : fffff802`4bc5fee8 ffffb587`13736230 ffffb587`13736230 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
ffffde00`4cd35f40 fffff802`4b3453fe     : 00000001`dfabccae ffffb587`13736180 ffffde00`4cdd1180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
ffffde00`4cd35f70 fffff802`4b42b55a     : ffffc605`d3740050 ffffb587`13736180 ffffde00`4cdd1180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
ffffde00`4cd35fb0 fffff802`4b42bdc7     : 00000000`1fcbc119 ffffc605`d3742000 00000000`00000000 fffff802`4b057d8c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc605`d373ffd0 fffff802`4b216f1a     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`4b3a9fa0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc605`d3740160 fffff802`4b216e05     : 00000000`c0000004 ffffc605`00000001 ffffc605`d3741630 ffffc605`d3742000 : nt!KiIpiStallOnPacketTargetsPrcb+0x2a
ffffc605`d3740190 fffff802`4b6aab8c     : 00000000`c0000004 ffffc605`d37410e0 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0xd9
ffffc605`d37401e0 fffff802`4b6ba895     : 00000000`00000000 ffffc605`00000000 fffff802`6259231b 00000000`00000000 : nt!ExpGetProcessInformation+0x17c
ffffc605`d37407f0 fffff802`4b6b9a69     : ffffc605`d3741578 ffffc605`d3741bb8 00000000`00000000 000ffff7`f7ffffff : nt!ExpQuerySystemInformation+0xcf5
ffffc605`d3741020 fffff802`4b43e1e8     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc605`d3741220 : nt!NtQuerySystemInformation+0x79
ffffc605`d3741060 fffff802`4b42ec90     : fffff802`625939ad 00000000`00000110 00000000`00000088 00000000`000001a0 : nt!KiSystemServiceCopyEnd+0x28
ffffc605`d37411f8 fffff802`625939ad     : 00000000`00000110 00000000`00000088 00000000`000001a0 00000000`00000040 : nt!KiServiceLinkage
ffffc605`d3741200 00000000`00000110     : 00000000`00000088 00000000`000001a0 00000000`00000040 00000000`00000000 : vgk+0x1739ad
ffffc605`d3741208 00000000`00000088     : 00000000`000001a0 00000000`00000040 00000000`00000000 00000000`00000001 : 0x110
ffffc605`d3741210 00000000`000001a0     : 00000000`00000040 00000000`00000000 00000000`00000001 00000000`00000001 : 0x88
ffffc605`d3741218 00000000`00000040     : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000101 : 0x1a0
ffffc605`d3741220 00000000`00000000     : 00000000`00000001 00000000`00000001 00000000`00000101 ffffc605`d3741bb8 : 0x40


SYMBOL_NAME:  nt!KeAccumulateTicks+2522d2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1413

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2522d2

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

BIOS'ta RAM'lerin XMP'si kapalıymış açınca düzeldi. Tekrar hata alırsam buraya yazarım.
 
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala
halil206 dedi:
merhaba , bendede aynı hata olduda biota ramlerin xmpsini açınca tekrar hata aldınmı
Genişletmek için tıkla...
Yok almadım, şu anda o bilgisayarı kullanmıyorum ama bayadır hata almadım.
 
Artı 0 Eksi

Benzer konular

Ö
  • Soru
"CLOCK_WATCHDOG_TIMEOUT" mavi ekran hatası
Mesaj
1
Görüntüleme
64
GFYT
GFYT
ByknınR6sı
  • Soru
"CLOCK_WATCHDOG_TIMEOUT" mavi ekran hatası
Mesaj
3
Görüntüleme
129
tahakeskinn
T
Y
  • Soru
CLOCK_WATCHDOG_TIMEOUT mavi ekran hatası
Mesaj
0
Görüntüleme
152
yazo164
Y
mutlu pide
  • Soru
CLOCK_WATCHDOG_TIMEOUT mavi ekran hatası
Mesaj
1
Görüntüleme
224
Cliff_Burton
Cliff_Burton
OyunMeraklısıErgen
  • Çözüldü
Çözüldü  "CLOCK_WATCHDOG_TIMEOUT" Mavi ekran hatası
2
Mesaj
14
Görüntüleme
749
OyunMeraklısıErgen
OyunMeraklısıErgen

Yeni konular

Yeni mesajlar

Geri
Yukarı