求助求助 蓝屏日志 求大神看下 附蓝屏日志

以前偶尔蓝屏  昨天更新了下显卡驱动别的没动 蓝屏了几次   还原了歌显卡驱动现在好像没蓝屏了  大神帮我看下日志是不是显卡驱动的问题 怎么解决
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\071022-32062-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`79000000 PsLoadedModuleList = 0xfffff802`79c2a310
Debug session time: Sun Jul 10 06:03:32.699 2022 (UTC + 8:00)
System Uptime: 0 days 2:40:38.406
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`793f7f30 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8401`28ad2e20=0000000000000133
8: 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: fffff80279cfb320, 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                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 3937
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 28618
    Key  : Analysis.Init.CPU.mSec
    Value: 374
    Key  : Analysis.Init.Elapsed.mSec
    Value: 26502
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 97
    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:  071022-32062-01.dmp
BUGCHECK_CODE:  133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80279cfb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME:  ffffbc034849f9d0 -- (.trap 0xffffbc034849f9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802793fbb01 rsp=ffffbc034849fb60 rbp=0000000000000000
r8=0000000000000008  r9=0000000000000000 r10=fffff80292e215a0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiIdleLoop+0x101:
fffff802`793fbb01 48f7433001000000 test    qword ptr [rbx+30h],1 ds:00000000`00000030=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
STACK_TEXT:  
ffff8401`28ad2e18 fffff802`79437170     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`79cfb320 : nt!KeBugCheckEx
ffff8401`28ad2e20 fffff802`7925f203     : 00001979`58821bd4 ffff8401`28a80180 00000000`00000000 ffff8401`28a80180 : nt!KeAccumulateTicks+0x1d5710
ffff8401`28ad2e80 fffff802`7925ecea     : ffffa585`d2b07b20 ffffbc03`4849fa50 ffff8401`28a8e000 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffff8401`28ad2f30 fffff802`7922d885     : ffffa585`d2b07b20 fffff802`793479b7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff8401`28ad2f60 fffff802`793f99da     : ffffbc03`4849fa50 ffffa585`d2b07b20 00000000`000003b8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8401`28ad2fb0 fffff802`793f9f47     : ffff8401`28a80180 00000000`00000000 00000000`00040082 fffff802`7925f9e8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffbc03`4849f9d0 fffff802`793fbb01     : ffffffff`00000000 ffff8401`28a8b440 ffffa585`deeb9080 00000000`000003b8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffbc03`4849fb60 00000000`00000000     : ffffbc03`484a0000 ffffbc03`48499000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x101
SYMBOL_NAME:  nt!KeAccumulateTicks+1d5710
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.19041.1806
STACK_COMMAND:  .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:  1d5710
FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup:     MachineOwner
---------

请看一下在C:\Windows\Minidump文件夹中是否有文件，如果有压缩后挂附件上传到本帖；在C:\Windows文件夹里边有没有一个叫memory.dmp的文件，如果有请压缩后上传网盘，把分享链接发一下。

来大神   给我看一下谢谢

没有权限

提供的日志内容看不出蓝屏原因，如果蓝屏很频繁建议重置或者重装系统试试。