Update: I have traced the problem to my cell phone being plugged in via USB (front I/O port #1) (which is how I get Internet, via USB hotspot). If I plug it into port #2, there is no problem. But again, it only crashes when games are launched, and I don't exactly trust this problem not to recur. Any ideas??
To preface this, this is a brand new build and for the first day, it worked absolutely fine. I put in a few hours of gaming and had no problems whatsoever. The second day, this problem began to occur. It happens every single time no matter what game I run. There is nothing I can think of that changed between now and yesterday, when the system was running fine.
Within 3 minutes (shortest was 40 seconds, longest nearly 3 minutes) of launching a Company of Heroes 2 match or loading a save file in Witcher 2, I get a BSOD with the watchdog violation error. Info from my dump file is below. But first, what I have tried: Reinstalled latest NVIDIA drivers. No luck. Did a complete system restore to a time yesterday when the system was running fine. No luck. Installed Samsung Magician and confirmed my SSD has the latest firmware. Currently running Windows Update, but I don't see why that would fix it when it ran fine yesterday. Hardware: GTX970, MSI motherboard, i7 processor, 250gb Samsung Evo 850 SSD. Thank you very much.
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8000ea0dad6 to fffff8000e9cdfa0
STACK_TEXT:
ffffd001`f4847c98 fffff800`0ea0dad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`f4847ca0 fffff800`0e92e678 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`f4847d30 fffff800`0e81267f : 00000000`000000ff fffff800`0e964426 ffffe001`ed06c8b0 fffff800`0e87a000 : nt!KeClockInterruptNotify+0x788
ffffd001`f4847f40 fffff800`0e949363 : ffffe001`ed06c800 fffff800`0e98173b ffffed75`8ecad560 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
ffffd001`f4847f70 fffff800`0e9cf42a : ffffe001`ed06c800 ffffe001`ed0162f0 00000000`00000000 ffffe001`ed016398 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`f4847fb0 fffff800`0e9cf80f : 00000000`00000000 00000000`000000ff 00000000`00000000 ffffe001`ed01b3a0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`f8bb67e0 fffff800`551d1cb3 : ffffd001`f8bb6b02 ffffe001`f06234b0 ffffe001`f02e4118 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`f8bb6970 fffff800`0e8d3810 : ffffd001`f8bb6b00 00000000`00025896 ffffd001`f8bb6ab0 ffffd001`00000002 : usb80236!CancelSendsTimerDpc+0x5b
ffffd001`f8bb69b0 fffff800`0e9d1aea : ffffd001`f8a40180 ffffd001`f8a40180 ffffd001`f8a4c3c0 ffffe001`f15d6080 : nt!KiRetireDpcList+0x4f0
ffffd001`f8bb6c60 00000000`00000000 : ffffd001`f8bb7000 ffffd001`f8bb1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usb80236!CancelSendsTimerDpc+5b
fffff800`551d1cb3 7549 jne usb80236!CancelSendsTimerDpc+0xa6 (fffff800`551d1cfe)
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usb80236!CancelSendsTimerDpc+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usb80236
IMAGE_NAME: usb80236.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f828
BUCKET_ID_FUNC_OFFSET: 5b
FAILURE_BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc
BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_usb80236!cancelsendstimerdpc
FAILURE_ID_HASH: {a33649e0-3f49-3074-35df-91e00215eed4}
Followup: MachineOwner
To preface this, this is a brand new build and for the first day, it worked absolutely fine. I put in a few hours of gaming and had no problems whatsoever. The second day, this problem began to occur. It happens every single time no matter what game I run. There is nothing I can think of that changed between now and yesterday, when the system was running fine.
Within 3 minutes (shortest was 40 seconds, longest nearly 3 minutes) of launching a Company of Heroes 2 match or loading a save file in Witcher 2, I get a BSOD with the watchdog violation error. Info from my dump file is below. But first, what I have tried: Reinstalled latest NVIDIA drivers. No luck. Did a complete system restore to a time yesterday when the system was running fine. No luck. Installed Samsung Magician and confirmed my SSD has the latest firmware. Currently running Windows Update, but I don't see why that would fix it when it ran fine yesterday. Hardware: GTX970, MSI motherboard, i7 processor, 250gb Samsung Evo 850 SSD. Thank you very much.
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8000ea0dad6 to fffff8000e9cdfa0
STACK_TEXT:
ffffd001`f4847c98 fffff800`0ea0dad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`f4847ca0 fffff800`0e92e678 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`f4847d30 fffff800`0e81267f : 00000000`000000ff fffff800`0e964426 ffffe001`ed06c8b0 fffff800`0e87a000 : nt!KeClockInterruptNotify+0x788
ffffd001`f4847f40 fffff800`0e949363 : ffffe001`ed06c800 fffff800`0e98173b ffffed75`8ecad560 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
ffffd001`f4847f70 fffff800`0e9cf42a : ffffe001`ed06c800 ffffe001`ed0162f0 00000000`00000000 ffffe001`ed016398 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`f4847fb0 fffff800`0e9cf80f : 00000000`00000000 00000000`000000ff 00000000`00000000 ffffe001`ed01b3a0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`f8bb67e0 fffff800`551d1cb3 : ffffd001`f8bb6b02 ffffe001`f06234b0 ffffe001`f02e4118 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`f8bb6970 fffff800`0e8d3810 : ffffd001`f8bb6b00 00000000`00025896 ffffd001`f8bb6ab0 ffffd001`00000002 : usb80236!CancelSendsTimerDpc+0x5b
ffffd001`f8bb69b0 fffff800`0e9d1aea : ffffd001`f8a40180 ffffd001`f8a40180 ffffd001`f8a4c3c0 ffffe001`f15d6080 : nt!KiRetireDpcList+0x4f0
ffffd001`f8bb6c60 00000000`00000000 : ffffd001`f8bb7000 ffffd001`f8bb1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usb80236!CancelSendsTimerDpc+5b
fffff800`551d1cb3 7549 jne usb80236!CancelSendsTimerDpc+0xa6 (fffff800`551d1cfe)
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usb80236!CancelSendsTimerDpc+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usb80236
IMAGE_NAME: usb80236.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f828
BUCKET_ID_FUNC_OFFSET: 5b
FAILURE_BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc
BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_usb80236!cancelsendstimerdpc
FAILURE_ID_HASH: {a33649e0-3f49-3074-35df-91e00215eed4}
Followup: MachineOwner
Facebook
Twitter
Instagram