Windows 10: Dxgmms error and no monitor signal on startup

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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 10eBUGCHECK_P1: 33BUGCHECK_P2: ffffc9014bfc8cb0BUGCHECK_P3: 0BUGCHECK_P4: 0PROCESS_NAME: NVIDIA Share.exeSTACK_TEXT: fffffc07`0d0c6be8 fffff805`7c063ad0 : 00000000`0000010e 00000000`00000033 ffffc901`4bfc8cb0 00000000`00000000 : nt!KeBugCheckExfffffc07`0d0c6bf0 fffff805`80757f45 : 00000000`00000000 ffffc901`4bfc8db0 ffffb50f`65003000 ffffc901`4bfc8cb0 : watchdog!WdLogEvent5_WdCriticalError+0xe0fffffc07`0d0c6c30 fffff805`806c253a : ffffc901`4bfc8cb0 00000000`00000000 00000000`00000001 ffffc901`4bfc8cb0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27879fffffc07`0d0c6c70 fffff805`80750ec3 : ffffc901`6525e210 00000000`00000000 00000000`00000001 01000000`00100000 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xefffffc07`0d0c6ca0 fffff805`806b3112 : ffffc901`6525e210 ffffc901`41772de0 ffffb50f`63c3e770 00000000`00000070 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0x2bd43fffffc07`0d0c6cd0 fffff805`7bdc8a44 : 00000000`00000001 ffffc901`41772eb0 ffffc901`00000000 00000000`000000ee : dxgmms2!VidMmTerminateProcess+0x12fffffc07`0d0c6d00 fffff805`7bdc8547 : ffffb50f`6aa17cc0 fffffc07`0d0c6e30 00000000`00000400 ffffc901`41772de0 : dxgkrnl!VidMmTerminateProcessX+0x64fffffc07`0d0c6d30 fffff805`7bdc38e5 : ffffc901`41772de0 00000000`00000001 ffffc901`41772de0 00000000`00000668 : dxgkrnl!DXGPROCESS:estroy+0x1bffffffc07`0d0c6fa0 fffff805`7bcb6b67 : 00000000`00000000 ffffc901`41772de0 ffffb50f`5fcd2a00 fffff805`67404700 : dxgkrnl!DXGPROCESS:estroyDxgProcess+0x105fffffc07`0d0c70f0 fffff805`62e3759f : 00000000`00000000 ffffb50f`692fa080 00000000`00000000 ffffb50f`5fcd27f0 : dxgkrnl!DxgkProcessNotify+0xf7fffffc07`0d0c7150 fffff805`62e62894 : ffffb50f`692fa000 ffffb50f`692fa080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213fffffc07`0d0c7220 fffff805`62f06562 : ffffb50f`6941e4b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70fffffc07`0d0c7250 fffff805`62f09a9e : ffffb50f`00000000 00000000`00000001 00000000`00000000 000000f4`74a65000 : nt!PspExitThread+0x5b2fffffc07`0d0c7350 fffff805`62c071b5 : ffffb50f`692fa080 ffffb50f`6941e080 fffffc07`0d0c7440 fffffc07`0d0c7440 : nt!NtTerminateProcess+0xdefffffc07`0d0c73c0 00007ffc`0b5ec534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25000000f4`74d1f908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`0b5ec534SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27879MODULE_NAME: dxgmms2IMAGE_NAME: dxgmms2.sysIMAGE_VERSION: 10.0.19041.685STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 27879FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFOOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}Followup: MachineOwner

:)

 

Windows 10 Update Installed & Now No Signal to Monitor

Hi,

For us to isolate your concern with your monitor's signal, we would like to know the following:

• When you say "signal", are you referring to the Internet?
• Are you getting any error messages? If yes, what is the exact error message?
• To make sure that we have not missed on anything, what troubleshooting steps have you done so far?

We look forward to your response.

 

Can't get GPU-Z to start with Windows 8.1 startup

I'm not sure how to do that. Could you list the steps for a noob?

 

Windows 10 upgrade, bad config error, no signal to the monitors

Hi Shiv,

Thank you for contacting Microsoft Community.

In order to help you better, could you please confirm a couple of things:

• What happens when you select the drive from the bios setup, are you able to boot to the computer?
• Are you getting any error message now?

Causes:

• 
  The cable linking your CPU to your monitor might not be properly plugged in or it might be damaged. You should ensure that the two devices are properly connected ant that the cable is in working condition.
  
• 
  You might be facing a problem with your monitor if the CPU makes a single beep error sound when you switch on the system. You can check whether the problem comes from your monitor by testing it on another
  CPU. If you still have the "No Signal" error displayed, including the error beep, you may need to replace your monitor or get it fixed by a professional.
  

I suggest you to remove the power cord and hold the Power button for like 30 seconds to 1 minute and then connect it back and turn on to see if the problem persists.

Please do let us know with more information regarding this issue, so that we can assist you better.