I cannot help you regarding your Renesas USB 3.0 problems. To find out, if there is any negative impact between the USB 3.0 and SATA connected drives, I recommend to do some SSD benchmark comparison tests with enabled and disabled USB 3.0 Controller.
I also have similar PC specs to you and I would like some clarification on the "SWITCH" issue before I try these modified drivers.
Past posts in this thread suggest that System Devices ā> PCI Express Root Complex with a Hardware ID - ACPI\PNP0A08 is the switch mentioned. ( but no confirmation was ever provided by user Jest )
Research on the web says - Technically, the iusb3hcs driver (switch) is installed as a device lower filter of the PCI bus device. The filter driverās goal is to initialize the Intel-specific XUSB2PR register during PCI bus startup. This register allows per-port configuration, to either direct it to the XHCI (USB 3.0) or EHCI (USB 2.0) controller. If the filter driver is not installed, the default configuration will apply: all ports would be directed to USB 2.0.
So my question is should I install this switch driver on the PCI Express Root Complex? The currently loaded driver details for the PCI Express Root Complex is - pci.sys
I think, that these pictures verify, that it is really the device named "PCI Express Root Complex", which is supported by the Intel USB 3.0 Switch driver named iusb3hcs.sys:
Update: I just have tested it myself by installing all 3 (Controller/Hub/Switch) mod+signed USB 3.0 drivers v4.0.4.51 onto my Z97 system running Win10 x64. Everything worked flawlessly. After having successfully updated the driver for the device named "PCI Express Root Complex" by choosing the Intel USB 3.0 Switch Driver the device had been renamed to "PCI bus" and showed these driver informations:
I have just updated all the drivers (Controller/Hub/Switch) which includes the "PCI Express Root Complex" and can report everything is working correctly.
After the "PCI Express Root Complex" is updated it does indeed say "PCI Bus".
On my z77, i7 2600k I can also report that the problem the other posters were having with the computer waking from sleep and the Intel USB 3.0 ports not working and anything connected to them going to Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26 at usb 2.0 speeds is also fixed.
I can not thank you enough for your help and your excellent modded drivers!
Great work ā¦ shame that Microsoft and there drivers are not as reliable!
@all: Due to my recent findings regarding the exact procedure how to update the Intel USB 3.0 "Switch Driver", I have just updated the related part of the start post.
I mean no disrespect with this post, and Iām thankful to everyone involved for making the possibility of using Intel drivers on Windows 8(+) a reality (Iāve always been curious), but I have chosen to stick with the Microsoft XHCI drivers on my 64-bit Windows 10 laptop with a 7-Series chipset because:
VMware has trouble capturing host USB devices with the Intel driver. If I plug in my external Seagate device, everything works fine on the host, but attaching it to my Windows 10 VMware guest fails - the guest Windows brings up the āUSB device has malfunctioned messageā.
The Intel drivers cannot use Microsoftās UASP driver included with Windows 8 onwards. If I attach an external enclosure with UASP support with the Microsoft drivers, under Storage controllers, I get a device showing with the name of āUSB Attached SCSI (UAS) Mass Storage Deviceā, using Microsoftās uaspstor.sys. With the Intel drivers, the same drive shows up in Universal Serial Bus controllers as a bog-standard āUSB Mass Storage Deviceā, using USBSTOR.sys
Iāve installed these drivers multiple times now (restarting after installing both the controller and hub drivers), the latest attempt taking into account the PCI bus discovery but the first issue I have been able to successfully replicate each and every time. The second issue Iāve only checked for on my latest try but I do not expect that to change with further attempts should I choose to try the Intel driver again. Again, thanks to everyone involved - Iām glad forums like this exist where I can discover new improvements to be made to my laptop (and Iāve installed far more reliable drivers thanks to this site).
new: pure 32/64bit ASMedia USB 3.0+3.1 Drivers v1.16.34.2 WHQL for Win10 dated 03/22/2016
Thanks to Pacman resp. Station-Drivers for having published the source package. By the way: I have just installed the new 64bit ASMedia USB 3.0 drivers onto my Z97 system. Everything seems to run fine.
Good luck with the new ASMedia USB 3.0/3.1 drivers! Dieter (alias Fernando)
My laptop from 2012 is running Windows 8.0 core. And from what I think I understand, looking in Device Manager, itās mainly using the Microsoft drivers to run the USB 3.0 ports and hubs. Though some device titles say " Intel eXtensible 3.0 bla bla".
I like to install the latest Intel 3.0 xhci drivers to see if it fixes problems with my external USB enclosures
The Problem: No SMART data can be read/modified through this enclosure. Though some devices connected to this same 3.0 port are SMART enabled and show no problem with Smartmontools. Itās just this enclosure with the Asmedia 1153E bridge/chipset in it that cannot be SMART controlled.
Am I in the right place? And which drivers do I need? - My laptop has Intel 7-series chipset.
The related USB 3.0 devices are manufactured by Intel, but natively not supported by the Intel USB 3.0 drivers while running Win8/8.1/10.
The installation of the modded Intel USB 3.0 drivers will be difficult, if you donāt have alternative connection ports for your keyboard and mouse.
I am not sure, whether the installation of the Intel USB 3.0 drivers will solve this problem. Have you ever tried the free tool named CrystalDiskInfo (look >here<)?
I have tried accessing the SMART data through various software like hddscan. It shows nothing just an error for disks in this enclosure. But will try crystalsiskinfo tonight.
What could be the problem do yo have any ideas for me to investigate?
All devices connected to the same usb3.0 port will show SMART data. They also show /dev/sda-z format assignment when I run āsmartctl --scanā to detect all ATA devices connected to my system. But only the enclosure will show up as /dev/csmi0,0 (which indicates It is the only device behind a intel driver?)- Could this be a clue?
EDIT: I found out /dev/csmi0,0 isnāt even a designation for a drive. But in that case smartctl --scan does not show this enclosure at all. Under windows explorer it does show. Under disk management as well. Usb3.0 speeds are up to par (90-190mb/s to and from this disk). Under device manager it shows under a āmass storage controllerā label. Could it be this mass storage driver is not working with this device peoperly and not passing sata commands correctly? Can I try another mass storage controller driver. If yes which one? Is this directly related to AHCI should I uninstall this ?
I am trying to install Intel USB 3.0 Drivers v4.0.4.51 MOD on Windows 10 x64 running on a 7-series chipset with USB 3.0 ports. I installed the certificate then installed the modded drivers. The USB 3.0 disk worked at full speed. After a reboot, the USB disk wonāt show up in the explorer but the modded (and signed by WinRaid-RSA) controller and Hub are both still installed.
If I reboot with Driver Signature Enforcement DISABLED, it works again.
What can I do to have USB 3.0 persist after a reboot?
I suspect, that you havenāt imported the Win-RAID CA Certificate correctly. Please redo the procedure. What about the āUSB Switch Driverā? Did you install it as well?
Thank you for the reply. I used the .bat to install the certificate and the re-install said the certificate was already installed. Here is my output from running it a second time. I edited out some fields.
I replaced the USB Switch Driver and rebooted, but the USB 3.0 ports are still not working. They are supplying power just not transferring data. The drive's power light is flashing and is not detected, it should be solid when connected correctly. After re-disabling driving signing, everything works again.
EDIT by Fernando: Put the Certificate code into a spoiler and removed unneeded parts of the fully quoted post (to save space)