I cannot set the cache mode to Write Through for my single desk drive

I have a 3 disk system:

1x  Samsung 850 Pro M2.SSD 512GB
2x  Western Digital Red 3TB

I created two drives

1. Containing only the Samsung 850 Pro, no RAID

2. Containing both WD's in RAID1

Intel Rapid Storage lists all of them in the Storage System View

The top is the WD RAID1 set and I can click both the set and the individual disks on port 0 and 1

The 2nd is the Samsung 850 Pro on port 7

I can change the Cache mode for my RAID 1 set but not for my SSD drive as shown below.

How do I change the Cache more for my single drive SSD?

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 ?

Hi,

I'm trying to use BitLocker eDrive hardware encryption, but Intel RST 14.5.0.1081 is confilicting. I know this because when I uninstall RST, it works, but when it's installed it uses software encryption (BitLocker asks if I want to encrypt whole drive or only used portion)

This problem existed with an older version of RST on Windows 8.1 too and was fixed in version 13.2 (not entirely sure of exact version) but seems to be back.

Discussion about the issue earlier: T440s: How to enable the Windows eDrive feature? - Lenovo Community

Using Windows 10 x64 and Samsung 850 EVO SSD...

Ever since this summer I've gotten BSOD almost once a day. The system reboots and then all is good, but now I have grown tired of it.

DRIVER_IRQL_NOT_LETT_OR_EQUAL (storport.sys)

KERNEL_SECURITY_CHECK_FAILURE

DRIVER_IRQL_NOT_LESS_OR_EQUAL (iaStorA.sys and iaStorF.sys)

I noticed that the Intel System Identification Utility did not pick up the motherboard:

ASUS P9X79

After some google searches I've found out that the chipset (Intel C600 Series Chipset SATA AHCI Controller) might be the problem.

When I tried to update it with the Intel(R) Driver Update Utility 2.6 I got "unknow error".

Could the error be from the major windows 10 update this summer?

Can you please help?

Intel System Identification Utility Reference Number: 0365 5957
Date Created: Thursday, September 29, 2016 1:49:16 AM
ADVANCED

SYSTEM INFORMATION
Computer Manufacturer
Computer Model
Operating System (O/S)	Microsoft Windows 10 (build 10586), 64-bit
Operating System Build (O/S)	10586
Operating System (version)	10.0.10586
O/S Language	0414
System RAM	32 GB
.NET Framework Version	3.5.30729.4926
CD or DVD Device	HL-DT-ST DVDRAM GH22NS50 SCSI CdRom Device
System Hard Drive Overview
System Total Storage Size:	3.0 TB
Physical Drive
Maker
Model
Bus Type
Local Disk D:\	2.0 TB
Used space:	1.0 TB
Free Space:	1019.5 GB
Local Disk G:\	488.3 GB
Used space:	30.0 GB
Free Space:	458.2 GB
Memory Detail
Total Physical Memory	32 GB
Available Physical Memory	26.2 GB
Total Virtual Memory	2.0 GB
Internet Browser [101]	Internet Explorer
Internet Browser Version [101]	11.589.10586.0

GRAPHICS INFORMATION
Graphics Product [1]	NVIDIA Quadro K2000
Video Memory	4.0 GB
Current Graphics Resolution	1920x1080
Current Color Depth	32 Bits Per Pixel

MOTHERBOARD INFORMATION
Manufacturer	not detected (See info above)
Model
AA Number	not detected
BIOS Vendor
BIOS Version	American Megatrends Inc. 4701
BIOS Release Date	05/06/14
System Memory	32 GB
Sound Card	Realtek High Definition Audio

PROCESSOR INFORMATION
Manufacturer	Intel
Model	Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
Intel Processor analysis tools	Intel Processor analysis tools
CPU Speed	3.2 GHz
Link to Processor Specification	Link to Processor Specification
CPU Revision
CPU Type	00
CPU Family	06
CPU Model	2D
CPU Stepping	7

WIRED NETWORKING INFORMATION
Wired Networking Product	Intel(R)82579VbasedNetworkController(OEM)
Driver Version	12.12.50.6
Hardware IDs	PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_06

WIRELESS NETWORKING INFORMATION
Wireless Networking Product
Driver Version
Hardware IDs	*TEREDO

Hello,

there seems to be some strage issue between C236 chipset and Intel Xeon E3 v5 CPUs when Intel TXT(LT) is being used together with a hardware TPM module.

I noticed the following behaviour on an ASRock Rack board with plugged TPM 1.2 as well as on an ASUS Board with plugged TPM 2.0, both C236 chipset. CPU is a Xeon E3-1245 v5.

I found out that if the Xeon TXT (LT) feature is enabled in the BIOS and the TPM is plugged in, but disabled, both systems hang at POST. If the TPM is set to enabled, the system is not stuck at POST anymore, but after POST the system reboots (POST

loop). So if I want to use Intel TXT, the TPM must be physically removed. The TPM is recognized by Windows and working properly. The other way round also works, unplugging the TPM allows then to activate Intel TXT. But as TXT is made for use with a hardware TPM, that makes absolutely no sense.

Can you please assist here on how to solve this issue?

Best regards

Stefan

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!

Two of my HDDs are clicking and have an excessive load-unload cycles.

I'm running 2x Samsung F3 1TB (HD103SJ) in RAID-0 using Z97 chipset Sata 3 ports.

My MB is a ASRock Z97 Extreme6, HDDs firmware is 1AJ10001. MB Bios is P1.33.

I had 13.1.0.1058 RST driver and installed 12.9.2.1000 but the issue persisted.

I have Windows 8.1 Pro 64-bit running on a Samsung 830 Series 256GB SSD, I also have two more HDDs, one Seagate 3TB and one Toshiba 160GB... No issues with these drives.

On my previous setup I was using these HDDs on a X58 chipset Sata 2 ports, also in RAID-0 mode, Intel RST 11 and got no issues.

I think the drives are going idle too fast, because when I need to open or seek for something on the drive, the click starts.

I don't know if this is a BIOS problem or a Intel RST problem, I don't know for sure, but when the computer starts, during post I can hear the click (only once, if I go to UEFI there is no click there and the drive is detected by BIOS).

I tried some troubleshoots, configured (advanced power management, automatic acoustic management, sata aggressive link power management, windows power management) but nothing worked : (

I'm kinda desperate because I have one "click" each 10 seconds (approximately), it means 3600 load-unload cycles in 10 hours!

For now I made the disks off-line through Windows disk management, until I figure out some solution/workaround.

I appreciate any help you can give!

UPDATE!

The problem was solved by installing Intel RST 12 series drivers, power off, disconnect the PSU cable, connect the affected hard drives on another Z97 Sata port and power on the computer.

If I install Intel RST 13 series driver the issue will return, is this a bug with RST 13 series? I don't think my HDD spending one load/unload cycle each 10 seconds is normal.

I'm running a Xeon E3-1246 v3 Haswell-WS CPU in an 1150 socket with a C222 chipset.

What RSTe drivers do I need to download (and where) for this combination (or just the C222 chipset if the CPU doesn't matter)?

One of my customers' servers is running Intel RST 14.8.0.1042 on a Z77 chipset. I have two SATA 2TB WD RE4 HDDs in a RAID1 configuration. One of the drives failed over the weekend, which locked up the server. It would not boot into Windows, instead the Windows System Recovery kept popping up. And it took about 12min to get into that.

I disconnected the offending drive that I identified on the Intel Chipset BIOS screen via S/N, and boom, the server came up at normal speed, within 3 minutes.

Customer is not happy! RAID is supposed to keep on running if a drive fails, which this did NOT happen! Is there a switch I'm missing to "take drive offline if it fails so the OS can keep running"?

I have an Skylake i5-6600K system with Asus Z170 pro gaming motherboard with the latest bios v1105, but transfer speeds from SSD to usb 3.0 external devices are terrible slow and hangs under windows 10. All the external devices are usb 3.0 and works under windows 7 very good and the transfer speeds are normal.

Things I've done.

1. Windows 10 reinstalled (same issue)

2. Bios updated to latest version v1105 (same issue)

3. Windows 10 all drivers installed (same issue)

4. under windows 7 everything working fine transfer speeds are normal.

Why is usb 3.0 under windows 10 so terrible slow and hangs. Can i conclude that this is a driver issue in windows 10.

My hardware

Cpu Intel Skylake i5-6600k

Motherboard Asus Z170 pro gaming

GPU Asus Strix GTX970

Mem crucial ballistix 16GB kit

SSD Samsung SM951 nvme 250GB

SSD Samsung 850 Evo 250GB

OS windows 10 dualboot with windows 7

USB 3.0  sharkoon quickport xt v2 docking station

External HDD usb 3.0 for backup

And some  usb 3.0 thumb drives

Het bericht is bewerkt door: Misterd I added a few screenshots.

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.

Bonjour,

Je constate que depuis que mon Pc est passé sous Windows, la moitié de mes connexions USB ne sont plus détectées et ne fonctionnent plus.

Tout est dans la question.

Que puis-je faire ? Car j'ai bien essayé de mettre à jour les pilotes mais rien n'y fait.

Une seule fois, je suis parvenu en demandant de ré-installer l'ancienne version de pilote à les refaire fonctionner.

Mais depuis peut-être des mises à jour ont ré-écrasées cet effet.

Je ne parviens plus à faire cette manipulation.

Merci de votre aide pour m'aider à rétablir un fonctionnement normal car avec la moitié des prises USB en moins, je peux difficilement travailler.

Cordialement

その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 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

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.

[18BC:07D4][2016-10-06T21:02:40]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{0CE0F48D-1FC7-4B5F-B964-125C12A0C54C} {479B04F4-9810-4E16-91AA-D85AD43885EA} 204'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240.log'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe'

[18BC:07D4][2016-10-06T21:02:40]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:07D4][2016-10-06T21:02:40]i000: Loading managed bootstrapper application.

[18BC:07D4][2016-10-06T21:02:41]i000: Creating BA thread to run asynchronously.

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Command line:

[18BC:0C48][2016-10-06T21:02:41]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Calling Engine.Detect()

[18BC:07D4][2016-10-06T21:02:41]i100: Detect begin, 3 packages

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet35' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Client' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Full' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet45' to value '394802'

[18BC:07D4][2016-10-06T21:02:41]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:41]i103: Detected related package: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, scope: PerMachine, version: 10.1.1.14, language: 0 operation: MajorUpgrade

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: DotNet45, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx64.msi, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i199: Detect complete, result: 0x0

[18BC:07D4][2016-10-06T21:02:49]i200: Plan begin, 3 packages, action: Install

[18BC:07D4][2016-10-06T21:02:49]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'NOT VersionNT64' evaluates to false.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'VersionNT64' evaluates to true.

[18BC:07D4][2016-10-06T21:02:49]i000: ** MBA ** SetupChipsetx64.msi: Converting 'Install' to 'Repair'.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240_0_SetupChipsetx64.msi.log'

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx64.msi, state: Present, default requested: Present, ba requested: Repair, execute: Repair, rollback: None, cache: Yes, uncache: No, dependency: Register

[18BC:07D4][2016-10-06T21:02:49]i299: Plan complete, result: 0x0

[18BC:0C48][2016-10-06T21:02:49]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Getting window handle.

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Calling Engine.Apply(). Window handle: 3212024

[18BC:07D4][2016-10-06T21:02:49]i300: Apply begin

[00CC:0850][2016-10-06T21:02:50]i000: Caching bundle from: 'C:\Users\Bryan\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'

[00CC:0850][2016-10-06T21:02:50]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14

[00CC:1B60][2016-10-06T21:02:50]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.

[00CC:1B60][2016-10-06T21:02:50]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.

[00CC:0850][2016-10-06T21:02:50]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:02:50]i301: Applying execute package: SetupChipsetx64.msi, action: Repair, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to run maintanance mode for MSI package.

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[18BC:07D4][2016-10-06T21:03:11]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:03:11]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi

[00CC:0850][2016-10-06T21:03:11]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}

[00CC:0850][2016-10-06T21:03:11]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\

[18BC:07D4][2016-10-06T21:03:11]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[18BC:07D4][2016-10-06T21:03:11]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[18BC:0C48][2016-10-06T21:03:11]e000: ** MBA ** Unknown error.

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?

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

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