Jump to content

rb_

Registered User
  • Posts

    10
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    X

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

rb_'s Achievements

Settling In

Settling In (2/7)

4

Reputation

  1. Yes, 372.70 are the last known working drivers. Drivers past that point have issues for mPCIe users (and up until recently, Thunderbolt users). 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.
  2. That's because Nvidia fixed it for us Thunderbolt 2 users, but not mPCI users.
  3. Can confirm that 375.86 does indeed fix Error 43. Woo hoo! (1060 on Win10 64-bit with Akitio Thunder2)
  4. 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.
  5. 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: 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?
  6. @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?
  7. 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!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.