%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C7F
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_00
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_01
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_02
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_03
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_04
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_8C31&REV_05
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C7F
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C31&REV_00
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C31&REV_01
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C31&REV_02
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C31&REV_03
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_9C31&REV_04

Quoted from README.txt:

"*  NOTE:  This document refers to systems containing the
*         following Intel processors/chipsets:
*
*          3rd generation Intel(R) Core(TM) Processor Family
*              2nd generation Intel(R) Core(TM) i3 processor
*              2nd generation Intel(R) Core(TM) i5 processor 
*              2nd generation Intel(R) Core(TM) i7 processor
*              2nd generation Intel(R) Core(TM) i7 Extreme processor
*
*          Intel(R) 7 Series/C216 Chipset Family (Panther Point PCH)"

...

"***************************************************************************
*   Operating Systems supported
***************************************************************************

Intel® 7 Series Chipset Family:
•  Windows* 7 Operating System (both 32-bit and 64-bit versions).

Intel® C216 series chipset family:
•  Windows* 7 Operating System (both 32-bit and 64-bit versions).
•  Windows* Server 2008 R2 64-bit Operating System."

"The reason you aren't finding any Intel drivers, is because they aren't providing driver support for Windows 8. Microsoft has taken over the task of writing drivers for USB 3.0 chipsets. This obviously was a mistake on their part. Not because they took over responsibility, but because they didn't handle it properly."
Quoted from:http://answers.microsoft.com/en-us/wind … 702612df4b November 9,2012 @ 2:36:09 AM

"It seems that the 'universal' USB 3 drivers in windows 8 do not allow installing directly from USB 3."
Quoted from: http://communities.intel.com/message/172275#172275

"What these changes do is add in the IntelAMD64.6.2 section into the driver INFs (the files that tells Windows HOW to install the driver). This section is blank in the current driver release."
quoted from:http://communities.intel.com/message/171830#171830

"one important tidbit concerning Driver Signing.  If it's just a modded .Inf that is at issue:"

Laslow wrote:

"Once the driver is installed you don’t need to leave enforcement disabled."

Quoted from: http://forum.driverpacks.net/viewtopic. … 705#p49705

"Precautions against counterfeit semiconductor chips

November 14, 2011

Renesas has recently confirmed some counterfeit chips that have very similar appearances to the company's products. These counterfeits are exquisitely made so it is very difficult to discriminate them by appearance. For instance, we discovered counterfeits in which mold surface, marks, or the packages had close resemblances to that of Renesas' genuine products.

Some of these counterfeits have very poor quality and functionality, and may cause breakdowns or malfunctions if used in your systems or applications.

The counterfeits have not been distributed through Renesas' official sales channels and we would like our customers to purchase Renesas products through our official sales channels. Please note that Renesas holds no responsibilities for any malfunctions or damages caused by using counterfeit products."
http://www.renesas.com/press/notices/no … 11114.html

NEC/Renesas uPD720200(A) xHCI USB 3.0 Host Controller/Hub

Etron Technology Inc. USB 3.0 Extensible Host Controller (EJ168, EJ188, or EJ198)

Edit:  except for v2.1.36.0 (for XP?) here --> http://download.lenovo.com/ibmdl/pub/pc … y210ww.exe
and v3.0.12.0 (incl. XP) here --> http://download.lenovo.com/ibmdl/pub/pc … 02us17.exe
*** v3.0.16.0 (incl. XP) here --> http://downloadcenter.samsung.com/conte … 0.16.0.ZIP
or v3.0.20.0 (incl. XP?) from this previously-unknown-to-me vendor --> http://www.lycom.com.tw/Drivers/USB%203 … V30200.zip or http://dl.sunix.com.tw/upload_product_d … -setup.zip 

Excerpt quoted from the v3.0.20.0 uPD720201(2) lycom driver (file "Release_Note_xHCI-201-202-DR-WIN.txt"):

"4. History
---------------------------------------------------------------------------
---------------------------------------------------------------------------
 Version 3.0.20.0 : May 31, 2012
---------------------------------------------------------------------------
- Windows Logo Information
  Submission ID: 1497869
  Product Name: Renesas Electronics USB3.0 Host Controller
  Category: Device
  Subcategory: Bus Controllers and Ports > USB Controller
               Unclassiified
  Qualification Level:  Signature Only - Microsoft Windows XP family, x86
                        Signature Only - Microsoft Windows XP family, x64
                        Logo - Microsoft Windows Vista family, x86 Basic
                        Logo - Microsoft Windows Vista family, x64 Basic
                        Windows 7
                        Windows 7 x64 
                        Logo - Certified for Microsoft Windows Server 2008 Release 2 family, x64 

[1. Modified driver]
1-1.Modified the driver not to issue SetFeature(RemoteWake) in a PC, in which
   SystemWake is in PowerSystemSleeping3.
   
1-2.There is a possibility that BSOD occurs when the Stress Test of Pnpdtest.exe
  is excuted with connecting USB HUB having USB devices.

1-3.Additional remediation was implemented for the following ver 3.0.16.0 issue:

   [ver 3.0.16.0's history, item 2-4]
   2-4. USB3.0 Devices connected with USB3.0 HUB are not detected after S3/S4 resume.
       This issue occurs only under the following conditions.
        - C_PORT_CONNECTION of the downstream port of the hub is not changed after resume.
        - The PERSTB of the system is asserted after resume.

[2. Solved interoperability issue caused by function driver or system]
2-1.Fixed the interoperability issue of the specific docking station integrated
   SuperSpeed HUB.

2-2.When continues to start & stop the vedio capture with the specific USB2.0 Camera,
   the specific USB2.0 cannot start the video capture.

2-3.There is a possibility that BSOD occurs when a USB device, which a function
   driver sends the Power IRP before our device driver handles the "IRP_MN_START_DEVICE", 
   is connected.


---------------------------------------------------------------------------
 Version 3.0.16.0 : March 29, 2012
---------------------------------------------------------------------------
- Windows Logo Information
  Submission ID: 1490957
  Product Name: Renesas Electronics USB3.0 Host Controller
  Category: Device
  Subcategory: Bus Controllers and Ports > USB Controller
               Unclassiified
  Qualification Level:  Signature Only - Microsoft Windows XP family, x86
                        Signature Only - Microsoft Windows XP family, x64
                        Logo - Microsoft Windows Vista family, x86 Basic
                        Logo - Microsoft Windows Vista family, x64 Basic
                        Windows 7
                        Windows 7 x64 
                        Logo - Certified for Microsoft Windows Server 2008 Release 2 family, x64 

[1. Add function]
1-1. IOCTL_USB_USER_REQUEST(UWSBUSER_GET_POWER_STATE_MAP) is supported.
1-2. HUB's icon isn't shown on the Devices and Printers of Windows7.

[2. Modified driver bugs]
2-1. There is a possibility of BSOD when OUT transaction with data shorter than 8byte
     is transferred.  Short packet is out of this issue.
     We have never seen this BSOD on the real system. We found this on code review.
     v3.0.8.0 or later version includes this bug.
2-2. There is a possibility of BSOD when a user changes the resolution of the video
     capture application and an ISO device is disconnectd.
     We have never seen this BSOD on the real system. We found this on code review.
2-3. There is a possibility of BSOD when OverCurrent indication occurs before Windows
     OS detects the device. 
     We have never seen this BSOD on the real system. We found this on code review.
2-4. USB3.0 Devices connected with USB3.0 HUB are not detected after S3/S4 resume.
     This issue occurs only under the following conditions.
     - C_PORT_CONNECTION of the downstream port of the hub is not changed after resume.
     - The PERSTB of the system is asserted after resume.
2-5. Driver did not check the descriptor size. If USB devices send the descriptor
     with invalid size, driver might behave in undefined operation.
2-6. When BIOS does not release the ownership of xHCI after S3/S4 resume, host driver
     should not have been loaded.    
2-7. Wrong bandwidth information is displayed in the popup message when available 
     bandwidth is consumed.

[3. Solved interoperability issue caused by function driver or system]
3-1. PC freezes when any of the specific devices are disconnected.
3-2. The following specific devices can't work 
     A) The specific Wireless Headset does not produce sound in Windows XP enviroment. 
     B) The specific Keyboard is not detected. 
        This issue only occurs on v3.0.8.0 or later verion. 
     C) The specific Keyboard is not detected after remote wakeup under the condition
        that ForceHCResetOnResume is set to 1.
     D) The specific AV Portable Player disappears from Device Manager after it is
        disabled in Device Manager.
     E) Time from when the specific USB2.0 Flash is connected until it is detected
        is over 30 seconds. This issue may occur on v3.0.8.0 although we have 
        never seen this issue on the real system.
3-3. PC freezes when the specific Audio device is disconnected actively.
     This issue only occurs on V3.0.8.0 or later version.
3-4. Monitor function of the specific docking station cannot work correctly after
     resume when multi-display mode is used.
3-5. When multiple USB3.0-hubs including the specific hub are connected by cascade 
     connection and host driver is disabled and enabled, the hub connected with 
     the specific hub's downstream port is not detected.
3-6. When one of the multiple USB3.0 hubs in cascade connection is the specific
     HUB, it is not detected after S3-Resume.
3-7. When a specific smart phone is working in tethering mode, communication
     speed is too slow to keep the connection.  

---------------------------------------------------------------------------
---------------------------------------------------------------------------
 Version 3.0.12.0 : December 8th, 2011
---------------------------------------------------------------------------
- Windows Logo Information
  Submission ID: 1479314
  Product Name: Renesas Electronics USB3.0 Host Controller
  Category: Device
  Subcategory: Bus Controllers and Ports > USB Controller
               Unclassiified
  Qualification Level:  Signature Only - Microsoft Windows XP family, x86
                        Signature Only - Microsoft Windows XP family, x64
                        Logo - Microsoft Windows Vista family, x86 Basic
                        Logo - Microsoft Windows Vista family, x64 Basic
                        Windows 7
                        Windows 7 x64 
                        Logo - Certified for Microsoft Windows Server 2008 Release 2 family, x64 

-  Supported the uPD720201 ES2.1 whose Revision ID in the PCI Configuration
  register is 3h.

-  The following issues, which depend on specific devices, were fixed.

 1. A specific Audio device (Native Instruments AUDIO 8 DJ) isn't unloaded in
   the device manager when this device is disconnected from USB 3.0 Host 
   Controller.

 2. There is a possibility that a specific Audio device (Creative Sound Blaster
   X-Fi Surround 5.1) stops working. 
   This issue occurs with ver 3.0.8.0 or earlier version, and this issue doesn't
   occur with ver 2.x.xx.x(uPD720200/A).

-  The following additional issues were fixed.

-- Driver
 1. Remote Wakeup function doesn't work from Hybrid sleep by a wireless mouse 
   connected to USB 3.0 host controller.
 
 2. Additional remediation was implemented for the following ver 3.0.8.0 issue:

   [ver 3.0.8.0's history, item 2]
   There is a possibility that a multi-display isn't displayed after 
   S3->Resume when the USB-to-VGA device connected to the USB 3.0 Host
   is used in multi-display mode.  This issue occurs depending on USB-to-VGA
   device driver version.
 
 3. The "/usbss" test time for the Signal Check Tool for Windows was too long  
   (double or triple time) compared to uPD720200/A with ver 2.0.34.0 or older.

 4. There is a possibility that BSOD occurs when a SuperSpeed device which 
   doesn't transfer the "SuperSpeed Endpoint Companion Descriptor is 
   connected to USB 3.0 Host controller.

 5. A SuperSpeed device is reconnected in SuperSpeed mode after 
   S3/S4->resume if the SuperSpeed device transfers the 
   USB 2.0 Descriptor to USB 3.0 Host controller.

 6. A device cannot do Isochronous Transfer when an illegal start frame is 
   specified by the function driver for an Isochronous transfer.

 7. There is a possibility that BSOD occurs when performing the Common Scenario
   Stress-with-IO test in WHQL, when connecting an external USB hub to USB 3.0
   Host Controller.

---------------------------------------------------------------------------
 Version 3.0.8.0 : October 3rd, 2011
---------------------------------------------------------------------------
- Fisrt Major version Release for uPD720201/uPD720202 ES2.0 or later.

- Windows Logo Information
  Submission ID: 1470301
  Product Name: Renesas Electronics USB3.0 Host Controller
  Category: Device
  Subcategory: Bus Controllers and Ports > USB Controller
               Unclassiified
  Qualification Level:  Signature Only - Microsoft Windows XP family, x86
                        Signature Only - Microsoft Windows XP family, x64
                        Logo - Microsoft Windows Vista family, x86 Basic
                        Logo - Microsoft Windows Vista family, x64 Basic
                        Windows 7
                        Windows 7 x64 
                        Logo - Certified for Microsoft Windows Server 2008 Release 2 family, x64 

-  The following issues, which depend on specific devices, were fixed.
 1. A specific USB Full Speed device that can't respond to a standard request
    isn't detectd.
     
 2. There is a possibility that a multi-display isn't displayed after 
   S3->Resume when the USB-to-VGA device connected to the USB 3.0 Host
   is used in multi-display mode.  This issue occurs depending on USB-to-VGA
   device driver version.
   
 3. There is a possibility that the Bluetooth communication is cut off with 
   a specific Bluetooth module.
 
 4. There is a USB speaker which only requests a data transfer by a URB within 
   about 1ms. In this case, sound is cut off depending on CPU performance.

 5. iPad isn't detected on iTunes application after S3->Resume.
 
 6. BSOD ("Blue Screen of Death," i.e., system halt) occurs when PC shoutdown 
    is performed while a specific Bluetooth module (Billionton BT-0003) is 
    connected and a specific Bluetooth module driver version is being used. 
    This issue doesn't occur with the latest Bluetooth module driver version.
   
-  The following additional issues were fixed.
-- Driver
 1. There is a possibility that BSOD occurs or USB 3.0 Hub isn't detected on
   Windows XP when hot plug operation is done with a USB 3.0 Hub having USB 
   devices already connected to it.

 2. USB 3.0 Host controller Driver forcibly caused BSOD from ver2.1.16.0 to ver
   2.1.25.0 when Host System Error of USB 3.0 occurred.
   When we updated to ver2.1, we had a mistake in which the USB 3.0 Host 
   Controller Driver focibly caused BSOD.

 3. A USB device isn't detected when the USB device is connected to a downstream
   port on a specifc USB 3.0 Hub that moves to U2 state althouth U1/U2 timeout 
   value is zero.

 4. There is a miscalcuation of U2 Exit Latency.

--Monitor
 1. The pop-up message is wrong when a USB 3.0 device is connected to USB 2.0 port
   while running the Simplified Chinese OS.
 
 2. The pop-up message is wrong when USB 3.0 Host Controller does not have 
   enough bandwidth available while running the Polish OS."

Included here are sunix & lycom's product download pages to show that they are indeed either an OEM, VAR, or reseller.
Feel free to comment on either site's validity.