电脑在跑深度学习实验时经常蓝屏

Question

电脑在跑深度学习实验时经常蓝屏，显示的是dpc-watchdog-violation错误代码。但是我通过启动WinDbg Preview对于蓝屏文件进行分析，显示的是以下代码：

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

Loading Dump File [C:\Windows\Minidump\042323-33468-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
Machine Name:
Kernel base = 0xfffff802`4fa00000 PsLoadedModuleList = 0xfffff802`5062a2d0
Debug session time: Sun Apr 23 01:46:46.337 2023 (UTC + 8:00)
System Uptime: 0 days 8:13:27.047
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:
fffff802`4fdfbc10 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`52697c90=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: 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: fffff802506fb320, 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: 1733

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3659

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802506fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ComputerZServi

STACK_TEXT:  
fffff802`52697c88 fffff802`4fe43714     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`506fb320 : nt!KeBugCheckEx
fffff802`52697c90 fffff802`4fc86e3d     : 0000662f`70f68114 fffff802`49ee5180 00000000`00000246 00000000`001ce9c3 : nt!KeAccumulateTicks+0x1bfaf4
fffff802`52697cf0 fffff802`4fc7dec1     : 00000000`00000000 00000000`00113bcb fffff802`49ee5180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff802`52697d40 fffff802`4fc81253     : fffff802`49ee5180 00000000`00000000 fffff802`50631670 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff802`52697e80 fffff802`4fc88ae2     : fffff802`52690970 fffff802`526909f0 fffff802`52690900 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff802`52697f30 fffff802`4fd3e965     : 00000044`ef43df77 fffff802`506f3ae0 fffff802`506f3b90 ffffe181`e08d6c80 : nt!HalpTimerClockInterrupt+0xe2
fffff802`52697f60 fffff802`4fdfdbaa     : fffff802`526909f0 fffff802`506f3ae0 ffff9c8b`10ff6810 fffff802`52690cc0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`52697fb0 fffff802`4fdfe377     : 00000000`00000002 00000000`00000002 00000000`00000000 fffff802`70194ba0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`52690970 fffff802`4fc263f7     : ffffe181`e08d6d00 fffff802`49ee8200 fffff802`52690b70 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`52690b00 fffff802`4fc8b68d     : fffff802`49ee8240 ffff9c8b`10fed000 fffff802`52690cb0 fffff802`00000002 : nt!EtwpLogKernelEvent+0x2a7
fffff802`52690bb0 fffff802`4fc8a864     : fffff802`49ee5180 00000000`00000000 00000000`00000000 00000000`00113ab4 : nt!KiExecuteAllDpcs+0x41d
fffff802`52690d20 fffff802`4fe04105     : 00000000`00000000 fffff802`49ee5180 00000000`00000000 ffff9c8b`1c8bfa58 : nt!KiRetireDpcList+0x1f4
fffff802`52690fb0 fffff802`4fe03ef0     : 00000000`00000075 fffff802`4fe0333f 00000000`01000010 00000000`00000246 : nt!KxRetireDpcList+0x5
ffffb18e`a6e2e1c0 fffff802`4fe03358     : 00000000`0010a01c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffb18e`a6e2e1f0 fffff802`6f9b9a7c     : 00000000`00000000 00000000`0010a01c ffff9c8b`19e50390 00000000`00000000 : nt!KiDpcInterrupt+0x2e8
ffffb18e`a6e2e380 00000000`00000000     : 00000000`0010a01c ffff9c8b`19e50390 00000000`00000000 00000000`00000020 : nvlddmkm+0x99a7c

SYMBOL_NAME:  nvlddmkm+99a7c

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  99a7c

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff802`6f920000 fffff802`723ce000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jul 22 08:04:08 2022 (62D9E978)
    CheckSum:         029C5C2B
    ImageSize:        02AAE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Answer 1

您好，我是A&K，前来提供帮助。

您提供的信息显示Nvidia显卡驱动程序造成了崩溃。

这有可能是显卡故障或者驱动程序损坏导致的，建议先卸载显卡驱动程序，然后执行一下系统修复。以管理员身份打开PowerShell输入以下命令：

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-image /RestoreHealth
sfc /scannow

然后从设备制造商官网下载最新版本的驱动程序并重新安装。