DriverFrameworks-UserMod Critical system error blocking my Remote desktop connection

Question

Hello ,

I am facing problems to use remote desktop connection and I get some critical events related to Remote Display Adapter. I am working on updated Windows 10 Pro version. Here bellow you find the critical event information. Could you, please, help me find a solution for my problem ? Thank you.

• <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
• <System> <Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" /> <EventID>10110</EventID> <Version>1</Version> <Level>1</Level> <Task>64</Task> <Opcode>0</Opcode> <Keywords>0x2000000000000000</Keywords> <TimeCreated SystemTime="2021-06-18T13:06:36.5205660Z" /> <EventRecordID>16970</EventRecordID> <Correlation /> <Execution ProcessID="368" ThreadID="744" /> <Channel>System</Channel> <Computer>HYPERON</Computer> <Security UserID="S-1-5-18" /> </System>
• <UserData>
• <UMDFHostProblem xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event"> <LifetimeId>{1277e4d7-fc6b-4269-8109-e1e55bebae93}</LifetimeId> <Problem>8</Problem> <DetectedBy>2</DetectedBy> <ActiveOperation>0</ActiveOperation> <ExitCode>1879048193</ExitCode> <Message>0</Message> <Status>4294967295</Status> </UMDFHostProblem> </UserData> </Event>
• <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
• <System> <Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" /> <EventID>10111</EventID> <Version>1</Version> <Level>1</Level> <Task>64</Task> <Opcode>0</Opcode> <Keywords>0x2000000000000000</Keywords> <TimeCreated SystemTime="2021-06-18T13:06:36.5231813Z" /> <EventRecordID>16971</EventRecordID> <Correlation /> <Execution ProcessID="368" ThreadID="744" /> <Channel>System</Channel> <Computer>HYPERON</Computer> <Security UserID="S-1-5-18" /> </System>
• <UserData>
• <UmdfDeviceOffline xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event"> <LifetimeId>{1277e4d7-fc6b-4269-8109-e1e55bebae93}</LifetimeId> <FriendlyName>Microsoft Remote Display Adapter</FriendlyName> <Location>(unknown)</Location> <InstanceId>SWD\REMOTEDISPLAYENUM\RDPIDD_INDIRECTDISPLAY&SESSIONID_0001</InstanceId> <RestartCount>5</RestartCount> </UmdfDeviceOffline> </UserData> </Event>
• <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
• <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7034</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2021-06-18T10:20:41.2351821Z" /> <EventRecordID>16680</EventRecordID> <Correlation /> <Execution ProcessID="364" ThreadID="16788" /> <Channel>System</Channel> <Computer>HYPERON</Computer> <Security /> </System>
• <EventData> <Data Name="param1">Services Bureau à distance</Data> <Data Name="param2">4</Data> <Binary>5400650072006D0053006500720076006900630065000000</Binary> </EventData> </Event>

Answer 1

Hi,
The display drivers in the system may causing the RDP display driver to crash.
Firstly, we could try to reinstall the latest video card driver from the manufacturer's official website.
Then try to modify the Group Policy below:
Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use WDDM graphics display driver for Remote Desktop Connections | set to "Disabled".
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 2

Hi,

Thank you. It worked for me.

Best regards,
Lotfi Fahem

Answer 3

Hi. I have the same problem. I tried to reinstall graphic drivers with different versions, latest and not latest, set Group policies "set WDDM graphics display driver for Remote Desktop Connections" and "Use hardware graphics adapters for all Remote Desktop Services sessions" to "Disabled" and "Enabeld" - all of it did not resolve the prblem. What can I do else ?