Windows 10: Getting random BSOD (DPC_WATCHDOG_VIOLATION)

Discus and support Getting random BSOD (DPC_WATCHDOG_VIOLATION) in Windows 10 BSOD Crashes and Debugging to solve the problem; Greetings, I'm creating this post because I'm at a loss here. I've recently upgraded to a Gainward GTX 1070 from my previous card and it was... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by xStarrk, Jan 8, 2017.

  1. xStarrk Win User

    Getting random BSOD (DPC_WATCHDOG_VIOLATION)


    Greetings,

    I'm creating this post because I'm at a loss here.
    I've recently upgraded to a Gainward GTX 1070 from my previous card and it was running fine until it gave me a bluescreen.
    I tried looking it up already tried out a few things like doing a syscheck etc. but it didn't seem to solve the problem.
    The weird thing about this is that I thought it was because of my Graphics Card but the bluescreens seem to happen randomly at the weirdest moments. For example I didn't have a bluescreen for over a week(where i extensively could game whatever I wanted without anything happening). I also did benchmarks to see if it would occur if my graphics card is put under pressure but nothing happened.

    I did a clean windows installation to minimize the chance of it being a driver fault and I updated all my drivers and only used the ones from the manufacturers pages.

    When checking the minidump it suggests that "ntoskrnl.exe" might be faulty for this issue.
    The bugcheck code is: 0x133 (0x0, 0x501, 0x500, 0x0)

    I'll attach the log collector and hope you guys can help me!

    Thank you in advance.

    :)
     
    xStarrk, Jan 8, 2017
    #1
  2. C-aLica Win User

    random Freezing leads to BSOD. I give up.

    Stop code is random.

    like CRITICAL_PROCESS_DIED, BAD_SYSTEM_CONFIG_INFO, DPC_WATCHDOG_VIOLATION..

    I've got multiple BSOD and the stop code is that random.

    right now after multiple debugging the issue, I hypothetically assume it's my nvme fault.

    I've ordered a new nvme drive and gonna retest the system if this will works.
     
    C-aLica, Jan 8, 2017
    #2
  3. notthere Win User
    Random BSOD DPC_WATCHDOG_VIOLATION

    It's been 24hrs computer up and running since reverting back to NVIDIA driver version 388.13 (I've actually downgraded to 378.92 but I think Windows Update updated it to 388.13 immediately so I gave this version a shot), It looks like my problem is solved.
    Thanks for help.
     
    notthere, Jan 8, 2017
    #3
  4. Ztruker Win User

    Getting random BSOD (DPC_WATCHDOG_VIOLATION)

    First question, what happens if you remove the GTX 1070 and use the onboard Intel HD Graphics? Does the problem go away?

    The dump shows:
    Code: BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+e04c3 )[/quote] You have the latest driver for the card. You can try removing it and run with the onboard graphics adapter, see if that resolves the problem. If yes, try older drivers for the GTX 1070. If no help, you could RMA the card and see if a different one works correctly.
     
    Ztruker, Jan 8, 2017
    #4
  5. xStarrk Win User
    First of all thanks for the quick response.

    I haven't tried switching to the onboard graphics card yet because of the bluescreen happening so inconsistently.
    If it would happen every day on a regular basis I would've considered that.
    The problem is I need my Graphics card on a daily basis and now switching to the onboard card and not being able to know when or if it will occur is making it hard on me because as I said this bluescreen happened the last time multiple days ago.

    Also what exactly does the part of the dump that you copied mean?
     
    xStarrk, Jan 8, 2017
    #5
  6. Ztruker Win User
    It means windbg did not like or find something it expected. Not necessarily bad but most of the time it indicates something is not right.

    Those type entries are pulled from the active thread and it's sort of like a road map of what has been going on recently. On the same PC, it will show in one dump and not in another.
     
    Ztruker, Jan 8, 2017
    #6
  7. xStarrk Win User
    Much apologies but I have just seen that my SATA Drivers and my Chipset drivers seemed to be out of date despite me thinking they were up to date.(Could this be also related to the issue?)
     
    xStarrk, Jan 8, 2017
    #7
  8. Ztruker Win User

    Getting random BSOD (DPC_WATCHDOG_VIOLATION)

    And outdated driver could cause problems and not always directly associated with the device the driver applies to, so definitely update them.
     
    Ztruker, Jan 8, 2017
    #8
  9. xStarrk Win User
    Alright I have updated them and this time really checked that my drivers are all up to date.
    I will watch out and see if the Blue Screen occurs again.
     
    xStarrk, Jan 8, 2017
    #9
  10. xStarrk Win User
    Update! Sorry it took so long. I RMA'd my card and got a new GTX 1070 and it didn't even take 2 days and the graphics card is dead. My PC crashed and after that it refused to give me a picture. I tried installing the card into my brothers PC same result but his Graphics card(GTX 970 which was installed in MY pc before upgrading to the GTX 1070 works) and my old GTX 750TI works aswell. I am literally at a loss here.
     
    xStarrk, Jan 15, 2017
    #10
  11. Ztruker Win User
    Power? Maybe the PSU is not putting out the right voltage, enough voltage, or its fluctuating or there is a problem with the PCI-E port
     
    Ztruker, Jan 17, 2017
    #11
  12. xStarrk Win User
    How could I check that? I have a beQuiet 630W PSU and my Motherboard is a Gigabyte z97x soc. My PCI-E port seems to work fine with other graphics cards tho I had 0 issues up until upgrading to the GTX 1070.
     
    xStarrk, Jan 17, 2017
    #12
  13. Ztruker Win User

    Getting random BSOD (DPC_WATCHDOG_VIOLATION)

    Adding the GTX 1070 is what made me ask about the power supply. Maybe that card requires more power than the one it replaced? Now a 2nd one is dead, so something is definitely wrong. Are you running with the onboard video for now?

    Without a sophisticated++- PSU tester it's difficult to test them unless it's just not putting out a voltage, which is not your case at all. If anything, I would expect one of the voltages that feeds the GTX 1070 is low or fluctuating. The only way to test for sure is replace it.
     
    Ztruker, Apr 5, 2018
    #13
Thema:

Getting random BSOD (DPC_WATCHDOG_VIOLATION)

Loading...
  1. Getting random BSOD (DPC_WATCHDOG_VIOLATION) - Similar Threads - Getting random BSOD

  2. Random DPC_WATCHDOG_VIOLATION BSODs

    in Windows 10 Gaming
    Random DPC_WATCHDOG_VIOLATION BSODs: I bought this laptop last year, and lately it's been plagued by issues, most notably random BSODs, as mentioned in the title. I tried reinstalling Windows 11 not completely, I chose to keep my files while reinstalling, but after a while the issues started popping up again....
  3. Random DPC_WATCHDOG_VIOLATION BSODs

    in Windows 10 Software and Apps
    Random DPC_WATCHDOG_VIOLATION BSODs: I bought this laptop last year, and lately it's been plagued by issues, most notably random BSODs, as mentioned in the title. I tried reinstalling Windows 11 not completely, I chose to keep my files while reinstalling, but after a while the issues started popping up again....
  4. Random DPC_WATCHDOG_VIOLATION bsod

    in Windows 10 Software and Apps
    Random DPC_WATCHDOG_VIOLATION bsod: 2 dmp files attached. I analyzed it myself. But both of them shows ntkrnlmp.exe is the failing module. Can anyone help? https://answers.microsoft.com/en-us/windows/forum/all/random-dpcwatchdogviolation-bsod/18876d49-4d17-4da8-85fd-8e22aa9433ca
  5. Random DPC_WATCHDOG_VIOLATION bsod

    in Windows 10 BSOD Crashes and Debugging
    Random DPC_WATCHDOG_VIOLATION bsod: 2 dmp files attached. I analyzed it myself. But both of them shows ntkrnlmp.exe is the failing module. Can anyone help? https://answers.microsoft.com/en-us/windows/forum/all/random-dpcwatchdogviolation-bsod/18876d49-4d17-4da8-85fd-8e22aa9433ca
  6. Random DPC_WATCHDOG_VIOLATION bsod

    in Windows 10 Gaming
    Random DPC_WATCHDOG_VIOLATION bsod: 2 dmp files attached. I analyzed it myself. But both of them shows ntkrnlmp.exe is the failing module. Can anyone help? https://answers.microsoft.com/en-us/windows/forum/all/random-dpcwatchdogviolation-bsod/18876d49-4d17-4da8-85fd-8e22aa9433ca
  7. random DPC_watchdog_violation BSOD freeze

    in Windows 10 BSOD Crashes and Debugging
    random DPC_watchdog_violation BSOD freeze: Hello everyone. Really hoping there is some help out there for this random freezing issue I am having. It is not associated with any particular software or function. I have tried numerous things: removing and resetting the RAM and drives; removing my video card driver using...
  8. Random DPC_WATCHDOG_VIOLATION BSOD

    in Windows 10 BSOD Crashes and Debugging
    Random DPC_WATCHDOG_VIOLATION BSOD: Bought my computer from CyberPower PC in early December 2020 and the computer ran great with zero issues until mid January. Been getting a DPC_WATCHDOG_VIOLATION BSOD for 3 months now and all my troubleshooting hasn't solved it. It's been the same Bug Check Code when I use...
  9. Random BSOD - DPC_WATCHDOG_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD - DPC_WATCHDOG_VIOLATION: Usually every couple of weeks this machine will BSOD with a DPC_WATCHDOG_VIOLATION on an unknown module. If I run heavy disk I/O the crash will happen a little more often but even then it could go days just fine. Most of the time it crashes when I am away and the...
  10. Random DPC_WATCHDOG_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    Random DPC_WATCHDOG_VIOLATION: Hello, I would really appreciate some help with my issues here. This BSOD appears seemingly at random, it can go days without it occuring and it can happen a few times a day. I'm not really sure what seems to trigger it unfortunately. I hope you guys can shed some light on...