Question
2173 views

DPC Watchdog Violation

KaveendraVithana asked on

This problem started few days ago and now happens every now and then. Didn't install any new hardware recently.

Minidump https://skydrive.live.com/redir?resid=B218D0E8F8D4878C!149&authkey=!APNMkwFBVY_BWS4

 

 

3 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi,

The attached DMP file is of the DPC_WATCHDOG_VIOLATION (133) bugcheck.

The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.

I am going to recommend temporarily for troubleshooting purposes removing AVG with the removal tool and replacing it with Windows 8's built-in Windows Defender:

AVG removal tool - http://www.avg.com/us-en/utilities

If removing and replacing AVG does not stop the crashes, please enable Driver Verifier to see if we can see if a device driver is causing any conflicts:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier  will help flush out the rogue driver by flagging it and causing your system to BSOD.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
 8.    Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do [b]not[/b] panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in C:\Windows\Minidump

Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617

Regards,

Patrick
Debugger/Reverse Engineer.
2 people found this helpful

Abuse history


The answered status icon Answer
KaveendraVithana replied on

After couple of days of usual work on the computer, I haven't seen a single BSOD. Even this is not a conclusive decision, Blackberry Link application (with couple of more blackberry supporting apps running in the background together) seems to be the cause of BSOD in my computer. Removing that application (making sure no blackberry supporting apps and DLLs loaded at boot) made my day without BSOD. 



Be the first person to mark this helpful

Abuse history


progress