Dosya Ekleri

  • IMG_1802.webp
    IMG_1802.webp
    95,8 KB · Görüntüleme: 68
  • IMG_1803.webp
    IMG_1803.webp
    104 KB · Görüntüleme: 63
  • IMG_1804.webp
    IMG_1804.webp
    108,1 KB · Görüntüleme: 68
Son düzenleme:
Son düzenleyen: Moderatör:
@bicy hocam dumplara baktım da pek anlamadım. Şu dosyaya sen de bakar mısın?

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1218

 Key : Analysis.Elapsed.mSec
 Value: 4524

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

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

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

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x101

 Key : Failure.Bucket
 Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

 Key : Failure.Hash
 Value: {95498f51-33a9-903b-59e5-d236937d8ecf}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc300c59d0180

BUGCHECK_P4: 1

FILE_IN_CAB: 010724-13843-01.dmp

FAULTING_PROCESSOR: 1

PROCESS_NAME: TslGame.exe

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffc300`c61f9c88 fffff805`82e37886 : 00000000`00000101 00000000`00000010 00000000`00000000 ffffc300`c59d0180 : nt!KeBugCheckEx
ffffc300`c61f9c90 fffff805`82c5945d : 00000000`00000000 ffffc300`c59e3180 00000000`00000246 00000000`00010255 : nt!KeAccumulateTicks+0x1e1646
ffffc300`c61f9cf0 fffff805`82c519b1 : 00000000`0000ff00 00000000`000099fa ffffc300`c59e3180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffc300`c61f9d40 fffff805`82c53873 : ffffc300`c59e3180 00000000`00000000 fffff805`83631960 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffc300`c61f9e80 fffff805`82c50a82 : ffffbe83`51f6edb0 ffffbe83`51f6ee30 ffffbe83`51f6ee00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffc300`c61f9f30 fffff805`82d00825 : 00000002`680066b6 ffffd808`fe6e9720 ffffd808`fe6e97d0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffc300`c61f9f60 fffff805`82dff6da : ffffbe83`51f6ee30 ffffd808`fe6e9720 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc300`c61f9fb0 fffff805`82dffee7 : 00000000`10022a36 ffffc300`c59e3180 00000000`00000002 ffffc300`c59e6130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffbe83`51f6edb0 fffff805`82c8f020 : 00000000`00000000 00000000`00000001 00000000`00000002 fffff805`82c6ba94 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffbe83`51f6ef40 fffff805`82c8ee38 : 00000000`00000000 ffffd809`169f2700 00000000`00000000 00000000`00000001 : nt!KeFlushMultipleRangeTb+0x160
ffffbe83`51f6efe0 fffff805`82c79ea9 : ffffd809`169f2700 000001fc`4f6c4000 00000000`00000000 ffffbe83`51f6f030 : nt!MiFlushTbList+0x88
ffffbe83`51f6f010 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFreeWsleList+0x119

SYMBOL_NAME: nt!KeAccumulateTicks+1e1646

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3803

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1e1646

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
---------

5: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.3, DMIVersion 0, Size=5863]
BiosMajorRelease = 5
BiosMinorRelease = 19
BiosVendor = American Megatrends International, LLC.
BiosVersion = FE
BiosReleaseDate = 06/07/2023
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H510M H
SystemFamily = H510 MB
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = H510M H
BaseBoardVersion = Default string
5: kd> !irql [Processor]
Debugger saved IRQL for processor 0x0 -- 0 (LOW_LEVEL)
5: kd> !irql
Debugger saved IRQL for processor 0x5 -- 13
5: kd> !irql 1
Debugger saved IRQL for processor 0x1 -- 0 (LOW_LEVEL)
5: kd> !irql 0
Debugger saved IRQL for processor 0x0 -- 0 (LOW_LEVEL)

@Hans evet. Olay görüntüleyicisine baktım. gcloud.exe diye bir yazılım var Gigabyte yazılımı onu kaldır. Dumpda da çeşitli şeyler denedim ancak diyeceğim şu. Bu hata çoğunlukla işlemci yanıt vermediğinde veya kilitlendiğinde meydana gelir. Ancak ben neyin buna sebep olduğunu bulamadım. Donanım sorunu olay görüntüleyicisinde geçmemiş. Öncelikle ağ sürücülerini güncelle. Bir de Prime95 15 dakika işlemci kararlılık testi yap.

Çeşitli yerlerden baktım ve minidump dosyasında bu hata kodu hataya götüren türden değilmiş. Ondan dolayı olay görüntüleyicisinde verdiği hatalara göre bakmak durumundayız.
 
Son düzenleme: