[Outdated] USB 3.0/3.1 Drivers (original and modded)

Important Drivers General: Storage Drivers (AHCI/RAID, NVMe and USB)
1261

@Black_Lion :
Welcome to the Win-RAID Forum!

My answers: 2 x Yes (but there is no success guarantee)!

Good look!
Dieter (alias Fernando)

1262

thanks for the fast reply. so which of these components of my device manager would be affected by this driver package:



The USB 3.0-Hostcontroller and the USB-Root-Hub (USB3.0) of course. Anything else?

1263

No!

1264

hello

there is a chance the auto installer damaged my windows? since i tried installing it (which didnt succeed) my windows couldent start any more, then i reinstalled windows 10 and tried to install your auto usb 3 drivers without any success thinking that on a fresh system it will work (the auto installation) but not only that it didnt work i suspect that again it caused my windows to stop loading after start up.

this is from the event viewer after windows was able to fix the loading of the startup.

Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 6

Level 1

Task 63

Opcode 0

Keywords 0x8000400000000002

- TimeCreated

[ SystemTime] 2017-10-31T16:23:47.185550700Z

EventRecordID 2687

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer DESKTOP-0K7TLSP

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 6
PowerButtonTimestamp 0
BootAppStatus 3221225684
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true
CheckpointStatus 0

this error happens i think every time i do a restart

EDIT by Fernando: The Event Viewer details were put into a spoiler (to save space)

1265

@egozi :
Without any knowledge about your system (mainboard model, chipset, manufacturer of the USB Controller) and the used specific driver (what means “auto usb 3 drivers”?) I cannot answer your question.

1266

so here it is(attached)
the usb is intel
and the driver is the latest posted.
i ment by writing "auto" to the Dpins64.

as i wrote before, the windows does not let me install those drivers although i install the certificate. on the older drivers you posted it works fine. i always thaught it was my windows that is not quit okay after long time of use but as i worte before, i installed a fresh installation of latest windows 10 (1709) and i get the same message saying windows can let those drivers to be installed because of security - unknown publisher i think it says, anyway i now suspect (as writing before) that just the attempt to install the driver using the "dpins" messed up my system in a way windows crushes doesnt start up any more.

for you evaluation…
thank you

sys2.PNG

sys1.PNG

1267

@egozi :
Thanks for having given finally the asked information about your system (I have deleted our recent absolutely unneeded discussion).

To find out, whether
a) the installation procedure of any of my mod+signed drivers or
b) the DPInst method regarding the Intel USB 3.0 drivers
have been changed by the “Fall Creators Update” (v1709) of Windows 10, I just have done a test with my Z170 system running a fresh and “clean” installed Win10 x64 v1706.

This is what I did:

  1. Import of the Win-RAID CA Certificate:
    • Procedure: Right-click onto the file named ImportCertificate.cmd > Choose option “Run as Admin” > Enter “y” and use the “Enter” key > Press any key… > Done!
    • Pictures:

      Import of the Win-RAID CA Certificate Pic1.png

      Import of the Win-RAID CA Certificate Pic2.png

    2. 

  2. 
Installation of the 64bit mod+signed Intel USB 30 drivers v5.0.4.43 by using the DPInst method:
      

    • Procedure:
      Right-click onto the file named DPInst64.exe > Choose option "Run as Admin" > Click "Continue" > Wait until the work is completed > Click "Finish" > Choose the option "Restart the Computer"
      To check the success you should open the Device Manager and look for the in-use drivers of the Intel USB 3.0 devices.
      • 

    • Pictures:
      [[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic1.png|none|auto]][[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic2.png|none|auto]][[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic3.png|none|auto]]
      [[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic7.png|none|auto]][[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic4.png|none|auto]][[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic5.png|none|auto]][[File:DPInst Install of the mod+signed Intel USB 3.0 drivers Pic6.png|none|auto]]
      • 

    

    3. 


My conclusion: Since everything worked fine on my side, it seems, that your problem has not been caused by 
a) the "Fall Creators Update" Edition of Win10,
b) the used Intel USB 3.0 drivers or
c) the used DPInst file.

DPInst Install of the mod+signed Intel USB 3.0 drivers Pic1.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic2.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic3.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic7.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic4.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic5.png


DPInst Install of the mod+signed Intel USB 3.0 drivers Pic6.png

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1268
              
            

            

              
but that couldent be  because i did as the above exactly on a fresh system. maybe it doesnt work on all systems?

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1269
              
            

            

              
It’s a fact that those drivers didn’t work on a fresh system. What needs more digging is if the system crushed because of the attempt to install drivers windows rejected

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1270
              
            

            

              

Your fresh system it totally different from my fresh system. The fact, that we both tried to get the Intel UB 3.0 drivers installed, does not mean, that we automaticly get the same result. Not only our mainboard chipset and our on-board Intel USB 3.0 Controller model are different.



You got it! That is why I asked you within my first reply for the most important infos about your system (mainboard/Chipset/USB driver).



A fresh system doesn’t help, if you do something terribly wrong.
If you want  to find out the reason why your installation failed while my installation worked flawlessly, you should give us some additional information:
1. Are you sure, that you succeeded with the import of the Win-RAID CA Certificate?
2. What exactly happened after you have executed the DPInst64.exe as Admin? 
3. Did you get the “Finalisation” GUI at all (see my second picture of the installation procedure)? 
4. Which are the HardwareIDs of your on-board Intel USB 3.0 Controller (right-click onto it > “Properties” > “Details” > “Property” > “HardwareIDs”)?

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1271
              
            

            

              
I don’t think there is a reason to do all of that because the fact that older versions do work means it’s not a problem with my installation, otherwise it’s a problem with that specific version with my system - probably the combination. But that less worries me. What more worries me is the fact that this might be the cause of my system before and after the format of the hard drive not to load and have critical problems.
It’s just the only thing that I did after the fresh installation of Windows except maybe installing office and chrome. I am insisting of explaining that to you because I think you should check that driver you came up with so people won’t get there systems messed up. I must say that when it does work is wonderful.

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1272
              
            

            

              

The driver itself (= *.SYS file) was made by Intel and hasn’t been touched by me. So if the driver should be bad, you should ask Intel for a better one.
By the way: Nobody is forced to install any of my mod+signed drivers. The OS Win10 has in-box USB 3.0 drivers, which are compatible with nearly all USB 3.0/3.1 Controllers.

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1273
              
            

            

              


that is right.

i am only saying something is not working in the installation process

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1274
              
            

            

              
maybe i will record my screen and show you… i am thinking of reinstalling windows 10 again because of that problem, maybe i will just record the proccess just before that to show you

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1275
              
            

            

              
@egozi :
Before you are going to do a fresh OS installation, you should post the HardwareIDs of your on-board Intel USB 3.0 Controller.
Maybe your specific device is not supported by the Intel driver.

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1276
              
            

            

              
I will post but again, the message Windows gives me is that Windows prevented the installation of a new driver because it is front an unknown provider. And I did install the certificate the right way

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1277
              
            

            

              
hardwareIDs:

USB xHCI Compliant Host Controller:
PCI\VEN_8086&DEV_8C31&SUBSYS_85341043&REV_05
PCI\VEN_8086&DEV_8C31&SUBSYS_85341043
PCI\VEN_8086&DEV_8C31&CC_0C0330
PCI\VEN_8086&DEV_8C31&CC_0C03

USB Root Hub (USB 3.0):
USB\ROOT_HUB30&VID8086&PID8C31&REV0005
USB\ROOT_HUB30&VID8086&PID8C31
USB\ROOT_HUB30

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1278
              
            

            

              
@egozi :
Thanks for posting the HardwareIDs of your on-board Intel USB 3.0 Controller.
According to the related INF file the HardwareIDs “PCI\VEN_8086&DEV_8C31&REV_05” are supported by the latest Intel USB 3.0 drivers, but I am not sure, whether this is valid as well for the more specific HardwareIDs “PCI\VEN_8086&DEV_8C31&SUBSYS_85341043&REV_05”.

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1279
              
            

            

              
Hi, Fernando.

Just a quick note to say THANKS for ending my search for a solution to the Win 10 USB 3 issue.  Works great!

One note: I made the mistake of installing the drivers before the certificate, which cause the results to be unstable.  Deleted and started over and all is well.  Read the docs!

Tim

            


            

              
              
              
            


            

                
                
              


          

          

            

              



              
                  
                  
              1280
              
            

            

              
So could that be the reason? Can you post the older drivers which worked in the past?
How can you make sure the drivers should or shouldn’t work?