so i picked up a 1060 SSC for a build im doing for someone for christmas, rest of hardware is a ASRock H270 ITX, 6600 cpu and 16GB ram, M.2 boot drive, PSU is a EVGA G3 550. win10 all the latest updates and drivers.
now the issue is at boot, either cold or restart the display ports take a very long time to come on, no bios screen, then all of a sudden the mouse and keyboard light and i get the win login screen. if i switch to HDMI or DVI it works normal, see the bios screen, windows logon is there very fast. i have tried three other GPU's, 950, 970 and even a quadro card with display port and they work flawless, i even put my 1080 FTW2 in it and it works fine. everything else with the card works great, good temps, very stable. and if i connect the display port after boot they work perfectly. any suggestions?

AHowes
Have you tried the other display port connection on the card. Make sure it's fully inserted.

Might be handshake issue.. monitor on before you power on the pc? I know if I don't have the power on my 4k screen before I hear the post beep of the pc it's hell to pay with usually needing to remove the HDMI connection and reinserting it to get the screen to come on. That's using a 4k ultra HDMI to display port adapter as I'm using the HDMI to Oculus rift vr.

yep all three do the same, on two different monitors with two display ports on each monitor, the ones im using right now actually and they work just fine, the cable is fully seated and click when i insert them. the board doesnt have a beep speaker or even a connection i can find for one.

HeavyHemi

quadlatte
so i picked up a 1060 SSC for a build im doing for someone for christmas, rest of hardware is a ASRock H270 ITX, 6600 cpu and 16GB ram, M.2 boot drive, PSU is a EVGA G3 550. win10 all the latest updates and drivers.
now the issue is at boot, either cold or restart the display ports take a very long time to come on, no bios screen, then all of a sudden the mouse and keyboard light and i get the win login screen. if i switch to HDMI or DVI it works normal, see the bios screen, windows logon is there very fast. i have tried three other GPU's, 950, 970 and even a quadro card with display port and they work flawless, i even put my 1080 FTW2 in it and it works fine. everything else with the card works great, good temps, very stable. and if i connect the display port after boot they work perfectly. any suggestions?

What it almost sounds like is the GPU is acting like it's initializing the DVI and HDMI ports as if a display was connected to them during boot and not recognizing a display connected to the DP and initializing that port during boot. Have you tried a different cable that is DP certified is the only thing I can think of. I don't know it trying it in another system would make any difference.

Tried 5 different cables, 3 were brand new certified cables. Even with now hdmi plugged in it does the same, and even if the hdmi is connected it does the same, with no displayport connected and only hdmi it works fine. I may try it in my rig which has a debug led and beeper

HeavyHemi

quadlatte

HeavyHemi

quadlatte
so i picked up a 1060 SSC for a build im doing for someone for christmas, rest of hardware is a ASRock H270 ITX, 6600 cpu and 16GB ram, M.2 boot drive, PSU is a EVGA G3 550. win10 all the latest updates and drivers.
now the issue is at boot, either cold or restart the display ports take a very long time to come on, no bios screen, then all of a sudden the mouse and keyboard light and i get the win login screen. if i switch to HDMI or DVI it works normal, see the bios screen, windows logon is there very fast. i have tried three other GPU's, 950, 970 and even a quadro card with display port and they work flawless, i even put my 1080 FTW2 in it and it works fine. everything else with the card works great, good temps, very stable. and if i connect the display port after boot they work perfectly. any suggestions?

What it almost sounds like is the GPU is acting like it's initializing the DVI and HDMI ports as if a display was connected to them during boot and not recognizing a display connected to the DP and initializing that port during boot. Have you tried a different cable that is DP certified is the only thing I can think of. I don't know it trying it in another system would make any difference.

Tried 5 different cables, 3 were brand new certified cables. Even with now hdmi plugged in it does the same, and even if the hdmi is connected it does the same, with no displayport connected and only hdmi it works fine. I may try it in my rig which has a debug led and beeper

I suspect this is either a defective GPU or a fault in the firmware.  It would be interesting just as a data point to see if a different system gives any different results even if it's just a code or beep for EVGA.

about to try that now. checked the bios of the MB and all looks good there as far as settings go soi going to try it in my z270 classy now

AHowes
Real quick.. do you happen to have the built in gpu enabled in the bios?

Nope its disabled.

Put the 1060 in my main rig and it worked fine with the DP cable plugged in, so moved it back and used the same exact dp cable and no display for about 2minutes or so, here is another kicker, if i unplug the dp so in effect making the system headless and count to 15 then plug it in it has a display. Been search the inerwebs and found a lot of people have dp issues kinda like this but no real clear solution.

Nice.. I always buy Asus boards anyways but have been hearing a lot about ASROCK.. guess not!

quadlatte
so turns out this is a issue with the ASRock MB, something in the bios that ASRock "will look into" so guess that means probably never. i know what MB brand i wont buy again.

You gave yourself "Best Answer"? LOL.       

XrayMan

quadlatte
so turns out this is a issue with the ASRock MB, something in the bios that ASRock "will look into" so guess that means probably never. i know what MB brand i wont buy again.

You gave yourself "Best Answer"? LOL.       

I have had that happen before. I had issues with the RGB lighting on my ASUS motherboard. Even Asus gave me some answer of taking screws off of the motherboard and unplugging the RGB lighting and plugging it back in. Turns out the fall Windows update didn't load a file correctly and I had to just right click when unzipping the file. If I wasn't looking around for an answer I wouldn't have found out why the error happened. 
 
In this case hopefully ASrock is able to fix the issue with a BIOS update. Right now it seems like it could be a big enough issue to address.

XrayMan

quadlatte
so turns out this is a issue with the ASRock MB, something in the bios that ASRock "will look into" so guess that means probably never. i know what MB brand i wont buy again.

You gave yourself "Best Answer"? LOL.       

No. Cool GTX marked his post as the best answer.