dump文件：https://www.123pan.com/s/NxOUVv-U4Bld提取码:lDOw日志分析如下：Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\120922-9593-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 22000 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff803`6d000000 PsLoadedModuleList = 0xfffff803`6dc29a40 Debug session time: Fri Dec 9 17:56:49.303 2022 (UTC 8:00) System Uptime: 0 days 0:03:18.250 Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................................ .................. Loading User Symbols Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`6d41af80 48894c2408 mov qword ptr [rsp 8],rcx ss:ffffcb80`2817a9f0=0000000000000133 4: 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: fffff8036dd05330, 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: 2453 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 6414 Key : Analysis.IO.Other.Mb Value: 15 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 30 Key : Analysis.Init.CPU.mSec Value: 921 Key : Analysis.Init.Elapsed.mSec Value: 70128 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1008 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 FILE_IN_CAB: 120922-9593-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8036dd05330 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: crossfire.exe FAULTING_THREAD: 000000000000000b STACK_TEXT: ffffcb80`2817a9e8 fffff803`6d231a1e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffcb80`2817a9f0 fffff803`6d2314a1 : 0000007b`f3e4e3fa ffffcb80`00000500 00000000`00000297 fffff803`6d39ba05 : nt!KeAccumulateTicks 0x39e ffffcb80`2817aa60 fffff803`6d22e4d6 : 00000000`00003190 00000000`00001d8a 00000000`762a8f36 00000000`00000000 : nt!KiUpdateRunTime 0x61 ffffcb80`2817aac0 fffff803`6d22f7e2 : ffffba0f`37e678f0 00000000`00000000 fffff803`6dc2b568 00000000`00000000 : nt!KiUpdateTime 0x686 ffffcb80`2817aeb0 fffff803`6d22d112 : ffffba0f`37e678f0 ffff820d`09d30b70 ffff820d`00000000 00000000`00000002 : nt!KeClockInterruptNotify 0x272 ffffcb80`2817af40 fffff803`6d214600 : 00000000`76426dd6 ffff820d`09d30ac0 00000000`00000001 fffff803`6d41ce6b : nt!HalpTimerClockInterrupt 0xe2 ffffcb80`2817af70 fffff803`6d41d0ca : ffffba0f`37e67970 ffff820d`09d30ac0 0000006f`df764f42 ffffcb80`28116fe0 : nt!KiCallInterruptServiceRoutine 0xa0 ffffcb80`2817afb0 fffff803`6d41d937 : 00000000`00000000 00000000`00000000 ffffba0f`38921f00 fffff803`6d41d944 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffba0f`37e678f0 fffff803`6d218acc : ffffffff`ffffffd1 fffff803`6d218900 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffba0f`37e67a80 fffff803`6d218913 : 00000000`00000001 ffffcb80`28440190 ffff302f`baaf7597 ffffcb80`282ad180 : nt!KeYieldProcessorEx 0x1c ffffba0f`37e67ab0 fffff803`6d2215e1 : ffffba0f`37e67e70 fffff803`130b97c5 00000000`00000000 ffffcb80`2810f180 : nt!KiSwapDirectoryTableBaseTarget 0x53 ffffba0f`37e67b00 fffff803`6d2205e2 : ffffcb80`2810f180 00000000`0000000f 00000000`6a399fc3 00000000`00001aa7 : nt!KiExecuteAllDpcs 0x491 ffffba0f`37e67d00 fffff803`6d4244e5 : 00000000`00000000 ffffcb80`2810f180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList 0x2a2 ffffba0f`37e67fb0 fffff803`6d4242c0 : 00000000`000003fe 00000000`00403000 00000001`013e0000 00000000`00000000 : nt!KxRetireDpcList 0x5 ffffba0f`3d8a79b0 fffff803`6d423652 : ffff820d`1661b080 00000000`26d4a150 00000000`00000000 00000001`0491005c : nt!KiDispatchInterruptContinue ffffba0f`3d8a79e0 00007ff8`49f9b875 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt 0x332 00000000`5df7f4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`49f9b875 STACK_COMMAND: ~11 ; .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_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner ---------
您提供的信息显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
您提供的信息显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
在今天玩游戏过程中电脑蓝屏并且一直继续重启后也无效，蓝屏时候显示电脑终止码：DPCWATCHDOGVIOLATION此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
