Windows 10: BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks

Discus and support BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks in Windows 10 BSOD Crashes and Debugging to solve the problem; I get BSOD, I get debug details use winDbg Microsoft (R) Windows Debugger Version 10.0.18272.1001 AMD64 Copyright (c) Microsoft Corporation. All... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by 易心, Dec 3, 2018.

  1. 易心 Win User

    BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks


    I get BSOD, I get debug details use winDbg




    Microsoft (R) Windows Debugger Version 10.0.18272.1001 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Users\wyndd\Desktop\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





    ************* Path validation summary **************

    Response Time (ms) Location

    Deferred srv*

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 17763 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff800`64ca9000 PsLoadedModuleList = 0xfffff800`650c8990

    Debug session time: Tue Dec 4 00:30:29.407 2018 (UTC + 8:00)

    System Uptime: 1 days 6:57:15.203

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    ......

    Loading User Symbols



    Loading unloaded module list

    .............................

    For analysis of this file, run !analyze -v

    nt!KeBugCheckEx:

    fffff800`64e5a040 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`64a179b0=0000000000000133

    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: 0000000000001e00, The watchdog period.

    Arg3: fffff8006516d380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding the cumulative timeout

    Arg4: 0000000000000000



    Debugging Details:

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



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

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: TickPeriods ***

    *** ***

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



    KEY_VALUES_STRING: 1





    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



    SYSTEM_MANUFACTURER: System manufacturer



    SYSTEM_PRODUCT_NAME: System Product Name



    SYSTEM_SKU: SKU



    SYSTEM_VERSION: System Version



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: 0304



    BIOS_DATE: 11/14/2016



    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



    BASEBOARD_PRODUCT: PRIME B250-PLUS



    BASEBOARD_VERSION: Rev X.0x



    DUMP_TYPE: 1



    BUGCHECK_P1: 1



    BUGCHECK_P2: 1e00



    BUGCHECK_P3: fffff8006516d380



    BUGCHECK_P4: 0



    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED



    CPU_COUNT: 8



    CPU_MHZ: 1068



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: 9



    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXPNP: 1 (!blackboxpnp)





    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0x133



    PROCESS_NAME: System



    CURRENT_IRQL: d



    ANALYSIS_SESSION_HOST: DESKTOP-IGD8G3S



    ANALYSIS_SESSION_TIME: 12-04-2018 00:38:12.0808



    ANALYSIS_VERSION: 10.0.18272.1001 amd64fre



    LAST_CONTROL_TRANSFER: from fffff80064eac8f7 to fffff80064e5a040



    STACK_TEXT:

    fffff800`64a179a8 fffff800`64eac8f7 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`6516d380 : nt!KeBugCheckEx

    fffff800`64a179b0 fffff800`64d21f84 : 0000ed6b`9d66fd8b 00000000`00000000 00000000`006cd2cd fffff800`635cf180 : nt!KeAccumulateTicks+0x187837

    fffff800`64a17a10 fffff800`64c13332 : 00000000`00000000 fffff800`64c77b30 fffff800`64a17e80 00000000`00000003 : nt!KeClockInterruptNotify+0x604

    fffff800`64a17d30 fffff800`64d8ca15 : 00000103`7706cd07 fffff800`64c7a7e0 fffff800`64c7a890 fffff800`64a17e80 : hal!HalpTimerClockInterrupt+0xf2

    fffff800`64a17d60 fffff800`64e5ba3a : fffff800`64a17e80 fffff800`64c7a7e0 ffffca03`7228c500 fffff800`64c14ae6 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff800`64a17db0 fffff800`64e5bf87 : 00000000`00000001 00000000`ffffffff 00000000`00000024 00000000`00400a02 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    fffff800`64a17e00 fffff800`64e5fa76 : fffff800`635cf180 00000000`00000000 fffff18c`e2e0cd50 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    fffff800`64a17f90 fffff800`64e5f5f7 : fffff800`635cf180 fffff18c`e2e0cd50 ffffb781`46cb8140 fffff800`73582395 : nt!KiVmbusInterruptSubDispatch+0xd6

    fffff18c`e2e0ccd0 fffff800`64e60c98 : ffffb781`46cb8140 fffff800`64c14ae6 ffffca03`6f67ce90 fffff800`7390b337 : nt!KiVmbusInterruptDispatch+0x37

    fffff18c`e2e0ce60 fffff800`64e60555 : ffffca03`7228c590 fffff800`64e5b2f1 00000000`00000000 fffff18c`e2e0cf20 : nt!KiDispatchInterruptContinue+0x8

    fffff18c`e2e0ce90 fffff800`64e5b2f1 : 00000000`00000000 fffff18c`e2e0cf20 ffffb781`46cb8140 fffff18c`e2e0d05c : nt!KiDpcInterruptBypass+0x25

    fffff18c`e2e0cea0 fffff800`73a4596c : ffffca03`7228c590 fffff18c`e2e0d1e0 ffffca03`757e4000 fffff800`73a509b8 : nt!KiChainedDispatch+0xb1

    fffff18c`e2e0d030 fffff800`73a46a25 : 00000000`00000000 ffffca03`757e4000 ffffca03`74aee500 fffff18c`e2e0d1e0 : nvlddmkm+0x6c596c

    fffff18c`e2e0d090 fffff800`73a4679d : fffff18c`e2e0d1e0 ffffca03`717bb000 ffffca03`757e4000 ffffca03`74aee500 : nvlddmkm+0x6c6a25

    fffff18c`e2e0d0e0 fffff800`73a500e8 : 00000000`00000000 ffffca03`717bb000 ffffca03`736d9b00 fffff18c`e2e0d1e0 : nvlddmkm+0x6c679d

    fffff18c`e2e0d130 fffff800`73a50256 : 00000000`00000000 00000000`00000000 ffffca03`74aee501 ffffca03`736d9b00 : nvlddmkm+0x6d00e8

    fffff18c`e2e0d180 fffff800`73aa8ee7 : 00000000`00000eee fffff18c`e2e0d2b8 ffffca03`74aee500 ffffca03`757e401a : nvlddmkm+0x6d0256

    fffff18c`e2e0d1e0 fffff800`73aa8c0b : ffffca03`717bb000 00000000`00000000 fffff18c`e2e0d280 ffffca03`757e4000 : nvlddmkm+0x728ee7

    fffff18c`e2e0d250 fffff800`73a508cf : 00000000`00000000 00000000`00000000 00000802`757e4000 ffffca03`757e4000 : nvlddmkm+0x728c0b

    fffff18c`e2e0d2b0 fffff800`73ab1c7d : 00000000`00000000 ffffca03`68b8dd60 ffffca03`757e4000 fffff18c`e2e0d401 : nvlddmkm+0x6d08cf

    fffff18c`e2e0d310 fffff800`73ab1750 : 000a1be4`72280802 fffff18c`e2e0d5a0 fffff18c`e2e0d4f0 ffffca03`6ab72000 : nvlddmkm+0x731c7d

    fffff18c`e2e0d380 fffff800`73a45b90 : ffffca03`757e4000 ffffca03`717bb000 ffffca03`7228c590 ffffca03`717b5203 : nvlddmkm+0x731750

    fffff18c`e2e0d420 fffff800`73a46b8f : 00000000`00000000 ffffca03`757e4000 ffffca03`74aee500 ffffca03`6ab72000 : nvlddmkm+0x6c5b90

    fffff18c`e2e0d4f0 fffff800`7397b27e : 00000000`00000000 fffff18c`e2e0d5c0 fffff18c`e2e0d6a0 ffffca03`717bb000 : nvlddmkm+0x6c6b8f

    fffff18c`e2e0d550 fffff800`7397aaf5 : ffffca03`74a81010 fffff18c`e2e0d650 00000000`000000c4 00000003`00000003 : nvlddmkm+0x5fb27e

    fffff18c`e2e0d600 fffff800`7397c265 : ffffca03`79bd19b0 fffff18c`e2e0d6f0 00000000`0000001b 00000000`00000000 : nvlddmkm+0x5faaf5

    fffff18c`e2e0d680 fffff800`7397d453 : ffffca03`79bd1903 ffffca03`6ab72000 ffffca03`79bd19b0 fffff18c`e2e0d8c8 : nvlddmkm+0x5fc265

    fffff18c`e2e0d730 fffff800`7398765a : ffffca03`79bd19b0 00000000`00000000 ffffca03`6fe5d000 fffff18c`e2e0d8c8 : nvlddmkm+0x5fd453

    fffff18c`e2e0d7b0 fffff800`73987900 : 00000000`00000006 ffffca03`6fe5deec ffffca03`00000000 fffff800`7359a57d : nvlddmkm+0x60765a

    fffff18c`e2e0d850 fffff800`7390c713 : 00000000`00000000 ffffca03`757e4000 00000000`00000000 ffffca03`6ab72000 : nvlddmkm+0x607900

    fffff18c`e2e0d970 fffff800`7355a2c5 : ffffca03`888376a0 ffffca03`6ac8e030 ffffca03`00000001 ffffca03`71257080 : nvlddmkm+0x58c713

    fffff18c`e2e0d9b0 fffff800`64d7c9bb : ffffca03`81745b50 ffffca03`81745b50 ffffca03`6ac8e030 00000000`00000000 : nvlddmkm+0x1da2c5

    fffff18c`e2e0da80 fffff800`64d0611a : ffffca03`6867da10 ffffca03`7a317280 fffff800`64d7c930 ffffb781`00000000 : nt!IopProcessWorkItem+0x8b

    fffff18c`e2e0daf0 fffff800`64dca6c5 : ffffca03`7a317280 ffffca03`6865f300 ffffca03`7a317280 00000000`00000000 : nt!ExpWorkerThread+0x16a

    fffff18c`e2e0db90 fffff800`64e6149c : ffffb781`46f6d180 ffffca03`7a317280 fffff800`64dca670 00000000`00000246 : nt!PspSystemThreadStartup+0x55

    fffff18c`e2e0dbe0 00000000`00000000 : fffff18c`e2e0e000 fffff18c`e2e07000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c





    THREAD_SHA1_HASH_MOD_FUNC: 654b467902ade4aa6b7b65436773a74661d2b8f5



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 16c961e8b346bbe1d1cf9d8ef79d653fa0345eb1



    THREAD_SHA1_HASH_MOD: f92918c120da9a632e68738c223b0c622ae2dcba



    FOLLOWUP_IP:

    nt!KeAccumulateTicks+187837

    fffff800`64eac8f7 cc int 3



    FAULT_INSTR_CODE: ab3944cc



    SYMBOL_STACK_INDEX: 1



    SYMBOL_NAME: nt!KeAccumulateTicks+187837



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    DEBUG_FLR_IMAGE_TIMESTAMP: 3eeaaca9



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 187837



    FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks



    BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks



    PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks



    TARGET_TIME: 2018-12-03T16:30:29.000Z



    OSBUILD: 17763



    OSSERVICEPACK: 0



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: 2003-06-14 13:03:37



    BUILDDATESTAMP_STR: 180914-1434



    BUILDLAB_STR: rs5_release



    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



    ANALYSIS_SESSION_ELAPSED_TIME: 34a0



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks



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



    Followup: MachineOwner

    ---------

    :)
     
    易心, Dec 3, 2018
    #1

  2. Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

    Check (enable) it then do Step #5 & test.

    The above notwithstanding...

    Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?
     
    PA Bear - MS MVP, Dec 3, 2018
    #2
  3. BSOD with DPC_WATCHDOG_VIOLATION

    Hi,

    Thank you for contacting Microsoft community.

    I suggest you to follow the below article regarding BSOD error and check if it helps.

    DPC_WATCHDOG_VIOLATION

    Bluescreen Error: DPC_WATCHDOG_VIOLATION

    Hope this information was helpful and do let us know if you need further assistance. We will be glad to assist.
     
    Karthicka_R, Dec 3, 2018
    #3
  4. Allan Mej Win User

    BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks

    DPC_Watchdog_Violation

    Hi,

    In most cases, faulty drivers are the reason why DPC_Watchdog_Violation BSOD occurs. To further assist your issue, kindly answer these following questions:

    • What are the specifications of your PC?
    • Is your PC up-to-date?
    • Have you made any changes to your PC prior to the issue?

    We'll be looking forward for your reply.

    Regards.
     
    Allan Mej, Dec 3, 2018
    #4
Thema:

BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks

Loading...
  1. BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks - Similar Threads - BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt

  2. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 BSOD Crashes and Debugging
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: I fromated my disks, reinstalled fresh copy of Windows 10 and every time is same problem. All drivers are installed and up to date. Specification: Microsoft Windows 10 Home Motherboard B450 AORUS PRO Procesor AMD Ryzen 5 5600G with Radeon Graphics, 3901 MHzRAM: 32GB 4slotsSSD...
  3. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 BSOD Crashes and Debugging
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: While playing games, and doing a cinebench throttling test: I get a BSOD I use Windbg to analyze:Microsoft R Windows Debugger Version 10.0.22473.1005 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\121821-5750-01.dmp]Mini...
  4. BSOD - DPC_WATCHDOG_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    BSOD - DPC_WATCHDOG_VIOLATION: I've been having this BSOD randomly, like about 5-6 times a day. I had noticed my Windows Defender, and BitDefender antivirus had been suspiciously uninstalled, as well as Windows Update services had been deleted somehow. I reinstalled the Update service using registry keys...
  5. BSOD DPC_Watchdog_Violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_Watchdog_Violation: This is the 4th time in a row Below is obtained from BlueScreenView Code: ================================================== Dump File : 100219-34359-01.dmp Crash Time : 02-10-2019 11:14:48 Bug Check String : Bug Check Code : 0x00000133 Parameter 1 : 00000000`00000000...
  6. Bsod: Dpc_watchdog_violation

    in Windows 10 BSOD Crashes and Debugging
    Bsod: Dpc_watchdog_violation: I have started to get the above BSOD frequently when I am using my computer. When I let it idle, it's fine, even for hours at a time. When I actively use it, however, it will BSOD at random intervals (~10-15 minutes after startup to about 90 minutes or so afterward). I have...
  7. Bsod dpc_watchdog_violation

    in Windows 10 BSOD Crashes and Debugging
    Bsod dpc_watchdog_violation: Hello I get a Blue screen of death error maybe once or twice a day, it is labeled as DPC_WATCHDOG_VIOLATION. I've ran some minidump file analyzers and one said it was my razer mouse software, so I updated it, restarted the computer, and got the BSOD again. Here is all the...
  8. BSOD dpc_watchdog_violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD dpc_watchdog_violation: Hello I'm having issues with Win10, i'm experiencing this BSOD, it has happened twice now randomly. The last software change I did was to update my video from this "amd-catalyst-15.7.1-win10-64bit", to this one "radeon-crimson-16.3.2-win10-64bit". BEfore the driver...
  9. BSOD DPC_Watchdog_Violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_Watchdog_Violation: Blue screen of death randomly happens saying to look up DPC_Watchdog_Violation. Have searched the internet for solutions and thus far have not found a fix that works. Solutions I have tried are: Update drivers, if it's a driver issue I can't find it Turn off quick start...
  10. BSOD with DPC_WATCHDOG_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    BSOD with DPC_WATCHDOG_VIOLATION: Hi Please can you tell me how to debug using the attached debug files! And tell me what the error is! Dell XPS 730 Quad Core Extreme @ 3.0GHz, dual GTX560 Graphics, 8Gb Crucial Memory Thanks 33813

Users found this page by searching for:

  1. 0x133_isr_nt!keaccumulateticks

    ,
  2. bucket id: 0x133_isr_nt!kxflushentiretb

    ,
  3. nt!KeAccumulateTicks

    ,
  4. nt!KeBugCheckEx: fffff803`5d7c1410 48894c2408,
  5. 0x133_DPC_nt!KeAccumulateTicks,
  6. KeAccumulateTicks,
  7. nt!KeAccumulateTicks,
  8. 0x133_ISR_nt!KeAccumulateTicks],
  9. FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks