Windows 10: HDMI switcher causes dwm.exe to crash in kernelbase.dll and I get no video and cannot RDP

I have two machines going into a BENFEI HDMI 1.4V 2 to 1 splitter. Theres a button you just push to toggle between input 1 and 2. The output goes to a 24" Dell monitor.One input is a machine that dual boots fedora linux and Mac OSX Ventura. The other input is my main machine thats a Dell Precision tower with Windows 10 on it. On the dual boot machine if I'm in fedora linux it seems fine and I can switch back and forth. Once it boots into Mac OS though, if I click my HDMI switcher back I get no signal from my windows pc at all. I cannot RDP to it either I get error 0x108 after sitting on

:)

 

Dual Monitor (HDMI) Through HDMI Switcher

Hello Kevin,

We appreciate the details that you have provided. For us to further isolate the issue, we would like to know the following information:

• Have you tried updating the drivers for your HDMI switcher?
• Can you provide us the Make and Model of your HDMI switcher?

Looking forward to your reply.

 

What is causing dwm to crash?

Hello, matt__thomas

Thanks for posting your report here.

Based on the information provided in the crash log, the crash of dwm (Desktop Window Manager) is caused by an exception with the error code 8898008d. The error message states: "No HW rendering device is available for this operation." This suggests that the crash is related to a problem with the hardware rendering device, which is responsible for rendering graphics on the screen.

If we need to dig deeper into this issue, can you please share additional information such as:

1. What rendering software is currently running before the crash occurs? If it is rendering software, can you describe the name of this software.
   
2. As of now, can you share the hardware information of the current PC? For example, the hardware of your GPU/CPU/RAM/motherboard. The version of Windows 11(Press Windows+R to call run window > Type winver.exe > then take a screenshot of version and attach it here.)
   

From the log analysis results, the following are some possible causes:

1. Graphics driver issues: The crash may occur due to outdated or incompatible graphics drivers. It's recommended to update your graphics drivers to the latest version compatible with your system. Assuming that the latest driver has been installed before and caused dwm.exe to crash, please try to Roll back driver version.
   
2. System resource limitations: Insufficient system resources, such as memory (RAM) or GPU memory, could cause dwm to crash. Ensure that your system meets the minimum requirements for running graphics-intensive applications and consider closing unnecessary programs or upgrading your hardware if needed.
   

In this regard, factors that may need to be considered include software issues and hardware issues, such as:

• Graphics hardware problems: There could be an issue with the graphics hardware itself, such as a malfunctioning GPU or insufficient hardware resources. In such cases, troubleshooting or replacing the graphics hardware may be necessary.
  
• Conflicting software: Certain software applications or utilities installed on the system could interfere with the operation of dwm, causing it to crash. Try to identify any recently installed software or updates and uninstall them to see if the issue is resolved.
  

The following are some discussions about the dwm.exe program in the Microsoft Learn community. Some users have solved the problem by re-plugging the graphics card, replacing the PSU, and removing the PCIe cable or USB-C device. You can try them one by one. and see if these steps work for your situation.

DWM Crashing randomly causing Black Screen - Microsoft Q&A

If the problem persists, you can also try to upload the newly generated dump file to the your cloud drive and post the link here to share with me, which will help us discuss how to proceed next.

Best regards,



Chandy |Microsoft Community Support Specialist

 

dwm failure on rdp session in win 10

When logged in to a Win 10 pro system remotely from a Win 7 pro system, two instances of the dwm process are created. Only one appears when logged into the same system locally.

One of the two processes in the rdp session seems to be dormant, accumulating no cpu usage. However, the second dwm process seems to have an event processing thread in the dwmcore DLL that is hung in a tight loop, thus consuming a core of a multicore processor.

dwm version is 10.0.10240.16384...interesting versioning!