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: ffff8507836ed960
Arg4: ffffdc0000e8b110
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 0
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 0
Key : Analysis.Memory.CommitPeak.Mb
Value: 42
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff8507836ed960
BUGCHECK_P4: ffffdc0000e8b110
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffff8507`836ed888 fffff805`45af41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8507`836ed960 : 0xfffff805`379c2390
ffff8507`836ed890 00000000`00000119 : 00000000`00000002 ffffffff`c000000d ffff8507`836ed960 ffffdc00`00e8b110 : 0xfffff805`45af41a0
ffff8507`836ed898 00000000`00000002 : ffffffff`c000000d ffff8507`836ed960 ffffdc00`00e8b110 00000000`0000000a : <Unloaded_Unknown_Module_00000000`00000002>+0x117
ffff8507`836ed8a0 ffffffff`c000000d : ffff8507`836ed960 ffffdc00`00e8b110 00000000`0000000a ffffdc00`00e8b110 : <Unloaded_Unknown_Module_00000000`00000002>
ffff8507`836ed8a8 ffff8507`836ed960 : ffffdc00`00e8b110 00000000`0000000a ffffdc00`00e8b110 fffff805`33b8abf8 : 0xffffffff`c000000d
ffff8507`836ed8b0 ffffdc00`00e8b110 : 00000000`0000000a ffffdc00`00e8b110 fffff805`33b8abf8 00000000`00000000 : 0xffff8507`836ed960
ffff8507`836ed8b8 00000000`0000000a : ffffdc00`00e8b110 fffff805`33b8abf8 00000000`00000000 ffffdc00`00e88000 : 0xffffdc00`00e8b110
ffff8507`836ed8c0 ffffdc00`00e8b110 : fffff805`33b8abf8 00000000`00000000 ffffdc00`00e88000 ffff8507`836ed999 : <Unloaded_Unknown_Module_00000000`00000002>+0x8
ffff8507`836ed8c8 fffff805`33b8abf8 : 00000000`00000000 ffffdc00`00e88000 ffff8507`836ed999 ffffdc00`00e88000 : 0xffffdc00`00e8b110
ffff8507`836ed8d0 00000000`00000000 : ffffdc00`00e88000 ffff8507`836ed999 ffffdc00`00e88000 00000000`00000000 : 0xfffff805`33b8abf8
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x119
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {4972d02e-6a88-98d8-7b5b-41106f17750a}
Followup: MachineOwner
---------
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: ffffaa8b8fe99960
Arg4: ffffae8826598e70
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 19
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffaa8b8fe99960
BUGCHECK_P4: ffffae8826598e70
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffaa8b`8fe99888 fffff807`2b2f41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffaa8b`8fe99960 : nt!KeBugCheckEx
ffffaa8b`8fe99890 fffff807`2b8eabf8 : 00000000`00000000 ffffae88`26596000 ffffae88`26596000 ffffae88`26598e70 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffaa8b`8fe998d0 fffff807`2b948684 : ffffae88`00000000 ffffae88`26598e70 ffffae88`26cd2000 ffffae88`26211010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffffaa8b`8fe99a00 fffff807`2b959c15 : ffffae88`1e0a3140 ffffae88`26cd2000 00000000`00000000 ffffae88`264911e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffffaa8b`8fe99b80 fffff807`2b959a8a : ffffae88`26cd2400 fffff807`2b9599c0 ffffae88`26cd2000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffffaa8b`8fe99bd0 fffff807`1d26bcd5 : ffffae88`25ee1040 fffff807`00000001 ffffae88`26cd2000 00000000`00000001 : dxgmms2!VidSchiWorkerThread+0xca
ffffaa8b`8fe99c10 fffff807`1d3c9998 : fffff807`1874f180 ffffae88`25ee1040 fffff807`1d26bc80 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffaa8b`8fe99c60 00000000`00000000 : ffffaa8b`8fe9a000 ffffaa8b`8fe94000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.1059
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a08
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80414773358, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 40
Key : Analysis.Memory.CommitPeak.Mb
Value: 71
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80414773358
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:
fffff804`19e1ab08 fffff804`1443d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`14773358 : nt!KeBugCheckEx
fffff804`19e1ab10 fffff804`142b90a7 : 0000039d`d32286af fffff804`11555180 00000000`00000286 fffff804`19e0c3a0 : nt!KeAccumulateTicks+0x181641
fffff804`19e1ab70 fffff804`1415f291 : 00000000`00000000 fffff804`141cc000 fffff804`19e0c420 fffff804`141cc0b0 : nt!KeClockInterruptNotify+0xc07
fffff804`19e1af30 fffff804`1422cc75 : fffff804`141cc000 00000000`00000000 00000000`00000000 ffff3487`257f3c69 : hal!HalpTimerClockIpiRoutine+0x21
fffff804`19e1af60 fffff804`143c3e1a : fffff804`19e0c420 fffff804`141cc000 ffff9a0f`7c46c0d0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`19e1afb0 fffff804`143c4387 : ffffffff`0000ffff 00000000`00000000 fffff804`19e0ffff 00000000`00000008 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`19e0c3a0 fffff804`26676241 : fffff804`266ac3ef ffff9a0f`7dd23000 ffff9a0f`7dd23000 ffff9a0f`7834d8a0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`19e0c538 fffff804`266ac3ef : ffff9a0f`7dd23000 ffff9a0f`7dd23000 ffff9a0f`7834d8a0 00000000`00000000 : nvlddmkm+0x1a6241
fffff804`19e0c540 ffff9a0f`7dd23000 : ffff9a0f`7dd23000 ffff9a0f`7834d8a0 00000000`00000000 00000000`00000020 : nvlddmkm+0x1dc3ef
fffff804`19e0c548 ffff9a0f`7dd23000 : ffff9a0f`7834d8a0 00000000`00000000 00000000`00000020 fffff804`19e0c580 : 0xffff9a0f`7dd23000
fffff804`19e0c550 ffff9a0f`7834d8a0 : 00000000`00000000 00000000`00000020 fffff804`19e0c580 00000000`00000000 : 0xffff9a0f`7dd23000
fffff804`19e0c558 00000000`00000000 : 00000000`00000020 fffff804`19e0c580 00000000`00000000 fffff804`266a9a90 : 0xffff9a0f`7834d8a0
SYMBOL_NAME: nvlddmkm+1a6241
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1a6241
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8077d173358, 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.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 25
Key : Analysis.Memory.CommitPeak.Mb
Value: 71
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8077d173358
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: dwm.exe
STACK_TEXT:
fffff807`82e1ab08 fffff807`7ce3d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`7d173358 : nt!KeBugCheckEx
fffff807`82e1ab10 fffff807`7ccb90a7 : 00003907`78bdd122 fffff807`7a577180 00000000`00000286 fffff807`82e131e0 : nt!KeAccumulateTicks+0x181641
fffff807`82e1ab70 fffff807`7cb5f291 : 00000000`0000002d fffff807`7cbcc000 fffff807`82e13260 fffff807`7cbcc0b0 : nt!KeClockInterruptNotify+0xc07
fffff807`82e1af30 fffff807`7cc2cc75 : fffff807`7cbcc000 00000000`00000000 00000000`00000000 ffff207d`8bb6bc32 : hal!HalpTimerClockIpiRoutine+0x21
fffff807`82e1af60 fffff807`7cdc3e1a : fffff807`82e13260 fffff807`7cbcc000 ffffb904`4eca51a0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`82e1afb0 fffff807`7cdc4387 : 00000000`0010a1c4 00000000`00000000 ffffb904`00000020 fffff807`82e13210 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`82e131e0 fffff807`8fc829a3 : fffff807`8fc82969 00000000`00000004 ffffb904`4da3aee8 ffffb904`4da3aed0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`82e13378 fffff807`8fc82969 : 00000000`00000004 ffffb904`4da3aee8 ffffb904`4da3aed0 00000000`00000000 : nvlddmkm+0x1d29a3
fffff807`82e13380 00000000`00000004 : ffffb904`4da3aee8 ffffb904`4da3aed0 00000000`00000000 00000000`0edeb3cd : nvlddmkm+0x1d2969
fffff807`82e13388 ffffb904`4da3aee8 : ffffb904`4da3aed0 00000000`00000000 00000000`0edeb3cd fffff807`90181cdd : 0x4
fffff807`82e13390 ffffb904`4da3aed0 : 00000000`00000000 00000000`0edeb3cd fffff807`90181cdd 00000000`00000000 : 0xffffb904`4da3aee8
fffff807`82e13398 00000000`00000000 : 00000000`0edeb3cd fffff807`90181cdd 00000000`00000000 fffff807`01171000 : 0xffffb904`4da3aed0
SYMBOL_NAME: nvlddmkm+1d29a3
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d29a3
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8021cb73358, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 61
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8021cb73358
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:
fffff802`2181ab08 fffff802`1c83d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1cb73358 : nt!KeBugCheckEx
fffff802`2181ab10 fffff802`1c6b8e2c : 00002af1`4ca922c6 fffff802`18e3f180 00000000`00133fba 00000000`00133fba : nt!KeAccumulateTicks+0x181641
fffff802`2181ab70 fffff802`1c55d567 : 00000000`00000000 fffff802`2180bb00 fffff802`2180bb80 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff802`2181af30 fffff802`1c62cc75 : 0000002d`e4b4696b fffff802`1c5cc100 fffff802`1c5cc1b0 ffff3a57`7e8bad66 : hal+0x1567
fffff802`2181af60 fffff802`1c7c3e1a : fffff802`2180bb80 fffff802`1c5cc100 fffff802`1c609422 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`2181afb0 fffff802`1c7c4387 : 0004c758`01089000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`2180bb00 fffff802`1c6faca6 : fffff802`1cb116f0 fffff802`2180bda8 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`2180bc90 fffff802`1c609422 : fffff802`21807000 00000000`00000000 00000000`00000001 fffff802`2e5fd2f5 : nt!RtlpWalkFrameChain+0x3b6
fffff802`2180c380 fffff802`1c609372 : 00000000`0000000b fffff802`2180c418 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
fffff802`2180c3b0 fffff802`2e595fca : ffff950b`2d866d70 fffff802`2180c510 00000000`00000000 00000000`00000001 : nt!RtlCaptureStackBackTrace+0x42
fffff802`2180c3e0 ffff950b`2d866d70 : fffff802`2180c510 00000000`00000000 00000000`00000001 fffff802`2e61ae42 : nvlddmkm+0x1d5fca
fffff802`2180c3e8 fffff802`2180c510 : 00000000`00000000 00000000`00000001 fffff802`2e61ae42 fffff802`2e57a5a1 : 0xffff950b`2d866d70
fffff802`2180c3f0 00000000`00000000 : 00000000`00000001 fffff802`2e61ae42 fffff802`2e57a5a1 fffff802`1cb91400 : 0xfffff802`2180c510
SYMBOL_NAME: nvlddmkm+1d5fca
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d5fca
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
drive.google.com
