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?

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.

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)

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.

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

Here are some breadcrumbs for anyone debugging random reboot issues on Proxmox 8.3.1 or later.

tl:dr; If you're experiencing random unpredictable reboots on a Proxmox rig, try DISABLING (not leaving at Auto) your Core Watchdog Timer in the BIOS.

I have built a Proxmox 8.3 rig with the following specs:

• CPU: AMD Ryzen 9 7950X3D 4.2 GHz 16-Core Processor

• CPU Cooler: Noctua NH-D15 82.5 CFM CPU Cooler

• Motherboard: ASRock X670E Taichi Carrara EATX AM5 Motherboard 

• Memory: 2 x G.Skill Trident Z5 Neo 64 GB (2 x 32 GB) DDR5-6000 CL30 Memory 

• Storage: 4 x Samsung 990 Pro 4 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive

• Storage: 4 x Toshiba MG10 512e 20 TB 3.5" 7200 RPM Internal Hard Drive

• Video Card: Gigabyte GAMING OC GeForce RTX 4090 24 GB Video Card 

• Case: Corsair 7000D AIRFLOW Full-Tower ATX PC Case — Black

• Power Supply: be quiet! Dark Power Pro 13 1600 W 80+ Titanium Certified Fully Modular ATX Power Supply 

This particular rig, when updated to the latest Proxmox with GPU passthrough as documented at https://pve.proxmox.com/wiki/PCI_Passthrough , showed a behavior where the system would randomly reboot under load, with no indications as to why it was rebooting.  Nothing in the Proxmox system log indicated that a hard reboot was about to occur; it merely occurred, and the system would come back up immediately, and attempt to recover the filesystem.

At first I suspected the PCI Passthrough of the video card, which seems to be the source of a lot of crashes for a lot of users.  But the crashes were replicable even without using the video card.

After an embarrassing amount of bisection and testing, it turned out that for this particular motherboard (ASRock X670E Taichi Carrarra), there exists a setting Advanced\AMD CBS\CPU Common Options\Core Watchdog\Core Watchdog Timer Enable in the BIOS, whose default setting (Auto) seems to be to ENABLE the Core Watchdog Timer, hence causing sudden reboots to occur at unpredictable intervals on Debian, and hence Proxmox as well.

The general intention of the Core Watchdog, since many people in the comments seem confused about this, is a Hail-Mary type play where, if the OS does not occasionally hit a bit on the motherboard saying "I'm still alive", then the hardware assumes that the OS has hung, and reboots the entire machine. However. As it turns out, there are multiple situations in normal operation where Debian does NOT update the Core Watchdog at tempo -- probably having to do with power management -- and so you get spurious random reboots with Core Watchdog enabled.

The workaround is to set the Core Watchdog Timer Enable setting to Disable.  In my case, that caused the system to become stable under load.

Because of these types of misbehaviors, I now only use zfs as a root file system for Proxmox.  zfs played like a champ through all these random reboots, and never corrupted filesystem data once.

In closing, I'd like to send shame to ASRock for sticking this particular footgun into the default settings in the BIOS for its X670E motherboards.  Additionally, I'd like to warn all motherboard manufacturers against enabling core watchdog timers by default in their respective BIOSes.

EDIT: Following up on 2025/01/01, the system has been completely stable ever since making this BIOS change. Full build details are at https://be.pcpartpicker.com/b/rRZZxr .

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

I wanted to share a frustrating issue I've been dealing with on my Beelink SER8 and see if I'm the only one experiencing this.

Starting yesterday, my mini PC began freezing completely. The symptoms were very specific:

• It would freeze right on the Beelink boot logo

• If I managed to get into Windows, it would freeze about 20 seconds after login.

Weirdest part: The mouse cursor would still move smoothly, but the entire Windows interface was completely frozen and unclickable. After about 20 seconds of hang, it would crash with a DPC_WATCHDOG_VIOLATION (0x133) BSOD.

I initially thought my internal NVMe SSD was dying or had a loose connection, but after some troubleshooting (and realizing it was a classic storage I/O hang), I traced it back to the recent AMD Chipset Drivers update - Version 8.05.04.516.

I managed to completely uninstall this specific chipset driver package, and the system immediately became stable again. I'm going to do a clean reinstall of Windows 11 tomorrow just to be completely safe and wipe any corrupted leftover files.

Has anyone else run into this issue with the 8.05.04.516 driver version?

I just built my pc but I'm having trouble with the ryzen cpu. Every time I turn on the pc it stays for like 15 minutes and I get a BSOD with Clock watchdog timeout. I tried updating bios from f2 to f10 but it didn't solve my problem. Does anyone have an idea of why this is happening? Here are the parts I'm using: Thermaltake v1 core Gigabyte a520i ac Ryzen 3 3100 Oloy 16gb 3200 mhz Nvidia gtx 745 Evga 80+ 500w

Status: RESOLVED I guess my Win10 iso was too old or corrupt. I redownloaded the iso using microsoft media creation tool and Windows hasn't crashed, even played a few games.

Computer Type: Desktop

GPU: MSI 980 ti

CPU: AMD Ryzen 1700

Motherboard: Asrock x370 k4

RAM: Gskill F4-3000C16D-16GISB

PSU: Corsair TX750w v2

Operating System & Version: Windows 10 pro

GPU Drivers: Latest available

Chipset Drivers: Latest available

Background Applications:

Description of Problem: BSOD x101 Clock Watchdog Timeout

Troubleshooting: installed Windows updates, AMD drivers, Disable HPET, raising vcore, and latest beta bios. I was able to install Windows 7 Ultimate and so far it hasn't crashed in 1 hour. It usually freezes within 10 minutes. Is this going to be a motherboard/driver issue? I don't want to be stuck with Win7 forever.

I just bought this cpu. I did a complete fresh windows 10 install and i keep getting this bsod. My cpu temp is steady at 35C, however i am on build 10240 now which is a very early build could this be the cause ? Also for some weird reason my ram which should run at 2400mhz are detected by cpuz and the task manager as running at 1200mhz, back when i was on ddr3 they would show me 1333mhz . Last but not least, each time i start my pc. I get a black screen for a more than 10 seconds before the bios logo actually shows . Why does this happen. I have an msi b350 arctic. I never overclocked btw. Thanks in advance, please help

OS: Windows 11 (Version: 23H2, Build: 22631.4317)

CPU: AMD Ryzen 9 5900X

GPU: FE RTX 3080

RAM: Corsair Vengeance RGB Pro 32GB

I'm not certain on the exact date of when this started happening, but it's been going on for about 3-4 months now.

Every time I lock my PC (Win + L), I am guaranteed to get a DPC crash. I know this because I've left my PC for weeks without locking it and never got the crash. But when I lock it, I crash within the hour. When the crash happens, my PC doesn't fully reboot. It freezes at 100% and I have to cycle the PSU.

I've tried diagnosing the issue myself by analyzing dump files in WinDBG, but I've read conflicting things about how reliable these dump files can be. Most of them pin the cause on Discord or Steam. I reinstalled both. The most recent dump file (10/29) points to svchost.

I've followed the first 3 steps in this video: https://www.youtube.com/watch?v=Ijgq59hQ2Zk . I reinstalled Windows/used their repair tool without deleting my files. No dice.

Not sure what else to do besides a clean reinstall of Windows. I guess I can just never lock my computer but I'd prefer not to.

Here's a link to dump files: https://www.mediafire.com/file/pcesi3fnjydzufj/Minidump.zip/file

EDIT: I seemed to have resolved the issue after doing these two steps. Don't know which was the root cause.

1. Completely uninstalled and reinstalled nvidia graphics drivers using DDU.

During this process, I ran into multiple freezes during startup and some dpc watchdog timeouts. After many restarts, my computer seemed stable.

However, Valorant would randomly crash with out of memory errors, especially if I had discord running. Sometimes my system would freeze again with no blue screen. This lead me to...

2. Set swap file size to be managed by system. I had disabled this and set my own value (half of my 32GB of RAM) because The Last of Us would create massive swap file and not free up space after quitting the game. After setting it back to manage by system, no crashing in Valorant. Also, no DPC error after locking PC for couple of hours.

Since DPC errors are typically driver related, I assume the graphics driver was the issue.

AMD release new driver to fix this issue:

AMD Radeon Software Adrenalin 23.3.1

Release Note:

Intermittent driver timeout, system freeze or BSOD may be observed using select displays on Radeon™ RX 7000 series GPUs.

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-3-1

However, some monitor still have this issue!!

Not fix totally.

Tracking thread from AMD Community (BSOD issue with Adrenalin 23.3.1).

Upate: 24.3.2 still not fix.

https://community.amd.com/t5/drivers-software/driver-crashes-when-adaptivesynccompatible-is-enabled/m-p/591925#M171291

===================================================================

Tracking thread from AMD Community.

https://community.amd.com/t5/drivers-software/dpc-watchdog-violation-amdkmdag-sys-rx-7900-xtx-xt-discussion/m-p/586573#M169748

Dears, 7900 XTX/XT user,

If you have this BSOD issue, you can try to disable FreeSync and please let me know if that fixed it.

And please help to use AMD Radeon Bug report to AMD, let them aware this problem.

Thanks!

Temporary Workaround (try all of them):

1. Disable FreeSync (Adaptive-Sync) from AMD driver.

2. Disable Windows Variable Refresh Rate.

3. Disable FreeSync (Adaptive-Sync) from Display OSD.

How to Enable or Disable Variable Refresh Rate (VRR) in Windows 11

https://www.howto-connect.com/disable-enable-variable-refresh-rate-vrr-windows-11/

Dear AMD Engineer, please help to check this problem!

u/AMD_PoolShark28 u/AMD_Vik

Thank you very much!

System & BSOD info please reference this post:

https://www.reddit.com/r/AMDHelp/comments/105nhoe/rx_7900_xtx_ref_card_system_hang_when_launch_some/

Similar issue from Internet (7900 XTX/XT):

DPC_Watchdog_Violation

https://www.reddit.com/r/AMDHelp/comments/11282zj/dpc_watchdog_violation/j8pb92a/?context=3

ntoskrnl.exe 428700 and 010523-10015-01.dmp 123122-9312-01.dmp

https://answers.microsoft.com/en-us/windows/forum/all/ntoskrnlexe-428700-and-010523-10015-01dmp-1231...

BlueScreen DPC_WATCHDOG_VIOLATION 0x00000133 00000000`00000001 , freeze and after 30 Secounds the BOD comes.

https://answers.microsoft.com/en-us/windows/forum/all/bluescreen-dpcwatchdogviolation-0x00000133/fa1...

Random freeze then bluescreens error DPC watchdog violation

https://answers.microsoft.com/en-us/windows/forum/all/random-freeze-then-bluescreens-error-dpc-watch...

For RX 7900 Series driver with refresh rates above 60 hz may cause BSOD

https://forums.guru3d.com/threads/for-rx-7900-series-driver-with-refresh-rates-above-60-hz-may-cause...

7900xt DPC_Watchdog_Violation BSOD

https://community.amd.com/t5/graphics/7900-xtx-freezing-and-bluescreens-after-30-secounds/m-p/571413...

7900 XTX freezing and Bluescreens after 30 secounds

https://community.amd.com/t5/graphics/7900-xtx-freezing-and-bluescreens-after-30-secounds/m-p/571413...

7900 XT Intermittent freezing

https://community.amd.com/t5/graphics/7900-xt-intermittent-freezing/m-p/570824#M92623

7900 XTX 와 FreeSync 상태에서 60Hz+ 동시 사용시 문제   dpc watchdog violation

https://quasarzone.com/bbs/qf_vga/views/5532370

How to check:

After BSOD, you can get minidump file.

C:\Windows\Minidump

Used Windbg to check the callback and module name:

If you see this module name and BSOD reason, you can try to disable FreeSync.

*You can upload your windows minidump and give it to u/AMD_Vik

https://send.vis.ee/

Hope it can help AMD Driver team to analyze this issue.

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

SYMBOL_NAME: amdkmdag+22559fd

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

BSOD

As the title suggest I got this BSOD when using the computer, I have had this pc for 2 days and yesterday it only happened once, today after windows update it crashed 3 times in a row any help? Maybe the realtek wifi chip? Or maybe I need to update bios?

Here is a minidump of the 4 cases: https://drive.google.com/file/d/1zhkL7_Po14Aax_kHPOmrRcz9loe3qDDa/view?usp=drivesdk

I recently built a PC with the following specs:

Mobo: ASUS ROG STRIX B650E-F GAM WF Current bios is rev 2412, updating to 2616.

Ram: G.SKILL 32G 2X D5 6000 C36 FX B - Not running XMP, sleep is disabled with it on

CPU: AMD RYZEN 9 7900X

PSU: ASUS TUF 750W 80+G ATX3 PSU

GPU: 4070TI-S Asus STX4070TISO16G Current drivers are 551.23 will update to 555.85

SSD: SAMSUNG 2TB 980PRO

Running Windows 10, tried 11 for about 3 days. No missing drivers. Has passed Memtest86 and has no problems running prime95 and/or Furmark. This issue has been appearing since the initial build and I have yet to figure out the cause. There are no memory dumps. There is no discernable pattern. While using the pc, it will become mostly unresponsive for 60-90 seconds before it reboots on it's own.

There is nothing that I can tell for where to start to diagnose this issue in event viewer. The issue starts with "The system watchdog timer was triggered." the next event is "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

I am out of ideas. Please assist.

Hey all,

I just finished building my new gaming computer and I borrowed a Windows 10 usb media booter from a friend and installed windows 10. He said it was an older version so I need to install updates but when I was getting everything configured I was getting a BSoD and the error code DPC_Wathcdog_Violation about every 10-15 minutes. I haven't updated any of the windows drivers yet and this is a dated version of the windows 10 booter. Should I be concerned that this is a hardware issue? All my parts are brand new. I've heard of Ryzen cpu's and windows 10 not getting along. Anyone else have experience with this? Any advice would be much appreciated. PO that I just dropped 800 on a new system for this to happen.

Here is my build: PCPartPicker part list: https://pcpartpicker.com/list/3DTVpG Price breakdown by merchant: https://pcpartpicker.com/list/3DTVpG/by_merchant/

CPU: AMD - Ryzen 3 2200G 3.5 GHz Quad-Core Processor ($94.89 @ OutletPC) Motherboard: ASRock - B450 Pro4 ATX AM4 Motherboard ($88.56 @ OutletPC) Memory: Corsair - Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 Memory ($104.99 @ Amazon) Storage: Kingston - A400 240 GB 2.5" Solid State Drive ($29.99 @ Amazon) Storage: Western Digital - Caviar Blue 1 TB 3.5" 7200RPM Internal Hard Drive ($44.89 @ OutletPC) Video Card: XFX - Radeon RX 570 8 GB Video Card ($139.99 @ Newegg) Case: Fractal Design - Focus G (White) ATX Mid Tower Case ($49.13 @ Amazon) Power Supply: Corsair - CX (2017) 450 W 80+ Bronze Certified ATX Power Supply ($46.88 @ OutletPC) Fan Controller: Thermaltake - Commander FT Fan Controller ($39.48 @ Amazon) Other: CUK 6-Pack Red Halo Ring 120mm LED Vibrant Color Computer Case Fan for CPU Coolers and Radiators - High Airflow 45 CFM & Anti-Vibration Pads ($22.49 @ Amazon) Total: $661.29

Thank you,

Caulin