Slickback

25 minutes ago, bloodhawk said:

 

Im looking into the registry method @Tech Inferno Fan mentioned earlier in this thread. should be able to test that out tomorrow. If that works, there wont be any need to mess with the BIOS.

I initially tried that however I couldn't find the SurpriseRemovalSupport and EnableRunTimePowerManagement registry entries noted here. That post was also from January so either I just failed in finding them (very possible) or Nvidia has removed them again.

Maybe you'll have better luck?

On ‎2016‎-‎10‎-‎30 at 6:21 PM, GTANAdam said:

I'd like to confirm my theory earlier concerning the Code 43 device error.

Seems like the newer nvidia drivers are trying to reset the graphics device while installing but such feature called "Hotplugging" is not safe on laptops so the BIOS actually partially disables the device to avoid further conflict.

 

So the solution is enabling "Hotplug" in the PCIe settings in BIOS.

For those who are not able to access the advanced options, You will either have to wait for Nvidia to fix it or actually install a custom BIOS (This is dangerous).

Thanks so much! After enabling Hot Plug the new drivers worked, finally!

The only thing is that I had to mod my BIOS to get that setting, might be a possibility for others who have limited BIOS options...

On ‎2016‎-‎10‎-‎24 at 10:45 AM, rbut said:

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!

If it's possible to have that option in eGPU setup that would be awesome, the power profile change didn't work for me either.

Update: The new Nvidia driver 375.63 still gives code 43... 372.70 or below continues to work fine

2 hours ago, bloodhawk said:

It's not specific to MBR users.  Most egpu users are having this issue.  

And no 375.57 isn't working either.

+1 on 375.57 not working  

On ‎2016‎-‎10‎-‎15 at 10:34 PM, Salman said:

 

 

 

Same problem !!

anyone know how to solve this issue ???

 

 

.

 

to solve this issue :

 

I've got the same issue, reinstalled 372.70 and it works fine again. Really hope the next update fixes this!

I was struggling with error 43 as well, I installed 372.70 and it worked perfectly! Don't know what changed in 373.06 but I hope someone fixes it too!

Thanks for your help!

(sorry, don't know how to delete posts)