Windows 10 DCP Watchdog violation BSODs even after factory reset; ntoskrnl.exe identified as cause

  • Thread starter Thread starter JaynGG
  • Start date Start date
J

JaynGG

My HP desktop has been going through BSODs with an DCP Watchdog Violation code for the past year. I've performed a factory reset of the computer and have installed all the latest updates in hopes that it would resolve the issue, but again, BSoDs still pop up at least once a day. BlueScreenView identified ntoskrnl.exe as the cause, but I've performed the Memtest86 and there were 0 errors. WinDbg identified Netwtw04.sys as the cause, but my LAN driver is up to date. Here's the latest minidump after completing all the necessary windows updates. Minidumps

Continue reading...
 

Similar threads

Back
Top