电脑蓝屏，终止代码：dpc watchdog violation

      WINDbg分析如下：Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\103122-13093-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`6ec00000 PsLoadedModuleList = 0xfffff803`6f82a290
Debug session time: Mon Oct 31 12:27:45.690 2022 (UTC + 8:00)
System Uptime: 8 days 3:35:21.266
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`6eff8fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff803`74a13c90=0000000000000133
0: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8036f8fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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: 3124

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3187

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  103122-13093-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8036f8fb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

STACK_TEXT: 
fffff803`74a13c88 fffff803`6f0596fe     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`74a13c90 fffff803`6eed83ed     : 00021494`403ed20c fffff803`6bbe8180 00000000`00000246 00000000`02af9e51 : nt!KeAccumulateTicks+0x18452e
fffff803`74a13cf0 fffff803`6eed8991     : 00000000`02af9e50 00000000`0199da3e fffff803`6bbe8180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff803`74a13d40 fffff803`6eed2803     : fffff803`6bbe8180 00000000`00000000 fffff803`6f8314c0 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff803`74a13e80 fffff803`6eedb1c2     : fffff803`74a0c6b0 fffff803`74a0c730 fffff803`74a0c700 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff803`74a13f30 fffff803`6ee08a45     : 00000667`7e7accd9 fffff803`6f8f39e0 fffff803`6f8f3a90 ffff299b`3676c29e : nt!HalpTimerClockInterrupt+0xe2
fffff803`74a13f60 fffff803`6effaa4a     : fffff803`74a0c730 fffff803`6f8f39e0 ffff8802`5c6a9010 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`74a13fb0 fffff803`6effafb7     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8802`67f7a310 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`74a0c6b0 fffff803`791bfa30     : 00000000`00000017 03070001`40006107 00000f78`42880000 a9b0119b`00001000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`74a0c840 00000000`00000017     : 03070001`40006107 00000f78`42880000 a9b0119b`00001000 1a9005f2`c001109b : Netwbw02+0x3fa30
fffff803`74a0c848 03070001`40006107     : 00000f78`42880000 a9b0119b`00001000 1a9005f2`c001109b fffff803`00000000 : 0x17
fffff803`74a0c850 00000f78`42880000     : a9b0119b`00001000 1a9005f2`c001109b fffff803`00000000 fffff803`6bbe0000 : 0x03070001`40006107
fffff803`74a0c858 a9b0119b`00001000     : 1a9005f2`c001109b fffff803`00000000 fffff803`6bbe0000 ffff7d47`9b65e744 : 0x00000f78`42880000
fffff803`74a0c860 1a9005f2`c001109b     : fffff803`00000000 fffff803`6bbe0000 ffff7d47`9b65e744 ffff8802`5c682a20 : 0xa9b0119b`00001000
fffff803`74a0c868 fffff803`00000000     : fffff803`6bbe0000 ffff7d47`9b65e744 ffff8802`5c682a20 fffff803`79425380 : 0x1a9005f2`c001109b
fffff803`74a0c870 fffff803`6bbe0000     : ffff7d47`9b65e744 ffff8802`5c682a20 fffff803`79425380 00000000`00000000 : 0xfffff803`00000000
fffff803`74a0c878 ffff7d47`9b65e744     : ffff8802`5c682a20 fffff803`79425380 00000000`00000000 ffff8802`5c6a9010 : 0xfffff803`6bbe0000
fffff803`74a0c880 ffff8802`5c682a20     : fffff803`79425380 00000000`00000000 ffff8802`5c6a9010 ffffae00`272d50c8 : 0xffff7d47`9b65e744
fffff803`74a0c888 fffff803`79425380     : 00000000`00000000 ffff8802`5c6a9010 ffffae00`272d50c8 ffffae00`272d5100 : 0xffff8802`5c682a20
fffff803`74a0c890 00000000`00000000     : ffff8802`5c6a9010 ffffae00`272d50c8 ffffae00`272d5100 00000000`00000000 : Netwbw02+0x2a5380


SYMBOL_NAME:  Netwbw02+3fa30

MODULE_NAME: Netwbw02

IMAGE_NAME:  Netwbw02.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  3fa30

FAILURE_BUCKET_ID:  0x133_DPC_Netwbw02!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5d4ef19d-3919-c41d-7c35-1a1b96cb8411}

Followup:     MachineOwner
---------

0: kd> lmvm Netwbw02
Browse full module list
start             end                 module name
fffff803`79180000 fffff803`7950d000   Netwbw02 T (no symbols)          
    Loaded symbol image file: Netwbw02.sys
    Image path: Netwbw02.sys
    Image name: Netwbw02.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 29 23:02:27 2019 (5CC71203)
    CheckSum:         003630EC
    ImageSize:        0038D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:      欢迎访问本站！。可能和网络有关。若是有使用代理，游戏加速器，外接网卡，虚拟网卡，usb网络共享，网络监控类软件等，建议卸载。然后到设备供应商的官网更新一下bios，下载网卡驱动覆盖安装一下，包括有线，无线，蓝牙3个驱动，请勿使用第三方的驱动安装程序。完成后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否恢复正常。