关于NT错误导致的蓝屏代码clock watchdog timeout

Question

关于NT错误导致的蓝屏代码clock watchdog timeout

匿名

以下是dmp文件分析的结果

如有需要我可以提供dmp源文件

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories

  ----&gt; Repository : LocalInstalled, Enabled: true

  ----&gt; 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.047 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64

Loading Dump File [C:\Users\KiyoT\Desktop\031124-13578-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 22621 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff80159600000 PsLoadedModuleList = 0xfffff8015a213550

Debug session time: Mon Mar 11 05:43:35.888 2024 (UTC + 9:00)

System Uptime: 0 days 9:19:45.734

Loading Kernel Symbols

...............................................................

................................................................

...................

Loading User Symbols

PEB is paged out (Peb.Ldr = 00000000`00f27018). Type ".hh dbgerr001" for details

Loading unloaded module list

...............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff80159a16c30 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbb8037e579f0=0000000000000101

1: 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: ffffbb80381d1180, The PRCB address of the hung processor.

Arg4: 0000000000000007, The index of the hung processor.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 718

Key  : Analysis.Elapsed.mSec

Value: 4278

Key  : Analysis.IO.Other.Mb

Value: 23

Key  : Analysis.IO.Read.Mb

Value: 0

Key  : Analysis.IO.Write.Mb

Value: 31

Key  : Analysis.Init.CPU.mSec

Value: 296

Key  : Analysis.Init.Elapsed.mSec

Value: 21087

Key  : Analysis.Memory.CommitPeak.Mb

Value: 97

Key  : Bugcheck.Code.LegacyAPI

Value: 0x101

Key  : Bugcheck.Code.TargetModel

Value: 0x101

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

Key  : Failure.Bucket

Value: CLOCK\_WATCHDOG\_TIMEOUT\_nt!KeAccumulateTicks

Key  : Failure.Hash

Value: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffbb80381d1180

BUGCHECK_P4: 7

FILE_IN_CAB: 031124-13578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

FAULTING_PROCESSOR: 7

FAULTING_THREAD: ffffa908c6e62080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: ui32.exe

IP_IN_FREE_BLOCK: 0

STACK_TEXT:

ffffbb8037e579e8 fffff80159a70094 : 0000000000000101 0000000000000018 0000000000000000 ffffbb80381d1180 : nt!KeBugCheckEx

ffffbb8037e579f0 fffff80159812421 : fffff78000000000 ffffbb8037c9a180 000000000020cc6e 0000000000000000 : nt!KeAccumulateTicks+0x25d714

ffffbb8037e57a50 fffff8015980fa2f : 0000000000000008 0000000000001388 000000000020cc00 0000000000138caa : nt!KiUpdateRunTime+0xd1

ffffbb8037e57c00 fffff80159810618 : 0000000000000000 ffffbb803c5e3e00 ffffbb8037c9a180 0000000000000000 : nt!KiUpdateTime+0x63f

ffffbb8037e57ea0 fffff8015980feda : fffff8015a25fe68 ffffbb803c5e3e70 ffffbb803c5e3e70 000000000000000c : nt!KeClockInterruptNotify+0x228

ffffbb8037e57f40 fffff80159924cdc : 0000004e32bf61e7 ffffa908b4f3e5a0 ffffa908b4f3e650 0000000000000000 : nt!HalpTimerClockInterrupt+0x10a

ffffbb8037e57f70 fffff80159a18dea : fffff981d93be490 ffffa908b4f3e5a0 ffffbb8037c9a180 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c

ffffbb8037e57fb0 fffff80159a19697 : fffff981d93be490 ffffffffffffffff 0000000000000003 0000000011443e20 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff981d93be410 fffff80159837a6c : 00000001000000ff 0000000100000001 0000000000000001 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff981d93be5a0 fffff801599af82d : 0000000000000002 0000000000000002 0000000000000000 fffff98100000200 : nt!KiIpiSendRequestEx+0x7c

fffff981d93be5e0 fffff80159a3e679 : 0000000000000002 0000000000000004 0000000000000000 0000000000000000 : nt!KxFlushEntireTb+0xa1

fffff981d93be650 fffff8015996ee7e : ffff86801781b1a0 ffff97885769e000 0000000000000000 0000000000000000 : nt!KeFlushTb+0x1ee839

fffff981d93be6d0 fffff8015996dabc : ffff868000000000 0000000000000008 0000000000000000 fffff8015982a58f : nt!MiFlushEntireTbDueToAttributeChange+0x3a

fffff981d93be7c0 fffff80159868bd3 : ffff86801781b1a0 0000000000000001 0000000000000000 00000000007d5e5e : nt!MiChangePageAttribute+0x154

fffff981d93be810 fffff801598bc5fe : fffff8015a26afc0 fffff80100000006 fffff8015a26afc0 ffffdf8000000018 : nt!MiGetSlabPage+0x333

fffff981d93be8a0 fffff801598bc3f6 : 0000000000000000 0000000000000000 ffffdfef00000000 fffff981d93be970 : nt!MiGetPageTablePages+0xe6

fffff981d93be910 fffff8015988a6a6 : 0000000000000000 fffff981d93bedf0 ffffdfeffe006ed8 0000000000000000 : nt!MiCreateSystemPageTable+0x76

fffff981d93be970 fffff8015988aa6a : fffff981d93bedf0 fffff8015a269700 ffffdfef00000000 fffff981d93bee50 : nt!MiWalkPageTablesRecursively+0x266

fffff981d93bea00 fffff8015988aa6a : fffff981d93bedf0 fffff8015a269700 ffffdfef00000000 fffff981d93bee60 : nt!MiWalkPageTablesRecursively+0x62a

fffff981d93bea90 fffff8015988a341 : 0000000000000000 fffff8015a269700 ffffac7a00000000 fffff981d93bee70 : nt!MiWalkPageTablesRecursively+0x62a

fffff981d93beb20 fffff80159900b7f : fffff981d93bedf0 0000000000000001 fffff80100000002 0000000000000000 : nt!MiWalkPageTables+0x371

fffff981d93bec20 fffff801598fe4fd : 00000000001bb600 ffffdffc00ddb000 ffffa908d2f460d0 fffff801574164e9 : nt!MiMakeZeroedPageTablesEx+0x29f

fffff981d93bef00 fffff8015984d75c : 0000000000000040 0000000000000400 000000000001bb00 0000000000000001 : nt!MiExpandPtes+0x109

fffff981d93befa0 fffff80159900451 : 0000000000000040 00000000003f4000 fffff981d93bf1f0 0000000000000000 : nt!MiReservePtes+0x3bc

fffff981d93bf070 fffff80159d677ba : fffff981d93bf300 fffff981d93bf280 fffff981d93bf310 0000000000000001 : nt!MiInsertInSystemSpace+0x171

fffff981d93bf1f0 fffff80159d67652 : ffffa908d0d49dc0 fffff981d93bf2c0 00000000000003f4 0000000000000000 : nt!MiMapViewInSystemSpace+0xb2

fffff981d93bf250 fffff80159d1b070 : 0000000000000000 0000000000000002 0000000000000000 00000000003f4000 : nt!MiMapImageInSystemSpace+0x10a

fffff981d93bf300 fffff80159d0e8b3 : fffff981d93bf720 fffff981d93bf720 fffff981d93bf549 0000000000000002 : nt!MiParseComAndCetHeaders+0xbc

fffff981d93bf470 fffff80159d0d88a : ffffa908c9375370 fffff981d93bf720 fffff981d93bf720 ffffa908c9375340 : nt!MiCreateNewSection+0x2e3

fffff981d93bf5b0 fffff80159d0ce34 : fffff981d93bf5e0 ffff97884d0c44f0 ffffa908c9375370 0000000000000000 : nt!MiCreateImageOrDataSection+0x2fa

fffff981d93bf6a0 fffff80159d0cba5 : 0000000001000000 fffff981d93bfa60 0000000000000001 ffffa908d305d2c8 : nt!MiCreateSection+0xf4

fffff981d93bf820 fffff80159d0c93c : 000000000108e418 000000000000000d 0000000000000000 0000000000000001 : nt!MiCreateSectionCommon+0x255

fffff981d93bf900 fffff80159a2bce5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!NtCreateSection+0x5c

fffff981d93bf970 00007ffa52e6fcb4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

000000000108e378 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`52e6fcb4

SYMBOL_NAME: nt!KeAccumulateTicks+25d714

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3155

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 25d714

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Followup: MachineOwner

—————————————————-

其中ui32.exe为wallpaper engine

***moved from Windows / Windows 11 / 性能和系统故障***

锁定的问题。此问题已从 Microsoft 支持社区迁移。你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

7 个答案

Answer 1

您好，欢迎您咨询微软社区。

了解到您的问题，正如您所指出的，这确实是“ui32.exe”程序报错。

请您暂时卸载wallpaper engine之后干净启动启动一下，干净启动之后看看是否还会出现问题。（注意：请您严格按照执行顺序操作，如果在执行干净启动时未勾选隐藏所有Microsoft服务，将导致所有Microsoft服务也被禁用，登录系统时PIN码和人脸识别将失效，只能通过密码登录）

如何在 Windows 中执行干净启动 (microsoft.com)

免责声明: 干净启动是通过一组最少的驱动程序和启动程序来启动 Windows，以便你可以确定后台程序是否干扰你的游戏或程序，并帮助您找出问题的原因。“干净启动”的步骤乍一看可能很复杂，但为了避免给您带来麻烦，请按顺序一步一步地操作，它将帮助您回到正轨。

如果没有问题可尝试重新安装该软件。

希望以上信息能够帮助到您。

Carlos|微软社区支持专员

Answer 2

您好，这两天又出现了同样的问题，但除了报错的PROCESS_NAME不一样，其他好像是一样的。
这次是在HDD的文件转移中出现的蓝屏
以下是dmp文件
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : 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.047 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Loading Dump File [C:\Users\KiyoT\Desktop\031424-34828-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.2506.amd64fre.ni_release_svc_prod3.231018-1809 Kernel base = 0xfffff8064c800000 PsLoadedModuleList = 0xfffff8064d413550 Debug session time: Thu Mar 14 04:29:55.997 2024 (UTC + 9:00) System Uptime: 0 days 4:47:39.843 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................ Loading User Symbols PEB address is NULL ! Loading unloaded module list ................ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8064cc16c30 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe601540bc9f0=0000000000000101 5: 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffe60153f5b180, The PRCB address of the hung processor. Arg4: 0000000000000003, The index of the hung processor.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 671

Key  : Analysis.Elapsed.mSec
Value: 3261

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x101

Key  : Bugcheck.Code.TargetModel
Value: 0x101

Key  : Failure.Bucket
Value: CLOCK\_WATCHDOG\_TIMEOUT\_nt!KeAccumulateTicks

Key  : Failure.Hash
Value: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Key  : WER.OS.Branch
Value: ni\_release\_svc\_prod3

Key  : WER.OS.Version
Value: 10.0.22621.2506

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe60153f5b180

BUGCHECK_P4: 3

FILE_IN_CAB: 031424-34828-01.dmp

FAULTING_PROCESSOR: 3

FAULTING_THREAD: ffffb80f533ed080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Registry

TRAP_FRAME: ffffb80f69e84e6c -- (.trap 0xffffb80f69e84e6c) Unable to read trap frame at ffffb80f`69e84e6c

STACK_TEXT:
ffffe601540bc9e8 fffff8064cc70094 : 0000000000000101 0000000000000018 0000000000000000 ffffe60153f5b180 : nt!KeBugCheckEx ffffe601540bc9f0 fffff8064ca12421 : fffff78000000350 ffffe601540a2180 000000000010daf5 0000000000000000 : nt!KeAccumulateTicks+0x25d714 ffffe601540bca50 fffff8064ca0fa2f : 0000000000000008 0000000000001388 000000000010da00 00000000000a0bea : nt!KiUpdateRunTime+0xd1 ffffe601540bcc00 fffff8064ca10618 : 0000000000000000 0000000000000000 ffffe601540a2180 0000000000000000 : nt!KiUpdateTime+0x63f ffffe601540bcea0 fffff8064ca0feda : fffff8064d45fe20 0000000000000001 0000000000000001 000000000000000c : nt!KeClockInterruptNotify+0x228 ffffe601540bcf40 fffff8064cb24cdc : 000000282fc2289f ffffb80f4a746720 ffffb80f4a7467d0 0000000000000000 : nt!HalpTimerClockInterrupt+0x10a ffffe601540bcf70 fffff8064cc18dea : fffff98c7ee9dba0 ffffb80f4a746720 ffffe601540a2180 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c ffffe601540bcfb0 fffff8064cc19697 : fffff98c7ee9dba0 ffffe601540a2180 0000000000000001 000000000e125ae7 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff98c7ee9db20 fffff8064ca37a6c : 0000000000000000 0000000000000001 ffffb80f69e84e6c 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff98c7ee9dcb0 fffff8064cb8e564 : fffff98c7ee9de00 ffffffffffffffff 0000000000000000 0000000000000000 : nt!KiIpiSendRequestEx+0x7c fffff98c7ee9dcf0 fffff8064cb8e482 : fffff98c7ee9de00 fffff98c7ee9ddb0 0000000000000001 0000000000000000 : nt!KxFlushMultipleTb+0xa0 fffff98c7ee9dd60 fffff8064ca4fe1d : fffff98c7ee9de70 fffff97ca2c24e00 0000000000000000 fffff98c7ee9de80 : nt!KeFlushMultipleRangeTb+0x9e fffff98c7ee9dde0 fffff8064cb0292b : fffff945849c05f0 ffffab0003960600 8200000132023121 fffff945849c05e8 : nt!MiFlushTbList+0xcd fffff98c7ee9de10 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MmProtectPool+0x373

SYMBOL_NAME: nt!KeAccumulateTicks+25d714

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3155

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 25d714

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks

OS_VERSION: 10.0.22621.2506

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e}

Followup: MachineOwner

Answer 3

您好，感谢您的回复。

这次是注册表程序报错，请问您电脑上有安装什么三方防病毒软件或安全软件吗？

如果有请暂时关闭，关闭防火墙，之后再干净启动一下。（注意：请您严格按照执行顺序操作，如果在执行干净启动时未勾选隐藏所有Microsoft服务，将导致所有Microsoft服务也被禁用，登录系统时PIN码和人脸识别将失效，只能通过密码登录）

如何在 Windows 中执行干净启动 (microsoft.com)

免责声明: 干净启动是通过一组最少的驱动程序和启动程序来启动 Windows，以便你可以确定后台程序是否干扰你的游戏或程序，并帮助您找出问题的原因。“干净启动”的步骤乍一看可能很复杂，但为了避免给您带来麻烦，请按顺序一步一步地操作，它将帮助您回到正轨。

暂时关闭防护软件中的防病毒保护以便帮您找出问题的原因，但请记住，关闭该功能后，你的设备可能易受威胁。故一旦问题解决，请立即开启防护软件.

完成之后建议您尝试系统修复。

请在开始搜索框输入cmd，以管理员身份运行命令提示符。

输入并执行以下命令（请在输入一条回车执行后再输入下一条）

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-image /RestoreHealth

SFC /scannow

Answer 4

好的，谢谢！我会去尝试。

但请允许我以一个非专业人员的角度来看待蓝屏问题，
因为我是业余人员，所以这些dmp信息我都曾经交代给GPT-4处理过
对于这次新的蓝屏给出的解释是
根据你提供的调试器输出，系统崩溃是由 CLOCK_WATCHDOG_TIMEOUT 错误引起的。这个错误一般是由于指定的处理器在分配的间隔内没有收到预期的时钟中断，这表明该处理器挂起并且没有处理中断。当 PROCESS_NAME 显示为 "Registry" 时，这意味着在系统崩溃（蓝屏）发生时，引发问题的进程与Windows注册表操作有关。然而，这并不一定意味着注册表操作本身直接导致了 CLOCK_WATCHDOG_TIMEOUT 错误。这个错误通常与处理器相关，尤其是处理器在预定的时间内未能处理中断的问题。

在这种情况下，虽然注册表进程是崩溃时的活动进程，但更可能的情况是系统中的某个底层问题（如处理器故障、过热、电源不稳定、驱动程序冲突或BIOS/固件问题）引发了这个错误。注册表进程可能只是碰巧在错误发生时正在执行。
上一次蓝屏给出的关注点也是在 CLOCK_WATCHDOG_TIMEOUT 错误。

请问我是否应该把硬件问题考虑在内呢？
非常抱歉麻烦您，也请您多多关照！

Answer 5

您好，感谢您的回复。

确实如您查询到的，注册表报错可能是程序在注册表进行写入或更改时出现的错误，常见的有安全程序修改或系统内部程序错误。

当然像这些驱动、BIOS等问题或是硬件方面的问题也是有可能的，只不过从可能性上考虑现在建议您先作一下系统或软件方面的排查。