使用lumion过程中突然蓝屏！

      Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Desktop\110322-13500-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`4fc00000 PsLoadedModuleList = 0xfffff807`5082a270
Debug session time: Thu Nov  3 16:23:15.999 2022 (UTC + 8:00)
System Uptime: 0 days 17:02:44.406
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`4fff90f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9080`8f4f2e20=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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807508fb320, 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: 1140

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 52567

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  110322-13500-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff807508fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffc68528b3ecb0 -- (.trap 0xffffc68528b3ecb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffb68ecae2def0
rdx=ffff90808f4d9180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8074fea9a9c rsp=ffffc68528b3ee40 rbp=ffffc68528b3f1d0
 r8=ffffb68ecad7f118  r9=ffffc68528b3f010 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff807`4fea9a9c 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  QQProtect.exe

STACK_TEXT: 
ffff9080`8f4f2e18 fffff807`50059882     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`508fb320 : nt!KeBugCheckEx
ffff9080`8f4f2e20 fffff807`4fed2973     : 0000ce4f`800ede6a ffff9080`8f4d9180 00000000`00000000 ffff9080`8f4d9180 : nt!KeAccumulateTicks+0x1846b2
ffff9080`8f4f2e80 fffff807`4fed245a     : ffffb68e`aa517600 ffffc685`28b3ed30 00000000`00000000 ffffc685`28b3f3a0 : nt!KeClockInterruptNotify+0x453
ffff9080`8f4f2f30 fffff807`4fe08a45     : ffffb68e`aa517600 00000000`00000000 00000000`00000000 ffffa837`8bf34d32 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9080`8f4f2f60 fffff807`4fffab9a     : ffffc685`28b3ed30 ffffb68e`aa517600 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9080`8f4f2fb0 fffff807`4fffb107     : 00000000`e1344441 00000000`000fffff 0051002f`00640061 00440043`00500051 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc685`28b3ecb0 fffff807`4fea9a9c     : ffffc685`28b3f3a0 ffffc685`28b3f35c 00000000`00000001 ffffc685`28b3f1d0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc685`28b3ee40 fffff807`4fe15c97     : ffffb68e`cae2de90 00000000`00000000 ffffb68e`00000007 fffff807`00000001 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffffc685`28b3ee70 fffff807`502054ee     : ffffb68e`cac97a20 00000000`00989680 00000000`00000001 ffffb68e`cac97a20 : nt!IoRemoveIoCompletion+0x3e7
ffffc685`28b3efa0 fffff807`5000aab5     : 00000000`0000000a 00000000`00000019 00000000`00000032 00000000`00000000 : nt!NtRemoveIoCompletionEx+0xfe
ffffc685`28b3f0e0 fffff807`4fffcf80     : fffff38e`bf2c3e23 fffff3ba`04207010 fffff3ba`04207010 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
ffffc685`28b3f2e8 fffff38e`bf2c3e23     : fffff3ba`04207010 fffff3ba`04207010 00000000`00000000 fffff38e`bee410c0 : nt!KiServiceLinkage
ffffc685`28b3f2f0 fffff3ba`04207010     : fffff3ba`04207010 00000000`00000000 fffff38e`bee410c0 ffffc685`28b3f398 : win32kfull+0x53e23
ffffc685`28b3f2f8 fffff3ba`04207010     : 00000000`00000000 fffff38e`bee410c0 ffffc685`28b3f398 00000000`00000000 : 0xfffff3ba`04207010
ffffc685`28b3f300 00000000`00000000     : fffff38e`bee410c0 ffffc685`28b3f398 00000000`00000000 00000000`00000000 : 0xfffff3ba`04207010


SYMBOL_NAME:  win32kfull+53e23

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  53e23

FAILURE_BUCKET_ID:  0x133_ISR_win32kfull!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c1c3fa1-9dcb-993b-cfb5-e74899d88134}

Followup:     MachineOwner
---------      Hi广,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好广，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
        你说的OneDrive或GoogleDrive都无法共享，我文件已经用WinDbg打开，并且全部复制到上面了，请仔细查看后！Microsoft(R)WindowsDebuggerVersion10.0.25200.1003AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
        你好，感谢分享minidump文件，抱歉晚了minidump文件没有命名任何驱动程序，仅表明win32kfull.sys是一个Windows组件，这意味着其他原因导致系统出现故障，或者它可能是通常由于驱动程序不兼容而发生的内存损坏。如果只出现一次，可能是更新驱动或驱动不兼容造成的。如果它经常发生，请尝试以下步骤来解决此问题：1-检查更新：转到设置>更新和安全>检查更新>安装所有待处理的更新2-使用DDU免费工具完全卸载显卡驱动：https://www-guru3d-com.translate.goog/files-det.然后，安装制造商网站上提供的最新驱动程序。3-卸载任何第三方安全软件并使用免费的Malwarebytes扫描病毒和恶意软件：https://www-malwarebytes-com.translate.goog/mwb.4-以管理员身份运行命令提示符。键入此命令并按回车键：dism.exe/online/cleanup-image/restorehealth然后，键入此命令并按回车键：sfc/scannow5-如果您要超频您的PC，请尝试以它们的库存速度运行所有东西（CPU、GPU、系统内存）。看看问题是否仍然可以重现。或者，关闭XMP配置文件或将其设置为自动。6-从制造商的网站下载并安装最新版本的BIOS和芯片组驱动程序。7-使用免费实用程序MemTest86测试RAM，然后运行完整的8次扫描以测试您的RAM是否存在物理错误：https://www-tenforums-com.translate.goog/tutori.8-运行Windows内存诊断：https://www-howtogeek-com.translate.goog/260813.运行硬盘诊断：https://www-lifewire-com.translate.goog/free-ha.9-如果您愿意这样做，请取出所有系统内存条，检查它们是否有任何明显的缺陷，然后将它们重新插入插槽。确保它们正确安装在插槽中。如果您安装了多根系统内存并且您怀疑其中一根有故障，则可以尝试的一件事是一次仅使用一根内存模块重现该问题。这将帮助您隔离故障模块。10-如果执行上述步骤后问题仍然存在，请启用驱动程序验证程序并让计算机崩溃3次，然后将其禁用并共享新创建的minidump文件：https://www-tenforums-com.translate.goog/tutori.请随时询问您是否需要进一步的帮助。