你好，
建议打开文件夹，进入 C:\Windows\Minidump ，把里面的 .dmp 文件通过网盘分享一下，我将看下情况。
玩游戏时总是蓝屏重启（已保留用户数据重置此电脑、使用DDU卸载显卡驱动均无效果）
![](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(76.8, 84%, 17%)' 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)
梦晖 陈
20
信誉分
玩游戏时总是蓝屏重启（已保留用户数据重置此电脑、使用DDU卸载显卡驱动均无效果）玩游戏时总是蓝屏重启（已保留用户数据重置此电脑、使用DDU卸载显卡驱动均无效果）
Windows 家庭版 | Windows 11 | 性能和系统故障
问题作者接受的答案
-
彭迪斯 10,130 信誉分 志愿者审查方2025-11-04T16:19:37.4833333+00:00 -
梦晖 陈 20 信誉分
2025-11-05T11:02:26.4066667+00:00 ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110425-6890-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff805`13000000 PsLoadedModuleList = 0xfffff805`13c2a930 Debug session time: Tue Nov 4 22:34:00.567 2025 (UTC + 8:00) System Uptime: 0 days 0:55:54.323 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: fffff805`133fd570 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffbd82`31b8f740=0000000000000113 0: kd> !analyze -v 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 .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000002 Arg3: 00000000000010de Arg4: 0000000000002191 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1546 Key : Analysis.Elapsed.mSec Value: 15496 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 1 Key : Analysis.Init.CPU.mSec Value: 843 Key : Analysis.Init.Elapsed.mSec Value: 45796 Key : Analysis.Memory.CommitPeak.Mb Value: 114 Key : Analysis.Version.DbgEng Value: 10.0.29457.1000 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff8054596f9b3 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0xe3f9b3 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 2 BUGCHECK_P3: 10de BUGCHECK_P4: 2191 FILE_IN_CAB: 110425-6890-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump FAULTING_THREAD: ffffc28203c1a040 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffbd82`31b8f738 fffff805`299b3ad0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx ffffbd82`31b8f740 fffff805`297f70da : ffffc281`f2c94180 ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94180 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffffbd82`31b8f780 fffff805`29775721 : ffffc281`f6816000 fffff805`4592d400 ffffc281`00000000 ffffc281`effaa600 : dxgkrnl!DpiFdoHandleDevicePower+0x8111a ffffbd82`31b8f820 fffff805`29776c51 : ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94030 00000028`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21 ffffbd82`31b8f850 fffff805`4596f9b3 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffc281`f6816000 : dxgkrnl!DpiDispatchPower+0xe1 ffffbd82`31b8f970 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c : nvlddmkm+0xe3f9b3 ffffbd82`31b8f978 00000000`00000000 : 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c ffffc282`00000004 : 0x1 SYMBOL_NAME: nvlddmkm+e3f9b3 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffc281e60a0040; .thread 0xffffc28203c1a040 ; kb BUCKET_ID_FUNC_OFFSET: e3f9b3 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner --------- 0: kd> .process /r /p 0xffffc281e60a0040; .thread 0xffffc28203c1a040 ; kb Implicit process is now ffffc281`e60a0040 Loading User Symbols ************* Symbol Loading Error Summary ************** Module name Error nvlddmkm The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. Implicit thread is now ffffc282`03c1a040 *** Stack trace for last set context - .thread/.cxr resets it # RetAddr : Args to Child : Call Site 00 fffff805`299b3ad0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx 01 fffff805`297f70da : ffffc281`f2c94180 ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94180 : watchdog!WdLogEvent5_WdCriticalError+0xe0 02 fffff805`29775721 : ffffc281`f6816000 fffff805`4592d400 ffffc281`00000000 ffffc281`effaa600 : dxgkrnl!DpiFdoHandleDevicePower+0x8111a 03 fffff805`29776c51 : ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94030 00000028`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21 04 fffff805`4596f9b3 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffc281`f6816000 : dxgkrnl!DpiDispatchPower+0xe1 05 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c : nvlddmkm+0xe3f9b3 06 00000000`00000000 : 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c ffffc282`00000004 : 0x1 -
彭迪斯 10,130 信誉分 志愿者审查方
2025-11-06T04:10:39.94+00:00 根据描述，已经重新安装过英伟达显卡驱动。
请尝试安装几款不同版本的英伟达显卡驱动，看下是否某个版本可以恢复正常。
登录以评论 -
-
Noel Macadangdang 3,070 信誉分 独立顾问2025-11-04T17:07:57.0833333+00:00 嗨 梦晖，
感谢你提出问题。 我了解到你在玩游戏时遇到了蓝屏问题，我在这里帮助你解决。
根据我的了解，游戏过程中出现蓝屏通常是由以下几个原因共同造成的：
图形驱动程序损坏或存在故障（即使是刚刚干净卸载过的）
硬件过热或负载过高
内存或电源供应问题
程序之间的冲突，尤其是反作弊软件或后台运行的其他程序
BIOS 中的某些设置不兼容或被错误修改
请按照以下步骤操作：
安装稳定的显卡驱动程序
在使用 DDU 清除驱动后，尝试从你的电脑或显卡制造商官网安装一个较旧版本的驱动程序。 最新版本不一定最稳定，很多用户发现旧版本更可靠。
测试电脑内存
按下 Win + R 打开运行窗口，输入 mdsched.exe，然后重启电脑进行内存检测。 损坏的内存是游戏时蓝屏的常见原因。
检查是否过热
使用 HWMonitor 或 MSI Afterburner 等工具监控 CPU 和 GPU 的温度。 如果温度过高，请清理风扇、改善通风，或考虑降低硬件功耗。
关闭超频设置
如果你对 CPU、GPU 或内存进行了超频，请在 BIOS 或相关软件中恢复默认设置。 超频可能导致游戏时系统不稳定。
执行干净启动
这可以关闭可能与游戏冲突的后台程序。 输入 msconfig，进入“服务”选项卡，勾选“隐藏所有 Microsoft 服务”，然后点击“全部禁用”。
更新 Windows 和游戏
确保你的操作系统和游戏都是最新版本。 旧版本的游戏或驱动程序有时会导致蓝屏。
查看事件查看器和 Minidump 文件
这些文件可能会显示具体的错误代码（如 0x0000007E 或 0xD1），有助于我们进一步分析问题。 如果你愿意，我可以帮你查看这些文件。
我可以问一下，这些崩溃是只在某一个游戏中发生，还是所有游戏都会？ 你有没有看到蓝屏上的错误代码或提示信息？
希望这个回答对你有帮助。 如果你还有其他问题，欢迎随时回复。
此致敬礼，
圣诞颂歌
-
梦晖 陈 20 信誉分
2025-11-05T11:26:19.3833333+00:00 这是WinDbg上的分析内容
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110425-6890-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff805`13000000 PsLoadedModuleList = 0xfffff805`13c2a930 Debug session time: Tue Nov 4 22:34:00.567 2025 (UTC + 8:00) System Uptime: 0 days 0:55:54.323 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: fffff805`133fd570 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffbd82`31b8f740=0000000000000113 0: kd> !analyze -v 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 .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000002 Arg3: 00000000000010de Arg4: 0000000000002191 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1546 Key : Analysis.Elapsed.mSec Value: 15496 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 1 Key : Analysis.Init.CPU.mSec Value: 843 Key : Analysis.Init.Elapsed.mSec Value: 45796 Key : Analysis.Memory.CommitPeak.Mb Value: 114 Key : Analysis.Version.DbgEng Value: 10.0.29457.1000 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff8054596f9b3 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0xe3f9b3 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 2 BUGCHECK_P3: 10de BUGCHECK_P4: 2191 FILE_IN_CAB: 110425-6890-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump FAULTING_THREAD: ffffc28203c1a040 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffbd82`31b8f738 fffff805`299b3ad0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx ffffbd82`31b8f740 fffff805`297f70da : ffffc281`f2c94180 ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94180 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffffbd82`31b8f780 fffff805`29775721 : ffffc281`f6816000 fffff805`4592d400 ffffc281`00000000 ffffc281`effaa600 : dxgkrnl!DpiFdoHandleDevicePower+0x8111a ffffbd82`31b8f820 fffff805`29776c51 : ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94030 00000028`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21 ffffbd82`31b8f850 fffff805`4596f9b3 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffc281`f6816000 : dxgkrnl!DpiDispatchPower+0xe1 ffffbd82`31b8f970 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c : nvlddmkm+0xe3f9b3 ffffbd82`31b8f978 00000000`00000000 : 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c ffffc282`00000004 : 0x1 SYMBOL_NAME: nvlddmkm+e3f9b3 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffc281e60a0040; .thread 0xffffc28203c1a040 ; kb BUCKET_ID_FUNC_OFFSET: e3f9b3 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner --------- 0: kd> .process /r /p 0xffffc281e60a0040; .thread 0xffffc28203c1a040 ; kb Implicit process is now ffffc281`e60a0040 Loading User Symbols ************* Symbol Loading Error Summary ************** Module name Error nvlddmkm The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. Implicit thread is now ffffc282`03c1a040 *** Stack trace for last set context - .thread/.cxr resets it # RetAddr : Args to Child : Call Site 00 fffff805`299b3ad0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx 01 fffff805`297f70da : ffffc281`f2c94180 ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94180 : watchdog!WdLogEvent5_WdCriticalError+0xe0 02 fffff805`29775721 : ffffc281`f6816000 fffff805`4592d400 ffffc281`00000000 ffffc281`effaa600 : dxgkrnl!DpiFdoHandleDevicePower+0x8111a 03 fffff805`29776c51 : ffffc281`effaa410 ffffc281`f2c94180 ffffc281`f2c94030 00000028`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21 04 fffff805`4596f9b3 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffc281`f6816000 : dxgkrnl!DpiDispatchPower+0xe1 05 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c : nvlddmkm+0xe3f9b3 06 00000000`00000000 : 00000000`00000000 ffffc281`f6816000 ffffbd82`31b8fa1c ffffc282`00000004 : 0x1
登录以评论 -