欢迎访问 Microsoft Q&A，我是 Pondsi。
请问什么闪退？是说应用会闪退吗？是特定的应用？还是大部分应用都会？
电脑本身有死机、蓝屏、重启的情况吗？
请使用提问的账号点击我回答下面的 “ 添加注释 ” 进行回复，这样我才能收到提醒。
我在使用电脑时会遇见闪退的情况，我通过windbg分析了一下，具体信息如下：
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 99%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
先生 游
45
信誉分
我在使用电脑时会遇见闪退的情况，我通过windbg分析了一下，具体信息如下：我在使用电脑时会遇见闪退的情况，我通过windbg分析了一下，具体信息如下：
Windows 家庭版 | Windows 11 | 显示器和显卡
{count} 票
-
先生 游 45 信誉分
2025-09-13T01:47:13.1233333+00:00 Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the display engines failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffda801fdf3460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff806700032d0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffda80171a0080, Optional internal context dependent data. Debugging Details: ------------------ Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1453 Key : Analysis.Elapsed.mSec Value: 5851 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 12 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 953 Key : Analysis.Init.Elapsed.mSec Value: 64956 Key : Analysis.Memory.CommitPeak.Mb Value: 124 Key : Analysis.Version.DbgEng Value: 10.0.27920.1001 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.LegacyAPI Value: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x141_IMAGE_nvlddmkm.sys Key : Failure.Exception.IP.Address Value: 0xfffff806700032d0 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x14932d0 Key : Failure.Hash Value: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc} BUGCHECK_CODE: 141 BUGCHECK_P1: ffffda801fdf3460 BUGCHECK_P2: fffff806700032d0 BUGCHECK_P3: 0 BUGCHECK_P4: ffffda80171a0080 FILE_IN_CAB: WATCHDOG-20250912-1250.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING_THREAD: ffffda80161e5480 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffda801fdf3460 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: ffffda80171a0080 PROCESS_NAME: System STACK_TEXT: ffffc28f`765aeeb0 fffff806`c54d7239 : ffffda80`1fdf3460 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e ffffc28f`765af3e0 fffff806`c587e60a : 00000000`00000000 00000000`00000000 fffff806`c589a2a0 00000000`c0000099 : nt!DbgkpWerProcessPolicyResult+0x21 ffffc28f`765af410 fffff806`c587e409 : 00000000`00000003 ffffc28f`765af5f0 ffffda80`1fdf3460 ffffda80`22677c60 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea ffffc28f`765af470 fffff806`583f0509 : ffff918a`032a7b70 ffff918a`032a7b70 ffff918a`041a33bb ffffda80`1fdf3460 : nt!DbgkWerCaptureLiveKernelDump+0x69 ffffc28f`765af4f0 fffff806`5ba59b02 : 00000002`7af8a17a 00000000`00000006 ffffda80`16218000 ffffda80`161a3000 : dxgkrnl!TdrCollectDbgInfoStage1+0xd69 ffffc28f`765af6b0 fffff806`5bab6f76 : ffffda80`16218000 ffffda80`16218000 ffffda80`161a3000 00000000`00000000 : dxgmms2!VidSchiResetEngine+0x37a ffffc28f`765af8a0 fffff806`5bab9af6 : fffff780`00000000 ffffda80`161a3000 ffffc28f`765afa39 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xea ffffc28f`765af8f0 fffff806`5ba35ed4 : ffffda80`161a3000 00000000`00000000 ffffc28f`765afa39 00000000`00010a32 : dxgmms2!VidSchiCheckHwProgress+0x316 ffffc28f`765af980 fffff806`5baba4b2 : ffffda80`161a3000 ffffc28f`765afaf0 ffffda80`22176010 ffffda80`1faed010 : dxgmms2!VidSchiScheduleCommandToRun+0x64 ffffc28f`765afaa0 fffff806`5bab710c : ffffda80`161a3500 ffffda80`161a3000 fffff806`5bab7030 ffffda80`161a3000 : dxgmms2!VidSchiRun_PriorityTable+0x42 ffffc28f`765afaf0 fffff806`c525904a : ffffda80`161e5480 fffff806`00000001 ffffb181`f68d1180 026fe47f`b19bbdff : dxgmms2!VidSchiWorkerThread+0xdc ffffc28f`765afb30 fffff806`c54741c4 : ffffb181`f68d1180 ffffda80`161e5480 fffff806`c5258ff0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a ffffc28f`765afb80 00000000`00000000 : ffffc28f`765b0000 ffffc28f`765a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nvlddmkm+14932d0 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffda8ff06bf040; .thread 0xffffda80161e5480 ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc} Followup: MachineOwner ---------重新发一下，刚才乱码了
登录以评论
-
Pondsi 346.1K 信誉分 独立顾问2025-09-13T02:10:19.3366667+00:00
-
先生 游 45 信誉分
2025-09-13T03:11:48.89+00:00 闪退主要集中在两款游戏，日常使用倒是没有遇见什么问题，但是有时候edge浏览器会画面出问题，就是很明显却也不太好描述的问题，不同于蓝屏和黑屏，就是画面变得特别的乱七八糟的。重启浏览器一般就没了。
-
Pondsi 346.1K 信誉分 独立顾问
2025-09-13T03:13:37.6233333+00:00 感谢回复，
可能和显卡有关。
请到电脑品牌的官网下载显卡驱动，重新安装一遍，请勿使用第三方的驱动安装程序。不是检测驱动更新，要下载后重新安装。
然后打开edge→进入
edge://settings/resetProfileSettings点击【重置】→暂时不要安装任何扩展。看下是否恢复正常。
-
先生 游 45 信誉分
2025-09-20T09:25:05.5933333+00:00 现在似乎可以确定了，只要在运行游戏时（并非单一某一款）就会出现画面卡顿，但游戏仍在运行（还有声音，也可以切屏，打开任务管理器）。最新的winddg分析报告如下
VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the display engines failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffe3890d620010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff805682116a0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffe38911136080, Optional internal context dependent data. Debugging Details: ------------------ Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1375 Key : Analysis.Elapsed.mSec Value: 6083 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 12 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 906 Key : Analysis.Init.Elapsed.mSec Value: 73381 Key : Analysis.Memory.CommitPeak.Mb Value: 126 Key : Analysis.Version.DbgEng Value: 10.0.27920.1001 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.LegacyAPI Value: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 0x18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x141_IMAGE_nvlddmkm.sys Key : Failure.Exception.IP.Address Value: 0xfffff805682116a0 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x17016a0 Key : Failure.Hash Value: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc} BUGCHECK_CODE: 141 BUGCHECK_P1: ffffe3890d620010 BUGCHECK_P2: fffff805682116a0 BUGCHECK_P3: 0 BUGCHECK_P4: ffffe38911136080 FILE_IN_CAB: WATCHDOG-20250920-1006.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump FAULTING_THREAD: ffffe388feb7a480 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe3890d620010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: ffffe38911136080 PROCESS_NAME: System STACK_TEXT: fffff90a`ad1eeec0 fffff805`bc6fcfb9 : ffffe389`0d620010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e fffff90a`ad1ef3f0 fffff805`bcaa4dfa : 00000000`00000000 00000000`00000000 fffff805`bcad7740 00000000`c0000099 : nt!DbgkpWerProcessPolicyResult+0x21 fffff90a`ad1ef420 fffff805`bcaa4bf9 : 00000000`00000003 fffff90a`ad1ef600 ffffe389`0d620010 ffffe389`12cd8e10 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea fffff90a`ad1ef480 fffff805`4e232459 : ffffbf8f`5d4561d0 ffffbf8f`5d4561d0 ffffbf8f`6b1329bd ffffe389`0d620010 : nt!DbgkWerCaptureLiveKernelDump+0x69 fffff90a`ad1ef500 fffff805`706c4b82 : 0000000d`94ed969d 00000000`00000006 ffffe388`feb7b000 ffffe388`feb0d000 : dxgkrnl!TdrCollectDbgInfoStage1+0xd69 fffff90a`ad1ef6c0 fffff805`70725176 : ffffe388`feb7b000 ffffe388`feb7b000 ffffe388`feb0d000 00000000`00000000 : dxgmms2!VidSchiResetEngine+0x37a fffff90a`ad1ef8b0 fffff805`7072db86 : fffff90a`00000000 ffffe388`feb0d000 fffff90a`ad1efa39 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xea fffff90a`ad1ef900 fffff805`706a3c4f : ffffe388`feb0d000 00000000`00000000 fffff90a`ad1efa39 00000000`0005b252 : dxgmms2!VidSchiCheckHwProgress+0x316 fffff90a`ad1ef990 fffff805`7072e542 : ffffe388`feb0d000 ffffe389`044c5500 ffffe389`0bb51010 ffffe389`0bb51010 : dxgmms2!VidSchiScheduleCommandToRun+0x5f fffff90a`ad1efaa0 fffff805`70725361 : ffffe388`feb0d500 ffffe388`feb0d000 fffff805`70725280 ffffe388`feb0d000 : dxgmms2!VidSchiRun_PriorityTable+0x42 fffff90a`ad1efaf0 fffff805`bc487c2a : ffffe388`feb7a480 fffff805`00000001 ffffab01`a7bca180 066fe47f`b19bbdff : dxgmms2!VidSchiWorkerThread+0xe1 fffff90a`ad1efb30 fffff805`bc6a0b24 : ffffab01`a7bca180 ffffe388`feb7a480 fffff805`bc487bd0 006e6f69`73726556 : nt!PspSystemThreadStartup+0x5a fffff90a`ad1efb80 00000000`00000000 : fffff90a`ad1f0000 fffff90a`ad1e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nvlddmkm+17016a0 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffe388d86d5040; .thread 0xffffe388feb7a480 ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc} Followup: MachineOwner ---------有意思的一点是我注意到每一次报错都是以下问题
Mini Kernel Dump does not contain unloaded driver list Mini Kernel Dump does not contain unloaded driver list Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys然后这个偏移位置，我看见的都是这两个位置
SYMBOL_NAME: nvlddmkm+14932d0 SYMBOL_NAME: nvlddmkm+17016a0 其中nvlddmkm+17016a0占了大部分。 -
先生 游 45 信誉分
2025-09-20T09:28:34.1866667+00:00 我的显卡为RTX4060，是笔记本。然后我使用DDU工具尝试了很多个驱动版本。有最新的，有笔记本官网上的，也有最新的，然后现在是566.36
登录以评论 -