Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD dpc_watchdog_violation


  • Please log in to reply
1 reply to this topic

#1 matiyarosz

matiyarosz

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:25 PM

Posted 21 May 2014 - 01:27 PM

Hello,

I have an occasional problem with my PC. 4 days ago and today it showed the BSOD, so today I decided to investigate it a bit more. This is what I have from the debugger logs:


Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\052114-27750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff801`5ba70000 PsLoadedModuleList = 0xfffff801`5bd3a2d0
Debug session time: Wed May 21 18:51:18.696 2014 (UTC + 1:00)
System Uptime: 1 days 20:11:26.046
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

*** WARNING: Unable to verify timestamp for PLTGC.sys
*** ERROR: Module load completed but symbols could not be loaded for PLTGC.sys
Probably caused by : PLTGC.sys ( PLTGC+29397 )

Followup: MachineOwner
---------


0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8015bc03ad6 to fffff8015bbc3fa0

STACK_TEXT:  
fffff801`5d490c98 fffff801`5bc03ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`5d490ca0 fffff801`5bb24678 : 00000000`00000000 00000000`00000000 00000000`009b5b83 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
fffff801`5d490d30 fffff801`5ba0867f : ffffe001`10dd8ed0 fffff801`00000000 fffff801`5ba549b0 00000000`00008101 : nt!KeClockInterruptNotify+0x788
fffff801`5d490f40 fffff801`5bb3f363 : fffff801`5ba54900 00000000`00000008 fffff801`5d490f50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x4f
fffff801`5d490f70 fffff801`5bbc542a : fffff801`5ba54900 ffffe001`10dd8ed0 ffffe001`10dd8e00 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
fffff801`5d490fb0 fffff801`5bbc580f : 00000000`00007800 fffff801`830b2e2d fffff801`5d481df0 fffff801`84ec4cde : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`5d481c70 fffff801`5bb3f660 : 00000000`00000030 ffffe001`0b000000 ffffe001`c0000001 ffffe001`0c7ad1f0 : nt!KiInterruptDispatchLBControl+0x11f
fffff801`5d481e00 fffff801`85c96397 : 00000000`00000000 ffffe001`0deac928 00000000`00000000 ffffe001`0b922060 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff801`5d481e30 00000000`00000000 : ffffe001`0deac928 00000000`00000000 ffffe001`0b922060 00000000`00000000 : PLTGC+0x29397


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PLTGC+29397
fffff801`85c96397 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  PLTGC+29397

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PLTGC

IMAGE_NAME:  PLTGC.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50a44da9

FAILURE_BUCKET_ID:  0x133_DPC_PLTGC+29397

BUCKET_ID:  0x133_DPC_PLTGC+29397

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_dpc_pltgc+29397

FAILURE_ID_HASH:  {d0e09505-0289-a43b-6e64-253c0a9a13a9}

Followup: MachineOwner
---------

Thank you for your help!

Mateusz


Edited by matiyarosz, 21 May 2014 - 01:28 PM.


BC AdBot (Login to Remove)

 


#2 matiyarosz

matiyarosz
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:25 PM

Posted 21 May 2014 - 03:01 PM

Solved:

 

http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/dpcwatchdogviolation-solved/e5883134-8067-49cb-9505-2a3bcf6b65ed#tabs






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users