wind10频繁蓝屏，导致文件损坏，windbg preview分析结果如下，求帮忙解答

      Wind10频繁蓝屏，导致文件损坏，WinDbg Preview分析结果如下，求帮忙解答Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\14524\Documents\081122-14062-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 16299 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff803`0b28d000 PsLoadedModuleList = 0xfffff803`0b5f3030 Debug session time: Thu Aug 11 23:52:21.367 2022 (UTC + 8:00) System Uptime: 0 days 1:38:02.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`0b402570 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffba80`a9afdbd0=???????????????? 1: 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: fffff8030b689370, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains     additional information regarding the cumulative timeout Arg4: 0000000000000000  Debugging Details: ------------------   KEY_VALUES_STRING: 1      Key  : Analysis.CPU.mSec     Value: 1702      Key  : Analysis.DebugAnalysisManager     Value: Create      Key  : Analysis.Elapsed.mSec     Value: 1801      Key  : Analysis.Init.CPU.mSec     Value: 2296      Key  : Analysis.Init.Elapsed.mSec     Value: 507875      Key  : Analysis.Memory.CommitPeak.Mb     Value: 70   DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump  BUGCHECK_CODE:  133  BUGCHECK_P1: 1  BUGCHECK_P2: 1e00  BUGCHECK_P3: fffff8030b689370  BUGCHECK_P4: 0  DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED  BLACKBOXBSD: 1 (!blackboxbsd)   BLACKBOXPNP: 1 (!blackboxpnp)   CUSTOMER_CRASH_COUNT:  1  PROCESS_NAME:  WeChat.exe  STACK_TEXT:   ffffba80`a9afdbc8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx   SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE  MODULE_NAME: Unknown_Module  IMAGE_NAME:  Unknown_Image  STACK_COMMAND:  .thread ; .cxr ; kb  FAILURE_BUCKET_ID:  ZEROED_STACK_0x133  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {6a989cd5-40e4-233b-794c-d6318e86cad7}  Followup:     MachineOwner --------- 有一次蓝屏时正在看一个pdf文档，蓝屏重启后文件损坏无法打开了，这是正常的吗？是Wechat的问题吗？      您好，A&K，前来提供帮助。请将您的系统目录C:\Windows\Minidump中所有的文件上传到不限制下载的网盘然后将链接分享过来，这边帮您看一下。在查看文件的过程中系统崩溃，通常不会造成文件损坏，因为此时只是在读取，没有写入内容。通常考虑是应用程序的问题。
        感谢解答！链接：https://pan.baidu.com/s/1yLIhzY-6WNU25hSDLZC3Sw提取码：qeqw