Windows 10 Desktop crashes on wakeup from sleep (VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e))

[NoxianLyfe]

Hello everyone,


I have recently built a custom PC and every time I put my computer to sleep, and attempt to wake it up, it crashes. (I don't see any BSOD as my monitors are off but it reboots as if starting from shutdown).


Things I have tried:

• Uninstalling and reinstalling the latest Nvidia drivers
• Uninstalling and reinstalling an older version of Nvidia drivers
• Removing my GPU and putting it back (and using a riser cable).

I have never experienced this issue when playing games such as League of Legends, Modern Warfare. This issue only happens when attempting to wake up from sleep.


Here is a link to my DMP files and output of msinfo: Crash Files


Here is the bugcheck analysis from one of the DMP files (I wasn't able to find parameter 1 value of 33 at Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL) :

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000033, The subtype of the bugcheck:
Arg2: ffffd609bf5e65a0
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4578

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4E8NB9J

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 23855

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

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: 10e

BUGCHECK_P1: 33

BUGCHECK_P2: ffffd609bf5e65a0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffff800f`7c1e5168 fffff804`3a483ad0 : 00000000`0000010e 00000000`00000033 ffffd609`bf5e65a0 00000000`00000000 : nt!KeBugCheckEx
ffff800f`7c1e5170 fffff804`3c787a05 : 00000000`00000000 ffffd609`bf5e66a0 ffffc005`bbfbe000 ffffd609`bf5e65a0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff800f`7c1e51b0 fffff804`3c6f253a : ffffd609`bf5e65a0 00000000`00000002 00000000`00000001 ffffd609`bf5e65a0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27799
ffff800f`7c1e51f0 fffff804`3c780983 : ffffd609`bcae91e0 00000000`00000002 00000000`00000001 01000000`00100000 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
ffff800f`7c1e5220 fffff804`3c6e3112 : ffffd609`bcae91e0 ffffd609`b63a2de0 ffffc005`b4aecb70 00000000`00000070 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0x2bc63
ffff800f`7c1e5250 fffff804`3a1de773 : 00000000`00000001 ffffd609`b63a2eb0 ffffd609`00000000 00000000`0000032b : dxgmms2!VidMmTerminateProcess+0x12
ffff800f`7c1e5280 fffff804`3a1de277 : ffffc005`bda1d9b0 ffff800f`7c1e53b0 00000000`00000400 ffffd609`b63a2de0 : dxgkrnl!VidMmTerminateProcessX+0x63
ffff800f`7c1e52b0 fffff804`3a1d9615 : ffffd609`b63a2de0 00000000`00000000 ffffd609`b63a2de0 00000000`00000000 : dxgkrnl!DXGPROCESS:estroy+0x1bf
ffff800f`7c1e5520 fffff804`3a0d5e07 : 00000000`00000000 ffffd609`b63a2de0 ffffc005`b09ab4f0 fffff804`2efc4713 : dxgkrnl!DXGPROCESS:estroyDxgProcess+0x105
ffff800f`7c1e5670 fffff804`2ab0560f : 00000000`00000000 ffffc005`bd1eb0c0 ffffc005`ab00ff00 ffffc005`bcb4a4a0 : dxgkrnl!DxgkProcessNotify+0xf7
ffff800f`7c1e56d0 fffff804`2aaa0b4c : ffffc005`bd1eb000 ffffc005`bd1eb0c0 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
ffff800f`7c1e57a0 fffff804`2a9e6f52 : ffffc005`bd5fc4b8 00000000`00000000 ffff800f`7c1e5990 00000000`00000000 : nt!PspExitProcess+0x70
ffff800f`7c1e57d0 fffff804`2aa7a978 : 00000001`00000022 ffff800f`00000001 ffff800f`7c1e59e0 00000016`da4cd000 : nt!PspExitThread+0x5b2
ffff800f`7c1e58d0 fffff804`2a6e25c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
ffff800f`7c1e5910 fffff804`2a7f97b0 : 00000000`00000000 ffff800f`7c1e59c0 ffff800f`7c1e5b80 000001fe`00000000 : nt!KiDeliverApc+0x487
ffff800f`7c1e59c0 fffff804`2a806c5f : ffffc005`bd5fc080 ffffc005`bd603360 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffff800f`7c1e5b00 00007ffe`68e0be24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000016`da21f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`68e0be24


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27799

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.606

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 27799

FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}

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

Continue reading...