0x133_ISR_nvlddmkm!unknown_function

Question

Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\122023-9375-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff802`47e00000 PsLoadedModuleList = 0xfffff802`48a134a0
Debug session time: Wed Dec 20 17:51:44.865 2023 (UTC + 8:00)
System Uptime: 0 days 0:09:55.547
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000a7`06251018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`48216b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff802`4edbcc90=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: fffff80248b1d340, 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: 608

    Key  : Analysis.Elapsed.mSec
    Value: 13089

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80248b1d340

BUGCHECK_P4: 0

FILE_IN_CAB:  122023-9375-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8024edb4e50 -- (.trap 0xfffff8024edb4e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000002e0405
rdx=0000000000b81014 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8026f5298bc rsp=fffff8024edb4fe0 rbp=ffff958f2998fbe8
 r8=fffff8024edb5028  r9=0000000000b81014 r10=ffff958f29992c38
r11=fffff8024edb5060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x998bc:
fffff802`6f5298bc 488b5c2430      mov     rbx,qword ptr [rsp+30h] ss:fffff802`4edb5010=ffff958f2998f000
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NarakaBladepoint.exe

STACK_TEXT:  
fffff802`4edbcc88 fffff802`48012bb9     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`48b1d340 : nt!KeBugCheckEx
fffff802`4edbcc90 fffff802`48012421     : 00000180`d3adcc29 00000000`000094e3 00000000`000094e2 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff802`4edbccf0 fffff802`480104b1     : 00000000`00000000 ffff8401`64f7f600 fffff802`46318180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff802`4edbcea0 fffff802`4800feda     : fffff802`48a60088 ffff8401`64f7f6f0 ffff8401`64f7f6f0 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
fffff802`4edbcf40 fffff802`48124b2c     : 00000001`631147fc fffff802`48b0d5b0 fffff802`48b0d660 00000000`ffffffff : nt!HalpTimerClockInterrupt+0x10a
fffff802`4edbcf70 fffff802`48218cba     : fffff802`4edb4ed0 fffff802`48b0d5b0 ffff958f`2998fbe8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff802`4edbcfb0 fffff802`48219567     : 00000000`00000004 ffff958f`00000000 00000000`05000000 00000000`00000030 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`4edb4e50 fffff802`6f5298bc     : 00000000`00000000 00000000`00b81014 ffff958f`2998f000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`4edb4fe0 00000000`00000000     : 00000000`00b81014 ffff958f`2998f000 00000000`00000000 00000000`00000020 : nvlddmkm+0x998bc

SYMBOL_NAME:  nvlddmkm+998bc

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  998bc

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------

Answer 1

更新顯卡驅動程式。

Answer 2

我需要该怎么做😭

Answer 3

我需要該怎麼做 😭

官方驅動程式 |英偉達

官方 GeForce 驅動程式 | NVIDIA

Answer 4

不 我不是显卡，显卡从重新安装过了，系统也同样是重装过的😭

Answer 5

IMAGE_NAME:  nvlddmkm.sys

這是顯卡驅動程式。