Windows 10: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

Discus and support CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks in Windows 10 Gaming to solve the problem; 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... Discussion in 'Windows 10 Gaming' started by Punknavy777, Dec 18, 2021.

  1. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks


    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 Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name

    :)
     
    Punknavy777, Dec 18, 2021
    #1
  2. 易心 Win User

    BSOD DPC_WATCHDOG_VIOLATION 0x133_isr_nt!keaccumulateticks

    I get BSOD, I get debug details use winDbg

    Code:
    
    Microsoft (R) Windows Debugger Version 10.0.18272.1001 AMD64Copyright (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)     LocationDeferred                                       srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 17763 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 17763.1.amd64fre.rs5_release.180914-1434Machine Name:Kernel base = 0xfffff800`64ca9000 PsLoadedModuleList = 0xfffff800`650c8990Debug session time: Tue Dec  4 00:30:29.407 2018 (UTC + 8:00)System Uptime: 1 days 6:57:15.203Loading Kernel Symbols.....................................................................................................................................................................................................Loading User Symbols
    
    Loading unloaded module list.............................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`64e5a040 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`64a179b0=00000000000001330: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************
    
    DPC_WATCHDOG_VIOLATION (133)The 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 atDISPATCH_LEVEL or above. The offending component can usually beidentified with a stack trace.Arg2: 0000000000001e00, The watchdog period.Arg3: fffff8006516d380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which containsadditional information regarding the cumulative timeoutArg4: 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!KeBugCheckExfffff800`64a179b0 fffff800`64d21f84 : 0000ed6b`9d66fd8b 00000000`00000000 00000000`006cd2cd fffff800`635cf180 : nt!KeAccumulateTicks+0x187837fffff800`64a17a10 fffff800`64c13332 : 00000000`00000000 fffff800`64c77b30 fffff800`64a17e80 00000000`00000003 : nt!KeClockInterruptNotify+0x604fffff800`64a17d30 fffff800`64d8ca15 : 00000103`7706cd07 fffff800`64c7a7e0 fffff800`64c7a890 fffff800`64a17e80 : hal!HalpTimerClockInterrupt+0xf2fffff800`64a17d60 fffff800`64e5ba3a : fffff800`64a17e80 fffff800`64c7a7e0 ffffca03`7228c500 fffff800`64c14ae6 : nt!KiCallInterruptServiceRoutine+0xa5fffff800`64a17db0 fffff800`64e5bf87 : 00000000`00000001 00000000`ffffffff 00000000`00000024 00000000`00400a02 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff800`64a17e00 fffff800`64e5fa76 : fffff800`635cf180 00000000`00000000 fffff18c`e2e0cd50 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff800`64a17f90 fffff800`64e5f5f7 : fffff800`635cf180 fffff18c`e2e0cd50 ffffb781`46cb8140 fffff800`73582395 : nt!KiVmbusInterruptSubDispatch+0xd6fffff18c`e2e0ccd0 fffff800`64e60c98 : ffffb781`46cb8140 fffff800`64c14ae6 ffffca03`6f67ce90 fffff800`7390b337 : nt!KiVmbusInterruptDispatch+0x37fffff18c`e2e0ce60 fffff800`64e60555 : ffffca03`7228c590 fffff800`64e5b2f1 00000000`00000000 fffff18c`e2e0cf20 : nt!KiDispatchInterruptContinue+0x8fffff18c`e2e0ce90 fffff800`64e5b2f1 : 00000000`00000000 fffff18c`e2e0cf20 ffffb781`46cb8140 fffff18c`e2e0d05c : nt!KiDpcInterruptBypass+0x25fffff18c`e2e0cea0 fffff800`73a4596c : ffffca03`7228c590 fffff18c`e2e0d1e0 ffffca03`757e4000 fffff800`73a509b8 : nt!KiChainedDispatch+0xb1fffff18c`e2e0d030 fffff800`73a46a25 : 00000000`00000000 ffffca03`757e4000 ffffca03`74aee500 fffff18c`e2e0d1e0 : nvlddmkm+0x6c596cfffff18c`e2e0d090 fffff800`73a4679d : fffff18c`e2e0d1e0 ffffca03`717bb000 ffffca03`757e4000 ffffca03`74aee500 : nvlddmkm+0x6c6a25fffff18c`e2e0d0e0 fffff800`73a500e8 : 00000000`00000000 ffffca03`717bb000 ffffca03`736d9b00 fffff18c`e2e0d1e0 : nvlddmkm+0x6c679dfffff18c`e2e0d130 fffff800`73a50256 : 00000000`00000000 00000000`00000000 ffffca03`74aee501 ffffca03`736d9b00 : nvlddmkm+0x6d00e8fffff18c`e2e0d180 fffff800`73aa8ee7 : 00000000`00000eee fffff18c`e2e0d2b8 ffffca03`74aee500 ffffca03`757e401a : nvlddmkm+0x6d0256fffff18c`e2e0d1e0 fffff800`73aa8c0b : ffffca03`717bb000 00000000`00000000 fffff18c`e2e0d280 ffffca03`757e4000 : nvlddmkm+0x728ee7fffff18c`e2e0d250 fffff800`73a508cf : 00000000`00000000 00000000`00000000 00000802`757e4000 ffffca03`757e4000 : nvlddmkm+0x728c0bfffff18c`e2e0d2b0 fffff800`73ab1c7d : 00000000`00000000 ffffca03`68b8dd60 ffffca03`757e4000 fffff18c`e2e0d401 : nvlddmkm+0x6d08cffffff18c`e2e0d310 fffff800`73ab1750 : 000a1be4`72280802 fffff18c`e2e0d5a0 fffff18c`e2e0d4f0 ffffca03`6ab72000 : nvlddmkm+0x731c7dfffff18c`e2e0d380 fffff800`73a45b90 : ffffca03`757e4000 ffffca03`717bb000 ffffca03`7228c590 ffffca03`717b5203 : nvlddmkm+0x731750fffff18c`e2e0d420 fffff800`73a46b8f : 00000000`00000000 ffffca03`757e4000 ffffca03`74aee500 ffffca03`6ab72000 : nvlddmkm+0x6c5b90fffff18c`e2e0d4f0 fffff800`7397b27e : 00000000`00000000 fffff18c`e2e0d5c0 fffff18c`e2e0d6a0 ffffca03`717bb000 : nvlddmkm+0x6c6b8ffffff18c`e2e0d550 fffff800`7397aaf5 : ffffca03`74a81010 fffff18c`e2e0d650 00000000`000000c4 00000003`00000003 : nvlddmkm+0x5fb27efffff18c`e2e0d600 fffff800`7397c265 : ffffca03`79bd19b0 fffff18c`e2e0d6f0 00000000`0000001b 00000000`00000000 : nvlddmkm+0x5faaf5fffff18c`e2e0d680 fffff800`7397d453 : ffffca03`79bd1903 ffffca03`6ab72000 ffffca03`79bd19b0 fffff18c`e2e0d8c8 : nvlddmkm+0x5fc265fffff18c`e2e0d730 fffff800`7398765a : ffffca03`79bd19b0 00000000`00000000 ffffca03`6fe5d000 fffff18c`e2e0d8c8 : nvlddmkm+0x5fd453fffff18c`e2e0d7b0 fffff800`73987900 : 00000000`00000006 ffffca03`6fe5deec ffffca03`00000000 fffff800`7359a57d : nvlddmkm+0x60765afffff18c`e2e0d850 fffff800`7390c713 : 00000000`00000000 ffffca03`757e4000 00000000`00000000 ffffca03`6ab72000 : nvlddmkm+0x607900fffff18c`e2e0d970 fffff800`7355a2c5 : ffffca03`888376a0 ffffca03`6ac8e030 ffffca03`00000001 ffffca03`71257080 : nvlddmkm+0x58c713fffff18c`e2e0d9b0 fffff800`64d7c9bb : ffffca03`81745b50 ffffca03`81745b50 ffffca03`6ac8e030 00000000`00000000 : nvlddmkm+0x1da2c5fffff18c`e2e0da80 fffff800`64d0611a : ffffca03`6867da10 ffffca03`7a317280 fffff800`64d7c930 ffffb781`00000000 : nt!IopProcessWorkItem+0x8bfffff18c`e2e0daf0 fffff800`64dca6c5 : ffffca03`7a317280 ffffca03`6865f300 ffffca03`7a317280 00000000`00000000 : nt!ExpWorkerThread+0x16afffff18c`e2e0db90 fffff800`64e6149c : ffffb781`46f6d180 ffffca03`7a317280 fffff800`64dca670 00000000`00000246 : nt!PspSystemThreadStartup+0x55fffff18c`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+187837fffff800`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---------
    
    DMP file: [url]https://drive.google.com/open?id=1Ws7LaOBdpar1xV4UKdik7RAQ05eCd6dl[/url]
    
    may be related to NVIDIA, I have created a topic in their forum, 
    {{MetaTags.og.title}}
     
    易心, Dec 18, 2021
    #2
  3. Fault bucket 0x133_DPC_nt!KeAccumulateTicks, type 0

    Hi,

    My computer goes to bluescreen and shutting down suddenly.

    Is there anyone had the same problem as me before?

    Please give me a solution for that

    Fault bucket 0x133_DPC_nt!KeAccumulateTicks, type 0

    Event Name: BlueScreen

    Response: Not available

    Cab Id: d5f983fc-cc08-46ae-95d9-e02669ebd6fc

    Problem signature:

    P1: 133

    P2: 0

    P3: 501

    P4: 500

    P5: fffff801a27ef348

    P6: 10_0_15063

    P7: 0_0

    P8: 256_1

    P9:

    P10:




    Thank you in advance. =)
     
    AbolfazlSeyed, Dec 18, 2021
    #3
  4. Ychaai Win User

    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

    CLOCK_WATCHDOG_TIMEOUT

    Any help would be greatly appreciated. Thanks in advance.This is the report:

    Microsoft (R) Windows Debugger Version 10.0.18869.1002 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\qty94\Downloads\061019-37921-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 18362 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff800`83a00000 PsLoadedModuleList = 0xfffff800`83e432b0
    Debug session time: Mon Jun 10 00:53:14.914 2019 (UTC + 8:00)
    System Uptime: 0 days 1:08:40.047
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff800`83bbc8a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`87689b00=0000000000000101
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffff9680abd79180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, The index of the hung processor.

    Debugging Details:
    ------------------

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 9

    Key : Analysis.Elapsed.Sec
    Value: 23

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 69

    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

    SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

    SYSTEM_SKU: To Be Filled By O.E.M.

    SYSTEM_VERSION: To Be Filled By O.E.M.

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: P1.40

    BIOS_DATE: 05/21/2012

    BASEBOARD_MANUFACTURER: ASRock

    BASEBOARD_PRODUCT: A55iCafe

    BASEBOARD_VERSION:

    DUMP_TYPE: 2

    BUGCHECK_P1: 30

    BUGCHECK_P2: 0

    BUGCHECK_P3: ffff9680abd79180

    BUGCHECK_P4: 2

    BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

    FAULTING_PROCESSOR: 2

    PROCESS_NAME: Steam.exe

    CPU_COUNT: 4

    CPU_MHZ: aeb

    CPU_VENDOR: AuthenticAMD

    CPU_FAMILY: 12

    CPU_MODEL: 1

    CPU_STEPPING: 0

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST: DESKTOP-PR5VP4U

    ANALYSIS_SESSION_TIME: 06-11-2019 05:01:52.0422

    ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80083bebb22 to fffff80083bbc8a0

    STACK_TEXT:
    fffff800`87689af8 fffff800`83bebb22 : 00000000`00000101 00000000`00000030 00000000`00000000 ffff9680`abd79180 : nt!KeBugCheckEx
    fffff800`87689b00 fffff800`83a1f764 : 00000000`00000000 00000000`00000000 00000000`00040603 fffff800`7fc26180 : nt!KeAccumulateTicks+0x1c9262
    fffff800`87689b60 fffff800`8395e4b2 : 00000000`00000000 ffffba8c`f02a6c30 ffffba8c`f02a6cb0 00000000`0000000c : nt!KeClockInterruptNotify+0x6c4
    fffff800`87689f30 fffff800`83a02e15 : 00000009`97d2aa4a fffff800`839cbcf0 fffff800`839cbda0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf2
    fffff800`87689f60 fffff800`83bbe30a : ffffba8c`f02a6cb0 fffff800`839cbcf0 00000000`00000001 fffff800`839cbcf0 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff800`87689fb0 fffff800`83bbe857 : 00000000`92483016 ffffba8c`f02a6cb0 fffff800`839cbcf0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    ffffba8c`f02a6c30 fffff800`83abaea0 : 00000000`00000000 fffff800`7fc26180 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffffba8c`f02a6dc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0

    THREAD_SHA1_HASH_MOD_FUNC: dc8736af616fc8dbbe5744546b76f6197d522250

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f83251215b5c77f255c4ca8bb5458675110e916d

    THREAD_SHA1_HASH_MOD: 77b99fd8d0bba6459fea0474c255a54ffe46d91a

    FOLLOWUP_IP:
    nt!KeAccumulateTicks+1c9262
    fffff800`83bebb22 cc int 3

    FAULT_INSTR_CODE: cb8b48cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KeAccumulateTicks+1c9262

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.18362.145

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1c9262

    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

    BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

    PRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

    TARGET_TIME: 2019-06-09T16:53:14.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 145

    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: unknown_date

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

    ANALYSIS_SESSION_ELAPSED_TIME: 5b1a

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

    FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

    Followup: MachineOwner
    ---------
     
    Ychaai, Dec 18, 2021
    #4
Thema:

CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

Loading...
  1. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks - Similar Threads - CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt KeAccumulateTicks

  2. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Gaming
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true...
  3. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Software and Apps
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true...
  4. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Gaming
    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...
  5. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Software and Apps
    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...
  6. 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...
  7. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Gaming
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path...
  8. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Software and Apps
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path...
  9. CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

    in Windows 10 Drivers and Hardware
    CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path...
  10. 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...