

Seriously though, DisplayPort might be the most frustrating technology I've ever used. Works like a charm, and makes me feel like I'm working in an office circa 1997! My grand solution? Shut off the monitor connected via DisplayPort when I turn the computer off. I tried swapping out cables, using a DisplayPort/DVI adapter. The monitor powers down and will no longer receive a signal until the cord is completely removed and the computer rebooted. As near as I can tell, DisplayPort has issues whenever a monitor loses the signal connection, either through sleep/hibernation, or because the computer was shut off. How bizarre.Īnyway, I had a similar issue, and never really resolved it. I have never seen a thread with so many "one and done" posters in it. If it happens again I hope it only happens when I'm trying to turn on the monitor, not while I'm in the middle of a work session or trading stocks. I wouldn't be suprised if it happens again.maybe my video card or mainboard or some other part is wearing out.
#Displayport autoturn off windows
I tried detecting it in the AMD FirePro Control Center.didn't work, although at least it showed the monitor as part of my desktop and didn't indicate that there was a problem, while in the windows display properties, it showed my monitor as being disconected or deactivated, and when I chose to activate it, it wouldn't take.anyway, while I was in the AMD FirePro Control Center, I did a few things, like turn on all 4 monitors, (which I already tried previously but didn't help) and for some reason while trying different things, I saw that the display resolutions on most of my monitors was set too low and also one monitor needed to be reset back to portrait mode, so I fixed that using the AMD FirePro Control Center, and when I turned the problem monitor on I was suprised to see it showed the desktop.also, the monitor resolution was not the cause of the problem.some monitors just happened to switch to a lower resolution during my troubleshooting episode.I don't know if any of that might help someone with a similar problem, but the problem seemed to get solved while adjusting settings in the AMD FirePro Control Center.also I think another important clue to the problem is that during the computer boot up, the "Windows is starting" message showed up on the problem monitor before it went black, which would seem to indicate it isn't a monitor problem, but something on the computer side. I tried detecting it thru the windows display properties.that didn't work. I finally got it to work except I don't know exactly what I did. I tried lots of things.(my displayport cables are only about a week old, as I recently replaced my older ones with new "approved" ones).Unplugged and plugged back in the display port cable from both the problem monitor and video card, unplugged and plugged back in the power cord to the monitor, exchanged displayport cables with a monitor that was working, turned the monitor on and off several times, shut down the computer and turned it back on.funny thing, when I shut down the computer and turned it back on, I thought that fixed it at first, because when Windows was starting up, both monitors showed the "Windows is starting" message with the animated logo showing, but instead of showing the desktop, the problem monitor just went black with the "no display port" signal. Turned my monitors off while I left the room for awhile, then when I got back to the computer, turned 2 monitors on, but one of them had the "no display port" signal. I have 4 pb278q monitors connected to a AMD firepro V7900 card.had this setup for over a year. I'm hoping that's the solution for whenever this happens, because beyond this nuisance bug, I'm very happy with the monitor. And then I remebered how it worked after I had tried the VGA, and doing that again (temporarily displaying through VGA) restored the DisplayPort capability. No sequence of rebooting, switching input modes, messing with the NVIDIA settings or re-plugging of the DisplayPort cable would bring it back. But then it hit again, and I think what happened was that the desktop power management feature put it to sleep. And then it worked without issue for a few days through reboots of the laptop and power cyclings of the monitor.

But then when I tried DisplayPort again it worked perfectly (full 2560x1440). Initially when I first tried it out, I couldn't get it to receive a DisplayPort signal at all, so then I tried the VGA cable, and VGA worked (at 1920x1080). It sounds like in some cases it doesn't know when to awaken after it is put to sleep. From reading this and other threads, it seems to be an issue with the PB278 monitor. I recently bought this monitor and had the trouble with no DisplayPort signal.
