• Our team is working to address issues posting quotes or media to the forums. Please bear with us as we get this sorted out.

Question Clock_Watchdog_Timeout (101)

Mar 15, 2021
17
0
10
0
Having Issues with my build, Randomly crashing for apparently no reason giving me the error Clock_Watchdog_Timeout. Form what I can see no one really knows what this means.

I've recently replaced the PSU with a CV550 as I was recommended to do so but this hasn't sorted the problem. I've tried changing what RAM stick is in which slot and am currently testing the 1st stick in the second slot so I'll update on if that fixes it or not.

I've upgraded all the drivers and BIOS, nothing is showing in Task Viewer but BlueScreenView says it's related to "ntoskrnl.exe+3f5c50". I've also downloaded WinDbg and this is what it's telling me:

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

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

*** WARNING: Unable to verify timestamp for Netwtw10.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9374

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 35599

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

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

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

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

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9b80e65e7180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

FAULTING_THREAD: ffffda89965e5040

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffff9a84048fe098 fffff8016130a6d2 : 0000000000000000 ffff9a84048f9000 ffff128507e7c1f9 ffff9a84048fdfc8 : nt!HalpPciReadMmConfigUlong+0x7
ffff9a84048fe0a0 fffff8016130a502 : 0000000000000026 0000000000000100 0000000000000000 0000000000000000 : nt!HalpPCIPerformConfigAccess+0x5a
ffff9a84048fe0d0 fffff8016130a3d7 : 0000000000000000 0000000000000100 ffffda899c1ddb9c 0000000000000000 : nt!HalpPciAccessMmConfigSpace+0x82
ffff9a84048fe110 fffff8016130a2f2 : 0000000000000100 ffffda89966d01f0 ffffda899c1ddb9c 0000000000000026 : nt!HalpPCIConfig+0xa7
ffff9a84048fe190 fffff801626020c8 : ffffda899c1ddb9c ffffda899c1ddb9c ffffda8992662f88 fffff801619dee18 : nt!HaliPciInterfaceReadConfig+0x32
ffff9a84048fe1e0 fffff80162751646 : ffffda8996671240 ffffda899c1ddb9c 0000000000000006 fffff80160de129b : ACPI!AcpiWrapperReadConfig+0x28
ffff9a84048fe230 fffff80162efa906 : 0000000000000000 0000000000000000 ffffda899c1ddb9c ffffda8900000000 : pci!PciBusInterface_GetBusData+0x636
ffff9a84048fe310 fffff803026182f5 : 0000000000000100 ffffda89a7b1c4a0 ffffda899c1ddb9c 0000000000000000 : ndis!NdisMGetBusData+0xa6
ffff9a84048fe370 0000000000000100 : ffffda89a7b1c4a0 ffffda899c1ddb9c 0000000000000000 0000000000000100 : Netwtw10+0x1682f5
ffff9a84048fe378 ffffda89a7b1c4a0 : ffffda899c1ddb9c 0000000000000000 0000000000000100 0000000000000008 : 0x100
ffff9a84048fe380 ffffda899c1ddb9c : 0000000000000000 0000000000000100 0000000000000008 0000000000000001 : 0xffffda89a7b1c4a0
ffff9a84
048fe388 0000000000000000 : 0000000000000100 0000000000000008 0000000000000001 fffff8030263b27c : 0xffffda899c1ddb9c


STACK_COMMAND: .thread 0xffffda89965e5040 ; kb

SYMBOL_NAME: pci!PciBusInterface_GetBusData+636

MODULE_NAME: pci

IMAGE_NAME: pci.sys

IMAGE_VERSION: 10.0.19041.870

BUCKET_ID_FUNC_OFFSET: 636

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_VRF_pci!PciBusInterface_GetBusData

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {64a8ad8d-6659-dc41-42e6-664fb4d1735a}

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




If you need more info just ask

Specs:
CPU: Ryzen 5 2600
GPU: GTX 1650
Motherboard: MSI A320M-A Pro Max
RAM: 16GB (2x8GB) DDR4
SSD: 1TB SSD
PSU: CV550

Thanks in advance,
GetYaArmour
 
The two things I would try is resetting your bios and if that doesn't work, replace the battery. If this doesn't work I would also try re-seating your cpu and checking the cpu and socket carefully for anomalies/damage.
 
Mar 15, 2021
17
0
10
0
The two things I would try is resetting your bios and if that doesn't work, replace the battery. If this doesn't work I would also try re-seating your cpu and checking the cpu and socket carefully for anomalies/damage.
Resetting bios has not worked.
I'm using a desktop which doesn't have a battery.

I guess I could check the cpu
 
Mar 15, 2021
17
0
10
0
If you didn't install the cpu, then I don't think the re-seat will help and the cpu or motherboard may have failed.
Reseat did not work, do you have any suggestions on what I should try next? Or will I need it to be sent somewhere to see if they can repair it?
 
Thread starter Similar threads Forum Replies Date
W CPUs 3

ASK THE COMMUNITY

TRENDING THREADS