But with generic MS USB 3.0 driver, the card shows it doesn't work with an exclamation sign in Device manager list and doesn't react with any USB device plugged in... All other USB ports on motherboard work normally (https://www.gigabyte.com/Motherboard/GA-...aming-rev-10#ov)

and to mention, when I bought that card, it showed the same error and I returned it back to the store and exchnaged it for the same one they had in stock. When I pluged the 2nd one and saw the same thing, I knew the problem was not in hardware but driver/OS support (think)

Hi All,
I'm seeking some advise on whether I should be updating the drivers for my Intel eXtensible usb3 controller on a DZ77Sl-50K motherboard, whilst running Win10 64bit build 16299?
If it helps my hardwareID is: PCI\VEN_8086&DEV_1E31&SUBSYS_20308086&REV_04 (Screenshot attached with driver version)

The reason for all this is that a Tobii EyeX (in-game eye tracking) that require USB3 explicitly is not being detected correctly, on there website they say there a known issue with Asmedia 3.0 & 3.1 controller, but nothing about a workaround, so my thinking is to updated the drivers, but the only place I can find any reliable information is here as Intel does not provide Win10 drivers.

So any advise you can offer would be appreciated.

Thanks.

I tried to find solution myself again since my last message here.
My motherboard already has vl805 chip on itself for USB 3.0 ports and they work as they should..

Since generic Win10 in-box USB 3.0 drivers doesn't work for add-on card, and VIA doesn't support vl800 for Windows 10, I removed all VIA drivers and tried to see if add-on 3.0 will work. Nope.

Then I tried to update drivers manually with Have disc...used VIA drivers from Page 1 here and got a switch from "USB xHCI Compliant Host Controller" to "VIA xHCI Compliant Host Controller" without an exclamation mark(This device cannot start. (Code 10)). But got another device "VIA USB 3 Root hub" with exclamation mark"This device cannot start. (Code 10); STATUS_DEVICE_POWER_FAILURE" and in Events->Information:Device USB\VIA_ROOT_HUB\5&6ddd906&1 was not migrated due to partial or ambiguous match.
Because of this "ambiguous match", maybe two VIA chips together won't work? (vl805 onboard and vl800 on add-on card).

After that I tried to change two parameters in BIOS, xHCI hand-off and EHCI hand-off to all 4 options, both disabled, both enabled, enabled-disabled, and disabled-enabled. With or without VIA drivers, and Have disc option. No changes.

If anybody has any idea what to do next, I'll try it. Or if @Fernando can add Windows 10 x64 driver support for VIA 3.0 (dev_3483)? I'll give my report here how it went, and finally use this card or throw it to the garbage :D

Ok, I'm sorry to bother you. I thought it's just VIA's laziness that they won't incorporate a string or checkbox to support vl800 in their Windows 10 drivers. Probably there's something more and hardware differences are the reason that Microsoft doesn't support it too.

Thanks for your support (y)

Hi Fernando,

I've installed the following Intel 3.0 drivers on my Asus motherboard:
B. Latest modded Intel USB 3.0/3.1 drivers

I've imported the certificate with administrator rights and the certificate is imported.
Installed the drivers some weeks ago but had no performance impact, still 355 kb/s after a few seconds :-(

Reinstalled the normale windows drivers and today decied to update the intel and other drivers once again.
The certificate is already imported and the batch script tells me so if I run it again.

After the installation with the DPInst.exe (started with admin rights) and a computer restart I get a yellow sign in the devices manager telling me,
that the certificate is not trust worthy somehow and the driver is not signed (error 52)?

I cnanot re-import the certificate as it is already in and I cannot use the drivers now. Any chance you can assist me here what to do?

Many thanks


P.S.
German error message showing in the devices manager:
Die digitale Signatur der für dieses Gerät erforderlichen Treiber kann nicht überprüft werden. Bei einer vor Kurzem durchgeführten Änderung an Hardware oder Software wurde möglicherweise eine Datei installiert, die falsch signiert oder beschädigt ist. Möglicherweise handelt es sich auch um schädliche Software einer unbekannten Quelle. (Code 52)


Edit:
I've removed the 2 certificate files manually, rebboted the pc and reimported them. The cmd file was telling me everything is ok.
After installation the error 52 is shown again and the certificate of one of the installed files is not correct as it seems.

Thank you for the quick answer.

About the cache size:
All my usb sticks are not able to be properly used anymore since a few weeks :-( My files start to copy and all of sudden drop to 0 or 255kb/s.
Any ideas how to change these cache sizes or fix this problem? I experience the most problems with a 2TB hard disk (no ssd) -> usb sticks.
But even copying files from my SSd to the usb sticks drops to 0kb very often. My whole computer freezes then sometimes and I need to do a hard reset.

About your help @error code 52
-I have removed the 2 certificates from the certificates manager, removed the intel host driver and searched for new hardware -> MS host driver got installed and told me to restarted the pc -> Did this.
-After that I have imported the certificate again and everhting seems to work well. Installed the drivers with the DPInst64.exe (admin rights) and the driver installation was really quick, only took abou 4 seconds ?!
The results showed:
Intel(R) Corporation (iusb..) Gerät wurde aktualisiert
Intel(R) Corporation (iusb..) Betriebsbereit
Intel (iusb3hcs) Sytem (... Gerät wurde aktualisiert

Did I do something wrong installing the MS drivers? How am I able to "clean install them and the intel drivers again"?


Edit:
I've just read your intel driver section post again and reinstaleld the MS drivers like explained there (using the "Have file" button).
Restarted, and the installed driver line showed:
Intel(R) USB 3.0 eXtensible-Hostcontroller - 1.0 (Microsoft)
Everything ok.

Tried to manually install the intel 3.0 modified drivers from your website here using the have disk button. It's directly telling me that the digital signature is not ok and the driver cannot be installed.
I've not used the DPInt64.exe file, just manually pointed the system to the inf file.
I'm not sure why this happens but I'm not able to install the driver :-(

Thanks for the link.

@Readyboost:
From reading the Wiki article the readyboost got nothing to do with my problems? I own 16gb of ram, 3 SSDs and my only problem ist, that copying files from the internal hadrdrives or ssd to an extenral USB stick starts performant with about 80mb/s or more and all of sudden drops to 356 kb/s or even 0 kb/s.
I cannot see any relevance of the ReadyBoost sytem here and further more: It worked fine until a few weeks ago windows updated something. Everything was copying fast and reliable.
And all of sudden every copy/move attempt results in a failure as the files won't be transfered anymore.
Even usb 2.0 sticks suffer form that problem. I cannot use any of my usb sticks currently, External harddrives (non ssd) seem to work normal btw.
Edit: Copying to external usb harddrive suffers from the same problem now... WTF?! Starting at 120mb/s, then droppping to 30 then 0kb. And everything freezes then.
Great, now I'm totally unable to copy files to any external ressource. THANK YOU MICROSHIT!

@Intel USB driver
I've read your post and I started with the controller driver "iusb3xhc" from the subfolder "Controller" and this is giving me the info that the digital signature is not signed!
I wasn't able to try the host or hub drivers afterwards as the controler is telling me the error message at first.

I'm uisng the following usb drivers from your post:
"only for Intel Chipsets from 8-Series up:"

Hardware ID of the controller with MS driver: PCI\VEN_8086&DEV_A12F&SUSBSYS_869410&REV_31
Hardware ID of controller with your Intel usb 3.0 drivers: PCI\VEN_8086&DEV_A12F&SUSBSYS_869410&REV_31
-> Not able to show you another hardware ID as it seems to not update due to the non installing driver?!

Any possibilities to get a "debug log" or "logfile" from the DPInst64.exe file I can send you?

Ok thanks for the test. Well good for you but that doesn't fix my problem unfortunately.

What could be the problem that my windows is telling me the file is not signed correctly?
I've disabled all antivirus and other tools.
Followed the instructions in your post.
Deleted the certificates and reinstalled them.

Any idea why the file tells me that it's not correct then?
Windows 10 pro, 64bit, version 10.0.15063