Thank you, I will investigate further when I have more free time. It is interesting that the previous driver I had (ASMedia USB 3.0 Drivers v1.16.26.1 WHQL) appears as signed everywhere.
EDIT: Just as I suspected, they left something out of the signature. This is the old one:
D:\Download\Sigcheck\asmtxhci.cat HWID1: usb\asmediausbd_hub HWID2: usb\asmediausbd_hub&vid_040e&pid_0100 HWID3: pci\ven_1b21&dev_1040&rev_00 HWID4: pci\ven_1b21&dev_1040&rev_01 HWID5: pci\ven_1b21&dev_1040&rev_02 HWID6: pci\ven_1b21&dev_1041&rev_00 HWID7: pci\ven_1b21&dev_1041&rev_01 HWID8: pci\ven_1b21&dev_1041&rev_02 HWID9: pci\ven_1b21&dev_1042&rev_00 HWID10: pci\ven_1b21&dev_1042&rev_01 HWID11: pci\ven_1b21&dev_1042&rev_02 HWID12: pci\ven_1b21&dev_1142&rev_00 HWID13: pci\ven_1b21&dev_1240&rev_00 HWID14: pci\ven_1b21&dev_1241&rev_00 HWID15: pci\ven_1b21&dev_1242&rev_00 HWID16: pci\ven_1b21&dev_1042&subsys_84881043&rev_00 HWID17: pci\ven_1b21&dev_1042&subsys_84881043&rev_01 HWID18: pci\ven_1b21&dev_1042&subsys_84881043&rev_02 HWID19: pci\ven_1b21&dev_1142&subsys_85bf1043&rev_00 OS: 2000,XPX86,XPX64,VistaX86,VistaX64,7X86,7X64,Server2008R2X64,8X86,8X64,_v63,_v63_X64,_v63_Server_X64 Submission ID: 1734379 DTC: 1 Qualification Level: 5000 OS Attributes: 2:5.00 Windows XP Windows Vista/Windows Server 2008 Windows 7/Windows Server 2008 R2 Windows 8/Windows Server 2012 Windows 8.1/Windows Server 2012 R2 File: asmtxhci.sys Algorithm: sha1NoSign Hash: E4C2D4F66D033F8039803DA82885ED501A60EF70 OS Attributes: Windows XP Windows Server 2003 Windows Vista/Windows Server 2008 Windows 7/Windows Server 2008 R2 Windows 8/Windows Server 2012 Windows 8.1/Windows Server 2012 R2 File: asmtxhci.sys Algorithm: sha1NoSign Hash: B00E2845EED771515DE2C03F7B0DCC982BBB3C71 OS Attributes: 2:5.00 Windows XP Windows Server 2003 Windows Vista/Windows Server 2008 Windows 7/Windows Server 2008 R2 Windows 8/Windows Server 2012 Windows 8.1/Windows Server 2012 R2 File: asmtxhci.inf Algorithm: sha1NoSign Hash: 93D6D259B9764B75E149F2603BA2E50070AAEAE3
First of all: Thanks to all of the people who make this place happen :). Really glad to have found this resource
I have an Aorus X7 Pro-SYNC laptop (w 5th Intel CPU).
It has 3 USB 3.0 ports.
One of them runs at USB 2.0 speeds no matter what I do. Another functions normally at normal speeds. The last one has normal 3.0 speed write but, USB 2.0 read speed.
So I downloaded and installed the modded Intel 3.0 drivers .
I get the following errors under the Intel(R) USB 3.0 eXtensible Host Controller entry (via USB Tree View):
===================== USB Host Controller =======================
+++++++++++++++++ Device Information ++++++++++++++++++ Device Description : Intel(R) USB 3.0 eXtensible Host Controller Device ID : PCI\VEN_8086&DEV_8CB1&SUBSYS_17591458&REV_00\3&11583659&0&A0 Vendor : Intel Driver KeyName : {36fc9e60-c465-11cf-8056-444553540000}\0000 (GUID_DEVCLASS_USB) Driver : C:\WINDOWS\System32\drivers\iusb3xhc.sys (Version: 4.0.2.42 Date: 2015-09-25) Driver Inf : C:\WINDOWS\inf\oem46.inf Legacy BusType : PCIBus Class : USB Service : iusb3xhc Enumerator : PCI Location Info : PCI bus 0, device 20, function 0 Manufacturer Info : Intel(R) Corporation Capabilities : 0x00 (-) Problem Code : 0 Power State : D0 (supported: D0, D3, wake from D0) Child Device 1 : Intel(R) USB 3.0 Root Hub Device ID : IUSB3\ROOT_HUB30\4&5D1BBCE&0 Class : USB
HcInfo0 Error : ERROR_INVALID_FUNCTION
Roothub Symbolic Link : IUSB3#ROOT_HUB30#4&5d1bbce&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
BusStatistics Error : ERROR_INVALID_FUNCTION
DriverVersion Error : ERROR_INVALID_FUNCTION
BandwidthInfo Error : ERROR_INVALID_FUNCTION
PowerInfo Error : ERROR_INVALID_FUNCTION
This is on a clean install of Windows 10. Also tried it with Windows 8.1. Same results.
Also, uninstalling the modded drivers and rolling back to the stock microsoft ones, I get the following error viewing the 'USB Root Hub' entry below Intel(R) USB 3.0 eXtensible Host Controller:
========================= USB Root Hub =========================
+++++++++++++++++ Device Information ++++++++++++++++++ Device Description : USB Root Hub (xHCI) Device Path : \\.\USB#ROOT_HUB30#4&5d1bbce&1&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} Device ID : USB\ROOT_HUB30\4&5D1BBCE&1&0 Driver KeyName : {36fc9e60-c465-11cf-8056-444553540000}\0005 (GUID_DEVCLASS_USB) Driver : C:\WINDOWS\System32\drivers\UsbHub3.sys (Version: 6.3.9600.16384 Date: 2013-08-22) Driver Inf : C:\WINDOWS\inf\usbhub3.inf Legacy BusType : PNPBus Class : USB Service : USBHUB3 Enumerator : USB Location Info : - Manufacturer Info : (Standard USB HUBs) Capabilities : 0x80 (SurpriseRemovalOK) Address : 0 Problem Code : 0 Power State : D0 (supported: D0, D2, D3, wake from D0, wake from D2) Child Device 1 : USB Composite Device Device ID : USB\VID_046D&PID_C521\5&32D5A86C&0&9 Class : USB
------------------- USB Hub Descriptor ----------------- bDescriptorLength : 0x09 (9 bytes) bDescriptorType : 0x29 (Hub Descriptor) bNumberOfPorts : 0x15 (21 Ports) wHubCharacteristics : 0x0000 Power switching : Ganged Compound device : No Over-current protection : Global TT Think Time : At most 8 FS bit times Port Indicators : Not supported bPowerOnToPowerGood : 0x02 (4 ms) bHubControlCurrent : 0x00 (0 mA) !*ERROR Descriptor too short: PortPwrCtrlMask needs 3 bytes to hold 21 bits HubIsBusPowered : 0x00 (Self Powered)
-------------- Extended USB Hub Descriptor ------------- HubType : USB Root Hub HighestPortNumber : 21
----------------- USB Hub Capabilities ---------------- HighSpeedCapable : No HighSpeed : Yes MultiTtCapable : No HubIsMultiTt : No ArmedWakeOnConnect : No IsBusPowered : No IsRoot : Yes
Notice the error message at line 37:
1 2
bHubControlCurrent : 0x00 (0 mA) *!*ERROR Descriptor too short: PortPwrCtrlMask needs 3 bytes to hold 21 bits
The speed issues still remain. Seems to be related to some kind of power setting? I can rule out the registry because this happens on clean Windows 7/8.1/10 installs
If someone could help me figure this issue out I would be so thankful! Cheers
I firstly want to thank Fernando and all the others who use their time to solve those problems that manufacturers should fix, your work is AWESOME.
Said this, I have a mini-PC that has an Intel USB 3.0 port, this port works with USB 2.0 devices but not with USB 3.0 such as hard disks (I have the typical “USB error” and in device manager appears a line named “not recognized USB device” with the warning signal on the icon.). I’ve follow the Fernando steps, and those steps are magistrally explained, so there is no place for user error, I’ve reinstall OS and problem remains, so I explain my case:
The controlled is calle something like “eXtensible host controller Intel(R) Usb 3.0 - 1.0 (Microsoft)” and its ID is one of the specified on the list of Fernando (DEV_22B5&CC_0C03).
What have I done:
-Of course, nothing connected to USB 3.0 connector during all the process. -Since I use a 64bit Windows 10 I’ve download “64bit Intel USB 3.0 Drivers v4.0.2.42 mod+signed by Fernando< (>MIRROR<)” and extract files. -Import the Win-RAID CA certificate into my system following the guide (apparently everything goes ok). -Go into “eXtensible host controller Intel(R) Usb 3.0 - 1.0 (Microsoft)” properties and navigate to “driver” “update driver” “look for the driver in the computer”, then choose second option “Choose from a list of controller in my computer”, then navigate to the folder “Controller driver - as first” and select “iusb3xhc”. -Now it apparently goes ok and system ask me if I want to trust on the driver, but… -The problem comes now, in this moment computer gets frozen or I have a bsod with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL (USBXHCI.SYS). -No matter if system hangs or show error, when I reset I have the same microsoft driver and I have nothing to do :(.
I’ve restore system to a point before doing anything related to the drivers, run Windows update, try firstly to update device with right click, update… nothing works and the fact is that I’ve check the Fernando’s steps several times.
The BSOD has nothing to do with my "mod+signed" Intel USB 3.0 driver. As first step I recommend to check the integrity of your system files by running the Command Prompt as Admin and entering the following command:
1
sfc /scannow
Maybe the OS own MS USB 3.0 driver named USBXHCI.SYS is corrupt and needs to be repaired. If you should get the message, that some system files could not be repaired, I recommend to insert the Win10 installation media and to enter the following command into the Command Prompt
I’ve completely format internal eMMC (hard drive) and install an original windows 10 x64. The result is very close to the one I had with the OS that came with the device. Now I have no BSODs, but when computer installs new driver -step one- it shows a windows telling the driver has been correctly installed, but computer gets completely frozen in this moment.
After restart the Microsoft driver is installed again, so there is nothing to do. I have also try to remove device and apparently it does, but also froze the computer, and again, when restart the microsoft driver is restored.
I truly had hope on installing a new Windows 10 (original new licence moved from the DVD to a USB drive), but the problem remains. It can’t be a system files issue, since it is a new OS freshly installed.
Concerning the ASMedia ASM104x-ASM114x driver v1.16.29.1, I might be wrong, don’t take my word for it, but a quick check makes me think the driver is only for Win10. Method : files size comparison with full 1.16.28.1 just above and to be more serious Sigcheck -a
For the ASMedia ASM104x-ASM114x “Drivers and Software Set” v1.16.28.1, I think it would be better to put a complete package (ie. setup, readme + INF, SYS, CAT) like this one https://mega.nz/#!gMI3HDxD!FF4xGHtZ_BrrK…w1hFTWkmErF1ksQ
It may be possible, but would be very strange, because the OS compatibility is usually well-defined within the related INf file and the INF files of both v1.16.28.1 drivers seem to be identical. Nevertheless I changed the text regarding the OS compatibility of the latest ASMedia USB 3.0/3.1 drivers within the start post.
Before I risk having to re-customize all these ASMedia USB 3.0/3.1 driverpacks again, I will wait until I get feedback from the users.
@ all: Here are some additional finds regarding the ASMedia USB 3.0 drivers:
Yesterday I have installed the "Asmedia USB 3.0+3.1 Drivers & Software Set v1.16.28.1 WHQL", which I am offering within the start post, onto my Z97 system by running the installer (just for testing purposes, I usually prefer to install the "pure" driver manually). Although the package doesn’t contain any separate driver folder (like your package), the installation completed successfully. This verifies, that all required driver files are in compressed form within the Setup.exe file. That was the reason why I had removed both driver folders from the Installer package.
Today I wanted to uninstall the ASMedia USB 3.0 Drivers v1.16.28.1 from within the Control Panel by using the "Add/remove Software" option. The procedure failed at 2/3 of its way with a freezing of my computer - nothing worked, but I saw heavy SSD/RAM activity. I waited 10 minutes and then turned off the computer. After having restarted it, everything seemed to be fine again. Even the ASMedia USB 3.0 ports were working fine again by using the generic MS USB 3.0 drivers, but the Control Panel still showed the "Asmedia USB Host Controller Driver" as being installed. A second try to get rid of it failed again. My conclusion: These drivers are installable via installer, but the installer itself is not completely removable.
.By “only for” I was talking of the WHQL digital signature, at the very least. Thus DSEO or changing cat needed on other platforms.
.If you check the v1.16.28.1 aforementionned, you will see that there are 2 folders, one for Win10, one for the other Windows version. This has been the case since there’s Win10 drivers. Also apply to ASM106x from the same company. Ok, .SYS files between driver/driver_win10 are not very different if you strip the digital signature at the end (4 bytes actually), but one can wonder why “they” take the pain to create a double folder install if it’s not needed (Occam’s razor, this sort of thing).
.Concerning the need of the separate driver folders, no it is not required, I was only suggesting to make either : .one package (setup + driver v1.16.28.1) and another package (driver only v1.16.29.1) .one package (setup v1.16.28.1), another package (driver only v1.16.28.1) and another package (driver only v1.16.29.1)
.I don’t see the need to mod ASMedia drivers. Can you explain what you intend to do ?
Attached : sigcheck results (zipped), which are pretty clear, I think.
In short, whether it’s with the setup.exe ("Drivers and Software Set" sounds like a shortcut for "install/setup.exe and ‘Have Disk’ method", plus that’s how ASMedia package them), or in a separate package, v1.16.28.1 .inf+.cat+.sys (‘Have Disk’ method) have to be available, in some way. Hence the 2 suggestions of packaging. You decide. Hey, it’s your forum, after all.
Sorry, misunderstanding on my part, in
I understood re-customizing with modding, my bad.
I’ve edited my post with a .zip file of sigcheck results.
Doesn’t seem to work on my system: asrock z87 extreme6 4770k win 10 using intel 3.0 modded x64
After I install the controller driver for the highlighted device, and I install the hub driver, my usb devices are not working and causes my pc to crash.
After having installed the driver for the Intel USB 3.0 Controller you have to reboot. After having done that you can install the driver for the Intel USB 3.0 Hub Devices. Reason: Although the Controller drivers have been sucessfully installed, they are not in use until the next reboot.
Questions: 1. Has the update of the Intel USB 3.0 Controller driver been successful? 2. Did you see any devices with a yellow flag within the Device Manager after the reboot? 3. Are you sure, that you updated the correct (Intel related) USB 3.0 Hub Devices?
