This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(44.800000000000004, 18%, 14%)' 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)
These are from windbg. I encountered them when I tried to run the APEX.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\liang\Desktop\随用\012323-10109-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff806`75800000 PsLoadedModuleList = 0xfffff806`76413010
Debug session time: Mon Jan 23 12:48:53.407 2023 (UTC + 8:00)
System Uptime: 0 days 0:00:56.099
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`75c28f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff918a`f6e1f6b0=0000000000000113
2: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000002520
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1530
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 16511
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 31
Key : Analysis.Init.CPU.mSec
Value: 186
Key : Analysis.Init.Elapsed.mSec
Value: 27548
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.DumpHeader
Value: 0x113
Key : Bugcheck.Code.Register
Value: 0x113
Key : DirectX.FatalError.Code
Value: 19
Key : DirectX.FatalError.Desc
Value: UNEXPECTED_DEFERRED_DESTRUCTION
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 012323-10109-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 113
BUGCHECK_P1: 19
BUGCHECK_P2: 2
BUGCHECK_P3: 10de
BUGCHECK_P4: 2520
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff918a`f6e1f6a8 fffff806`92925685 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffff918a`f6e1f6b0 fffff806`927251a1 : ffffa782`e2a59100 ffffa782`de246c20 ffffa782`de246c28 ffffa782`de246c30 : watchdog!WdLogSingleEntry5+0x3b45
ffff918a`f6e1f760 fffff806`9267c601 : ffffa782`e2a59030 fffff806`75b53200 00000000`00000000 ffffa782`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0xa8701
ffff918a`f6e1f800 fffff806`9267e031 : ffffa782`e80a98e0 ffffa782`e2a59180 ffffa782`e2a59030 00000000`00000000 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff918a`f6e1f830 fffff806`a330806f : ffffa782`e2b86000 ffffa782`eb12a000 ffffa782`e2b86000 ffffa782`e80a9ad0 : dxgkrnl!DpiDispatchPower+0xe1
ffff918a`f6e1f950 ffffa782`e2b86000 : ffffa782`eb12a000 ffffa782`e2b86000 ffffa782`e80a9ad0 ffffa782`00000004 : nvlddmkm+0xff806f
ffff918a`f6e1f958 ffffa782`eb12a000 : ffffa782`e2b86000 ffffa782`e80a9ad0 ffffa782`00000004 00000000`00000000 : 0xffffa782`e2b86000
ffff918a`f6e1f960 ffffa782`e2b86000 : ffffa782`e80a9ad0 ffffa782`00000004 00000000`00000000 00000000`00000001 : 0xffffa782`eb12a000
ffff918a`f6e1f968 ffffa782`e80a9ad0 : ffffa782`00000004 00000000`00000000 00000000`00000001 00000000`000000ff : 0xffffa782`e2b86000
ffff918a`f6e1f970 ffffa782`00000004 : 00000000`00000000 00000000`00000001 00000000`000000ff ffffa782`e2b86000 : 0xffffa782`e80a9ad0
ffff918a`f6e1f978 00000000`00000000 : 00000000`00000001 00000000`000000ff ffffa782`e2b86000 00000000`00000000 : 0xffffa782`00000004
SYMBOL_NAME: nvlddmkm+ff806f
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: ff806f
FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\liang\Desktop\随用\012323-12359-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`7d600000 PsLoadedModuleList = 0xfffff803`7e213010
Debug session time: Mon Jan 23 12:52:46.961 2023 (UTC + 8:00)
System Uptime: 0 days 0:03:03.654
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:
fffff803`7da28f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9b84`110b76b0=0000000000000113
7: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000002520
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4737
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 202
Key : Analysis.Init.Elapsed.mSec
Value: 72470
Key : Analysis.Memory.CommitPeak.Mb
Value: 106
Key : Bugcheck.Code.DumpHeader
Value: 0x113
Key : Bugcheck.Code.Register
Value: 0x113
Key : DirectX.FatalError.Code
Value: 19
Key : DirectX.FatalError.Desc
Value: UNEXPECTED_DEFERRED_DESTRUCTION
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
FILE_IN_CAB: 012323-12359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 113
BUGCHECK_P1: 19
BUGCHECK_P2: 2
BUGCHECK_P3: 10de
BUGCHECK_P4: 2520
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9b84`110b76a8 fffff803`9d395685 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffff9b84`110b76b0 fffff803`9d1951a1 : ffffd683`d46d9100 ffffd683`d4036850 ffffd683`d4036858 ffffd683`d4036860 : watchdog!WdLogSingleEntry5+0x3b45
ffff9b84`110b7760 fffff803`9d0ec601 : ffffd683`d46d9030 00000000`00989600 00000000`00000000 ffffd683`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0xa8701
ffff9b84`110b7800 fffff803`9d0ee031 : ffffd683`dd852870 ffffd683`d46d9180 ffffd683`d46d9030 ffff9b84`110b7920 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff9b84`110b7830 fffff803`aa8c806f : ffffd683`d4692000 ffffd683`dfe4e000 ffffd683`d4692000 ffffd683`dd852a60 : dxgkrnl!DpiDispatchPower+0xe1
ffff9b84`110b7950 ffffd683`d4692000 : ffffd683`dfe4e000 ffffd683`d4692000 ffffd683`dd852a60 ffffd683`00000004 : nvlddmkm+0xff806f
ffff9b84`110b7958 ffffd683`dfe4e000 : ffffd683`d4692000 ffffd683`dd852a60 ffffd683`00000004 00000000`00000000 : 0xffffd683`d4692000
ffff9b84`110b7960 ffffd683`d4692000 : ffffd683`dd852a60 ffffd683`00000004 00000000`00000000 00000000`00000001 : 0xffffd683`dfe4e000
ffff9b84`110b7968 ffffd683`dd852a60 : ffffd683`00000004 00000000`00000000 00000000`00000001 00000000`000000ff : 0xffffd683`d4692000
ffff9b84`110b7970 ffffd683`00000004 : 00000000`00000000 00000000`00000001 00000000`000000ff ffffd683`d4692000 : 0xffffd683`dd852a60
ffff9b84`110b7978 00000000`00000000 : 00000000`00000001 00000000`000000ff ffffd683`d4692000 00000000`00000000 : 0xffffd683`00000004
SYMBOL_NAME: nvlddmkm+ff806f
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: ff806f
FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f}
Followup: MachineOwner
---------
3.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\liang\Desktop\随用\012323-12468-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff806`7fc00000 PsLoadedModuleList = 0xfffff806`80813010
Debug session time: Mon Jan 23 12:47:45.604 2023 (UTC + 8:00)
System Uptime: 0 days 0:00:51.297
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
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
nvlddmkm+0x472a86:
fffff806`ab852a86 49f7f1 div rax,r9
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff806ab852a86, The address that the exception occurred at
Arg3: fffffb8918f3eba8, Exception Record Address
Arg4: fffffb8918f3e3c0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1781
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10394
Key : Analysis.IO.Other.Mb
Value: 1
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 10
Key : Analysis.Init.CPU.mSec
Value: 233
Key : Analysis.Init.Elapsed.mSec
Value: 52654
Key : Analysis.Memory.CommitPeak.Mb
Value: 105
Key : Bugcheck.Code.DumpHeader
Value: 0x1000007e
Key : Bugcheck.Code.Register
Value: 0x20
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
FILE_IN_CAB: 012323-12468-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000094
BUGCHECK_P2: fffff806ab852a86
BUGCHECK_P3: fffffb8918f3eba8
BUGCHECK_P4: fffffb8918f3e3c0
EXCEPTION_RECORD: fffffb8918f3eba8 -- (.exr 0xfffffb8918f3eba8)
ExceptionAddress: fffff806ab852a86 (nvlddmkm+0x0000000000472a86)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffffb8918f3e3c0 -- (.cxr 0xfffffb8918f3e3c0)
rax=000000017e67ffff rbx=ffffdb844d428000 rcx=0000000000000020
rdx=0000000000000000 rsi=ffffdb844d423000 rdi=ffffdb844d423000
rip=fffff806ab852a86 rsp=fffffb8918f3ede0 rbp=0000000000000000
r8=000000017e680000 r9=0000000000000000 r10=0000000000000000
r11=fffffb8918f3ebb0 r12=0000000000000005 r13=ffffdb8442010000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
nvlddmkm+0x472a86:
fffff806`ab852a86 49f7f1 div rax,r9
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000094 - { } 0
EXCEPTION_CODE_STR: c0000094
EXCEPTION_STR: 0xc0000094
STACK_TEXT:
fffffb89`18f3ede0 fffff806`abe89988 : ffffdb84`37268c48 00000000`00000000 00000000`00000001 00000000`00000000 : nvlddmkm+0x472a86
fffffb89`18f3ede8 ffffdb84`37268c48 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff806`ab85831d : nvlddmkm+0xaa9988
fffffb89`18f3edf0 00000000`00000000 : 00000000`00000001 00000000`00000000 fffff806`ab85831d ffffdb84`4d428000 : 0xffffdb84`37268c48
SYMBOL_NAME: nvlddmkm+472a86
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffffb8918f3e3c0 ; kb
BUCKET_ID_FUNC_OFFSET: 472a86
FAILURE_BUCKET_ID: 0x7E_C0000094_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {89d11fb4-8344-29d7-bdc6-1079f6a02ee9}
Followup: MachineOwner
---------
4.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\liang\Desktop\随用\012323-13359-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`10200000 PsLoadedModuleList = 0xfffff800`10e13010
Debug session time: Mon Jan 23 12:46:43.622 2023 (UTC + 8:00)
System Uptime: 1 days 1:01:40.484
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:
fffff800`10628f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`0dbf69b0=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: fffff80010f1c340, 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
*************************************************************************
*** ***
*** ***
*** 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: 2109
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3812
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 203
Key : Analysis.Init.Elapsed.mSec
Value: 13586
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
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
FILE_IN_CAB: 012323-13359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80010f1c340
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff800`0dbf69a8 fffff800`10427a6f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`10f1c340 : nt!KeBugCheckEx
fffff800`0dbf69b0 fffff800`104268a4 : 000072ad`9b5b2e08 fffff800`0d926180 00000000`0057fd1e 00000000`00000000 : nt!KeAccumulateTicks+0x23f
fffff800`0dbf6a10 fffff800`10426786 : 00000000`00000014 00000000`00000000 fffff800`0d926180 000000d1`c811a700 : nt!KiUpdateRunTime+0xf4
fffff800`0dbf6bd0 fffff800`104249ae : 00000000`00000000 fffff800`0d926180 ffffffff`ffffffff 00000000`00000002 : nt!KiUpdateTime+0x13e6
fffff800`0dbf6e90 fffff800`104241ba : fffff800`10e5fd38 fffff800`10f0de60 fffff800`10f0de60 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff800`0dbf6f40 fffff800`10544d5e : 000000d1`c88e954e fffff800`10f0ddb0 fffff800`0d926180 fffff800`1062ae1b : nt!HalpTimerClockInterrupt+0x10a
fffff800`0dbf6f70 fffff800`1062b07a : fffff800`0dbe7280 fffff800`10f0ddb0 fffff800`0dbe7b20 fffff800`0d926180 : nt!KiCallInterruptServiceRoutine+0x19e
fffff800`0dbf6fb0 fffff800`1062b8e7 : fffff800`0dbe7220 00000000`00000014 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`0dbe7200 fffff800`3bb8b0a0 : fffff800`104bd9fa 00000000`00000000 ffffb683`2fad0000 ffffcd00`9486cbf0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`0dbe7398 fffff800`104bd9fa : 00000000`00000000 ffffb683`2fad0000 ffffcd00`9486cbf0 fffff800`00000002 : nvlddmkm+0x9b0a0
fffff800`0dbe73a0 fffff800`104bd204 : 00000000`000001e0 fffff800`0dbe79f0 fffff800`10f4c6c0 00000000`00000000 : nt!KiExecuteAllDpcs+0x54a
fffff800`0dbe78f0 fffff800`1062dd1e : 00000000`00000000 fffff800`0d926180 fffff800`10f4c6c0 ffffb683`4dded080 : nt!KiRetireDpcList+0xfe4
fffff800`0dbe7b80 00000000`00000000 : fffff800`0dbe8000 fffff800`0dbe1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nvlddmkm+9b0a0
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 9b0a0
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
Hello
Thank you for posting here.
The VIDEO_DXGKRNL_FATAL_ERROR bugcheck has a value of 0x00000113. This indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation.
It is recommended to update the graphics card driver to the latest.
Best Regards,
Wesley Li