Microsoft-Windows-DriverFrameworks-UserMode Critical Error on Remote Desktop servers

Question

Microsoft-Windows-DriverFrameworks-UserMode Critical Error on Remote Desktop servers

Daniel R 0

Hello,

I am receiving the attached critical errors on our two RDS servers on the Server Manager with IDs 10110 and 10111. This seems to occasionally result in disconnection for the end user. I have disabled the "Remote Desktop Connection using WDDM Graphical Display Driver" policy in the local group policy of both servers. The RDS servers are both on Server 2022, while the broker server that allows connections to them is on 2019, so I'm not sure if there is some incompatibility. I am looking for solutions to this error to prevent the disruption of user connections going forward.

854a0cdb-5d44-49ed-8ba2-f988355d9fbb.png

Thank you!

Anonymous

2024-10-22T01:43:32.12+00:00

Hi Daniel R,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Could you please confirm if you are encountering this error on an Azure cloud server or an on-premises server?
Daniel R 0 Reputation points

2024-10-22T12:13:06.95+00:00

Hi @Anonymous

This error is on an Azure cloud server. Additionally, it seems to happen within the same timespan each day.
Anonymous

2024-10-23T03:45:03.25+00:00

Hi Daniel R,

Could you please provide details about the operating system (OS) version you're using, along with the SKU type of the Azure virtual machine? This information will help us replicate the issue in a lab environment for further analysis.

Thank you.
Daniel R 0 Reputation points

2024-10-23T13:01:03.4433333+00:00

Hi @Anonymous

Both RDS servers have a SKU of Standard D4s v3 and are on Windows (Windows Server 2022 Datacenter Azure Edition).

The broker server has a SKU of Standard D8s v3 and is on Windows (Windows Server 2019 Datacenter).
Daniel R 0 Reputation points

2024-10-23T13:04:02.67+00:00

Hi @Anonymous

The two RDS servers have SKUs of Standard D4s v3 (4 vcpus, 16 GiB memory) and are running Windows (Windows Server 2022 Datacenter Azure Edition).

The broker server has a SKU of Standard D8s v3 (8 vcpus, 32 GiB memory) and is running Windows (Windows Server 2019 Datacenter).
Anonymous

2024-10-24T06:08:04.62+00:00

Hi Daniel R,

The issue may be related to the display drivers causing the RDP display driver to crash. Please try the following steps:

Reinstall the latest video card driver from the manufacturer's official website (e.g., NVIDIA, AMD, or Intel).

Modify the Group Policy to disable the WDDM graphics display driver for Remote Desktop connections:

Open Group Policy Editor (gpedit.msc).

Navigate to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

Set Use WDDM graphics display driver for Remote Desktop Connections to Disabled.

After making these changes, restart the server and check if the issue persists.

If you found this information helpful, please click an accepting the answer and "Upvote" on my post for other community members' reference
Daniel R 0 Reputation points

2024-10-24T14:52:32.3966667+00:00

Hi @Anonymous ,

As I stated in my original post, I have already disabled that group policy object, and the error still occurred occasionally after doing so.
Anonymous

2024-10-28T04:22:56.5666667+00:00

Hi Daniel R,

Thank you for the update. Since disabling the “Remote Desktop Connection using WDDM Graphics Display Driver” policy didn't fully resolve the issue, please try the following steps to further address the driver-related errors (Event IDs 10110 and 10111) on your NVadsA10 v5-series RDS servers:

Verify that the latest NVIDIA drivers specific to Azure NVadsA10 v5-series and Windows Server 2022 are installed. Updated drivers often resolve compatibility and stability issues.

Confirm that both your RDS servers and the connection broker server (2019) have all recent Windows updates, particularly those that impact Remote Desktop Services and GPU performance. Use Azure Monitor or Performance Monitor to track GPU and system performance, which might reveal patterns related to these errors, potentially highlighting periods of high GPU utilization or driver instability.

For more information, refer to the below documents:
Install NVIDIA GPU drivers on N-series VMs running Windows
Remote Desktop Services (RDS) troubleshooting guide

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Anonymous

2024-10-29T04:16:00.84+00:00

Hi Daniel R,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
Daniel R 0 Reputation points

2024-10-29T13:25:54.9466667+00:00

Hi @Anonymous
I do not have a NVadsA10 v5-series server to my knowledge. They are Standard D4s v3 servers, so I am unsure what drivers would suit this server. Both the RDS servers and broker servers are up to date.
Anonymous

2024-10-30T08:06:25.98+00:00

Hi Daniel R,

Thank you for clarifying the server type. Since you’re using Standard D4s v3 servers without GPU support.

Since all servers are fully updated, here are some other steps to try:

Disable Hardware Acceleration Software-based graphics acceleration may sometimes cause display issues. Try disabling hardware acceleration in the Remote Desktop Session Host Configuration.

Enable Detailed Event Logging to get more information on Event IDs 10110 and 10111, enable detailed logging for DriverFrameworks-UserMode. This may help pinpoint what’s causing these events.

Adjust RemoteFX Settings although deprecated, could be affecting display processes. You might disable RemoteFX in Group Policy:

Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

Set Configure RemoteFX options to Disabled if it’s enabled.

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Anonymous

2024-11-01T09:15:27.9966667+00:00

Hi Daniel R,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
TTOL 0 Reputation points

2025-04-17T21:04:40.43+00:00

Hi

Were you able to find the solution for this?

It seems Microsoft Support is clueless on this.

Thanks

1 answer

Your answer

Anonymous

2024-10-22T01:43:32.12+00:00

Hi Daniel R,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Could you please confirm if you are encountering this error on an Azure cloud server or an on-premises server?
Daniel R 0 Reputation points

2024-10-22T12:13:06.95+00:00

Hi @Anonymous

This error is on an Azure cloud server. Additionally, it seems to happen within the same timespan each day.
Anonymous

2024-10-23T03:45:03.25+00:00

Hi Daniel R,

Could you please provide details about the operating system (OS) version you're using, along with the SKU type of the Azure virtual machine? This information will help us replicate the issue in a lab environment for further analysis.

Thank you.
Daniel R 0 Reputation points

2024-10-23T13:01:03.4433333+00:00

Hi @Anonymous

Both RDS servers have a SKU of Standard D4s v3 and are on Windows (Windows Server 2022 Datacenter Azure Edition).

The broker server has a SKU of Standard D8s v3 and is on Windows (Windows Server 2019 Datacenter).
Daniel R 0 Reputation points

2024-10-23T13:04:02.67+00:00

Hi @Anonymous

The two RDS servers have SKUs of Standard D4s v3 (4 vcpus, 16 GiB memory) and are running Windows (Windows Server 2022 Datacenter Azure Edition).

The broker server has a SKU of Standard D8s v3 (8 vcpus, 32 GiB memory) and is running Windows (Windows Server 2019 Datacenter).
Anonymous

2024-10-24T06:08:04.62+00:00

Hi Daniel R,

The issue may be related to the display drivers causing the RDP display driver to crash. Please try the following steps:

Reinstall the latest video card driver from the manufacturer's official website (e.g., NVIDIA, AMD, or Intel).

Modify the Group Policy to disable the WDDM graphics display driver for Remote Desktop connections:

Open Group Policy Editor (gpedit.msc).

Navigate to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

Set Use WDDM graphics display driver for Remote Desktop Connections to Disabled.

After making these changes, restart the server and check if the issue persists.

If you found this information helpful, please click an accepting the answer and "Upvote" on my post for other community members' reference
Daniel R 0 Reputation points

2024-10-24T14:52:32.3966667+00:00

Hi @Anonymous ,

As I stated in my original post, I have already disabled that group policy object, and the error still occurred occasionally after doing so.
Anonymous

2024-10-28T04:22:56.5666667+00:00

Hi Daniel R,

Thank you for the update. Since disabling the “Remote Desktop Connection using WDDM Graphics Display Driver” policy didn't fully resolve the issue, please try the following steps to further address the driver-related errors (Event IDs 10110 and 10111) on your NVadsA10 v5-series RDS servers:

Verify that the latest NVIDIA drivers specific to Azure NVadsA10 v5-series and Windows Server 2022 are installed. Updated drivers often resolve compatibility and stability issues.

Confirm that both your RDS servers and the connection broker server (2019) have all recent Windows updates, particularly those that impact Remote Desktop Services and GPU performance. Use Azure Monitor or Performance Monitor to track GPU and system performance, which might reveal patterns related to these errors, potentially highlighting periods of high GPU utilization or driver instability.

For more information, refer to the below documents:
Install NVIDIA GPU drivers on N-series VMs running Windows
Remote Desktop Services (RDS) troubleshooting guide

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Anonymous

2024-10-29T04:16:00.84+00:00

Hi Daniel R,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
Daniel R 0 Reputation points

2024-10-29T13:25:54.9466667+00:00

Hi @Anonymous
I do not have a NVadsA10 v5-series server to my knowledge. They are Standard D4s v3 servers, so I am unsure what drivers would suit this server. Both the RDS servers and broker servers are up to date.
Anonymous

2024-10-30T08:06:25.98+00:00

Hi Daniel R,

Thank you for clarifying the server type. Since you’re using Standard D4s v3 servers without GPU support.

Since all servers are fully updated, here are some other steps to try:

Disable Hardware Acceleration Software-based graphics acceleration may sometimes cause display issues. Try disabling hardware acceleration in the Remote Desktop Session Host Configuration.

Enable Detailed Event Logging to get more information on Event IDs 10110 and 10111, enable detailed logging for DriverFrameworks-UserMode. This may help pinpoint what’s causing these events.

Adjust RemoteFX Settings although deprecated, could be affecting display processes. You might disable RemoteFX in Group Policy:

Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

Set Configure RemoteFX options to Disabled if it’s enabled.

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Anonymous

2024-11-01T09:15:27.9966667+00:00

Hi Daniel R,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
TTOL 0 Reputation points

2025-04-17T21:04:40.43+00:00

Hi

Were you able to find the solution for this?

It seems Microsoft Support is clueless on this.

Thanks

Answer 1

Dear Daniel R,

thank you for posting your question on the Q&A portal your detailed description is very helpful, and I’m sure many in the community will benefit from this discussion.

The critical Event IDs 10110 and 10111 from the Microsoft-Windows-DriverFrameworks-UserMode source typically indicate a failure in a User-Mode Driver Framework (UMDF) component, which in Remote Desktop environments often points to issues with display drivers or device redirection components under stress.

Since you already disabled the “Use WDDM graphics display driver for Remote Desktop Connections” policy, you've taken the correct first step. This policy has historically contributed to rendering-related instability in RDS sessions, especially when mismatches exist between host and broker versions. However, Server 2022 (RDS hosts) and Server 2019 (Broker) are officially supported to work together, so incompatibility is unlikely the root cause here. More often, the crash results from a third-party or outdated UMDF driver on the RDS host.

As you said you are looking for solutions to this error to prevent the disruption of user connections going forward, so:

Ensure all device drivers on your RDS servers are up-to-date, especially display and USB redirection components.

Review this Microsoft documentation on UMDF driver failures and logging: UMDF Driver Framework Events and Troubleshooting

Validate if third-party software (e.g., printer redirection, virtual audio drivers) might be involved.

You may also consult Microsoft's guidance on Remote Desktop with WDDM here: Configure WDDM Graphics Display Driver

For deeper diagnostics, you can also enable Driver Verifier to track problematic drivers: How to use Driver Verifier

I hope that would helpful.

rgds,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment

Let me know if the issue persists after driver updates and policy tweaks and I’ll be happy to help you dig further.

Share via

Microsoft-Windows-DriverFrameworks-UserMode Critical Error on Remote Desktop servers

1 answer

Your answer