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

Similar Messages

  • 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 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" 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. 

  • Yoga 13 - Windows 8 update always fails

    Hi I have a Yoga 13 with Windows 8 64 bit.
    I just recently recieved the machine back from repair where they replaced the keyboard and reinstalled the OS after a problem occured with windows update.
    The orginial problem:
    After completing windows update nov 8 i recieved an error DPC_Watchdog_Violation. The system restarted and loaded the Novo Button Recovery and they keyboard does not work. 
    The technition said they attempted to flash the Bios but was unable to due to Intel Anti-Theft 4.0 blocking update. A program which i did not install on the machine. The tech did not mention if the program was removed, but comparing the bios it appears that they did not update as it registers as 66CN54WW, the latest being 66CN55WW.
    Same Problem:
    After recieving the machine, completed windows install and updated the system the same error DPC_Watchdog_Violation occured. Then the system booted into Novo Button Recovery and the keyboard does not work. 
    Please help, i am afraid if i send the system back in they will not resolve the problem.

    The tip I used to solve this problem was found here: 
    http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/i-cannot-install-windows-u...
    Basically, uncheck all non-MS / Intel services, reboot your machine, and then try windows update.  Re-enable the services after the update is successful.
    good luck!

  • Windows 8 bugcheck (133) on T430 & W530 with Intel Centrino Advanced-N 6205 AGN

    I have bought both T430 (Windows 8) & W530 (Windows 8 Pro) this ThanksGiving. I have seen both machines crashed when I waked them up from S3. I analyzed the crash dumps, all point to Intel wireless link driver NETwew00.sys.
    Repro steps:
    1. Leave the machine idle, let it go sleep (I did not customize the system power settings so far)
    2. Wake the system up
    3. Black screen for a while, then system restarted
    4. Check c:\windows\memory.dmp
    I live in an appartment building, lots of WIFI access points.
    Here is the crash dump analysis:
    (From T430 machine)
    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: 0000000000000281, The DPC time count (in ticks). Arg3: 0000000000000280, 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
    LAST_CONTROL_TRANSFER:  from fffff801dda4b853 to fffff801dd8f1740
    STACK_TEXT:  fffff801`dcd05e08 fffff801`dda4b853 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx fffff801`dcd05e10 fffff801`dd91ce51 : 00000000`00000000 fffff801`ddb6d180 fffff801`dcd05fc0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c fffff801`dcd05e90 fffff801`dd91dcd8 : ffffffff`ffd0ec08 fffff801`dd857502 fffff801`dcd05fc0 fffffa80`039fb010 : nt!KeUpdateRunTime+0x51 fffff801`dcd05ec0 fffff801`dd82deca : ffffffff`ffd0ec08 fffff801`dd857502 fffffa80`0732f098 00000000`00000000 : nt!KeUpdateTime+0x3f9 fffff801`dcd060b0 fffff801`dd8eab2e : 00000009`dcae355d 00000000`6ca2e81e fffff801`dd857580 fffffa80`0732f098 : hal!HalpTimerClockInterrupt+0x86 fffff801`dcd060e0 fffff801`dd8e1643 : fffffa80`07332700 fffff880`05aff06b fffffa80`0af52cd8 fffff801`dcd06309 : nt!KiInterruptDispatchLBControl+0x1ce fffff801`dcd06270 fffff801`dd91e025 : 00000000`00000002 fffff880`05d1aa24 fffff801`dcd06370 fffffa80`0af57990 : nt!KxWaitForSpinLockAndAcquire+0x23 fffff801`dcd062a0 fffff880`05d10d44 : fffffa80`0c166230 00000000`c0000001 fffff801`dcd06440 fffff880`05a9f3a3 : nt!KeAcquireSpinLockRaiseToDpc+0x35 fffff801`dcd062d0 fffff880`05ce3dd6 : fffffa80`0af7a1e0 fffff880`05ce3db0 fffffa80`075fca90 fffffa80`0af6cab0 : NETwew00+0x28cd44 fffff801`dcd06330 fffff880`05ab3304 : fffffa80`00000009 00000000`00000000 00000000`000000e2 fffff880`00000009 : NETwew00+0x25fdd6 fffff801`dcd06370 fffff880`05aab28f : 00000000`00000010 fffffa80`0af28e28 fffffa80`0af6cab0 fffffa80`075fcd70 : NETwew00+0x2f304 fffff801`dcd063c0 fffff880`05ad0d3f : 00000000`c0000001 fffff880`05b08c00 fffffa80`0b55a850 fffffa80`0af52c80 : NETwew00+0x2728f fffff801`dcd06410 fffff880`05aecc69 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : NETwew00+0x4cd3f fffff801`dcd06460 fffff880`05b08c30 : 00000000`00000000 fffffa80`0af7f168 fffffa80`0af694a0 fffffa80`07a0d000 : NETwew00+0x68c69 fffff801`dcd06490 fffff880`05ab3304 : 00000000`00000000 fffff880`05b08040 fffffa80`0b55a850 00000000`00000001 : NETwew00+0x84c30 fffff801`dcd064d0 fffff880`05aab28f : 00000000`00000040 fffffa80`0af69408 fffffa80`0af694a0 fffffa80`075db2b0 : NETwew00+0x2f304 fffff801`dcd06520 fffff880`05aecde9 : 00000000`ff000401 fffff801`dcd06638 00000000`00000004 fffffa80`075db2b0 : NETwew00+0x2728f fffff801`dcd06570 fffff880`05afb3f2 : fffffa80`000000c7 fffffa80`07332700 00000000`00000000 00000000`00000000 : NETwew00+0x68de9 fffff801`dcd065f0 fffff880`05d17981 : fffffa80`075e2c00 00000000`00000000 00000000`00000000 fffff880`05d17870 : NETwew00+0x773f2 fffff801`dcd06630 fffff880`05bced9f : fffffa80`0732f320 00000000`00000000 fffffa80`0732f000 00000000`00000000 : NETwew00+0x293981 fffff801`dcd06680 fffff880`05cded45 : fffffa80`075e2c00 fffffa80`0732f000 fffffa80`0af6efb0 00000000`00000000 : NETwew00+0x14ad9f fffff801`dcd066f0 fffff880`05d534de : fffffa80`0732f1a0 fffff880`05ab7bdb fffff880`05d884b0 fffff880`05d746f0 : NETwew00+0x25ad45 fffff801`dcd06720 fffff880`05bcf40d : fffffa80`0732f000 00000000`00000000 fffffa80`0af6efb0 00000000`00000000 : NETwew00+0x2cf4de fffff801`dcd06770 fffff880`05ab3304 : 00000000`00000000 fffff880`05bcf3a0 fffffa80`075fca90 fffff880`05ab2e63 : NETwew00+0x14b40d fffff801`dcd067d0 fffff880`05aab28f : 00000000`00000000 00000000`00000000 fffffa80`0af6efb0 fffffa80`075fcd70 : NETwew00+0x2f304 fffff801`dcd06820 fffff880`05ad10fc : 00000000`00000000 fffff880`05bd93b0 fffffa80`0b55a850 fffffa80`0b550900 : NETwew00+0x2728f fffff801`dcd06870 fffff880`05ab3304 : fffffa80`0af6c0a0 fffff880`05c91690 fffffa80`0b55a850 fffffa80`0af6f260 : NETwew00+0x4d0fc fffff801`dcd068b0 fffff880`05aab28f : 00000000`00000010 fffffa80`0af6ca48 fffffa80`0af7f6e0 fffffa80`075db2b0 : NETwew00+0x2f304 fffff801`dcd06900 fffff880`05b350bf : fffffa80`0b56b4e8 fffffa80`07324cf0 fffffa80`0b56b4e0 00000000`00000001 : NETwew00+0x2728f fffff801`dcd06950 fffff880`05ac9a6e : 00000000`00000000 fffff880`00000000 ffff193d`b0ee837f fffff880`05cf08f1 : NETwew00+0xb10bf fffff801`dcd069a0 fffff880`05acc3b7 : fffffa80`07324cf0 00000000`000000ff 00000000`00000000 fffffa80`0afe0190 : NETwew00+0x45a6e fffff801`dcd069f0 fffff880`05ac76f6 : fffffa80`0afe0190 fffffa80`07324cf0 00000000`000000ff fffff880`05ab7b3d : NETwew00+0x483b7 fffff801`dcd06a20 fffff880`05ac7fd1 : 00000002`00000001 fffffa80`0b532df0 00000000`00000000 fffffa80`07324cff : NETwew00+0x436f6 fffff801`dcd06ab0 fffff880`05ac25e7 : fffffa80`0b55aa01 fffffa80`0b55ab90 fffff801`dcd06bff fffff801`dcd06b70 : NETwew00+0x43fd1 fffff801`dcd06b50 fffff880`01c83e2e : 00000000`00000000 fffffa80`0b55ab90 00000000`00000000 00000000`00000000 : NETwew00+0x3e5e7 fffff801`dcd06bd0 fffff880`01c83f3e : fffffa80`0b55ae78 00000000`ffffffff fffffa80`0b55ab90 00000424`9431ba34 : ndis!ndisMiniportDpc+0xfe fffff801`dcd06c70 fffff801`dd918fd8 : fffff801`ddb6ff00 fffff801`00001000 fffff801`dcd06e80 fffff801`dcd00f44 : ndis!ndisInterruptDpc+0x9e fffff801`dcd06d00 fffff801`dd9185d0 : fffff801`ddb6d180 fffff880`03a9f7d0 fffffa80`04d4cb00 00000000`00000004 : nt!KiExecuteAllDpcs+0x198 fffff801`dcd06e40 fffff801`dd917fc5 : 00000000`00000000 fffff801`ddb6d180 fffff880`1ab7d740 fffff880`03343840 : nt!KiRetireDpcList+0xd0 fffff801`dcd06fb0 fffff801`dd917dc9 : fffff880`1ab7d650 00000000`00000010 ffffcd41`5a2d6bb7 fffff801`ddb08bc0 : nt!KxRetireDpcList+0x5 fffff880`1ab7d680 fffff801`dd9b3415 : fffffbdb`6bce4263 fffff801`dd8ea823 fffff880`1ab7d740 fffff880`1ab7d900 : nt!KiDispatchInterruptContinue fffff880`1ab7d6b0 fffff801`dd8ea823 : fffff880`1ab7d740 fffff880`1ab7d900 fffff880`1ab7d740 fffff880`00000000 : nt!KiDpcInterruptBypass+0x25 fffff880`1ab7d6c0 fffff801`dd836be2 : fffff801`dd8290e0 00000000`00000013 fffff880`05efe4a0 00000000`00000014 : nt!KiInterruptDispatch+0x273 fffff880`1ab7d858 fffff801`dd8290e0 : 00000000`00000013 fffff880`05efe4a0 00000000`00000014 fffff880`05f0a320 : hal!HalpTscQueryCounter+0x2 fffff880`1ab7d860 fffff880`05f00c0f : 00000000`000007b1 00000000`000007b1 fffff880`1ab7d9c9 00000000`00000000 : hal!HalpTimerStallExecutionProcessor+0x131 fffff880`1ab7d8f0 fffff880`05f12cd3 : 00000000`00000001 00000000`00000000 00000000`00042065 00000000`000000ff : i8042prt!I8xGetBytePolled+0xef fffff880`1ab7d930 fffff880`05f151fd : 00000000`00030001 00000000`00030001 00000000`00000064 00000000`00000064 : i8042prt!I8xInitializeKeyboard+0x143 fffff880`1ab7da30 fffff880`05f0f008 : fffffa80`0483ba20 fffffa80`072e5b40 fffffa80`073618b0 fffffa80`072e5b40 : i8042prt! ?? ::NNGAKEGL::`string'+0x1ea fffff880`1ab7da90 fffff801`dd8dd49b : fffffa80`04c0ba50 fffff880`c0000001 fffff880`c0000001 fffffa80`0d565940 : i8042prt!I8xReinitializeHardware+0x108 fffff880`1ab7db10 fffff801`dd92a641 : fffff801`ddafb110 fffffa80`0d7686c0 fffff801`dd8dd43c fffff801`00000000 : nt!IopProcessWorkItem+0x5f fffff880`1ab7db80 fffff801`dd899625 : fffffa80`03f89b80 00000000`00000080 fffff801`dd92a500 fffffa80`0d7686c0 : nt!ExpWorkerThread+0x142 fffff880`1ab7dc10 fffff801`dd8d7e56 : fffff880`00996180 fffffa80`0d7686c0 fffffa80`03699040 fffffa80`03629040 : nt!PspSystemThreadStartup+0x59 fffff880`1ab7dc60 00000000`00000000 : fffff880`1ab7e000 fffff880`1ab78000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: NETwew00+28cd44 fffff880`05d10d44 83bc2480000000ff cmp     dword ptr [rsp+80h],0FFFFFFFFh
    SYMBOL_STACK_INDEX:  8
    SYMBOL_NAME:  NETwew00+28cd44
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NETwew00
    IMAGE_NAME:  NETwew00.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5051de6a
    FAILURE_BUCKET_ID:  0x133_DPC_NETwew00+28cd44
    BUCKET_ID:  0x133_DPC_NETwew00+28cd44
    Followup: MachineOwner ---------
    (From W530 machine) 
    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: 0000000000000281, The DPC time count (in ticks). Arg3: 0000000000000280, 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:  netsh.exe
    CURRENT_IRQL:  d
    LAST_CONTROL_TRANSFER:  from fffff801c0dd9853 to fffff801c0c7f740
    STACK_TEXT:  fffff801`bfd78e08 fffff801`c0dd9853 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx fffff801`bfd78e10 fffff801`c0caae51 : 00000000`00000000 fffff801`c0efb180 fffff801`bfd78fc0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c fffff801`bfd78e90 fffff801`c0cabcd8 : ffffffff`ffd0ec08 fffff801`c139a502 fffff801`bfd78fc0 fffff880`00000000 : nt!KeUpdateRunTime+0x51 fffff801`bfd78ec0 fffff801`c1370eca : ffffffff`ffd0ec08 fffff801`c139a502 00000000`4dedc032 00000000`00000000 : nt!KeUpdateTime+0x3f9 fffff801`bfd790b0 fffff801`c0c78b2e : 00000130`eb958f54 00000000`56005d8e fffff801`c139a580 fffff880`033326c0 : hal!HalpTimerClockInterrupt+0x86 fffff801`bfd790e0 fffff801`c0c6f643 : fffffa80`159f0d40 fffff880`06acb06b fffffa80`1596f598 fffff801`bfd79309 : nt!KiInterruptDispatchLBControl+0x1ce fffff801`bfd79270 fffff801`c0cac025 : 00000000`00000002 fffff880`06ce6a24 fffff801`bfd79370 fffffa80`1596f310 : nt!KxWaitForSpinLockAndAcquire+0x23 fffff801`bfd792a0 fffff880`06cdcd44 : fffffa80`169fd0d0 00000000`c0000001 fffff801`bfd79440 fffff880`06a6b3a3 : nt!KeAcquireSpinLockRaiseToDpc+0x35 fffff801`bfd792d0 fffff880`06cafdd6 : fffffa80`1598a1e0 fffff880`06cafdb0 fffffa80`159c19b0 fffffa80`159654d0 : NETwew00+0x28cd44 fffff801`bfd79330 fffff880`06a7f304 : fffffa80`00000006 00000000`00000000 00000000`000000e2 fffff880`00000006 : NETwew00+0x25fdd6 fffff801`bfd79370 fffff880`06a7728f : 00000000`00000010 fffffa80`15972508 fffffa80`159654d0 fffffa80`159c1d70 : NETwew00+0x2f304 fffff801`bfd793c0 fffff880`06a9cd3f : 00000000`c0000001 fffff880`06ad4c00 fffffa80`15ba3e70 fffffa80`1596f540 : NETwew00+0x2728f fffff801`bfd79410 fffff880`06ab8c69 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : NETwew00+0x4cd3f fffff801`bfd79460 fffff880`06ad4c30 : 00000000`00000000 fffffa80`15978cd8 fffffa80`1597cab0 fffffa80`0ba2f000 : NETwew00+0x68c69 fffff801`bfd79490 fffff880`06a7f304 : 00000000`00000000 fffff880`06ad4040 fffffa80`15ba3e70 00000000`00000001 : NETwew00+0x84c30 fffff801`bfd794d0 fffff880`06a7728f : 00000000`00000040 fffffa80`15979408 fffffa80`1597cab0 fffffa80`0bbed010 : NETwew00+0x2f304 fffff801`bfd79520 fffff880`06ab8de9 : 00000000`ff000401 fffff801`bfd79638 00000000`00000004 fffffa80`0bbed010 : NETwew00+0x2728f fffff801`bfd79570 fffff880`06ac73f2 : fffffa80`000000c7 fffffa80`159f0d40 00000000`00000000 00000000`00000000 : NETwew00+0x68de9 fffff801`bfd795f0 fffff880`06ce3981 : fffffa80`0b160bc0 00000000`00000000 00000000`00000000 fffff880`06ce3870 : NETwew00+0x773f2 fffff801`bfd79630 fffff880`06b9ad9f : fffffa80`159e8320 00000000`00000000 fffffa80`159e8000 00000000`00000000 : NETwew00+0x293981 fffff801`bfd79680 fffff880`06caad45 : fffffa80`0b160bc0 fffffa80`159e8000 fffffa80`159704f0 00000000`00000000 : NETwew00+0x14ad9f fffff801`bfd796f0 fffff880`06d1f4de : fffffa80`159e81a0 fffff880`06a83bdb fffff880`06d544b0 fffff880`06d406f0 : NETwew00+0x25ad45 fffff801`bfd79720 fffff880`06b9b40d : fffffa80`159e8000 00000000`00000000 fffffa80`159704f0 00000000`00000000 : NETwew00+0x2cf4de fffff801`bfd79770 fffff880`06a7f304 : 00000000`00000000 fffff880`06b9b3a0 fffffa80`159c19b0 fffff880`06a7ee63 : NETwew00+0x14b40d fffff801`bfd797d0 fffff880`06a7728f : 00000000`00000000 00000000`00000000 fffffa80`159704f0 fffffa80`159c1d70 : NETwew00+0x2f304 fffff801`bfd79820 fffff880`06a9d0fc : 00000000`00000000 fffff880`06ba53b0 fffffa80`15ba3e70 fffffa80`15ba3ba0 : NETwew00+0x2728f fffff801`bfd79870 fffff880`06a7f304 : fffffa80`15969790 fffff880`06c5d690 fffffa80`15ba3e70 fffffa80`1597f260 : NETwew00+0x4d0fc fffff801`bfd798b0 fffff880`06a7728f : 00000000`00000010 fffffa80`1596a138 fffffa80`15953b70 fffffa80`0bbed010 : NETwew00+0x2f304 fffff801`bfd79900 fffff880`06b010bf : fffffa80`0b0eb4e8 fffffa80`0bbed390 fffffa80`0b0eb4e0 00000000`00000001 : NETwew00+0x2728f fffff801`bfd79950 fffff880`06a95a6e : 00000000`00000000 00000000`00000f32 00000000`00400a02 fffff880`01a68d24 : NETwew00+0xb10bf fffff801`bfd799a0 fffff880`06a983b7 : fffffa80`0bbed390 00000000`000000ff 00000000`00000000 fffffa80`15b43400 : NETwew00+0x45a6e fffff801`bfd799f0 fffff880`06a936f6 : fffffa80`15b43400 fffffa80`0bbed390 00000000`000000ff fffff801`c0efdf00 : NETwew00+0x483b7 fffff801`bfd79a20 fffff880`06a93fd1 : fffffa80`00000001 fffffa80`15b5dbd0 fffffa80`0bbed700 fffffa80`0bbed3ff : NETwew00+0x436f6 fffff801`bfd79ab0 fffff880`06a8e5e7 : fffffa80`159fec01 fffffa80`15b85850 fffff801`bfd79bff fffffa80`06c89398 : NETwew00+0x43fd1 fffff801`bfd79b50 fffff880`01a68e2e : 00000000`00000000 fffffa80`15b85850 00000000`00000000 fffffa80`07760a70 : NETwew00+0x3e5e7 fffff801`bfd79bd0 fffff880`01a68f3e : fffffa80`15b85d38 00000000`ffffffff fffffa80`15b85850 0000240a`bb33711e : ndis!ndisMiniportDpc+0xfe fffff801`bfd79c70 fffff801`c0ca6fd8 : fffff801`c0efdf00 00000000`00001000 fffffa80`0b0870b8 fffff801`bfd70f44 : ndis!ndisInterruptDpc+0x9e fffff801`bfd79d00 fffff801`c0ca65d0 : fffff801`c0efb180 00000126`a2c54098 fffffa80`17125b00 00000000`00000025 : nt!KiExecuteAllDpcs+0x198 fffff801`bfd79e40 fffff801`c0ca5fc5 : 00000000`00000000 fffff801`c0efb180 fffff880`1f8532b0 fffffa80`2e5edba0 : nt!KiRetireDpcList+0xd0 fffff801`bfd79fb0 fffff801`c0ca5dc9 : ffffe9a6`00000005 00000000`00000000 fffffa80`1dde1b50 fffff880`03332780 : nt!KxRetireDpcList+0x5 fffff880`1f853200 fffff801`c0d412d8 : fffff880`1f8532b0 00000000`00000000 fffff880`1f8532b0 fffff880`00000000 : nt!KiDispatchInterruptContinue fffff880`1f853230 fffff801`c0cb9262 : fffffa80`1faa3f04 fffffa80`08de09e0 fffffa80`1faa3f20 fffff801`c0efb180 : nt!KiDpcInterrupt+0xc8 fffff880`1f8533c0 fffff801`c1064f13 : fffffa80`1faa3f20 00000000`00000000 00000000`00000000 fffff880`1f8538c0 : nt!IopQueueThreadIrp+0x82 fffff880`1f8533f0 fffff801`c104b6da : 00000000`00000000 fffffa80`08de09e0 fffff880`1f853751 00000000`00000001 : nt!IopCloseFile+0x123 fffff880`1f853480 fffff801`c1047c7d : fffff801`c0c05000 fffff801`c0c05000 00000000`00000000 fffffa80`08bc9c90 : nt!IopParseDevice+0xdda fffff880`1f853670 fffff801`c104d2d8 : 00000000`00000000 fffff880`1f853818 00000000`00000040 fffffa80`06ce55a0 : nt!ObpLookupObjectName+0x7a1 fffff880`1f8537a0 fffff801`c0ffce7c : 00000000`00000000 00000000`00f2df88 00000000`00000001 fffff801`c10196d8 : nt!ObOpenObjectByName+0x258 fffff880`1f853870 fffff801`c0c7e753 : 00000000`00000000 00000000`00000000 fffffa80`1dde1780 fffff880`c0000034 : nt!NtQueryAttributesFile+0x13b fffff880`1f853b00 000007fd`5c722fba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00f2df48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`5c722fba
    STACK_COMMAND:  kb
    FOLLOWUP_IP: NETwew00+28cd44 fffff880`06cdcd44 83bc2480000000ff cmp     dword ptr [rsp+80h],0FFFFFFFFh
    SYMBOL_STACK_INDEX:  8
    SYMBOL_NAME:  NETwew00+28cd44
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NETwew00
    IMAGE_NAME:  NETwew00.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5051de6a
    FAILURE_BUCKET_ID:  0x133_DPC_NETwew00+28cd44
    BUCKET_ID:  0x133_DPC_NETwew00+28cd44
    Followup: MachineOwner ---------
    0: kd> lmvm netwew00 start             end                 module name fffff880`06a50000 fffff880`06ebc000   NETwew00   (no symbols)               Loaded symbol image file: NETwew00.sys     Image path: \SystemRoot\system32\DRIVERS\NETwew00.sys     Image name: NETwew00.sys     Timestamp:        Thu Sep 13 06:23:54 2012 (5051DE6A)     CheckSum:         00419EED     ImageSize:        0046C000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    NETwew00.sys version on my system: 15.5.4.45
    Latest driver version from Lenovo support site: 15.5.3.43

  • 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

  • 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!!!

  • DPC Watchdog Violation in windows 8

    Hello everyone,
    my uncle just purchased my toshiba laptop model P55-A5200 last week. i had this problem now, when my pc is configuring windows updates at 15 % ,it  freezes and is having  DPC Watchdog Violation bluescreen errors and then when it was  about to restart, still appears the same, it can't proceed to windows 8. Instead, in the blue screen a "Recovery" appears and made me choose either restart my pc or see advanced repair options. i tried to choose "restart my pc" but still the same. when i choose "see advanced repair option" i don't know where to choose to. I also had this problem, I was not able to create recovery media in my usb.  PLEASE HELP ME. I don't know what to do ... see these images here that i attached. please please please help me...
    Attachments:
    imm_2013_09_18_07_34_07_320.JPG ‏26 KB
    imm_2013_09_18_07_34_24_9.JPG ‏26 KB
    imm_2013_09_18_07_35_11_929.JPG ‏25 KB

    Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Caused By Driver  : tm.sys
    Bug Check 0x133 DPC_WATCHDOG_VIOLATION
    Caused By Driver  : hal.dll
    The other dmp file was corrupt.
    The two files mentioned here don't help us, because they are Windows core system files.
    Attach a few more. Maybe we'll get better clues. You might zip up a bunch of them.
    Did you do a Refresh as I suggested?
    ==================================================
    Dump File         : 092013-58343-01.dmp
    Crash Time        : 9/20/2013 5:55:01 AM
    Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code    : 0x000000d1
    Parameter 1       : 00000000`00000aa0
    Parameter 2       : 00000000`00000002
    Parameter 3       : 00000000`00000000
    Parameter 4       : fffff880`1742c33b
    Caused By Driver  : tm.sys
    Caused By Address : tm.sys+1675433b
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\092013-58343-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 9200
    ==================================================
    ==================================================
    Dump File         : 091413-33500-01.dmp
    Crash Time        : 9/20/2013 5:54:52 AM
    Bug Check String  :
    Bug Check Code    : 0x00000133
    Parameter 1       : 00000000`00000001
    Parameter 2       : 00000000`00001e00
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : hal.dll
    Caused By Address : hal.dll+22e94
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\091413-33500-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 9200
    ==================================================
    -Jerry

  • 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"

  • Repeated BSODs in my brand new X230 (with Windows 8)

    Hello
    I purchased the new X230 in early December and then went on vacation (without it) for two weeks. Thus this is really my first week using it. I've had NINE blue screens of death already, each with the term dpc_watchdog_violation. Further, my Citrix remote work-enabled system shuts down on this computer, making this computer just about useless for work purposes. I'm worried this is a lemon -- how can I have so many crashes in the first week of use? The summary of the crash events is below. Has anyone had similar problems? Has anyone had problems with rtwlane.sys on their X230s?
    Thanks for your thoughts and time,
    ML
    On Sat 1/12/2013 7:41:48 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011213-19546-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/12/2013 7:41:48 PM GMT your computer crashed
    crash dump file: C:\windows\memory.dmp
    This was probably caused by the following module: rtwlane.sys (rtwlane+0xFF204)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\drivers\rtwlane.sys
    product: Realtek PCIEWireless LAN PCI-E NIC
    company: Realtek Semiconductor Corporation
    description: Realtek PCIE NDIS Driverr
    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: rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation ).
    Google query: Realtek Semiconductor Corporation DPC_WATCHDOG_VIOLATION
    On Fri 1/11/2013 7:08:31 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011113-22437-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/11/2013 6:27:07 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011113-20000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/10/2013 7:25:31 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011013-19296-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/10/2013 7:18:01 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011013-25890-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/10/2013 6:50:59 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011013-26921-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/10/2013 7:01:44 AM GMT your computer crashed
    crash dump file: C:\windows\Minidump\011013-73421-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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 1/9/2013 7:18:40 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\010913-17562-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
    Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® 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.
    Solved!
    Go to Solution.

    Hi, MLinBerlin
    I did some research on the issue on Microsoft's website and found this page explaining what a DPC_WATCHDOG_VIOLATION is. According to Microsoft, this error is normally caused by either hardware or a driver of associated hardware. For this reason, I would recommend making sure that all the drivers and BIOS are up to date to rule out any software reasons for this issue. All drivers for your system can be found here. It could possibly be hardware, but let's hope that some updates will get it running smoothly.
    Good luck, and let me know how it goes
    Adam
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

  • 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

    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

Maybe you are looking for

  • How can you tell if the line has errors?

    I'll try and keep this as brief as possible. <background> For 2years (up to 6months ago) I was on BE ADSL and was very impressed with the quality of the service (low latency, decent bandwidth) on my line.  However when I heard that FTTC was being rol

  • How long does it takes to install boot camp?

    Hi, I am short in time so i would like to know how much time does it takes to install bootcamp, by this i mean partitioning, installing windows xp and the drivers. Thanx

  • Save billing document as pdf file in a shared folder

    hi experts, my requirement is to save the billing documents as a pdf file whenever it is generated automatically. is it possible to define a output type to save the pdf file similar to the one used for sending pdf files as attachemnts in email.

  • Exporting result of query to another input query (Write Cube )?

    Hello BI experts, Is it possible to send a result of a read cube / query to be saved into other write cube  / query ? If yes , how to do ? thx in advance

  • Authorization based on cost center for manual actual postings

    Hello, We tried to use customer function (COCCA001)/EXIT_SAPLKBER_001 for actual postings (as this is not feasible in standard with PFCG). Unfortunately, this exit seems not to be working for actuals postings (kb11n, kb15n, KB21n). I found in SPRO th