最近电脑蓝屏，0x133_DPC_nt!KeAccumulateTicks

Question

最近电脑蓝屏，0x133_DPC_nt!KeAccumulateTicks

lostworks 0

For analysis of this file, run !analyze -v

2: 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: 0000000000000500, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: fffff806c5bc43b0, 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 ***

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 1937

Key  : Analysis.Elapsed.mSec

Value: 3157

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 0

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 1218

Key  : Analysis.Init.Elapsed.mSec

Value: 10371

Key  : Analysis.Memory.CommitPeak.Mb

Value: 100

Key  : Bugcheck.Code.LegacyAPI

Value: 0x133

Key  : Dump.Attributes.AsUlong

Value: 21008

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_DPC_nt!KeAccumulateTicks

Key  : Failure.Hash

Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 500

BUGCHECK_P3: 500

BUGCHECK_P4: fffff806c5bc43b0

FILE_IN_CAB: 030126-7281-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008

Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: TS4_x64.exe

FAULTING_THREAD: 000000000000001f

STACK_TEXT:

ffffd300e1eb4c08 fffff806c4ec248c : 0000000000000133 0000000000000000 0000000000000500 0000000000000500 : nt!KeBugCheckEx

ffffd300e1eb4c10 fffff806c4ec19bb : fffff806c5bc43b0 00000000001d4e90 0000000000000000 ffffd300e1e98180 : nt!KeAccumulateTicks+0x59c

ffffd300e1eb4c80 fffff806c4f0f7ce : 0000000000000000 00000045df833574 ffffd300e1e98180 ffff870f8a839188 : nt!KiUpdateRunTime+0x9b

ffffd300e1eb4e40 fffff806c4f101cc : ffff870f86785200 ffff870f867852b0 fffff806c5b8eba0 0000000000000000 : nt!KeClockInterruptNotify+0x3ee

ffffd300e1eb4f40 fffff806c52a41fe : ffffe58415c76802 ffff870f86785200 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x32c

ffffd300e1eb4fb0 fffff806c52a4a0c : 0000000000000000 0000000000000001 0000000200001000 00000020c4f9189c : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e

ffffe5840e0678f0 fffff806c4ffa635 : 0000000000000000 0000000000000000 ffff76b4af63ab0c ffff870fb563f080 : nt!KiInterruptDispatchNoLockNoEtw+0x3c

ffffe5840e067a80 fffff806c4ed11f5 : 0000000000000000 ffffd300e1e98180 ffffe58415c768f0 0000000000000000 : nt!KiSwapDirectoryTableBaseTarget+0x55

ffffe5840e067ae0 fffff806c4ece04e : ffffe5840e067e20 ffff870fc2fb5100 ffffe5840e067e20 ffff870fb563f080 : nt!KiExecuteAllDpcs+0x675

ffffe5840e067d20 fffff806c52a9e05 : 0000000000000000 ffffd300e1e98180 ffff870fb563f080 0000000000173cdc : nt!KiRetireDpcList+0x43e

ffffe5840e067fb0 fffff806c52a9daf : ffffe584165df4e0 fffff806c4ebb865 00007ff417487390 0000000000000000 : nt!KxSwapStacksAndRetireDpcList+0x5

ffffe584165df420 fffff806c4ebb865 : 00007ff417487390 0000000000000000 0000000000000000 000000006daf0000 : nt!KiPlatformSwapStacksAndCallReturn

ffffe584165df430 fffff806c52a923f : 00000045d3e0c128 000000006c616fb8 000000006f28fb90 0000000000000028 : nt!KiDispatchInterrupt+0x65

ffffe584165df460 000000006e0aa416 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDpcInterrupt+0x39f

000000006f28f9f0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x6e0aa416

STACK_COMMAND: ~31 ; .cxr ; kb

SYMBOL_NAME: nt!KeAccumulateTicks+59c

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.7462

BUCKET_ID_FUNC_OFFSET: 59c

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup: MachineOwner

2: kd> !process 0 0 TS4_x64.exe

Unable to read _LIST_ENTRY @ fffff806c5b056f0

2 个答案

你的答案

Answer 1

Jason Nguyen Tran 12,250 独立顾问

您好，

我想跟进确认一下该问题是否已经解决。如果之前提供的信息对您有所帮助，请点击 “接受答案”，以便帮助社区中的其他用户。谢谢！

Answer 2

您好，

您看到的错误 DPC_WATCHDOG_VIOLATION (133) 通常表示某个驱动程序或硬件组件在高优先级中断级别下响应时间过长。实际情况下，这类问题通常由过时的存储驱动程序（如 SATA/AHCI 或 NVMe）、显卡驱动程序，或某些防病毒/安全软件干扰内核操作引起。由于您的转储文件中显示的进程名称为 TS4_x64.exe，看起来崩溃发生在运行《The Sims 4》期间，这表明问题可能与 GPU 或存储子系统有关。

我建议您尝试以下步骤：

直接从 NVIDIA/AMD/Intel 官网更新显卡驱动程序（不要仅通过 Windows Update）。
更新存储控制器驱动程序（如 Intel Rapid Storage 或标准 AHCI/NVMe 驱动）。
检查 SSD 是否有固件更新，因为过时的固件可能会触发 watchdog 错误。
暂时禁用或卸载第三方防病毒/安全软件，以排除干扰的可能性。
如果问题仍然存在，请再次运行 chkdsk /f 和 sfc /scannow 以确认系统没有损坏，并收集新的转储文件以便进一步分析。

希望这些步骤能帮助您解决问题。如果您觉得此回答有帮助，请考虑点击“接受答案”，以便其他人也能从中受益 🙂。

Jason.

通过

最近电脑蓝屏，0x133_DPC_nt!KeAccumulateTicks

2 个答案

你的答案