Windows 10 Dxgmms error and no monitor signal on startup

[Tony de Lacey]

Hi i have a really big issue with my computer. Ive only had it for a bit (really powerful gaming pc)

and it occasional freezes after the first 10 minutes of booting (occasionally)

and sometimes when it starts up it shuts down then starts up again but no signal goes to my 2 monitors.

i have to either keep hard reseting or unplug everything including 1 monitor and then it starts up again

(unpluigging usb thingys).


Its been happening for a while now even after a full factory restart,

clean uninstalling nvidia (including DDR) etc.


Desperate need for help. It used to be an nvlddmkm.sys error but now its dxgmms. What's going on here??


Many thanks in advance.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7093

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 7172

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

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: ffffc9014bfc8cb0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: NVIDIA Share.exe

STACK_TEXT:
fffffc07`0d0c6be8 fffff805`7c063ad0 : 00000000`0000010e 00000000`00000033 ffffc901`4bfc8cb0 00000000`00000000 : nt!KeBugCheckEx
fffffc07`0d0c6bf0 fffff805`80757f45 : 00000000`00000000 ffffc901`4bfc8db0 ffffb50f`65003000 ffffc901`4bfc8cb0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffc07`0d0c6c30 fffff805`806c253a : ffffc901`4bfc8cb0 00000000`00000000 00000000`00000001 ffffc901`4bfc8cb0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27879
fffffc07`0d0c6c70 fffff805`80750ec3 : ffffc901`6525e210 00000000`00000000 00000000`00000001 01000000`00100000 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
fffffc07`0d0c6ca0 fffff805`806b3112 : ffffc901`6525e210 ffffc901`41772de0 ffffb50f`63c3e770 00000000`00000070 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0x2bd43
fffffc07`0d0c6cd0 fffff805`7bdc8a44 : 00000000`00000001 ffffc901`41772eb0 ffffc901`00000000 00000000`000000ee : dxgmms2!VidMmTerminateProcess+0x12
fffffc07`0d0c6d00 fffff805`7bdc8547 : ffffb50f`6aa17cc0 fffffc07`0d0c6e30 00000000`00000400 ffffc901`41772de0 : dxgkrnl!VidMmTerminateProcessX+0x64
fffffc07`0d0c6d30 fffff805`7bdc38e5 : ffffc901`41772de0 00000000`00000001 ffffc901`41772de0 00000000`00000668 : dxgkrnl!DXGPROCESS:estroy+0x1bf
fffffc07`0d0c6fa0 fffff805`7bcb6b67 : 00000000`00000000 ffffc901`41772de0 ffffb50f`5fcd2a00 fffff805`67404700 : dxgkrnl!DXGPROCESS:estroyDxgProcess+0x105
fffffc07`0d0c70f0 fffff805`62e3759f : 00000000`00000000 ffffb50f`692fa080 00000000`00000000 ffffb50f`5fcd27f0 : dxgkrnl!DxgkProcessNotify+0xf7
fffffc07`0d0c7150 fffff805`62e62894 : ffffb50f`692fa000 ffffb50f`692fa080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
fffffc07`0d0c7220 fffff805`62f06562 : ffffb50f`6941e4b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70
fffffc07`0d0c7250 fffff805`62f09a9e : ffffb50f`00000000 00000000`00000001 00000000`00000000 000000f4`74a65000 : nt!PspExitThread+0x5b2
fffffc07`0d0c7350 fffff805`62c071b5 : ffffb50f`692fa080 ffffb50f`6941e080 fffffc07`0d0c7440 fffffc07`0d0c7440 : nt!NtTerminateProcess+0xde
fffffc07`0d0c73c0 00007ffc`0b5ec534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000f4`74d1f908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`0b5ec534


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27879

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 27879

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...