Windows 10: FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

Euler Lym · Apr 29, 2024

Microsoft R Windows Debugger Version 10.0.27553.1004 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\043024-13359-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSKernel base

:)

AbolfazlSeyed · Apr 29, 2024

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. =)

WelcomeCar22539 · Apr 29, 2024

FAILURE_BUCKET_ID: 0x133_OUT_OF_SYNC_PROCESSOR_nt!KeAccumulateTicks

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

Loading Dump File [D:\112222-17093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`25e00000 PsLoadedModuleList = 0xfffff804`26a29a40
Debug session time: Tue Nov 22 22:09:48.511 2022 (UTC + 8:00)
System Uptime: 9 days 0:19:16.641
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`2621af80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcf00`751fe9f0=0000000000000133
10: 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: fffff80426b05330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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 ***
*** ***
*************************************************************************
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
*** WARNING: Unable to verify checksum for win32k.sys
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138
Unable to read KTHREAD address ffff95022a0d2138

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2062

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 15533

Key : Analysis.IO.Other.Mb
Value: 19

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 33

Key : Analysis.Init.CPU.mSec
Value: 546

Key : Analysis.Init.Elapsed.mSec
Value: 29340

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

Key : Bugcheck.Code.DumpHeader
Value: 0x133

Key : Bugcheck.Code.KiBugCheckData
Value: 0x133

Key : Bugcheck.Code.Register
Value: 0x133

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: 112222-17093-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80426b05330

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TAG_NOT_DEFINED_c000000a: *** Unknown TAG in analysis list c000000a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

FAULTING_THREAD: 0000000000000002

STACK_TEXT:
ffffcf00`74b1d630 fffff804`2621b087 : ffffcf00`74b1dde0 00000000`00000004 ffffcf00`74b02180 00000000`00000004 : nt!KeBugCheck2+0xd03
ffffcf00`74b1dda0 fffff804`26031a1e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx+0x107
ffffcf00`74b1dde0 fffff804`260314a1 : 00029e42`142e67a2 ffffcf00`00000500 00000000`00000002 fffff804`2602cc2e : nt!KeAccumulateTicks+0x39e
ffffcf00`74b1de50 fffff804`2602f68a : ffffcf00`74b0b200 fffff182`aee478f0 ffffcf00`74b0b2c0 fffff804`2611ed8b : nt!KiUpdateRunTime+0x61
ffffcf00`74b1deb0 fffff804`2602f476 : ffff9502`0392e0e0 ffff9502`0392e190 00000079`00000002 00007ffe`a1215000 : nt!KeClockInterruptNotify+0x11a
ffffcf00`74b1df40 fffff804`26014600 : ffff9502`0392e0e0 fffff804`26075bdc 00000079`00000000 00000000`000000e2 : nt!HalpTimerClockIpiRoutine+0x16
ffffcf00`74b1df70 fffff804`2621d0ca : fffff182`aee47970 ffff9502`0392e0e0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffffcf00`74b1dfb0 fffff804`2621d937 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff182`aee478f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

STACK_COMMAND: ~2 ; .cxr ; kb

SYMBOL_NAME: nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22000.1219

BUCKET_ID_FUNC_OFFSET: 39e

FAILURE_BUCKET_ID: 0x133_OUT_OF_SYNC_PROCESSOR_nt!KeAccumulateTicks

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c6929bd4-963e-1e8f-1d38-6ff304808cd5}

Followup: MachineOwner
---------
Click to expand...

Punknavy777 · Apr 29, 2024

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 AMD64
Copyright (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 available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`1b000000 PsLoadedModuleList = 0xfffff800`1bc2a2d0
Debug session time: Fri Dec 17 20:04:04.930 2021 (UTC - 6:00)
System Uptime: 0 days 0:00:18.588
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`1b3f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd501`5ae7fc90=0000000000000101
8: 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: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd5015b05c180, The PRCB address of the hung processor.
Arg4: 000000000000000b, The index of the hung processor.

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2312

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 41000

Key : Analysis.Init.CPU.mSec
Value: 811

Key : Analysis.Init.Elapsed.mSec
Value: 51637

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 121821-5750-01.dmp

BUGCHECK_CODE: 101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd5015b05c180

BUGCHECK_P4: b

FAULTING_PROCESSOR: b

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd501`5ae7fc88 fffff800`1b41f56e : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffd501`5b05c180 : nt!KeBugCheckEx
ffffd501`5ae7fc90 fffff800`1b21c3cd : 00000000`00000000 ffffd501`5adeb180 00000000`00000246 00000000`000004a5 : nt!KeAccumulateTicks+0x2063be
ffffd501`5ae7fcf0 fffff800`1b21c971 : 00000000`00000200 00000000`000002c5 ffffd501`5adeb180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffd501`5ae7fd40 fffff800`1b2167e3 : ffffd501`5adeb180 00000000`00000000 fffff800`1bc315b8 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffd501`5ae7fe80 fffff800`1b21f1a2 : ffff878e`6e7c9640 ffff878e`6e7c96c0 ffff878e`6e7c9600 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffd501`5ae7ff30 fffff800`1b2de055 : 00000000`0b2b5555 ffffb08a`d62e8c40 ffffb08a`d62e8cf0 ffff128a`ec03462e : nt!HalpTimerClockInterrupt+0xe2
ffffd501`5ae7ff60 fffff800`1b3f8d4a : ffff878e`6e7c96c0 ffffb08a`d62e8c40 ffff8540`944e2ad8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd501`5ae7ffb0 fffff800`1b3f92b7 : 00000000`12ffec73 ffffd501`5adeb180 00000000`00000002 ffffd501`5adee130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff878e`6e7c9640 fffff800`1b23a300 : ffffd501`5c073100 00000000`00000001 00000000`00000001 ffff8540`944e2ad0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff878e`6e7c97d0 fffff800`1b47aa62 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiSendRequestEx+0xb0
ffff878e`6e7c9810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushNonGlobalTb+0x13a49e

SYMBOL_NAME: nt!KeAccumulateTicks+2063be

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1348

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2063be

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
Click to expand...

Windows 10: FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks - Similar Threads - FAILURE_BUCKET_ID 0x133_DPC_nt KeAccumulateTicks

how to fix FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks crash windows ? DISPATCH_LEVEL

how to fix FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks crash windows ? DISPATCH_LEVEL

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

FAILURE_BUCKET_ID: 0x133_OUT_OF_SYNC_PROCESSOR_nt!KeAccumulateTicks

FAILURE_BUCKET_ID: 0x133_OUT_OF_SYNC_PROCESSOR_nt!KeAccumulateTicks

CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks

CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumu lateTicks