DisplayFusion RSS: NVIDIA App Surround conflict leading to black screens / bootloop with HDMI switches https://www.displayfusion.com/Discussions/RSS/?TopicID=01a0f73e-ba4d-71bf-931f-556d730d7959 DisplayFusion RSS: NVIDIA App Surround conflict leading to black screens / bootloop with HDMI switches Fri, 02 Oct 2026 12:47:00 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=01a0f73e-ba4d-71bf-931f-556d730d7959 NVIDIA App Surround conflict leading to black screens / bootloop with HDMI switches https://www.displayfusion.com/Discussions/View/nvidia-app-surround-conflict-leading-to-black-screens-bootloop-with-hdmi-switches/?ID=01a0f73e-ba4d-71bf-931f-556d730d7959 Thu, 01 Oct 2026 11:34:38 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-app-surround-conflict-leading-to-black-screens-bootloop-with-hdmi-switches/?ID=01a0f73e-ba4d-71bf-931f-556d730d7959 DisplayFusion Hi,
I am experiencing a severe issue when switching monitor profiles using DisplayFusion in combination with the new NVIDIA App (which replaced the old NVIDIA Control Panel/GeForce Experience).
My Setup:
• GPU: RTX 4070 Ti
• Configuration: Dual triple-screen setup (1x Triple Monitor Desk Setup, 1x Triple Monitor Sim Racing Setup).
• Connection: The center screens are connected directly to the GPU. The left and right screens of both setups are routed through physical HDMI switches to save GPU ports.
The Problem:
Previously, I used DisplayFusion to successfully switch the main/center monitor, then I enabled NVIDIA Surround for sim racing. However, since the recent NVIDIA updates where Surround was integrated into the new NVIDIA App, this workflow crashes the system.
If I switch profiles using DisplayFusion and then reboot the PC, the system boots into completely black screens (no signal on any monitor). The GPU/driver seems to enter a bootloop/EDID conflict because the new NVIDIA driver tries to load the last saved Surround configuration, but conflicts with the display state managed by DisplayFusion and the HDMI switches.
The only way to recover is to physically unplug all monitor cables from the GPU and plug them back in to reset the display topology.
It seems like the interaction between DisplayFusion's monitor profile switching API and the new NVIDIA App's Surround architecture is causing the Windows Display API to crash upon reboot.
Could you please look into how DisplayFusion handles monitor state changes when an NVIDIA App Surround topology is active?
Thank you! ]]>