HyperSLI (Enabling SLI on non-sli motherboards)

[erykos]

just bought gtx 750 ti 4gb nice all games in my pc tested so far with my crap procesor like told new one cost just 230zl =max 60 euro xDDD and this graphic ard 4gb bought cause 2g is only 60zl-max 15 euro cheaper only than 4gb one and this gtx 750 ti do great work with crap cheap thing in my pc gta v 0 laggs on max,bf4 too the witcher 3 too worthy buy with crap procesor of if we have all codec drivers,programs in our pc xD and if someone tell its nothing so someone dont have drivers,codecs in pc simple xD and good thing its cheap not like 2gb 960 or 4gb xD this 750 ti 4gb only 620zl xD-150-155euro xD while gtx 960 200-250 or more xD and on friend pc work more crappy with better procesor than at my gtx 750 ti

 

[Kasakuru]

To jbailey8:
I found my error. It was very trivial. My computer somehow got his fate changed from 2015 to 2002 without me noticing it. I noticed when all my internet activities were blocked by not having a valid certificate or rather expired certificate. Changing back my date I now got the patched drivers signed by the Install.cmd. And everything seems to work now. SLI is enabled and I get more performance in games. Thanks for the help dude!

 

[jbailey8]

To Kasakuru:

Glad you got it going!

To erykos:

I had a little trouble reading your post, but I think your saying you like your 750 video board, Good! Have fun!

 

[GGrafx]

Howdy jbailey8,

I have used diffSLI on my dual GTX780ti setup successfully previously (Asus P9D-WS mobo, non-SLI, Win 8.1 Pro X64), but with the 355.98 drivers I'm getting this:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd \Applications\differentsli

C:\Applications\differentsli>Install.cmd
root "Trusted Root Certification Authorities"
================ Certificate 8 ================
Serial Number: e04c87ef47757e904a75357b9eb0a0ea
Issuer: CN=DifferentSLIAuto
NotBefore: 23.06.2015 22:50
NotAfter: 01.01.2040 01:59
Subject: CN=DifferentSLIAuto
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): 16 ed 1d 1c 7c d5 62 c1 c9 05 d5 f2 8c 89 cf 3f a0 b5 f8 2d
No key provider information
Cannot find the certificate and private key for decryption.
Encryption test passed
CertUtil: -store command completed successfully.
SignTool Error: File not found:

SUCCESS: The file (or folder): "C:\Windows\System32\drivers\nvlddmkm.sys" now o
ned by the administrators group.
processed file: C:\Windows\System32\drivers\nvlddmkm.sys
Successfully processed 1 files; Failed processing 0 files
The operation completed successfully.
1 file(s) copied.
Reboot now for changes to take effect

C:\Applications\differentsli>

So, I'm a successfull message, but I see errors relating to the driver signing.

And, it doesn't work anymore. After rebooting I see that something is wrong because the Nvidia Control Panel is no longer in the right-click-on-desktop menu, and when I start the control panel from the control panel menu, it crashes (Nvidia the control panel.)

Now, Windows is in Test Mode (and in fact, this was part of the install process in earlier differentSLI versions...) but I don't see this as being a requirement anywhere anymore. Perhaps I should nto be running in Test Mode anymore?

Any ideas?

Thnx for your help.

GG

 

[jbailey8]

To GGrafx:

I've never seen that error before, check the following:

1. Make sure your trying to install the right modified driver: http://www.gamefront.com/files/25235387/nvlddmkm-35598-win7-8-81-64-bit.rar
2. Download and unpack the current version of differentsliauto: https://github.com/EmberVulpix/DifferentSLIAuto/releases (1.3 zip).
3. Download and install the current driver version for windows 8.1 64 bit 355.98 from nvidias' site and run the installer.
4. Make sure your anti-virus is either disabled temporarily or you have an exception for the diffsli13 folder in place in your anti-virus program.
5. Make sure your system clock is accurate to the current date & time.
6. Unpack differentsliauto to a folder of your choice, (ex: diffsli13).
7. Unpack the modified driver into the same folder.
8. Open a administrator level command prompt and run the 'Install.cmd'.
9. Go to your nvidia control panel and activate sli mode and reboot your computer.

If you are still getting errors after this, let me know. Another poster had virtually the same problem as you, it turned out to be his anti-virus program was interfering with the install.cmd
and his system clock/calendar was way off, once these things were fixed, everything worked fine.

 

[GGrafx]

Hi jbailey8,

yes sir, I have installed and re-installed according to your instructions. Between re-installs I used DDU to wipe out the driver entirely.

Now, what I notice is that I rebooted after step 8, I did not turn on SLI and THEN reboot. I will try that when I am on the workstation again.

BTW: should I disable Windows test mode? Is this still required for self-signed certificates?

Thnx,

GG

 

[jbailey8]

You can't turn off test mode, if you do that the patched driver will stop working.

 

[GGrafx]

You can't turn off test mode, if you do that the patched driver will stop working.

Got it. Test mode stays on. =)

Okay, so, I did the driver patch by the numbers, but no love. SLI is not available in the control panel before or after reboot and after reboot the crontrol panel crashes. (Yes, the unpatched Nvidia driver works, as does the control panel).

I got the following error when I tested each command by hand, signtool.exe complained about the timestamp page:
"http://timestamp.verisign.com/scripts/timstamp.dll not available"

A search for this error suggests using a different time stamper (https://stackoverflow.com/questions/9714798/http-timestamp-verisign-com-scripts-timstamp-dll-not-available)
I tried the comodo stamper, this did get rid of the "not available error", it did not change the "File not available" error though.

Here is some food for thought:


I removed "@Echo off" from the install.cmd. Here is the full output:

C:\Applications\differentsli>Install.cmd

C:\Applications\differentsli>title DifferentSLI Sign and Install

C:\Applications\differentsli>setlocal EnableExtensions

C:\Applications\differentsli>cd /d "C:\Applications\differentsli\"

C:\Applications\differentsli>if not exist "tools\" goto wtfrudoin

C:\Applications\differentsli>net session 1>nul 2>&1

C:\Applications\differentsli>if 0 NEQ 0 goto notadmin

C:\Applications\differentsli>call "C:\Windows\System32\certutil.exe" -store root
DifferentSLIAuto
root "Trusted Root Certification Authorities"
================ Certificate 8 ================
Serial Number: e04c87ef47757e904a75357b9eb0a0ea
Issuer: CN=DifferentSLIAuto
NotBefore: 23.06.2015 22:50
NotAfter: 01.01.2040 01:59
Subject: CN=DifferentSLIAuto
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): 16 ed 1d 1c 7c d5 62 c1 c9 05 d5 f2 8c 89 cf 3f a0 b5 f8 2d
No key provider information
Cannot find the certificate and private key for decryption.
Encryption test passed
CertUtil: -store command completed successfully.

C:\Applications\differentsli>if 0 EQU 0 goto certexists

C:\Applications\differentsli>call "tools\ChecksumFix.exe" "nvlddmkm.sys"

C:\Applications\differentsli>call "tools\signtool.exe" sign /v /s DifferentSLIAu
to /n DifferentSLIAuto /t http://timestamp.comodoca.com/authenticode " nvlddmkm.
sys"
SignTool Error: File not found:

C:\Applications\differentsli>call "C:\Windows\System32\takeown.exe" /f "C:\Windo
ws\System32\drivers\nvlddmkm.sys" /a

SUCCESS: The file (or folder): "C:\Windows\System32\drivers\nvlddmkm.sys" now ow
ned by the administrators group.

C:\Applications\differentsli>call "C:\Windows\System32\icacls.exe" "C:\Windows\S
ystem32\drivers\nvlddmkm.sys" /grant "xtian":f
processed file: C:\Windows\System32\drivers\nvlddmkm.sys
Successfully processed 1 files; Failed processing 0 files

C:\Applications\differentsli>call "C:\Windows\System32\bcdedit.exe" /set TESTSIG
NING ON
The operation completed successfully.

C:\Applications\differentsli>if exist "C:\Windows\Sysnative\" goto x32mode

C:\Applications\differentsli>copy "nvlddmkm.sys" "C:\Windows\System32\drivers\nv
lddmkm.sys" /y
1 file(s) copied.

C:\Applications\differentsli>goto filecopied

C:\Applications\differentsli>color 0a

C:\Applications\differentsli>echo Reboot now for changes to take effect
Reboot now for changes to take effect

C:\Applications\differentsli>goto end

C:\Applications\differentsli>pause 1>nul

C:\Applications\differentsli>

 

[jbailey8]

It sounds like the patched nvlddmkm.sys file isn't being installed for some reason, assuming your running differentsliauto 1.3 you have the current install.cmd, be sure your unpacking the patched
driver into the same folder where you installed differentsliauto, and just to cover bases, don't run the exe that's in that folder, the nvlddmkm.sys is already patched.
However just to try everything, you can extract the nvlddmkm.sy_ file from the original installer with winrar and put that file in the differentsli folder run a administrator command prompt
and type in 'expand nvlddmkm.sy_ nvlddmkm.sys' then try running the patcher program, maybe doing that will help in your case.

Another thing you could try is to manually copy over the nvlddmkm.sys (patched) to
C:\Windows\System32\drivers and run the install.cmd again.

 

[GGrafx]

It sounds like the patched nvlddmkm.sys file isn't being installed for some reason, assuming your running differentsliauto 1.3 you have the current install.cmd, be sure your unpacking the patched
driver into the same folder where you installed differentsliauto, and just to cover bases, don't run the exe that's in that folder, the nvlddmkm.sys is already patched.
However just to try everything, you can extract the nvlddmkm.sy_ file from the original installer with winrar and put that file in the differentsli folder run a administrator command prompt
and type in 'expand nvlddmkm.sy_ nvlddmkm.sys' then try running the patcher program, maybe doing that will help in your case.

Another thing you could try is to manually copy over the nvlddmkm.sys (patched) to
C:\Windows\System32\drivers and run the install.cmd again.

Hi, will try that out. I see that there is a 1.3.1 and a 1.3 Version - and I stuck with the 1.3, did not use 1.3.1.
Thanks!

GG

 

[GGrafx]

Okay, the patching is working fine, both with manually expanded nvlddmkm.sys and the one copied from the win32 drivers folder, the differentsliauto.exe reports success. It's the driver signing that is failing (as seen in the messages from certutil and signtool). Device Manager reports the following with the patched drivers:
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)".
Which is why the Nvidia control panel crashes with the patched driver.
This is normal Win 8.1 Pro X64. And this used to work with... what was it... I think I had 352.86 or 353.06 running.
I have "Test mode" on the background of the desktop, so I assume it really is in test mode. I could take it out of test mode and put it back in test mode as another thing to check.
I will see if I can get more documentation on certutil and signtool. I think you can get them in some Windows SDK...

 

[jbailey8]

I have no idea really as to why your having this much trouble, I've installed (and currently running) the same exact driver your trying to run and it's working perfectly for me (windows 7 64 bit), most people don't have any
of these problems counting you there's been maybe 3 or 4 people out of the total number of people running this driver (around 150-200 by my count). I'll keep thinking about the problem, but at the moment I don't know what else to suggest. Perhaps turn off uac?

 

[GGrafx]

Hi,

I got it working!

I downloaded the Win 8.1 SDK, I then replaced the signtool.exe and makecert.exe with the 64bit versions from the SDK (from Program Files (x86)\Windows Kits\8.1\bin\x64). These files are newer (datestamp is 24.10.2014 vs. 19.03.2010 as supplied in the differentsliauto1.3 "tools" directory.)

Cool, 355.98 with SLI on this Xeon board (with ECC RAM, which is what all this pain and trouble is about: I didn't find any Xeon + ECC capable SLI mobos, they all seem to be CrossFire only.)

Perhaps that will help someone else.

Thanks jbailey8 for all your patience, as usual. =)

GG

PS. Well, I should add that this is running the "self-patched" (with the differentsliauto.exe) nvlddmkm.sys. Now, as noted before, the self-patched driver alone did not fix the problem, but since I added the newer certificate tools after that, I can not tell you whether it is the combination of both that makes it work. My guess is that the newer certificate tools are the important part.

 

[jbailey8]

Glad things are working fine now! Maybe make the updated signing tools available as a seperate download link that would be posted whenever I post new downloads along with a readme.

 

[GGrafx]

Gladly!

The Windows 8.1 SDK Page:
https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx

The direct download link (for the installer, which then downloads the actual components):
https://www.microsoft.com/click/services/Redirect2.ashx?CR_EAC=300135395

After SDK install (I kept all install options selected) I ended up using the signtool.exe and makecert.exe from "Program Files (x86)\Windows Kits\8.1\bin\x64".

Next time driver upgrade I will test some more and perhaps be able to provide more precise information (I'll do a scratch install, let it fail, and then replace only one and then the other certificate tool.)

GG

 

[jbailey8]

I just looked at the installer, I'd rather not download 8.1 code on my windows 7 computer, (just to be safe), if you don't mind, just put signtool.exe & makecert.exe in a zip (or rar), and post the zip to gamefront and put the download link
here, I'll download it (anyone else here can get them too then without the sdk download) and I'll try to include the download link in any new driver updates.

 

[GGrafx]

Howdy jbailey8,

here you (and anyone else that needs 'em) are:

http://www.gamefront.com/files/25251528/differentsliauto_win81-x64_cert_tools.zip

signtool.exe (CRC64 DE2929C8BD8C8ADC)
makecert.exe (CRC64 3E16A0AE3604CB4E)
certmgr.exe (CRC64 E366020413F577A9)

GG

 

[jbailey8]

Appreciate the download link! I'll include these files in any further driver links I post.

 

[Dudeabides]

Hello- new here, just wondering if I could get some help trying to get this to work for me!

My system:
Windows 7 pro sp1
P5Q Pro motherboard (Crossfire compatible, not SLI)
Q9650 CPU
MSI 760
Gigabyte 760
8gb g.skill ddr2 800 ram

I recently had the Gigabyte card given to me, and I thought great I can just throw it in next to my MSI and it will all work perfectly the first try right? Wrong. I'm ashamed to admit I didn't even realize that SLI and Crossfire are not nativly compatible.

Anyway, I threw them both in, put the bridge on, and got to gaming. Everything seemed more or less okay, though I was receiving error messages I had never received before, along the lines of 'the nvidia driver has stopped responding and has recovered.' During this time, I was also overclocking my system and assumed these errors were caused by my RAM no being able to handle the OC (I was failing Prime 95 blend test with rounding errors). Anyway, I've reset all my specs to default and I'm trying to now go about figuring out what is causing my problems. Could it be issues stemming from my gpu situation (ie two Nvidia gpus bridged in a crossfire board)?

I've tried all the advice in this thread, and I now have the option to put my cards in SLI mode via the NVIDIA control panel (where there was no option to before), however when I enable SLI my system hardfreezes within about 5 minutes or so of light internet browsing. Disabling SLI seems to alleviate this. I would really love to get these two cards working in SLI if possible- any suggestions? No minidump files were generated or I would post them : /

Edit: forgot to add my PSU, its an Antec 850 'high current gamer'

 

[jbailey8]

To Dudeabides:

Make sure you've installed the official 355.98 driver from nvidias' site and your installing the patched driver of the same version according to instructions (and operating system version). If you've done this, then I'd say 1 of your boards is possibly bad since the problem seems to go away when sli mode is disabled, I'm reasonably sure it's not the driver itself since I'm running the same driver on my system with no issues. Your power supply is barely good enough (in my opinion), I'm
running 1000w in my system, according to the specs for your video boards (from nvidias' site) 500w is the minimum power requirement for the whole system with 1 board, your trying to run 2 so that equals 1000w, however this would tend to be the case when actually playing a game, your having this problem while simply browsing internet, so your system would be drawing minimal power. Another thing you can check is any error logs listed in the event viewer. Make sure the cooling fans
are actually running on both boards, this whole thing might simply be some overheating and 1 board is shutting down temporarily, which would confuse the driver and could lead to bluescreens, etc.

Also, go to your device manager and make sure both video boards are listed as active
devices and you don't have any '!' or 'X' on the device entries which would indicate a
driver problem.

 

[Dudeabides]

Hey, thanks for the reply! Just getting home now... was at a wedding (I just turned 30 and thats all I do now... go to weddings).

So, after a fresh install of MS 7 pro, I downloaded the latest nvidia drivers (355.98) and then downloaded the latest version of DifferentALIAuto and followed the steps in the readme to the letter. I was happy see that I was indeed able to select sli mode in the NVIDIA control panel, but like I said it causes the system to freeze in short order : /

I did actually consider the PSU as a possible issue, but I checked the system power draw with http://outervision.com/power-supply-calculator, and it estimated peak load to be ~720, pretty well under my max.

As far as heat goes, I wasn't actually checking my sensors but I wouldn't expect it- its been pretty cold here in Vermont recently, and I have a Thor v2 case which has like 743957 fans in it and pretty decent cable management.

The device manager shows two NVIDIA Geforce 760 adapters with no errors.

Also, I was wondering- if for some reason it just doesn't want to work on my system, can this extra card be of any use? For instance, if I set up one card to power each display, then run two clients of EVE, let's say, will each card be responsible for each client? Or perhaps I make one card a dedicated physx card?

 

[player1]

Hey guys !

I've been trying to get SLI working with my 7950 GX2 and 7900 GX2 on my Gigabyte X38-DS5 for some days now. (without SLI bridge)

I was able to get the SLI option into the latest forceware driver that support my card (309.08) but the screen turned black and then I got a bluescreen telling me something about timestamp issue. I've used the SLI Auto 1.3.1.

However during my endless researches I've read that there was a lot more people having success with the 0.7 sli patch and the forceware 77.77 drivers.

Unfortunally I couldnd find any working link to download them. So my question is if anybody could provide me a working link to download them or any other way I could get them working in SLI.

Btw I'm running win 7 x64 and I'm not sure if the 77.77 drivers even support windows 7. But maybe compability mode could solve that issue.

Thank you !

 

[jbailey8]

To Dudeabides:

You can check settings in your bios that are related to crossfire and make sure you don't see any bad settings, but it's possible your motherboard simply won't handle sli mode properly, despite the fact you can activate sli mode with
the modified driver installed, the only other thing I can think of is something is overheating and locking up the system, but I'm not sure about this, you can still assign 1 board to handle video, and the other board to handle phyx
(non-sli). I'm not familiar with EVE so I can't say there.

---------------------------------

To player1:

I might have misunderstood something, but why are you trying to run drivers that are *WAY* out of date?

It's possible that the driver you installed wasn't patched/not patched properly (not likely though), also, you *need* a sli bridge installed or sli mode will never work properly, here's the download link to
309.08 windows 7 64-bit patched driver:

http://www.gamefront.com/files/25258552/nvlddmkm-30908-windows7-64-bit.rar

Unpack this file into the same directory as differentsliauto 1.3 and run the Install.cmd from a administrator command prompt, make sure there are no errors listed in the text output of the install.cmd,
if you see any you might need newer signing tools which I'll post a download link for if you need them. The timestamp error your getting suggests this. These tools are primarily for windows 8 & 8.1 but would probably work ok on windows 7.

 

[GoldenX]

I remember making this work with 2x 7600GT and an AMD 770 chipset, one in the 16x slot and the other over a 1x with an open end.
Performance was erratic, 3DMark had a 15% bump, but games run slower.

 

[jbailey8]

To GoldenX:

Your pci slot setup is a little unusual, your mixing a 1x slot with a 16x slot, I'm not suprised your computer's performance was a little off, I would recommend 2 x16 slots or 2 x8 slots. (if available), but if this is all you
had available, then this is as good as your computer can do. I'm glad the modified driver was still able to help a little though.