SLI with different cards

[topmysteries5]

Yeah, I'm seeing it now. No offense taken I should have just read my way through the thread

@ Toastybros
You should goto Page 120. Post #2990 has this process in very simplest form possible.
#3000 has results
Different SLI auto doent work with newer driver now, you will have to do hex edit for newer 418 drivers.

@Statelo
I tried your method and sucessfully managed to load modified driver without test mode enabled.
But It brought lots of problems and headaches with it. My rig was getting many different types of random BSOD's with new error name everytime. It was not only during benchmarking, it was happening while browsing the internet too. Sometimes there was random screen black-outs for few seconds in games/ benchmarks. Some BSOD's were "critical structure corruption" and "machine check exception". As soon as I removed DifferentSLIAutoLoader and renabled test signing, everything is fixed now.

I have installed modified nvidia driver by CHEF-KOCH,
https://github.com/CHEF-KOCH/nVidia-modded-Inf
above page has a method to sign driver via SelfCert. Also this modded driver works without test signing after installing its certificate.


@Pretentious
I did hex editing to enable SLI on non matching GPUs as you suggested on #3027. But it didn't work. SLI setting is visible, as soon as I try to enable SLI i get nvlddmkm.sys BSOD. I tried this with GTX 1080 + GTX 1050ti.
As expect SLI is working well in 2/3/4 way with 1050tis.

 

[Elgektos]

Sorry for dumb question guys, but I just don't get it. What am I suppose to do with that numbers? I found nvlddmkm.sys, copied it into DSLIA folder, opened it with HxD aaaaand now what? I can't find this exact strings (e.g. 00000000002C35A3), only some parts of some of them (e.g. 2C35A3 but not 2C35A4). Am I even supposed to find this exact strings? All of them? And what is the second part of that strings (75 C7)?
I have 2 1063 gigabyte and 418.81 drivers.
I have read last 15 pages and still don't understand it. I even watched LTT video.

418.81
===================== The usual stuff
00000000002C35A3: 75 C7
00000000002C35A4: 05 43
00000000002C35A5: 0F 24
00000000002C35A6: BA 00
00000000002C35A7: 6B 00
00000000002C35A8: 24 00
00000000002C35A9: 0E 00

 

[topmysteries5]

Sorry for dumb question guys, but I just don't get it. What am I suppose to do with that numbers? I found nvlddmkm.sys, copied it into DSLIA folder, opened it with HxD aaaaand now what? I can't find this exact strings (e.g. 00000000002C35A3), only some parts of some of them (e.g. 2C35A3 but not 2C35A4). Am I even supposed to find this exact strings? All of them? And what is the second part of that strings (75 C7)?
I have 2 1063 gigabyte and 418.81 drivers.
I have read last 15 pages and still don't understand it. I even watched LTT video.

Please read last 4 pages properly. It not very difficult as it looks. I have posted results too. #3000 and #3012 has results

You should goto Page 120. Post #2990 has this process in very simplest form possible.
and hex edit nvlddmkm.sys according to #3025 on Page 121.
Different SLI auto app doesn't work for newer driver now, you will have to hex edit for newer 418 drivers.

 

[Toastybros]

Please read last 4 pages properly. It not very difficult as it looks. I have posted results too. #3000 and #3012 has results

You should goto Page 120. Post #2990 has this process in very simplest form possible.
and hex edit nvlddmkm.sys according to #3025 on Page 121.
Different SLI auto app doesn't work for newer driver now, you will have to hex edit for newer 418 drivers.

I'm still not fully understanding what I need to Hex edit? What values? I read your post and still am lost

Also in safe mode, I can't find a way to run in administrator mode.

Maybe I'm just overlooking how to do this but I'm lost.

 

[topmysteries5]

I'm still not fully understanding what I need to Hex edit? What values? I read your post and still am lost

Also in safe mode, I can't find a way to run in administrator mode.

Maybe I'm just overlooking how to do this but I'm lost.

Steps to be followed:-
(1) DDU

(2) Install Official / Modded Nvidia 418.81 drivers.

(3) Then copy nvlddmkm.sys from system 32 to your desktop and hex edit it by following #3025 on Page 121.

(4) Use the following in CMD (admin):-
bcdedit.exe /set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set NOINTEGRITYCHECKS ON
bcdedit.exe /set TESTSIGNING ON

(4) Reboot your PC into safemode.

(5) Replace that hex edited nvlddmkm.sys into original location.

(6) Reboot your PC into normal mode.
As soon as you reboot into normal mode, You'll get notification in lower right side of screen that, SLI capable GPUs are installed.

Note:- If your GPUs are connected at PCIE 3.0 X4 (4GB/s) or PCIE 2.0 X8 (4GB/s) lanes, then SLI will never work for you.
Minimum 8GB/s bandwidth is required for SLI.
Minimum requirement is PCIE 3.0 X8 (8GB/s) or PCIE 2.0 X16 (8GB/s) lanes.
Due to only 16 lanes SLI might not work if you already have PCIE 3.0 X4 nvme SSD installed on Kabylake / Skylake or older rigs except X79/X99/X299.

 

[Elgektos]

Please read last 4 pages properly. It not very difficult as it looks. I have posted results too. #3000 and #3012 has results

You should goto Page 120. Post #2990 has this process in very simplest form possible.
and hex edit nvlddmkm.sys according to #3025 on Page 121.
Different SLI auto app doesn't work for newer driver now, you will have to hex edit for newer 418 drivers.

Thanks for reply. I looked through this posts. (but still cant understand meaning of "00000000002C35A3: 75 C7"). So I took a different path -
1. Used DDU to uninstall my drivers.
2. Installed 417.35
3. Changed hex values according to this reply:

Except that for patching nvlddmkm.sys you no longer use DifferentSLIauto.exe, but have to modify a series of bytes using a hex editor:
From address 00000000002BB52F onwards change '75 05 0F BA 6B 24 0E' to 'C7 43 24 00 00 00 00' (valid for 417.35 and 417.71)

4. Then I changed paths in Install.cmd
5. I also added 1 string to Install.cmd according to:

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

Because device manager pointed to System32\drivers\%_nvlddmkm%.sys and not to System32\DriverStore\FileRepository\nv_dispi.inf_amd64_neutral_026dc60e2400f220\%_nvlddmkm%.sys.
6. Safe mode with networking and ran Install.cmd as admin.
7. Reboot
And now i have Code 52 error with this drivers. What did i do wrong?
Sorry for bad english. I also attaching some screenshots, may be it will help, but i doubt it - it is in russian and i dont know how to translate this properly (looks like 2 lines that can be errors - line under hash "no information about key provider", "Could not find certificate and private key for decoding" and signTool Error.

 

[topmysteries5]

@Elgektos
You have messed up your certificates.
Open certmgr and delete DifferentSLIauto certificates by searching it.

Then follow post #3080.

"00000000002C35A3: 75 C7"
this means you have to search "02C35A3" and you'll find '75' as its value. You have to edit that value to C7.

 

[Statelo]

@topmysteries5

I will try to fix your issue. I think it's due to patchguard that isn't disabled (reason of BSOD), because Shark included in my app doesn't work sometimes - maybe needs more time before running DSEFIX.

Signing method is better, but it's not 100% legal.

 

[Pretentious]

@topmysteries5

I will try to fix your issue. I think it's due to patchguard that isn't disabled (reason of BSOD), because Shark included in my app doesn't work sometimes - maybe needs more time before running DSEFIX.

Signing method is better, but it's not 100% legal.

I'm currently working on 419.17, if I have the time I will look through Shark's source code to see if I can put up something together to avoid having to load the driver via DSEFIX.


EDIT:
419.17
=====================
00000000002C2CDB: 75 C7
00000000002C2CDC: 05 43
00000000002C2CDD: 0F 24
00000000002C2CDE: BA 00
00000000002C2CDF: 6B 00
00000000002C2CE0: 24 00
00000000002C2CE1: 0E 00

 

[P!nkpanther]

Because device manager pointed to System32\drivers\%_nvlddmkm%.sys and not to System32\DriverStore\FileRepository\nv_dispi.inf_amd64_neutral_026dc60e2400f220\%_nvlddmkm%.sys.

The patch for 4xx drivers is for Win 10 only.
You're on Windows 7. Nobody of the regulars in this forum can offer much help for that.

• The install procedure for Windows 10 outlined in this post may work for Win 7 (start reading below the video):
  https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3968942
• However you have to find a driver version yourself which can be patched by the legacy patcher (1.7.1), probably 388.71 works.

 

[Elgektos]

@topmysteries5
Thanks. I get it working this time! Now I need to convince EAC that it's just a normal driver. Will try dsefix and UPGDSED

The patch for 4xx drivers is for Win 10 only.
You're on Windows 7. Nobody of the regulars in this forum can offer much help for that.

• The install procedure for Windows 10 outlined in this post may work for Win 7 (start reading below the video):
  https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/post-3968942
• However you have to find a driver version yourself which can be patched by the legacy patcher (1.7.1), probably 388.71 works.

Actually worked fine with 417.35 and bytes from your post. Just added line from DBF68 post - "copy "%_nvlddmkm%.sys" "%SystemRoot%\System32\drivers\%_nvlddmkm%.sys" /y"

 

[topmysteries5]

I'm currently working on 419.17, if I have the time I will look through Shark's source code to see if I can put up something together to avoid having to load the driver via DSEFIX.


EDIT:
419.17
=====================
00000000002C2CDB: 75 C7
00000000002C2CDC: 05 43
00000000002C2CDD: 0F 24
00000000002C2CDE: BA 00
00000000002C2CDF: 6B 00
00000000002C2CE0: 24 00
00000000002C2CE1: 0E 00

I tried non- matching GPU for SLI, I tried with GTX 1070 + GTX 1080. This time there was no BSOD, but screen went black as soon as I clicked apply. also numlock+capslock were lighting on-off when pressed, which means there was no BSOD, screen was just black
Earlier there was nvlddmkm.sys BSOD when GTX 1050ti + GTX 1080 was mixed and SLIed.
I did hex editing to enable SLI on non matching GPUs as you suggested on #3027.

 

[Statelo]

If someone have problems with DifferentSLIAutoLoader BSOD's, please give me your Windows 10 version from winver.exe. I think Shark isn't compatible with your OS version.

 

[slaine_mcroth]

I'm currently working on 419.17, if I have the time I will look through Shark's source code to see if I can put up something together to avoid having to load the driver via DSEFIX.


EDIT:
419.17
=====================
00000000002C2CDB: 75 C7
00000000002C2CDC: 05 43
00000000002C2CDD: 0F 24
00000000002C2CDE: BA 00
00000000002C2CDF: 6B 00
00000000002C2CE0: 24 00
00000000002C2CE1: 0E 00

thank you for these new offsets, works fine

 

[Pretentious]

thank you for these new offsets, works fine

You're welcome.

I tried non- matching GPU for SLI, I tried with GTX 1070 + GTX 1080. This time there was no BSOD, but screen went black as soon as I clicked apply. also numlock+capslock were lighting on-off when pressed, which means there was no BSOD, screen was just black
Earlier there was nvlddmkm.sys BSOD when GTX 1050ti + GTX 1080 was mixed and SLIed.
I did hex editing to enable SLI on non matching GPUs as you suggested on #3027.

I see, yeah Ideally I would need to get my hands on a non 1080 TI in order to test it myself otherwise it's going to be really hard to figure it out if I can't see which instructions are causing the BSOD.

 

[CoUsT]

Black screens are caused when you get "too much" non-matching GPUs I guess?

You can simulate this by locking one of your GPUs to lower profiles. You can do so with nvidia inspector.

Examples:

nvidiaInspector.exe -setPStateLimit:0,0 - limit GPU0 to P0 (highest state, unlimited)
nvidiaInspector.exe -setPStateLimit:0,5 - limit GPU0 to P5 state (max it can go is P5)
nvidiaInspector.exe -setPStateLimit:1,0 - limit GPU1 to P0 (highest state, unlimited)
nvidiaInspector.exe -setPStateLimit:1,5 - limit GPU1 to P5 state (max it can go is P5)

Tested with two 1060.

If you lock it to P2 or so, it will make the screen go black, so keep shortcut nearby to unlimit states again or you will be locked on black screen. I was playing a game and wanted to get away from PC for few hours but didn't want to close the game so I tried locking state to lower one and reduce power usage but the screen went black.

Also, fun fact. Novideo binning is one hella crazy ride. One GPU maxed out at 1.05V, another one barely at 0.9V. Had fun playing with GPUs.

 

[king of swag187]

Hi, kindly read the first post as to understand why this isn't possible

 

[Coler]

Sorry, did anyone test the performance with 2x 1050 Ti SLI, compared to a single one?
unfortunately my low profile SFF case desn't let me go beyond that.
Instead of a larger gpu I would add another one in height

 

[topmysteries5]

Sorry, did anyone test the performance with 2x 1050 Ti SLI, compared to a single one?
unfortunately my low profile SFF case desn't let me go beyond that.
Instead of a larger gpu I would add another one in height

You should at least read last 4 pages of this thread before asking performance results, You'll find everything you need.
I have already shared screenshots with 2 way, 3 way, 4 way SLI with 1050ti.

Page-120 / Post #3000
Page-121 / Post #3012

Note:- You will not get good performance scaling if 16 lanes cpu is used.

 

[Coler]

You should at least read last 4 pages of this thread before asking performance results, You'll find everything you need.
I have already shared screenshots with 2 way, 3 way, 4 way SLI with 1050ti.

Page-120 / Post #3000
Page-121 / Post #3012

Note:- You will not get good performance scaling if 16 lanes cpu is used.

I tried using the search function without any luck, didn't know how many pages back had to read,
Thanks anyway.

 

[gerardfraser]

Thanks to all who help out.
HI there I hope I read enough not to annoy anyone.It is not critical to get RTX SLI running on X470 crossfire motherboard as I have an SLI motherboard I can use.

I would like to enable NVLink SLI without NVLink Bridge on a Crossfire X470 Motherboard that does not support SLI.With RTX 2080 Cards.

Basically I can not seem to enable the SLI part.I have tried a few drivers and maybe I can not do it.I do know that people have made it work,and I am just doing something wrong.

Last driver I tried with correct offset for nvlddmkm.sys and replaced the edited nvlddmkm.sys in the correct folder.
Driver 419.17
RTX 2080 Cards
MSI x470 Gaming Plus motherboard
No NVLink Bridge
Successfully singed and time stamped nvlddmkm.sys
Please check screenshot for any glaring mistake and I am willing to listen to any suggesting.Thanks

 

[gerardfraser]

It seems you're doing everything correctly. This SLI mod will work on any motherboard which has atleast dual PCIe 3.0 X8 slots.

Still no SLI option. Then maybe you dont have enough PCIe lanes available for SLI. You can check your current PCIe lanes speed from GPU-z.
Since all 2nd gen ryzen have 20/24 PCIe lanes, it should work with yout MSI x470 gaming plus mobo. You need to install both GPUs in PCIE_1 and PCIE_4 slots only, so it will work@x8 each.
If your GPUs are connected at PCIE 3.0 X4 (4GB/s) or PCIE 2.0 X8 (4GB/s) lanes, then SLI will never work.
Minimum 8GB/s bandwidth is required for SLI.
Minimum requirement is PCIE 3.0 X8 (8GB/s) or PCIE 2.0 X16 (8GB/s) lanes.

Thanks for the quick reply.
Great reply ,my fault I should have covered that I am good with 20 lanes and 8x8.
Well maybe I will go back a few drivers to 417.22 and give it another shot,I must just try one of my intel systems with SLI motherboard.

 

[P!nkpanther]

Minimum 8GB/s bandwidth is required for SLI.

This is what nVidia requires for certifying motherboards, not a physical requirement of SLI.
We had a lot of Xfire mobos, which only had PCIe 2.0 x4 as secondary slot, successfully used for SLI in this forum, using the old 1.7.1 patch (for 3.xx drivers).
It's possible however that the old patch removed the bandwidth requirement as well, while the new one only removes the check for certification.

 

[Coler]

I'm sure I've done SLI in the past with x16/x4, also people around the web did recently, probably due the old 380 drivers and patch?

EDIT:

Indeed

This is what nVidia requires for certifying motherboards, not a physical requirement of SLI.
We had a lot of Xfire mobos, which only had PCIe 2.0 x4 as secondary slot, successfully used for SLI in this forum, using the old 1.7.1 patch (for 3.xx drivers).
It's possible however that the old patch removed the bandwidth requirement as well, while the new one only removes the check for certification.

 

[P!nkpanther]

Yep, I also used that x4 configuration successfully.

Please check screenshot for any glaring mistake

Looking good, the only thing to check is whether Windows actually loaded the very file you edited by checking the location of the active driver.
Open Device Manager → Double click main display adapter → Tab: Driver → Driver Details and check the folder name of nvlddmkm.sys