Forum - RE: USB 3.0/3.1 Drivers (original and modded)

#1216 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 7:17 am

I have a EVGA Z97 board with Win 10 Pro x64 (Creator's Update) and am trying to install the "pure" modded 64bit Intel USB 3.0/3.1 Drivers v5.0.4.43. I've tried the DPInst option, but when I run it I get "Install Failed" for all three components. And if I try to manually update the drivers for the Intel USB 3.0 eXtensible Host Controller with iusb3xhc.inf I get the message that "Windows encountered a problem installing the drivers for your device". Any suggestions?

reply

#1217 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 10:08 am

@fragilityV1:
Welcome to the Win-RAID Forum!
Please post the HardwareIDs of your on-board Intel USB 3.0 Controller.
Regards
Dieter (alias Fernando)

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1218 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 4:58 pm

For The Device labeled Intel USB 3.0 eXtensible Host Controller I get the Hardware Ids:

PCI\VEN_8086&DEV_8CB1&SUBSYS_103B3842&REV_00
PCI\VEN_8086&DEV_8CB1&SUBSYS_103B3842
PCI\VEN_8086&DEV_8CB1&CC_0C0330
PCI\VEN_8086&DEV_8CB1&CC_0C03

reply

#1219 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 5:40 pm

@fragilityV1:
Thanks for the HardwareIDs.
The only DEV_8CB1 Intel USB 3.0 Controller, which is natively supported by the Intel USB 3.0 drivers v5.0.4.43, has the the DeviceID DEV_8CB1&REV_00 (that means without any SUBSYS_ID).
So I suspect, that you cannot use this driver.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1220 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 8:09 pm

Ahh, oh well. Thanks for checking.

reply

#1221 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Fri Aug 25, 2017 9:32 pm (Last edited: Fri Aug 25, 2017 10:14 pm)

Fernando, re ASMedia USB 3.0/3.1 Drivers, Due to problems with the previous asus motherboard, I cannot guarantee my test results in post no 1177. I now have a gigabyte board and will rerun them and re post/update the results in #1177 by the end of next week. Sorry for any inconvinience to you and other users. :)

reply

#1222 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Sun Aug 27, 2017 5:33 am (Last edited: Sun Aug 27, 2017 11:31 am)

Alright Dieter... I'm having the same issue as several other folks. Windows 10 Pro x64 1703, fresh install on an Asus Z170 motherboard. I installed the Win-RAID CA cert in all the certificate stores that are circled in the attached MMC screenshot below and rebooted the system prior to attempting any driver installs. I hash-checked the old Win-RAID cert I installed several months ago with the one in your latest Intel .zip file, and they're exactly the same.

The drivers refuse to install via the Update Driver wizard from the Device Manager. A screenshot of the error message is attached below.

The drivers will install via DPInst64.exe. HOWEVER, if you install them that way, that's when the real fun begins. After a reboot, Windows doesn't load and instead goes straight into its Automatic Repair routine. Automatic Repair finds nothing actionable, and essentially what you're left with is a dead stick of a computer. Windows will not load again until Secure Boot is disabled. After Secure Boot is disabled, Windows loads perfectly fine, and the modded drivers also work perfectly fine, but Secure Boot is essentially busted from that point on until the drivers are removed.

I've tried installing the drivers with Secure Boot disabled and nointegritychecks on, but as soon as I re-enable Secure Boot, Windows refuses to load.

setupapi.dev.log outputs the following when attempting to install the XHCI controller driver via the Update Driver Wizard (not DPInst64.exe):

>>> [Device Install (DiShowUpdateDevice) - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0]
>>> Section start 2017/08/26 14:52:09.363
cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 14:52:09.363
dvi: Default installer: Enter 14:52:09.363
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 14:52:09.378
ndv: {Update Driver Software Wizard - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: {DIF_SELECTDEVICE} 14:52:19.536
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:19.536
dvi: {DIF_SELECTDEVICE} 14:52:44.654
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:44.654
sto: {Setup Import Driver Package: <***REDACTED***>\iusb3xhc.inf} 14:52:51.436
inf: Provider: Intel(R) Corporation
inf: Class GUID: {36FC9E60-C465-11CF-8056-444553540000}
inf: Driver Version: 05/11/2017,5.0.4.43
inf: Catalog File: iusb3xhc.cat
sto: {Copy Driver Package: <***REDACTED***>\iusb3xhc.inf} 14:52:51.452
sto: Driver Package = <***REDACTED***>\iusb3xhc.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}
sto: Copying driver package files to 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}'.
flq: Copying '<***REDACTED***>\iusb3xhc.cat' to 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.cat'.
flq: Copying '<***REDACTED***>\iusb3xhc.inf' to 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf'.
flq: Copying '<***REDACTED***>\iusb3xhc.sys' to 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sys'.
sto: {Copy Driver Package: exit(0x00000000)} 14:52:51.624
pol: {Driver package policy check} 14:52:51.624
pol: {Driver package policy check - exit(0x00000000)} 14:52:51.624
sto: {Stage Driver Package: C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.624
inf: {Query Configurability: C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.671
inf: Driver package 'iusb3xhc.inf' is configurable.
inf: {Query Configurability: exit(0x00000000)} 14:52:51.671
flq: Copying 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.cat' to 'C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat'.
flq: Copying 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf' to 'C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf'.
flq: Copying 'C:\Users\<***REDACTED***>\AppData\Local\Temp\{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sys' to 'C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.sys'.
sto: {DRIVERSTORE IMPORT VALIDATE} 14:52:51.686
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.686
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:52:51.702
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.702
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:52:51.702
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 14:52:51.702
sig: Signer Score = 0x0F000000
sig: Signer Name = Win-RAID CA
sto: {DRIVERSTORE IMPORT BEGIN} 14:52:51.702
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 14:52:51.702
cpy: {Copy Directory: C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}} 14:52:51.702
cpy: Target Path = C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5
cpy: {Copy Directory: exit(0x00000000)} 14:52:51.718
idb: {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Created driver package object 'iusb3xhc.inf_amd64_448d1c959f5d15e5' in SYSTEM database node.
idb: Created driver INF file object 'oem15.inf' in SYSTEM database node.
idb: Registered driver package 'iusb3xhc.inf_amd64_448d1c959f5d15e5' with 'oem15.inf'.
idb: {Register Driver Package: exit(0x00000000)} 14:52:51.718
idb: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Activating driver package 'iusb3xhc.inf_amd64_448d1c959f5d15e5'.
cpy: Published 'iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf' to 'oem15.inf'.
idb: Indexed 40 device IDs for 'iusb3xhc.inf_amd64_448d1c959f5d15e5'.
sto: Flushed driver database node 'SYSTEM'. Time = 16 ms
idb: {Publish Driver Package: exit(0x00000000)} 14:52:51.733
sto: {DRIVERSTORE IMPORT END} 14:52:51.733
dvi: Flushed all driver package files to disk. Time = 0 ms
sig: Installed catalog 'iusb3xhc.cat' as 'oem15.cat'.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 14:52:51.749
sto: {Stage Driver Package: exit(0x00000000)} 14:52:51.749
sto: {Setup Import Driver Package - exit (0x00000000)} 14:52:51.749
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Plug and Play Service: Device Install for PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: Driver INF Path: C:\Windows\INF\oem15.inf
dvi: Driver Node Name: iusb3xhc.inf:f8231471b5248d3d:IUsb3XhcModel:5.0.4.43:pci\ven_8086&dev_a12f&rev_31,
dvi: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Core Device Install} 14:52:51.780
dvi: {Install Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
dvi: {Configure Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
sto: {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf}
sto: Source Filter = pci\ven_8086&dev_a12f&rev_31
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Class Options = Configurable BootCritical
inf: {Configure Driver: Intel(R) USB 3.0 eXtensible Host Controller}
inf: Section Name = IUsb3XhcModel
inf: {Add Service: iusb3xhc}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\iusb3xhc.sys
inf: Display Name = Intel(R) USB 3.0 eXtensible Host Controller Driver
inf: Group = Base
inf: Created new service 'iusb3xhc'.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = PCI\VEN_8086&DEV_A12F&REV_31
inf: {Configure Driver Configuration: IUsb3XhcModel}
inf: Service Name = iusb3xhc
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Copying 'C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.sys' to 'C:\Windows\System32\drivers\iusb3xhc.sys'.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
dvi: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (oem15.inf:pci\ven_8086&dev_a12f&rev_31,IUsb3XhcModel). 14:52:51.796
dvi: Install Device: Configuring device completed. 14:52:51.796
dvi: {Restarting Devices} 14:52:51.796
dvi: Query-remove: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
dvi: Restart: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
! dvi: Device 'PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0' required reboot: Device has problem: 0x34 (CM_PROB_UNSIGNED_DRIVER), problem status: 0xc0000428.
dvi: {Restarting Devices exit} 14:52:53.594
dvi: {Configure Device - exit(0x00000000)} 14:52:53.594
dvi: {Install Device - exit(0x00000000)} 14:52:53.611
dvi: {Core Device Install - exit(0x00000000)} 14:52:53.611
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Install Related Drivers} 14:52:53.619
ndv: {Install Related Drivers: exit(0x00000000)} 14:52:53.625
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 14:52:53.638
dvi: Default installer: Enter 14:52:53.640
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 14:52:53.643
ndv: {Update Driver Software Wizard exit(00000000)}
<<< Section end 2017/08/26 14:54:46.535
<<< [Exit status: SUCCESS]

The juiciest part of which appears to be this:

sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.686
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:52:51.702
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.702
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:52:51.702

There is no certification "path" for the certificate you used to sign these drivers, so I'm not sure why it's saying this. I tried adding the three timestamping countersignatures from Thawte and Symantec to the necessary stores just for fun, but this had no effect.

What's very interesting, though, is that I CAN install version 5.0.1.38 of your modded drivers without any issues, whatsoever. I'll try installing some newer ones that precede 5.0.4.43 and see where the problem lies exactly.

I believe that either something has changed with 1703 as it pertains to Secure Boot and/or driver signing, or there's something going on with the drivers themselves past a certain version. Are you open to such possibilities? Did you upgrade to 1703, or do a fresh install like the folks (myself included) who are having this issue?

I know you've stated multiple times now that you're able to install the drivers fine on 1703, but there also multiple, dissociated reports of people who cannot, and the symptoms are strikingly similar amongst the different people who have reported difficulties with these drivers and 1703.
Take a look at this.... https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/

Looks and sounds familiar, doesn't it??? How about this?
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/1e34a9e4-5520-43a4-8fe0-f68458db2fff/windows-10-creators-update-device-driver-issue?forum=wdk

Could really use some help here.. I'll help you however I can, but first, it'd probably be constructive if you'd be kind enough to concede that there may actually be a problem here.

EDIT by Fernando: Screenshots resized and re-inserted as attachments (can be enlarged by clicking onto them), added a spoiler and removed unneeded blank lines (to save space)

reply

#1223 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Sun Aug 27, 2017 5:58 am (Last edited: Sun Aug 27, 2017 6:17 am)

Hey there.. Looks like you're only hosting version 5.0.4.43 of the modded Intel drivers. Is there some place where I can download the other ones you've released since 5.0.1.38? Thanks

reply

#1224 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Sun Aug 27, 2017 11:53 am

Zitat von cousinit99 im Beitrag #1220
The drivers will install via DPInst64.exe. HOWEVER, if you install them that way, that's when the real fun begins. After a reboot, Windows doesn't load and instead goes straight into its Automatic Repair routine. Automatic Repair finds nothing actionable, and essentially what you're left with is a dead stick of a computer. Windows will not load again until Secure Boot is disabled. After Secure Boot is disabled, Windows loads perfectly fine, and the modded drivers also work perfectly fine, but Secure Boot is essentially busted from that point on until the drivers are removed.

Thanks for your detailed report, which verifies,
a) that the Intel USB 3.0 drivers v5.0.4.43 mod+signed have been correctly digitally signed by me and can be properly installed even while running Win10 v1703 and
b) that it is the "Secure Boot" option, which prevents booting into Win10 v1703, when there are any drivers installed, which haven't been "correctly digitally signed" according to the Win10 v1703 Device Management,

Zitat von cousinit99 im Beitrag #1221
Looks like you're only hosting version 5.0.4.43 of the modded Intel drivers. Is there some place where I can download the other ones you've released since 5.0.1.38?

No, but I will attach such driver, if you tell me which version you want to test.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1225 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Sun Aug 27, 2017 9:54 pm

If you would please, I need all the modded versions you've released after 5.0.1.38, but prior to 5.0.4.43. I don't know how many there are or what the version numbers are. 5.0.1.38 is the last version I downloaded several months ago, so I don't know what versions were released after that.

Zitat
b) that it is the "Secure Boot" option, which prevents booting into Win10 v1703, when there are any drivers installed, which haven't been "correctly digitally signed" according to the Win10 v1703 Device Management,

Yes, that's how it appears, but in a a lot of ways, that makes absolutely no sense. Don't you agree? If 5.0.4.43 and 5.0.1.38 are signed exactly the same way, and 5.0.1.38 installs without issue, then why does only 5.0.4.43 trip Secure Boot? Why doesn't 5.0.1.38 trip it as well?? What does "correctly digitally signed" mean exactly, according to Windows? This doesn't make any sense. There must be something we're missing here.......

reply

#1226 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Sun Aug 27, 2017 10:33 pm

@cousinit99:
Attached is the 64bit DPInst Set with Intel USB 3.0+3.1 Drivers v5.0.3.42 mod+signed by me at 04/19/2017.
Unfortunately I have deleted the previously offered mod+signed Intel USB 3.0 drivers.

Fernando has attached files to this post

64bit DPInst Set with Intel USB 3.0+3.1 Drivers v5.0.3.42 mod+signed by Fernando.rar

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1227 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Tue Aug 29, 2017 9:38 am

@Fernando
Ok, essentially, 5.0.3.42 doesn't work on my system either. I say essentially because it kind of does at first, but then it totally doesn't, as odd as that might sound.

- The 5.03.42 drivers install via the Device Manager without issue, with one minor caveat. The 5.0.1.38 drivers don't ask for a system restart when I plug them into the Device Manager, but the 5.0.3.42 drivers do. I'm absolutely certain that this is significant somehow, because the 5.0.4.43 drivers do the same thing. The difference is that the 5.0.4.43 drivers break the connection to all my USB devices as soon as they're installed, whereas the 5.0.3.42 drivers do not. I'm not sure what exactly causes drivers to set a "reboot required" flag in Windows after they're installed, but perhaps you do??

- After a reboot, the 5.0.3.42 drivers will appear to function normally, and they do not trip Secure Boot, but after a relatively short period of system uptime (8-12 hours), something about the way the drivers interact with the Windows kernel causes catastrophic system instability. It starts out as mini-freezes, 6-10 seconds a piece in 0.5-3 minute intervals, but eventually, the system ends up crashing with either a KERNEL_SECURITY_CHECK_FAILURE or a PAGE_FAULT_IN_NONPAGED_AREA bug check, and upon restarting, the system crashes with a PAGE_FAULT_IN_NONPAGED_AREA bug check. At this point, Windows will not load again until Secure Boot is disabled or Driver Signature Enforcement is disabled from the Advanced Startup menu.

My XHCI controller hardware ID is DEV_A12F. What's yours, Fernando? At this point, I'd say it's highly unlikely to be the same as mine...

Also, I know this might be a silly question, but did you acquire the 5.0.1.38 drivers from a different person or source than you did the 5.0.3.42 and 5.0.4.43 drivers?

reply

#1228 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Tue Aug 29, 2017 9:59 am

@cousinit99:
Thanks for your report.

Zitat von cousinit99 im Beitrag #1225
My XHCI controller hardware ID is DEV_A12F. What's yours, Fernando? At this point, I'd say it's highly unlikely to be the same as mine...

The DeviceID of my on-board Intel USB 3.0 Controller is exacty the same as yours (DEV_A12F).

Zitat
did you acquire the 5.0.1.38 drivers from a different person or source than you did the 5.0.3.42 and 5.0.4.43 drivers?

I generally do not offer any mod+signed driver, whose source files are not taken from the chipset manufacturer.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1229 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Tue Aug 29, 2017 8:35 pm

sound familiar to my problem.
that last version its problematic

reply

#1230 | RE: USB 3.0/3.1 Drivers (original and modded) datum

Tue Aug 29, 2017 9:13 pm

Zitat von egozi im Beitrag #1227
that last version its problematic

In which way? Did you enable the �Secure Boot� option?

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

Please enter a reason for warning.