Install driver 388.71 & then use DSLIA. 

388.71 doesn't enable SLI but it claims patch succeeds. I will try 387.92 but first the README says
>  version 1.7 25/05/17 Supporting WHQL up to 382.33  
so I'll d/l that one first.

Maybe a silly question, but the jumper connector is still in place on the video cards, right?

Looks like you're out of luck.

https://www.evga.com/articles/00613/
https://www.evga.com/Products/Specs/GPU.aspx?pn=8A32A680-39FA-4EED-8FCF-EE6B0B1E0A5C
This card has single SLI Fork like the GTX 690 and runs Quad SLI unlike 4-Way SLI.
GeForce 326.80 Driver ^BETA Win 7
GeForce 385.12 Driver ^BETA Win 10, I Could not run my GTX 690 in Quad SLI under Windows 10

bcavnaugh
This card has single SLI Fork like the GTX 690 and runs Quad SLI unlike 4-Way SLI.
 ^BETA Win 7

Can you point me to more info re "single SLI fork"? I'll search on "Quad SLI unlike 4-Way SLI" also. Thanks.

The timing on that beta driver looks right. Perhaps I used that together with HyperSLI 0.96 (that I just found hiding under the /Windows folder). BTW HyperSLI references "/Windows/Sysnative", a folder I don't see in Win 7--is that causing the BSOD? Can I point those refs to "/Windows/system32"?

Update:
I've tried GeForce driver 326.80 beta, ditto DSLIA, ditto HyperSLI1.0, and ditto HperSLI0.96.
 
With the vanilla driver and DSLIA'd just no difference -> PhysX all 3 GPU but no SLI settings. Both HyperSLI yield BSOD. The NTOSKrnl and HAL are both 2018-09, so maybe that's the issue with HyperSLI.
 
I could roll back the BIOS. Also, I disabled Lucid but I know Lucid was running back when things worked.

Did you even end up testing driver 387.92 like I suggested?

@bcavnaugh I couldn't get Lucid to install, anyway. That led to a rabbit hole. I tried to use the iGPU. Couldn't get HDMI to provide signal. When I'm running thru the GTX I see the iGPU is available for PhysX. I completely removed the GPU, reset CMOS, bang bang, but no Intel i7 iGPU HDMI signal.
 
@Sajin I thought I had tried 387.92 but I don't see its installer. I'm d/l now, will update you

@MhzManiac I don't understand. This is one card, one dual-gpu card.
 
@Sajin no love with the driver you suggest.
 
So the old drivers (285.62, 296.10) also BSOD with HyperSLI (0.96, 1.0). I think the kernel/hal have changed too much for HyperSLI, or maybe I could still try with old BIOS. Plus they won't support my 2560x1080 monitor.
 
I want to track down the issue of integrated GPU before I try to contact DSLIA peeps. I naively thought, just plug into HDMI on MOBO. Then I pulled GFX. Then I cleared CMOS. I THINK I remember a setting in the BIOS that is no longer there, to disable iGPU. Where did it go? Intel diagnostic tool skips gfx check when connected to gfx card. Hmm.
 
I have an i3. I could swap CPUs to see if I get mobo video signal. So much work and risk of error. AND this mITX box is so inconvenient!
 
Aside from one wasted GTX460 it is a fine machine. Maybe I will sleep on it for a week before I risk bending cpu pins on the mobo.

@bcavnaugh "Maybe it is just time to upgrade your computer now." But I HAD it working! :D
 
I'll track down SLI Patch 1.5. HyperSLI is the continuation, the replacement and extension of SLIPatch1.5. Same dev, anatolymik.
 
It's funny you link PCPer because I'm in that forum reporting I got the SLI to work with HyperSLI on this SAME BOX. I do not mention the HyperSLI version or the drivers and obviously Windows (though still 7 SP1)  has moved on regardless. Sure I have the install DVD and there are ISOs of intermediate versions.. But again, ROI.
 
I have a thought about the HDMI mobo port. Maybe "way back then" the Intel drivers wouldn't stretch to 2560x1080 like the "ancient" nVidia 275.33 already did. I have another display to try.
 
Way too many moving parts after 5 years. And THINK MORE THAN TWICE about using super small mItx cases!

With some of the Windows 7 Patches lately it is hard to keep even our Older OS Computers running well anymore.

Let us know if it work!