Windows 10: Windows 10 Freezing followed by Watchdog Violation Blue Screen

I've been having some major issues with my custom built pc recently.
Specs:

Windows 10 Pro 64-bit
Motherboard: Asus X99-E WS/USB 3.1
CPU: Intel i7 5960X overclocked (stable) @4.3GHz
RAM: 64GB 2400MHz, I think it was HyperX
GPUs: 2 Nvidia GeForce GTX Titan X (Pascal)'s in SLI
Main C: Drive is a Samsung 960 Evo 500GB NVMe SSD

So, I'll just be doing normal, every day type things like web browsing, watching videos, or launching programs, and then the whole screen freezes in place, the screen doesn't turn black, and then after about 30 seconds to a minute, I get the blue screen of death and the infamous "DPC WATCHDOG VIOLATION" error.
I'll reboot and one time it didn't even get past the sign in screen before it froze and crashed again.

The Minidump file that I uploaded to OSR Online's Instant Online Crash Analysis said this:

"Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`0ea95000 PsLoadedModuleList = 0xfffff800`0ee43150
Debug session time: Sat Oct 27 22:36:04.516 2018 (UTC - 4:00)
System Uptime: 0 days 6:06:47.375
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8000eee2378
Arg4: 0000000000000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff8000ec90495 to fffff8000ec3e490

STACK_TEXT:
fffff800`0e73a208 fffff800`0ec90495 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`0eee2378 : nt!KeBugCheckEx
fffff800`0e73a210 fffff800`0eb741ad : 00003c37`c74f446a fffff800`0e434180 00000000`00000246 00000000`00157dd8 : nt!KeAccumulateTicks+0x1187d5
fffff800`0e73a270 fffff800`0eb75293 : fffff780`00000340 fffff800`0e434180 00000000`00157dd8 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff800`0e73a2c0 fffff800`0ea0a883 : 00003c37`c74f372e fffff800`0e73ab22 00000000`00000000 fffff800`0e73a690 : nt!KeClockInterruptNotify+0x8f3
fffff800`0e73a5d0 fffff800`0ebc1d75 : fffff800`0ea6bcb0 fffff800`0ea0a883 ffff3df2`815f817b fffff800`0e73ab22 : hal!HalpTimerClockInterrupt+0x63
fffff800`0e73a600 fffff800`0ec3fd4a : fffff800`0e73a710 fffff800`0ea6bcb0 fffff800`0e73ab50 ffffdd85`b5a87930 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`0e73a640 fffff800`0ec40237 : fffff800`0e73ab50 fffff800`0ea0c4e6 ffffdd85`b67db000 00000000`006118bc : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff800`0e73a690 fffff800`be33c825 : fffff800`be35f870 ffffdd85`b67db000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`0e73a828 fffff800`be35f870 : ffffdd85`b67db000 00000000`00000000 00000000`00000000 fffff800`be35d7c9 : nvlddmkm+0x1ec825
fffff800`0e73a830 ffffdd85`b67db000 : 00000000`00000000 00000000`00000000 fffff800`be35d7c9 ffffdd85`00000020 : nvlddmkm+0x20f870
fffff800`0e73a838 00000000`00000000 : 00000000`00000000 fffff800`be35d7c9 ffffdd85`00000020 fffff800`0e73a870 : 0xffffdd85`b67db000


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+1ec825
fffff800`be33c825 c3 ret

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: nvlddmkm+1ec825

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5ba0fd29

FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+1ec825

BUCKET_ID: X64_0x133_nvlddmkm+1ec825

Followup: MachineOwner
---------"

I tried reinstalling graphics drivers countless times, and trying older drivers but nothing has worked.

I also have been constantly seeing errors in the event viewer that say:
"Event 10016, DistributedCOM"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user JON-PC\Jon SID (S-1-5-21-3745566328-979363614-2101655147-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

And also this very similar one I got 8 times in a row all within a few seconds:
"Event 10016, DistributedCOM"
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user JON-PC\Jon SID (S-1-5-21-3745566328-979363614-2101655147-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe SID (S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194-4256926629-1688279915-2739229046-3928706915). This security permission can be modified using the Component Services administrative tool."

Some more errors:
"Event 10016, DistributedCOM"
"The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider
and APPID
Unavailable
to the user JON-PC\Jon SID (S-1-5-21-3745566328-979363614-2101655147-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

"Event 10005, DistrubutedCOM"
"DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}"


"Event 10005, DistrubutedCOM"
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{E48EDA45-43C6-48E0-9323-A7B2067D9CD5}

I searched that online and went through this process of going into the DCOM Cfg and changing the permissions on the CLSID and the APPID, I didn't really know what I was doing and I don't know if it helped but I did that, restarted, and the problem went away for a little while. Then I was just doing more normal activities , I even played some GPU intensive games, and then while in Google Chrome, it froze and crashed again.

I'm sure that reinstalling Windows would be a solution, unless my GPU is dying, but I REALLY don't want to go through with that again. I've reinstalled Windows about 3 times on this machine now, once because I upgraded from Windows 7 to 10 and it broke a bunch of things, and another time it was because of Windows update. I also updated my BIOS for my motherboard to see if it would fix this but it didn't. This PC is my MAIN workstation, it was over $7000 and I need it to be up and running error-free again ASAP.

:)

 

Windows 10 - Blue Screen / WatchDog Violation

Hi,

Incompatible drivers can cause the Watchdog Violation blue screen error. We'd like to learn more about your concern so that we can provide the proper resolution. We just have a few questions for you:

• Which build version of Windows 10 is on your computer? To check, click
  Start, type winver, and press Enter. For example, 14393.1066.
• Are you using a third-party antivirus program?
• Did you make any changes to your computer before this started happening?
• What troubleshooting steps have you done so far?

As an initial recommendation, we suggest carefully following the steps suggested

here for troubleshooting blue screen errors. That article was specifically created for resolving stop (also called blue screen) errors that happen in Windows 10.

We'll wait for your response and the results of the initial troubleshooting.

 

Help! Watchdog Violation

More info on that BSOD

How to Fix DPC_Watchdog_Violation Blue Screen error

 

Help! Watchdog Violation

Thanks, good info for the future (hopefully not)! I had never heard of this.