通过

电脑最近频繁死机，使用windbg分析结果如下，请问该如何解决呢？

ico t 0 信誉分
2025-12-11T02:56:58.08+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.359 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29482.1003 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\121125-13453-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 26100 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff801a0600000 PsLoadedModuleList = 0xfffff801a14f5010

Debug session time: Thu Dec 11 10:14:58.362 2025 (UTC + 8:00)

System Uptime: 0 days 1:22:43.991

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:

fffff801a0afb310 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa03968ef2e0=000000000000019c

9: 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                                    *

  •                                                                         *

WIN32K_POWER_WATCHDOG_TIMEOUT (19c)

Win32k did not turn the monitor on in a timely manner.

Arguments:

Arg1: 0000000000000050, Calling monitor driver to power on.

Arg2: ffffaf034673a080, Pointer to the power request worker thread.

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 2515

Key  : Analysis.Elapsed.mSec

Value: 387927

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 45

Key  : Analysis.Init.CPU.mSec

Value: 1921

Key  : Analysis.Init.Elapsed.mSec

Value: 442163

Key  : Analysis.Memory.CommitPeak.Mb

Value: 112

Key  : Analysis.Version.DbgEng

Value: 10.0.29482.1003

Key  : Analysis.Version.Description

Value: 10.2509.29.03 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2509.29.3

Key  : Bugcheck.Code.LegacyAPI

Value: 0x19c

Key  : Bugcheck.Code.TargetModel

Value: 0x19c

Key  : Dump.Attributes.AsUlong

Value: 0x21008

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: 0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusiveWithTracking

Key  : Failure.Hash

Value: {95ab60d9-2b98-256d-1506-a2e5b3ccc3f3}

Key  : WER.System.BIOSRevision

Value: 5.29.0.0

BUGCHECK_CODE: 19c

BUGCHECK_P1: 50

BUGCHECK_P2: ffffaf034673a080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 121125-13453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008

Kernel Generated Triage Dump

FAULTING_THREAD: ffffaf034673a080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

fffffa039115e4a0 fffff801a085a764 : ffff8b81703a7180 ffff8b81703a7198 0000000000000000 ffffaf0346832280 : nt!KiSwapContext+0x76

fffffa039115e5e0 fffff801a0915cad : 0000000000000000 0000000000000000 fffffa039115e770 fffff80100000011 : nt!KiSwapThread+0x6d4

fffffa039115e670 fffff801a0913ec9 : ffffaf0300000000 0000000000000002 0000000000000011 0000000b9044539e : nt!KiCommitThreadWait+0x39d

fffffa039115e700 fffff801a089fa02 : fffffa039115e8e8 ffffaf030000001b 0000000000000000 0000ff0000000000 : nt!KeWaitForSingleObject+0x859

fffffa039115e7e0 fffff801a089f0f4 : ffffaf03613b0d90 fffffa039115e8d0 ffffaf0300010224 000000000000002d : nt!ExpWaitForResource+0x72

fffffa039115e870 fffff801328cf53c : ffffaf0361520000 0000000000000002 0000000000000002 0000000000000001 : nt!ExAcquireResourceExclusiveLite+0x5e4

fffffa039115e980 fffff801327d5f67 : ffffaf034ce95000 0000000000000001 0000000000000001 ffffaf03613b0df0 : dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusiveWithTracking+0x58

fffffa039115eb40 fffff801327d5a98 : 0000000000000002 0000000000000000 fffffa039115ec90 0000000000000000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusive+0x117

fffffa039115ebc0 fffff801327d5893 : 0000000000000002 0000000000000000 0000000000000000 ffffaf034feeb0d8 : dxgkrnl!DXGADAPTER::AcquireCoreSync+0xc4

fffffa039115ec20 fffff801327d565c : ffffaf034feea180 0000000000000000 0000000000000001 0000000000000001 : dxgkrnl!DxgkAcquireAdapterCoreSync+0x83

fffffa039115eca0 fffff8013293b624 : ffffaf034feea030 fffffa039115edb9 0000000000000000 ffffaf034feea180 : dxgkrnl!DpiAcquireCoreSyncAccessSafe+0xf4

fffffa039115ecd0 fffff8013293e35e : 000000000000000e 0000000000000000 ffffaf034673a080 fffff801327be2b4 : dxgkrnl!DxgkPowerOnOffMonitor+0x840

fffffa039115ee10 fffff801328ac4ff : ffffaf03ffffffff ffffaf039044f9f0 fffffa039115ef89 ffffaf035e91dc30 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x5fe

fffffa039115eec0 fffff8016fb083c6 : ffffaf039044f9f0 ffffaf039044fac0 ffffaf039044f9f0 00000000c0000225 : dxgkrnl!DpiDispatchInternalIoctl+0xff

fffffa039115eff0 ffffaf039044f9f0 : ffffaf039044fac0 ffffaf039044f9f0 00000000c0000225 fffffa039115f1a8 : nvlddmkm+0x19a83c6

fffffa039115eff8 ffffaf039044fac0 : ffffaf039044f9f0 00000000c0000225 fffffa039115f1a8 ffffaf039044f9f0 : 0xffffaf03`9044f9f0

fffffa039115f000 ffffaf039044f9f0 : 00000000c0000225 fffffa039115f1a8 ffffaf039044f9f0 0000000000000014 : 0xffffaf03`9044fac0

fffffa039115f008 00000000c0000225 : fffffa039115f1a8 ffffaf039044f9f0 0000000000000014 fffff801a088da6b : 0xffffaf03`9044f9f0

fffffa039115f010 fffffa039115f1a8 : ffffaf039044f9f0 0000000000000014 fffff801a088da6b 00000000c0000002 : 0xc0000225

fffffa039115f018 ffffaf039044f9f0 : 0000000000000014 fffff801a088da6b 00000000c0000002 0000000000000000 : 0xfffffa03`9115f1a8

fffffa039115f020 0000000000000014 : fffff801a088da6b 00000000c0000002 0000000000000000 ffffaf035e91dae0 : 0xffffaf03`9044f9f0

fffffa039115f028 fffff801a088da6b : 00000000c0000002 0000000000000000 ffffaf035e91dae0 ffffaf039044f9f0 : 0x14

fffffa039115f030 fffff801a088d9e3 : ffffc30317746001 fffffa039115f100 fffffa039115f0f0 fffff8017c897d03 : nt!IopfCallDriver+0x5b

fffffa039115f070 fffff8017c897d34 : ffffc3033ed225f0 0000000000000002 ffffc3033ed225f0 fffff8017c9346e4 : nt!IofCallDriver+0x13

fffffa039115f0a0 fffff8017c8a4c6a : ffffc3033ed225f0 fffffa039115f1a9 ffffc3033ed225f0 0000000000000001 : win32kbase!GreDeviceIoControlImpl+0x104

fffffa039115f140 fffff8017c8a4a0f : 0000000000000000 0000000000000000 fffff801324ee9c8 0000000000000000 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x23a

fffffa039115f210 fffff8017c8f27ab : ffffaf0378112000 0000000000000000 0000000000000000 0000000000000000 : win32kbase!DrvSetMonitorPowerState+0x2f

fffffa039115f240 fffff8017c938dfa : 0000000000000000 fffffa039115f319 000000000000000f fffff80100000001 : win32kbase!PowerOnMonitor+0x19b

fffffa039115f2b0 fffff8017c937edd : ffffaf0363cf98e0 ffffaf03906c1f70 0000000000000001 0000000000000020 : win32kbase!xxxUserPowerEventCalloutWorker+0xaaa

fffffa039115f380 fffff8017c3c3fc2 : ffffaf034673a080 fffffa039115f4e0 0000000000000000 0000000000000020 : win32kbase!xxxUserPowerCalloutWorker+0x13d

fffffa039115f400 fffff80132417b2a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : win32kfull!NtUserUserPowerCalloutWorker+0x22

fffffa039115f430 fffff801a0cb5658 : 00000000000005bf 0000000000000100 ffffaf034673a080 0000000000000000 : win32k!EngAllocMem+0x1ea

fffffa039115f460 00007ffb872bca84 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28

000000db3d5ffd48 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`872bca84

SYMBOL_NAME: dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusiveWithTracking+58

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffaf03612ca180; .thread 0xffffaf034673a080 ; kb

BUCKET_ID_FUNC_OFFSET: 58

FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusiveWithTracking

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {95ab60d9-2b98-256d-1506-a2e5b3ccc3f3}

Followup: MachineOwner

Windows 家庭版 | Windows 11 | 性能和系统故障
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Carl-L 4,155 信誉分 Microsoft 外部员工 仲裁人
    2025-12-11T09:41:10.72+00:00

    免责声明：请注意，所提供的信息是通过自动翻译工具翻译而成的。尽管我们力求准确，但翻译内容可能无法完全准确地反映源内容的原始含义、上下文或意图。

    您好ico t，

    欢迎来到微软问答论坛。很高兴能为您服务。

    我了解到您的电脑正在经历崩溃问题。您发送的分析结果表明问题出在显卡驱动上。因此我们首先应该尝试更新或重新安装驱动程序。

    1. 在搜索栏中输入“设备管理器”，然后按下回车键。
    2. 右键点击您的图形驱动程序 > 更新驱动程序。
    3. 如果以上方法无效，请选择“卸载驱动程序”并重新启动计算机。

    你说崩溃现象多次发生，请问除了这个文件外是否还有其他迷你转储文件？错误信息是否相同？

    若此回答对您有帮助，请点击“接受答案”并给予好评。若对此回答有其他疑问，请点击“评论”。

    注意：如需接收本讨论串的相关邮件通知，请按照文档中的步骤启用邮件通知功能。

你的答案

提问者可以将答案标记为“已接受”，版主可以将答案标记为“已推荐”，这有助于用户了解答案是否解决了提问者的问题。