Share via

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

Sinan AKYAZICI 0 Reputation points
2024-11-30T19:04:15.76+00:00

Hi,

My windows is getting crashed, i have dump files and bsod. can you help me ?

https://drive.google.com/file/d/1JxDP1a13bAfEImjhGDPfNtQJtDvlARBO/view?usp=sharing

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.156 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Users\sinan\Desktop\crash dumps\113024-7890-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 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`1d400000 PsLoadedModuleList = 0xfffff801`1e0134f0
Debug session time: Sat Nov 30 21:34:48.161 2024 (UTC + 3:00)
System Uptime: 0 days 5:26:54.813
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`1d814fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa581`11b749f0=0000000000000133
11: 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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8011e11d340, 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

    Key  : Analysis.CPU.mSec
    Value: 1062

    Key  : Analysis.Elapsed.mSec
    Value: 1708

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8011e11d340

BUGCHECK_P4: 0

FILE_IN_CAB:  113024-7890-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe30f4af75080

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffa581`11b749e8 fffff801`1d639779     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`1e11d340 : nt!KeBugCheckEx
ffffa581`11b749f0 fffff801`1d638fe1     : 0000403f`cc798cb6 ffffa581`11bc0180 00000000`001327b3 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffffa581`11b74a50 fffff801`1d6366bf     : 00000000`00000014 00000000`00001388 00000000`00132700 00000000`000b6ad5 : nt!KiUpdateRunTime+0xd1
ffffa581`11b74c00 fffff801`1d6371d8     : 00000000`00000000 00000000`00000000 ffffa581`11bc0180 00000000`00000000 : nt!KiUpdateTime+0x63f
ffffa581`11b74ea0 fffff801`1d636b6a     : fffff801`1e05ffb0 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0x228
ffffa581`11b74f40 fffff801`1d715f9c     : 0000002d`ab5a0e94 ffffe30f`4af44160 ffffe30f`4af44210 ffffa581`11ce7180 : nt!HalpTimerClockInterrupt+0x10a
ffffa581`11b74f70 fffff801`1d8171aa     : ffffdf84`2f3370d0 ffffe30f`4af44160 ffffa581`11ce7180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffa581`11b74fb0 fffff801`1d817a77     : fffff7fd`c001b758 00000000`00002710 00000000`0000000f fffff801`1d817a84 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffdf84`2f337050 fffff801`1d6b942c     : ffffffff`ffffffd1 fffff801`1d72660f 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffdf84`2f3371e0 fffff801`1d72660b     : ffffa910`b37b5999 fffff801`1d858da7 ffffa910`b37b5a59 fffff801`1d858586 : nt!KeYieldProcessorEx+0x1c
ffffdf84`2f337210 fffff801`1d858a4a     : ffffa581`11ce7180 ffffdf84`d1c7c46f ffffa581`11ce7180 ffffdf84`2f3372d0 : nt!KiAcquirePrcbLocksForPreemptionAttempt+0xbb
ffffdf84`2f337260 fffff801`1d61a8f2     : ffffe30f`5446f080 ffffa581`11ce7180 00000000`000fffff ffffe30f`566d3080 : nt!KiHeteroChooseTargetProcessor+0x274
ffffdf84`2f337310 fffff801`1d610c24     : 00000000`00000000 ffffe30f`5b9f2158 00000000`00000000 00000000`00000000 : nt!KiDeferredReadySingleThread+0x742
ffffdf84`2f3376e0 fffff801`1d611ca3     : ffffe30f`0000001c 00000000`00000001 ffffdf84`00000000 00000000`00000002 : nt!KiProcessThreadWaitList+0x134
ffffdf84`2f337760 fffff801`1d612ed9     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`18331108 : nt!KiProcessExpiredTimerList+0x343
ffffdf84`2f337890 fffff801`1d819fae     : 00000000`00000000 ffffa581`11bc0180 ffffe30f`4af75080 ffffe30f`6fb7c080 : nt!KiRetireDpcList+0xaf9
ffffdf84`2f337b40 00000000`00000000     : ffffdf84`2f338000 ffffdf84`2f331000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+239

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4455

STACK_COMMAND:  .process /r /p 0xfffff8011e149f40; .thread 0xffffe30f4af75080 ; kb

BUCKET_ID_FUNC_OFFSET:  239

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-02T02:55:26.15+00:00

    Hello,

    If a driver is identified in the bug check message, to isolate the issue, disable the driver. Check with the manufacturer for driver updates.

    Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x133.

    Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, for Windows 10, you can get information about required hardware at Windows 10 Specifications.

    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

    Best Regards,

    Hania Lian

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.