Unstable Hyper-V behaviours when access through Remote desktop

I’m asking this in Windows Server sub-forum because my actual host OS Windows 10 does not have a dedicated Hyper-V sub-forum.

Late last year I was running a couple of Windows 10 client VMs on my home desktop PC to test Windows Autopilot and MDM. I would access my home computer from outside via RDC and had no problems operating the VMs (Virtual Machine Connection).

This year, I’m not exactly sure what’s changed, but it seems like accessing the VM display console cannot succeed. Either the VMC window would get stuck resizing the window to the VM’s desktop resolution and eventually close by itself, or it’d hang with
corrupted display.

There are corresponding crash events in Application log.

Log Name:      Application
Source:        .NET Runtime
Date:          15/1/2020 15:22:16
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060

Event Xml:

 
   
    1026
    2
    0
    0x80000000000000
   
    42127
    Application
    HYPERVHOST
   
 

 
    Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060

 

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 15:22:16
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: VmConnect.exe, version: 10.0.18362.1, time stamp: 0xa8d2f2dc
Faulting module name: atidxx64.dll, version: 26.20.15003.5016, time stamp: 0x5df7d2d3
Exception code: 0xc0000005
Fault offset: 0x0000000000014060
Faulting process id: 0x32b4
Faulting application start time: 0x01d5cb7481d2a7df
Faulting application path: C:WINDOWSsystem32VmConnect.exe
Faulting module path: C:WINDOWSSystem32DriverStoreFileRepositoryc0349841.inf_amd64_d70567d658937ff8B349895atidxx64.dll
Report Id: e506f08b-f1b7-418f-a14e-5a7df056b38a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42128
    Application
    HYPERVHOST
   
 

 
    VmConnect.exe
    10.0.18362.1
    a8d2f2dc
    atidxx64.dll
    26.20.15003.5016
    5df7d2d3
    c0000005
    0000000000014060
    32b4
    01d5cb7481d2a7df
    C:WINDOWSsystem32VmConnect.exe
    C:WINDOWSSystem32DriverStoreFileRepositoryc0349841.inf_amd64_d70567d658937ff8B349895atidxx64.dll
    e506f08b-f1b7-418f-a14e-5a7df056b38a
   
   

   
   

 

Worse is if that corrupt VMC window appears, I could very well lose RDC connection to my computer.

I have to get back home to re-gain access to the OS via physical monitor displays. In the physical logon session, I have connect and vmconnect.exe can render the VM screens. The error below probably explains the RDC failure.

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10110
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.
Event Xml:

 
   
    10110
    1
    1
    64
    0
    0x2000000000000000
   
    29917
   
   
    System
    HYPERVHOST
   
 

 
   
      {b125172c-e769-468f-ac22-28b8331ebce8}
      8
      2
      0
      1879048193
      0
      4294967295
   

 

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10111
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
The device Microsoft Remote Display Adapter (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.
Event Xml:

 
   
    10111
    1
    1
    64
    0
    0x2000000000000000
   
    29918
   
   
    System
    HYPERVHOST
   
 

 
   
      {b125172c-e769-468f-ac22-28b8331ebce8}
      Microsoft Remote Display Adapter
      (unknown)
      SWDREMOTEDISPLAYENUMRDPIDD_INDIRECTDISPLAY&SESSIONID_0001
      5
   

 

And even worse scenario is when I get the corrupted VMC window, lose connection, and cannot even get into the OS via physical means; the monitors keep sleeping and waking with blank screens. I might be able to connect to the VMs via RDC Manager (with VM
mode) from another computer to interact and shut them down, but since the host OS is inaccessible at this state I have to hard reset the computer.

I later found scores of display driver restarts, and even broken dwm.exe which likely explains the loss of physical access.

Log Name:      System
Source:        Display
Date:          15/1/2020 22:31:50
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Display driver amdkmdap stopped responding and has successfully recovered.
Event Xml:

 
   
    4101
    3
    0
    0x80000000000000
   
    30166
    System
    HYPERVHOST
   
 

 
    amdkmdap
   
   

 

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 22:31:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: dwm.exe, version: 10.0.18362.387, time stamp: 0x8e064b77
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xe0464645
Fault offset: 0x0000000000000000
Faulting process id: 0x4718
Faulting application start time: 0x01d5cbb05c00d5c0
Faulting application path: C:WINDOWSsystem32dwm.exe
Faulting module path: unknown
Report Id: 350b442b-5588-4cee-a1ca-cf09d0254be7
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42330
    Application
    HYPERVHOST
   
 

 
    dwm.exe
    10.0.18362.387
    8e064b77
    unknown
    0.0.0.0
    00000000
    e0464645
    0000000000000000
    4718
    01d5cbb05c00d5c0
    C:WINDOWSsystem32dwm.exe
    unknown
    350b442b-5588-4cee-a1ca-cf09d0254be7
   
   

   
   

 

Log Name:      Application
Source:        Dwminit
Date:          15/1/2020 22:32:00
Event ID:      0
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: )
Event Xml:

 
   
    0
    3
    0
    0x80000000000000
   
    42332
    Application
    HYPERVHOST
   
 

 
    0x000000ff
    1
   
   

 

Log Name:      Application
Source:        Application Hang
Date:          15/1/2020 22:33:20
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
The program dwm.exe version 10.0.18362.387 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 3fdc
 Start Time: 01d5cbb044188c04
 Termination Time: 20308
 Application Path: C:WindowsSystem32dwm.exe
 Report Id: 0d04efe7-c646-4105-aa35-9c80142c42ea
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown

Event Xml:

 
   
    1002
    2
    101
    0x80000000000000
   
    42352
    Application
    HYPERVHOST
   
 

 
    dwm.exe
    10.0.18362.387
    3fdc
    01d5cbb044188c04
    20308
    C:WindowsSystem32dwm.exe
    0d04efe7-c646-4105-aa35-9c80142c42ea
   
   

   
   

    Unknown
    55006E006B006E006F0077006E0000000000
 

Seems like I’m forced to work with Hyper-V only through physical display now. What is it about Hyper-V services and components that can make it (now) unsuitable for control over RDC?


The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 46 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995