以下是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.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022525-10078-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 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff803`7f200000 PsLoadedModuleList = 0xfffff803`7fe13510
Debug session time: Tue Feb 25 00:46:12.764 2025 (UTC + 8:00)
System Uptime: 1 days 23:42:28.078
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
........................
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp 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.
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`7f614c00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`84d559f0=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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8037ff1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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: nt!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KINTERRUPT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KTHREAD ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 15
Key : Analysis.Elapsed.mSec
Value: 4362
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 93
Key : Analysis.Init.Elapsed.mSec
Value: 58603
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Bugcheck.Code.TargetModel
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 1008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: WRONG_SYMBOLS_X64_10.0.22621.4890_(WinBuild.160101.0800)_TIMESTAMP_090501-174839_49FB35F7_nt_wrong_symbols!49FB35F71047000
Key : Failure.Hash
Value: {7dfc0e7f-dfab-cde8-f46b-db29954bb820}
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8037ff1c340
BUGCHECK_P4: 0
FILE_IN_CAB: 022525-10078-01.dmp
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 49fb35f7
WRONG_SYMBOLS_SIZE: 1047000
FAULTING_MODULE: fffff8037f200000 nt
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
FAULTING_THREAD: fffff8037ff4c700
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffff803`84d559e8 fffff803`7f4398f9 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`7ff1c340 : nt!KeBugCheckEx
fffff803`84d559f0 fffff803`7f439161 : 000078c4`2d5b915a 00000000`00a7b905 00000000`00a7b904 00000000`00000000 : nt!KeClockInterruptNotify+0x27c9
fffff803`84d55a50 fffff803`7f43676f : 00000000`00000018 00000000`00001388 00000000`00a7b900 00000000`0063f875 : nt!KeClockInterruptNotify+0x2031
fffff803`84d55c00 fffff803`7f437358 : 00000000`00000000 ffffd680`bd96fb00 fffff803`7d383180 00000000`00000000 : nt!ObReferenceObjectSafeWithTag+0x68f
fffff803`84d55ea0 fffff803`7f436c1a : fffff803`7fe5fe68 ffffd680`bd96fbf0 ffffd680`bd96fbf0 00000000`00000000 : nt!KeClockInterruptNotify+0x228
fffff803`84d55f40 fffff803`7f5152bc : 0000018f`e2df0fe6 fffff803`7ff0d470 fffff803`7ff0d520 00000000`ffffffff : nt!ObReferenceObjectSafeWithTag+0xb3a
fffff803`84d55f70 fffff803`7f616e0a : fffff803`84d45b00 fffff803`7ff0d470 ffff8800`051bcd80 ffff8800`051bcd80 : nt!FsRtlAreNamesEqual+0x1ac
fffff803`84d55fb0 fffff803`7f6176d7 : ffff8800`00000001 fffff803`7d383180 ffffd680`00000000 ffffd680`ae952180 : nt!KeSynchronizeExecution+0xa3a
fffff803`84d45a80 fffff803`af59c233 : 00000000`00000001 fffff803`af5b3049 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x1307
fffff803`84d45c10 00000000`00000001 : fffff803`af5b3049 00000000`00000000 00000000`00000000 00000000`00b81000 : nvlddmkm+0xdc233
fffff803`84d45c18 fffff803`af5b3049 : 00000000`00000000 00000000`00000000 00000000`00b81000 ffff9d80`0b2068dc : 0x1
fffff803`84d45c20 00000000`00000000 : 00000000`00000000 00000000`00b81000 ffff9d80`0b2068dc 00000000`00b81010 : nvlddmkm+0xf3049
STACK_COMMAND: .thread /r /p 0xfffff8037ff4c700 ; kb
EXCEPTION_CODE_STR: 49FB35F7
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!49FB35F71047000
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_10.0.22621.4890_(WinBuild.160101.0800)_TIMESTAMP_090501-174839_49FB35F7_nt_wrong_symbols!49FB35F71047000
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7dfc0e7f-dfab-cde8-f46b-db29954bb820}
Followup: MachineOwner
---------
DPC_WATCHDOG_VIOLATION蓝屏
- 订阅
- 订阅 RSS 源
|
举报滥用情况
详细信息(必填):
谢谢。
已提交报告的内容
你好，郭宇昕
欢迎来到微软社区。
我看到您的系统在日常使用中遇到了问题，从您提供的日志来看，蓝屏问题主要与 NVIDIA 显卡驱动（nvlddmkm.sys）相关，这通常是由于驱动程序未能及时响应系统调用或在高负载下出现问题所致。您可以回想一下近期是否执行过任何的系统、驱动程序的更新，这可能是问题的导火索之一。
我建议您先访问 NVIDIA 官方网站，下载并安装最新驱动程序。建议选择“自定义安装”并勾选“干净安装”，以移除旧版本驱动，避免冲突。建议使用诸如 DDU的工具来彻底清除当前驱动程序和其残留的文件、注册表项，避免由于驱动程序更新不完全或文件冲突导致的问题，从而为新的驱动安装提供一个干净的基础。此外，除了直接使用最新版本的显卡驱动，建议您安装几个旧版本的驱动程序分别试试看。
如果需要进一步的分析具体的错误原因，我推荐您可以将转储文件直接上传到云端软件（比如百度网盘或者OneDrive等），我将会进一步结合其中的信息进行调查。此外，您也可以与我分享更多的细节，比如：
您是在多久以前出现的问题，在出现以前是否执行过任何比如系统更新、删除或者添加特定的进程应用、BIOS更新等更改操作？
蓝屏或黑屏通常发生在什么情况下，比如启动特定的应用、运行游戏或者长时间待机以后？
经过以上的步骤将为我们提供一些提示，感谢您的理解和合作！祝您生活愉快，身体健康！
Rota |微软社区支持专员
举报滥用情况
详细信息(必填):
谢谢。
已提交报告的内容
此回复是否有帮助？
抱歉，这没有帮助。
太棒了！ 感谢你的反馈。
你对此回复的满意度如何?
感谢你的反馈，它能帮助我们改进网站。
你对此回复的满意度如何?
感谢你的反馈。