[SOLVED] DPC_WATCHDOG_VIOLATION

A

antalya

Member
Joined
Jan 8, 2013
Posts
5
Dear

I am a new member and wish to thank you for such a great site!
My problem is getting freezes then BSOD with DPC_WATCHDOG_VIOLATION error.
I have just bought a ACER Aspire S3 Ultrabook with W8 installed on it.
This happens randomly, sometimes once a day or five in an hour.

I checked that there is no yellow ! in any of the system devices.
I uninstalled pre-installed McAffee Int. Security but still continues.

It is very annoying and please help me...

Regards

Hakan
 

Attachments

Last edited:
Dear jcgriff2

Thank you for your quick answer.
I did the process and uploaded the file.
Yes, I also used the Mcafee removal tool. I used this link: http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Thank you.
 
I noticed there was a WDF (Windows Driver Framework) component in here, a USB transfer stack, and a thread in the print spooler:
Code: 
// This thread in spoolsv.exe is talking to the USB bus:
0: kd> k
Child-SP          RetAddr           Call Site
fffff880`19636948 fffff801`9225c19b nt!KeBugCheckEx
fffff880`19636950 fffff801`9212e011 nt! ?? ::FNODOBFM::`string'+0x13ca8
fffff880`196369d0 fffff801`9203ee94 nt!KeUpdateRunTime+0x51
fffff880`19636a00 fffff801`920fc7ee hal!HalpTimerClockInterrupt+0x50
fffff880`19636a30 fffff801`9212f166 nt!KiInterruptDispatchLBControl+0x1ce
fffff880`19636bc0 fffff880`04f5cbe0 nt!KeReleaseSpinLock+0x26
fffff880`19636bf0 fffff880`04f5dfed USBXHCI!TransferRing_StageInsertIntoRing_BulkOrInt+0x3c8
fffff880`19636cd0 fffff880`04f5c11f USBXHCI!TransferRing_StageInsertIntoRing+0x1b1
fffff880`19636d30 fffff801`92028184 USBXHCI!TransferRing_EvtProgramControlDma+0x13
fffff880`19636d60 fffff801`920231a3 hal!HalBuildScatterGatherListV2+0x2a8
fffff880`19636df0 fffff880`04f5fd09 hal!HalGetScatterGatherList+0xd3
fffff880`19636e70 fffff880`04f6014b USBXHCI!TransferRing_StageProcess+0x375
fffff880`19636f00 fffff880`04f60853 USBXHCI!TransferRing_TransferProcess+0x24f
fffff880`19636f90 fffff880`04f5928a USBXHCI!TransferRing_DispatchEventsAndReleaseLock+0x407
fffff880`19637010 fffff880`011690f3 USBXHCI!TransferRing_WdfEvtIoQueueReadyNotification+0x62
fffff880`19637040 fffff880`010e92df Wdf01000!FxIoQueue::ProcessReadyNotify+0xa7
fffff880`196370a0 fffff880`010f4fbb Wdf01000!FxIoQueue::DispatchEvents+0x51f
fffff880`19637120 fffff880`01146458 Wdf01000!FxIoQueue::QueueRequest+0x2ab
fffff880`19637190 fffff880`019d4d99 Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x514
fffff880`19637230 fffff880`019d40b3 ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x16d
fffff880`196372e0 fffff880`019c9fcd ucx01000!Urb_USBPORTStyle_ProcessURB+0x407
fffff880`19637350 fffff880`010ed946 ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x505
fffff880`19637410 fffff880`010edaa6 Wdf01000!FxDevice::Dispatch+0x106
fffff880`19637450 fffff880`01001a97 Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`19637490 fffff880`0100ef3e ACPI!ACPIDispatchForwardIrp+0x37
fffff880`196374c0 fffff880`01001196 ACPI!ACPIIrpDispatchDeviceControl+0x82
fffff880`196374f0 fffff880`058baff6 ACPI!ACPIDispatchIrp+0x156
fffff880`19637590 fffff880`010ed946 UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xcb6
fffff880`196376a0 fffff880`010edaa6 Wdf01000!FxDevice::Dispatch+0x106
fffff880`196376e0 fffff880`05f47840 Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`19637720 fffff880`05f472f9 usbccgp!UsbcForwardIrp+0x30
fffff880`19637750 fffff880`05f475d0 usbccgp!DispatchPdoUrb+0x139
fffff880`196377b0 fffff880`05f47b7d usbccgp!DispatchPdoInternalDeviceControl+0x1b0
fffff880`19637810 fffff880`05ff503f usbccgp!USBC_Dispatch+0x22d
fffff880`19637890 fffff801`924c9978 usbprint!USBPRINT_Read+0x123
fffff880`196378c0 fffff801`9246ebe3 nt!IopSynchronousServiceTail+0x158
fffff880`19637990 fffff801`92102353 nt!NtReadFile+0x661
fffff880`19637a90 000007f8`a7492c4a nt!KiSystemServiceCopyEnd+0x13
00000000`01f8cdb8 00000000`00000000 0x000007f8`a7492c4a

// The USBXHCI driver is the one causing the delay:
0: kd> lmvm USBXHCI
start             end                 module name
fffff880`04f3c000 fffff880`04f93000   USBXHCI    (pdb symbols)          d:\websymbols\usbxhci.pdb\D307A738E5644688A4AF60BEA8AED1F61\usbxhci.pdb
    Loaded symbol image file: USBXHCI.SYS
    Mapped memory image file: d:\websymbols\USBXHCI.SYS\505AB2A757000\USBXHCI.SYS
    Image path: \SystemRoot\System32\drivers\USBXHCI.SYS
    Image name: USBXHCI.SYS
    Timestamp:        Thu Sep 20 02:07:35 2012 (505AB2A7)
    CheckSum:         00057B02
    ImageSize:        00057000
    File version:     6.2.9200.16420
    Product version:  6.2.9200.16420
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbxhci.sys
    OriginalFilename: usbxhci.sys
    ProductVersion:   6.2.9200.16420
    FileVersion:      6.2.9200.16420 (win8_gdr.120919-1813)
    FileDescription:  USB XHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Since this driver is simply responsible for talking to the USB bus, it stands to reason that there's at least one print driver loaded here that has a device on the USB bus on this computer, and we're delaying while trying to communicate with this device. Unfortunately once you get to this point it's incredibly difficult to determine if the print driver itself is at fault, if there's some sort of USB bus problem, or if the device is misbehaving. Given I don't see a print driver here, that would seem to rule that out, but it is a minidump and thus is hiding many secrets potentially. The next questions I have are:
a. What printer are you trying to print to when this fails?
b. Is it attached over USB to the computer?
c. Is it attached to a USB2 or USB3 port?
d. Is the USB port setting in the BIOS set to "automatic" or something else for legacy USB support on your USB ports?



Also I noticed you have the basic video device driver loaded and not a video driver from Intel, AMD, or NVidia, so I don't know if you intentionally didn't install those either. It has nothing to do with the problem, but I thought that I would point it out.
 
At work we've noticed several new, straight out of the box systems having problems with USBXHCI.sys (shows in Device Management).
Our fix (so far) is to uninstall the device and reboot the system. So far it's seemed to fix every one - but we're only talking a week or two of observation here.
 
Normally, computer freezes randomly, once-two days a day, in several duties.
But, last time, it freezed 5 times in an hour, while trying to print out.

Below, the answers to questions:
a. What printer are you trying to print to when this fails? HP Deskjet F2280
b. Is it attached over USB to the computer? Yes
c. Is it attached to a USB2 or USB3 port? It is a USB3 port
d. Is the USB port setting in the BIOS set to "automatic" or something else for legacy USB support on your USB ports? Automatic

By the way, I have only 2 USB ports, I use a microsoft wireless mouse/keyboard on one of it and an USB hub is connected to the other, with printer on it, others are empty.
Also, I use a Samsung SCX3400W network printer connected to the network.
 
@usasma: USBXHCI.sys was listed under my Intel wireless display device. I have it on my new Toshiba, and ran into the same problem described that uninstalling and restarting fixed it. Figured that out last night. :-}


@antalya: Do you have the same problems if you use the network printer and remove the USB printer from the system?
 
Last edited:
Yes, but most printers aren't USB3 capable, and in fact can cause issues if used on a USB3 port (just like you shouldn't attach USB2 keyboards and mice to USB3 ports as well). I'd recommend a reinstall of the device after full removal, but if possible, please do not plug it into a USB3 device - the drivers for that bus will have far less tolerance for delay, as it's supposed to be used by *fast* USB3 devices.

If it's not specifically a USB3 device, please don't use a USB3 port unless you absolutely have to.
 
writhziden said:
@usasma: USBXHCI.sys was listed under my Intel wireless display device. I have it on my new Toshiba, and ran into the same problem described that uninstalling and restarting fixed it. Figured that out last night. :-}


@antalya: Do you have the same problems if you use the network printer and remove the USB printer from the system?
Click to expand...
No since yesterday.
 
Back
Top