通过

电脑卡主，蓝屏重启（WIN10企业版系统，3090显卡），系统日志分析指向显卡，但是不知道具体是什么原因

匿名
2024-12-07T04:22:34+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.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:\Users\77560\Desktop\新建文件夹 (9)\120624-10531-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 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`18e01000 PsLoadedModuleList = 0xfffff806`192209b0
Debug session time: Fri Dec  6 23:04:47.777 2024 (UTC + 8:00)
System Uptime: 0 days 0:05:34.672
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:
fffff806`18fb2040 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff806`1b8a1bb0=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: fffff806192c5380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 843

    Key  : Analysis.Elapsed.mSec
    Value: 11657

    Key  : Analysis.IO.Other.Mb
    Value: 18

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 25

    Key  : Analysis.Init.CPU.mSec
    Value: 343

    Key  : Analysis.Init.Elapsed.mSec
    Value: 440427

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93

    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: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x3d78af7a

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Stack.Pointer
    Value: ISR

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806192c5380

BUGCHECK_P4: 0

FILE_IN_CAB:  120624-10531-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff806192e2400

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff806`1b8a1ba8 fffff806`190048f7     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`192c5380 : nt!KeBugCheckEx
fffff806`1b8a1bb0 fffff806`18e79f84     : 0000010a`578e01f0 00000000`00000000 00000000`000053ab fffff806`176c3180 : nt!KeAccumulateTicks+0x187837
fffff806`1b8a1c10 fffff806`197f3332     : 00000000`00000000 fffff806`19857b48 fffff806`1b8923a0 00000000`00000002 : nt!KeClockInterruptNotify+0x604
fffff806`1b8a1f30 fffff806`18ee4a15     : 00000000`c791e403 fffff806`1985a7e0 fffff806`1985a890 ffff7cb0`dc3b43a6 : hal!HalpTimerClockInterrupt+0xf2
fffff806`1b8a1f60 fffff806`18fb3a3a     : fffff806`1b8923a0 fffff806`1985a7e0 fffff806`1b892640 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`1b8a1fb0 fffff806`18fb3f87     : ffffffff`0000000b fffff806`192c66c0 ffffffff`ffffffff fffff806`18fb0001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`1b892320 fffff803`1577072c     : ffffaa0b`328e2000 00000000`00000000 ffffaa0b`328e2000 00000000`00000100 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`1b8924b0 ffffaa0b`328e2000     : 00000000`00000000 ffffaa0b`328e2000 00000000`00000100 00000000`00000010 : nvlddmkm+0x9072c
fffff806`1b8924b8 00000000`00000000     : ffffaa0b`328e2000 00000000`00000100 00000000`00000010 fffff803`15864c04 : 0xffffaa0b`328e2000

SYMBOL_NAME:  nvlddmkm+9072c

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xfffff806192df9c0; .thread 0xfffff806192e2400 ; kb

BUCKET_ID_FUNC_OFFSET:  9072c

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
Windows 适用于 IT 专业人员的 Windows 客户端性能和维护系统性能

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。 为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

0 个注释
接受的答案
  1. 匿名
    2024-12-09T06:28:46+00:00

    此响应已自动翻译。 因此，可能存在语法错误或奇异的措辞。

    你好

    感谢您在 Microsoft 社区论坛中发帖。

    根据描述，我知道您的问题与蓝屏死机有关。

    DPC_WATCHDOG_VIOLATION bug 检查的值为 0x00000133。此 bug 检查指示 DPC 监视器执行，要么是因为它检测到单个长时间运行的延迟过程调用 （DPC），要么是因为系统在 DISPATCH_LEVEL 或更高的中断请求级别 （IRQL） 花费了很长时间。

    根据错误，BSOD 是由故障的模块引起的nvlddmkm.sys

    这 nvlddmkm.sys file 是与 NVIDIA 显卡关联的系统文件。它负责管理操作系统和显卡之间的通信。 

    尝试将驱动器更新到最新版本或暂时卸载驱动程序并监控此问题。

    有好的一天。 

    此致敬意

    莫莉

    0 个注释

0 个其他答案

排序依据： 非常有帮助
非常有帮助 最新 最早