Windows 8 and 8.1 Forums


Windows 8 Pro DPC_Watchdog_Violation

  1. #1


    Posts : 12
    windows 8

    Windows 8 Pro DPC_Watchdog_Violation


    Windows 8 Pro DPC_Watchdog_Violation

    When i put some stress to my computer i get a BSOD, normally when im playing video-games defragmenting hard drive, coping a lot of information from i disk to other, or using a couple of heavy software like photoshop, lightroom, etc...



    I re-install 3 time windows 8.
    I change my seagates hdd for a WD caviar black
    i change my cpu from intel 2 core duo to a quad core
    i upgrade my memory ram from 4 gb to 8 gb kingston HyperX

    i don´t know what else to do to have a healthy PC.

    I still have problems. Please how can i fix this problem.

    any help and/or advice would be much appreciated!! thanks in advanced!

    I uploaded the .zip file as an attachment. Hopefully that works better.
    Last edited by capitancabeza; 05 Feb 2013 at 04:29. Reason: More details

      My System SpecsSystem Spec

  2. #2


    Welcome to the forums, had a peek at your dump files your BSOD is being cause by Norton:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {4, 12c, fffffa800bfd3680, fffff803d4378940}
    
    *** WARNING: Unable to verify timestamp for SRTSP64.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
    Can't retrieve thread context, Win32 error 0n30
    Probably caused by : SRTSP64.SYS ( SRTSP64+734e5 )
    
    Followup: MachineOwner
    ---------
    please remove it using this tool: Norton removal tool

    you may also wish to install Mbam as it words well with windows defender which comes as a built in virus protection for Windows 8

    Tip: when installing Mbam be sure to uncheck the box to start a free trial.
      My System SpecsSystem Spec

  3. #3


    Posts : 12
    windows 8


    ok, ty i uninstalled, let´s seee what happen in a few day.


    Now the other dump file about the dpc watch dog what is the problem:

    take a look to this:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 133, {1, 784, 0, 0}
    
    
    Probably caused by : storahci.sys ( storahci!P_NotRunning+e7 )
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> !analyza -v
    No export analyza found
    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: 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: 0000000000000784, 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:  svchost.exe
    
    
    CURRENT_IRQL:  d
    
    
    TAG_NOT_DEFINED_c000000f:  FFFFF802FAA3EFB0
    
    
    LAST_CONTROL_TRANSFER:  from fffff802fb7f1637 to fffff802fb698040
    
    
    STACK_TEXT:  
    fffff802`faa3e6e8 fffff802`fb7f1637 : 00000000`00000133 00000000`00000001 00000000`00000784 00000000`00000000 : nt!KeBugCheckEx
    fffff802`faa3e6f0 fffff802`fb6c2f11 : 00000000`00000001 fffff802`fb913180 fffff802`faa3e8a0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c00
    fffff802`faa3e770 fffff802`fb6c3d98 : ffffffff`ffd0a270 fffff802`fbdb1506 fffff802`faa3e8a0 fffff802`fbdb1506 : nt!KeUpdateRunTime+0x51
    fffff802`faa3e7a0 fffff802`fbd87eba : ffffffff`ffd0a270 fffff802`fbdb1506 ffffffff`ffd0a270 00000000`00000001 : nt!KeUpdateTime+0x3f9
    fffff802`faa3e990 fffff802`fb691bca : 00000012`2d1ddd64 ffffed0d`7863e6cf fffff802`fbdb1580 ffffed0d`7ac65673 : hal!HalpTimerClockInterrupt+0x86
    fffff802`faa3e9c0 fffff802`fbd90ba2 : fffff802`fbd830d0 00000000`ffffffff fffffa80`0bddc650 00000000`fffd58dd : nt!KiInterruptDispatchNoLockNoEtw+0x1aa
    fffff802`faa3eb58 fffff802`fbd830d0 : 00000000`ffffffff fffffa80`0bddc650 00000000`fffd58dd 00000000`00000000 : hal!HalpTscQueryCounter+0x2
    fffff802`faa3eb60 fffff880`00a98f27 : fffffa80`0772803b fffffa80`0772803b fffff802`faa3ee00 fffff802`fb913180 : hal!HalpTimerStallExecutionProcessor+0x131
    fffff802`faa3ebf0 fffff880`00a9a35d : fffffa80`07728000 fffff802`faa3ee00 fffffa80`07728948 fffff802`faa3ef01 : storahci!P_NotRunning+0xe7
    fffff802`faa3ec20 fffff880`00a9bb45 : fffffa80`07728000 fffffa80`0771ec30 00000000`00000003 00000000`00000000 : storahci!AhciPortReset+0x29
    fffff802`faa3ec50 fffff880`00a9bc4a : fffffa80`07728000 fffffa80`07728000 00000000`00000000 fffff802`faa3ec40 : storahci!PortBusChangeProcess+0x95
    fffff802`faa3ecc0 fffff802`fb68e498 : fffff802`faa3ee00 00000000`000000f4 fffffa80`07acb038 fffff802`faa3eef0 : storahci!AhciPortBusChangeDpcRoutine+0x76
    fffff802`faa3ed00 fffff802`fb6bed50 : fffff802`fb913180 00000012`252d0431 fffffa80`0a3e9b00 00000000`0000002d : nt!KiExecuteAllDpcs+0x198
    fffff802`faa3ee40 fffff802`fb6be745 : 00000000`00000000 fffff802`fb913180 fffff880`0a46fcc0 fffff880`031feb40 : nt!KiRetireDpcList+0xd0
    fffff802`faa3efb0 fffff802`fb6be549 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0a46fc00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    storahci!P_NotRunning+e7
    fffff880`00a98f27 fec3            inc     bl
    
    
    SYMBOL_STACK_INDEX:  8
    
    
    SYMBOL_NAME:  storahci!P_NotRunning+e7
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: storahci
    
    
    IMAGE_NAME:  storahci.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5010abcb
    
    
    BUCKET_ID_FUNC_OFFSET:  e7
    
    
    FAILURE_BUCKET_ID:  0x133_ISR_storahci!P_NotRunning
    
    
    BUCKET_ID:  0x133_ISR_storahci!P_NotRunning
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> lmvm storahci
    start             end                 module name
    fffff880`00a93000 fffff880`00aa9000   storahci   (pdb symbols)          c:\symbols\storahci.pdb\543C42D3E183427F9D8491D3704C41981\storahci.pdb
        Loaded symbol image file: storahci.sys
        Mapped memory image file: c:\symbols\storahci.sys\5010ABCB16000\storahci.sys
        Image path: \SystemRoot\System32\drivers\storahci.sys
        Image name: storahci.sys
        Timestamp:        Thu Jul 26 04:30:35 2012 (5010ABCB)
        CheckSum:         0001BCA3
        ImageSize:        00016000
        File version:     6.2.9200.16384
        Product version:  6.2.9200.16384
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     storahci.sys
        OriginalFilename: storahci.sys
        ProductVersion:   6.2.9200.16384
        FileVersion:      6.2.9200.16384 (win8_rtm.120725-1247)
        FileDescription:  MS AHCI Storport Miniport Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.


    What could be the problem with this BSOD

    thanks in advanced!
    Last edited by capitancabeza; 10 Feb 2013 at 07:47. Reason: wrap code around bugcheck analysis
      My System SpecsSystem Spec

  4. #4


    It may actually be alright now often times a 0x101 stop is caused by a driver (in this case the Norton AV driver) locking up one of your computers processors and causing the other processors to think that something has gone wrong when they try to synchronize with it.
      My System SpecsSystem Spec

  5. #5


    Posts : 12
    windows 8


    ok, i will test the system and come back with results, thx a lot.
      My System SpecsSystem Spec

  6. #6


    I look forward to hearing from you.
      My System SpecsSystem Spec

  7. #7


    Posts : 12
    windows 8


    I had another BSOD Today,

    I learn how to debug the crash dump, and i Google it, I know is a nvidia driver, but i don´t know how to resolve it, because i have the lasted driver for nvidia geforce gtx 550 TI FPS 1024mb (310.70-desktop-win8-win7-winvista-64bit-english-whql december 2012), and 3 day ago i ordered another card unit to install it as a sli configuration.

    Everything happen when i turn on the pc, and the computer restart by itself.

    So my question is , what can i do to avoid this cain of BSOD


    Here is the analysis:


    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 133, {0, 283, 282, 0}
    
    
    *** WARNING: Unable to verify timestamp for nvstor64.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
    Probably caused by : nvstor64.sys ( nvstor64+4cbb )
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 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:  dwm.exe
    
    
    CURRENT_IRQL:  d
    
    
    TAG_NOT_DEFINED_c000000f:  FFFFF8021CC00FB0
    
    
    LAST_CONTROL_TRANSFER:  from fffff8021d9d5143 to fffff8021d87c340
    
    
    STACK_TEXT:  
    fffff802`1cc005c8 fffff802`1d9d5143 : 00000000`00000133 00000000`00000000 00000000`00000283 00000000`00000282 : nt!KeBugCheckEx
    fffff802`1cc005d0 fffff802`1d8a7011 : 00000000`00000000 fffff802`1daf7180 fffff802`1cc00780 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c
    fffff802`1cc00650 fffff802`1d8a7e97 : ffffffff`ffd0a270 fffff802`1df96502 fffff802`1cc00780 00000000`00000004 : nt!KeUpdateRunTime+0x51
    fffff802`1cc00680 fffff802`1df6ceca : ffffffff`ffd0a270 fffff802`1df96502 00000000`00000000 fffffa80`06b1d000 : nt!KeUpdateTime+0x3f9
    fffff802`1cc00870 fffff802`1d875f0a : 0000019a`2d768e64 fffff880`0335c3c0 fffff802`1df96580 00000000`00000000 : hal!HalpTimerClockInterrupt+0x86
    fffff802`1cc008a0 fffff880`00a04cbb : fffff880`00a0f938 fffff880`0335c3c0 fffff880`0335c3c0 fffffa80`06b1d280 : nt!KiInterruptDispatchNoLockNoEtw+0x1aa
    fffff802`1cc00a38 fffff880`00a0f938 : fffff880`0335c3c0 fffff880`0335c3c0 fffffa80`06b1d280 fffff880`00a0b55b : nvstor64+0x4cbb
    fffff802`1cc00a40 fffff880`0335c3c0 : fffff880`0335c3c0 fffffa80`06b1d280 fffff880`00a0b55b fffffa80`06b1d000 : nvstor64+0xf938
    fffff802`1cc00a48 fffff880`0335c3c0 : fffffa80`06b1d280 fffff880`00a0b55b fffffa80`06b1d000 fffff880`00a22e39 : 0xfffff880`0335c3c0
    fffff802`1cc00a50 fffffa80`06b1d280 : fffff880`00a0b55b fffffa80`06b1d000 fffff880`00a22e39 fffff880`0335c3e0 : 0xfffff880`0335c3c0
    fffff802`1cc00a58 fffff880`00a0b55b : fffffa80`06b1d000 fffff880`00a22e39 fffff880`0335c3e0 fffffa80`06b1d201 : 0xfffffa80`06b1d280
    fffff802`1cc00a60 fffffa80`06b1d000 : fffff880`00a22e39 fffff880`0335c3e0 fffffa80`06b1d201 fffffa80`06b1d218 : nvstor64+0xb55b
    fffff802`1cc00a68 fffff880`00a22e39 : fffff880`0335c3e0 fffffa80`06b1d201 fffffa80`06b1d218 fffffa80`06b1d000 : 0xfffffa80`06b1d000
    fffff802`1cc00a70 fffff880`0335c3e0 : fffffa80`06b1d201 fffffa80`06b1d218 fffffa80`06b1d000 fffff880`0335c3e0 : nvstor64+0x22e39
    fffff802`1cc00a78 fffffa80`06b1d201 : fffffa80`06b1d218 fffffa80`06b1d000 fffff880`0335c3e0 fffff880`00a0e1a2 : 0xfffff880`0335c3e0
    fffff802`1cc00a80 fffffa80`06b1d218 : fffffa80`06b1d000 fffff880`0335c3e0 fffff880`00a0e1a2 fffffa80`06b1d210 : 0xfffffa80`06b1d201
    fffff802`1cc00a88 fffffa80`06b1d000 : fffff880`0335c3e0 fffff880`00a0e1a2 fffffa80`06b1d210 fffffa80`06b1d210 : 0xfffffa80`06b1d218
    fffff802`1cc00a90 fffff880`0335c3e0 : fffff880`00a0e1a2 fffffa80`06b1d210 fffffa80`06b1d210 fffffa80`06b1d2b0 : 0xfffffa80`06b1d000
    fffff802`1cc00a98 fffff880`00a0e1a2 : fffffa80`06b1d210 fffffa80`06b1d210 fffffa80`06b1d2b0 fffffa80`06b1d218 : 0xfffff880`0335c3e0
    fffff802`1cc00aa0 fffffa80`06b1d210 : fffffa80`06b1d210 fffffa80`06b1d2b0 fffffa80`06b1d218 00000000`00000001 : nvstor64+0xe1a2
    fffff802`1cc00aa8 fffffa80`06b1d210 : fffffa80`06b1d2b0 fffffa80`06b1d218 00000000`00000001 00000000`00000000 : 0xfffffa80`06b1d210
    fffff802`1cc00ab0 fffffa80`06b1d2b0 : fffffa80`06b1d218 00000000`00000001 00000000`00000000 00000000`000000c0 : 0xfffffa80`06b1d210
    fffff802`1cc00ab8 fffffa80`06b1d218 : 00000000`00000001 00000000`00000000 00000000`000000c0 00000000`00400000 : 0xfffffa80`06b1d2b0
    fffff802`1cc00ac0 00000000`00000001 : 00000000`00000000 00000000`000000c0 00000000`00400000 fffffa80`06b1d210 : 0xfffffa80`06b1d218
    fffff802`1cc00ac8 00000000`00000000 : 00000000`000000c0 00000000`00400000 fffffa80`06b1d210 fffff880`00a0e28f : 0x1
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nvstor64+4cbb
    fffff880`00a04cbb ??              ???
    
    
    SYMBOL_STACK_INDEX:  6
    
    
    SYMBOL_NAME:  nvstor64+4cbb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nvstor64
    
    
    IMAGE_NAME:  nvstor64.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbef1e1
    
    
    FAILURE_BUCKET_ID:  0x133_DPC_nvstor64+4cbb
    
    
    BUCKET_ID:  0x133_DPC_nvstor64+4cbb
    
    
    Followup: MachineOwner
    ---------
    Last edited by capitancabeza; 10 Feb 2013 at 08:18. Reason: add attachments
      My System SpecsSystem Spec

  8. #8


    Posts : 12
    windows 8


    I was reading this post
    HTML Code:
    https://www.eightforums.com/bsod-crashes-debugging/17744-random-bsod-when-watching-videos.html
    An I did this

    update

    ASACPI.sys from version 1043.2.15.37 29/03/2005 to 1043.6.0.0 2009/05/05 still old but asus don´t have newer version.

    i´m giving you all the information of my move, so you can figure out how to analyze this problem.

    thx
      My System SpecsSystem Spec

  9. #9


    Tha's because that particular Nvidia driver has nothing to do with your graphics card its your storage driver:

    Driver Reference Table - nvstor64.sys
      My System SpecsSystem Spec

  10. #10


    Posts : 12
    windows 8


    You are my hero, i have an asus P5N-E sli motherboar with a Chipset NVIDIA nForce 650i SLI, i check driver´s version and it was from 2010, now i download the 2011 for windows 7, that should work with W8.

    Thank you a lot...

    Pd: about Windows 8 Pro DPC_Watchdog_Violation after i uninstall Norton Antivirus, everything i working nice, no more blue screen when im playing.
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Windows 8 Pro DPC_Watchdog_Violation
Related Threads
Windows 8 Pro DPC_Watchdog_Violation in BSOD Crashes and Debugging
I turn on pc and when windows starting go BSOD When im playing lol and it go BSOD Litening music and it go to BSDO I restart and the master hard drive disapear, i wait a couple of minute and turn on then i have to go to the BIOS and set the boot priority again.
Solved dpc_watchdog_violation windows 8.1 in BSOD Crashes and Debugging
Hi Just built a new computer and keep getting the dpc_watchdog_violation BSOD at boot It seems to get to the login screen okay, I click with the mouse to show login screen, but keyboard won't let me type in password, and then after a few moments I get the error Boots fine in safe mode ...
windows 8 BSOD DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
hi, I need help regarding my bsod its always DPC_WATCHDOG_VIOLATION. my minidump says its always the halmacpi.dll that causes the problem. :(( I hope this will be fixed soon. I can't even use my pc properly.
Windows 8 BSOD with DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hello I am running windows 8 pro 32 bit system. I seem to be getting BSOD with DPC_WATCHDOG_VIOLATION message quite frequently when browsing internet, on specific sites. Any help is highly appreciated. Regards,
Windows 8 Pro DPC_Watchdog_Violation in BSOD Crashes and Debugging
well like many I am also having the Win 8 BSoD error. i have followed other threads advice tho to no avail. my computer is a ASUS G74SX-XT1 only additions are a 4GB of ram and a 1 TB HDD any help and/or advice would be much appreciated!! thanks in advanced! brsegert
Everytime win8 configure update "features" it just stuck at 15 % and then i got this BSOD screen with the Windows 8 DPC_Watchdog_violation. Thanks!
Solved Windows 8 DPC_Watchdog_Violation in BSOD Crashes and Debugging
Hey..I am hoping someone can give me a hand here because I am all out of ideas. I have tested every subsystem of my PC that I know how.. done mem, cpu, video, disk, stress testing and everything I could think of outside of windows to try and discover a problem.. They all passed. However inside of...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook