Hey, just thought I'd share my experiences with a rather particular setup, that's probably going to become more commonplace in the near future.
 
I recently picked up a TITAN, and decided along with it to change my desk layout, adding a secondary monitor via the DP 1.2 spec (which was just added in the 320.00 betas), and so far it's worked well when the computer is up and running, but it's when the computer is powered down that a problem exists.
 
See, DP still to this day has flaky support from the Green Team, and I'm starting to question how much of it might be related to the BIOS on the card, as a lot of the issues I've got with the TITAN were identical to the ones I ran into on my 690 (used in a HTPC). Every now and then, after a restart, the videocard "forgets" that a screen is attached via DP. The only solution to this is to disconnect the screen (or power down the monitor, as DP thinks this means you've DC'd it), which forces the videocard to redetect it...and if you've got a DP 1.2 setup like mine, that means shutting down both screens, starting them up one at a time, and resetting custom options. 
 
Now, to make matters even worse, if the system is running in UEFI mode, the videocard needs to support GOP to be able to use Windows 8's Secure Boot feature. Since I'm trying to be more conservative with my power consumption these days (meaning I don't really want to leave my system on 24/7 like I used to), and since Sleep Mode is still only stable for laptops and prebuilt PCs, having the ability to boot in <4 seconds from a system shutdown is great. While other GPUs need a GOP BIOS update, the TITAN comes preloaded with a Legacy and GOP compatible one...
 
...except the card doesn't know which one to pick at boot sometimes. After spending the weekend doing a full Windows 8 reinstall and a full mobo firmware upgrade/overhaul to get Secure Boot to be 100% compatible, I finally got some results: the BIOS boot screen scaled properly on my monitor -- which is a sign of UEFI GOP working -- and from Power Button to Windows was <4 seconds. However, after shutting the computer down and letting it sit overnight, I came back the following morning to a blank screen and the monitor being stuck in sleep mode at boot (even the keyboard becomes unresponsive at boot). This happened to me when I was experimenting with some of the UEFI settings while Win 8 was installed (before I reformatted everything), and meant that I needed to fully power down the computer and let it discharge completely before trying again. As far as I can tell, this is the only way to force the GOP BIOS to kick in on the TITAN.
 
I'm just wondering, has anyone else run into a similar issue? And if so, does anyone have any fixes?

Well, I'll shoot a message off to Dell (the displays are a U2913WM and U2311H), but the "display lost" behavior has occurred on a GTX 690 hooked to a TV/Home Theater via DP-to-HDMI (the receiver is a NR-717 and a Panasonic VT25), and a GTX 680 using both DP and HDMI outputs.

The issue is sporadic on the TITAN, but the GOP booting problem is a 50/50 occurrence.

The GTX 680 has a similar "lost display" when using HDMI as the primary output.

Is there a way to maybe force a certain connection to default as the primary? Could it be that the card is checking the DVI connection first and ignoring everything else if no display is connected?

Yeah, I did completely disable the CSM on my BIOS (I've got a Sabertooth X79), which is what first made me aware of the UEFI GOP BIOS kerfluffle, but this glitch still happens every now and then. I thought at first it was related to the 650 Ti I've got as a dedicated PhysX card, but I did do the GOP BIOS update to that one as well, because without it, the computer refused to even post without the CSM activated. 
 
Do you think I should try clearing the Secure Boot keys and reload them?
 
EDIT: Okay, tried loading and unloading the keys. Didn't really change much. Though it seems to start up 50% of the time properly, the other 50% gives me a blank screen and the BOOT_DEVICE_LED is brighter than heck at startup when things go wrong. Maybe this is more of a mobo issue...it's an X79 board, which hasn't had the best track record with NVidia components as of late...
 
Hey callofduty511 and ChrisB...what motherboards are you using?

Your not alone with this issue! I have GTX680 02G-P4-2683-KR model updated to UEFI GOP BIOS, when I updated to the 320.00 drivers all sorts of problems started with my DELL U2410 connected via DP, no problems with DVI-D or when using 314.22 WHQL, made me suspicious when I saw in the notes for 320.00 "DP 1.2 support"
 
I have already logged a support ticket with the NVIDIA driver team about a week or so ago but not heard anything back yet.
 
I am using Windows 8 pro, UEFI install/secure boot, CSM disabled.
Motherboard: ASUS Maximus V GENE Z77 Latest BIOS 1707, do I notice a trend here?, DELL monitors, Windows 8, UEFI GOP displayport, ASUS BIOS? I think there is something that needs to be looked into here.
 
I accept that we are probably in the minority of users using DP, Windows 8, UEFI GOP CSM disabled etc but it's obviously an issue nevertheless.
 
Thanks

Pretty sure the U2410 is DP 1.1 only, I cannot find anything in the menu related to enabling DP 1.2 I think this is only an option on late 2012/13 DELL monitors.
 
This was never an issue before the 320.00 driver which made me think its a NVIDIA issue, coupled with the mention of DP 1.2 support but given my monitor is DP 1.1 has something fundamental to DP changed in this driver revision? or is it a bug within the UEFI GOP BIOS or something to do with the monitors that causes the problem now a change has been made in the driver software...
 
Below are some pictures I took to show the issue, I also have a video I can upload to youtube.
 

This is just an idea that has worked for me in the past -- I used to have a Gigabyte X58A-UD3R motherboard that had weird issues (USB keyboard and/or integrated Ethernet wouldn't be detected at boot) after I put my PC to sleep and/or shut it down for a while. The solution turned out to be replacing the motherboard CMOS battery -- once it had a fresh new battery all the strange quirks went away. Can't say it will help in your case, but it's worth a shot (and it's cheap to replace), given the problems occur after being off.

funny I had the same problem with my 580's, seems to have gone away after a system upgrade (got the Titan and a Rampage MB). cant tell you how many DVI to HDMI converts I bought as I thought I had a bad connection. good luck!
 

Well, the new drivers didn't work. Just tried the 320.49 on both computers, and while the TITAN equipped one seemed to take the driver update fine, my 680+650ti tower connected via DP just locked up on the uninstall/reinstall portion of the driver setup, and just tapping the front power button immediately shut the system down (which only happens on a complete failure).

'm wondering...does the way the drivers identify panels have any sort of priority? My DP 1.2 panel chains to a 1.1a panel, but frequenly, the 1.1a panel will engage, but the 1.2 panel will remain off...if it even starts. I've been forced to disable the 1.2 support just to install drivers...arg...