Windows 10: Multiple BSODs after 15-20 Minutes, DPC Watchdog Violation

After i upgraded to 1903 from 1803, my PC crashed almost 10 times showing me the DPC Watchdog Violation error.

First couple of crashes were due to AMD drivers (version 18.1.2) as found out from the Minidumps (while playing a video on youtube especially). I downgraded to a lower and more stable version (17.7) as Wattman of 18.1.2 had issues on 1803 too and made the system crash once in a while. I saw no crashes due to AMD drivers after downgrading.
Most of the time it crashed due to the ntoskrnl.exe thing, and this happened for every 20 minutes. I found no driver problems (exclamation marks) in the Device Manager. Here are the logs i took from WhoCrashed:

Code: -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dumps are enabled on your computer. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Mon 03-06-2019 16:43:56 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\060319-35484-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80443B6E350) 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. On Mon 03-06-2019 16:43:56 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x3a3eb) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80443B6E350) Error: DPC_WATCHDOG_VIOLATION file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics Kernel 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 a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Mon 03-06-2019 16:25:15 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\060319-36921-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8017436E350) 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. On Mon 03-06-2019 16:15:21 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\060319-34875-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8012C96E350) 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. On Sun 02-06-2019 21:33:57 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\060219-49859-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8015516E350) 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. On Sun 02-06-2019 21:11:11 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\060219-34406-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8025376E350) 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.[/quote] P.S i had to roll back to 1803, as that was the only option left as i needed my PC to be in a proper state ASAP.
There is no bluescreen troubleshooter in 1903 (discontinued from 1809 *Sad )

What could be the reason ?

:)

 

BSOD- DPC Watchdog violation

BSOD - DPC watchdog violation how to fix?

 

BSOD DPC WATCHDOG VIOLATION

According to what I found from your minidump file, ndis.sys is caused this
DPC WATCHDOG VIOLATION BSOD error on your Windows computer.It's a
NDIS 6.20 Wrapper Driver and installed onto your computer through Windows Update. As far as I know, you have installed new Windows updates lately.

You can uninstall those updates out of your computer, restart your PC and check again the result. Remember to do these steps in Safe Mode.

For more solutions to fix DPC watchdog violation BSOD error in case the above method doesn't work, check it out the following link below:

https://usefulpcguide.com/17082/dpc-watchdog-violation/

 

Help! Watchdog Violation

More info on that BSOD

How to Fix DPC_Watchdog_Violation Blue Screen error