打开大型软件时就会蓝屏,最后一次蓝屏的分析日志如下,帮忙看看如何解决是驱动更新的问题还是硬件问题。
Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\081821-12781-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`1d600000 PsLoadedModuleList = 0xfffff805`1e22a2b0
Debug session time: Wed Aug 18 21:02:32.318 2021 (UTC + 8:00)
System Uptime: 0 days 0:03:21.015
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`1d9f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff805`1c1cde20=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: fffff8051e2fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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: 7608
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 346609
Key : Analysis.Init.CPU.mSec
Value: 1218
Key : Analysis.Init.Elapsed.mSec
Value: 311882
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8051e2fa320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8051c1c6480 -- (.trap 0xfffff8051c1c6480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000020
rdx=fffff8051c1c65c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8052e871357 rsp=fffff8051c1c6610 rbp=ffffca89b7f9a000
r8=0000000000000001 r9=0000000000000020 r10=ffffca89b02c6cc0
r11=fffff8051c1c64f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0x251357:
fffff805`2e871357 ebfe jmp nvlddmkm+0x251357 (fffff805`2e871357)
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: lsass.exe
DPC_STACK_BASE: FFFFF8051C1C6FB0
STACK_TEXT:
fffff805`1c1cde18 fffff805`1da3a988 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff805`1c1cde20 fffff805`1d86f9a3 : 00000088`b1c95116 fffff805`1befe180 00000000`00000000 fffff805`1befe180 : nt!KeAccumulateTicks+0x1c8788
fffff805`1c1cde80 fffff805`1d86f48a : fffff805`1e2f3840 fffff805`1c1c6500 fffff805`277d3c00 00000000`0000b201 : nt!KeClockInterruptNotify+0x453
fffff805`1c1cdf30 fffff805`1d927ef5 : fffff805`1e2f3840 fffff805`1c1cdf40 00000000`00000010 ffffc2e0`83cb6d97 : nt!HalpTimerClockIpiRoutine+0x1a
fffff805`1c1cdf60 fffff805`1d9f722a : fffff805`1c1c6500 fffff805`1e2f3840 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`1c1cdfb0 fffff805`1d9f7797 : ffffca89`b985d000 00000000`00000001 00000000`00000000 fffff805`2eb39ed7 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`1c1c6480 fffff805`2e871357 : ffffca89`b9856050 ffffca89`b7f9a000 ffffca89`b984b000 ffffca89`b0455db8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`1c1c6610 ffffca89`b9856050 : ffffca89`b7f9a000 ffffca89`b984b000 ffffca89`b0455db8 00000000`00000010 : nvlddmkm+0x251357
fffff805`1c1c6618 ffffca89`b7f9a000 : ffffca89`b984b000 ffffca89`b0455db8 00000000`00000010 fffff805`2e871b90 : 0xffffca89`b9856050
fffff805`1c1c6620 ffffca89`b984b000 : ffffca89`b0455db8 00000000`00000010 fffff805`2e871b90 00000000`0001ffdf : 0xffffca89`b7f9a000
fffff805`1c1c6628 ffffca89`b0455db8 : 00000000`00000010 fffff805`2e871b90 00000000`0001ffdf ffffca89`b984b000 : 0xffffca89`b984b000
fffff805`1c1c6630 00000000`00000010 : fffff805`2e871b90 00000000`0001ffdf ffffca89`b984b000 00000000`00000000 : 0xffffca89`b0455db8
fffff805`1c1c6638 fffff805`2e871b90 : 00000000`0001ffdf ffffca89`b984b000 00000000`00000000 fffff805`1c1c6720 : 0x10
fffff805`1c1c6640 00000000`0001ffdf : ffffca89`b984b000 00000000`00000000 fffff805`1c1c6720 00003576`467a3000 : nvlddmkm+0x251b90
fffff805`1c1c6648 ffffca89`b984b000 : 00000000`00000000 fffff805`1c1c6720 00003576`467a3000 00000000`00000000 : 0x1ffdf
fffff805`1c1c6650 00000000`00000000 : fffff805`1c1c6720 00003576`467a3000 00000000`00000000 00000000`80000000 : 0xffffca89`b984b000
SYMBOL_NAME: nvlddmkm+251357
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 251357
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
---------
0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff805`2e620000 fffff805`30625000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nvlt.inf_amd64_1a8f542bd7ea04ef\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Nov 20 18:58:04 2020 (5FB7A13C)
CheckSum: 01F8DA10
ImageSize: 02005000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables: 欢迎咨询本站!Chen-彭迪斯(姓陈)。若是有超频,调压,建议恢复正常,包括主板自动超频功能。显示N显卡的问题,建议到设备供应商的官网更新一下bios,以及显卡驱动,覆盖安装一下,建议安装今年5月之前发布的N卡驱动,请勿使用第三方的驱动安装程序。完成后鼠标右击左下角开始按钮