DPC_Watchdog_violation error

I got a new laptop. But recently I got a few DPC_watchdog_violations crashes.
My dumplink can be found here: 
https://skydrive.live.com/redir?resid=4995EFD0693075C4%21803
I tried nearly everything. I updated my drivers and restarted some programs, but so far nothing has helped.
Can someone please help me out?

Bankaaai
The verified crash was Related to
Apfiltr.sys Alps Pointing-device Driver.  Yours is 2 years old.  I would install the newest driver available
Remember to turn off verifier by typing verifier /reset
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`4ec86000 PsLoadedModuleList = 0xfffff801`4ef4a990
Debug session time: Sat Jan 11 22:21:15.647 2014 (UTC - 5:00)
System Uptime: 0 days 0:15:25.837
Loading Kernel Symbols
*** WARNING: Unable to verify timestamp for Apfiltr.sys
*** ERROR: Module load completed but symbols could not be loaded for Apfiltr.sys
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000000e, Irql > DPC at IoCompleteRequest
Arg2: 0000000000000007, the current Irql
Arg3: ffffcf8012954c10, the IRP
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0xc9_e
DRIVER_VERIFIER_IO_VIOLATION_TYPE: e
CURRENT_IRQL: 7
IRP_ADDRESS: ffffcf8012954c10
DEVICE_OBJECT: ffffe00004c4a7e0
DRIVER_OBJECT: ffffe00004c2a080
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff8014f2e6a44 to fffff8014edd3ca0
STACK_TEXT:
fffff801`508ecb78 fffff801`4f2e6a44 : 00000000`000000c9 00000000`0000000e 00000000`00000007 ffffcf80`12954c10 : nt!KeBugCheckEx
fffff801`508ecb80 fffff800`02cf8a37 : 00000000`00000018 fffff801`508eccc0 ffffcf80`12954c10 ffffe000`04c4a930 : nt!IovCompleteRequest+0xac
fffff801`508ecc50 fffff800`02cc519f : ffffcf80`12954f68 ffffe000`04c33310 00000000`00000001 ffffe000`04c31511 : mouclass!MouseClassServiceCallback+0x3d3
fffff801`508eccf0 ffffcf80`12954f68 : ffffe000`04c33310 00000000`00000001 ffffe000`04c31511 ffffe000`04c33310 : Apfiltr+0x4319f
fffff801`508eccf8 ffffe000`04c33310 : 00000000`00000001 ffffe000`04c31511 ffffe000`04c33310 ffffe000`04c31550 : 0xffffcf80`12954f68
fffff801`508ecd00 00000000`00000001 : ffffe000`04c31511 ffffe000`04c33310 ffffe000`04c31550 fffff801`508e5200 : 0xffffe000`04c33310
fffff801`508ecd08 ffffe000`04c31511 : ffffe000`04c33310 ffffe000`04c31550 fffff801`508e5200 00000000`00000001 : 0x1
fffff801`508ecd10 ffffe000`04c33310 : ffffe000`04c31550 fffff801`508e5200 00000000`00000001 fffff801`508ecf88 : 0xffffe000`04c31511
fffff801`508ecd18 ffffe000`04c31550 : fffff801`508e5200 00000000`00000001 fffff801`508ecf88 fffff801`508ecee0 : 0xffffe000`04c33310
fffff801`508ecd20 fffff801`508e5200 : 00000000`00000001 fffff801`508ecf88 fffff801`508ecee0 00001fff`fb3ccfd8 : 0xffffe000`04c31550
fffff801`508ecd28 00000000`00000001 : fffff801`508ecf88 fffff801`508ecee0 00001fff`fb3ccfd8 00000000`00000000 : 0xfffff801`508e5200
fffff801`508ecd30 fffff801`508ecf88 : fffff801`508ecee0 00001fff`fb3ccfd8 00000000`00000000 ffffe000`04c31550 : 0x1
fffff801`508ecd38 fffff801`508ecee0 : 00001fff`fb3ccfd8 00000000`00000000 ffffe000`04c31550 00001fff`fb3ccfd8 : 0xfffff801`508ecf88
fffff801`508ecd40 00001fff`fb3ccfd8 : 00000000`00000000 ffffe000`04c31550 00001fff`fb3ccfd8 fffff801`508ecee0 : 0xfffff801`508ecee0
fffff801`508ecd48 00000000`00000000 : ffffe000`04c31550 00001fff`fb3ccfd8 fffff801`508ecee0 fffff800`02c868a7 : 0x00001fff`fb3ccfd8
STACK_COMMAND: kb
FOLLOWUP_IP:
mouclass!MouseClassServiceCallback+3d3
fffff800`02cf8a37 488d4f20 lea rcx,[rdi+20h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: mouclass!MouseClassServiceCallback+3d3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: mouclass
IMAGE_NAME: mouclass.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f861
IMAGE_VERSION: 6.3.9600.16384
BUCKET_ID_FUNC_OFFSET: 3d3
FAILURE_BUCKET_ID: 0xc9_e_VRF_mouclass!MouseClassServiceCallback
BUCKET_ID: 0xc9_e_VRF_mouclass!MouseClassServiceCallback
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc9_e_vrf_mouclass!mouseclassservicecallback
FAILURE_ID_HASH: {a6e88987-0038-3c8a-5374-1124db171c27}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Similar Messages

  • DPC_WATCHDOG_VIOLATION error on windows 8.1 X64

    hello their ! i have beeen using windows 8.1 pro X64 for the last 3-4 months and it worked fine .but from few days ago a blue screen error freezing my pc every time . thoug it shows DPC_WATCHDOG_VIOLATION sometimes but when i try to use chrome
    it occurs more frequently . i have uploaded the dump files here . plz help me out!

    Hi,
    We don't find your dump file in your post, Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive 
    Here is the error information for your reference:
    Bug Check 0x133 DPC_WATCHDOG_VIOLATION
    http://msdn.microsoft.com/en-us/library/windows/hardware/jj154556(v=vs.85).aspx
    Kate Li
    TechNet Community Support

  • DPC_WATCHDOG_VIOLATION error when adding device

    Brand new DELL computer, first thing I did was to update from Windows 8 to 8.1 and one of my devices won't show up, tried to scan for new device and getting that blue screen... Tried updating the disk drive firmware (Seagate st500dm002-1bd142)
    but no update driver on Seagate website or anywhere else. Attached the DMP file... Help?
    https://www.dropbox.com/s/7dmwue71pyuyd56/012114-12328-01.dmp

    UK
    This crash was related to Athw8x.sys with description Qualcomm Atheros Extensible Wireless LAN device driver from company Qualcomm Atheros Communications, I would reinstall the newest driver available
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\012114-12328-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff802`12414000 PsLoadedModuleList = 0xfffff802`126d8990
    Debug session time: Tue Jan 21 10:39:10.214 2014 (UTC - 5:00)
    System Uptime: 0 days 0:01:19.954
    Loading Kernel 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 athw8x.sys
    *** ERROR: Module load completed but symbols could not be loaded for athw8x.sys
    Probably caused by : athw8x.sys ( athw8x+c231b )
    Followup: MachineOwner
    1: 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.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff80212585f7c to fffff80212561ca0
    STACK_TEXT:
    ffffd000`20638c58 fffff802`12585f7c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffd000`20638c60 fffff802`1246881b : fffff802`12be8eb0 ffffd000`20600180 fffff800`028f1e80 0000003d`8b4540c8 : nt! ?? ::FNODOBFM::`string'+0x13ddc
    ffffd000`20638cf0 fffff802`1246848c : 00000000`00000001 ffffd000`20638d70 ffffd000`20638e30 fffff802`126ae920 : nt!KiUpdateRunTime+0x57
    ffffd000`20638d30 fffff802`125e731c : fffff802`126e03f0 00008000`00000000 ffffd000`20600180 00000000`00000002 : nt!KiUpdateTime+0x63c
    ffffd000`20638f10 fffff802`12b9be5f : 00000000`00000000 ffffe000`03962040 00000000`00000000 ffffd000`20600180 : nt!KeClockInterruptNotify+0x5c
    ffffd000`20638f40 fffff802`124aa343 : fffff802`12be8e00 ffffd000`2062a500 ffffd000`2099cb48 fffff802`12562d4a : hal!HalpTimerClockInterrupt+0x4f
    ffffd000`20638f70 fffff802`1256312a : fffff802`12be8e00 ffffe000`03b9edf0 fffff800`028f1ee4 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd000`20638fb0 fffff802`1256350f : ffffd000`2062a60e 00000000`000000d0 ffffd000`2062a5e0 00000000`00000042 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`2062a490 fffff800`0278231b : 00000000`00000000 00000000`00000000 fffff800`028f1e80 fffff800`028f1ee4 : nt!KiInterruptDispatchLBControl+0x11f
    ffffd000`2062a620 00000000`00000000 : 00000000`00000000 fffff800`028f1e80 fffff800`028f1ee4 00000000`00000000 : athw8x+0xc231b
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    athw8x+c231b
    fffff800`0278231b ?? ???
    SYMBOL_STACK_INDEX: 9
    SYMBOL_NAME: athw8x+c231b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: athw8x
    IMAGE_NAME: athw8x.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 50f7c13b
    FAILURE_BUCKET_ID: 0x133_DPC_athw8x+c231b
    BUCKET_ID: 0x133_DPC_athw8x+c231b
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x133_dpc_athw8x+c231b
    FAILURE_ID_HASH: {9320244e-5b0c-ef29-1f75-27c5a7ee7185}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • XPower Z87 Suddenly Unable to Boot

    Very strange behavior....
    Right now motherboard only has power to 6 lights: CMOS, OC Switch LEDs (one red, one blue), discharge and power buttons (among the overclocking buttons). Initially, they were blinking, but now they are constant.
    Won't boot, or demonstrate any other power.
    Likely issue right now is the PSU. It doesn't seem like it is testing properly with it integrated testing switch, from what I remember of its behavior after installing it when I first built system. Looking into that further after this is posted.
    Thought that the motherboard LEDs and other lights might have indicated useful information.
    Extensive searching on Google and MSI forums have given me very little feedback.
    On MSI I've noticed a couple other users in particular that seemed to experience very similar behavior, but were given very little attention because of their poor posts.
    Incidents leading up to issue:
    Rig was running pretty decent for over 8 months.
    (Only in the last month or two???), I occasionally I received a random BSOD.
    Narrowed it down to four likely suspects:
       1. SLI
       2. NVIDIA conflict with Firefox and "Use hardware acceleration when available" setting
       3. NVIDIA version issue
       4. OCZ PCIe SSD (RevoDrive 3 x2).
    Over the last few weeks started to devote more time to windows Event Viewer.
    Had two MSI GeForce GTX 7700N graphic cards in SLI.
    Disabled SLI. Still received random BSOD.
    Installed Who Crashed Windows (free version), reconfig'd my temp files and pagefile settings to accommodate dumpfiles.
    Received a successful log the other night, and found it was a 0x133 DPC_Watchdog_Violation error relating to ntoskrnl.exe
    Adjusted Firefox settings.
    Was going to stop there, but HAD to check in on the drivers, in light of ntoskrnl.exe.
    Went to MSI product page for MSI GeForce GTX 770N Lighting, found the special note "The Drivers provided here are exclusively for MSI products only", and the latest posted version being 331.65.
    Cruised over to NVIDIA and found they were posting is 335.23.
    Grabbed them both, renamed and archived them for easy reference and testing.
    Began with MSI's download. The special note was clear enough and offered the best choice.
    Wouldn't install. Received an error message: Graphics could not find compatible graphics hardware.
    Attempted install with NVIDIA's latest version.
    Wouldn't install. Received an error message: Graphics could not find compatible graphics hardware.
    Thought it might have been a problem with different PCIe slots, considering I also had this OCZ PCIe SSD card to consider.
    Reduced it one graphic card, and the OCZ.
    Suddenly the OCZ card wasn't booting anymore, and wasn't even being recognized in the BIOS (if it ever was because of it's special drivers).
    Now I needed to test the OCZ SSD.
    Removed the second graphic card.
    Changed settings in BIOS to internal graphic card.
    Grabbed a (new) Kingston SSD.
    Installed fresh Windows8.1.
    Made a drive image backup with Symantec System Restore 2013.
    Was intending to install OCZ Toolbox and drivers to recognize OCZ SSD, and see what I can see.
    Never got that far...
    Rebooted the system.
    And that is where it all ended.
    System:
    Motherboard: MSI XPower Z87
    CPU: Intel i7-4770K
    Cooler: CoolerMaster Eisberg 240L Prestige
    PSU: Corsair AX1200i
    RAM: Corsair Dominator Platinum 16GB DDR3 2400MHz CL10 Dual Channel Kit (2 x 8GB)
    Graphics: Internal
    SSD: Kingston 240GB SSD
    UPS: Cyberpower CP850PFCLCD 850VA
    OS: Windows8.1 (no updates)
    I didn't take proper care and attention to log my NVIDIA driver version, and have no way to go back and check. I was mindful of the knowledge that I had only one archived version that I had ever installed. The name of the archive is "nvidia_32063_win78_v64.
    All settings are stock. Hadn't yet gotten around to overclocking.
    As far as I can remember, system was pretty stable until adding the second graphic card. Not saying the graphic card was the issue, could have been something else.
    I have been pretty particular with maintaining a Firefox 21.0 version. Any time I upgrade past that version, extensions start breaking and I become exponentially dissatisfied with successive upgrades.
    UPDATE:
    Removed all cables from PSU, and it tests fine.
    Before posting attempted plugged and unplugged CMOS clear, jumper clear, BIOS switch, power discharge, reset, and removed battery temporarily - all without change.
    Have removed the battery and unplugged for period of time, and attempting restart shortly.
    hmmm... The 24 pin connector to this power supply splits into two cables that plug into the PSU, a smaller connector and a larger connector. All the previous motherboard lights mentioned previously appear when I plug in the second smaller 24 pin ATX connector.
    Seems like the issue is persisting.
    Beginning to believe the only real solution is an in-store product replacement.

    Thanks, guys!
    For clarity, final shutdown of system was normal. Nothing indicated anything out of the ordinary at time of power down.
    Last test done was only with necessary connections, with same results.
    After posting here I did notice this:
    http://www.tomshardware.com/answers/id-1809712/msi-z87-mpower-max-start.html
    After more than 8 months of use, the circumstance of failure was entirely unusual and completely unacceptable. So, too, was the behavior. It was powered by a premium power supply from a respected company with the added benefit of filtered power, and had been doing nothing unusual with the board to stress or disrupt it at the time of failure.
    Judging from the number of posts demonstrated by multiple users on the same issue there appears to be a recurring flaw somewhere.
    Best solution in my circumstance was to take the board back for an in-store product replacement. I bought a 4 year protection plan to cover events exactly like this. Their tech has an incentive to justify the return. Also left them the power supply to give it a look over, just in case. It also has a 4 year protection plan, if anything unusual turns up.
    I hope to have a better idea of what's going on in about a week, and will update.

  • "DPC_watchdog_violation" happens almost everyday, tried re-installing, is this a hardware problem?

    Hello, I'm from Hong Kong. You guys must be wondering why I'd post in a foreign forum instead of local one - I cant find any support from my local forum. I cant even find this model form my local Website.
    First of all, I brought this laptop (Envy 14) in 2013 from my so called "University Notebook Scheme". But once I got my first Envy, problem arised - my screen keeps flashing. I went back to the store and replaced it with a new one. Yet, this "new one" keeps having "DPC_watchdog_violation" almost everyday, no matter what Im doing - browsing the Net, using iTunes, even when Im using Microsoft Office for my assignments. 
    I've tried many solutions suggested: updating software & drivers, and reinstalling the windows; nothing works. Instead, more problem arised throughout these 2 years: my screen starts to flash, sometimes I cant even turn my computer on (power button on with a black, turned on, screen). I cant update my windows - "Failure configuring Windows updates, Reverting changes" and got stuck in the update loop.
    I'm scared to do anything with this laptop now, even typing this "problem discription". I stored every files into the Dropbox for safety purposes. I save my Word documents every minutes, try to run as less programme as I could.
    I've been wondering if this is a hardware problem, a serious one. Some of my classmates also got this Laptop from the University Scheme as well, most of them reported with the same issue (especially for the screen/display issue). With the notorious HP's repair and warranty service,  I'm discouraged to sent my Laptop to them. I've even heard that I'll be charged even I'm still under warranty.
    P.S. sorry if I have made any grammatical mistakes.

    Additional Information for my Laptop (from WhoCrased):
    System Information (local)
    windows version: Windows 8 , 6.2, build: 9200
    windows dir: C:\Windows
    Hardware: HP ENVY 14 Sleekbook, Hewlett-Packard, 198C
    CPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 8351010816 total
    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump
    Crash dumps are enabled on your computer.
    On Fri 27/02/15 7:02:39 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022715-19390-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Fri 27/02/15 7:02:39 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: iastora.sys (iaStorA+0x770DB)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\drivers\iastora.sys
    product: Intel Rapid Storage Technology driver
    company: Intel Corporation
    description: Intel Rapid Storage Technology driver - x64
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
    Google query: Intel Corporation DPC_WATCHDOG_VIOLATION
    On Fri 27/02/15 3:22:12 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022715-15015-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Thu 26/02/15 7:39:23 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022615-33093-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Mon 16/02/15 9:27:12 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021615-23328-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sat 14/02/15 9:37:59 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021415-28265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Wed 28/01/15 3:01:05 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012815-19171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Tue 27/01/15 2:44:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012715-33937-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Fri 23/01/15 3:33:59 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012315-63484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Tue 20/01/15 5:31:56 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012015-18734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: MicrosoftR WindowsR Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

  • Windows 8.1 Pro DPC_WATCHDOG_VIOLATION BSOD

    I built a PC a few months ago, and recently decided to move to Windows 8. I had a Windows 8 upgrade key, so I had to go through Windows 8 before I could move to 8.1. Before I could upgrade to 8.1, I needed my Ethernet driver updated, because W8 does not
    have the proper Intel I217-V driver. I downloaded the latest driver off of the internet, and when I went to install it, every time just before the installation finished, I got a BSOD (DPC_WATCHDOG_VIOLATION). I had to install the drivers off the CD. I upgraded
    to Windows 8.1, and updated the drivers without a problem. But now, every once in a while, I get the same BSOD in the Windows 8.1 login screen. I have uploaded the dump file to SkyDrive.
    http://sdrv.ms/Ml26aW

    D4
    This one was related to a known problem with LogMeIn Hamachi Virtual Miniport Driver. Driver Update Site: https://secure.logmein.com/products/ios/
    Their 1/23/2014 driver (which is your date) is buggy.  I suggest you contact them for a patch, beta, or work around or wailing that revert to an older driver until they figure it out
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\013014-6031-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\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
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff802`a1674000 PsLoadedModuleList = 0xfffff802`a1938990
    Debug session time: Thu Jan 30 09:32:29.245 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:21.933
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 44, {ffffe00003338db0, f8a, 0, 0}
    *** WARNING: Unable to verify timestamp for Hamdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for Hamdrv.sys
    Probably caused by : Hamdrv.sys ( Hamdrv+1f0a )
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    MULTIPLE_IRP_COMPLETE_REQUESTS (44)
    A driver has requested that an IRP be completed (IoCompleteRequest()), but
    the packet has already been completed. This is a tough bug to find because
    the easiest case, a driver actually attempted to complete its own packet
    twice, is generally not what happened. Rather, two separate drivers each
    believe that they own the packet, and each attempts to complete it. The
    first actually works, and the second fails. Tracking down which drivers
    in the system actually did this is difficult, generally because the trails
    of the first driver have been covered by the second. However, the driver
    stack for the current request can be found by examining the DeviceObject
    fields in each of the stack locations.
    Arguments:
    Arg1: ffffe00003338db0, Address of the IRP
    Arg2: 0000000000000f8a
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    IRP_ADDRESS: ffffe00003338db0
    FOLLOWUP_IP:
    Hamdrv+1f0a
    fffff800`01985f0a ?? ???
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x44
    PROCESS_NAME: svchost.exe
    CURRENT_IRQL: 2
    DEVICE_OBJECT: ffffe00001fcb9e0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff802a17fcb4b to fffff802a17c1ca0
    STACK_TEXT:
    ffffd000`22bc9818 fffff802`a17fcb4b : 00000000`00000044 ffffe000`03338db0 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`22bc9820 fffff800`01985f0a : 00000000`00000000 ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
    ffffd000`22bc9930 00000000`00000000 : ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 ffffd000`00000020 : Hamdrv+0x1f0a
    STACK_COMMAND: kb
    SYMBOL_STACK_INDEX: 2
    SYMBOL_NAME: Hamdrv+1f0a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: Hamdrv
    IMAGE_NAME: Hamdrv.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 52e10c23
    FAILURE_BUCKET_ID: 0x44_Hamdrv+1f0a
    BUCKET_ID: 0x44_Hamdrv+1f0a
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x44_hamdrv+1f0a
    FAILURE_ID_HASH: {af270f7d-2329-db64-39cf-85dffdd63412}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • DPC_WatchDog_Violation on Yoga 13

    I updated my Yoga 13 to Windows 8.1 a couple of weeks ago. 
    Yesterday, suddendly, I started getting a BSOD, stating DPC_WatchDog_Violation. 
    The windows would load, and a few seconds later, the keyboard and touchpad would stop responding, and then I get the BSOD stating the error. 
    The computer restarts to the Novo Button Menu, but the keyboard doesn't respond, and I can't select any option, until shutting down and pressing the Novo button. 
    Non of the recovery options seem to work, and I keep getting the violation.
    Why is this happening? What can I do? Do I need to send my Yoga for service?
    Solved!
    Go to Solution.

    I have the same problem!
    However I managed to make a recovery installation - shut the computer down and keep the power button pressed for about 30 seconds. When the computer boots, turn it off again. Than press the novo button and do a recovery installation (the keyboard is now working again).
    Next I will try this:
    http://social.technet.microsoft.com/Forums/windows/en-US/a74beaec-87af-4660-8c7f-19e8b9b23382/dpc-wa...
    Otherwise it would be great to get some support from lenovo!!!

  • Windows 8 Dpc Watchdog Violation error

    please i would like to know how to fix this watchdog violation error i am getting since monday.
    here is the link to dump files
    http://www.mediafire.com/download.php?ney1rln6fgumnsn

    * 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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: avgnsa.exe
    CURRENT_IRQL: d
    TAG_NOT_DEFINED_c000000f: FFFFF800EF4A0FB0
    LAST_CONTROL_TRANSFER: from fffff800ef7dd6ef to fffff800ef684040
    STACK_TEXT:
    fffff800`ef4a0618 fffff800`ef7dd6ef : 00000000`00000133 00000000`00000000 00000000`00000283 00000000`00000282 : nt!KeBugCheckEx
    fffff800`ef4a0620 fffff800`ef6aff06 : 00000000`00000005 00000000`0003fb67 fffff800`ef4a07a0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c80
    fffff800`ef4a06a0 fffff800`efd74eca : fffffa80`04d16870 00000000`000000dd 00000000`8068aecd 00000000`00000001 : nt!KeUpdateTime+0x41b
    fffff800`ef4a0890 fffff800`ef67dbfa : 00000009`7a925d51 00000000`89ed155a fffff800`efd9e580 fffff880`00000000 : hal!HalpTimerClockInterrupt+0x86
    fffff800`ef4a08c0 fffff800`ef673903 : 00000000`00000001 fffff800`ef88d000 00000000`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x1aa
    fffff800`ef4a0a50 fffff800`ef6b0315 : 00000000`00000002 fffff800`ef88d000 fffff880`01541180 fffff800`ef6ad033 : nt!KxWaitForSpinLockAndAcquire+0x23
    fffff800`ef4a0a80 fffff880`01b68ff2 : fffff800`ef4a0b49 fffff800`ef8ff180 00000009`7494f883 fffff800`ef88d000 : nt!KeAcquireSpinLockRaiseToDpc+0x35
    fffff800`ef4a0ab0 fffff880`019b3626 : 00000000`00000000 fffffa80`03fe33f0 fffffa80`03fe3280 fffffa80`03fe33f0 : tcpip!TcpEnqueueTcbSend+0x72
    fffff800`ef4a0b80 fffff880`019b307b : fffffa80`042651a0 fffffa80`04d16870 00000000`00000000 000009a8`73d17274 : NETIO!StreamInjectRequestsToStack+0x23e
    fffff800`ef4a0c60 fffff880`019b2f21 : fffffa80`042651a0 00000000`00000000 00000000`00000008 ffff87fc`ec58fef4 : NETIO!StreamPermitDataHelper+0x5f
    fffff800`ef4a0c90 fffff800`ef679f38 : fffff800`ef901f00 fffff800`ef4a0e00 fffffa80`090463a0 00000000`00000000 : NETIO!StreamPermitRemoveDataDpc+0x81
    fffff800`ef4a0d00 fffff800`ef6aaeb0 : fffff800`ef8ff180 00000009`532a8f50 fffffa80`073b4680 00000000`00000025 : nt!KiExecuteAllDpcs+0x198
    fffff800`ef4a0e40 fffff800`ef6aa8a5 : 00000000`00000000 fffff800`ef8ff180 fffff880`0c8bc270 fffffa80`090463a0 : nt!KiRetireDpcList+0xd0
    fffff800`ef4a0fb0 fffff800`ef6aa6a9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0c8bc1c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    NETIO!StreamInjectRequestsToStack+23e
    fffff880`019b3626 8bf0 mov esi,eax
    IMAGE_NAME: NETIO.SYS
    fffff880`0197b000 fffff880`019ea000 NETIO (pdb symbols) c:\sym\dl\netio.pdb\F6A6ADDF9B3C4AECAFFCADC1489938262\netio.pdb
    Loaded symbol image file: NETIO.SYS
    Mapped memory image file: c:\sym\dl\NETIO.SYS\507656246f000\NETIO.SYS
    Image path: \SystemRoot\system32\drivers\NETIO.SYS
    Image name: NETIO.SYS
    Timestamp: Thu Oct 11 07:16:20 2012 (50765624)
    CheckSum: 000798F6
    ImageSize: 0006F000
    File version: 6.2.9200.16433
    Product version: 6.2.9200.16433
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.6 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: netio.sys
    OriginalFilename: netio.sys
    ProductVersion: 6.2.9200.16433
    FileVersion: 6.2.9200.16433 (win8_gdr.121010-1704)
    FileDescription: Network I/O Subsystem
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    Update all your network driver and tools like AVG.
    "A programmer is just a tool which converts caffeine into code"

  • Dpc_watchdog_violation windows 8

    I bought DELL i5 laptop some 15 days back which uses windows 8 64 bit, I repeatedly gets DPC_WATCHDOG_VIOLATION windows 8 blue screen error repeatedly please some one fix my problem.

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    Wanikiya and Dyami--Team Zigzag

  • DPC_WATCHDOG_VIOLATION - I'm very tired of this thing

    Hello.
    I'm tired of seeing this error everytime I start working with a certain application. I don't want to remove the application, so is there a way around this? I just want to stop the error from ever happening
    again.
    Recent DXDIAG folder info:
    System Information
    Time of this report: 3/8/2014, 15:35:55
           Machine name: STELLAR
       Operating System: Windows 8 Single Language 64-bit (6.2, Build 9200) (9200.win8_gdr.130531-1504)
               Language: English (Regional Setting: English)
    System Manufacturer: Acer
           System Model: Aspire E1-422
                   BIOS: V2.05
              Processor: AMD E1-2500 APU with Radeon(TM) HD Graphics     (2 CPUs), ~1.4GHz
                 Memory: 4096MB RAM
    Available OS Memory: 3526MB RAM
              Page File: 2283MB used, 4825MB available
            Windows Dir: C:\Windows
        DirectX Version: DirectX 11
    DX Setup Parameters: Not found
       User DPI Setting: Using System DPI
     System DPI Setting: 96 DPI (100 percent)
        DWM DPI Scaling: Disabled
         DxDiag Version: 6.02.9200.16384 64bit Unicode
    DxDiag Notes
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
            Sound Tab 2: No problems found.
              Input Tab: No problems found.
    DirectX Debug Levels
    Direct3D:    0/4 (retail)
    DirectDraw:  0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay:  0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow:  0/6 (retail)
    Display Devices
              Card name: AMD Radeon HD 8240
           Manufacturer: Advanced Micro Devices, Inc.
              Chip type: AMD Radeon HD 8240 (0x9838)
               DAC type: Internal DAC(400MHz)
            Device Type: Full Device
             Device Key: Enum\PCI\VEN_1002&DEV_9838&SUBSYS_07671025&REV_00
         Display Memory: 2006 MB
       Dedicated Memory: 500 MB
          Shared Memory: 1506 MB
           Current Mode: 1366 x 768 (32 bit) (60Hz)
           Monitor Name: Generic PnP Monitor
          Monitor Model: unknown
             Monitor Id: LGD03FA
            Native Mode: 1366 x 768(p) (59.989Hz)
            Output Type: Internal
            Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Driver File Version: 8.17.0010.1191 (English)
         Driver Version: 12.102.1.1300
            DDI Version: 11.1
         Feature Levels: 11.1,11.0,10.1,10.0,9.3,9.2,9.1
           Driver Model: WDDM 1.2
    Graphics Preemption: DMA
     Compute Preemption: DMA
      Driver Attributes: Final Retail
       Driver Date/Size: 6/13/2013 23:22:24, 1151656 bytes
            WHQL Logo'd: n/a
        WHQL Date Stamp: n/a
      Device Identifier: {D7B71EE2-DB78-11CF-3277-6D27BEC2C535}
              Vendor ID: 0x1002
              Device ID: 0x9838
              SubSys ID: 0x07671025
            Revision ID: 0x0000
     Driver Strong Name: oem3.inf:cb0ae41400453105:ati2mtag_Kabini_Mobile:12.102.1.1300:pci\ven_1002&dev_9838&subsys_07671025
         Rank Of Driver: 00E00001
            Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C 
            DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeMPEG2_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeVC1_VLD  DXVA2_ModeVC1_IDCT  DXVA2_ModeWMV9_IDCT  
       Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                         {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                         {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                         {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                         {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                         {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                         {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                         {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
           D3D9 Overlay: Not Supported
                DXVA-HD: Not Supported
           DDraw Status: Enabled
             D3D Status: Enabled
             AGP Status: Enabled
    If anyone want more DXDIAG info ask the user for it.

    GK
    The most recent 3 crashes were Related to
    Apfiltr.sys Alps Pointing-device Driver.  Yours is 3 years old.  I would install the newest driver available and if you continue to crash I would run driver verifier to find the underlying issue
    Please run this test to find which driver is causing the problem.  
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
    know what it is you probably are not overclocking.
    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff801`93203000 PsLoadedModuleList = 0xfffff801`934c7990
    Debug session time: Thu Mar 20 15:05:26.078 2014 (UTC - 4:00)
    System Uptime: 0 days 5:45:47.125
    BugCheck 133, {1, 1e00, 0, 0}
    *** WARNING: Unable to verify timestamp for Apfiltr.sys
    *** ERROR: Module load completed but symbols could not be loaded for Apfiltr.sys
    Probably caused by : mouclass.sys ( mouclass!MouseClassServiceCallback+3d3 )
    Followup: MachineOwner
    1: 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: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x133
    PROCESS_NAME: COSService.exe
    CURRENT_IRQL: d
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff80193374fd2 to fffff80193350ca0
    STACK_TEXT:
    ffffd000`2071b6a8 fffff801`93374fd2 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`2071b6b0 fffff801`9325781b : ffffe000`006a9000 ffffd000`206e1180 ffffe000`000007b8 ffffd000`206e1180 : nt! ?? ::FNODOBFM::`string'+0x13e32
    ffffd000`2071b740 fffff801`933d63a3 : fffff801`939d7d00 ffffd000`206e1180 fffff801`93500e40 fffff801`934f1180 : nt!KiUpdateRunTime+0x57
    ffffd000`2071b780 fffff801`9398af85 : 00000000`00400a02 fffff801`9325d900 fffff800`01a7ef90 00000000`0000b201 : nt!KeClockInterruptNotify+0xe3
    ffffd000`2071b7b0 fffff801`93299343 : ffffd000`2071b7d0 00000000`00000008 ffffd000`2071b7c0 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15
    ffffd000`2071b7e0 fffff801`9335212a : fffff801`939d7d00 fffff801`934f1180 00000000`c1409c3a fffff801`934a2100 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd000`2071b820 fffff801`93352a9b : 00000000`00000000 00000000`00000000 ffffe000`0295fb20 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`2071b870 fffff801`932adf82 : ffffe000`00000001 00000000`0024be14 00000000`00000000 00000000`00000100 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    ffffd000`2071ba00 fffff801`932aae7f : ffffd000`2071bbe9 ffffd000`206e1180 ffffe000`03548250 00000000`00000000 : nt!KiDeferredReadyThread+0x1222
    ffffd000`2071bb40 fffff800`01e76a37 : 00000000`00000018 ffffd000`2071bc06 00000000`00000018 ffffe000`0357b070 : nt!IopfCompleteRequest+0x3af
    ffffd000`2071bc50 fffff800`01e4319f : ffffe000`01058f28 ffffe000`023282f0 00000000`00000001 ffffe000`022f4511 : mouclass!MouseClassServiceCallback+0x3d3
    ffffd000`2071bcf0 ffffe000`01058f28 : ffffe000`023282f0 00000000`00000001 ffffe000`022f4511 ffffe000`023282f0 : Apfiltr+0x4319f
    ffffd000`2071bcf8 ffffe000`023282f0 : 00000000`00000001 ffffe000`022f4511 ffffe000`023282f0 ffffe000`022f4550 : 0xffffe000`01058f28
    ffffd000`2071bd00 00000000`00000001 : ffffe000`022f4511 ffffe000`023282f0 ffffe000`022f4550 ffffd000`20710000 : 0xffffe000`023282f0
    ffffd000`2071bd08 ffffe000`022f4511 : ffffe000`023282f0 ffffe000`022f4550 ffffd000`20710000 00000000`00000001 : 0x1
    ffffd000`2071bd10 ffffe000`023282f0 : ffffe000`022f4550 ffffd000`20710000 00000000`00000001 ffffd000`2071bf88 : 0xffffe000`022f4511
    ffffd000`2071bd18 ffffe000`022f4550 : ffffd000`20710000 00000000`00000001 ffffd000`2071bf88 ffffd000`2071bee0 : 0xffffe000`023282f0
    ffffd000`2071bd20 ffffd000`20710000 : 00000000`00000001 ffffd000`2071bf88 ffffd000`2071bee0 00001fff`fdcd7ff8 : 0xffffe000`022f4550
    ffffd000`2071bd28 00000000`00000001 : ffffd000`2071bf88 ffffd000`2071bee0 00001fff`fdcd7ff8 00000000`00000000 : 0xffffd000`20710000
    ffffd000`2071bd30 ffffd000`2071bf88 : ffffd000`2071bee0 00001fff`fdcd7ff8 00000000`00000000 ffffe000`022f4550 : 0x1
    ffffd000`2071bd38 ffffd000`2071bee0 : 00001fff`fdcd7ff8 00000000`00000000 ffffe000`022f4550 00001fff`fdcd7ff8 : 0xffffd000`2071bf88
    ffffd000`2071bd40 00001fff`fdcd7ff8 : 00000000`00000000 ffffe000`022f4550 00001fff`fdcd7ff8 ffffd000`2071bee0 : 0xffffd000`2071bee0
    ffffd000`2071bd48 00000000`00000000 : ffffe000`022f4550 00001fff`fdcd7ff8 ffffd000`2071bee0 fffff800`01e048a7 : 0x00001fff`fdcd7ff8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    mouclass!MouseClassServiceCallback+3d3
    fffff800`01e76a37 488d4f20 lea rcx,[rdi+20h]
    SYMBOL_STACK_INDEX: a
    SYMBOL_NAME: mouclass!MouseClassServiceCallback+3d3
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: mouclass
    IMAGE_NAME: mouclass.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5215f861
    IMAGE_VERSION: 6.3.9600.16384
    BUCKET_ID_FUNC_OFFSET: 3d3
    FAILURE_BUCKET_ID: 0x133_ISR_mouclass!MouseClassServiceCallback
    BUCKET_ID: 0x133_ISR_mouclass!MouseClassServiceCallback
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x133_isr_mouclass!mouseclassservicecallback
    FAILURE_ID_HASH: {267ac66e-1c0c-dc16-17db-d23062ddc339}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • DPC_WATCHDOG_VIOLATION (133)

    hi,
    I ran the CHAOS test on our driver and get DPC_WATCHDOG_VIOLATION (133).
    in the stack I see tat last try is to enqueue a request to the IoDefaultQueue (from EvtIoIncallerContext):
          nt!VfIrpDatabaseCheckExFreePool+0x7d
                                            nt!VerifierExFreePoolWithTag+0x1e
                                            Wdf01000!FxTagTracker::UpdateTagHistory+0x1ae
                                            Wdf01000!FxObject::Release+0x41e3e
                                            Wdf01000!FxPkgIo::EnqueueRequest+0x26a
                                            Wdf01000!imp_WdfDeviceEnqueueRequest+0xc9
                                            myDriver!WdfDeviceEnqueueRequest+0x3d
                                            myDriver!EvtIoInCallerContext+0x551
    is there any internal spinlock used by the framework to insert requests to queue? if so, how can I know which spinlocks are used and who catch them? Is there an option that another callback use the internal spinlock and for that, the enqueue is stuck?
    we have in our default queue only one callback: EvtIoDefault and our queue dispach its requests as WdfIoQueueDispatchParellel, so I assume that the EvtIoDefault don't cause the enqueue to be stucked.
    Any guidance how to progress with this BSOD will be very appreciated.
    thanks,
    Shosho
    EvtIoDefault

    The frame Wdf01000!FxTagTracker::UpdateTagHistory in the call stack you pasted, suggests that you have "TrackHandles" verification enabled for the driver. Tracking reference counts on WDF objects may add significant over head,
    especially if enabled for all or multiple WDF object types and while running stress (CHAOS test). I'd suggest you try running the test with handle tracking disabled.
    The use of TrackHandles is documented here:
    https://msdn.microsoft.com/en-us/library/windows/hardware/ff544573(v=vs.85).aspx
    This blog post also has useful information relevant to this bug check code:
    http://blogs.msdn.com/b/ntdebugging/archive/2012/12/07/determining-the-source-of-bug-check-0x133-dpc-watchdog-violation-errors-on-windows-server-2012.aspx

  • DPC_WATCHDOG_VIOLATION Help!

    I'm having bsod lately while playing games and weird thing is it's only happens to some games only by far it only happens to The Wolf Among Us and The Walking Dead Season 2 which are telltale games and whenever I play them they freeze and the BSOD DPC_WATCHDOG_VIOLATION
    but what's bugging me is it's never happened to me while I'm playing TWD before but now after installing and playing The Wolf Among Us, both games starts freezing and THE BSOD dpc watchdog error appears.
    My laptop is not SSD cause it's 1tb and it doesn't happen to other games and it ONLY happens to Telltale games :(
    Please Help! (O_O)

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
    drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
    log'.
    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
    4. Double check that the WERS is ENABLED:
    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
    Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • DPC WATCHDOG VIOLATION error.. Help please!

    I have a fairly new computer, like 1 month old and it's been having no trouble at all!
    But recently, there's this error that's been bugging me... "DPC_WATCHDOG_VIOLATION"
    Anyways, I've tried looking for solutions and none of them worked at all!
    Those people with similar problems posted their minidumps folder so here is mine https://skydrive.live.com/redir?resid=8890455B2D279646%21360
    This error randomly happens (mainly when I watch a video or play games) and it's really annoying!
    Thanks in advanced.

    MR A
    These were all Related to
    rtl8192su.sys RTL8192S USB NDIS Driver from Realtek Semiconductor Corporation.  YOurs is 4 years old.  I would install the newest driver available.
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck D1, {0, 2, 0, fffff80000a5b688}
    Probably caused by : RTL8192su.sys ( RTL8192su+11d79 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 0 days 3:05:42.735
    System Uptime: 0 days 1:08:18.344
    System Uptime: 0 days 5:00:43.657
    System Uptime: 0 days 5:33:28.469
    System Uptime: 0 days 7:48:15.074
    **************************Fri Jan 17 21:20:40.097 2014 (UTC - 5:00)**************************
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\SysnativeBSODApps\011714-21875-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: c:\symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff801`69214000 PsLoadedModuleList = 0xfffff801`694d8990
    Debug session time: Fri Jan 17 21:20:40.097 2014 (UTC - 5:00)
    System Uptime: 0 days 3:05:42.735
    Loading Kernel 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 RTL8192su.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
    Probably caused by : RTL8192su.sys ( RTL8192su+3ab26 )
    Followup: MachineOwner
    0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q'
    * 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: LolClient.exe
    CURRENT_IRQL: d
    LAST_CONTROL_TRANSFER: from fffff80169385f7c to fffff80169361ca0
    STACK_TEXT:
    fffff801`6ac86c58 fffff801`69385f7c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    fffff801`6ac86c60 fffff801`6926881b : fffff801`699e89b0 fffff801`69502180 ffffe000`04620038 00002385`29df0c24 : nt! ?? ::FNODOBFM::`string'+0x13ddc
    fffff801`6ac86cf0 fffff801`6926848c : 00000000`00000001 fffff801`6ac86d70 fffff801`6ac86e30 fffff801`694ae920 : nt!KiUpdateRunTime+0x57
    fffff801`6ac86d30 fffff801`693e731c : fffff801`694e03d8 fffff801`6926e813 fffff801`69502180 00000000`00000002 : nt!KiUpdateTime+0x63c
    fffff801`6ac86f10 fffff801`6999be5f : ffffd000`00400a02 ffffd000`20f105b0 fffff800`0272e090 ffffd000`00006101 : nt!KeClockInterruptNotify+0x5c
    fffff801`6ac86f40 fffff801`692aa343 : fffff801`699e8900 00000000`00000008 fffff801`6ac86f50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x4f
    fffff801`6ac86f70 fffff801`6936312a : fffff801`699e8900 ffffe000`03e60060 ffffe000`0462003c ffffe000`03f3aa01 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff801`6ac86fb0 fffff801`6936350f : ffffe000`03c20010 fffff801`6ac7ebd0 00000000`00000000 ffffe000`03c21500 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff801`6ac7e9e0 fffff801`692a8e03 : ffffe000`04a47031 ffffe000`03ef7a5e ffffe000`03ef7740 ffff8eaa`316a9fd9 : nt!KiInterruptDispatchLBControl+0x11f
    fffff801`6ac7eb70 fffff801`692a8dc2 : 00000000`00000002 ffffe000`0462003c ffffe000`03e60000 00000000`00000001 : nt!KxWaitForSpinLockAndAcquire+0x23
    fffff801`6ac7eba0 fffff800`02b4eb26 : ffffe000`04a47001 ffffe000`03ef7750 00000000`00000001 ffffe000`03c660d9 : nt!KeAcquireSpinLockRaiseToDpc+0x32
    fffff801`6ac7ebd0 ffffe000`04a47001 : ffffe000`03ef7750 00000000`00000001 ffffe000`03c660d9 ffffe000`03c60025 : RTL8192su+0x3ab26
    fffff801`6ac7ebd8 ffffe000`03ef7750 : 00000000`00000001 ffffe000`03c660d9 ffffe000`03c60025 fffff800`02b4cc9f : 0xffffe000`04a47001
    fffff801`6ac7ebe0 00000000`00000001 : ffffe000`03c660d9 ffffe000`03c60025 fffff800`02b4cc9f ffffe000`03e60000 : 0xffffe000`03ef7750
    fffff801`6ac7ebe8 ffffe000`03c660d9 : ffffe000`03c60025 fffff800`02b4cc9f ffffe000`03e60000 fffff800`02b4eeda : 0x1
    fffff801`6ac7ebf0 ffffe000`03c60025 : fffff800`02b4cc9f ffffe000`03e60000 fffff800`02b4eeda ffffe000`03ef7750 : 0xffffe000`03c660d9
    fffff801`6ac7ebf8 fffff800`02b4cc9f : ffffe000`03e60000 fffff800`02b4eeda ffffe000`03ef7750 ffffe000`03ef7740 : 0xffffe000`03c60025
    fffff801`6ac7ec00 ffffe000`03e60000 : fffff800`02b4eeda ffffe000`03ef7750 ffffe000`03ef7740 ffffe000`03ef7720 : RTL8192su+0x38c9f
    fffff801`6ac7ec08 fffff800`02b4eeda : ffffe000`03ef7750 ffffe000`03ef7740 ffffe000`03ef7720 ffffe000`0462003c : 0xffffe000`03e60000
    fffff801`6ac7ec10 ffffe000`03ef7750 : ffffe000`03ef7740 ffffe000`03ef7720 ffffe000`0462003c ffffe000`03e60000 : RTL8192su+0x3aeda
    fffff801`6ac7ec18 ffffe000`03ef7740 : ffffe000`03ef7720 ffffe000`0462003c ffffe000`03e60000 fffff800`02b58d26 : 0xffffe000`03ef7750
    fffff801`6ac7ec20 ffffe000`03ef7720 : ffffe000`0462003c ffffe000`03e60000 fffff800`02b58d26 00000000`00000000 : 0xffffe000`03ef7740
    fffff801`6ac7ec28 ffffe000`0462003c : ffffe000`03e60000 fffff800`02b58d26 00000000`00000000 00000000`0000000a : 0xffffe000`03ef7720
    fffff801`6ac7ec30 ffffe000`03e60000 : fffff800`02b58d26 00000000`00000000 00000000`0000000a 00000000`000000a0 : 0xffffe000`0462003c
    fffff801`6ac7ec38 fffff800`02b58d26 : 00000000`00000000 00000000`0000000a 00000000`000000a0 00000000`000000a0 : 0xffffe000`03e60000
    fffff801`6ac7ec40 00000000`00000000 : 00000000`0000000a 00000000`000000a0 00000000`000000a0 00000000`00000000 : RTL8192su+0x44d26
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    RTL8192su+3ab26
    fffff800`02b4eb26 ?? ???
    SYMBOL_STACK_INDEX: b
    SYMBOL_NAME: RTL8192su+3ab26
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: RTL8192su
    IMAGE_NAME: RTL8192su.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4cedfd9f
    FAILURE_BUCKET_ID: 0x133_DPC_RTL8192su+3ab26
    BUCKET_ID: 0x133_DPC_RTL8192su+3ab26
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Error in starting Adobe Bridge in Photoshop CS2

    I've just installed Photoshop CS2, however upon opening Adobe Bridge this error message appears " The application has failed to start because libagluc28.dll was not found. Reinstalling to application may fix the problem"
    I have reinstalled and click repair but to no avail
    I followed Adobe Support Knowledgebase solution and run CMD and this appears:
    c:Documents and Settings/Jesus M Ferraris>
    then i entered the command
    cacls c:\windows\installer /T /E /C /G administrators:F
    but an error message appears - 'cacls' is not recognized as an internal or external command, operable program or bathc file
    I also entered the next command
    cacls "c:\documents and setting\all users" /Y /E /C /G administrators:F
    still the same error as above appears, Please help, have I miss something or was my procedure correct...
    P4, 512ram, WXP 80gHD

    Very useful.
    Good Luck.
    My
    Si
    tes

  • Windows Vista: Ipod Error Message, no longer read by PCs

    Hello,
    I have a 5th generation black ipod video with 30GB of memory.
    The other day I hooked it up to my laptop (Toshiba, 4 months old) that it's been functioning on with no problems whatsoever. This weird error message flashed twice about it not being able to sync because of some software problem.
    Eversince then, the only thing I can charge my ipod on is the family treadmill in the basement (~_~) as no other computer in the house recognizes it. I can't even charge it through the wall sockets, either.
    I have changed the ipod cord, still no luck. I've also reset the device about 3 or 4 times and uninstalled, restarted the laptop then reinstalled itunes. I would like to reset it back to factory settings but that's impossible as computers/laptops don't pick it up. I live very far from a Mac store...
    What's a girl to do? I can't live without my Busta Rhymes and Wu-Tang Clan!
    Any advice would be greatly appreciated! Thanks!

    you have to update Vista go to this site and up-date http://windowsupdate.microsoft.com

Maybe you are looking for