EDIT BY EVGA (8/30/2016)
We have identified this and can confirm that this occurs on a small number of 1080 FTW cards. We have found the root cause and have corrected it. If you are experiencing this problem please contact us directly at 888-880-3842 or at support@evga.com.

 

EDIT BY EVGA (10/24/2016)
Recently, there are many customers wanting to know more details about the EVGA GeForce 1080 FTW “Black Screen” issue and we believe we need to make a clear statement to clear all kinds of speculation.
 
The EVGA GeForce GTX 1080 FTW “Black Screen” issue was fixed as of the first week of September and this has been confirmed by all users who have received the replacement units with the issue resolved. Also, all new production has been confirmed to not have this issue after the first week of September.
 
This previous black screen issue was caused by On Semiconductor (VRM IC Manufacturer) VRM IC’s being out of spec, triggering the OCP (Over Current Protection) and will not cause any damage to your system. The percentage of the IC’s that were out of spec has been confirmed by On Semiconductor and is approximately 3% to 4%. Since then, EVGA and On Semiconductor have worked out the solution and RMA replacement action a couple months ago as we stated above.  At this moment, all of the EVGA GeForce GTX 1080 FTW’s have been corrected and all products in the field are working properly.
 
If you have any questions, please contact our support directly at: support@evga.com. 
 
Thanks,
EVGA

 
 
I'm running into some issues with my new GTX 1080 FTW.  Thinking I may be out of options short of RMA, but wanted to check here and see if maybe there is anything that can be done.
 
This is a brand new system build that I put together and had been running without issue for 2 months with a EVGA GTX 760 while waiting to purchase the 1080 to complete the build.  MB BIOS and drivers are all up to date and this is far from my first PC build.  I am, not currently overclocking anything in this system(see specs in sig)  To install the 1080, I ran DDU to clean up all the old 760 drivers.  Then did a clean install of just the 368.81 drivers and the physx software.  The only changes I have made from a stock driver install are things I've picked up researching the card.  
 
Those changes are as follows:  (Note: The lock-ups happen before and after these changes)
Running Precision Xoc with the aggressive fan settings.  (I like my cards cool.  As I type it is sitting idle at a nice 32c)
Enabling Nvidia's Multi Display Power Saver.  It's configured to activate full 3D by GPU usage of 30%.  (This was a recommendation from a thread on Nvidia's site for multi-monitor setups.)  
 
This has happened to me on multiple occasions now while playing Witcher 3 and Battleborn.  Sometimes I can get in 4 matches of Battleborn, other times only 1 before this happens.  With Witcher is seems random as well.  My 2 monitors will go black, and I can hear the fans spool up on the video card to what must be 100% (if not higher).  The only way out of this state is a reset or power cycle.  When windows 10 comes back up, my event log is full of errors.  Today after work it happened and I counted 1954 separate Errors from the 1 event.  Each one appears to have slightly different information included but all from \Device\Video3.
 
Just a small handful from the almost 2000 errors that appear in the Windows Event log under System:
Graphics Exception: Injected Bundle Error
Graphics Exception: Class 0xffff Subchannel 0x7 Mismatch
Graphics Exception - Speculative Go Idle
Graphics Exception: EXTRA_INLINE_DATA
Graphics Exception: MISSING_INLINE_DATA
Graphics Exception: SKEDCHECK02_LOCAL_MEMORY_LOW_SIZE failed
Graphics Exception: SKEDCHECK03_LOCAL_MEMORY_HIGH_SIZE failed
Graphics Exception: SKEDCHECK04_LOCAL_MEMORY_CRS_SIZE failed
Graphics Exception: SKEDCHECK05_LOCAL_MEMORY_TOTAL_SIZE failed
Graphics Exception: SKEDCHECK06_REGISTER_COUNT failed
Graphics Exception: Shader Program Header 0 Error
Graphics Exception - INSTR_RAM_ACCESS_OUT_OF_BOUNDS
Graphics Exception on GPC 0: 2D SYSMEM KIND Violation. Coordinates: (0xffff, 0xffff)
Graphics Exception on GPC 0: POOLPAGE_INVALID
Graphics Exception on (GPC 0, PPC 0): ESR 0x503038=0xffffffff
Graphics Exception on (GPC 0, PPC 0): PEM_TGB_FILL_BD_P02_ERR
Graphics Exception on (GPC 0, PPC 2): ESR 0x503438=0xffffffff
Graphics SM Global Exception on (GPC 0, TPC 0): Physical Multiple Warp Errors
Graphics SM Global Exception on (GPC 0, TPC 0): VAT ALARM Errors
NVRM: Graphics TEX Exception on (GPC 0, TPC 1): TEX APERTURE
NVRM: Graphics TEX Exception on (GPC 0, TPC 3): TEX NACK / Page Fault
Graphics Exception on (GPC 1, PPC 0): ESR 0x50b038=0xffffffff
Graphics Exception on (GPC 1, PPC 1): PEM_TGB_FILL_WK_P01_ERR
NVRM: Graphics TEX Exception on (GPC 1, TPC 0): TEX NACK / Page Fault
Graphics Exception on (GPC 2, PPC 1): ESR 0x513238=0xffffffff
Graphics Exception on (GPC 2, PPC 2): ESR 0x513438=0xffffffff
Graphics SM Global Exception on (GPC 2, TPC 1): ECC SEC Error
NVRM: Graphics TEX Exception on (GPC 2, TPC 3): TEX LAYOUT
NVRM: Graphics TEX Exception on (GPC 3, TPC 0): TEX FORMAT
Graphics Exception on (GPC 3, TPC 1): ACACHE_ERR
 
I was also running GPUz and logging during the last lock up, trying to catch anything out of the ordinary there.  Now the full log is not very forum friendly, but nothing showed out of the ordinary to me before the lockup when most stats show 0.    Battleborn doesn't exactly stress the system with a resolution of 1920x1080 either.
 
GPU Temperature [°C] , Fan Speed (%) [%] , Fan Speed (RPM) [RPM] , Memory Used [MB] , GPU Load [%] , Memory Controller Load [%] 
45.0   ,                           55   ,                     1468   ,                              3019   ,                  42   ,                       12 
46.0   ,                           55   ,                     1464   ,                              3019   ,                  40   ,                       13 
 0.0   ,                             0   ,                           0   ,                              3019   ,                    -   ,                        -   
 0.0   ,                             0   ,                           0   ,                              3019   ,                    -   ,                        -   
 
My next step based on this forum will be to put the card into Debug Mode as suggested in one of the main threads here.  But based on my experience thus far, I wont be holding my breath.  Any suggestions would be appreciated.
 
Thanks

Just checked the newegg order for kicks, and it was on 5/6/2016.  So i guess it's just over 3 months now.  For what it's worth the power supplies monitoring system (Corsair Link) shows that while gaming the system power draw is well within it's capability. 
 
I should have enough spare cables to give that a try.  Right now I'm trying to see if it will crash on me in debug mode.

Brutal
2 hours of gaming in debug mode down.  No errors, no crashes.  I plan on testing a bit more tomorrow, but RMA is beginning to look like the path I'll have to take.  :(

It happens. At least you'll get another new card since you're within the first 30 days of purchase. 

I'm having this exact same issue. I can replicate it in monstrom after just 2 min of play.
I have done a clean install of drivers. A driver roll back. Underclocking the card. And I even set a very aggressive fan curve. Still nothing.
Am I going to have to RMA my card as well?

This has happened to me as well with my 1080 FTW. So far, I've only been able to replicate it in World of Warcraft in a specific spot, Time Spy stress test and Overwatch haven't resulted in any crashes, so it doesn't sound as bad as yours. Still, I'm leaning towards RMAing, especially since other people are having the problem with a variety of games and it's not just my system.

It has been happening with GTX 9 series as well.....
 
http://forums.evga.com/Intermittently-Screens-Go-Black-System-Still-Active-m2528533.aspx
 
From my experience only certain DX11 games cause it, but I've had it occur with DX9 randomly as well. Trying to figure out what is causing it and haven't had the problem reoccur since I uninstalled the physx drivers.

fearpoint
It has been happening with GTX 9 series as well.....
 
 
 
From my experience only certain DX11 games cause it, but I've had it occur with DX9 randomly as well. Trying to figure out what is causing it and haven't had the problem reoccur since I uninstalled the physx drivers.

This sounds similar, but when mine occurs the only course of action is a power cycle.
 
FWIW the issue is much more common while playing Battleborn, than my other games like Witcher 3.  A game crash is one thing, but a hard lock that forces a power cycle to clear is not good.  The last one while in Debug Mode, triggered my RAID drives to into a very long verification and recovery check.  Thankfully nothing was wrong there when it completed.  
 
Also to address Sajin's suggestion to which i never replied, to try re-seating the card and swap power cables.  I Have done that and unfortunately it continues to happen.
 
I'm awaiting the RMA to ship at the moment.

Just had this happen with my 1080 FTW in World of Warcraft - happened twice straight after as soon as I launched anything that used 3D (WoW and Overwatch menus) - temps were fine at 40c.
 
Have the card running on a pretty new AX1200i (Don't ask) in a Z170 Sabretooth.
 
Reseated the card into the same slot and power plugs and its working again, but I'm keeping a close eye on it.

Received my 1080 FTW a week ago today and have had this happen 10 times so far. Tried all the fixes I could possibly find and finally called EVGA support who told me the card probably had an unstable clock. (Peaking at 2025 MHz and haven't increased the offset at all) I've played WoW, MGS5 and No Man's Sky the past week and only WoW was doing the black screen lockup + 100% fan ramp up. Heaven/Valley on repeat for 2 hours did nothing either. The solution the rep gave me was to enable V-Sync in WoW which so far has worked, I've left the game running all last night and today with no crashes.  If it continued to happen he recommended down clocking the card or just going for an RMA. 

Happened to me twice today. The only change i made was putting the voltage slider in Precision x to 100% which increased my voltage from 1.050 to 1.094. Iam using a EVGA supernova G2 850 gold and updated to latest driver that came out today after the first time it happened and reseated the card with no change. Going back to stock profile to see if it happens again. Something else to note is that both time i got black screen 100% fan and had to reset/power cycle was during World of warcraft (game wasnt even pushing the card I had it fps capped at 144). My old card was gtx 780 and 1.2V was no issue for that card. If it happens again I'll likely RMA it (unless a fix comes out) since it has terrible coil whine as well.
 

I'm having the same issue. Happened a couple times with Witcher 3 and just occurred tonight with Gauntlet. I don't think it's a stress/heat issue. I had HW monitor running with Witcher 3 after the first crash and CPU and GPU were not overheating before crash occurred. Using two monitors, one 27" using display port at 2560x1440 @ 144Hz, and another 27' using HDMI at 1920x1080 @ 59Hz. Both screens would go black and monitors would indicate no signal detected. System still running in background and any commands I do I can still hear working in game. Reset will cycle through the boot process but still no display. Only way to fix is to do a hard power cycle. I just got this GTX 1080 FTW less than a week ago. 
 
Edit:
I found other threads with similar problems with 9 series video cards from EVGA. Is this a common problem with EVGA? I had no issues with my previous MSI 980 that was previously installed in the same system.

That is just how gpu boost 3.0 works. If the problem was the card boosting too high with low temps it should artifact or driver crash i would have thought. Isnt the black screen fans at 100% a fail safe for when the card is overheating?

This only happened to me on my 970 when I had low power input to the card...stopped happening when I fixed that.
 

o/
Well to start off I never had the coil while issue with my card.
 
I did receive the new card from RMA today, and installed it when I got home from work.  
 
Started off with a Heaven benchmark to sort of warm it up.  The results were slightly better than the first card but hardly worth mentioning.  After that I spent a couple hours playing Battleborn because that was the game that triggered crashes most often for me before.  Took a break to cook/eat dinner then played a couple more hours.  No crashes yet!
 
Now with the old card I did manage to have one night of gaming where it didn't crash.  So I'm taking this first evening with a grain of salt.  I'll be keeping an eye on things until the card has more than a few hours of lightweight gaming under it's belt.  Doom, Witcher 3 and Just Cause 3 will all make the 1080 actually try.  I've also been wanting to spend some time in Fallout 4, Dying Light and some other old ones to enjoy what it's like with everything maxxed.     

Well, I was crashing pretty consistently in Heroes of the Storm, but I noticed that the back plate of the card was (excuse the cliche) hot enough to cook an egg on. I think that something else on the PCB, maybe the ram or some other component is overheating. I ran the fans at 100% with the case open and my gpu didn't exceed 43 degrees, and didn't crash once. Before I was crashing when I hit 70 degrees and maintained that for more than a couple minutes. I'm wondering if this is a design flaw, or a flaw in just my card?
 
Can anyone else having this problem try that solution? Granted, I did a lot of other fixes before this, including step 1 & 2 in Sajin's troubleshooting guide (very nice by the way, thanks), but maybe someone can confirm.