DisplayFusion RSS: RTX 5090 + Dual Samsung Odyssey Neo G9 (57" & 49") - Monitor ID Drift Breaking Profile Switching https://www.displayfusion.com/Discussions/RSS/?TopicID=019bf62d-ab9f-731c-bb18-10597dea3c04 DisplayFusion RSS: RTX 5090 + Dual Samsung Odyssey Neo G9 (57" & 49") - Monitor ID Drift Breaking Profile Switching Wed, 06 May 2026 01:32:50 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=019bf62d-ab9f-731c-bb18-10597dea3c04 RE: RTX 5090 + Dual Samsung Odyssey Neo G9 (57" & 49") - Monitor ID Drift Breaking Profile Switching https://www.displayfusion.com/Discussions/View/rtx-5090-dual-samsung-odyssey-neo-g9-57-49-monitor-id-drift-breaking-profile-switching/?ID=019bf62d-ab9f-731c-bb18-10597dea3c04#2 Fri, 06 Feb 2026 20:50:28 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/rtx-5090-dual-samsung-odyssey-neo-g9-57-49-monitor-id-drift-breaking-profile-switching/?ID=019bf62d-ab9f-731c-bb18-10597dea3c04#2 DisplayFusion Apologies for the delayed response here!

DisplayFusion does try to fall back to the simpler Windows monitor IDs when loading a monitor profile if the hardware IDs don't match any more. Do the simple monitor IDs (1, 2, 3 etc) change as well?

Could you update to the latest 12.0.2 Beta and then send us a couple of debug logs?

  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and then click "Clear Log"
  • Manually configure the monitors how they should be and save that as a new Monitor Profile
  • Click the "Export Info to File" button on the Settings > Troubleshooting tab, save it
  • Change to your other profile, then try to load the newly created one
  • Click the "Export Info to File" button on the Settings > Troubleshooting tab, save it
  • Reply with both zip files attached
  • Disable debug logging after sending the logs

Thanks! ]]> RTX 5090 + Dual Samsung Odyssey Neo G9 (57" & 49") - Monitor ID Drift Breaking Profile Switching https://www.displayfusion.com/Discussions/View/rtx-5090-dual-samsung-odyssey-neo-g9-57-49-monitor-id-drift-breaking-profile-switching/?ID=019bf62d-ab9f-731c-bb18-10597dea3c04 Sun, 25 Jan 2026 17:22:27 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/rtx-5090-dual-samsung-odyssey-neo-g9-57-49-monitor-id-drift-breaking-profile-switching/?ID=019bf62d-ab9f-731c-bb18-10597dea3c04 DisplayFusion System Configuration
  • GPU: NVIDIA RTX 5090
  • Monitors (Workstation Profile): Samsung 57" Odyssey Neo G9 + Samsung 49" Odyssey Neo G9 (both DisplayPort, DSC active)
  • TV (Couch Gaming Profile): LG C1 OLED (HDMI)
  • Software: DisplayFusion (Latest), Windows 11 Pro
The Problem
When switching between my "Workstation" profile (both Samsungs enabled, TV disabled) and "Couch Gaming" profile (TV enabled, Samsungs disabled), returning to the Workstation profile fails consistently.
Symptoms:
  • Samsung monitors remain black or disabled after switching back from Couch Gaming profile
  • Windows fails to recall correct display topology
  • DisplayFusion cannot apply the profile because Monitor Hardware IDs have changed during the sleep/disconnect cycle
Root Cause (Confirmed):
The RTX 5090 combined with Samsung's DisplayPort DSC implementation causes monitors to generate new Hardware IDs upon waking from deep sleep. This ID drift causes a mismatch with the IDs saved in DisplayFusion profiles.
Per ToastyX (CRU developer), NVIDIA's driver ignores EDID overrides when DSC is active and the resolution/refresh rate exceeds the GPU's single-head pixel clock limit (1620 MHz for RTX 5000-series). This prevents any software-based EDID locking from working.
Troubleshooting Completed
  • Registry Reset: Deleted 
    HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
    (Configuration, Connectivity, ScaleFactors) to wipe corrupted monitor history
  • Driver Reset: Win + Ctrl + Shift + B successfully wakes GPU but doesn't resolve ID mismatch
  • Profile Recreation: Deleted old profiles and created fresh "Workstation" and "Couch Gaming" profiles after registry reset
  • DisplayFusion Settings:
    • Enabled "Include Disabled Monitors in Saved Monitor Profiles for Matching"
    • Disabled all Auto-Detect and Auto-Load Profile features (strictly manual switching via hotkey)
  • Samsung OSD Settings: Power Saving Mode OFF, Auto Power Off OFF, Eco Timer OFF, Auto Source Switch+ OFF, PC/AV Mode set to PC
  • Device Manager: No ghost monitors currently visible
Questions for the Community / Dev Team

Does DisplayFusion have any option to match monitors by DisplayPort output path (physical connection) rather than Hardware ID? This would bypass the ID drift issue entirely.
Is there a way to configure profiles with wildcard or partial ID matching for monitors that share the same model but generate different serial/ID strings?
Would a scripted function that calls 
restart64.exe
(CRU's driver restart utility) before applying a profile help force consistent ID detection?
Has anyone successfully used hardware EDID emulators inline with DisplayPort cables to solve similar issues? If so, which products worked?
Any other suggestions for achieving reliable profile switching with high-refresh DSC monitors?

Additional Context
I'm aware of the 
EnableTiledDisplay=0
registry workaround to force NVIDIA to respect EDID overrides, but this caps pixel clock at 1620 MHz which would significantly reduce my refresh rate capabilities. Looking for solutions that preserve full 240Hz functionality if possible.
Appreciate any insights from those who've tackled similar multi-monitor DSC configurations. Happy to provide logs, screenshots, or additional diagnostic info.

Edit:
Update:
After further testing, I've discovered an additional issue that may be contributing to or separate from the ID drift problem.
When I attempt to switch back to the Workstation profile (dual Samsungs) using DisplayFusion Remote, DisplayFusion appears to crash and freeze entirely. The application becomes unresponsive and the profile switch never completes.
This happens consistently when switching to the dual Samsung configuration, but not when switching away to the Couch Gaming profile (single LG TV).
I'm unsure if this is:
  • A result of DisplayFusion trying to apply a profile to monitors with mismatched Hardware IDs
  • An issue with enabling two high-resolution DSC displays simultaneously
  • Something specific to profile switching via DisplayFusion Remote
  • A combination of the above
Has anyone experienced crashes or freezes when switching to multi-monitor DSC configurations via Remote? Are there logs I should pull to help diagnose this? ]]>