USB PCIe Expansion Card. Code 10.

takochako

Prominent
Jul 25, 2017
50
0
660
I recently got an Oculus Rift and this USB 3.0 PCIe card so I can actually hook up the Oculus. I have it in a PCIe x1 slot and I have the molex to SATA power connected, but I get this error in device manager:
SQIro9TUTr2d7FvNdIdDMw.png

I have "successfully" installed the drivers for the VIA Labs 805 controller from qicent.cc, via-labs.com, and gigabyte.us, but none of them show up when trying to update the driver for the card. I have done sfc /scannow and all it really did was remove Ultra UX Theme Patcher. Please let me know if you need any more information!
 

takochako

Prominent
Jul 25, 2017
50
0
660


The SATA end is plugged into the PSU and the molex end is plugged into the card.

EDIT: Sorry, I didn't understand. I just connected the PSU molex directly into the molex port for the card, but it didn't change anything.
 

takochako

Prominent
Jul 25, 2017
50
0
660


Yes. That is exactly what it looks like.
 

cpams322

Honorable
Dec 26, 2017
67
1
10,645
I bought a similar type pf PCIe card a few days ago. PCIe can be finicky. I actually had to install the card while the PC was on in order for the BIOS to recognize it. Believe it or not!!! I DO NOT suggest you do that, but I'm just sayin'.

Have you rebooted your system to see if the issue is resolved?

Anyway...

- Uninstall the driver and remove the card then shut down the system. Reinstall the card (if you have compressed air blow out the PCIe slot before putting the card back in). WHen you are booting back up, check your bios to see if it recognizes the card in the slot. If not, then you need to power down and reinstall the card again. If bios sees the card, boot back up and reinstall the driver. Also, make sure the driver you are using is for the right type of OS you are running (32-bit or 64-bit). If this doesn't work uninstall the driver again and have windows check for/install the driver and see if that works.

- Perhaps even a BIOS upgrade is in order if there is one for your BIOS. Just make sure you have a backup copy of your current bios in case the new bios messes things up for you.
 

takochako

Prominent
Jul 25, 2017
50
0
660


I've removed the drivers multiple times and reinstalled the card multiple times in 2 both PCIe x1 slots in my PC. I must've rebooted my computer about 40 times yesterday and today, and it fixed some code 43 errors, but not the code 10. I installed the 64 bit drivers but they won't show up when I try to manually select a different driver. I don't think it's a BIOS issue since the card is successfully detected, I think it might be a driver issue, but I can't change the drivers. When I try to change the driver for the device it just spits out error code 10 again.
 

cpams322

Honorable
Dec 26, 2017
67
1
10,645
You said you have uninstalled and reinstalled the driver several times but that you "can't change the drivers". That's confusing.

Anyhow, after you uninstalled the drivers have you ever tried to let windows install the drivers it thinks are appropriate?
 

takochako

Prominent
Jul 25, 2017
50
0
660
So I just manually installed the drivers after fishing through the Temp folder (they were windows 8.1 drivers, so I don't know if that's causing the problem) and I "successfully" updated the drivers for the USB card to the new ones. However this seems to have introduced another problem. There's a new device showing up as "VIA USB 3 Root Hub" which also has a code 10 error. Except this time it says "STATUS_DEVICE_POWER_FAILURE" when I look in it's properties. Would this be caused by plugging directly into molex instead of SATA to molex?

EDIT: I don't know how useful this will be but I just saw this under Events:
qvO6mIWjRSqw-T1CJ8RQPA.png
 

takochako

Prominent
Jul 25, 2017
50
0
660


Yes I tried to let Windows do it's thing with the drivers, but all it did was use some generic driver that seems to have caused a large portion of this mess.
 

cpams322

Honorable
Dec 26, 2017
67
1
10,645
I read on another site that sometimes a solution to code 10 on one USB device is to uninstall ALL USB drivers. All of them, and then reinstall all of them. You have nothing to lose.

As far as Win 8.1 driver being the wrong driver, no on can really answer that since you never told us what OS you are using. I assumed Win 10 from your screenshots.

As far as not using an adapter and just plugging directly into Molex, well, if you have a molex on your PSU then there is no reason for a sata to molex adapter, of course, unless it's already being used by another device. However, I guess there is always a chance that the molex is defective and not delivering the power it is supposed to be. I would google "molex pinout" and use a multimeter to see if you are getting the voltages you are supposed to be getting from the molex pins.

Of course, you can never rule out that you may have gotten a defective card. It's possible.

I still don't understand why you are having a problem uninstalling drivers. It should not be hard or even impossible to install drivers.
 

takochako

Prominent
Jul 25, 2017
50
0
660


I have 3 molex connectors in my PC and they all work fine. Before I hooked it up to this card I had the connector plugged into some LED strips. Part of me thinks I might have a defective card but since I managed to make slight progress with drivers I'm guessing (and hoping) it's a driver issue. I'm going to uninstall all USB drivers and restart my PC, then I'll update here.
 

takochako

Prominent
Jul 25, 2017
50
0
660
I couldn't uninstall all of them because I couldn't find my PS2 mouse (I kept accidentally removing the device that allowed my keyboard and mouse to work), but I uninstalled most of them and it brought me right back to the beginning. I switched over to the VIA USB eXtensible Host Controller and it add the VIA USB 3 Root Hub again, with the same error. I think the VIA USB 3 Root Hub driver is incompatible with Windows 10. Would it be possible for me to make it compatible?
 

takochako

Prominent
Jul 25, 2017
50
0
660


I'm not sure I understand what you mean...
The problem seems to be that the ViaHub3.sys driver is incompatible with Windows 10. The installer executable would say that the drivers were successfully installed but they weren't. So I ran the executable, grabbed the files from Temp, and ran the inf files to install the drivers. This is probably a stupid question, but is it possible to use inf files in compatibility mode somehow?