2016/10/19 10:02:59
smjameel93
AHowes
EZtouch
AHowes
Looked like his black screen fix was to reset the mb bios (pulled cmos batttery) and load optimised default settings and reinstall the 1080.

Still could be an issue with another setting on the board like do you have the main gfx set to pcie or built in as in the gpu built into the cpu?

I believe there's a setting to turn off the built in gpu. I think there was on my z97 board but don't see the option on my z170 but just an option to choose the main display on built in or pcie.

Already tried turning the igpu off without success. /that person said he reseted the bios but it didn't work, the issue did not go, then he plugged in a 970 and he saw the boot sequence, then when he put the 1080 back the issue went away.


What I took from it is that he feels the clearing of the cmos and slapping the 970 back in and getting into Windows and uninstslling the prior gpu drivers using DDU and then installing the 1080 and seeing it post for the first time he felt that fixed it.. though we all know uninstallling the drivers first didn't fix it but it's obviously the right move to uninstall the old drivers first anyways when replacing a card so it won't interfer with the new card.

So you feel since he put the 970 back in the mb and held the cards bios so when he put the new 1080 in it worked cause it was still holding the info from the old card and eventually won't work soon after again't cause it will loose the old info.

I'm not sure that's how it all works. Would think the only info being passed is from the card to the monitor but yeah the motherboard would be allowing the card to send it.



 
I believe that he had an older driver (see post time), which did not support the 1080. As he was without a working GOP driver, the windows basic driver did not load up.
Then he booted with the 970's GOP driver (which the NVIDIA driver took over after windows load) and upgraded his driver to the one which supports the 1080.
Now, even if he faces the same issue, he got the NVIDIA driver available after loading windows to take over the GPU.
 
I think your issue is very similar to his and most likely the same.
 
Did he mentioned the motherboard which he uses, if its ASUS as well, it might be better to inform ASUS of this issue as well. Never the less, EVGA is the current maker of the GPU for all similar issues, yours, the few you linked before, and his.
2016/10/20 08:51:53
EZtouch
So I thought the only issue was that I couldn't access the UEFI BIOS settings, safemode and advanced startup settings when the issue happens....
 
But now this happened:
I was using Windows 10, I had google chrome opened
I left my pc for a while (probably 1 hour)
I came back to it, the screen was black, I thought it was on standby, so i moved the mouse, clicked on the keyboard, still HDMI1 no signal...
I tried pinging my pc using its name and IP, but it was unreachable (I use a static IP)...
So I had to turn it off using the power button on my case, and when I clicked on it again to turn it on, I heared only one beep (I used to hear 3 beeps and the 1080 wouldn't show the boot sequence), I thought maybe the issue fixed itself, but it is worse now.
I waited and waited, I cannot ping it, I think it's not posting now...
I did not change anything.
 
I will try to do a cold boot and see if that helps.
Update: turning off the PSU and powering on the pc to clear the energy for a cold boot, then starting the system DID NOT solve the problem. Again, I was on Windows 10, then it black screened/crashed and I can't ping my pc anymore, then it can't post anymore, did not change anything in the hardware, software, settings anywhere.
2016/10/20 11:48:50
AHowes
That sucks.. now it's like what's dead.. cpu/mb? Unplug everything you don't need to post.

Though you can try another gpu to make sure it's not that.
2016/10/20 11:57:09
Sajin
EZtouch
So I thought the only issue was that I couldn't access the UEFI BIOS settings, safemode and advanced startup settings when the issue happens....
 
But now this happened:
I was using Windows 10, I had google chrome opened
I left my pc for a while (probably 1 hour)
I came back to it, the screen was black, I thought it was on standby, so i moved the mouse, clicked on the keyboard, still HDMI1 no signal...
I tried pinging my pc using its name and IP, but it was unreachable (I use a static IP)...
So I had to turn it off using the power button on my case, and when I clicked on it again to turn it on, I heared only one beep (I used to hear 3 beeps and the 1080 wouldn't show the boot sequence), I thought maybe the issue fixed itself, but it is worse now.
I waited and waited, I cannot ping it, I think it's not posting now...
I did not change anything.
 
I will try to do a cold boot and see if that helps.
Update: turning off the PSU and powering on the pc to clear the energy for a cold boot, then starting the system DID NOT solve the problem. Again, I was on Windows 10, then it black screened/crashed and I can't ping my pc anymore, then it can't post anymore, did not change anything in the hardware, software, settings anywhere.


Sorry to hear that. Remove the gpu, clear the cmos & try booting off the igpu.


 
The solution to accessing uefi bios settings, safe mode & advanced startup settings... 
 
http://www.tenforums.com/...side-windows-10-a.html
2016/10/21 04:05:06
EZtouch
removed the 1080
plugged in the 970
the bios recovered automatically to the default settings after installing the 970
reseting the settings of the bios now by removing the cmos battery just to be extra sure that everything is reset
configuring the bios setings back to how they were using the 970
Downgraded the motherboard BIOS version to a MUCH older version, will see if the issue comes back in the old bios version
plugged in the 1080 back
 
I've analysed the memory dump, and it appears that the plexturbo software was responsible for crashing windows, I think it rebooted into advanced startup after the crash, and that's why it stayed a black screen, as the hybrid's issue causes the motherboard to be unable to read the gop uefi driver. I've uninstalled the software so hopefully no more crashes.
 
@Sajin when the issue happens, and the UEFI BIOS of the hybrid is not loaded, I will be stuck if I try to access safe mode/advanced startup settings, and I will have to pull out the CMOS battery to enable CSM which emulates the legacy BIOS, then turn it off and setup the boot devices to be able to get back to Windows
 
 
I'm now running benchmarks / stress test applications (unigine valley, heaven, 3dmark, gta v), I will let it run for a while (at the moment the issue is not present), then I will lock the pc, and from the lock screen I will click restart (again, I'm now on a MUCH older motherboard BIOS version) and see if the issue comes back anytime soon.
 
At the moment the issue is not present, no beeps, no VGA_LED that stays lit all the time.
2016/10/21 04:45:47
The Rudster
Just something to note, have the exact same issue with my GTX 1080 FTW Hybrid here
 
I have had it boot once but on reboot after installing new drivers, no post. tried three other systems, same issues. GTX 550 ti, 790 ti, 950 all work but the 1080 does not. There is something wrong with I would say there is something up with some of the 1080 FTW Hybrid cards. I tried running it in a Z87-WS (Mine) h170m-plus (Testbench) z170m-plus (work system) and a z87-gryphon (Work system). All had issues. the Z87-WS have failed to boot it, the ws once.
Booted with CSM on after a complete cmos reset but have not been able to replicate the issue. I believe there was one more person with the same issue in France that posted a week or 2 ago about it.
Seems OP is able to get his to post now and then but I'm having no luck. Anyone know if EVGA knows about this specific issue? Unrelated to the black screen 100% fan issue.
 
Would be interesting to know if OP can boot with a second card installed (If the motherboard has a second 8x slot) and see if the GPU has an error in mine when viewing it in device manager. Error Code: 43
 
I even went as far as updating the individual modules in the bios and flashing a completely custom bios because ASUS abandoned my board after just under a year
2016/10/22 02:41:37
EZtouch
And the issue is back! :(
No hardware/software/configuration was changed.
 
VGA_LED lit all the time.
Beeps: beep                      beeeep   beep beep beep
Cannot see boot sequence/no display before windows loads.
The motherboard cannot read the UEFI driver of the hybrid 1080, therefore no display, until windows loads the driver
If I try to access safe mode I will not have display.
I only have display when windows is loaded.
 
Update:
removed the display cable from the graphics card
turned on the pc (no display connected), same vga_led lit all the time and the beeps stayed the same
turned it off
connected the display back to the hybrid 1080
turned it on, this time no beeps... but also no display, and can't ping the pc, seems like its not posting.. restarting it or turning it off did not help. cold boot did not help either.
 
no display, cannot ping the pc.. I will have to reset pull out the cmos battery again I guess
 
 
Update2:
It seems to me like there is a bug/issue in caching things..
1080 installed (MB cannot read its UEFI bios), vga_led lit all the time, issue#1
install 1060 in place of 1080, boot, no issues
install the 1080 back, issue#1 is gone
next day turn on the system/cold boot it
issue#1 is back
try going into safe mode/ or booting without display cable connected and the system will not post/cannot see anything, issue#2
plug the display back into the 1080, still no display and no post... issue#2
reset the bios by pulling out the CMOS battery, then configure exactly the same settings as before
issue#1 is back
plug in any other card in place of the 1080 (tried evga 970sc and msi1060)
turn on the system, no issues
turn it off, place the 1080 back
issue#1 is gone
 
repeat..
2016/11/14 11:17:03
EZtouch
Update:
For 3 weeks I've been using an MSI 1060 on my system now, not a single issue.
Today I plugged in my 1080 FTW Hybrid back, same port, same monitor, same system, red vga_led light lit all the time, beeps that mean "no VGA" according to ASUS' website.
Restart, shutdown, coldboot, the issue persists. Can't see anything on screen before windows loads.
I turned off the PC, and this time plugged in an HDMI cable instead of DVI, no red lights, no beeps... looking good
 
I will continue monitoring the system to see if the issue does came back on HDMI.
I'm suspecting that the 1080's DVI port has an issue or the BIOS of the 1080 has an issue with this specific port. the monitor and cable did work with the 1060, and my system worked flawlessly with it; it supports pascal GPUs.
2016/11/15 06:00:36
EZtouch
The issue did not come back on the HDMI port yet.
 
On other news, it seems that I have around 25GB of graphics memory

 
2016/11/15 06:03:10
Jimbo2112
EZtouch
The issue did not come back on the HDMI port yet.
 
On other news, it seems that I have around 25GB of graphics memory
 

Mine says that as well.

Use My Existing Forum Account

Use My Social Media Account