电脑蓝屏 dpc watchdog violation 蓝屏

      Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Windows\Minidump\062122-11734-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 Machine Name: Kernel base = 0xfffff800`52200000 PsLoadedModuleList = 0xfffff800`52e2a2b0 Debug session time: Tue Jun 21 18:54:46.556 2022 (UTC + 8:00) System Uptime: 2 days 8:26:05.960 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: fffff800`525f7dd0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbb00`3dbbfe20=0000000000000133 5: 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. The offending component can usually be     identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff80052efb320, 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: 2967      Key  : Analysis.DebugAnalysisManager     Value: Create      Key  : Analysis.Elapsed.mSec     Value: 10393      Key  : Analysis.Init.CPU.mSec     Value: 1030      Key  : Analysis.Init.Elapsed.mSec     Value: 107876      Key  : Analysis.Memory.CommitPeak.Mb     Value: 95      Key  : Dump.Attributes.AsUlong     Value: 8      Key  : Dump.Attributes.KernelGeneratedTriageDump     Value: 1   FILE_IN_CAB:  062122-11734-01.dmp  DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump  BUGCHECK_CODE:  133  BUGCHECK_P1: 1  BUGCHECK_P2: 1e00  BUGCHECK_P3: fffff80052efb320  BUGCHECK_P4: 0  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:   ffffbb00`3dbbfe18 fffff800`52637070     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`52efb320 : nt!KeBugCheckEx ffffbb00`3dbbfe20 fffff800`5245f203     : 0000d3a9`5cc2807b ffffbb00`3dba6180 00000000`00000000 ffffbb00`3dba6180 : nt!KeAccumulateTicks+0x1d5610 ffffbb00`3dbbfe80 fffff800`5245ecea     : ffff990d`8ecc4600 fffff08a`378c3ab0 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify+0x453 ffffbb00`3dbbff30 fffff800`5242d885     : ffff990d`8ecc4600 fffff800`525479b7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a ffffbb00`3dbbff60 fffff800`525f987a     : fffff08a`378c3ab0 ffff990d`8ecc4600 00000000`00000383 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffbb00`3dbbffb0 fffff800`525f9de7     : ffff990d`ac9790c0 ffff990d`ac9791c0 00000000`00000002 ffffbb00`3e136180 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff08a`378c3a30 fffff800`a319675d     : ffff990d`ac9790c0 00000000`00000000 00000000`00000000 fffff800`525a7613 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff08a`378c3bc0 ffff990d`ac9790c0     : 00000000`00000000 00000000`00000000 fffff800`525a7613 fffff08a`3ac52580 : netrtp+0x675d fffff08a`378c3bc8 00000000`00000000     : 00000000`00000000 fffff800`525a7613 fffff08a`3ac52580 fffff800`a3199240 : 0xffff990d`ac9790c0   SYMBOL_NAME:  netrtp+675d  MODULE_NAME: netrtp  IMAGE_NAME:  netrtp.sys  STACK_COMMAND:  .cxr; .ecxr ; kb  BUCKET_ID_FUNC_OFFSET:  675d  FAILURE_BUCKET_ID:  0x133_ISR_netrtp!unknown_function  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {d1a52398-623d-e4a5-5951-02cd99e33301}  Followup:     MachineOwner ---------  5: kd> lmvm netrtp Browse full module list start             end                 module name fffff800`a3190000 fffff800`a319f000   netrtp   T (no symbols)                Loaded symbol image file: netrtp.sys     Image path: netrtp.sys     Image name: netrtp.sys     Browse all global symbols  functions  data     Timestamp:        Wed Dec  8 16:08:28 2021 (61B067FC)     CheckSum:         0000E5C1     ImageSize:        0000F000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4     Information from resource tables: 5: kd> lmvm netrtp Browse full module list start             end                 module name fffff800`a3190000 fffff800`a319f000   netrtp   T (no symbols)                Loaded symbol image file: netrtp.sys     Image path: netrtp.sys     Image name: netrtp.sys     Browse all global symbols  functions  data     Timestamp:        Wed Dec  8 16:08:28 2021 (61B067FC)     CheckSum:         0000E5C1     ImageSize:        0000F000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4     Information from resource tables:dmp文件https://1drv.ms/u/s!ArOnN2zwJMCOgg4iEb4HTY4Gbp6t?e=yoXHQS      Hiturbo,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好turbo，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
        你好，我重新编辑了问题，在最后附加了文件分享链接此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        Hi,Thanksforgettingbacktothisthread.Iamafraidthatthereisnofileavailableintheprovidedlink.Wouldyoupleasedouble-checkit?Thankyou你好，感谢您回到这个话题。恐怕提供的链接中没有可用的文件。请你再检查一遍好吗？谢谢
        已修改，烦请查看此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        你好，感谢分享minidump文件。minidump文件表明第三方驱动程序netrtp.sys是导致BSOD的原因。根据我所做的搜索，此文件与适用于Windows的linux软件或工具相关联。您的计算机上是否安装了任何Linux工具？如果没有，请检查计算机遇到蓝屏时打开了哪些软件？请保持让我知道最新消息。
        你好，我并没有安装linux相关的软件。经我查找，我发现netrtp.sys文件是在联想电脑管家的安装目录下：C:\ProgramFiles(x86)\PCManager\5.0.20.6062\Modules\drivers\netrtp\x86\netrtp.sysC:\ProgramFiles(x86)\PCManager\5.0.20.6062\Modules\drivers\netrtp\x64\netrtp.sys是否可以直接删除？此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        你好，谢谢你更新我。恐怕我不确定这个驱动程序到底是什么，因此，我不能建议你删除它。您可以将其名称从netrtp.sys更改为netrtp.sys.old。我会让其他专家为您提供准确的信息。问候，