thatonedude14

bcavnaugh
It is called having fun.

That's one hell of a price tag for "fun" lol.

You do not put a Price on Fun.

Unless you are a Miner Then it is all only Work.

Hello everyone, I've read all the thread ... very interesting, I've built the 3-way SLI a long time ago and it works very well, works well for video editing and very well for games, however I have a problem, I have the 385.69 drivers and I have been stuck there since all the driver versions after these, do not work and cause instability, I have read in several forums and even in the hall of fame of the 3d mark the team of (K|NGP|N) use the same 385.69 ... does anyone have an idea what happens with the new drivers? is this related to WDDM 2.3 ?.
 
Thank you very much and excuse my bad english.

I'm running 3 Way SLI with 1080 Kingpin. As for newer games getting away from it, Far Cry 5 is not the case, runs like a charm and actually solves an issue with screen flickering when you activate 3 way SLI, I'm running it on 3 screen 2K each, at 60+ FPS, highly optimized game.
 
Battlefield 1, is a different thing. That would run better in two way SLI, or even with a single card. We are used to be disappointed by EA anyways.
 
Battlefield 4 runs perfect, but will use all available resources, as it seems to be very inefficient with newer cards.
 
SimCity 5, forget about SLI at all.
 
It's been kind of complicated to use 3 way SLI, but in some cases you don't even have to deal with profile inspector. Stability has gotten better with the latest drivers.
 

CraptacularOne

GunslingerOCS
Vince says it's not the bridge.  It's probably a motherboard PCIe bios setting.

That’s why I told you to investigate the PCI-E lane allocations on your board

STILL running 3 GTX 980 KINGPIN on Z77FTW FOR 6 YEARS STRAIGHT never a problem using 3 way bridge that came with mobo  oc i7 3770k 4.9 GHz on liquid   , never buying a new videocard after buying EVGA 3090 TI AND 3060 TI ,,,

Finally got my pretty sketchy 1080 Ti 3-way SLI setup going.
 
Using an dld, outdated x79 Classified motherboard.  I had a Xeon 1680 v2 CPU, but, the motherboard wouldn't enable the second PCIe slot to run 3-way (I tried 2 1680 v2 CPU's).  So, I had to put in an old i7 3930K and run them using PCIe 2.0 (3.0 doesn't even work on this CPU ).  It was still fun playing around and benchmarking.  3 different 1080 Ti's- Kingpin, Black Edition and Silver.  I might eventually find a different color to add to the mix.
 
Ya, I didn't feel like removing the backplates to give the fans space.  So, I wedged Q-Tips and thermal paste spreaders to give them some room.  Put a Delta fan on top to give them more airflow- it's just a test bench.
 

 

vcbb10
Finally got my pretty sketchy 1080 Ti 3-way SLI setup going.
 
Using an dld, outdated x79 Classified motherboard.  I had a Xeon 1680 v2 CPU, but, the motherboard wouldn't enable the second PCIe slot to run 3-way (I tried 2 1680 v2 CPU's).  So, I had to put in an old i7 3930K and run them using PCIe 2.0 (3.0 doesn't even work on this CPU ).  It was still fun playing around and benchmarking.  3 different 1080 Ti's- Kingpin, Black Edition and Silver.  I might eventually find a different color to add to the mix.
 
Ya, I didn't feel like removing the backplates to give the fans space.  So, I wedged Q-Tips and thermal paste spreaders to give them some room.  Put a Delta fan on top to give them more airflow- it's just a test bench.
 

 

Nice. 😎👍

cool setup & creative wedges to help the cooling

Sajin
#7 Scroll down the settings list again until you find the section listed as unknown, and change the setting 0x10FD4C5F (7 profiles) to use 0x01F296C1. Scroll down more and change the setting 0x209FD306 (27 profiles) to use 0x0FC00008.
 
 

Its a few years into the future here, and "0x10FD4C5F (7 profiles)" did not exist in my "unknown" section. After going through the "unknown" section I found "0x1066ED2B" that needed to get changed to "0x01F296C1". However "0x209FD306 (27 profiles)" did exist for me, and needed to get changed to "0x0FC00008" as stated previously. 
 
Edit: I downgraded to driver 385.69. I found that the "0x10FD4C5F" did exist in the older driver, but not in the newer 566.36 driver. The new driver needs "0x1066ED2B" to be changed.