I've been getting quite a lot of CLOCK_WATCHDOG_TIMEOUT BSODs with this PC. And someone suggested disabling the Watchdog Timer itself. However, I can't find it. I can only find C-states. Is that it? If so I already disabled that one and the Blue screens kept appearing.

When booting into openSUSE Tumbleweed, I get " 7.374285 sp5100-tco sp5100-tco: Watchdog hardware is disabled" on a black screen.

Happens every once in a while, usually after updating. Hardware includes an AMD Ryzen CPU.

Any help appreciated.

Edit: I think it's caused by newer kernels. I'm experimenting with blacklisting sp5100_tco in kernel modules. So far, the error is gone but still a black screen. Might have to roll back to an older kernel.

Solution:

• I hit Ctrl+Alt+F3 or F4 to get a command prompt on the black screen.

• Created /etc/modprobe.d/sp5100_tco.conf and added blacklist sp5100_tco to that file.

• Ran sudo zypper dup.

Everything's good after reboot.

I came upon this Arch Wiki page covering topics on how to improve performance, and one of the topics covered is how to disable watchdogs. The wiki page states that "normal users (i.e. desktop and laptop) do not need this feature and can disable it".

To do so I followed the instructions: I appended nowatchdogto boot parameters in grub.cfg:

% nano /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet cryptdevice=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX:root cryptkey=rootfs:/etc/sys.keyfile root=/dev/mapper/root nowatchdog"

% grub-mkconfig -o /boot/grub/grub.cfg

I then blacklisted the hardware watchdog

% nano /etc/modprobe.d/disable-sp5100-watchdog.conf

blacklist sp5100_tco 

Upon reboot I ran the suggested tests with the following outputs:

Test 1

% cat /proc/sys/kernel/watchdog
0

Test 2

% wdctl
Device:        /dev/watchdog0
Identity:      wdat_wdt [version 0]
Timeout:       30 seconds
Timeleft:      600 seconds

I'm not entirely sure how to interpret this: Does this mean the watchdog is disabled or not? The first test seems to indicate so, but the second seem to indicate it is still active. Do they test different watchdogs?

Also, when shutting down the computer, I've been getting the following error messages:

[ 162.640363] watchdog: watchdog0: watchdog did not stop!
[ 163.168381] watchdog: watchdog0: watchdog did not stop!

Now, I was getting these messages before I attempted to disable watchdogs. However, these error messages persists after disabling, which indicate watchdog is still active.

In such case, what am I doing wrong?

Tech specs:

Host: 82JY Legion 5 17ACH6H 
Kernel: 6.1.11-arch1-1 
DE: GNOME 43.2 
CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 3.200GHz [44.2°C] 
GPU: NVIDIA GeForce RTX 3070 Mobile / Max-Q 
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
Memory: 4.57GiB / 29.24GiB 
GPU Driver: NVIDIA 525.89.02 

[SOLVED]

I checked journal, searching for "watchdog" (instead of "sp5100-tco" as I did initially). Turns out I did successfully blacklist the AMD chipset hardware watchdog, sp5100-tco and disable the nmi_watchdog by adding nowatchdog to the kernel parameters as described in the instructions. However, there is apparently another hardware watchdog in addition, named wdat_wdt (see journalctl output below), which turned out to be the perpetrator. By blacklisting it, the error messages upon shutdown are now gone, and wdctl can no longer find a an active watchdog:

/etc/modprobe.d/disable-wdat_wdt-watchdog.conf
blacklist wdat_wdt

However, the journalctl message: rtkit-daemon[XXX]: Watchdog thread running still persists, which I do not entirely understand.

Outputs:

wdctl

% wdctl
wdctl: No default device is available.: No such file or directory

journalctl

% journalctl --grep=watchdog

# Before deactivating any of the watchdogs

-- Boot b2de489efce44ec69b0db21ab81534a2 --
feb. 09 14:32:28 my_pc kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
feb. 09 14:32:29 my_pc kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
feb. 09 14:32:29 my_pc kernel: sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
feb. 09 14:32:34 my_pc rtkit-daemon[818]: Watchdog thread running.
feb. 13 11:33:56 my_pc sudo[127537]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/gnome-text-editor /etc/modprobe.d/disable-sp5100-watchdog.conf
feb. 13 11:34:50 my_pc systemd[1]: Using hardware watchdog 'wdat_wdt', version 0, device /dev/watchdog0
feb. 13 11:34:50 my_pc systemd[1]: Watchdog running with a timeout of 10min.
feb. 13 11:34:50 my_pc kernel: watchdog: watchdog0: watchdog did not stop!
feb. 13 11:34:50 my_pc systemd-shutdown[1]: Using hardware watchdog 'wdat_wdt', version 0, device /dev/watchdog0
feb. 13 11:34:50 my_pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.

# After blacklisting sp5100_tco and deactivating NMI watchdog

-- Boot 9058032ba2b84058ae17c4930098dced --
feb. 13 11:36:16 my_pc kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848d-44b1e66182da:root cryp>
feb. 13 11:36:16 my_pc kernel: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848d-44b1e66182da:ro>
feb. 13 11:36:18 my_pc /usr/lib/gdm-x-session[720]: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87>
feb. 13 11:36:22 my_pc rtkit-daemon[802]: Watchdog thread running.
feb. 13 11:36:38 my_pc /usr/lib/gdm-x-session[1078]: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f8>
feb. 13 11:39:48 my_pc sudo[2701]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/gnome-text-editor /etc/modprobe.d/disable-sp5100-watchdog.conf
feb. 13 13:37:53 my_pc systemd[1]: Using hardware watchdog 'wdat_wdt', version 0, device /dev/watchdog0
feb. 13 13:37:53 my_pc systemd[1]: Watchdog running with a timeout of 10min.
feb. 13 13:37:53 my_pc kernel: watchdog: watchdog0: watchdog did not stop!
feb. 13 13:37:53 my_pc systemd-shutdown[1]: Using hardware watchdog 'wdat_wdt', version 0, device /dev/watchdog0
feb. 13 13:37:53 my_pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.

# After blacklisting wdat_wdt

-- Boot 269bea6e8f8040b1858b6a9ed3ed30e3 --
feb. 15 13:01:53 my_pc kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848d-44b1e66182da:root cryptkey=>
feb. 15 13:01:53 my_pc kernel: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848d-44b1e66182da:root cr>
feb. 15 13:01:57 my_pc /usr/lib/gdm-x-session[764]: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848d>
feb. 15 13:02:01 my_pc rtkit-daemon[873]: Watchdog thread running.
feb. 15 13:02:57 my_pc /usr/lib/gdm-x-session[1488]: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ee34c9c4-7093-428d-9bd1-cc8475c262e4 rw rootflags=subvol=@ loglevel=3 quiet cryptdevice=UUID=a7f7243e-0a6f-4f87-848>
lines 475-506/506 (END)

Built a new PC and on BS start I get the blue screen error and forced computer restart.

Ryzen 5600X

Gigabyte 3070

16GB

Win 10

Everything else runs fine. I searched to stop/removed Hyper V its not even installed and don't have access to Memory Isolation as all the guides recommend.

Anything else I can do? Am I missing something?

[SOLVED]
for solution, follow reply chain of me and computix

ive been getting a bunch of BSOD's recently with this error code "DPC_WATCHDOG_VIOLATION", im pretty sure i know what the error code means and im slowly ruling out what might be causing it but i need someone to look at these 3 minidumps and tell me what might be causing it (and maybe how to solve it)

if it helps, i just recently wiped my entire computer, this BSOD never happened before that, i think it started after getting my essentials (discord, oculus, steam, amd chipset and gpu drivers) and roughly around when i started to download games on my 4tb hdd

md: https://www.mediafire.com/file/qv9kff8eikef7em/Minidump_%25283%2529.zip/file

system specs:cpu: AMD Ryzen 7 3700Xgpu: RTX 3060 12gb VRAM32 gigs of rammb: B550 UD ACstorage: 500gb m.2 SSD, 1tb HDD, 4tb HDDethernet

Hi everyone,

First of all I'm not an english native speaker so my message is not gonna be perfect

For a few weeks now my computer completely freezes randomly when I'm in game, sometime during game 1 and sometimes after 4 hours of playing. After 1 minute of freezing (not able to do anything during that time) I get a blue screen with the DPC_WATCHDOG-VIOLATION error and computer restarts normally.

___________________________________________________

Computer config :

MSI Katana B12VFK

Intel(R) Core(TM) i7-12650H

Nvidia Geforce RTX 4060 8go laptop gpu

Motherboard MSI 1585

_________________________________________________

I tried running whocrashed so you guys could maybe see what's going on, here are the analysis results :

On Tue 27/02/2024 01:37:13 your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\022724-27406-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x416C30)

Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8006511C340, 0x0)

Error: DPC_WATCHDOG_VIOLATION

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

________________________

I already reinstalled properly every driver from MSI website and using display driver uninstaller for GPU drivers, nothing changed.

Thank you for your time

I can only use the PC for ONE task at a time, for example: if i run a movie and copy some files in the background or run/install/uninstall a program or browse the internet my computer freezes restarts and this error shows up before the PC restarts CLOCK_WATCHDOG_TIMEOUT. Need help on how to resolve this. Thanks!

Here are my specs:

AMD RYZEN 7 SERIES OCTA CORE PROCESSOR 1700 - WITH WRAITH SPIRE COOLING SOLUTION (AM4 SOCKET, 20MB CACHE, UP TO 3.7 GHz)

MSI Gaming AMD Ryzen B350 DDR4 VR Ready HDMI USB 3 ATX Motherboard (B350 PC MATE)

Corsair Vengeance RGB LED 16GB (2x8GB) DDR4 3000 (PC4-24000) C15 - Intel 100/200 Series PC Memory (CMR16GX4M2C3000C15)

Zotac Amp Edition GeForce GTX 1060 6GB DDR5 PCI-e Graphics Card with IceStorm Cooling

Corsair RMx Series RM750x 750W Fully Modular Power Supply 80 PLUS Gold Certified

COOLER MASTER LIQUID COOLER - MASTERLIQUID LITE 120

Samsung 850 EVO 250GB 2.5-Inch SATA III Internal SSD (MZ-75E250BW)

Seagate Barracuda 2TB SATA 6Gb/s 64MB Cache 3.5-Inch Internal Bare Drive with 7200 RPM (ST2000DM006)

Arctic MX-4 Thermal Compound