GTX 970 Display Port restarting PC

[KonfuciousK]

So I have an issue with an all-new build. I have a dual screen setup, 2 x Dell U2412M and have them connected to my Palit GTX 970 Jetstream through a DVI and Display port.

The DVI on a single display works fine but whenever I introduce the display port connection, whether on both or one - doesn't matter which or both of the two I choose - there are intermittent restarting issues. Some days it is okay and others it won't startup until I disconnect (one or all) the DP cables. It won't get to the windows loading screen before the whole thing shuts down and starts up again.

Other specs; GA Z97P-D3 (F6 Bios), i5 4690k, 8gb Kingston fury 1866mhz.

I've checked around and there is apparently a bios issue but I have the most recent F6 and from what I found it is related to older versions. I would like to avoid sending the card back anywhere even if there are workaround methods.

Any help or thoughts appreciated.

 

[snips86x]

I've had this issue too with my 980Ti but since changing to a g-sync monitor, it's strangely not occurring as frequently.

I yet have to find a solution but I have a suitable workaround...

 

[meldarthx]

So I have an issue with an all-new build. I have a dual screen setup, 2 x Dell U2412M and have them connected to my Palit GTX 970 Jetstream through a DVI and Display port.

The DVI on a single display works fine but whenever I introduce the display port connection, whether on both or one - doesn't matter which or both of the two I choose - there are intermittent restarting issues. Some days it is okay and others it won't startup until I disconnect (one or all) the DP cables. It won't get to the windows loading screen before the whole thing shuts down and starts up again.

Other specs; GA Z97P-D3 (F6 Bios), i5 4690k, 8gb Kingston fury 1866mhz.

I've checked around and there is apparently a bios issue but I have the most recent F6 and from what I found it is related to older versions. I would like to avoid sending the card back anywhere even if there are workaround methods.

Any help or thoughts appreciated.

flipping the screens doesn't help I'm guessing; or trying another dp cable?

which bios is causing this issue; card or mb?

 

[KonfuciousK]

I've had this issue too with my 980Ti but since changing to a g-sync monitor, it's strangely not occurring as frequently.

I yet have to find a solution but I have a suitable workaround...

Just bought these new, though I fully intend to upgrade in the near future so nice to know that G-sync lessens the issue.

flipping the screens doesn't help I'm guessing; or trying another dp cable?

which bios is causing this issue; card or mb?

This isn't confirmed just what someone else found and shared with me; when the DP cable is connected the motherboard bios switches to F3 and back again to f6 when disconnected. I haven't witnessed this myself, not sure where to check if I'm entirely honest - all I can say is it is definitely version F6 when I go there. Which cable I use seems irrelevant, even tried an adapter to switch it into a DVI at monitor end for giggles and obviously no difference.

Also the testing is inconsistent as it can work fine for a few days then go kookoo again until I unplug the DP(s).

I wouldn't mind but the annoying thing about this 970 is that it has two DP and one DVI port, kind of regretting moving from my 290x now. :/

 

[meldarthx]

why would you move from 290X to 970 at best side grade; and more likely degrade

is the f6 the latest bios or is there anything later.

It shouldn't be possible for it to switch to earlier bios; as memory in the bios chip will only hold which ever microcode that's flashed to it; it can't story another; unless its switching to backup bios chip which would be even weirder.

 

[dazzerd]

I;ve had similar issues and nailed it down to having my dells usb hubs connected to a usb3 port, moved to usb 2 and it stopped.

But I though that was just a bug with the 3rd party usb3 ports I have on my x79 mobo thought it woud be fixed for native stuff but something else to check.

 

[KonfuciousK]

why would you move from 290X to 970 at best side grade; and more likely degrade

is the f6 the latest bios or is there anything later.

It shouldn't be possible for it to switch to earlier bios; as memory in the bios chip will only hold which ever microcode that's flashed to it; it can't story another; unless its switching to backup bios chip which would be even weirder.

Basically I had both of them for a while and got a chance to really test them out in the real-world. Both on FX-8350 and 4690k I found that the 290x did indeed have a much higher performance range but consistently had to underclock itself resulting in low fps performance spikes. The GTX 970 has at worst a 5% performance loss average but remains consistent with low and high fps being very close to each other. Opposite being true for 290x.

Also, recording gameplay on the GTX is far superior, there was no piece of software that I could find that could make the 290x perform or record better without significant loss to in-game frame-rates, Raptr came close and was only able to match it at times.

Just a shame about the ports, would be nice to have two DVIs on the GTX.

I;ve had similar issues and nailed it down to having my dells usb hubs connected to a usb3 port, moved to usb 2 and it stopped.

But I though that was just a bug with the 3rd party usb3 ports I have on my x79 mobo thought it woud be fixed for native stuff but something else to check.

Interesting, I have been testing a bunch of USB hubs and devices recently I'll have to see if it is one of them causing the issue. Good call!

 

[Trying]

You might want to check out the many net posts about problems with Dell U2412m's and Display port connections

I also suffered problems with associating a 7970 amd card with a Dell U2412m through display port, ... and to this day..haven't found a way to resolve the issue

I believe the Dell only knows Display port 1.1 and not 1.2, and this could be something to do with the root cause of the problem.

I am willing to learn, and be corrected if I am wrong.