Windows 10: DPC_WATCHDOG_VIOLATION 133 causing PC to force reboot despite no overclocking?

Hello, I have seen people with similar issues but as far as I'm aware there are none identical to what is happening to me, and I was hoping to get some insight.Over the last month and a bit I have been experiencing an issue where I will be in the middle of playing a game or something and my monitor loses signal. It shuts off, but I can still hear audio and communicate with people via Discord. After about a minute or two, the audio goes bust and my PC force reboots itself. Sometimes the monitor comes back on after these reboots, sometimes not and I have to manually turn off PC and back on again

:)

 

DPC_WATCHDOG_VIOLATION (133) causing PC to force reboot despite no overclocking?

Hello, I have seen people with similar issues but as far as I'm aware there are none identical to what is happening to me, and I was hoping to get some insight.

Over the last month and a bit I have been experiencing an issue where I will be in the middle of playing a game or something and my monitor loses signal. It shuts off, but I can still hear audio and communicate with people via Discord. After about a minute or two, the audio goes bust and my PC force reboots itself. Sometimes the monitor comes back on after these reboots, sometimes not and I have to manually turn off PC and back on again.

I have tried a LOT to troubleshoot this. I have uninstalled and reinstalled all of my drivers, I have reseated GPU and RAM in case it was a hardware issue (although Ive had this PC since June and no issues from then). I have reset Windows entirely and reinstalled drivers, I have changed the socket my PSU was plugged into, I have updated BIOS for my motherboard and I have done a memory test. My GPU is a Nvidia GeForce RTX 4070 and I have an MSI Pro B650 P motherboard. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80465d1d340, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fd8cdfd7-1ddc-4c28-a237-7a3e8cb9c02d. is the error I received on eventviewer after my latest crash, and I have linked the memory dump here.

MEMORY.DMP

I was just wondering if anyone had a clue as to what is going on, as I have been having this problem for weeks and so far no solution has done the trick. If any extra info is needed I would be happy to provide. I am not overclocking my GPU or anything, so i dont know why the 133 error would apply because the most intensive game I run is BG3 and that was fine before mid November ish. Anyways any suggestions would be much appreciated

 

DPC_WATCHDOG_VIOLATION (133)

The log files displayed a RAM overclock.

The BSOD debugging displayed no misbehaving drivers.

Turn off Windows Driver Verifier.

The RAM modules were not seen on the Qualified Vendor List (QVL)

a) Had they been checked to see if they were or were not on the QVL?

b) If not, please check now and report whether they are or are not on the QVL.

The CPU: Ryzen 7 5800X supports RAM up to 3200 MHz.

The RAM speed when the log collector ran was recorded at 3600 MHz.

c) Make sure that there is no overclocking during the troubleshooting.

d) Turn off XMP.

If there are continued BSOD after turning off the RAM overclock then swap test RAM that is displayed on the QVL.

133, 1A. 3B

 

DPC_WATCHDOG_VIOLATION (133)

Hi there,

I keep getting the DPC_WATCHDOG_VIOLATION (133). I ran the minidump file through WinDbg, but I don't know how to proceed from there, and I was hoping that someone could help me.

I've been trying to fix this for a bit, so I've been going down a list of possible fixes for watchdog violations and for "\Driver\WUDFRd failed to load." Among the things I've done, I've checked for updates (everything seems to be up to date), I've tried adjusting Windows Driver Foundation (but I couldn't locate it), I've reinstalled all the USB controllers, and I even reset the PC.

I would appreciate any help!!

Here's snip from WinDbg: