SLI with different cards

[One-Knee-Toe]

To me this leaves two options:

1. The 'new' way of patching (for the 4xx driver generation) has had only some few installs so far; it's not been tested thoroughly. So while it does bypass some important checks, it might not cover all situations, for example missing bypassing the check for a SLI bridge. If you have one, you might try using a SLI bridge. But there's no guarantee that this is actually the culprit here.
2. Falling back to the proven old method, using DSLIA 1.7.1 and 388.71

I too have not been able to get this to work using the 417.35 (my last post was #2930), and I have followed @Pretentious suggestions. I ended up putting this effort aside as I was on vacation and I'll be on travel again in a few days, so I wont be able to get back to this for a few weeks - [sigh].

I don't know if I can use the 388.x drivers as I have the new GeForce RTX 2080 XCs.

Stupid Question: What was done to figure out how to hack the driver? Maybe I can spend some time looking into recent changes in the driver that may be causing problems.

Cheers!

 

[marcipan666]

thx
i rty 388.71 tomorow .

now my brain is burning .. thanks for everything

Today I have tried the 388.71 drivers. the result is the same.
incomprehensible....

there was a difference. the monitor quickly turned on black screen and back ,and did not stop it. but I could start the control panel and did not see the SLI option.
it was like a contact error and didn't stop it. only sometimes did the picture flash


update:
I selled today my two GTX1080 , this is a FIX
now i have to buy something ..... and to forget about "SLI" on CELSIUS workstation (M470-2)

 

[P!nkpanther]

I don't know if I can use the 388.x drivers as I have the new GeForce RTX 2080 XCs.

Stupid Question: What was done to figure out how to hack the driver? Maybe I can spend some time looking into recent changes in the driver that may be causing problems.

You cannot take advantage of the RTX cards' features using the old driver generation. Installing the proven old pair of DSLIA 1.7.1 & driver 388.71 however might give you a hint, whether your hardware setup is capable of running SLI at all after patching.
Like user @marcipan666 found out...

Concerning your other question: Basically what @Pretentious did by debugging the relevant system calls made by the driver, to verify the requirements made by nVidia to enable SLI, and bypass them.

Today I have tried the 388.71 drivers. the result is the same.
incomprehensible....

update:
I selled today my two GTX1080 , this is a FIX
now i have to buy something ..... and to forget about "SLI" on CELSIUS workstation (M470-2)

Oh...
That's strange, since most of the problems getting DSLIA to run came from the install procedure, not from the inability of the actual hardware combination.
Anyways, I hope you find another solution using a shiny new single card!

 

[marcipan666]

i have 30 years of linux experience .. i am hacking and hexedit skilled . I don't think I made a mistake during the installation. I understood exactly what I was doing (not just copying the video).

I think the windows could have been wrong. this is an old much used installation .......

 

[Pretentious]

I too have not been able to get this to work using the 417.35 (my last post was #2930), and I have followed @Pretentious suggestions. I ended up putting this effort aside as I was on vacation and I'll be on travel again in a few days, so I wont be able to get back to this for a few weeks - [sigh].

I don't know if I can use the 388.x drivers as I have the new GeForce RTX 2080 XCs.

Stupid Question: What was done to figure out how to hack the driver? Maybe I can spend some time looking into recent changes in the driver that may be causing problems.

Cheers!

In your case we don't know if the 20 series might use a different routine of the driver to handle the SLI (I would expect it to work like all other series, but it is something to keep in mind). So long as people are using windows 10 with 417.35, my instructions should work.

417.71 was released. I'm currently installing it and I am planning to release the offsets later Today.

 

[One-Knee-Toe]

In any case, 417.71 was released. I'm currently installing it and I am planning to release the offsets later Today.

I will be back from travel tomorrow and will give 417.71 a try!

Thanks again, @Pretentious.

 

[Pretentious]

417.71
===========
00000000002BBFCF: 75 C7
00000000002BBFD0: 05 43
00000000002BBFD1: 0F 24
00000000002BBFD2: BA 00
00000000002BBFD3: 6B 00
00000000002BBFD4: 24 00
00000000002BBFD5: 0E 00

 

[One-Knee-Toe]

I have it working now (see attached)!

@Pretentious: Thank you for your help and continued contributions (hacking the newer drivers). It would not have been possible without your support.

I followed the same steps as before:
1) Boot into Safe Mode.
2) DDU the old driver
3) Boot normal.
4) Installed 417.71 (custom, checking "clean install")
5) Ran the 3 bcdedit commands.
6) Modified *.sys
... [Deviation]...
7) Replaced old *.sys with hacked *.sys (C:\Windows\System32\DriverStore\FileRepository\nv_dispi*\)
-- Unsigned, unmodified checksum.
8) Booted with "disable Driver Cert" (same reboot sequence as "safe mode" but instead option 7)

Results:
I was able to open the NVIDIA control panel and see the SLI option.
I was able to enable the SLI option and upon rebooting (again with "Disable Driver Cert"), the SLI option was still enabled.

Problem:
With that working, I "signed" the driver and rebooted into Normal Windows. However, I had the issue with the NVIDIA console not starting.
* Via the device manager, I noticed that the driver was not showing up as signed.
* I looked at the command script and noticed that the signtool was using a timestamp.dll from the verisign.com.
* The problem here, Test System is not connected to the network.

Additional Steps to "sign the driver":
Using a PC connected to the network,
1) Created the cert and install the cert onto the PC.
2) Checksum fixed & signed the modified driver.
3) Go back to the "Test System"
4) Boot test system to "Safe Mode"
5) Add the Cert to the Test System
6) Copy the Cert and Driver to their correct folders:
-- Cert: C:\Windows\*.cert
-- Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispi*\ *.sys
7) Rebooted in normal mode

Success!
See attached for screen shots.

 

[Heavenwood]

417.71
===========
00000000002BBFCF: 75 C7
00000000002BBFD0: 05 43
00000000002BBFD1: 0F 24
00000000002BBFD2: BA 00
00000000002BBFD3: 6B 00
00000000002BBFD4: 24 00
00000000002BBFD5: 0E 00

Thank you for your help, I am very glad that everything worked out.

 

[P!nkpanther]

Vodka for the win...

 

[Arkanggel10]

Thanks Pretentious, you are the man

 

[Pretentious]

I have it working now (see attached)!

@Pretentious: Thank you for your help and continued contributions (hacking the newer drivers). It would not have been possible without your support.

I followed the same steps as before:
1) Boot into Safe Mode.
2) DDU the old driver
3) Boot normal.
4) Installed 417.71 (custom, checking "clean install")
5) Ran the 3 bcdedit commands.
6) Modified *.sys
... [Deviation]...
7) Replaced old *.sys with hacked *.sys (C:\Windows\System32\DriverStore\FileRepository\nv_dispi*\)
-- Unsigned, unmodified checksum.
8) Booted with "disable Driver Cert" (same reboot sequence as "safe mode" but instead option 7)

Results:
I was able to open the NVIDIA control panel and see the SLI option.
I was able to enable the SLI option and upon rebooting (again with "Disable Driver Cert"), the SLI option was still enabled.

Problem:
With that working, I "signed" the driver and rebooted into Normal Windows. However, I had the issue with the NVIDIA console not starting.
* Via the device manager, I noticed that the driver was not showing up as signed.
* I looked at the command script and noticed that the signtool was using a timestamp.dll from the verisign.com.
* The problem here, Test System is not connected to the network.

Additional Steps to "sign the driver":
Using a PC connected to the network,
1) Created the cert and install the cert onto the PC.
2) Checksum fixed & signed the modified driver.
3) Go back to the "Test System"
4) Boot test system to "Safe Mode"
5) Add the Cert to the Test System
6) Copy the Cert and Driver to their correct folders:
-- Cert: C:\Windows\*.cert
-- Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispi*\ *.sys
7) Rebooted in normal mode

Success!
See attached for screen shots.

Nice Setup! I'm glad you got it to work and thank you for sharing your steps with the rest of the community

Thanks Pretentious, you are the man

No problem

 

[benhonda03]

Hello everyone I am new here and I readed lots of awesome informations in this threads, and wanted to say thanks for what your are doing.

///Intro---
My 780ti and 780 was working perfeclty on the z97 gaming 7 MSI motherboard with DifferentSLIAuto 1.7.1(win7 64bit) and driver 388.71. I had great boost performance from it. Then, I saw the update for the new 417.71 so I decided to uptaded it like the same way I did before (except modify nvlddmkm.sys with hex editor using the offsets) :
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(Disable antivirus before loading DifferentSLIAuto)
1. Put cards together you want to SLI™ (Plug-IN PCI_E with bridge).
2. Restart into Safe Mode.
3. If you have installed old instances of DifferentSLIAuto, remove its certificates using certmgr.msc and its registry keys using Regedit (searching for keys containing 'differentsliauto' and deleting them).
4. DDU(DisplayDriverUnistaller) your old driver.
5. Reboot normally and install original lastest NVIDIA® drivers(custom, checking "clean install"). No need to reboot yet.
6. Set UAC to the lowest setting in Control Panel\All Control Panel Items\Security and Maintenance.
7- Run cmd.exe as admin and enter:
bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set NOINTEGRITYCHECKS ON
bcdedit.exe /set TESTSIGNING ON
No need to reboot yet.
8. Copy original "nvlddmkm.sys" from ("%SystemRoot%\System32\drivers\%_nvlddmkm%.sys") and put it in the same folder as the patcher .
9. Run as admin "DifferentSLIAuto.exe" and press patch, if everything went well it will say that patching was successful, if not contact techPowerUp! and do not continue.
10. Restart into Safe Mode.
11. Run the Install.cmd as admin. You should get a certificate installed and 1 file successfully copied.
12. Reboot normally
(Turn on Antivirus)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
///Problem:
Except now, I am getting stuck on the step #9 who's give me the following error : Could not find drivers #2 and #4
I have opened my nvlddmkm.sys on HexEd.it just to see how it work because I dont know much about this stuff and can't figure it out :

417.71
===========
00000000002BBFCF: 75 C7
00000000002BBFD0: 05 43
00000000002BBFD1: 0F 24
00000000002BBFD2: BA 00
00000000002BBFD3: 6B 00
00000000002BBFD4: 24 00
00000000002BBFD5: 0E 00

///Any Fix ?
I would like to know to how to modify nvlddmkm.sys with hex editor using the offsets correclty so I can understand what im doing. All others parts are easily okay for me if I follow the right step and you guys are really nice and good to gives advices. I think I have read some posts twice and I tried a lot of thing (even reintall fresh window ) but still no chance there.
It was working on 388.71 so why not on 417.71...
When I try to send my Attach files of the nvlddmkm.sys it tell's me that the uploaded file is too large for server to process.

I guess it time to take a break hehe

Thanks for your time and the help from everyone!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: Just finised the installation, had 2 problem that I didnt have the last time but I fixed it and it now working properly so if something happen similar happen to you I will try to be short:
After step 11 above, I got error message. So I had to fix the correct destination of my folders that I verified on device manager > main graphic card > right click property >2nd button driver > details > and find your nvlddmkm.sys path. By default the Install script path was something like this and I replaced it with the following :

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_neutral_026dc60e2400f220 --------> C:\Windows\System32\drivers\nvlddmkm.sys

I found out I got 2 nvlddmkm.sys but the one with this path C:\Windows\System32\drivers\nvlddmkm.sys is the one is used by the device manager. The other one with this path C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_neutral_026dc60e2400f220 is not working for me on window 7.

After that my Intall script worked correclty so I rebooted to see if my SLI was in Nvidia Control Panel but when I right clicked on the desktop, the panel was not there ! Device Manager is now saying cannot run no signed certif so I returned read more and I find a post on the top of the page about it by @chris189 ----------> https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/page-59

I was running 130 fps in Kombustor, im now at 205 fps @144hz NO Overclocks at all. For me this is amazing just the fact that they are not "" suposed "" to be together hahah Great job to everyone helping the cause.

Woop woop

Droppin my dxdiag if you wanna know my config.

https://www.virustotal.com/fr/file/...4cb86133a542936e88d7a05a/analysis/1548394804/

 

[SupDRN]

Hello everybody!
I read topic, but i'm too stupid to make it work on my windows 10. There are mistakes everywhere!


etc
Please could somebody share link to old modded driver, links of topic starter doesn't work. May be it works. I have 2 760 and I want SLI so much, but I took just headache and disappointence in myself. TU

 

[P!nkpanther]

I can't make out the errors written in Russian, but did you issue the commands as admin?
Patching did not work because of a version mismatch between patch and driver.

This post outlines the exact steps you need to take in Windows 10 (start reading below the video):
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3968942

 

[SupDRN]

I can't make out the errors written in Russian, but did you issue the commands as admin?
Patching did not work because of a version mismatch between patch and driver.

This post outlines the exact steps you need to take in Windows 10 (start reading below the video):
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3968942

TU, I read your post twice for better understanding, dowloaded latest DDU, ran it in safe mode, downloaded 388.71, started it and

This means that driver doesn't suppose to the windows version. I tried random 5 versions of driver and couldn't install them. Any way I installed GeForce Experiace? which succeded and and installed driver 417... TU for try, I'm gong go on living whith understanding that SLI just not for me

 

[P!nkpanther]

The install error of the 388.71 driver seems strange to me. Normally that part of the installation goes well for everybody. Did you make sure to choose the right OS version (Win 10 64-bit) ?

Anyways, since you got a running 417.71 and two identical cards, you might want to try the new patching procedure described in the earlier posts on this page and the page before.
Only if you know how to use a hex editor of course.

 

[SupDRN]

I'm the happiest man in the world! I got SLI!!

Thank U very much, P!nkpanther !!

I hexedited 417.35, at first. I had a problem as a One-Knee-Toe, I noticed that he didn't

Run cmd.exe as admin and enter:
bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set NOINTEGRITYCHECKS ON
bcdedit.exe /set TESTSIGNING ON

or didn't write about that. At first I had an error. I had to turn off safe mode in BIOS and then I succeded. No more intresting about my actions any more. And as a result:
WAS

NOW


Thank you, guys again!

 

[P!nkpanther]

Great!
Always a pleasure to help ppl who have 'grit' and know how to make use of all the information available in this forum.

BTW, I'd recommend to disable automatic driver updates in GeForce Experience, otherwise your new installation might get overwritten eventually.

 

[Edwired]

Cant believe this still going

 

[SupDRN]

Great!
Always a pleasure to help ppl who have 'grit' and know how to make use of all the information available in this forum.

BTW, I'd recommend to disable automatic driver updates in GeForce Experience, otherwise your new installation might get overwritten eventually.

I uninstalled GeForce Experience just as ended. I'm not going update drivers untill I could buy some better video card Trying Assasin creed in ultra grphic right now. Everything is going well, but temprature is about 75 C. But it is not a problem. Thanks again.

 

[One-Knee-Toe]

...I read topic, but i'm too stupid to make it work on my windows 10. There are mistakes everywhere!...

I'm the happiest man in the world! I got SLI!! ... Thank you, guys again!

Congratulations!! You're not "too stupid" at all and good job!

It is unfortunate that the GPU driver is made this way when there is no reason to prevent SLI as long as the system physically supports it.

 

[Edwired]

Question about the hexedit and offset that where im at a loss. Are you saying that modifiying the code in order to enable the sli each time the new drivers comes out?

 

[One-Knee-Toe]

Question about the hexedit and offset that where im at a loss. Are you saying that modifiying the code in order to enable the sli each time the new drivers comes out?

Yes and @Pretentious been kind to keep making the updates, all for free and on his spare time.

 

[Edwired]

It amazing how he able to do that. Which file is he currently modding or is that the nv file found in driverstore location