dpc_watchdog_violation fix?

Hey guys, I have an issue with my PC and it is destroying me and making me want to smash it to bits. My PC randomly freezes and then I get this blue screen error which says: dpc_watchdog_violation. How the hell do you fix it? I looked in my Event Viewer, and it says:

Event ID: 41
Source: Kernel-Power
Log: System

I then get this description in it: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

How do I fix this? I can barely use my PC for 10 mins without it crashing! Please help.

System Specs: Signature, but I will give key details anyway.

My power supply is fine, I know it is not the problem.

Motherboard: Asrock Extreme9/ac
CPU: Intel i7 4770k 3.5GHZ no o/c
RAM: G.Skill Sniper - 16GB (8x2)
GPU: EVGA 780 TI
OS: Windows 8.1 Full Professional.
Thank you in advance, pf12351.

 

Hi there !

first overall i got 2 question.

1. Do you use a SSD? which one?
2. Did you upgrade from Win 7 to 8.1 ?

i had the same problem with some Costumer PC´s, problem simply was the firmware from the SSD needed the newest Update. The Watchdog_violation is a failure code which basicly means something went wrong between the Software and Hardware you using.

Solution:

If you use a SSD try to get the newest FW Update.

If the problem is there without using a SSD then please try to boot your system in "Safe mode" and reinstall all drivers for every single Hardware you using. And try to follow the following steps:

a) (Intel) Chipset Drivers
b) Intel rapid storage technology
c) Intel Management Engine Components
d) VGA Drivers
e) Audio
f) Wireless drivers
g) LAN Drivers
h) Bluetooth Drivers
i) Card Reader Drivers
j) Touchpad Drivers
k) the rest of your drivers and utilities for your laptop/computer

if you dont use Wlan or something skip to next.
Why that you may ask, well the following will clear that out.

If that doesent do it, jump into you BIOS and have a look if your startin you BOOT drive in AHCI (Advanced Host Control Interface) mode. (maybe check that first)
AHCI is very important to make Win 7 + 8 + 8.1 work, you can install the OS as IDE (integrated development invironment) but you will never be able to use it. If it gets installed as the settings on IDE that will get you bluescreens and shut downs after several minutes, mostly 10 minutes.

If that all doesent work for you, im sorry to say that but you probably need de reinstall the whole Windows, because getting a windows back to work after installed as IDE needs some rewriting in your regestry. So if theres any chance not to loose important data while reinstalling Windows new you maybe do that (but please change to AHCI first ) Maybe do a 100GB partition for windows and basic drivers with that theres less to nearly no data loosing.

i hope its somewhere understandable even in the fact that im german and my technical english is veeery basic ^^

hope to get feedback

- Marco

 

Hey Marco, I use 2 Samsung 840 EVO's, 120 GB & 500 GB.

I only used 8.1 on my PC.

 

Firstly, IDE in respect to hard drives is not integrated development environment (which instead is a software tool intended to aid writing of software). It stands for Integrated Drive Electronics and is a legacy feature left over from PATA devices.
His boot drive should already be in AHCI mode unless his "proffesional" computer business isnt so professional after all. If the system was installed in IDE mode (absolutely no reason to, its slower and supports less features) then switching to AHCI mode will actually cause it to fail to boot. The other way also occurs. Modern UEFI BIOS's should default to AHCI.
Technically there is also a 3rd alternative. RAID.




As for the actual error. It is not limited to SSD firmware (although that is a common cause) and in this application as the OS was previously running fine on the same SSDs I would say it is not caused by the SSD at all, even if it was, playing around with AHCI vs IDE in the way you suggest would not fix it (you would want to go from AHCI to IDE, but windows doesnt like that switching about so couldnt do that anyway).

dpc_watchdog_violation occurs when a deferred procedure call seems to be running for too long, usually because it is jammed in an interrupt request it cannot process. *ANY* driver can be the cause of this.