SLI with different cards

[Darekills4]

I saw your posts on GitHub and unknowncheats, you're looking for people to tell you exactly what to do instead of trying to come up with the solution yourself so I will leave it at that.

Because these are potential exploits, and if there's no loophole in Windows to load unsigned drivers in normal mode then we are out of luck. Plus I am no security researcher.

 

[Pretentious]

One-Knee-Toe used windows 10 enterprise LTSC 2019

Heavenwood used Windows 10 enterprise LTSC 2016

also Pretentious used windows 10 enterprise??

i used windows 10 pro..

I believe the two were related.

What do you think?

I use Windows 10 Education but I can guarantee that the issue is not Windows version related. You're most likely making a mistake during the hex patching or .batch file.

 

[adiots123]

I use Windows 10 Education but I can guarantee that the issue is not Windows version related. You're most likely making a mistake during the hex patching or .batch file.

Correct, i failed on w10 enterprise .

I use Windows 10 Education but I can guarantee that the issue is not Windows version related. You're most likely making a mistake during the hex patching or .batch file.

may i have a question?

your motherboard is Z9PE-D8 WS?

i found this mobo got certification "sli license"

 

[Statelo]

I was looking for a solution for a few days and finally I have managed to load modified driver without test mode enabled I've singed the driver through software named DriverSigner that can be downloaded from UnknownCheats forum. It was tricky but it worked for me. It's the best solution so far, because a lot of tools for loading unsigned drivers like DSEFix can be detected by anticheats and doesn't work with modified Nvidia driver.

I was following these steps:
1. Install original Nvidia Driver.
2. Copy nvlddmkm.sys from System32 to DifferentSLIAuto folder.
3. Patch nvlddmkm.sys with DifferentSLIAuto.exe or HexEditor (depending on version of driver).
4. Download and extract DriverSigner from UnknownCheats forum.
5. Sign the driver by following the steps from pdf manual in DriverSigner folder.
6. Boot into safe mode.
7. Change the driver in System32 to the modified one.
8. Reboot computer.
9. Success!

I have enabled SLI on Non-SLI cards and motherboard. As you can see on the screenshoots, I'm playing Fortnite. Anticheat doesn't block the game due to disabled driver signature enforcement, that's because I'm not in Test Mode. I was using old Nvidia driver 342.01, because of crappy unsupported cards - Geforce 210 and 310 from 2009. I don't know if it will work on newer drivers but I think it will.

 

[Darekills4]

I was looking for a solution for a few days and finally I have managed to load modified driver without test mode enabled I've singed the driver through software named DriverSigner that can be downloaded from UnknownCheats forum. It was tricky but it worked for me. It's the best solution so far, because a lot of tools for loading unsigned drivers like DSEFix can be detected by anticheats and doesn't work with modified Nvidia driver.

I was following these steps:
1. Install original Nvidia Driver.
2. Copy nvlddmkm.sys from System32 to DifferentSLIAuto folder.
3. Patch nvlddmkm.sys with DifferentSLIAuto.exe or HexEditor (depending on version of driver).
4. Download and extract DriverSigner from UnknownCheats forum.
5. Sign the driver by following the steps from pdf manual in DriverSigner folder.
6. Boot into safe mode.
7. Change the driver in System32 to the modified one.
8. Reboot computer.
9. Success!

I have enabled SLI on Non-SLI cards and motherboard. As you can see on the screenshoots, I'm playing Fortnite. Anticheat doesn't block the game due to disabled driver signature enforcement, that's because I'm not in Test Mode. I was using old Nvidia driver 342.01, because of crappy unsupported cards - Geforce 210 and 310 from 2009. I don't know if it will work on newer drivers but I think it will.

Oh.
I literally downloaded DriverSigner and was reading through the PDF but then I saw all the comments on the UnknownCheats forum regarding how the certificates are old and don't work / don't work with the latest update of Windows.
I have failed to live up to my own principles of "don't trust anyone".

Thank you @Statelo.

I guess I owe @Pretentious an apology.

Sorry.

 

[Pretentious]

Correct, i failed on w10 enterprise .



may i have a question?

your motherboard is Z9PE-D8 WS?

i found this mobo got certification "sli license"

Correct, that is one of the motherboard that I own and it does in fact have SLI enabled. With that being said I'm the person who's releasing the offsets so you need not to worry about that , I test the changes on a system without SLI certification

Oh.
I literally downloaded DriverSigner and was reading through the PDF but then I saw all the comments on the UnknownCheats forum regarding how the certificates are old and don't work / don't work with the latest update of Windows.
I have failed to live up to my own principles of "don't trust anyone".

Thank you @Statelo.

I guess I owe @Pretentious an apology.

Sorry.

You don't owe me any apology. I do stick by what I said, there are ways to get Windows to load the unsigned driver by nvidia while blocking all others but it does require some creativity using similar methods to those I posted a couple of messages ago. As for using DriverSigner, it's all good but keep in mind those certificates are usually leaked online (so it is illegal to use them). You guys as individuals are unlikely to suffer any consequences from using them but it's something to keep in mind. Moreover, if the certificate expires or becomes blacklisted by MS you end up being unable to sign newer versions of the driver.

In any case, happy SLI 'ing

 

[adiots123]

Correct, that is one of the motherboard that I own and it does in fact have SLI enabled. With that being said I'm the person who's releasing the offsets so you need not to worry about that , I test the changes on a system without SLI certification



You don't owe me any apology. I do stick by what I said, there are ways to get Windows to load the unsigned driver by nvidia while blocking all others but it does require some creativity using similar methods to what I posted a couple of messages ago. As for using DriverSigner, it's all good but keep in mind those certificates are usually leaked online (so it is illegal to use them). You guys as individuals are unlikely to suffer any consequences from using them but it's something to keep in mind. Moreover, if the certificate expires or becomes blacklisted by MS you end up being unable to sign newer versions of the driver.

In any case, happy SLI 'ing

Thank you for ur reply.

I understand your words.

I will look forward to new test on non sli liecensed mobo.

Thank u so much!!

 

[6ixxx$h00ter]

Your use case doesn't sound like it would require SLI at all (@P!nkpanther any thoughts?). In terms of the whole P106 situation, I don't know of anyone who has actually tried to do the whole pass-through method with the most recent drivers. Assuming that it works (with the latest driver) then it would make sense to explore SLI, but honestly most people seem to be trying to put the "cart before the horse".


EDIT: For those who would like to test SLI with non matching GPU's and @topmysteries5:

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
=====================

------------------------------------ This might help enable SLI in non matching GPU's - ATTENTION: A lot of these bytes are not contiguous (adjacent to each other), make sure to patch things correctly and report back
00000000002C35ED: 0F 90
00000000002C35EE: BA 90
00000000002C35EF: 6B 90
00000000002C35F0: 24 90
00000000002C35F1: 11 90
------------------------------------
00000000002C3600: 0F 90
00000000002C3601: BA 90
00000000002C3602: 6B 90
00000000002C3603: 24 90
00000000002C3604: 18 90
------------------------------------
00000000002C3613: 0F 90
00000000002C3614: BA 90
00000000002C3615: 6B 90
00000000002C3616: 24 90
00000000002C3617: 19 90
------------------------------------
00000000002C3628: 0F 90
00000000002C3629: BA 90
00000000002C362A: 6B 90
00000000002C362B: 24 90
00000000002C362C: 0B 90
------------------------------------
00000000002C363F: 0F 90
00000000002C3640: BA 90
00000000002C3641: 6B 90
00000000002C3642: 24 90
00000000002C3643: 0C 90
------------------------------------
00000000002C3659: 0F 90
00000000002C365A: BA 90
00000000002C365B: 6B 90
00000000002C365C: 24 90
------------------------------------
00000000002C365D: 0F 90
00000000002C366E: 0F 90
00000000002C366F: BA 90
00000000002C3670: 6B 90
00000000002C3671: 24 90
00000000002C3672: 10 90
------------------------------------

EDIT 2: Separated the offsets by contiguous blocks so that it's easier to digest/follow.

I don't know how to Hex Edit, but would this work with the newest Nvidia Drivers, and with a TXP paired with a 980ti? I'm looking for a little boost in 4k gaming, and since I already own a 980ti, I wanted to know if I could use it, instead of it just lying around. If anyone could provide the modified driver with these changes, that would be highly welcomed!

"Would an SLI bridge be needed for this type of setup??"

My board supports SLI.

 

[Darekills4]

You don't owe me any apology. I do stick by what I said, there are ways to get Windows to load the unsigned driver by nvidia while blocking all others but it does require some creativity using similar methods to what I posted a couple of messages ago. As for using DriverSigner, it's all good but keep in mind those certificates are usually leaked online (so it is illegal to use them). You guys as individuals are unlikely to suffer any consequences from using them but it's something to keep in mind. Moreover, if the certificate expires or becomes blacklisted by MS you end up being unable to sign newer versions of the driver.

In any case, happy SLI 'ing

I believe the certificate is already blacklisted.
A few hours after I signed the drivers using @Statelo's method, Windows Malicious Software Removal Tool detected the driver and simply deleted it on the next boot.

For those using @Statelo's method, you will have to disable Windows Malicious Software Removal Tool. Winaero has a good guide about it.

https://winaero.com/blog/disable-malicious-software-removal-tool/

In my case, I was unable to remove the Windows Malicious Software Removal Tool using the 'wusa' command. If the same happens to you, simply delete 'MRT.exe' from your 'System32' folder.

 

[P!nkpanther]

...would this work with the newest Nvidia Drivers, and with a TXP paired with a 980ti?

Won't work because of different microarchitectures and even if it did, the performance difference between the cards would make the end result barely better than the single TXP (twice the performance of the weaker card is the theoretical max. and in practice it's maybe 85% of that).

 

[Statelo]

I was also working on another method of bypassing anti cheats detection of test mode. I found that if I change the certain registry key, BattleEye would block me from running the game or not. You need to read Element's value from HKLM\BCD00000000\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\23000003, then go to the key that is in Element's value. For me it's HKLM\BCD00000000\Objects\{c954eef3-2c98-11e9-8fcc-d7809f568b70} and then go to Elements\16000049. If you change there an Element value to 01, BattleEye would detect that you are in Test mode even when you're not. But if you change it to 00, BattleEye won't block the game from loading. It's cool but it's not working when you are in Test Mode that way. I have also found on UnknownCheats forum that BattleEye is loading a unsigned floppy driver to test if test mode is enabled. If a driver is loaded, that means that test mode is enabled. But if it won't load, test mode is disabled. So I came to the conclusion that If I block loading drivers in test mode somehow it's very possible that I will enable game without an issue.

 

[Darekills4]

I was also working on another method of bypassing anti cheats detection of test mode. I found that if I change the certain registry key, BattleEye would block me from running the game or not. You need to read Element's value from HKLM\BCD00000000\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\23000003, then go to the key that is in Element's value. For me it's HKLM\BCD00000000\Objects\{c954eef3-2c98-11e9-8fcc-d7809f568b70} and then go to Elements\16000049. If you change there an Element value to 01, BattleEye would detect that you are in Test mode even when you're not. But if you change it to 00, BattleEye won't block the game from loading. It's cool but it's not working when you are in Test Mode that way. I have also found on UnknownCheats forum that BattleEye is loading a unsigned floppy driver to test if test mode is enabled. If a driver is loaded, that means that test mode is enabled. But if it won't load, test mode is disabled. So I came to the conclusion that If I block loading drivers in test mode somehow it's very possible that I will enable game without an issue.

That's nice to have an alternate method, but from what I have read on UnknownCheats, BattleEye and Easy Anti-Cheat will flag you if you have an unsigned driver running in the kernel space.
So the previous method you posted is much safer.

If you plan on testing, make sure to test on a different account (unless it's a MAC ID ban, so you might wanna spoof that too, just in case).

 

[Pretentious]

I was also working on another method of bypassing anti cheats detection of test mode. I found that if I change the certain registry key, BattleEye would block me from running the game or not. You need to read Element's value from HKLM\BCD00000000\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\23000003, then go to the key that is in Element's value. For me it's HKLM\BCD00000000\Objects\{c954eef3-2c98-11e9-8fcc-d7809f568b70} and then go to Elements\16000049. If you change there an Element value to 01, BattleEye would detect that you are in Test mode even when you're not. But if you change it to 00, BattleEye won't block the game from loading. It's cool but it's not working when you are in Test Mode that way. I have also found on UnknownCheats forum that BattleEye is loading a unsigned floppy driver to test if test mode is enabled. If a driver is loaded, that means that test mode is enabled. But if it won't load, test mode is disabled. So I came to the conclusion that If I block loading drivers in test mode somehow it's very possible that I will enable game without an issue.

Precisely, not only that but following such approach is the only way to have the driver working in a way that is agnostic to any Anti-cheat.

 

[Statelo]

Here's more legal way to load unsigned driver without test mode. DSEFix as I mentioned before doesn't work. That's because of PatchGuard that prevents patching the kernel. A lot of tools for disabling it doesn't work with the latest version of Windows, but I found one that is working. By disabling PatchGuard in real time, we can disable DSE to load driver and then enable it, so we won't have problems with Anti cheats.

You need to follow these steps:
1. Install original Nvidia Driver.
2. Download DSEFix and Shark from Github.
3. Move dsefix.exe and Shark folder to C:\ (to make it easier).
4. Copy nvlddmkm.sys from System32 to DifferentSLIAuto folder.
5. Patch nvlddmkm.sys with DifferentSLIAuto.exe or HexEditor (depending on version of driver).
6. Boot into safe mode.
7. Change the driver in System32 to the modified one.
8. Reboot computer.
9. Open CMD as admin and Device Manager.
10. Go to Shark folder and run it from cmd. → cd C:\2018-12-27-19-52-00 and Shark.exe
11. Wait 2 or 3 seconds and run dsefix.exe from cmd. → dsefix.exe
12. Re-enable Nvidia driver in Device Manager by right clicking on your GPUs, selecting disable and then enable.
13. Go to Nvidia Control Panel and turn on SLI.
(If you end up with Nvidia Control Panel crash, just restart the computer, load driver by doing steps 9,10,11,12,14 and SLI will be enabled)
14. Run DSEFix from cmd but use -e argument. → dsefix.exe -e
15. Success!

Redo points 9,10,11,12,14 on every boot in order to load the driver.

I might write a simple script to do these steps automatically on every boot. Anyways, like in previous method, SLI is working perfectly fine and Anti Cheat doesn't complain. It's more complicated than previous one but I feel better about it I used Windows 10 17134 and Nvidia Driver 342.01.

 

[Grey]

This is great. Of course this method is better

 

[Grey]

Can this help ?
This

 

[Pretentious]

Here's more legal way to load unsigned driver without test mode. DSEFix as I mentioned before doesn't work. That's because of PatchGuard that prevents patching the kernel. A lot of tools for disabling it doesn't work with the latest version of Windows, but I found one that is working. By disabling PatchGuard in real time, we can disable DSE to load driver and then enable it, so we won't have problems with Anti cheats.

You need to follow these steps:
1. Install original Nvidia Driver.
2. Download DSEFix and Shark from Github.
3. Move dsefix.exe and Shark folder to C:\ (to make it easier).
4. Copy nvlddmkm.sys from System32 to DifferentSLIAuto folder.
5. Patch nvlddmkm.sys with DifferentSLIAuto.exe or HexEditor (depending on version of driver).
6. Boot into safe mode.
7. Change the driver in System32 to the modified one.
8. Reboot computer.
9. Open CMD as admin and Device Manager.
10. Go to Shark folder and run it from cmd. → cd C:\2018-12-27-19-52-00 and Shark.exe
11. Wait 2 or 3 seconds and run dsefix.exe from cmd. → dsefix.exe
12. Re-enable Nvidia driver in Device Manager by right clicking on your GPUs, selecting disable and then enable.
13. Go to Nvidia Control Panel and turn on SLI.
(If you end up with Nvidia Control Panel crash, just restart the computer, load driver by doing steps 9,10,11,12,14 and SLI will be enabled)
14. Run DSEFix from cmd but use -e argument. → dsefix.exe -e
15. Success!

Redo points 9,10,11,12,14 on every boot in order to load the driver.

I might write a simple script to do these steps automatically on every boot. Anyways, like in previous method, SLI is working perfectly fine and Anti Cheat doesn't complain. It's more complicated than previous one but I feel better about it I used Windows 10 17134 and Nvidia Driver 342.01.

Awesome job and thanks for sharing. Just wanted to point out a quick remark, https://github.com/hfiref0x/UPGDSED/tree/dev that branch works with the latest windows version

EDIT: Whops I hadn't noticed you were using Shark

 

[Statelo]

Thanks @Pretentious.

I made a simple app that will load driver automaticlly on every boot. I've also made a simple tool to load driver without re-enabling DSE so you can enable SLI in Nvidia Control Panel and then re-enable DSE by yourself.

Here's updated method:
1. Install original Nvidia Driver.
2. Download DifferentSLIAutoLoader from Github and extract it.
3. Copy nvlddmkm.sys from System32 to DifferentSLIAuto patch folder.
4. Patch nvlddmkm.sys with DifferentSLIAuto.exe or HexEditor (depending on version of driver).
5. Boot into safe mode.
6. Change the driver in System32 to the modified one.
7. Reboot computer.
8. Go to DifferetnSLIAutoLoader folder and run DifferentSLIAutoTools.exe.
9. Click "Load driver" button.
10. Go to Nvidia Control Panel and turn on SLI.
11. Go back to DifferentSLIAutoTools and click "Re-enable DSE" button.
12. Find Install script in DifferentSLIAutoLoader folder and run it as Admin.
13. Success!

DifferentSLIAutoLoader will start on every boot and load unsigned driver.

 

[Toastybros]

Hello!

Maybe I am missing a lot in this forum but I am at a loss trying to get this to work with 2x 1050's. (I suck at navigating these forums to find what I need to do next)

I follow these steps

1. Installed GPU
2. Installed drivers
3. Rebooted
4. Put in second GTX 1050
5. Download DifferentSLIAuto
6. Went to find nvlddmkm.sys but it does not exist in my system32 folder?

Went ahead and tried to run the Install and got an obvious error that the nvlddmkm.sys doesn't exist.

I apologize if this has been answered but I'm struggling to find it in this thread.

Thanks.

 

[king of swag187]

Curious but why 1050's? Is it for a new video?

 

[Darekills4]

Hello!

Maybe I am missing a lot in this forum but I am at a loss trying to get this to work with 2x 1050's. (I suck at navigating these forums to find what I need to do next)

I follow these steps

1. Installed GPU
2. Installed drivers
3. Rebooted
4. Put in second GTX 1050
5. Download DifferentSLIAuto
6. Went to find nvlddmkm.sys but it does not exist in my system32 folder?

Went ahead and tried to run the Install and got an obvious error that the nvlddmkm.sys doesn't exist.

I apologize if this has been answered but I'm struggling to find it in this thread.

Thanks.

nvlddmkm.sys is located in 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_****************'
Copy it to the DifferentSLIAuto folder.
Edit with a hex editor (I have quoted Pretentious below regarding which values need to be edited (keep in mind it's only for 418.81)).
Edit the "install.cmd" depending upon your 'nv_dispi.inf_amd64_****************' folder name (there should be 3 edits)
Boot in safe mode and run "install.cmd" as an Administrator.

It's that time of the month again

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

 

[P!nkpanther]

The correct way to find out the location of the active driver is to open Device Manager → Double click main display adapter → Tab: Driver → Driver Details and looking for the folder name of nvlddmkm.sys
On Win 10 it's in C:\Windows\System32\DriverStore\FileRepository\ and then within something like nv_dispi.inf_amd64_4aa19ae78d94d8a3
On Win 7 (only relevant for the 'classic' patch) it's in C:\Windows\System32\drivers\

This procedure is important since the location depends on the Windows version and whether the driver is managed by Windows Update 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 may have leftovers from previous driver versions which reside in very similarly named folders, etc.

 

[Toastybros]

The correct way to find out the location of the active driver is to open Device Manager → Double click main display adapter → Tab: Driver → Driver Details and looking for the folder name of nvlddmkm.sys
On Win 10 it's in C:\Windows\System32\DriverStore\FileRepository\ and then within something like nv_dispi.inf_amd64_4aa19ae78d94d8a3
On Win 7 (only relevant for the 'classic' patch) it's in C:\Windows\System32\drivers\

This procedure is important since the location depends on the Windows version and whether the driver is managed by Windows Update 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 may have leftovers from previous driver versions which reside in very similarly named folders, etc.

Oh wow, thanks! It didn't even cross my mind that the tutorial I was looking at was for Windows 7. Will try this and report back on the progress!

Curious but why 1050's? Is it for a new video?

Also yes, doing this for some content.

 

[topmysteries5]

Hello!

Maybe I am missing a lot in this forum but I am at a loss trying to get this to work with 2x 1050's. (I suck at navigating these forums to find what I need to do next)

I follow these steps

1. Installed GPU
2. Installed drivers
3. Rebooted
4. Put in second GTX 1050
5. Download DifferentSLIAuto
6. Went to find nvlddmkm.sys but it does not exist in my system32 folder?

Went ahead and tried to run the Install and got an obvious error that the nvlddmkm.sys doesn't exist.

I apologize if this has been answered but I'm struggling to find it in this thread.

Thanks.

I'm not trying to offend you, you must at least read last 3 pages of this thread, You'll find everything you need.
I have already shared screenshots with 2 way, 3 way, 4 way SLI with 1050ti.

 

[Toastybros]

I'm not trying to offend you, you must at least read last 3 pages of this thread, You'll find everything you need.
I have already shared screenshots with 2 way, 3 way, 4 way SLI with 1050ti.

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