SLI with different cards

[tytynono]

It was made for 384.94. Not sure whether it also works for newer versions.

The new driver version 385.69 is released. Please Update the patch.

Edit
I re-installed the 384.94 driver but it's the same, I think it's the version of windows 10 build 16362 that is problematic. For info nvlddmkm is in nv_ref_pubwu.inf_amd64_17a7729c4a220588.

 

[heinrich]

hello folks new buddy here,

I tried to SLI this two graphiccards:

GTX 1050 TI
vs
GTX 660

but get an error, like this: https://s26.postimg.org/7wrd04sk9/wgrgegeg.png
can this "Ember" person please help me with this?

Thanks.

 

[bryllstyles]

hello folks new buddy here,

I tried to SLI this two graphiccards:

GTX 1050 TI
vs
GTX 660

but get an error, like this: https://s26.postimg.org/7wrd04sk9/wgrgegeg.png
can this "Ember" person please help me with this?

Thanks.

U can't SLI different architecture

The new driver version 385.69 is released. Please Update the patch.

Edit
I re-installed the 384.94 driver but it's the same, I think it's the version of windows 10 build 16362 that is problematic. For info nvlddmkm is in nv_ref_pubwu.inf_amd64_17a7729c4a220588.

Use the latest 1.7.1

 

[tytynono]

Use the latest 1.7.1

I use the 1.7.1 but don't work with Windows 10 build 16362.

 

[P!nkpanther]

I use the 1.7.1 but don't work with Windows 10 build 16362.

Does it crash then? Otherwise there's no reason it has anything to do with the version of Windows...

 

[tytynono]

Does it crash then? Otherwise there's no reason it has anything to do with the version of Windows...

Before upgrading to Windows 10 Build 16362, I patch the 384.94 driver with a 1.7.1 patch and it works. Now with the 384.94 or 385.69 driver, patch 1.7.1 does not work at home.
The patch don't crash but

 

[P!nkpanther]

Must have been a wrong version of the nvlddmkm.sys you tried to patch, maybe an orphaned file because of your OS upgrade?
Make sure you have the correct version of that file copied into the DifferentSLIauto directory before you patch.
Look up its version in the file's properties.
I just tested the patch using version 385.28 and DifferentSLIauto 1.7.1 to confirm that the patching works.

Other possible cause might be that nVidia drivers for Win 10 Insider Preview differ from those for current Windows versions, even if the version numbering is the same.
If that's the case, then the patch is not gonna work, no chance.

 

[tytynono]

Must have been a wrong version of the nvlddmkm.sys you tried to patch, maybe an orphaned file because of your OS upgrade?
Make sure you have the correct version of that file copied into the DifferentSLIauto directory before you patch.
Look up its version in the file's properties.
I just tested the patch using version 385.28 and DifferentSLIauto 1.7.1 to confirm that the patching works.

Other possible cause might be that nVidia drivers for Win 10 Insider Preview differ from those for current Windows versions, even if the version numbering is the same.
If that's the case, then the patch is not gonna work, no chance.

I have again updated the driver to have the date of today to be sure of the file.
Since i patch my driver i always had Win 10 Insider Preview
You do not try to patch the 385.69?
I will wait for the next version of the patch before despairing.

 

[robert h sigler]

I have been trying all night to get this to work. Have 2 evga gtx 970 that are not compatible for sli. Tried on my ms7640 3.1 board which supports sli and always said i did not have sli bridge on. After trying many different ways i gave up and moved to a asrock 970a-g/3.1 . Both systems using windows 8.1 64bit . I did everything exactly as instructions say, patching from differentsliauto said something about windows 10 then said successful. but i had to run the install. it always says please fix the installation path manually before running. After running the install once it says directory doesnt exist and cant copy file. I manually changed the nv_dispi.inf_amd64 directory name that was on my harddrive to match what it was looking for and ran it again. It said successful on all. Rebooted and no sli optiona at all. Any ideas? I have 3 gtx 970 2 evga and a zotac and none cane sli together.

 

[P!nkpanther]

Device Manager → Double click your main display adapter → Tab: Driver → Driver Details
Take note where the active nvlddmkm.sys is located.
Go to that location and open the file properties of nvlddmkm.sys→ Tab: Digital Signatures
An unmodified driver would have 3 certificates listed, one from MS the rest from nVidia.
Your modified driver however should list the certificate from DifferentSLIauto.

If that is the case, the install very probably is correct.
If not, well... Try again and follow the instructions closely.

 

[robert h sigler]

I checked the file and it only had 2 cert's, both from nvidia. Found one that had the proper 1 cert from diffsli and manually copied it over. Sli mode is active! I have a bridge hooked up but it still tells me i need 1. Now my problem is how do i play games online with test mode on? Tried to play pubg to test if sli is really working and cant load battleeye because of test mode. Thanks for the help.

 

[CoreyR24]

I checked the file and it only had 2 cert's, both from nvidia. Found one that had the proper 1 cert from diffsli and manually copied it over. Sli mode is active! I have a bridge hooked up but it still tells me i need 1. Now my problem is how do i play games online with test mode on? Tried to play pubg to test if sli is really working and cant load battleeye because of test mode. Thanks for the help.

This is what I asked just a few pages back. It seems there is no way of using this without test signing, so if you want SLI, no PUBG unfortunately buddy.

From the BattlEye website:

When launching the game I get a “Failed to initialize BattlEye Service: Windows Test-Signing Mode not supported.” error. How can I solve this?

Please disable test-signing mode by following this guide: http://support.microsoft.com/kb/2509241. Alternatively you can follow the manual instructions provided here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx. If you are using hardware that requires driver signature enforcement to be disabled please check the vendor’s website for newer drivers. Unfortunately, due to our goal to provide the most effective protection possible we cannot support systems running in test-signing mode in any way. We ask for your understanding.

 

[robert h sigler]

Thats very disheartening, just got a good deal on a 2nd 970 and now i need to get another that matches one of the 3 i have. Ugh.

Couldn't someone who has paid for a cert link a copy of nvlddmkm.sys that they signed and then we would be good?

 

[Paul1234]

I tried to patch the nvlddmkm.sys file but that error appeard. Can anyone help with with this, I don´t know what to do.

 

[P!nkpanther]

Use nVidia driver version 384.94 or 385.28 which are known to work with 1.7.1

 

[Paul1234]

I tried it with the 385.28 version and it worked. I opened install and it worked also. After I restarted my PC but now it says I have no GPU attached too my PC. Any guesses?

 

[P!nkpanther]

Enable test signing mode.

This is no point and click install.
Read and follow the install instructions thoroughly; back read this forum a few pages...

 

[SirDrinkalot]

Ok, i think it could work but i can't get it to work... i don't know what i'm doing wrong and most of the time i don't know what i am doing at all.

SO: i probably won't manage by myself but i want this to work. I'm offering a $25 paysafe to whoever manages to install it for me via team viewer...

 

[P!nkpanther]

You can't install this remotely. You have to boot into Safe Mode to DDU your previous failed installs.
But why don't you just upload screenshots of the patch dialog, the install CMD window and the Digital Signatures properties of your nvlddmkm.sys, then we could actually help you.

(This example depicts the original nVidia driver certificates, not the modified ones)

 

[system1357]

I think I really should do a rewrite of this thing and add more dummy-proof functions like “your driver is too old!” or “please read the instructions THROUGHTOUT CAREFULLY ”

BTW, been trying another approach to live-patch the driver and avoid force driver signing
Tell me if you're interested in this.

 

[tytynono]

I think I really should do a rewrite of this thing and add more dummy-proof functions like “your driver is too old!” or “please read the instructions THROUGHTOUT CAREFULLY ”

BTW, been trying another approach to live-patch the driver and avoid force driver signing
Tell me if you're interested in this.

Of course we are interested. In case the patch does not work, could you tell us a manual method?

 

[slaine_mcroth]

Hello,

I have two quadro M4000, my mainboard is based on X58 chipset and has two PCi x16 gen2 (it's the mainboard of the dell T3500)
Does differentsli has been planned to work with Nvidia quadro ?

 

[P!nkpanther]

Although DifferentSLIauto has been developed exactly to overcome MoBo certification issues, like in your case a MoBo with the correct specs for regular SLI but no SLI cert, the patch will not work because the Quadro series has certified 'professional' drivers, not the consumer type of drivers DifferentSLIauto supports.
Also as far as I know, there are no 'plans' for this project; the original creator has abandoned it and it's basically kept alive by varying volunteers (without guarantees for further support).

 

[slaine_mcroth]

thanks for feedback, this is bad news for me, anyway i will make a try this evening, just to see what happens (a blue screen for sure ;-) )

 

[P!nkpanther]

thanks for feedback, this is bad news for me, anyway i will make a try this evening, just to see what happens (a blue screen for sure ;-) )

No blue screen, it's just that a driver with the wrong type or version cannot be patched at all.