rb_

1 hour ago, ArtemisHD said:

I've been following this thread for a while now and I just wanted to let you know that I'm currently running a Palit GTX 1060 3GB eGPU through my EXP GDC 8.4d (mPCIE) with NVIDIA 372.70 drivers on Windows 10 x64 build 10.0.10586 without any issues at all. I also have my dGPU GTX460M enabled and I can use my dGPU by switching to laptop display from the windows display settings or eGPU by switching to the external display. I hope this helps, thanks!

Yes, 372.70 are the last known working drivers. Drivers past that point have issues for mPCIe users (and up until recently, Thunderbolt users).

1 hour ago, Arquebusa said:

So, sir, there is still hope for the green team, especially the pascal 10xx...
sold my 1050 ti BTW, so, maybe I'll get 1060 now...

I am really lost with the red GPU's, never used it since 2009
 

No a 1060 will have the same issue. It's all Pascal cards. ArtemisHD said he is using 372.70, which are the last drivers that worked flawlessly. I'm sure if he tries running the latest drivers (375.95), he will hit Error 43 also. 

6 hours ago, Lucas114846 said:

I am not 100% sure about others, however, on a Mid 2015 15 inch MBP retina wo/gpu the newest drivers are working properly.

That's because Nvidia fixed it for us Thunderbolt 2 users, but not mPCI users.

13 minutes ago, GTANAdam said:

Nvidia has released an updated driver today versioned 375.86

Someone has to try it and report if it finally fixes this issue.

Can confirm that 375.86 does indeed fix Error 43. Woo hoo! (1060 on Win10 64-bit with Akitio Thunder2)

1 minute ago, Granty said:

I messaged an Nvidia software guy yesterday and asked if they were fixing the Nvidia drivers:

 

I said:
"Maybe you can help... I've tried installing many Nvidia drivers, including: 372.70, 372.90, 373.06, 375.70 and only 372.70 appears to recognise my Zotac GTX 1060 which is connected to my laptop via an Akitio Thunder2 eGPU (Thunderbolt port). The other drivers all cause the error 43. Is this an issue with ALL GTX1000 cards?"

 

and he replied:

"This is a known issue. Fortunately it was just fixed and QA is testing the fix. Assuming it checks out, it will appear in our next driver later this month". 

 

So fingers crossed guys, we will have a solution for this soon, at least sometime this month anyway.

Granty that has made my day. Thank you for the good news!

3 hours ago, Tech Inferno Fan said:

There is some suggestion this may be confined to Win10 anniversary edition [ comments welcome ].

Nope occurs on Win 8.1 also (Akitio Thunder 2 with 1060).

I can confirm two things:

1. Code 43 still occurs on Windows 8.1 (at least on a Thunderbolt 2 eGPU setup). So Windows 8.1 is not a solution.

2. The registry entries that Nando hinted at aren't referenced at all during the install.

I recorderd all registry reads/writes during installing the drivers and there is no reference to Hot plugging, Removal, Restarting, Resetting, etc. So this seems hard coded into the drivers, and not something that can be turned off via a registry entry.

Unfortunately, no solution thus far for Thunderbolt eGPU users, and those without BIOS access to PCI-e hot plugging settings.

Great work @GTANAdam and @bloodhawk.

I did read somewhere that Microsoft implemented Hot Plug for Thunderbolt 3 in Windows 10, so maybe that's why it works for you bloodhawk?

For us Thunderbolt 1-2 users though, it may be dependent on the age of our machines? For Apple users, their website states:

Quote

Thunderbolt devices are "hot pluggable," or usable without a restart, in some cases. Windows 8 or 8.1 on all 2014 and later Mac computers support hot plug.

 

So my Late 2013 rMBP seems out of luck?  Is anyone with a 2014+ Mac able to install the drivers?

I'm guessing playing with the PCI-E Slot Capabilities registers (to enable Hot Plug) is out of the question as it needs to be supported by the BIOS?

The only other option is to try and stop the installer from restarting the card somehow?

2 hours ago, bloodhawk said:

 

Yeah the latest driver is working as well, after i disabled the Advanced Error Reporting.

Were you able to unlock that option as well ? 

 

Instead of ASPM try and check if there is something called "Advanced Error Reporting" or similar under the PCIe settings for the port your eGPU is connected to. Because is the only think that worked for me. ASPM didn't do anything.

 

The black screen could either be :

 

- Unstable link.

- Insufficient power.

- In sufficient Bandwidth, when other ports are being used.

 

Here is a thread i created on their drivers forum :

 

https://forums.geforce.com/default/topic/970339/geforce-drivers/372-90-373-06-drivers-preventing-use-of-gpus-compute-cards-over-m-2-ngff-mpcie-/

@bloodhawk Can you please clarify on your solution. If you disable AER, then install the drivers, then reboot and immediately enable AER, then boot into windows for the first time, does it work?

Or is one reboot of windows with AER disabled required?

Edit: Ignore my post, I see it's already possible.

Would it be possible to disable ASPM before install, and reactivate it after, using something along the lines of pciutils/setpci (aka in software via a kernel driver)? Or is that what Windows is already doing when you disable it in the Power settings?

Edit: @Tech Inferno Fan Is this something that could be added to eGPU setup? (disabling ASPM or L1 Error Reporting). Thanks!