Maybe not, but you can do a right-click onto the yellow flagged device and choose the options "Update driver" > "Search for updated drivers on Windows Update". Which is the reason for the yellow exclamation mark (right click onto it and choose the option "Properties")?
You can easily find out the sort and manufacturer of that driver, if you open the INF file named oem71.inf, which you can find within the C:\Windows\INF directory.
Yes, I did that before. It turned out that the driver Windows then searched for wasnât one that this Etron chip requires. Windows reported that the only driver it had found was "Intel Xeon E3-1200/1500 v 5th/6th Gen Intel Core PCIe Controller (x 16) -1901" and that that was not the right one for this device!
Ah, I see, thanks. Hereâs the file header
1 2 3 4
; ** Filename: SkylakeSystem.inf ** ; ** Abstract: Assigns the null driver to devices ** ; ** for yellow-bang removal and ** ; ** brands Intel(R) devices
I assume that means that it isn't the cause of the problem I'm having.
@roberto : Thanks for the details of the oem71.inf file. Neither the file named SkylakeSystem.inf nor the other one for the device named "Intel Xeon E3-1200/1500 v 5th/6th Gen Intel Core PCIe Controller (x 16) -1901" are real drivers, but just Intel Chipset Device information files, which are not able to manage an USB 3.0/3.1 Controller. Please do again a right-click onto the yellow flagged device and post the DeviceID (DEV_XXXX) of it. You will get it by choosing the options "Properties" > "Details" > "Property" > "HardwareIDs".
Thanks for the email, and for the interest youâre taking. Iâll reply with the info you requested as soon as Iâve installed the StarTech card in my machine again (I removed it when I ceased making any progress and was close to giving up).
@roberto : AFAIK the only INF file, which definitively supports the Intel DeviceID DEV_1901, is the SkylakeSystem.inf, which you obviously have already installed and stored as oem71.inf. Attached is the latest version 10.1.1.38 of it.
Just checked, and thatâs the version number of the .inf file already in the Windows directory.
So that seems to exhaust all the possibilities.
Iâm left a bit puzzled however as to how this situation can come about because in theory it shouldnât be happening. I imagine it has to do with the care/skill with which the oemâs programmers wrote the driver for this controller-chip, and that theyâve sliipped-up somewhere along the way. Or might it be that the driver is OK but that some glitch in Windows 10 is causing it to faill to interact successfully with this driver?
Either way it leaves me stranded, with a device I canât use.
If you open the related INF file by using Notepad, you will find something interesting regarding the supported HardwareIDs: %PCI\VEN_8086&DEV_1900Desc%=Needs_NO_DRV,PCI\VEN_8086&DEV_1900 %PCI\VEN_8086&DEV_1901Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_1901 %PCI\VEN_8086&DEV_1905Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_1905 %PCI\VEN_8086&DEV_1909Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_1909 %PCI\VEN_8086&DEV_190FDesc%=Needs_NO_DRV,PCI\VEN_8086&DEV_190F %PCI\VEN_8086&DEV_1910Desc%=Needs_NO_DRV,PCI\VEN_8086&DEV_1910 %PCI\VEN_8086&DEV_191FDesc%=Needs_NO_DRV,PCI\VEN_8086&DEV_191F
According to the above entries the listed devices with the DeviceIDs DEV_1901 (yours), DEV_1905 and DEV_1909 definitively need a separate real PCI driver (= *.SYS file), whereas the devices with the DeviceIDs DEV_1900, DEV_190F, DEV_1910 and DEV_191F donât. My advice: Ask the manufacturer of your PCI card for the required driver.
Hello, I have a huge problem with the GA-Z77X-UD3H, Windows 10 64 Bit and the USB 3.0 ports. External hdds arenât working properly if I connect them to the USB 2.0 port they work fine.
Can you help me how to fix this problem, I guess I have to replace the Intel USB and the VIA USB driver? Attached a screenshot of my USB-Controller itâs in German but should be okay |addpics|c67-1-0744.png-invaddpicsinvv|/addpics|
Searching PCI\VEN_8086&DEV_1901 on Microsoft Update Catalog gives a choice of 10.1.1.38 or 10.1.2.80 drivers, it may be worth trying the "full" 10.1.2.80 from Station-Drivers http://www.station-drivers.com/index.phpâŚid=2441&lang=en
Windows can be a bit lax in finding those drivers on the Catalog, they donât always turn up in automatic search
Yes, this is what I recommend to do. Note: When you are going to install the Intel USB 3.0 drivers, you have to take my mod+signed ones. Win10 will not accept the original Intel USB 3.0 drivers.
Regards Dieter (alias Fernando)
@Matth79 : Thanks for your advice, but I doubt, that it will help roberto. Reasons: 1. Both Intel Chipset Device INF files v10.1.1.38 and v10.1.2.80 are simple text files and no drivers. 2. The entries of both INF files regarding the DEV_1901 device are identical:
I did as you told me, but unfortunately itâs not working. Now its not been able to install the drivers for my external USB 2.0 Hub what did go wrong?
Best regards |addpics|c67-2-2cdf.png,c67-3-d7af.png|/addpics|
Which special USB 2.0 device (manufacturer/model) do have connected? Have you tried to let Windows Update search for a suitable driver for that device?
Somehow its working now. I switched back to the old drivers, except I kept your PCI bus driver. Is it okay to do so. Or is better to replace them with the âoriginalâ one as well?
And is it possible to update the driver for the Intel Host controllers, in the past I had often uninstall them cause something didnât work? Does the Intel Update from the Giagabyte site does any good?
If you should mean the 3 Intel USB 3.0 drivers (for the Controller, the Hub devices and the device named "PCI Express Root Complex", you should either install them all or none of them.
It is possible to update the Intel USB 3.0 drivers, but you have to take the mod+signed ones, because Win8 and Win10 are natively not supported by the original Intel USB 3.0 drivers.
I doubt, that this tool will let you know about new Intel USB 3.0 drivers, because your OS is natively not supported by them. Furthermore I do not recommend to nstall such program, which is permanently running in the background and drops your performance. If you join our Forum or Station-Drivers each week, you will get much earlier the informations about the newest drivers, even about those, which never will be published at the manufacturerâs download pages.
If I'm interpreting the file correctly, it's telling it to implement PCI_DRV using the machine.inf entries, so the actual driver will come from there - PCI.SYS ... now if it's already found that by generic id, it won't change anything except the name, but if it hasn't already selected PCI.SYS as the driver, it might improve things
EDIT by Fernando: Unneeded part of the fully quoted post removed (to save space within this thread)
@Lagoon : The Intel RST/RSTe drivers do support the Intel SATA Controllers, if they are running in AHCI or RAID mode, but have nothing to do with the USB devices. That is the reason why you got the message, that the Intel RST/RSTe drivers are not compatible.