Crash when laptop screen saves or sleeps - external monitor on HDMI; dxgmms2!VidSchiSendToExecutionQ

[Cliff42]

Howdy,

My laptop keeps crashing with

"dxgmms2.sys fails with      0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue"

whenever I leave the computer for a few minutes (even if I have nothing open on the computer, or just a browser). It starts to go into either "screen off" mode or "sleep mode" and boom, it crashes and restarts. Sometimes it won't crash if I "lock" the screen first before leaving but even that isn't a sure thing.

This has been happening for more than the last year. I have tried updating the drivers multiple times by downloading them from the Nvidia GeForce experience app that came pre-installed, but it still happens.

A BUGCHECK_P1 value of 2 for dxgmms2.sys means "The driver failed upon the submission of a command."

I have the laptop connected to an external Asus monitor via HDMI and use both screens (no gaming, just Adobe/Office suite apps or app coding mostly). Everything seems to work fine other than this crash. I regularly update drivers, BIOS, etc.

I've pasted the windbg info below.

***Any ideas on how to fix this? ***

Thank you!!

Error info:

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff68ad8d2e860

BUGCHECK_P4: ffffd48c17fab590

PROCESS_NAME:  System

STACK_TEXT: 
fffff68a`d8d2e788 fffff801`3bfb3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff68a`d8d2e860 : nt!KeBugCheckEx
fffff68a`d8d2e790 fffff801`3e127b09     : ffffd48c`17fa8000 00000000`c000000d fffff68a`d8d2e899 00000000`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff68a`d8d2e7d0 fffff801`3e1a4b9d     : ffffd48c`00000000 ffffd48c`17fab590 ffffd48c`17eb4000 ffffd48c`1cae5010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
fffff68a`d8d2e900 fffff801`3e1ad51a     : ffffd48c`1cae5010 ffffd48c`17eb4000 00000000`00000000 ffffd48c`17ebb930 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffff68a`d8d2ea80 fffff801`3e1ad38a     : ffffd48c`17eb4400 fffff801`3e1ad2c0 ffffd48c`17eb4000 ffffc481`758cf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffff68a`d8d2ead0 fffff801`20155855     : ffffd48c`17f2a380 fffff801`00000001 ffffd48c`17eb4000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff68a`d8d2eb10 fffff801`201fe8f8     : ffffc481`758cf180 ffffd48c`17f2a380 fffff801`20155800 0007990e`001c9806 : nt!PspSystemThreadStartup+0x55
fffff68a`d8d2eb60 00000000`00000000     : fffff68a`d8d2f000 fffff68a`d8d28000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+a99

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1320

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  a99

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

System info:

OS Name        Microsoft Windows 10 Home

Version        10.0.19042 Build 19042

Other OS Description         Not Available

OS Manufacturer        Microsoft Corporation

System Name        MARSHALL

System Manufacturer        HP

System Model        OMEN Laptop 15-ek0xxx

System Type        x64-based PC

System SKU        3E768UA#ABA

Processor        Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s), 12 Logical Processor(s)

BIOS Version/Date        AMI F.10, 8/23/21

SMBIOS Version        3.2

Embedded Controller Version        17.29

BIOS Mode        UEFI

BaseBoard Manufacturer        HP

BaseBoard Product        878B

BaseBoard Version        17.29

Platform Role        Mobile

Secure Boot State        On

PCR7 Configuration        Elevation Required to View

Windows Directory        C:\WINDOWS

System Directory        C:\WINDOWS\system32

Boot Device        \Device\HarddiskVolume1

Locale        United States

Hardware Abstraction Layer        Version = "10.0.19041.1151"

User Name        

Time Zone       

Installed Physical Memory (RAM)        16.0 GB

Total Physical Memory        15.8 GB

Available Physical Memory        8.88 GB

Total Virtual Memory        18.2 GB

Available Virtual Memory        7.20 GB

Page File Space        2.38 GB

Page File        C:\pagefile.sys

Kernel DMA Protection        On

Virtualization-based security        Not enabled

Device Encryption Support        Elevation Required to View

Hyper-V - VM Monitor Mode Extensions        Yes

Hyper-V - Second Level Address Translation Extensions        Yes

Hyper-V - Virtualization Enabled in Firmware        Yes

Not sure if this is useful, from System info:

[Display]

Item Value
Name NVIDIA GeForce RTX 2070 Super with Max-Q Design
PNP Device ID PCI\VEN_10DE&DEV_1E91&SUBSYS_878B103C&REV_A1\4&312693F9&0&0008
Adapter Type GeForce RTX 2070 Super with Max-Q Design, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2070 Super with Max-Q Design
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_6f7f22b0a5610d99\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_6f7f22b0a5610d99\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_6f7f22b0a5610d99\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_6f7f22b0a5610d99\nvldumdx.dll
Driver Version 27.21.14.6280
INF File oem135.inf (Section049 section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 3840 x 2160 x 59 hertz
Bits/Pixel 32
Memory Address 0x77000000-0x780FFFFF
Memory Address 0x30000000-0x420FFFFF
Memory Address 0x40000000-0x41FFFFFF
I/O Port 0x00004000-0x00004FFF
IRQ Channel IRQ 4294967272
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVHM.INF_AMD64_6F7F22B0A5610D99\NVLDDMKM.SYS (27.21.14.6280, 37.44 MB (39,254,816 bytes), 11/6/21 16:07)

Hyper-V - Data Execution Protection        Yes

[Cliff42]

If crash at sleep or screen-off is not common, does anyone know if upgrade to Windows 11 has helped with HP system stability in general? This has been going on for well over a year so I am happy to find some solution. Thanks.

[Cliff42]

Alas, this still happens if I restore the drivers to the HP drivers recommended by the HP support assistant (ignoring the suggestions from the pre-installed GeForce app which I had been updating to). 

[Cliff42]

Alas, upgraded to Win 11 (Version 10.0.22000 ), have all recommended drivers (according to HP support assistant), and a new external monitor (via HDMI) and still have this crash.  This time while opening a Netflix browser tab (had plenty of resources available at the time)...

ffff8209`df077668 fffff807`57a2529a     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8209`df0777b0 : nt!KeBugCheckEx
ffff8209`df077670 fffff807`58e7358e     : 00000000`00000004 00000000`00000000 00000000`00000000 ffff9305`0d94f000 : watchdog!WdLogSingleEntry5+0x39aa
ffff8209`df077700 fffff807`58ee4fcd     : ffff9305`00000000 ffff9305`0d951c00 ffff9305`0d8a1000 ffff9305`24eee010 : dxgmms2!VidSchiSendToExecutionQueue+0x1a70e
ffff8209`df0778d0 fffff807`58efe47a     : ffff9305`24eee010 ffff9304`e7541040 00000000`00000000 fffff807`58efe220 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8209`df077a60 fffff807`58efe2ea     : ffff9305`0d8a1400 fffff807`58efe220 ffff9305`0d8a1000 ffff9305`0d92e400 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8209`df077ab0 fffff807`3ac478f5     : ffff9305`0d92e480 fffff807`00000001 ffff9305`0d8a1000 004fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8209`df077af0 fffff807`3ae19bb4     : ffffdf80`094ad180 ffff9305`0d92e480 fffff807`3ac478a0 00610068`0073002d : nt!PspSystemThreadStartup+0x55
ffff8209`df077b40 00000000`00000000     : ffff8209`df078000 ffff8209`df071000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

[Cliff42]

I should add that using the clean install setting for video driver didn't help.

Also, a check with sfc /scannow and DISM.EXE turned up no hardware errors.