I have rather a strange setup while I muster obsidians (money) to properly upgrade the whole thing. But here's what I have:
- Intel 4790K CPU
- 32GB DDR3 memory
- MSI Suprim Liquid X, RTX 4090
- Dell S2721dgf (1440p, 165Hz)
- Dell AW2724dm (1440p, 180Hz)
- LG "HD 16" (720p, 60Hz)
Both Dell screens are pugged to the 4090 DisplayPorts while the LG one is to my onboard intel graphics (via DB15 VGA).
My main purpose was to check if I could stop display port hotplug from screwing my desktop every time I turn on either (or both) dispay port screens. VGA one is kept fine when I turn off the LG screen. Only disconnects when I really push out the cable.
While installing the driver, I found the FreeSync range options and felt like trying them (bad idea!). Both screens are GSync *compatible* (thus, no dedicated module) but I read in the loaded settings, 48-165 (or 180) to both screens.
Pulled both screens to 1 min fps/hz and ran restart64. System froze, not even keyboard worked or hardware power button (to soft shutdown on press). VGA screen (on intel onboard) displayed the desktop and mouse, and it didn't move either. Completely frozen.
Reset button to the rescue. Turned on with only the tiny VGA one working. Opened CRU and changed the display IDs to something else. Changed "D" of "DELL" to "X" and went with that.
Reset64 and voila, freeze after several blinks of the screens. At least I had progress.
Reset button again. Booted up looking fine, all three screens working.
Went to nvidia pendulum (g-sync test program). Even though it was fully tied to the AW2724dm screen, the S2721dgf one went blanking out until it settled off. AW2724dm when going below 40Hz or so, blinked gray as if the textures were not being rendered at all. I guess it would be too good to be true to just unlock the range and work.
Back to CRU, reset the configs to just use the same EDID as it loaded from the screens with no change. Reset. Hang. Reset button.
Booted up fine, now nvidia pendulum is back to its normal >40fps gsync compatibility, and went to test the EDID persistence with the S2721dgf.
When it turned off, it screwed my desktop as usual, I guess CRU was never meant to act like that anyway.
But when powering the screen back on, guess what. Haze and lock ups again. So even if I kept the same settings CRU could read from my screens, it simply imposed something that made things super unstable I guess.
Then I ran reset-all as per instructions in the main CRU thread. Reset64 froze everything again. (what?) and then after the reboot I have everything reset, including primary screen pointing to the onboard one (it was initially on AW2724dm), but no longer freezes. Fortunately I could revert back (after repositioning the screens, etc) to where I was before CRU.
In the end it was fancy an experience, sad nothing worked out as I wanted and I am still looking forward to something that busts this most hated display port behavior when turning off screens.
The "solution" so far is running a script that switches to a power saving "power plan" (1 minute puts screens to standby) and runs the blank screen screensaver. But I can still see the computer "waking up" from time to time without exiting the screensaver. Some pesky background tasks are waking up the screens even though the screen saver stays on until I move the mouse around.
(then, back to the script, when the screen saver exits it prompts whether I want to switch back to the performance power plan so that it stops sleeping screens in 1 minute)
Hope this somehow helps other people trying to use CRU with similar peripherals... or hopes![Smile]( "Smile")
- Intel 4790K CPU
- 32GB DDR3 memory
- MSI Suprim Liquid X, RTX 4090
- Dell S2721dgf (1440p, 165Hz)
- Dell AW2724dm (1440p, 180Hz)
- LG "HD 16" (720p, 60Hz)
Both Dell screens are pugged to the 4090 DisplayPorts while the LG one is to my onboard intel graphics (via DB15 VGA).
My main purpose was to check if I could stop display port hotplug from screwing my desktop every time I turn on either (or both) dispay port screens. VGA one is kept fine when I turn off the LG screen. Only disconnects when I really push out the cable.
While installing the driver, I found the FreeSync range options and felt like trying them (bad idea!). Both screens are GSync *compatible* (thus, no dedicated module) but I read in the loaded settings, 48-165 (or 180) to both screens.
Pulled both screens to 1 min fps/hz and ran restart64. System froze, not even keyboard worked or hardware power button (to soft shutdown on press). VGA screen (on intel onboard) displayed the desktop and mouse, and it didn't move either. Completely frozen.
Reset button to the rescue. Turned on with only the tiny VGA one working. Opened CRU and changed the display IDs to something else. Changed "D" of "DELL" to "X" and went with that.
Reset64 and voila, freeze after several blinks of the screens. At least I had progress.
Reset button again. Booted up looking fine, all three screens working.
Went to nvidia pendulum (g-sync test program). Even though it was fully tied to the AW2724dm screen, the S2721dgf one went blanking out until it settled off. AW2724dm when going below 40Hz or so, blinked gray as if the textures were not being rendered at all. I guess it would be too good to be true to just unlock the range and work.
Back to CRU, reset the configs to just use the same EDID as it loaded from the screens with no change. Reset. Hang. Reset button.
Booted up fine, now nvidia pendulum is back to its normal >40fps gsync compatibility, and went to test the EDID persistence with the S2721dgf.
When it turned off, it screwed my desktop as usual, I guess CRU was never meant to act like that anyway.
But when powering the screen back on, guess what. Haze and lock ups again. So even if I kept the same settings CRU could read from my screens, it simply imposed something that made things super unstable I guess.
Then I ran reset-all as per instructions in the main CRU thread. Reset64 froze everything again. (what?) and then after the reboot I have everything reset, including primary screen pointing to the onboard one (it was initially on AW2724dm), but no longer freezes. Fortunately I could revert back (after repositioning the screens, etc) to where I was before CRU.
In the end it was fancy an experience, sad nothing worked out as I wanted and I am still looking forward to something that busts this most hated display port behavior when turning off screens.
The "solution" so far is running a script that switches to a power saving "power plan" (1 minute puts screens to standby) and runs the blank screen screensaver. But I can still see the computer "waking up" from time to time without exiting the screensaver. Some pesky background tasks are waking up the screens even though the screen saver stays on until I move the mouse around.
(then, back to the script, when the screen saver exits it prompts whether I want to switch back to the performance power plan so that it stops sleeping screens in 1 minute)
Hope this somehow helps other people trying to use CRU with similar peripherals... or hopes
