Multiple BSODs after 15-20 Minutes, DPC Watchdog Violation Solved

  1. AuraticTrance's Avatar
    Posts : 14
    Windows 10 Pro 1803 (Build 17134.590) x64
       #1

    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.
    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 )

    What could be the reason ?
      My ComputerSystem Spec


  2. Posts : 209
    Windows 8.1 Enterprise x64
       #2

    Insert minidumps and full memory dump
      My ComputerSystem Spec


  3. Posts : 25,820
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    See: BSOD - Posting Instructions
    BSOD - Posting Instructions
    Upload both V2 and DM.
      My ComputerSystem Spec

  4. AuraticTrance's Avatar
    Posts : 14
    Windows 10 Pro 1803 (Build 17134.590) x64
    Thread Starter
       #4

    I looked in but there aren't any minidumps and full memory dump. Those might have got deleted after the rollback. Rollback RX was blocking while upgrading, there was an option to block irreversible upgrades, i un-checked and continued the upgrade and it successfully got upgraded. After upgrading, rollback rx was unusable and displayed an error message.

    Is it always good to download windows updates during an in-place upgrade to fix issues ?
      My ComputerSystem Spec


  5. Posts : 25,820
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    Which version of Rollback RX are you using and had you compared it to Acronis, Aoemi, EaseUS, Macrium, Paragon, etc. ?

    It's possible that the Windows upgrade may have fixed problems related to BSOD.

    If there are no BSOD for several days you can complete the thread.

    If there are recurrent BSOD then follow the steps in the posting instructions.
      My ComputerSystem Spec

  6. AuraticTrance's Avatar
    Posts : 14
    Windows 10 Pro 1803 (Build 17134.590) x64
    Thread Starter
       #6

    zbook said: View Post
    Which version of Rollback RX are you using .
    Home edition 11.2

    It gave me some kernel related error every time i opened it after upgrading, so i uninstalled it. Don't know how it got messed up (might be a driver issue or something)

    I don't use Aoemi, EaseUS, Acronis, Macrium as i don't find the need to create a backup copy of System Image. Rollback RX is similar to System Restore and works a lot faster and better.
      My ComputerSystem Spec


  7. AuraticTrance's Avatar
    Posts : 14
    Windows 10 Pro 1803 (Build 17134.590) x64
    Thread Starter
       #7

    I installed 1903 on a VHD, well that's a clean installation. I found no problems, it's running fine. The driver crash might be due to some in-compatible software, i suspect the ntoskrnl issue might be due to Rollback RX software as it failed to open and gave a kernel related error message.
      My ComputerSystem Spec


  8. Posts : 25,820
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    If it needs troubleshooting the V2 and DM logs can be scanned and read for actionable problems.
      My ComputerSystem Spec


 

Related Threads
I'm getting BSODs in a consistent manner, usually whenever I'm using PhotoShop or HitFilm Express; and usually either 'DPC Watchdog Violation' or 'Driver Power State Failure'. Typically my mouse will freeze for a few seconds, after which it will...
DPC Watchdog Violation in General Support
I keep getting a DPC Watchdog Violation BSOD despite all of my drivers being up to date and my SSD being brand new. Is there anyone who can do event traces and full kernel dump analysis? Any help at all would be much appreciated. Here is the...
Hello helpful people, I have had massive BSOD problems for a week now, and after spending every single evening trying to solve it by myself I am reaching my humble limits. The story goes like this: For no apparent reason (meaning i hadn't...
Hi, I am facing multiple BSOD on my system. They occur randomly, i cant find a pattern. The latest windows updates are installed. Asus E200ha 2gb ram Atom Z8300 181649
DPC watchdog violation in BSOD Crashes and Debugging
Hi, I´ve been getting this error for a while now, i´ve tried everything from power options to updating drivers. Can anyone help? here is my log.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:46.
Find Us