您好!求助,有朋友说是驱动问题,我删掉了驱动重装,不管是哪个版本甚至是回退到出厂的版本依然无法解决问题,后续尝试了重装系统依然有此问题,每次MINIDUMP‘
的报错都是一下符号。之前半年无此问题,从上周开始频繁出现,一天大概2-3次,不知道是什么冲突,聊天,看视频,打游戏的时候都可能会出现。
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\84302\Desktop\062822-6687-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`20e00000 PsLoadedModuleList = 0xfffff801`21a2a270
Debug session time: Tue Jun 28 17:22:18.729 2022 (UTC + 8:00)
System Uptime: 0 days 0:27:39.427
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`211f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe80`633579e0=0000000000000116
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc08df124e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80133c331ec, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_3340992f43425889\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 48430
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 3479
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Bugcheck.Code.DumpHeader
Value: 0x116
Key : Bugcheck.Code.Register
Value: 0x116
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: 062822-6687-01.dmp
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffc08df124e010
BUGCHECK_P2: fffff80133c331ec
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffc08df124e010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000004
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffe80`633579d8 fffff801`2e87665e : 00000000`00000116 ffffc08d`f124e010 fffff801`33c331ec ffffffff`c000009a : nt!KeBugCheckEx
fffffe80`633579e0 fffff801`2e826e44 : fffff801`33c331ec ffffc08d`f3c408a0 00000000`00002000 ffffc08d`f3c40960 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffffe80`63357a20 fffff801`2e81f97c : ffffc08d`f3c6b000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
fffffe80`63357a50 fffff801`2e875d85 : 00000000`00000100 ffffc08d`f3c6ba70 00000000`f512dd60 fffff801`210cf40c : dxgkrnl!DXGADAPTER::Reset+0x4dc
fffffe80`63357ad0 fffff801`2e875ef7 : fffff801`21b25440 ffffc08d`f16417e0 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
fffffe80`63357b00 fffff801`210b8515 : ffffc08d`f142e040 fffff801`2e875ed0 ffffc08d`e3b1fbe0 ffffc08d`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffffe80`63357b30 fffff801`21155855 : ffffc08d`f142e040 00000000`00000080 ffffc08d`e3a99180 00000000`00000001 : nt!ExpWorkerThread+0x105
fffffe80`63357bd0 fffff801`211fe808 : ffffe400`9aa98180 ffffc08d`f142e040 fffff801`21155800 000002bd`28b38480 : nt!PspSystemThreadStartup+0x55
fffffe80`63357c20 00000000`00000000 : fffffe80`63358000 fffffe80`63351000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+e331ec
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
14: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff801`32e00000 fffff801`35730000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_3340992f43425889\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri May 20 01:01:59 2022 (62867807)
CheckSum: 0286E2D7
ImageSize: 02930000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables: 欢迎咨询本站!。显示和英伟达显卡有关的异常。若是有超频,降压等,建议恢复正常。然后到设备供应商的官网更新一下bios,覆盖安装一下芯片组驱动,英伟达显卡驱动,请勿使用第三方的驱动安装程序。完成后执行一下干净启动,排除其他干扰:https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师,代理,加速器,虚拟机等)。然后鼠标右键单击开始菜单→运行(RUN)→输入:msconfig(按下Enter键)点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”(请务必勾选)点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器,(点击底部“详细信息”),点击顶部”启动”,鼠标右键单击“状态”显示为“已启动”的项,选择“禁用”。(禁用所有启动项。)然后重启电脑(不是关机再开机,得选择“重启”)。若是仍然有异常,若是有核显,建议打开设备管理器,禁用英伟达显卡,看下是否恢复正常。以便判断是否英伟达显卡本身的问题。