Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\maksu\Downloads\Compressed\MiniDump\123020-6187-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`36000000 PsLoadedModuleList = 0xfffff804`36c2a2b0
Debug session time: Wed Dec 30 00:02:51.204 2020 (UTC + 3:00)
System Uptime: 0 days 0:00:19.809
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`363f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe106`a9d1f9e0=0000000000000116
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9908700a7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff804491339ac, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_bf4ac33d64df761f\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 19171
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 48433
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff9908700a7010
BUGCHECK_P2: fffff804491339ac
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe106`a9d1f9d8 fffff804`454c13ee : 00000000`00000116 ffff9908`700a7010 fffff804`491339ac ffffffff`c000009a : nt!KeBugCheckEx
ffffe106`a9d1f9e0 fffff804`45471c54 : fffff804`491339ac ffff9908`6fccd6e0 00000000`00002000 ffff9908`6fccd7a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe106`a9d1fa20 fffff804`4546a7cf : ffff9908`6fca8000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe106`a9d1fa50 fffff804`454c0b15 : 00000000`00000100 ffff9908`6fca8a58 00000000`36d24440 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffe106`a9d1fad0 fffff804`454c0c87 : fffff804`36d24440 fffff804`36c248c8 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe106`a9d1fb00 fffff804`36225975 : ffff9908`6d855040 fffff804`454c0c60 ffff9908`66ea4c70 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe106`a9d1fb30 fffff804`36317e25 : ffff9908`6d855040 00000000`00000080 ffff9908`66ea0040 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffffe106`a9d1fbd0 fffff804`363fcdd8 : ffffce81`fa600180 ffff9908`6d855040 fffff804`36317dd0 ffffe106`a9d1fc50 : nt!PspSystemThreadStartup+0x55
ffffe106`a9d1fc20 00000000`00000000 : ffffe106`a9d20000 ffffe106`a9d19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+d039ac
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\maksu\Downloads\Compressed\MiniDump\122920-5609-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`11200000 PsLoadedModuleList = 0xfffff803`11e2a2b0
Debug session time: Tue Dec 29 16:10:46.675 2020 (UTC + 3:00)
System Uptime: 0 days 0:08:07.353
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`115f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8206`073b7850=0000000000000119
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff8206073b7920
Arg4: ffffce0e4acc6e90
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 26483
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 65728
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff8206073b7920
BUGCHECK_P4: ffffce0e4acc6e90
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8206`073b7848 fffff803`22803ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8206`073b7920 : nt!KeBugCheckEx
ffff8206`073b7850 fffff803`2361bbe1 : 00000000`00000000 ffffce0e`4acc4000 ffff8206`073b7959 ffffce0e`4acc4000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8206`073b7890 fffff803`2368351d : ffffce0e`00000000 ffffce0e`4acc6e90 ffffce0e`4a462000 ffffce0e`4b051010 : dxgmms2!VidSchiSendToExecutionQueue+0x127a1
ffff8206`073b79c0 fffff803`2368b2ea : ffffce0e`4b051010 ffffce0e`4a462000 00000000`00000000 ffffce0e`4a482050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8206`073b7b40 fffff803`2368b15a : ffffce0e`4a462400 fffff803`2368b090 ffffce0e`4a462000 ffffde01`2d600100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8206`073b7b90 fffff803`11517e25 : ffffce0e`4a5ef040 fffff803`00000001 ffffce0e`4a462000 000004d0`00000001 : dxgmms2!VidSchiWorkerThread+0xca
ffff8206`073b7bd0 fffff803`115fcdd8 : ffffde01`2d600180 ffffce0e`4a5ef040 fffff803`11517dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8206`073b7c20 00000000`00000000 : ffff8206`073b8000 ffff8206`073b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+127a1
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 127a1
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\maksu\Downloads\Compressed\MiniDump\122920-5468-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`14e00000 PsLoadedModuleList = 0xfffff801`15a2a2b0
Debug session time: Tue Dec 29 16:24:12.111 2020 (UTC + 3:00)
System Uptime: 0 days 0:12:58.717
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`151f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffef83`fce9f850=0000000000000119
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffef83fce9f920
Arg4: ffff81884370cad0
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 28296
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 66703
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffef83fce9f920
BUGCHECK_P4: ffff81884370cad0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffef83`fce9f848 fffff801`22ce3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffef83`fce9f920 : nt!KeBugCheckEx
ffffef83`fce9f850 fffff801`2645bbe1 : 00000000`00000000 ffff8188`43709000 ffff8188`43726620 ffff8188`43709316 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffef83`fce9f890 fffff801`264c351d : ffff8188`00000000 ffff8188`4370cad0 ffff8188`43616000 ffff8188`48521010 : dxgmms2!VidSchiSendToExecutionQueue+0x127a1
ffffef83`fce9f9c0 fffff801`264cb2ea : ffff8188`48521010 ffff8188`43616000 00000000`00000000 ffff8188`436c5620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffef83`fce9fb40 fffff801`264cb15a : ffff8188`43616400 fffff801`264cb090 ffff8188`43616000 ffff9680`2b880100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffef83`fce9fb90 fffff801`15117e25 : ffff8188`43621380 fffff801`00000001 ffff8188`43616000 000fe067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffef83`fce9fbd0 fffff801`151fcdd8 : ffff9680`2b880180 ffff8188`43621380 fffff801`15117dd0 3a7becbc`197ea592 : nt!PspSystemThreadStartup+0x55
ffffef83`fce9fc20 00000000`00000000 : ffffef83`fcea0000 ffffef83`fce99000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+127a1
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 127a1
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------