Question BSOD | DPC Watchdogs Violation

[Kominator]

Hello everyone, forgive my English, I'm using google translator.

I formatted a few days for W11 and I updated the bios together (I used the 1 bios from the Ryzen 5000 release) and since Sunday I have BSOD related to the dpc watchdog violation. I've already performed all the procedures I saw on the internet and even formatted for W10 and the error persists.

I checked the memories both in memtest86 and in another computer and they show no error. I read that this BSOD is related to the driver, but I don't know which one could be incompatible, I've already used the DDU and installed the August driver for my video card and it persisted.
I used overclocking with undervolt on my processor, I already did a BIOS reset and went back a few versions to see if it solved and it didn't change anything either. Even without overclocking the entire ecosystem, BSOD continues at random times

Google Drive: BSODs & Freezing | Win 10
I uploaded the files found in the minidump and also the MEMORY.DMP if necessary to help solve this problem

My specs: Ryzen 5 5950X, Asus Rog B550-F, 64GB (4x16GB/3200Mhz) Crucial, RTX 3070, Power Supply Corsair 850W, Version 21H2 (OS Build 19044.2075) , Gigabyte SSD (GP-ASM2NE6100TTTD), Adata SX8100NP, 2x HDD (backup files)

 

[bmockeg]

There have been multiple Agesa updates since Ryzen 5000 release. You need to get the last one BEFORE 5800x3d support

 

[Kominator]

There have been multiple Agesa updates since Ryzen 5000 release. You need to get the last one BEFORE 5800x3d support

I put the bios I was using before the 1212 that was when the B550-F received support for the Ryzen 5000 and it's still crashing

 

[bmockeg]

I put the bios I was using before the 1212 that was when the B550-F received support for the Ryzen 5000 and it's still crashing

Try 2423

 

[Kominator]

Try 2423

It was already in this BIOS when it started to give the BSOD

Google Drive DUMP Files

According to the crash that just happened, even after I formatted it found an error in the RTX Broadcast driver that I always used

 

[bmockeg]

It was already in this BIOS when it started to give the BSOD

Google Drive DUMP Files

According to the crash that just happened, even after I formatted it found an error in the RTX Broadcast driver that I always used

Software can cause issues. Does it happen if you delete the broadcast software

 

[Kominator]

Software can cause issues. Does it happen if you delete the broadcast software

I also saw that on the blizzard forum several users were having the same problem with the RTX cards as they also used Nvidia Broadcast, I had noticed that it had not crashed while playing without it installed with a clean install.
https://us.forums.blizzard.com/en/o...ying-overwatch-2-anyone-else/703198/22?page=2

I took it moments ago and now it's testing

 

[Colif]

It was already in this BIOS when it started to give the BSOD

Google Drive DUMP Files

According to the crash that just happened, even after I formatted it found an error in the RTX Broadcast driver that I always used

The cause in that is an Nvidia driver
if the screenshot is from the last BSOD I can probably find the driver name from the above results? or have you updated Nvidia drivers this week?

First post dumps results: I didn't download the 1.54gb dump file, I will if I need to.

Conversion of dumps

report - Click run as fiddle to see report

Spoiler

File: 100622-9671-01.dmp (Oct 7 2022 - 04:03:07)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 42 Sec(s)

File: 100622-11796-01.dmp (Oct 7 2022 - 03:58:49)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 13 Min(s), and 20 Sec(s)

File: 100522-9515-01.dmp (Oct 6 2022 - 04:50:37)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: memory_corruption (Process: Discord.exe)
Uptime: 0 Day(s), 0 Hour(s), 42 Min(s), and 57 Sec(s)

File: 100522-17328-01.dmp (Oct 6 2022 - 03:15:55)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for nvrtxvad64v.sys
Probably caused by: memory_corruption (Process: NVIDIA Broadcast.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 28 Sec(s)

File: 100522-17328-02.dmp (Oct 6 2022 - 03:20:22)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for nvrtxvad64v.sys
Probably caused by: memory_corruption (Process: NVIDIA Broadcast.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 20 Sec(s)

Driver verifier is saying its the Nvidia drivers for at least 2 of them.

Aug 07 2020

nvrtxvad64v.sys

NVIDIA RTX Voice driver

I would run DDU in safe mode, uninstall Nvidia drivers, and once back into normal mode update drivers

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

Comment: The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2) << its an Asus motherboard so its possible this loaded with its drivers but are you using GPU Tweak? possible there is a newer version. If you have it and don't use, should take it off.