[SOLVED] “BSOD Clock Watchdog Timeout” when connecting to internet ?

Nov 8, 2022
4
0
10
0
Hello,
I keep getting a BSOD with the CLOCK_WATCHDOG_TIMEOUT error when I connect to the internet. PC just keeps on rebooting from then on. If it's not connected it doesn't crash, so that seems to trigger the BSOD. Please help.

Things I tried
  • connecting with the motherboard WIFI, external network card, or with a ethernet cable, but it still crashes.
  • updating chipset, GPU, and WIFI drivers
  • updating bios
  • reinstalling windows
  • reinstalling windows on another drive
  • testing RAM with memtest86 (no errors)
  • checked cable connections
Specs
CPU - ryzen 3900x
GPU - gtx 1660
MB - MSI MAg X570 TOMAHAWK WIFI
RAM - 2x Crucial ddr4 16GB (32GB) 3200MHz
SSD 1 - Samsung nvme evo plus 500GB
SSD 2 - WD SN550 nvme 1TB
PSU - Corsair RM650
Network Card - AC600 Wireless PCIE adapter

Dump file
https://drive.google.com/file/d/1GLZjL-9ffQwEZEcXSFVi7rhtb5udMlUv/view?usp=share_link
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
61,160
5,187
166,290
10,453
that was what i was thinking too, its just random.

no real tests for motherboard, only choices are test everything else. You have done that.
Other choice is put everything in another PC and see if you get errors.

repair store would be one choice. Better than buying new motherboard... could contact MSI and see what they suggest.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
61,160
5,187
166,290
10,453
report - click run as fiddle to read

File: 110722-3640-01.dmp (Nov 8 2022 - 17:28:12)
BugCheck: [CLOCK_WATCHDOG_TIMEOUT (101)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 33 Sec(s)

try updating drivers for these
May 14 2019Netwtw08.sysIntel(R) Wireless Networking driver
May 24 2019rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
both were running at time of crash
Realtek: download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

Intel - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

I wonder what hates internet
Try running Prime 95 - - https://www.guru3d.com/files-details/prime95-download.html
Prime 95 Instructions - https://appuals.com/how-to-run-a-cpu-stress-test-using-prime95/
 
Nov 8, 2022
4
0
10
0
Thanks,

Updated both drivers, still get BSOD when I try to connect. Maybe I'm installing them incorrectly?

Ran Prime 95 for a few hours, no errors
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
61,160
5,187
166,290
10,453
It seems unlikely to me that you installing drivers wrong for 3 different network connectors and on 2 installs of windows on 2 different drives, you would have to be unlucky.

connecting with the motherboard WIFI, external network card, or with a ethernet cable, but it still crashes.
which is why I looked somewhere else.

How old is PC? How long have you had problem for?
it crashing on wifi & Ethernet sort of removes the cable from blame.

is that 1 set of ram or 2? it doesn't help me that crucial sell those sticks in sets and by themselves with the same codes.
 
Nov 8, 2022
4
0
10
0
PC is more than 2 years old. Blue screens started a week ago.

The ram is a set of 2 sticks

At this point I think it's some hardware problem with the motherboard.
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
61,160
5,187
166,290
10,453
that was what i was thinking too, its just random.

no real tests for motherboard, only choices are test everything else. You have done that.
Other choice is put everything in another PC and see if you get errors.

repair store would be one choice. Better than buying new motherboard... could contact MSI and see what they suggest.
 
clock timeout was 8 clock ticks. This means that you have a hung cpu processor.
you would have to have someone look at a kernel memory dump and see what is running on the hung cpu core. often it will be the plug and play system loading a driver on one core while another core tries to use the driver. !pnptriage command on kernel dump should show the plug and play info.

general fixes for this type of issue would be bios update/ chipset updates remove all overclocking. basically one cpu core did not respond to another cpu core in its time out period.

I should point out the system uptimer was 33 seconds
if you think the system was running longer than that then you would need to look into why the system reset rather than trying to figure out the bugcheck.
common cause for this would be power issue and psu that fakes power_ok signal
 
Last edited:
Reactions: Colif

ASK THE COMMUNITY

TRENDING THREADS