SLI with different cards

[EnterpriseNL]

Okay, so the steps you explained above should work for 388.71?

 

[One-Knee-Toe]

DifferentAutoSLI 1.7.1 only works with driver 380, not 417.35. However, I am intrigued to see if you can get it working with NVLINK, I plan on getting some 20 series cards for machine learning tasks.
In order to use version 417.35 you need to patch the .dll manually using an Hex editor, I have some instructions on how to go about this a couple of pages back. You can't run DifferentSLI, you should only reuse/adapt the install.bat file to facilitate the installing and signing of the dll after the manual patch.

*Thank You* Pretentious for that clarification!!

I have ran into a new problem - the NVIDIA Control Panel doesn't start now...

I "started over" in a sense - Steps:

0) Used DDU to remove all nvidia stuff​

1) Install 417.35 and then restart​

2) I modified (HexEd.it) the nvlddmkm.sys file per your instructions:​

---- 417.35 ----​

00000000002BB52F: 75 C7​

00000000002BB530: 05 43​

00000000002BB531: 0F 24​

00000000002BB532: BA 00​

00000000002BB533: 6B 00​

00000000002BB534: 24 00​

00000000002BB535: 0E 00​

​

3) I restarted into SafeMode.​

4) Copied the *.sys to the same folder as Install.cmd.​

5) Corrected the paths in Install.cmd.​

6) Ran Install.cmd.​

-- I noticed that the file-size became smaller - from 19,946 to 19,925.​

7) I restarted in normal mode.​

8) Via Win10 Device Manager, I confirmed that the GPU was pointing to the correct *.sys, no warnings and that the file was signed.​

9) I attempted to open the NVIDIA Control Panel but could not.​

-- Double clicking, run as admin, etc. does nothing - the control panel does not pop-up.​

Alternative Attempt:

0) I went back into Safe Mode and deleted the "certified/signed" version of the *.sys.​

1) I took the modified *.sys (un-certified/signed, but hex-edited) and copied it back into the nv_dispi.inf... folder.​

-- My thinking is that the file was changed too much by the cert/sign, given the file size difference.​

2) I restarted with "disable driver signature enforcement ".​

-- Also did the bcdedit commands (testsigning, nointegritychecks, disable_integrity_checks).​

3) Via Win10 Device Manager, I confirmed that the GPU was pointing to the correct *.sys and no warnings.​

4) I attempted to open the NVIDIA Control Panel but could not; same as before.​

​

//

Has anyone else experienced this? Any luck getting around this problem?

Thank you, again, all.

 

[Pretentious]

Okay, so the steps you explained above should work for 388.71?

For 388.71 you can't manually patch since I did not post the offsets for that version either, but feel free to follow the steps. The only difference is that instead of manually patch, you would run DifferentAuto SLI.

*Thank You* Pretentious for that clarification!!

I have ran into a new problem - the NVIDIA Control Panel doesn't start now...

I "started over" in a sense - Steps:

0) Used DDU to remove all nvidia stuff​

1) Install 417.35 and then restart​

2) I modified (HexEd.it) the nvlddmkm.sys file per your instructions:​

---- 417.35 ----​

00000000002BB52F: 75 C7​

00000000002BB530: 05 43​

00000000002BB531: 0F 24​

00000000002BB532: BA 00​

00000000002BB533: 6B 00​

00000000002BB534: 24 00​

00000000002BB535: 0E 00​

​

3) I restarted into SafeMode.​

4) Copied the *.sys to the same folder as Install.cmd.​

5) Corrected the paths in Install.cmd.​

6) Ran Install.cmd.​

-- I noticed that the file-size became smaller - from 19,946 to 19,925.​

7) I restarted in normal mode.​

8) Via Win10 Device Manager, I confirmed that the GPU was pointing to the correct *.sys, no warnings and that the file was signed.​

9) I attempted to open the NVIDIA Control Panel but could not.​

-- Double clicking, run as admin, etc. does nothing - the control panel does not pop-up.​

Alternative Attempt:

0) I went back into Safe Mode and deleted the "certified/signed" version of the *.sys.​

1) I took the modified *.sys (un-certified/signed, but hex-edited) and copied it back into the nv_dispi.inf... folder.​

-- My thinking is that the file was changed too much by the cert/sign, given the file size difference.​

2) I restarted with "disable driver signature enforcement ".​

-- Also did the bcdedit commands (testsigning, nointegritychecks, disable_integrity_checks).​

3) Via Win10 Device Manager, I confirmed that the GPU was pointing to the correct *.sys and no warnings.​

4) I attempted to open the NVIDIA Control Panel but could not; same as before.​

​

//

Has anyone else experienced this? Any luck getting around this problem?

Thank you, again, all.

Boot into safe mode and replace the .sys file by the original 417.35 then reboot into normal mode and check if the NVIDIA Control Panel works (It has to). If it doesn't work then something else went wrong. Did you restart after DDU or ddi you install the driver right away?

EDIT: File size difference is expected after you re-sign the file. A valid hypothesis would be if you either made a mistake while hex editing or if you're editing a version other than 417.35. In any case check if the original .sys file works (if you didn't save the original then I would suggest to DDU again and follow the steps but this time backup the original .sys file just in case; it helps with debugging).

 

[EnterpriseNL]

Will try tomorrow one more time with 388.71 or trying the certificates thing, otherwise I will wait for the offsets for 391.35

Well, removed any extra certificates didn't work, gonna remove the whole driver now, and do it again with your Install CMD and differentsliauto of course

Once again copying works perfect, but the certificate thing is not, I'm gonna try one last thing

It finally works thanks to some credit in this post
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3323103

Timestamp(verisign) site doesn't work so with some changes it finally works, and indeed the last step for Nvaki is also needed


EDIT2, Worked for a short time, during a benchmark one of the cards failed after the restart only 1 card was seen, gonna work on that later


Would still love to have the offset for the 391.35 driver

 

[One-Knee-Toe]

Thank you, again, Pretentious!

Boot into safe mode and replace the .sys file by the original 417.35 then reboot into normal mode and check if the NVIDIA Control Panel works (It has to)...Did you restart after DDU or ddi you install the driver right away?

Yes, that was one of the first things I tried, go back to the original, and yes, thankfully, the NVIDIA Control Panel opens up (No SLI, of course). I did re-start into normal mode after the DDU completed.

...A valid hypothesis would be if you either made a mistake while hex editing or if you're editing a version other than 417.35...

I don't think I fat fingered the hex-edit. I attached a Beyond Compare hex-compare of my changes.

 

[Pretentious]

Will try tomorrow one more time with 388.71 or trying the certificates thing, otherwise I will wait for the offsets for 391.35

Well, removed any extra certificates didn't work, gonna remove the whole driver now, and do it again with your Install CMD and differentsliauto of course

View attachment 113070

Once again copying works perfect, but the certificate thing is not, I'm gonna try one last thing

It finally works thanks to some credit in this post
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3323103

Timestamp(verisign) site doesn't work so with some changes it finally works, and indeed the last step for Nvaki is also needed


EDIT2, Worked for a short time, during a benchmark one of the cards failed after the restart only 1 card was seen, gonna work on that later


Would still love to have the offset for the 391.35 driver

Awesome! I personally don't use verisign as I patched my windows 10 to acknowledge the nvidia sys file as certified regardless of it being signed or not. For the 391.35 offsets check back tomorrow, I should post them at some point (I said I wouldn't do older drivers but since your GPU support was dropped in more recent versions I will make an exception and help you out).

Thank you, again, Pretentious!



Yes, that was one of the first things I tried, go back to the original, and yes, thankfully, the NVIDIA Control Panel opens up (No SLI, of course). I did re-start into normal mode after the DDU completed.



I don't think I fat fingered the hex-edit. I attached a Beyond Compare hex-compare of my changes.

I see. Again, just to make sure it's not something trivial, if you replace the .sys file (switch between original and patched) and restart, the NVIDIA control panel will show up only if it's the original correct? Are you booting with testmode? (Do you have the watermark on the right bottom corner when you're using the patched driver?)

 

[EnterpriseNL]

@Pretentious Thanks, appreciate it, yeah support for the 500 series was dropped after 391, latest is as I said 391.35, the Verisign thing is still in the install.CMD so think some changes are needed to get it fully working

 

[Pretentious]

@Pretentious Thanks, appreciate it, yeah support for the 500 series was dropped after 391, latest is as I said 391.35, the Verisign thing is still in the install.CMD so think some changes are needed to get it fully working

391.35
===================
00000000002AF0B3: 75 C7
00000000002AF0B4: 05 43
00000000002AF0B5: 0F 24
00000000002AF0B6: BA 00
00000000002AF0B7: 6B 00
00000000002AF0B8: 24 00
00000000002AF0B9: 0E 00

Have fun

 

[MannyWhite]

I'm only doing identical. I can try to give out what I assume to be the right patch addresses for the other functions but since I don't have the means to test it, therefore there is no guarantee that it will work.

I would like to at least try those offsets for 417.35. I've got two GTX 970s that don't SLI unless I use DifferentSLIAuto. Is there any information I could give you that would help on your end?

 

[Arkanggel10]

is it possible to play battle eye games with this latest method?

 

[Pretentious]

is it possible to play battle eye games with this latest method?

You will need to either buy a $400 certificate or use something like UPGDSED to patch the kernel calls that allow battle eye to detect if you can register an unsigned driver. Both methods work.

 

[DBF68]

Hello,

I'm glad I found this forum within the last couple of months. The various posts and instructions eventually allowed me to SLI my NGF GTX 460 & 560 video cards to play through the Crysis games I had put on the back burner over the past decade. The frame rates and overall performance aren't as stellar as what new hardware can produce, but my old system played through Crysis Warhead, C2, and C3 without any problems.

The one thing I'd like to contribute is a better set of instructions, albeit, probably more detailed than desired. It's a composite of both Anatolymik's and Pink Panther's instructions. It also has a fix for the Install.cmd file that I'm kind of surprised no one has created by now.

On Line 35 is this install command:

copy "%_nvlddmkm%.sys" "%SystemRoot%\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_neutral_026dc60e2400f220\%_nvlddmkm%.sys" /y

What's been missing to make the whole install process work properly is this added command on Line 36 to also copy the patched nvlddmkm.sys driver to the %SystemRoot%\System32\drivers folder:

copy "%_nvlddmkm%.sys" "%SystemRoot%\System32\drivers\%_nvlddmkm%.sys" /y

I don't know if the original Install.cmd program creator forgot to add it or if there's a valid reason to not have that command line. Regardless, it doesn't make any sense to create an auto-install program if you still have to manually install the patched nvlddmkm.sys driver. So, I did my best monkey-see-monkey-do programming to come up with the Line 36 command and it's worked each time I've used the updated Install.cmd file.

As you'll see, I've tried to fill in the blanks in these revised instructions for the less initiated when it comes to doing things in Windows. Even so, if you see any errors or a better way to do something in these instructions, let me know and I'll make the changes. If someone here with a lot more seniority than newbie me wants to take charge of it, feel free. I just wanted to help anyone else that comes across this SLI post with instructions I felt were more detailed and efficient.

Thanks for your time.

 

[P!nkpanther]

I think your guide will help people who have trouble managing Windows and need instructions to even be able to install a driver removal app, but otherwise I have the impression it tries to make things more complicated than needed.

Examples:

• Entering Safe Mode is as easy as pressing <shift> while selecting the Restart option in Windows. Windows will present a list of options on next boot.
  Providing two more ways to do the same isn't going to make this install guide any easier to follow. Apart from that, anybody could google this info in seconds, if there truly was a need to do so.
• Why running Install.cmd from the shell, having to navigate through the entire path? Simply right-click the file and select 'Run as administrator'

As for the copy step I added in my original post on page 88, that was because my Windows 10 was migrated from Win 7 through 8.0 -> 8.1, which kept some weird driver locations. That step is not needed in the vast majority of installations.
Problem is, this forum doesn't let you edit older posts, so the corrections have to be added through later ones.

Instead I have since published a better solution in multiple posts, which is to find the target path by using Device Manager → Double click main display adapter → Tab: Driver → Driver Details, as can be seen here in this post by Pretentious:
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3963731
This procedure also solves ambiguities which may come from Windows Update messing with drivers, which is a pain in itself and has been addressed in another post a couple of pages earlier.

Next, replacing the target path in the Install.cmd has to be done using that same info from Device Manager, because it varies between driver versions.
Here's a video I made showing the procedure:

I'm following this thread for quite a long time now and I see that most problems with installing come from people not reading the instructions (or choosing not to follow them).

• GPU architectures have to match
• Patch and driver have to match (1.7.1 matches 388.71): https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3740425
• Test Signing Mode has to be activated; no discussion about that has ever resulted in something
• Installing has to be done by simply running Install.cmd in Safe Mode (w/Networking preferably). No manual copying, no changing ownership, no disabling cards in Device Manager etc.

That's how I would formulate the first time install procedure in a nutshell:

• Install the nVidia driver version matching DifferentSLIAuto. (Inform yourself in the forum, by backreading from the end)
• Find the location of the active nvlddmkm.sys in a folder in C:\Windows\System32\DriverStore\FileRepository. That folder name can be found in Device Manager → Double click main display adapter → Tab: Driver → Driver Details and searching for nvlddmkm.sys
• Unpack DifferentSLIAuto, copy nvlddmkm.sys over to your DifferentSLIAuto directory and run DifferentSLIAuto.exe
  If you're not successful with the patch, you have a version mismatch!
• Edit Install.cmd according to the video above.
• Set UAC off (google it, if you don't know how)
• Enable Test Signing Mode by right-clicking the Start menu button, selecting 'Windows Power Shell (Admin)' and entering:
  • bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
    bcdedit.exe /set NOINTEGRITYCHECKS ON
    bcdedit.exe /set TESTSIGNING ON
• <shift>-Restart into Safe Mode with Networking, right-click Install.cmd and run it as administrator. There should be a certificate installed and 1 file successfully copied.
• Reboot normally, check and enable the SLI option in nVidia Panel
• Re-enable UAC to your liking

If you're installing over an already present installation of DifferentSLIAuto, the old certificates have to be removed first:
Run certmgr.msc, look for DifferentSLIAuto certificates (there's one you can see right away, the other one is under 'Trusted Root Certification → Certificates') and delete them. Same using Regedit for its registry keys (search for keys containing 'differentsliauto' and delete them).

If you're not successful, you might read this post which should help debugging the issue:
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3949499

 

[DBF68]

I think your guide will help people who have trouble managing Windows and need instructions to even be able to install a driver removal app, but otherwise I have the impression it tries to make things more complicated than needed.

Examples:

• Entering Safe Mode is as easy as pressing <shift> while selecting the Restart option in Windows. Windows will present a list of options on next boot.
  Providing two more ways to do the same isn't going to make this install guide any easier to follow. Apart from that, anybody could google this info in seconds, if there truly was a need to do so.
• Why running Install.cmd from the shell, having to navigate through the entire path? Simply right-click the file and select 'Run as administrator'

This is exactly why I wanted feedback. Not everyone knows all the shortcuts to doing things in Windows. You just made and excellent point of the right-click Run As Admin option that I had forgotten. So, that's a change for the better in the documentation.

At the same time, one of the drawbacks with some experienced Windows users creating instruction documentation is that they don't consider less experienced Windows users because it's been so long since they could relate. That's why I always try to provide enough info in step by step form so that even a relative newbie could follow the instructions and get the objective accomplished. I try to be as efficient in the instructions as I can based on what I know, but I may inadvertently choose the long way around that still gets the intended results.

Also, not everyone is using W10. I'm still using W7 because I don't need W10 and I don't jump every time MS releases a new OS. I prefer to let other people be the guinea pigs prior to the first patch release. Although, the way W10 updates have been breaking things lately...

On W7, the shift-Restart option doesn't work. If there's a better way to get to Safe Mode in W7, it'd be nice to know. So, that's why I added the two means of accessing Safe Mode that I know. Now, the instructions need to be updated with the W10 method.

As for the copy step I added in my original post on page 88, that was because my Windows 10 was migrated from Win 7 through 8.0 -> 8.1, which kept some weird driver locations. That step is not needed in the vast majority of installations.

Problem is, this forum doesn't let you edit older posts, so the corrections have to be added through later ones.

That copy step in your page 88 post was very informative and a bit confusing as why there's been so much emphasis on the DriverStore folder. I may be completely wrong, but I thought the DriverStore folder was the location of a known good driver copy to be used if the System32\Drivers version became corrupted or was deleted. As many times as I tried to use the Install.cmd program after following your directions to change the three folder name references, it never worked until I added that Line 36 command to also copy the patched driver to the System32\Drivers folder.

Instead I have since published a better solution in multiple posts, which is to find the target path by using Device Manager → Double click main display adapter → Tab: Driver → Driver Details, as can be seen here in this post by Pretentious:
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3963731
This procedure also solves ambiguities which may come from Windows Update messing with drivers, which is a pain in itself and has been addressed in another post a couple of pages earlier.

Next, replacing the target path in the Install.cmd has to be done using that same info from Device Manager, because it varies between driver versions.
Here's a video I made showing the procedure:

Yes, I've seen that video and I like it. Dev Mgr is helpful for confirming the FileRepository path. At the same time, the search for nv_dispi.inf method seems more direct. Then you can right click on the FileRepository folder and Rename/Copy Name/Enter to Keep Name the FileRepository folder name and paste it in the Notepad folder Replace name field. It just might boil down to personal preference.

I'm following this thread for quite a long time now and I see that most problems with installing come from people not reading the instructions (or choosing not to follow them).

• GPU architectures have to match
• Patch and driver have to match (1.7.1 matches 388.71): https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3740425
• Test Signing Mode has to be activated; no discussion about that has ever resulted in something
• Installing has to be done by simply running Install.cmd in Safe Mode (w/Networking preferably). No manual copying, no changing ownership, no disabling cards in Device Manager etc.

Yes, I saw where you came into this post topic thread and the helpful info you've given to people, including myself. I've slog read and skimmed through most of this topic's pages. I've also seen the same problems people have had over and over. So, it might be helpful to put that qualifier info at the top of the instructions.

Until I added that Line 36 in Install.cmd, the SLI would never engage. Now, I can uninstall the drivers, the certificate, registry entries, and Line 36 from Install.cmd to see if it was just a fluke, but I tried that before with the same no SLI result. So I'm not above saying, "Oops, my mistake.". Maybe Install.cmd works after the folder name changes mostly for other people because those people are using W10, i.e. maybe W10 handles drivers differently than W7.

That's how I would formulate the first time install procedure in a nutshell:

• Install the nVidia driver version matching DifferentSLIAuto. (Inform yourself in the forum, by backreading from the end)
  • Driver version needs to be stated, as do necessary card compatibility specs, and backreading is unnecessarily inefficient.
• Find the location of the active nvlddmkm.sys in a folder in C:\Windows\System32\DriverStore\FileRepository. That folder name can be found in Device Manager → Double click main display adapter → Tab: Driver → Driver Details and searching for nvlddmkm.sys
  • Good for driver location confirmation, but Windows Explorer System32\Driver searching for nv_dispi.inf will have the folder name come up in the search window so you can right click on the folder to Rename/Copy Name/Enter to Keep Name and Paste it for the Replace folder name in Notepad.
• Unpack DifferentSLIAuto, copy nvlddmkm.sys over to your DifferentSLIAuto directory and run DifferentSLIAuto.exe
  If you're not successful with the patch, you have a version mismatch!
  • I'd say directory "folder".
• Edit Install.cmd according to the video above.
• Set UAC off (google it, if you don't know how)
  • Does it matter to set UAC off before or after doing bcdedits? Telling people to Start > Type uac in search field > Select "Change UAC Settings" would save them from unnecessary Googling.
• Enable Test Signing Mode by right-clicking the Start menu button, selecting 'Windows Power Shell (Admin)' and entering:
  • A W10 reference method that doesn't work with W7, but should be included.

bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS​

bcdedit.exe /set NOINTEGRITYCHECKS ON​

bcdedit.exe /set TESTSIGNING ON​

• <shift>-Restart into Safe Mode with Networking, right-click Install.cmd and run it as administrator. There should be a certificate installed and 1 file successfully copied.
  • A W10 reference method that doesn't work with W7, but should be included.
• Reboot normally, check and enable the SLI option in nVidia Panel
• Re-enable UAC to your liking

If you're installing over an already present installation of DifferentSLIAuto, the old certificates have to be removed first:

• Info that should be placed at the top of the instruction list instead at the bottom.

Run certmgr.msc, look for DifferentSLIAuto certificates (there's one you can see right away, the other one is under 'Trusted Root Certification → Certificates') and delete them. Same using Regedit for its registry keys (search for keys containing 'differentsliauto' and delete them).

If you're not successful, you might read this post which should help debugging the issue:
https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3949499

Maybe a set of instructions for experienced Windows 7/10 users first and basic Windows 7/10 users second in the same doc would be the way to go. For users with more than average experience, the short instructions should be fine. For people with far less experience, the detailed walk-through instructions would be better.

The thing I don't want to do is have people back read through 118 pages of forum topic helpful, semi-helpful, and useless filler posts to "maybe" solve their problem(s). This isn't rocket science. It's just a matter of creating a consolidated, efficient, streamlined set of information and instructions that should be, barring anomalies, all that's needed to be known and done to get DifferentSLIAuto1.7.1-win10 to work every time.

 

[P!nkpanther]

...some experienced Windows users creating instruction documentation is that they don't consider less experienced Windows users because it's been so long since they could relate. That's why I always try to provide enough info in step by step form so that even a relative newbie could follow the instructions...

IMHO installing DSLIA takes some minimal knowledge of Windows to be successful. If somebody does not know how to navigate a folder hierarchy or to look up a path in Device Manager, to me that person simply is not qualified to make this installation, but rather will mess up the system.
And it can also be assumed that this person is able to use Google whenever something is not understood.
Example: https://www.google.com/search?q=Set UAC off

Also, not everyone is using W10. I'm still using W7 because I don't need W10 and I don't jump every time MS releases a new OS. I prefer to let other people be the guinea pigs prior to the first patch release. Although, the way W10 updates have been breaking things lately...

I know you'd have to backread a lot, but in case you haven't noticed:
Installing DSLIA on Win 7 differs SIGNIFICANTLY from installing it on Win 10.

• Different versions of DSLIA/nVidia driver used
• No need to change the Install.cmd
• Smaller differences regarding the particularities of the OS's itself

On W7, the shift-Restart option doesn't work. If there's a better way to get to Safe Mode in W7, it'd be nice to know. So, that's why I added the two means of accessing Safe Mode that I know. Now, the instructions need to be updated with the W10 method.
...
Maybe a set of instructions for experienced Windows 7/10 users first and basic Windows 7/10 users second in the same doc would be the way to go.

As I said above: Win 7 and Win 10 are different animals.
The instructions which we try to maintain here in this forum are for Win 10 only.
AFAIK nobody of the regulars here is able to support Win 7 any longer. We don't even know the latest version pair of patch and driver known to work. Any person trying to install on Win 7 has to find this out by himself.
And most importantly: Any of possible future patches in all likelihood would be Win 10 only.

Dev Mgr is helpful for confirming the FileRepository path. At the same time, the search for nv_dispi.inf method seems more direct.

Maybe more direct, but very often it's WRONG. The active driver file actually can be at 3 different locations, depending on the Windows version and whether the driver is managed by Windows or nVidia. See these pictures, where one card is linked to a Windows Update driver, the other one to the nVidia install: https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3963731
Also, some users have leftovers from previous driver versions which reside in very similarly named folders, etc.
That's why the method using Device Manager is the only one which is foolproof. It's one of the things we learned in this forum.

The thing I don't want to do is have people back read through 118 pages of forum topic helpful, semi-helpful, and useless filler posts to "maybe" solve their problem(s).

The main problem is with the forum policy which does not let you update earlier posts or sticky them, as kind of 'Golden Post' which always contains the latest information.
Everything new has to be added in later posts, which makes the information extremely difficult to consolidate.
From time to time I try to link back to posts which contain all the relevant infos or links. That's all I can do in this situation.

...It's just a matter of creating a consolidated, efficient, streamlined set of information and instructions that should be, barring anomalies, all that's needed to be known and done to get DifferentSLIAuto1.7.1-win10 to work every time.

On this point I fully agree. On the other hand that's why it's is not helpful at all to publish another half-baked install method which covers only one use-case. Either it's 100% reliable information in every case or it should be deleted. There are already dozens of install suggestions around; mostly a list of steps taken, which led to success under that user's particular circumstances (or that users particular ignorance, like not wanting to use the install script but to do everything manually). Almost all of these install instructions propose things which are unnecessary (e.g. disabling cards, changing ownership of system files) and try to simplify other things which actually require greater attention (e.g. active driver location).

What I suggest to you is to adapt your instructions to Win 7 only (because that's what you seem to be able to verify with your system). Then that information will be rock solid. In the actual state it's clearly not. It's a mix of Win 7 and Win 10 instructions, tested on Win 7.

But by default, it can be assumed that everything else in this forum will be geared towards Win 10 going forward.

 

[marcipan666]

hi
I use 417.35

i HEX edited sys file succesfuly and create cert, but not show SLI option.
I fixed path in install.cmd

run us admin

install output:

********************************************************************
********************************************************************
Please fix the installation path
manually before running this script
********************************************************************
********************************************************************
Press any key to continue . . .
root "Megbízható legfelső szintű hitelesítésszolgáltatók"
================ Certificate 10 ================
Serial Number: 9908e3d298d77f844013fcd3106b2acf
Issuer: CN=DifferentSLIAuto
NotBefore: 2019. 01. 11. 16:20
NotAfter: 2040. 01. 01. 0:59
Subject: CN=DifferentSLIAuto
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): 17e19f7a97ab0b36fa8920ec67899cd6b6bf8faa
No key provider information
Nem található a tanúsítvány és a titkos kulcs a visszafejtéshez.
CertUtil: -store command completed successfully.
The following certificate was selected:
Issued to: DifferentSLIAuto
Issued by: DifferentSLIAuto
Expires: Sun Jan 01 00:59:59 2040
SHA1 hash: 17E19F7A97AB0B36FA8920EC67899CD6B6BF8FAA

Done Adding Additional Store
Successfully signed and timestamped: nvlddmkm.sys

Number of files successfully Signed: 1
Number of warnings: 0
Number of errors: 0

SUCCESS: The file (or folder): "C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvlddmkm.sys" now owned by the administrators group.
processed file: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvlddmkm.sys
Successfully processed 1 files; Failed processing 0 files
A művelet sikeresen befejeződött.
1 file(s) copied.
Reboot now for changes to take effect



I reboot but no effect.

I use this offset:

417.35

00000000002BB52F: 75 C7
00000000002BB530: 05 43
00000000002BB531: 0F 24
00000000002BB532: BA 00
00000000002BB533: 6B 00
00000000002BB534: 24 00
00000000002BB535: 0E 00


why not working?

 

[P!nkpanther]

Looks like the active nvlddmkm.sys has not been patched. Could be because you have duplicates and you copied over the 'wrong' file.
I'd suggest doing a file search for nvlddmkm.sys in C:\WINDOWS\System32\DriverStore\FileRepository, in addition to checking for the active driver location in Device Manager → Double click main display adapter → Tab: Driver → Driver Details and searching for nvlddmkm.sys

This should lead you to the active file location (which must be used to modify the install script) as well as to the suspected duplicate.

Did you run Install.cmd in Safe Mode?

The difference in size comes from assigning the new certificate.
Looks like a successful install, but the new driver does not circumvent nVidias SLI requirements, meaning it seems unmodded.
So obviously the patch either hasn't been applied correctly or does not match your driver version.

Do you use 417.35 on Windows 10 x64 ?

 

[marcipan666]

Looks like the active nvlddmkm.sys has not been patched. Could be because you have duplicates and you copied over the 'wrong' file.
I'd suggest doing a file search for nvlddmkm.sys in C:\WINDOWS\System32\DriverStore\FileRepository, in addition to checking for the active driver location in Device Manager → Double click main display adapter → Tab: Driver → Driver Details and searching for nvlddmkm.sys

This should lead you to the active file location (which must be used to modify the install script) as well as to the suspected duplicate.

Did you run Install.cmd in Safe Mode?

sys file not oreginal. new different size in :

Yes i run install.cmd in safe mode

now checked signed file in hexedit
0x2bb52f C7 43 27 00 00 00 00

is correct

and try this:

• bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
  bcdedit.exe /set NOINTEGRITYCHECKS ON
  bcdedit.exe /set TESTSIGNING ON

no effect

and 3x DDU today

 

[marcipan666]

sys file not oreginal. new different size in :

View attachment 114388

Yes i run install.cmd in safe mode

now checked signed file in hexedit
0x2bb52f C7 43 27 00 00 00 00

is correct

and try this:

• bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
  bcdedit.exe /set NOINTEGRITYCHECKS ON
  bcdedit.exe /set TESTSIGNING ON

no effect

and 3x DDU today

may not work because no bridge I use only one flexi cable? not have bridge now

 

[P!nkpanther]

Bridge is not absolutely necessary, though highly recommended.

now checked signed file in hexedit
0x2bb52f C7 43 27 00 00 00 00

Isn't it supposed to be
0x2bb52f C7 43 24 00 00 00 00
???

 

[marcipan666]

Looks like the active nvlddmkm.sys has not been patched. Could be because you have duplicates and you copied over the 'wrong' file.
I'd suggest doing a file search for nvlddmkm.sys in C:\WINDOWS\System32\DriverStore\FileRepository, in addition to checking for the active driver location in Device Manager → Double click main display adapter → Tab: Driver → Driver Details and searching for nvlddmkm.sys

This should lead you to the active file location (which must be used to modify the install script) as well as to the suspected duplicate.

Did you run Install.cmd in Safe Mode?

The difference in size comes from assigning the new certificate.
Looks like a successful install, but the new driver does not circumvent nVidias SLI requirements, meaning it seems unmodded.
So obviously the patch either hasn't been applied correctly or does not match your driver version.

Do you use 417.35 on Windows 10 x64 ?

Bridge is not absolutely necessary, though highly recommended.

Isn't it supposed to be
0x2bb52f C7 43 24 00 00 00 00
???

sry 24

this is signed file. I accidentally wrote 27, the file is in 24

I'm clueless. I have no idea
does someone work on 417.35?

 

[P!nkpanther]

This all looks correct.
Did you do a file search for nvlddmkm.sys all over C:\WINDOWS\System32\DriverStore\FileRepository to make sure you have no duplicates?
Does the secondary card point to the same driver location in Device Manager as the primary one?

 

[marcipan666]

This all looks correct.
Did you do a file search for nvlddmkm.sys all over C:\WINDOWS\System32\DriverStore\FileRepository to make sure you have no duplicates?
Does the secondary card point to the same driver location in Device Manager as the primary one?

yes both card use same driver path.
not found other "nvlddmkm.sys" on my drive

win ver?

maybe this solution incompatible for HTC VIVE ?

 

[P!nkpanther]

From what I can tell, everything looks correct: You made a copy of nvlddmkm.sys, patched it and installed it in Safe Mode as admin using Install.cmd, modified with the correct paths. The file was copied and the certificate installed successfully.
Still it doesn't seem to work.

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

 

[marcipan666]

From what I can tell, everything looks correct: You made a copy of nvlddmkm.sys, patched it and installed it in Safe Mode as admin using Install.cmd, modified with the correct paths. The file was copied and the certificate installed successfully.
Still it doesn't seem to work.

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

thx
i rty 388.71 tomorow .

now my brain is burning .. thanks for everything