BSOD (DPC Watchdog Violations)

Good Evening everyone!

I will start this out by saying I am not an 85 year old grandmother trying to get on Facebook. I have been using computer since I was 8 (1993) and I am, for the first time, at a total loss. I keep getting intermittent BSOD (DPC Watchdog Violations). I have had this on two computers now, one a stock lenovo small form factor desktop and the other is a rig i just built myself. The only overlapping feature between the two is that I have installed windows on each. I don't really care about the lenovo but the new rig I just bought needs to work; therefor, I am reaching out in hopes to find a solution from a community of like minded individuals.

My PC:
Intel Core i7-7700
ASROCK Fatal1ty B250 Gaming K4
XFX Radeon RX 570 RS XXX Edition
TEAMGROUP Elite Plus DDR4 16GB Kit (2x8GB) 2400MHz PC4-19200 CL16 Unbuffered Non-ECC 1.2V U-DIMM 288 Pin
Sabrent 256GB Rocket Nvme PCIe M.2 2280 Internal SSD High Performance Solid State Drive (SB-ROCKET-256)
DiabloTek PHD550 PHD Series ATX 550w PSU

Other peripherals:
22" Planar 1080p touchscreen monitor
x2 19" Sceptre 1600x900 monitors
Avolusion HDDGear 6TB (6000GB) 7200RPM 64MB Cache USB 3.0 External PS4 Gaming Hard Drive (PS4 Pre-Formatted)- I reformatted when it arrived for NTFS
A OTA Digital TV Converter (for my plex server)
A bluetooth dongle, wireless mouse and keyboard as well.

Attempts at Remediation:
Tried wiping the drive and starting fresh.
Tried swapping out all parts listed above, one by one.
Tried updating every driver
Checked compatibility for all hardware

Any help would be greatly appreciated, I am at a total loss and about to give up on windows, and go play online pinochle and try to figure out how to post videos to facebook all day long with my grandmom.

Hi please follow this and someone will try to help you. BSOD - Posting Instructions

Thank you, I have attached the log to this entry.

Two of the dumps suggest the driver "WiseTDIFw64.sys" might be involved. Have you tried uninstalling the program that installed it to see if the problems continue? I believe it's a component of Wise Disk Cleaner.

That is a system monitor I use to keep an eye on temps and usage. That could cause the bsod? I am pretty sure I have seen the violations happen before I got that program. I will uninstall and report back. The system crashes at least once a day so I'll let you know if that fixes it. Thanks for the suggestion!

I'd at least check to see if there is an update to the program if you want to continue using it. The version of that driver loading on your system has a 2016 timestamp which, by itself, would make me nervous.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Upgrade the BIOS:
2.0 > 2.2
ASRock > Fatal1ty B250 Gaming K4

15) Turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10

16) post a share link for any memory dump < 1.5 GB

Code:

LastWriteTime        Size (MB) FullName             
-------------        --------- --------             
2/11/2020 7:51:48 PM   1013.24 C:\Windows\MEMORY.DMP

WiseTDIFw64.sys Thu Jul 28 18:59:01 2016 (579AB865)
avgNetSec avgNetSec.sys Fri Sep 6 03:10:07 2019 (5D72307F)
avgbidsdriver avgbidsdriver.sys Fri Sep 6 02:31:17 2019 (5D722765)
avgSnx avgSnx.sys Thu Sep 26 05:03:04 2019 (5D8CA8F8)
avgMonFlt avgMonFlt.sys Tue Oct 29 03:15:36 2019 (5DB81148)
avgStm avgStm.sys Fri Sep 6 03:10:17 2019 (5D723089)
rtwlanu.sys Tue May 22 22:44:29 2018 (5B04FFBD)

Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
174592 file records processed.
File verification completed.
2026 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
196 reparse records processed.
282224 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
196 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
53817 data files processed.
CHKDSK is verifying Usn Journal...
35647040 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249398271 KB total disk space.
35549668 KB in 118228 files.
98080 KB in 53818 indexes.
0 KB in bad sectors.
284863 KB in use by the system.
65536 KB occupied by the log file.
213465660 KB available on disk.

4096 bytes in each allocation unit.
62349567 total allocation units on disk.
53366415 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-2GC1O8L\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-2GC1O8L\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

- - - Updated - - -

Were one of the 12 commands above supposed to perform a memory dump?