StoleMyOwnCar
2[H]4U
- Joined
- Sep 30, 2013
- Messages
- 3,048
I've found that Nvidia cards are weird about what outputs they selectively turn on and off, and which ones they automatically detect, and I'm wondering if you folks know any way to manage it.
To further elaborate, I'll add a few anecdotal cases:
Honestly the Diablo 3 experience was probably the biggest wtf, but this topic is mostly regarding the first two cases.
To further elaborate, I'll add a few anecdotal cases:
- On my current 980 Ti I decided to make sure the rest of the outputs were working fine, aside from the HDMI (projector), 2xDVI (Qnix, HP), and 1xDP (RoG Swift) ports I was using at the time. When I plugged in my RoG Swift into one of the other two DP port connectors, it would not work. I thought the board was faulty and was sadly about to return it... but then I had some ideas. I unplugged everything and plugged in just one DP->HDMI adapter monitor into each of the remaining displayport connectors at a time... and restarted. It worked. Then I tried connecting stuff to the DVI ports again, but they wouldn't work now. My RoG Swift seemed to only work in the DP connector that I initially had it on when I first installed the GPU into my MB.
That tells me that not only does it limit the amount of outputs that are turned on at any one time, but that some will not work in conjunction. And worse yet, sometimes this sticks throughout boots, and even in the BIOS. If I had chosen any other DP connector, I would have likely declared the card as having a faulty DVI output when in reality it was just selectively turning it off! One time it was even fine at the UEFI but then stopped displaying at the windows startup. That tells me part of this is hardware related and part of this is software related; the card seems to have some internal memory of what it turned off and what it didn't...
\n - So I had two 780's that I was using in SLI with the exact same setup before I got this card. I put one 780 in a friend's computer, but the DP connector would just refuse to work. Thinking it was the card, I swapped it out for my other one. That one was the top card, and had the ROG Swift hooked into it, so I knew it had to work... yet it didn't. Again, same deal. To rule out the possibility of the monitor DP port being faulty (or at least make it less likely), I used a DP to HDMI cable and encountered the same scenario. Everything but the displayport connector was working with the new monitor. I'm not even sure what to do about this case. I found a thread that may help somewhere, but it's a bit of a long shot. Of course it's possible that somehow in the extremely short time both of the GPU's were out of my computer, the DP ports somehow got fried in both of them... I guess...
\n - This is probably unrelated, but I was playing Diablo 3 once on my 780 SLI combo. I wanted to put it into Windowed fullscreen, but I think Flux (this is a screen color temperature modification program) was messing with it. Long story short all the screens were displaying black. Thinking I had to restart, I did... and then none of the screens would display anything, even in the BIOS. When the Qnix alone was hooked in, it was literally displaying test patterns on the screen (yeah wtf I know). This persisted through bootups. Eventually what I had to do was hook a monitor into the other card in the SLI combo. That actually worked, although everything moved at a crawling pace and was a mess of stuttering (yes the mouse was having period hangs). Afterwards, I nuked the drivers with DDU and then reinstalled the Nvidia drivers and finally after a reboot everything was working again. I just find it bizarre that a game can mess up a card so bad that it persists through bootups.
Honestly the Diablo 3 experience was probably the biggest wtf, but this topic is mostly regarding the first two cases.
Last edited: