Hello all,

I have run across a strange issue (just started) and I am not quite sure as to what the cause could potentially be. From time to time, when I go to wake my monitors from sleep, one monitor will come on, but the other will not.  Occasionally, the waking on the one monitor will be delayed.  The only ways I can get it to come on instantly, is to restart the computer, or disable and re-enable SLI in the nVidia control panel.   Has anyone had this happen to them before? If so, was there a common fix?

I am running Driver 340.43. I have not installed any new software, or anything like that. I did remove both GTX 670's to clean them, but that is about it. 

Thanks
CHris

If you're having strange issues whilst running any iteration of the beta drivers, the best thing is to roll back to a WHQL release and see if the problems continue or are resolved.
 
It's also immensely helpful to the driver developers if you post about your experiences with the beta drivers in the driver feedback thread on the GeForce forums. This will alert the devs to the issues with the beta drivers, and on what hardware the issues arise so they can address them quicker. 

Hello Erin,
 
I went ahead and rolled back on my drivers, and I am still experiencing the same issues.  It worked fine for a few hours.  I went to wake them this morning and the issue was still relevant.  To recap, the following will fix the issue:
 
1. Disable and Re-enable SLI
2. Restart Computer
3. Disconnect one of the monitor cables (either one) and then reconnect.
 
Both video cards are EVGA GTX 670 FTW edition cards.
 
Any thoughts?
Thanks
Chris

Hey Bob,

I will check bios, but I am fairly certain it's up to date. Also this sli ran flawlessly for about a year and half prior. I did perform a clean install of non beta drivers. I can sweep them if there is belief that would yield better results.

Thanks
Chris

StealthArsenal
Just as an update.  At this point in time, it seems the issue is resolved.  Between reinstalling drivers and flashing my bios (apparently I was a bit outdated even though I thought I just did it. Maybe I switch to my secondary bios and didn't realize.).  In any event, it seems everything is working.

Thanks for the update.

I think that's a good progression to try testing.  You can also swap cables to see if the issue follows the cable, or if it remains on one of the cards.
 
Another thing you can try is to swap the order of the cards in the motherboard, and see if that fixes the issue. 

Just guessing, GPU driver, monitor drive or bad GPU or bad monitor.
 
I might of missed it, but what was ur system doing when you try/tried iGPI(onboard GPU only)?

Hello all,
 
The DVI cable with its extension is about 10-feet.  The DVI cable from the monitor is 4-foot connected to a 6-foot extension (I know this is rudimentary math).  I replaced both cables just to make sure they weren't causing any type of issue.  The funny thing is, the computer isn't 10-feet from the monitor, but because of the internal routing through my articulating arm and a couple of bends out to the backside of the desk, 4-footer was just too short and I had the extensions.  Just throwing this out there (it just dawned on me), I could swap this monitor to HDMI and run that cable to the computer.
 
Knight, this issue really only cropped up when I started this thread, so around July 15th or so.  Before that I never had this issue and it seems, as I stated above, that it is happening when SLI is setup.  I did disconnect my "properly functioning" monitor and just let the "troublesome" monitor run off the SLI setup and in the hour I had it running, it woke each time.  Doesn't mean it will continue to do that because of the small sample size with regards to testing.  I have never tried the onboard gpu, it has been disabled since day one of this system.
 
Thoughts?
Thanks
Chris