I am looking for a version of

Intel(R) USB 3.0 eXtensible Host Controller Driver

which can function in Win10 - but Intel seems only to have drivers for Win7 (and 8).

Befor I upgraded from Win7, the USBs functioned perfectly - but after I had Win10 installed, the USB3.0 ports malfunction when a USB3.0 is connected (while it still functions correctly with a USB2).

I have had HP-support to investigate the problem. They upgraded the chipset-driver and some other drivers - but the error persisted. As a last attempt, the motherboard was exchanged - still without elimination of the problem. Then HP gave up - suggested to re-install Win7 and afterwards upgrade to Win10. However, I am quite reluctant with this suggestion, in particular because Win10 after the latest upgrade a few days ago tells that the driver does not function with Win10 - and that a new or updated version for Win10 should be installed. But do there exist such a version?

(My pc: HP ProDesk 490 G2 MT with Intel(R) Core(TM)i7-4790S CPU @ 3.20GHz)

Hey guys,

I am looking for a version of Mobile 5th Generation Intel(R) Core(TM) Camarillo Device - 1603 driver which can function Win 8.1.

Can you help me? It is for a Dell XPS13 9343. Thank you so much!

Sourcire

When I try to use the program "SetupChipset.exe" to update my drivers, I get "unknown error" as it's about to finish, everytime.

PLEASE help!!

Thanks in advance,

Robert

Oh, btw - I'm not sure which of the three log files I should paste but here's one of them:

[1F50:1F5C][2016-10-12T15:10:13]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\rober\Downloads\SetupChipset (1).exe, cmdline: ''

[1F50:1F5C][2016-10-12T15:10:13]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'

[1F50:1F5C][2016-10-12T15:10:13]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'

[1F50:1F5C][2016-10-12T15:10:13]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[1F50:1F5C][2016-10-12T15:10:13]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\rober\AppData\Local\Temp\Intel\Logs\Chipset_20161012151014.log'

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\rober\Downloads\SetupChipset (1).exe'

[1F50:1F5C][2016-10-12T15:10:14]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[1F50:1F5C][2016-10-12T15:10:14]i000: Loading managed bootstrapper application.

[1F50:1F5C][2016-10-12T15:10:14]i000: Creating BA thread to run asynchronously.

[1F50:2520][2016-10-12T15:10:14]i000: ** MBA ** Command line:

[1F50:2520][2016-10-12T15:10:14]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[1F50:2520][2016-10-12T15:10:14]i000: ** MBA ** Calling Engine.Detect()

[1F50:1F5C][2016-10-12T15:10:14]i100: Detect begin, 3 packages

[1F50:1F5C][2016-10-12T15:10:14]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5'

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'DotNet40Client' to value '1'

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'DotNet40Full' to value '1'

[1F50:1F5C][2016-10-12T15:10:14]i000: Setting string variable 'DotNet45' to value '394802'

[1F50:1F5C][2016-10-12T15:10:14]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[1F50:1F5C][2016-10-12T15:10:14]i101: Detected package: DotNet45, state: Present, cached: None

[1F50:1F5C][2016-10-12T15:10:14]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent

[1F50:1F5C][2016-10-12T15:10:14]i199: Detect complete, result: 0x0

[1F50:1F5C][2016-10-12T15:28:27]i200: Plan begin, 3 packages, action: Install

[1F50:1F5C][2016-10-12T15:28:27]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[1F50:1F5C][2016-10-12T15:28:27]i052: Condition 'NOT VersionNT64' evaluates to false.

[1F50:1F5C][2016-10-12T15:28:27]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i052: Condition 'VersionNT64' evaluates to true.

[1F50:1F5C][2016-10-12T15:28:27]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[1F50:1F5C][2016-10-12T15:28:27]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\rober\AppData\Local\Temp\Intel\Logs\Chipset_20161012151014_0_SetupChipsetx64.msi_rollback.log'

[1F50:1F5C][2016-10-12T15:28:27]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\rober\AppData\Local\Temp\Intel\Logs\Chipset_20161012151014_0_SetupChipsetx64.msi.log'

[1F50:1F5C][2016-10-12T15:28:27]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[1F50:1F5C][2016-10-12T15:28:27]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[1F50:1F5C][2016-10-12T15:28:27]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[1F50:1F5C][2016-10-12T15:28:27]i299: Plan complete, result: 0x0

[1F50:2520][2016-10-12T15:28:27]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[1F50:2520][2016-10-12T15:28:27]i000: ** MBA ** Getting window handle.

[1F50:2520][2016-10-12T15:28:27]i000: ** MBA ** Calling Engine.Apply(). Window handle: 1376664

[1F50:1F5C][2016-10-12T15:28:27]i300: Apply begin

[1190:04B0][2016-10-12T15:28:29]i000: Caching bundle from: 'C:\Users\rober\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'

[1190:04B0][2016-10-12T15:28:29]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14

[1190:0658][2016-10-12T15:28:29]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.

[1190:0658][2016-10-12T15:28:29]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.

[1190:04B0][2016-10-12T15:28:29]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi

[1190:04B0][2016-10-12T15:28:29]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"'

[1190:04B0][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to install MSI package.

[1190:04B0][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to execute MSI package.

[1F50:1F5C][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[1F50:1F5C][2016-10-12T15:28:42]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[1F50:1F5C][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to execute MSI package.

[1190:04B0][2016-10-12T15:28:42]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"'

[1190:04B0][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to uninstall MSI package.

[1190:04B0][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to execute MSI package.

[1F50:1F5C][2016-10-12T15:28:42]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[1F50:1F5C][2016-10-12T15:28:42]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[1190:04B0][2016-10-12T15:28:42]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi

[1190:04B0][2016-10-12T15:28:42]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\

[1190:04B0][2016-10-12T15:28:42]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi

[1190:04B0][2016-10-12T15:28:42]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}

[1190:04B0][2016-10-12T15:28:42]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\

[1F50:1F5C][2016-10-12T15:28:42]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[1F50:1F5C][2016-10-12T15:28:42]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[1F50:2520][2016-10-12T15:28:42]e000: ** MBA ** Unknown error.

Estou rodando o utilitário de atualização,ele localizou uma atualização de chipset 10.1.1.14 porem quando vai instalar da erro desconhecido. Alguém pode me ajudar ?

その2件の「ドライバー更新」をクリックしたのですが、エラーが発生しインストールが終了してしまいました。

その際に表示されたのは下記のものです。

Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26

Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D

インテルのDriver Update Utility 2.6を試みたのですが、やはりエラーが発生し「失敗」と表示される状態です。

その際に検索されたのは「チップセット・デバイス・ソフトウェア（INF　アップデート・ユーティリティーEXE)」でした。

ログファイルは下記の通りとなります。

現在、コードレスマウスや、USBメモリーが使用できずに困っています。

WIN7が自動更新でWIN10になっています。@

解決策を教えてください。

よろしお願いいたします。

================quote=============

DriverUpdateUI.exe Error: 0 : System.Windows.Markup.XamlParseException: 指定されたバインディング制約に一致する型 'DriverUpdateUI.MainWindow' のコンストラクターの呼び出しで例外がスローされました。 ---> System.IO.IOException: 別のプロセスで使用されているため、プロセスはファイル 'C:\Users\hokka\AppData\Local\Temp\IntelDLM\debugFile.Log' にアクセスできません。

   場所 System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   場所 System.IO.File.InternalDelete(String path, Boolean checkHost)

   場所 System.IO.File.Delete(String path)

   場所 DriverUpdateUI.MainWindow.PrepareLogFile()

   場所 DriverUpdateUI.MainWindow..ctor()

   --- 内部例外スタック トレースの終わり ---

   場所 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)

   場所 System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)

   場所 System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)

   場所 System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)

   場所 System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)

   場所 System.Windows.Application.DoStartup()

   場所 System.Windows.Application.<.ctor>b__1_0(Object unused)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

DriverUpdateUI.exe Error: 0 : System.Windows.Markup.XamlParseException: 指定されたバインディング制約に一致する型 'DriverUpdateUI.MainWindow' のコンストラクターの呼び出しで例外がスローされました。 ---> System.IO.IOException: 別のプロセスで使用されているため、プロセスはファイル 'C:\Users\hokka\AppData\Local\Temp\IntelDLM\debugFile.Log' にアクセスできません。

   場所 System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   場所 System.IO.File.InternalDelete(String path, Boolean checkHost)

   場所 System.IO.File.Delete(String path)

   場所 DriverUpdateUI.MainWindow.PrepareLogFile()

   場所 DriverUpdateUI.MainWindow..ctor()

   --- 内部例外スタック トレースの終わり ---

   場所 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)

   場所 System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)

   場所 System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)

   場所 System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)

   場所 System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)

   場所 System.Windows.Application.DoStartup()

   場所 System.Windows.Application.<.ctor>b__1_0(Object unused)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   場所 System.Windows.Threading.DispatcherOperation.InvokeImpl()

   場所 System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)

   場所 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   場所 MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)

   場所 System.Windows.Threading.DispatcherOperation.Invoke()

   場所 System.Windows.Threading.Dispatcher.ProcessQueue()

   場所 System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   場所 MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   場所 MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   場所 System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)

   場所 MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

   場所 MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

   場所 System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

   場所 System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

   場所 System.Windows.Application.RunDispatcher(Object ignore)

   場所 System.Windows.Application.RunInternal(Window window)

   場所 System.Windows.Application.Run(Window window)

   場所 DriverUpdateUI.App.Main()

================unquote=============

Hi everyone

I pretend to port coreboot to a system that has the (Intel® DH82C222 PCH) Specifications  chipset.

The problem is that I was not able to find the fsp (firmware support package) for this chipset.

Does anyone know were I can find it?

Thanks and Regards

Rafael R. Nachado

I have an Alienware Area 51 R2 desktop, which uses the Intel X99 chipset. This appears to be Intel RST 14.

I wish to use three large drives in a RAID 5 configuration. This will be a data volume (no boot).

What limitations need to be considered in selecting a drive? Are there capacity or other restrictions? The only limit I've found so far are that older drivers require 512e, but I run Windows 10 and have fully up to date RST drivers.

Is there any reason three 10TB Seagate IronWolf NAS drives would not work in a RAID 5 configuration? This is Seagate model number ST10000VN0004

HELP ME I CAN NOT USE THE USBS.I HAVE TO RESET WIN 10 AFTER THE RESET THERE WAS ONLY 1 USB WORKING AND TELL ME I NEED TO UPDATE TO THIS CHIP SET. BUT THE COMPUTER GIVE ME THIS ERROR.

Hi,

I have an issue with the Intel Extreme Tuning Utility, the latest version. (6.1.2.13)

I could not get it to install, latest windows 10 (build 14393) I kept getting getting an error saying could not start the XTU service, verify you have sufficient privileges.

I got frustrated, so I re-installed windows to remove any old versions or conflicts.  Then once windows and drivers were fully patched I tried the XTU install again, but got the same error.

In Windows Services I noted that XTU was listed as starting. I noted that in resource monitor the Intel integrated clock controller service ICCS was using a bit of CPU.

When i manually stopped the ICCS the XTU started just fine, then I could start the XTU without a drama, and the install completed without error.

Now each time I startup the PC the XTU does not start. it will start when I manually stop the ICCS.

The board is an ASrock Z170 Pro 4, with the latest BIOS, 7.0.

Hi forum

I have an ASUS H87M-E mainboard and 1 SATA SDD (OS) and a SATA HDD for data. It has a fresh (by OEM) Windows 10 installed with iRST as well.

Now I wanted to add a third HDD to this system. But Windows Disk Manager cannot initialize this disk. I get a CRC data error. I've tested the disk in another system and it didn't complain.  I can format it, diskpart it and so on - but as soon as I install this disk into my system above I failes to initialize the disk. SMART values are fine. The disk works fine in a Win7 and Win10 System. So something must be wrong with my system above.

I've seen, this system has iRST installed. On boot up I got an iRST error in the windows 10 notification area. In the iRST the current status states: "Your system reports one or more events and data may be at risk" (translated from german) with an alert symbol (white cross on red background). But both disks, the SSD and the HDD are having a green check icon. There is now alert icon (yellow) to indicate a missing disk or a degraded RAID. Therefore I'm a little bit lost here. Why do I get an error on startup and the status tells the same when both disks are available with fault free SMART values?

My investigation lead me the device manager to check the 3rd disk. But there wasn't a 3rd disk but a "Intel Storage Volume" listed. So I assume the iRST converts my 3rd disk somehow into a Intel Storage Volume (same size) which I cannot initialize. But why? This 3rd disk isn't listed in the iRST!

I've read a lot iRST threads and one thing differs from other user: My SSD disk has not only the green check icon but also a ribbon with 3 white dots which the HDD does not have.

Could it be that nevertheless a RAID was set up but iRST does not show this information (missing RAID disks)?

Why does a "Intel RAID Volume" popup in the device manager as soon as I install the 3rd disk?

And why can i not initialize this "Intel RAID Volume"? actually, I'd like to get rid off this volume in the device manager and want to have a single 3rd drive - just like the others. What is iRST messing up?

many thanks

SiS

Hi

I'm trying to pick an external multi-bay hdd enclosure for my H79-based HTPC, and some of them require host computer to have "Port Multiplier w/ FIS-based switching". I'd like to know if H79 chipset supports it. According to this table it is supported by X79, but I'm not sure this it also applies to H79.

Thanks!

chipset.exe will not install with the updater or by itself.

I'm having some issues with this Driver Installation:

I've used Intel(R) Driver Update Utility 2.6 to scan for my drivers, then i have installed the latest over the old updates. The software asked for a reboot to complete the installation, but after that, it keeps warning me about the same update.

This is the notification after the Reboot:

This is the History in the Utility (As you can see, it says (Completed):

After some online research, i found out that i can check the currently installed version of Chipset drivers via REGEDIT.

It seems that the "RebootRequired" entry is stuck, and i can't find out how to fix it.

Thank you for your time!

Can someone help me get a general overview and understanding of RST (Rapid Storage Technology) and RSTe (Intel Rapid Storage Technology enterprise).

On ark.intel.com you'll find these definitions:

Are you familiar with any other definitions - ones that are more specific?

I imagine it would be a good idea to have a matrix showing features of RST and RSTe and conjunction with the different Intel chipsets/Intel storage controllers.

Please provide me with any information you might have...I will when start creating this matrix :-)
Some of the questions to be asked/answered:

• what's the difference in features of RST and RSTe and when/how are the activated?
• what kind of Intel SATA controllers/chipset support RST and RSTe?
• Is it correct that not all RST supported SATA controllers support software RAID, which one do and don't?
• In your motherboard BIOS you can set your controller in either AHCI or RAID mode...what influence does this have relation to RST/RSTe, beside the obvious that the later will activate the software RAID feature?
• Has Intel SCU (SAS-Control-Unit or Storage-Controller-Unit) anyting to do with RST(e)?

I have boards with Intel chipset C232 and C236.

The PCI-IDs for the SATA  controllers are:

What SATA controller is in these boards?

In Windows 10 I can install a driver called "Intel(R) C600+/C220+ series chipset SATA AHCI Controller"

Tried to lookup the ID's on pcidatabase.com.....but it's not listed.

No help from Google either.

I have a motherboard with a Z170 chipset and I have two NVMe drives. I want them to be configured as RAID1 drives.

I tried installing RSTe NVMe 4.5.0.2125, but the message was "This computer does not meet the minimum requirements for installing the software."

I tried installing RST RAID 15.2.0.1020 and the RST from the Gigabyte website (motherboard is a GA-Z170X-UD3), but when I run it there are no NVMe drives connected: https://i.imgsafe.org/de500979f8.jpg

In Computer Management, I have two disks. Computer Management in Windows 10 shows this, but one disk has the OS, the other has the system partition: https://i.imgsafe.org/de477d4eaf.png

How can I get these two NVMe drives into RAID1? It is no problem reinstalling windows from scratch as this is a new build.

Hi all,

I currently have driver version's 9.3.0.1021 from Lenovo and also this version from Intel. I know this sounds daft but which should I be using? Thanks.

raid 1. RST ROM 10.1.0.1008

RST software 12.x

only if the original failed drive (which does detect) is hooked up, does the option to rebuild appear.

if a replacement drive is added, no option to rebuild, in ROM or Windows.

installed RST software v 15.x and that option did appear but did not work.

what is going on, and how do i replace a failed drive in a raid 1?

I have a Dell XPS 8100 that I purchased about 8 years ago. I ordered it with RAID 1 (mirroring) and a 1.5TB system disk. The system (OS) drive is the RAID drive. About a year ago drives started to fail, which I expected. I would replace the failed drive (port 0 or 1) and log on as an administrator and run the GUI for IRST. It would say there is a blank disk and offer to rebuild the array. I would say yes and over the next 24 hours or so it would rebuild the array. Fine. But a about a year ago drives started failing pretty frequently. In the last few months they have been failing at a rate of about one a month. I was talking to my supervisor at work about this (we are IT guys) and he suggested maybe the drives are not really failing but the IRST controller is having a problem and is giving me false information. He suggested bringing one of the "failed" drives to work and testing it. Today I brought the most recently failed disk to work and plugged it into my Startech USB drive dock. I am able to access it with no problem. Since it is mirrored it behaves just as if it were the only drive, with the same structure as a single drive in a Windows 7 system. I can open and access my user folder and can open files.

I noticed that there is a driver update for the IRST on my system. I was reluctant to install this before as I was afraid if something went wrong I would lose the whole array but if I can access the drive I brought to work I suppose I have a backup of everything.

Does anyone have any thoughts or advice on this?

Thanks,

Don

Hello everyone,

I'm experiencing a problem with my RAID 10 array and need some advice.

My computer is based on an ASUS P8Z77 WS motherboard with an Intel controller managing the following ports :

2 x SATA 6Gb/s port(s)

4 x SATA 3Gb/s port(s)

My OS is Windows 7.

I have a RAID 0 array of two SSDs for the system on the two SATA 6Gb/s ports and a RAID 10 array of four HDDs for data on the four SATA 3Gb/s ports.

Both arrays are managed through Intel Rapid Storage Technology software version 12.9.0.1001.

Yesterday I tried to clone a friend's HDD with Clonezilla, using an extra SATA port managed by a Marvell PCIe 9128 controller.

During the process of trying to save an image of the HDD on my computer, I couldn't see my RAID 10 array as a target to save the image and aborted the process.

After a reboot, one of the physical HDD of my RAID 10 array was indicated as degraded, so I allowed the IRST software to rebuild the data under Windows overnight.

Everything went fine and my RAID 10 array was working this morning.

Tonight I started my computer and realized my RAID 10 array was not accessible. All of the four drives are marked as offline in the IRST's POST slash screen and in the IRST software under Windows.

I'm pretty sure the HDDs are working and the data on the disks should be OK, but I'm not sure how to try to get it online again.

In the IRST software, I have the option to "Clear metadata" for each one of the four physical HDDs of my RAID 10 array.

So my questions are :

1. Should I click "Clear metadata" in order to let the RAID 10 array "rebuild" itself ?

1B. Which one should I click then ?

2. Would it be possible to try to rebuild the data from the RAID 10 array HDDs and save it to another HDD before trying anything with the IRST ?

2B. Which software would allow me to do that ?

3. Should I cry ?

Thanks in advance if you have any insight in this kind of problem and any advice...