DPC_Watchdog Violation When Using USB Hub/Extension Cable
I purchased an Acer Aspire M5-481PT-6644 Ultrabook about 5 months ago, but in the last 2 days I started getting the DPC_Watchdog_Violation when I try to use a USB hub/extension cable. Since the computer only has 2 USB ports, I was trying to use the cable
so that I could have my phone, external hard drive and wireless mouse in use at once. I tried plugging them in several different ways and also tried with other equipment (printer, camera, etc) but each time it caused a reboot.
Here is a link to the last 3 DMP files and MSinfo32 output: https://skydrive.live.com/redir?resid=CD94618F6C154482!175
OS: Windows 8 64-bit
RAM: 6.0 GB (5.82 GB usable)
Processor: Intel (R) Core (TM) i5-3337U CPU @ 1.80GHz
Any help is greatly appreciated. It is a brand new computer and I would love to have this issue resolved. Please let me know if any other info is needed.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
The attached DMP files are all of the DPC_WATCHDOG_VIOLATION (133) bugcheck.
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.
Given this is happening when you try and use a USB extension, it's possible there is a device driver conflict. Looking at your loaded modules list, I'm seeing a driver from
2005 - MRESP50a64.SYS
Sat Nov 19 03:14:28 2005.
If the above does not help, please enable Driver Verifier to look for further possible device driver conflicts:
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 if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
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.
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 not 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 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?