Hi

I have just updated from windows 7 to 10 ( beginning to wish I had not)

My storage controller is Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller

My Processors are 2 x  Intel(R) Core(TM)2cpu 6300 @ 1.86GHz

My Disk Drives are indicated in Device Manager as Intel Raid 1 Volume

The Raid Volume has operated perfectly well as a Raid level 1 mirror until update

At Boot the Raid indicates status as Verify

When I try to start up the Intel Matrix Storage Manager Consul I get the error message-

'Raid plug-in failed to load because the driver is not installed correctly'

I have tried to update drivers via device manager to be advised driver is up to date

I have tried to update drivers automatically via the Intel Download Centre but this fails to detect any drivers

I have downloaded f6flpy-x86.zip from the Intel Download Centre but am not certain this is appropriate for the Matrix Storage controller

but if it is I do not know how to install it.

Please can some one advise me - how can I resolve?

Thank you

Hi,

For a study, I would like to know the differences between two Intel Chipset driver versions (example: delta changes/fixes/improvements from v9.4.0.1026 and v10.0.27)

In the Intel websites, I don't get this information. can you please update from where can I get these information?

I would like to know the known issues/bugs in the previous release and fixes/improvements/new features in the next release.

Appreciate your help!

I came to the download center seeking to install the

Intel® Chipset Device Software (INF Update Utility)

The downloads worked fine, but both the setup and chipset...public fail to install.

Allegedly, these drivers MIGHT provide the PCI Data Acquisition and Signal Processing Controller that is missing on my Windows 7 Pro recent installation.

The suggestion from HP tech support was to install these drivers located on https://downloadcenter.intel.com/download/20775.

Whether or not these solve my root problem, they certain don't install and the failure is not informative.  Logs attached.

PS

I found some useless response on a similar thread that was never successfully resolved. The contributor suggested that Windows should be able to solve this problem itself and the download should not be necessary.

So, let me add that right clicking the device to update the driver results in:

Thus, we come to visit the download center for the INF Update Utility.

I used to think elevated UAC was a simple thing, but I just ran into a program that claims the elevation is not working. It's the Intel ChipUtil for identifying chipsets.

Download Intel® Chipset Identification Utility

I am launching it with a right click and RUN AS ADMINISTRATOR option.

WIndows (7 Pro) seems to go through the elevation process normally.

with a dimmed deskstop and a "Do you want to allow..." prompt to which I respond YES.

The result however is:

Hi, I used Google and found this: Intel software RAID to hardware RAID

I use a GIGABYTE H87M-HD3 with Intel H87 (Lynx Point) at the moment (5 HDD, Raid 5, Intel RST).

I bought an Intel RS3DC080 today. Is there any possibility to use the existing software raid with the new controller without rebuilding the array?

Hi,

I have to configure a RMM software on a couple of machines which have some Intel stuff on-board. I thought the easiest way would be to monitor the Windows Event logs, but I don't know in which event logs and under which source name the Intel stuff reports.

Some Examples:

* Intel Network Connections

* Intel Graphic Driver

* Intel Management Engine Components

* Intel Rapid Storage Technology

* Intel Security Assist

* Intel USB 3.0 Host Controller Adaptation Driver

* ...

I know not everything is important, and needs to be monitored. But for Example The Intel Rapid Storage Technology should be in charge of the harddisks, and it would be nice to know if there is a problem.

Thanks for any information/help,

Christian.

Hello,

Windows crashes(blue screen) pointing to sSATA RSTe storage controller:

A problem has been detected and Windows has been shut down to prevent damage

to your computer.

 

The problem seems to be caused by the following file: iaStorB.sys

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

If this is the first time you've seen this stop error screen,

restart your computer. If this screen appears again, follow

these steps:

 

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

 

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

 

Technical Information:

 

*** STOP: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000000,

0xfffff880010d243e)

 

*** iaStorB.sys - Address 0xfffff880010d243e base at 0xfffff88001073000 DateStamp

0x555d9453

 

Motherboard: Supermicro X10DRG-Q (system configured as UEFI, system FW up-to-date)

Chipset: C612

OS: Windows 7pro x64

RSTe driver: 4.3.0.1198

sSATA connected devices:

  Intel SSD DC S3610 (FW G2010160)

  Intel SSD DC S3520 (FW N2010101)

sSATA and SATA controllers run in RAID mode.

Windows installed on S3610, linux installed on S3520. System is stable - no memory problems(tested that). It seems that problems started after new ssd S3520 was added. Problem shows once/twice a day, possibly when windows is booted right after linux was booted(not 100% sure).

Any ideas ?

Thanks,

Vilius M.

Hello people,

Could you clarify if the chipset which is said to use the following qualities:

Intel® Z77 chipset :

2 x SATA 6Gb/s port(s), gray

2 x SATA 3Gb/s port(s), blue

2 x eSATA 3Gb/s port(s), red

Support Raid 0, 1, 5, 10

Supports Intel® Smart Response Technology, Intel® Rapid Start Technology, Intel® Smart Connect Technology *3

should be used for construction of Raid 1 of two SSD drivers?

I got an argument against hardware Raid use : "if a ssd dies in few years it would be a problem to buy one exactly same".

Should a software raid be considered to use at a board with the cpihset rather than a hardware raid controller used?

Does the hardware Raid support TRIM for ssd drives performance is not reduced?

Sincerely yours,

Andrey Volodin

Linux developer

Hello

Tested with different disks and with all versions between 14.0 and 15.2 : the bug is attested. The spin-down function was OK in 13.6.

Do you know why this bug hasn't been solved within more than 19 lonnnnnnnnnnng month ????!!!

Yet it has been reported long time ago !

New RST 14.0.0.1143 doesn't allow HDDs to spin down (bug?)

Thank you

some one knows if there exist? i found only for xp and up

Hi,

I used Intel® Driver Update today to see if there was a new chipset driver, and there was a new driver, but every time i try to install it, I get "Unknow error", your program says told me this

Installed Version: 10.0.14393.0

Latest Version: 10.1.1.14

But it will not install driver

I use

Windows 10 64Bit

P5Q-EM Motherboard from ASUS, and the chipset driver there is from 2009

[0AA8:26F4][2017-02-23T20:24:37]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Tower\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{35D389FB-6756-4B38-9711-B39607810130} {C6DB8491-D187-40A9-A4B3-F97AE68717AC} 6956'

[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'

[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'

[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438.log'

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Tower\Downloads\Intel Components\SetupChipset.exe'

[0AA8:26F4][2017-02-23T20:24:38]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[0AA8:26F4][2017-02-23T20:24:38]i000: Loading managed bootstrapper application.

[0AA8:26F4][2017-02-23T20:24:38]i000: Creating BA thread to run asynchronously.

[0AA8:2ADC][2017-02-23T20:24:38]i000: ** MBA ** Command line:

[0AA8:2ADC][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleName' to value 'Intel® Chipset Device Software'

[0AA8:2ADC][2017-02-23T20:24:38]i000: ** MBA ** Calling Engine.Detect()

[0AA8:26F4][2017-02-23T20:24:38]i100: Detect begin, 3 packages

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet35' to value '1'

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet40Client' to value '1'

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet40Full' to value '1'

[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet45' to value '394802'

[0AA8:26F4][2017-02-23T20:24:38]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: DotNet45, state: Present, cached: None

[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent

[0AA8:26F4][2017-02-23T20:24:39]i199: Detect complete, result: 0x0

[0AA8:26F4][2017-02-23T20:24:43]i200: Plan begin, 3 packages, action: Install

[0AA8:26F4][2017-02-23T20:24:43]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[0AA8:26F4][2017-02-23T20:24:43]i052: Condition 'NOT VersionNT64' evaluates to false.

[0AA8:26F4][2017-02-23T20:24:43]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i052: Condition 'VersionNT64' evaluates to true.

[0AA8:26F4][2017-02-23T20:24:43]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0AA8:26F4][2017-02-23T20:24:43]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438_0_SetupChipsetx64.msi_rollback.log'

[0AA8:26F4][2017-02-23T20:24:43]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438_0_SetupChipsetx64.msi.log'

[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[0AA8:26F4][2017-02-23T20:24:43]i299: Plan complete, result: 0x0

[0AA8:2ADC][2017-02-23T20:24:43]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[0AA8:2ADC][2017-02-23T20:24:43]i000: ** MBA ** Getting window handle.

[0AA8:2ADC][2017-02-23T20:24:43]i000: ** MBA ** Calling Engine.Apply(). Window handle: 5308976

[0AA8:26F4][2017-02-23T20:24:43]i300: Apply begin

[1B2C:1BA4][2017-02-23T20:24:43]i000: Caching bundle from: 'C:\Users\Tower\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'

[1B2C:1BA4][2017-02-23T20:24:43]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14

[1B2C:13F4][2017-02-23T20:24:43]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi.

[1B2C:13F4][2017-02-23T20:24:43]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\media1.cab.

[1B2C:1BA4][2017-02-23T20:24:43]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi

[1B2C:1BA4][2017-02-23T20:24:43]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[1B2C:1BA4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to install MSI package.

[1B2C:1BA4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to execute MSI package.

[0AA8:26F4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[0AA8:26F4][2017-02-23T20:24:53]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[0AA8:26F4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to execute MSI package.

[1B2C:1BA4][2017-02-23T20:24:53]i301: Applying rollback package: SetupChipsetx64.msi, action: Uninstall, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[1B2C:1BA4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to uninstall MSI package.

[1B2C:1BA4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to execute MSI package.

[0AA8:26F4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[0AA8:26F4][2017-02-23T20:24:55]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[1B2C:1BA4][2017-02-23T20:24:55]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi

[1B2C:1BA4][2017-02-23T20:24:55]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\

[1B2C:1BA4][2017-02-23T20:24:55]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi

[1B2C:1BA4][2017-02-23T20:24:55]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}

[1B2C:1BA4][2017-02-23T20:24:55]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\

[0AA8:26F4][2017-02-23T20:24:55]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[0AA8:26F4][2017-02-23T20:24:55]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[0AA8:2ADC][2017-02-23T20:24:55]e000: ** MBA ** Unknow Error.

Hello,

Reinstalled windows, can't understand which intel Chipset Driver and intel Management Engine Interface I should install?

I found this Download Intel® Chipset Device Software (INF Update Utility) for the chipset and this Download Intel® ME: Management Engine Driver for the MEI. Are those good?

System: xps 13, Ivy Bridge (7 Series).

Thanks

Does Braswell has some Relateddocuments about SATA RX (Receive) ModPHY Register section ?

Like SKYLAKE Can Adjustment SATA RX CTLE (As shown below)

Hi,

For a study, I would like to know the differences between two Intel Chipset driver versions (example: delta changes/fixes/improvements from v9.4.0.1026 and v10.0.27)

In the Intel websites, I don't get this information. can you please update from where can I get these information?

I would like to know the known issues/bugs in the previous release and fixes/improvements/new features in the next release.

Appreciate your help!

In Lenovo Idea pad 510 series running on windows 10, there is a tray Icon which says intel RST service is not running.

Here I would attache the pic of the error occurring.

I have uninstalled the program but not able to reinstall it again.

but the re installation is being failed , i will attach the log file below

How can i resolve the error ?

Hi there,

I have got an issue with a custom USB 2.0 device (with our own firmware) regarding enumeration and driver installation in windows 7 using USB 3.0 extensible Host Controller driver.

The devices uses the BOS descriptor (OS 1.0) to provide a compatible ID (RNDIS) for selecting the appropriate inf file / driver (rndiscmp.inf / rndiscmp6.sys). This works fine in Windows 7 using (native Microsoft) USB 2.0 driver and also in Windows 8 using USB 3.0 or 2.0 with MS driver (on many different installations). But it does not work in Windows 7 using intel USB 3.0 extensible Host Controller (using a VIA Chipset/driver stack it works!). Analyzing USB traffic I can observe that the Descriptor is requested from the device. Hereupon the compatible ID is sent to the PC but it can not be found in registry and hence it is not used to select the driver automatically (evaluating setupapi.dev). The driver must be chosen manually then.

Actually the USB requests are the same as in the USB 2.0 case but something goes wrong in intel USB 3.0 driver stack.

Does anybody have any idea? Or any additional debugging possibility?

Thank you very much!

Martin

I had to do a fresh in stall of win 7. Every thing went fine. I upgraded to two 2 TB Samsung EVO 850 drives. Rebuild of RAID 1 was moving along fine -then I got a message that "A hard drive is missing - A hard drive has failed and RAID volume is degraded. Replace the failed drive"  System is still running fine on one drive.

questions

1) Is there a way that I can attempt a rebuild of RAID 0?

2) Could it be the Intel Matrix Storage Console 8.9 that is the problem?

3) What is the latest version of  Intel Matrix Storage Manager that will work with my Asus Sabertooth z77 motherboard?

4) Is there a way to reformat my SSD drive and see if that fixes the problem?

5) Other solutions appreciated..

Thanks

Richard

Hello,

Windows crashes(blue screen) pointing to sSATA RSTe storage controller:

A problem has been detected and Windows has been shut down to prevent damage

to your computer.

 

The problem seems to be caused by the following file: iaStorB.sys

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

If this is the first time you've seen this stop error screen,

restart your computer. If this screen appears again, follow

these steps:

 

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

 

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

 

Technical Information:

 

*** STOP: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000000,

0xfffff880010d243e)

 

*** iaStorB.sys - Address 0xfffff880010d243e base at 0xfffff88001073000 DateStamp

0x555d9453

 

Motherboard: Supermicro X10DRG-Q (system configured as UEFI, system FW up-to-date)

Chipset: C612

OS: Windows 7pro x64

RSTe driver: 4.3.0.1198

sSATA connected devices:

  Intel SSD DC S3610 (FW G2010160)

  Intel SSD DC S3520 (FW N2010101)

sSATA and SATA controllers run in RAID mode.

Windows installed on S3610, linux installed on S3520. System is stable - no memory problems(tested that). It seems that problems started after new ssd S3520 was added. Problem shows once/twice a day, possibly when windows is booted right after linux was booted(not 100% sure).

Any ideas ?

Thanks,

Vilius M.

Hi, just built myself a desktop and went to download my drives, then I get to chip set and it starts to download and just goes to a black screen. I can't do anything and it's been an hour. I got it form my motherboards website so I don't know whats wrong. Any fixes?

Hi -

Can anyone help resolve this issue?  Device Manager shows "Universal Serial Bus (USB) Controller" listed under "Other devices" with a warning "There is no driver selected for the device information set or element."  I uninstalled it and ran "scan for new hardware".  System reinstalled it with same error message.  Tried "update driver" and that failed.  Right-clicked on device name > Properties:

Device Description:  Universal Serial Bus (USB) Controller
H/W ID:  PCI\VEN_8086&DEV_8C31&SUBSYS_05B71028&REV_05
               PCI\VEN_8086&DEV_8C31&SUBSYS_05B71028
               PCI\VEN_8086&DEV_8C31&CC_0C0330
               PCI\VEN_8086&DEV_8C31&CC_0C03
Config Flag: 00000040
                    CONFIGFLAG_FAILEDINSTALL

Location Information: PCI bus 0, device 20, function 0
Physical Device Object Name: \DEVICE\NTPNP_PCI0002

Checked System Information; results below:

Name Intel(R) 8 Series/C220 Series SATA AHCI Controller - 8C02

Manufacturer Intel

Status OK

PNP Device ID PCI\VEN_8086&DEV_8C02&SUBSYS_05B71028&REV_05\3&11583659&0&FA

I/O Port 0x0000F070-0x0000F077

I/O Port 0x0000F060-0x0000F063

I/O Port 0x0000F050-0x0000F057

I/O Port 0x0000F040-0x0000F043

I/O Port 0x0000F020-0x0000F03F

Memory Address 0xF7316000-0xF73167FF

IRQ Channel IRQ 19

Driver c:\windows\system32\drivers\msahci.sys (6.1.7601.17514, 30.38 KB (31,104 bytes), 11/20/2010 10:23 PM)

Name ATA Channel 0

Manufacturer (Standard IDE ATA/ATAPI controllers)

Status OK

PNP Device ID PCIIDE\IDECHANNEL\4&7B377EC&0&0

Driver c:\windows\system32\drivers\atapi.sys (6.1.7600.16385, 23.56 KB (24,128 bytes), 7/13/2009 7:19 PM)

Name ATA Channel 1

Manufacturer (Standard IDE ATA/ATAPI controllers)

Status OK

PNP Device ID PCIIDE\IDECHANNEL\4&7B377EC&0&1

Driver c:\windows\system32\drivers\atapi.sys (6.1.7600.16385, 23.56 KB (24,128 bytes), 7/13/2009 7:19 PM)

Any idea what's causing this or how to fix it?

Thanking you in advance...