3

Problem Description

I am using the following setup:

  • nVidia GeForce GTX 680
  • Dell UP3214Q (Ultra-HD, 3840x2160, run in its native resolution, connected via DisplayPort 1.2, i.e. DisplayPort on GTX --> mini-DisplayPort on monitor, setup as primary)
  • Dell 3008WFP (2560x1600, run in its native resolution, connected via DVI-D, setup as secondary)
  • Windows 8.1 Pro x64
  • Latest nVidia- and monitor drivers

I am experiencing the following problem: Even when only waking up from Standby, all previously running applications get moved to the primary monitor.

Own Research into the Problem

Coming from a dual-monitor-setup using two DVI-D connections to the same graphics card, which did not exhibit the erratic window-rearranging, I suppose, that the current behaviour with the new setup might result from the nVidia GTX 680 treating DisplayPort and DVI-D somehow differently, which might trick Windows 8.1 into "forgetting" the secondary for at least a moment.

Further research

I found this collection of slides on DisplayPort from VESA, from which I deduce, that the UltraHD may not provide a (proper) signal on the Hot-Plug-Detect pin when soft-powered off or in the process of "awaking" from standby, while the 3008WFP seems to provide this signal on the DVI-D counterpart. So, my UltraHD does not get detected in time, leading to all applications being transferred to the 3008WFP first, and when the UltraHD finally reports its presence, all windows get moved back to it, since it is the primary. :|

Questions

  1. How shall I proceed to have my windows on their respective monitors after a wake from standby as I left them before going into standby?
  2. Would there be a possibility to fake the Hot-Plug-Detect signal on the UltraHD without losing the interrupt capability (see page 21 here)?

References

DisplayPort Technical Overview

Improve this question
7
  • I had the same issue and after a ton of searching found the answer here: superuser.com/questions/730258/… They several solutions to try but I found that the registry edit did the trick for me!
    – user432231
    Commented Mar 27, 2015 at 19:53
  • Thanks for the tip, but the registry key mentioned is nowhere in the registry (I searched the whole registry...). :(
    – Jinxed
    Commented Mar 27, 2015 at 20:06
  • Can the 680 do 2160p @ 60 Hz over HDMI? I'm thinking it might be a problem with the 30" being too slow to wake over DVI.
    – Louis Waweru
    Commented Mar 27, 2015 at 20:21
  • @Louis: No. Neither HDMI nor DVI-D are sufficient for 3840x2160@60, so I use DisplayPort. Thing is, the older 3008WFP works flawlessly in all cases. I think this has to do with DisplayPort 1.2 possibly not sending an "here is a monitor connected" signal, even when the monitor is turned off. DVI does this obviously. So, it seems to be a matter of not having monitors autodetected, but I am at a loss on how to accomplish this in Windows 8.x.
    – Jinxed
    Commented Mar 27, 2015 at 20:27
  • I was suggesting HDMI on the 3008WFP. I've noticed my setups have ordered and possibly acknowledged ports in this order: DP>HDMI>DVI>VGA.
    – Louis Waweru
    Commented Mar 27, 2015 at 21:32

1 Answer 1

Reset to default
0

Have you considered just not going into standby? Personally, I disable standby because of performance issues and never wanting the disks to spin down. Could be a simple, permanent solution or a temporary one while you try to figure out why the monitor loses it's signal.

Additionally, splicing in a 5v power transformer into the "hot wire" of the display port might be a trick into making it think it's always got signal. ---Risky---

Improve this answer
4
  • I considered that, but taking into account my power bill, ditching standby is no option.
    – Jinxed
    Commented Mar 31, 2015 at 15:21
  • Understood. You can also try slowing down the signal on the 3008WFP. I'm thinking using HDMI from the video card to an HDMI signal selector to the monitor. Adding in the device in the middle may slow down the auto detection enough to send signal to the UP3214Q first. (there may be a dvi-d signal selector too).
    – bhizzle1121
    Commented Mar 31, 2015 at 15:40
  • I am beginning to think, that the issue is with the UltraHD-monitor itself, since I got word, that more recent firmware releases do not show the issue I am experiencing. :(
    – Jinxed
    Commented Mar 31, 2015 at 15:42
  • Lame. RMA time?
    – bhizzle1121
    Commented Mar 31, 2015 at 15:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .