Windows 10: Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133

Discus and support Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133 in Windows 10 BSOD Crashes and Debugging to solve the problem; I have been getting blue screens off and on for sometime but not nearly as many that have ocurred over the last few weeks. Mini-dumps and full dumps... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Boobot, Apr 5, 2021.

  1. Boobot Win User

    Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133


    I have been getting blue screens off and on for sometime but not nearly as many that have ocurred over the last few weeks. Mini-dumps and full dumps were taken. I took an effort to decipher them and review options on these boards. I'm having some issues with symbol loading. I have done as much as possibly can with updates to drivers, firmware, chipsets, etc. I'm hoping someone can review this with me and pinpoint the specific issue/culprit! Most of the time the bluescreens occur when the system is idle and not being used but not always the case.


    List of bluescreens over the last several weeks.


    Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133 a87bd566-33e9-4695-87f5-8721ab74efbc?upload=true.jpg




    [COLOR=rgba42, 0, 170, 1]Most recent bugcheck analysis today![/COLOR]


    *******************************************************************************

    * *

    * 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: fffff80632cfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding the cumulative timeout

    Arg4: 0000000000000000



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 4



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on BOOOFFICEPC



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 4



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 466



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 133



    BUGCHECK_P1: 1



    BUGCHECK_P2: 1e00



    BUGCHECK_P3: fffff80632cfb320



    BUGCHECK_P4: 0



    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    PROCESS_NAME: System



    STACK_TEXT:

    fffff806`3607ac88 fffff806`3243ac52 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`32cfb320 : nt!KeBugCheckEx

    fffff806`3607ac90 fffff806`3227541d : 00012261`653eff20 fffff806`2ef64180 00000000`00000246 00000000`0056c010 : nt!KeAccumulateTicks+0x1c8a52

    fffff806`3607acf0 fffff806`322759c1 : 00000000`00000000 00000000`0033b509 fffff806`2ef64180 00000000`00000001 : nt!KiUpdateRunTime+0x5d

    fffff806`3607ad40 fffff806`3226f833 : fffff806`2ef64180 00000000`00000000 fffff806`32c31b18 00000000`00000000 : nt!KiUpdateTime+0x4a1

    fffff806`3607ae80 fffff806`322781f2 : ffffb503`2be284c0 ffffb503`2be28540 ffffb503`2be28500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3

    fffff806`3607af30 fffff806`32327f55 : 000000ce`d43c222b fffff806`32cf3ba0 fffff806`32cf3c50 ffffcb4d`64373300 : nt!HalpTimerClockInterrupt+0xe2

    fffff806`3607af60 fffff806`323f76fa : ffffb503`2be28540 fffff806`32cf3ba0 ffff9001`10140180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff806`3607afb0 fffff806`323f7c67 : 00000000`ffffffff 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    ffffb503`2be284c0 fffff806`32519d6b : ffffb503`2be28860 00000000`00000cc0 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    ffffb503`2be28650 fffff806`3242c942 : fffff806`2ef64180 ffffe30f`cb4ac900 ffffa00d`00000002 ffffb503`2be2875c : nt!KiHeteroChooseTargetProcessor+0x58b

    ffffb503`2be28720 fffff806`3226d1cc : fffff806`2ef64180 fffff806`3251949e 00000000`00000fff ffffb503`2be28990 : nt!KiDeferredReadySingleThread+0x1e1df2

    ffffb503`2be28910 fffff806`323333f1 : ffffe30f`d7eb0158 00000000`0056a210 00000000`00000010 fffff806`2ef64180 : nt!KiReadyDeferredReadyList+0x3c

    ffffb503`2be28940 fffff806`32331646 : fffff806`2ef64180 fffff806`32d27600 00000000`02ff1a00 00000000`00000000 : nt!KiQueueReadyThread+0x361

    ffffb503`2be289c0 fffff806`323fca96 : fffff806`323f1d00 fffff806`322ec5ca 00007ffb`d96984b0 00007ffb`d9698488 : nt!KiQuantumEnd+0x366

    ffffb503`2be28ac0 fffff806`323fc335 : 00000207`5bab5eb0 fffff806`323f7ce1 00000207`66888aa0 ffffe30f`e541ef60 : nt!KiDispatchInterruptContinue+0x16

    ffffb503`2be28af0 fffff806`323f7ce1 : 00000207`66888aa0 ffffe30f`e541ef60 ffffb503`2be28b80 ffffe30f`00000000 : nt!KiDpcInterruptBypass+0x25

    ffffb503`2be28b00 00007ffb`96342b4b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1

    0000002e`197fee78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`96342b4b





    SYMBOL_NAME: nt!KeAccumulateTicks+1c8a52



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 1c8a52



    FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}



    Followup: MachineOwner

    ---------

    :)
     
    Boobot, Apr 5, 2021
    #1

  2. Blue screen: DPC_WATCHDOG_VIOLATION

    After a recent updating, my machine has blue screen every 5 - 10 minutes.

    The error code is DPC_WATCHDOG_VIOLATION

    I saw another post here which suggest to use "iastor.sys". But I don't have that in the driver list. Mine is storahci.sys.

    Please advise! Thanks,
     
    hairinwind, Apr 5, 2021
    #2
  3. Roan T Win User
    Blue Screen

    Hi,





    Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
    would like to know more about the issue. Please clarify the following:

    • Did you get a STOP code?
    • Did you install any hardware or driver recently?



    For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
    article and simply follow the steps.



    Feel free to contact us if you need further help.
     
    Roan T, Apr 5, 2021
    #3
  4. Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133

    DPC_WATCHDOG_VIOLATION

    Hi Mattie,

    The DPC_WATCHDOG_VIOLATION blue screen error can be caused by a variety of hardware, firmware, driver, or software issues. Now, you mentioned that you already changed the IDE ATA/ATAPI controllers to standard. Did you update the driver as well? And also,
    are you getting the same blue screen error when you play other games? Or is it only occurring when you play a particular game?

    For the mean time, if you haven't tried any further troubleshooting steps, we suggest that you perform the suggested steps from this article:

    Troubleshoot blue screen errors
    .

    Let us know how this turns out for you.
     
    Marque Lor, Apr 5, 2021
    #4
Thema:

Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133

Loading...
  1. Blue Screens - Most recent - DPC_WATCHDOG_VIOLATION 133 - Similar Threads - Blue Screens recent

  2. I get blue screen cause DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    I get blue screen cause DPC_WATCHDOG_VIOLATION 133: CAN SOMEONE HELP MEPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above.Arg2: 0000000000001e00, The...
  3. I get blue screen cause DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    I get blue screen cause DPC_WATCHDOG_VIOLATION 133: CAN SOMEONE HELP MEPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above.Arg2: 0000000000001e00, The...
  4. I get blue screen cause DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    I get blue screen cause DPC_WATCHDOG_VIOLATION 133: CAN SOMEONE HELP MEPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above.Arg2: 0000000000001e00, The...
  5. DPC_WATCHDOG_VIOLATION 133 Blue screen

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133 Blue screen: I've ran mindbg and it says this:4: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC...
  6. DPC_WATCHDOG_VIOLATION 133 Blue screen

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 133 Blue screen: I've ran mindbg and it says this:4: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC...
  7. DPC_WATCHDOG_VIOLATION 133 Blue screen

    in Windows 10 Drivers and Hardware
    DPC_WATCHDOG_VIOLATION 133 Blue screen: I've ran mindbg and it says this:4: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC...
  8. Blue Screen Error - DPC_WATCHDOG_VIOLATION 133 - 0x133_ISR_SmbCo10X64!unknown_function

    in Windows 10 Gaming
    Blue Screen Error - DPC_WATCHDOG_VIOLATION 133 - 0x133_ISR_SmbCo10X64!unknown_function: Hi,I get regular BSOD erros with DPC_WATCHDOG_VIOLATION 133 on my new Dell Inspiron 15 AMD R7 and Win11. I did a clean Win11 re-install and made sure all drivers are up to date but I keep getting BSOD.The dump file shows FAILURE_BUCKET_ID:...
  9. Blue Screen Error - DPC_WATCHDOG_VIOLATION 133 - 0x133_ISR_SmbCo10X64!unknown_function

    in Windows 10 Software and Apps
    Blue Screen Error - DPC_WATCHDOG_VIOLATION 133 - 0x133_ISR_SmbCo10X64!unknown_function: Hi,I get regular BSOD erros with DPC_WATCHDOG_VIOLATION 133 on my new Dell Inspiron 15 AMD R7 and Win11. I did a clean Win11 re-install and made sure all drivers are up to date but I keep getting BSOD.The dump file shows FAILURE_BUCKET_ID:...
  10. How to solve blue screen - DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    How to solve blue screen - DPC_WATCHDOG_VIOLATION 133: Hello all,I'm trying to solve this error and this is the result when I run the "!analyze -v" command.Microsoft R Windows Debugger Version 10.0.21349.1004 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump...