@davidm71
ASMedia have many HW modifications and very sensitive to proper FW. If you have flashed wrong FW, then you are in trouble.
Anyway, nobody can aswer you for sure, because you didn’t notice the model of your mobo, do you using external card or onboard chip.
To recognize the real chip for 100%, making the real photo of your chip (and numbers+letters) is often necessary.
Then you may asking specialists for some very first help and advices. I guess…
I’m, personally, sure in ASMedia FW only for my own mobo (no any updates since 2013 and updating process is highly dangerous).
So, I’m updated the chip only once with 100% proper FW and forget about it. The version of my present driver pack is the same as yours (the most rescent version by Fernando).
That’s it.
@iWARR :
Well I went there and back again and now back on the stock firmware. Hopefully I won’t have another drive fail on me!
Would recommend others not take risky chances as I have. I was lucky I didn’t brick the controller. Came very close!
All well now I hope.
@100PIER :
If your using 150707_30_02_10 (I thought you were go back on stock).
iWarr Since you asked it was an MSI X99A Godlike motherboard with 1141 and 1041A controller.
I used LSPCI to identify the proper chipset. Though this review marks them as slightly different:
https://www.tweaktown.com/reviews/8378/m…iew/index4.html
Thanks.
@davidm71
On my ASUS SabertoothX99 machine the ASMedia component "ASM1242 USB3.1 Host Controller", identified as "PCI\VEN_1B21&DEV_1242&SUBSYS_0001103C&REV_00" is equipped with a Firmware which has been updated 3 times from the beginning.
Firmware history versions I used (from 2016):
141231_30_02_0D => 150707_30_02_00 => 150707_30_02_0C => 150702_30_02_10 (currently the last one).
@iWARR :
Thank you very much for your report and your interesting finds.
What do you suggest for me regarding the future offer of mod+signed v5 platform Intel USB 3.0/3.1 drivers?
Should I offer them with or without adding the natively not supported DEV_IE31 USB 3.0 Controllers (on-board of Intel 7-Series chipsets)?
Or should I offer 2 differently modded driver variants, that means
a) a special driverpack for users with an Intel 7-Series chipset system to be able to install the v5 platform Intel USB drivers and
b) a "normal driverpack for users with an Intel chipset from 8-Series up (without DEV_IE31 support)?
I think, we can try in slightly different way.
I beleive DEV_IE31 USB 3.0 Controllers (Intel 7-Series chipsets) have to work.
I think the main problem is wrong digital sign, not comptibility issue. The proof is my Win10 part of two tests I did.
I remember that previous packs worked on Z77 (> v5.0.1 or so). And mod should be universal for the 7 & 8 chipset series.
a) The first step. It is fixing digital sign only for the Intel(R) USB 3.0 eXtensible Host Controller (the rest is nice).
The mod pack should work on both Win8.1/Win10
b) The second step. We can think about providing 2 packs not for chipsets, but for OS (Win10 / Win8-7), because the main Win10 USB 3.0 driver may appear newer for Win10.
It’s not a big problem update it from MS repo, test, grab and and include into the Win10 pack "as is" (with MS cert). 2 (Win-RAID) +1 (MS).
Or just exclude Intel(R) USB 3.0 eXtensible Host Controller from the Win10 mod…
2+1 looks more handy, because Intel USB 3.0 drivers do not update too frequently.
But first, we must make sure what kind of problem we have: inproper Digital Sign or incopatibility. For now I think it’s the Digital Sign…
Can you think about how to fix it? (same as in IRST issue thread)
@davidm71
Another one advice. I don’t recommend to use ASMedia USB3 controller for SDD/HDD drives on regular basis (furthmore, always connected 24/7).
Of course, you can still use ASMedia ports for connecting flash devices, periphery, smartphones, charging, etc.
Better use Intel USB3 ports for the big-capacity SDD/HDD drives within sensitive / important information.
Intel USB3 ports much more stable and work faster also.
@iWarr,
This particular board lacks Intel Usb 3 ports so best I can hope for is using the safest firmware and driver available. All I run off those ports are either flash drives or large capacity external platter based backup pocket drives.
Thanks
I will try to do it, but I am not sure, whether I will succeed.
The problem seems to be, that the modern Windows Operation Systems prefer the MS in-box drivers.
It would only appear newer, if I would type a wrong date into INF file of my modded driverpack (the latest original Intel USB 3.0 driver is dated 05/11/2017).
By the way: It wouldn’t make much sense to offer a mod+signed Intel USB 3.0/3.1 driverpack v5.0.4.43, because all users with a modern Intel chipset from 8-Series up can use the original drivers.
If I remember right, when I installed v5.0.4.43 (11.05.2017, test version) on Win10 LTSB 2016 for the first time, a few monthes ago, your mod offered newer Hub Driver & Switch Driver for my Z77 mobo.
I’m doubting MS repo will offer smth. new for Z77 on Win10…
And I don’t know what about 8 series, I don’t have it.
Until “Intel(R) USB 3.0 eXtensible Host Controller” is not fixed, it have function errors on Win8.1 and Win10.
For example, on Win8.1 “Atomatic” update method changes this modded driver to the stock one, v3.0 0100 (MS), 09.04.2015, 6.3.9600.17797 which is too old…
The strage thing is that modded driver works somehow, but there are function (launch) errors in the logs time to time (probably it happens when boot to OS or changing the driver, i.e. activating it, but not during the session).
Probably, this concerned with event time of the reading wrong digital sign… I don’t know why, exactly…
Contrary to you I suspect, that your issue is chipset related (Intel 7-Series chipsets are natively not supported by the v5 platform Intel USB 3.0 drivers) and has nothing to with the Win-RAID CA signature.
If you should have access to any system with a newer Intel chipset, please test my latest mod+signed USB 3.0 drivers with such system.
@iWARR :
The latest Intel USB 3.0 drivers, which natively do support Intel 7-Series chipset on-board USB 3.0 Controllers, are the v1.0.10.55 ones dated. 09/17/2013.
The download links are within the start post of this thread.
Manual updating (w/o DPInst) of the Intel(R) USB 3.0 eXtensible Host Controller (iusb3xhc.inf) on Win8.1:
1) "Browse…" method says "no need to update"
2) "Have Disk…" method gives me a BSOD immediately (during update process).
Next reboot reverts the driver to stock MS (09.04.2015) - this stock driver is newer (no need to update, anyway).
So v1.0.10.55 is useless. I can install Hub Driver and Switch Driver from v5.0.4.43 mod package.
Summary (Z77 - Win10 & Win8.1):
1) Hub Driver and Switch Driver - v5.0.4.43 mod package
2) Intel(R) USB 3.0 eXtensible Host Controller - Stock MS driver or Windows Update (if proposed)
3) v1.0.10.55 mod package is absolutely useless.
Hi @rankoneads
I have PCI\VEN_8086&DEV_ a36d ( Cannon Lake PCH USB 3.1 xHCI Host Controller )
Have you already can install Win7 32bit?
Please help me because I am having difficulties to install Win 7 32bit
Thank you for your attention and cooperation
Regards,
Firman
Hello Fernando.
Thanks for offering the modded Intel USB 3.0 / 3.1 drivers.
Unfortunately I can not install the offered drivers.
My system:
Windows 10 PRO 64bit version 1803.
Motherboard Chipset: Intel HM175 (Skylake PCH-H)
Intel(R) USB 3.0 eXtensible-Hostcontroller – 1.0 (Microsoft)
Hardware-IDs:
PCI\VEN_8086&DEV_A12F&SUBSYS_850A1558&REV_31
PCI\VEN_8086&DEV_A12F&SUBSYS_850A1558
PCI\VEN_8086&DEV_A12F&CC_0C0330
PCI\VEN_8086&DEV_A12F&CC_0C03
Many thanks for your help.
@Colossus :
Welcome to the Win-RAID Forum!
What does this mean? What have you done and what happened?
The DeviceID DEV_A12F is natively supported by the original driver. So you should be able to get the mod+signed drivers installed, but maybe you have to force the installation by using the “Have Disk” option.
Regards
Dieter (alias Fernando)
Thank you for the fast feedback,
with DPInst64.exe I could not install the driver.
After adding the Win-RAID CA Certificate, the installation worked.
Unfortunately I have read over, that only the certificate must be installed.
Please excuse my mistake.
The problem seems to be, that the modern Windows Operation Systems prefer the MS in-box drivers
It would only appear newer, if I would type a wrong date into INF file of my modded driverpack (the latest original Intel USB 3.0 driver is dated 05/11/2017)
I’m going for this because should be the solution for that the Intel drivers are not easily replaced like now.
The Intel "PCI bus" driver is not replaced because the inbox driver is older than it (11/05/2017 > 21/06/2006).
The "Intel(R) USB 3.0 eXtensible Host Controller" driver is replaced because it’s driver date is older than the inbox one (11/05/2017 < 10/04/2018).
The "Intel(R) USB 3.0 Root Hub" driver although is older than the inbox driver (11/05/2017 < 02/08/2018) is not replaced because the "Intel(R) USB 3.0 eXtensible Host Controller" driver exposes a different DeviceID for it than the inbox driver (IUSB3\ROOT_HUB30 vs USB\ROOT_HUB30), so do not match when update, leaving it alone:
I think will be good to change ONLY the DATE of the "Intel(R) USB 3.0 eXtensible Host Controller" driver to prevent a windows update replace it.
Change a byte do the trick (11/05/2017 < 11/05/2018 or 11/05/2019) so I think is not a so agresive change. Please @Fernando change the date, maybe you can offer 2 versions, the normal and a updated one, or only offer the updated one here in the thread and not in the first/original post… And surely you want to warning the users that the driver date is changed.