Hi,

I just bought myself a new DOS laptop a month ago. I installed Windows 8.1, and also installed all drivers (and its software) that came from laptop's manufacturer. One of them is IRST.

Unfortunately, I wasn't aware that the drivers they offered on DVD are for Windows 8. I accidentally installed older version of IRST (12.5.0.1066), which I learned not officially support Windows 8.1 (https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22676).

I wanted to uninstall it, and maybe install the latest version. But the uninstaller always fails, and just showing a message: "There is a pending reboot for this product". Of course this statement was incorrect since I have used this laptop for a month, and restarted it a lot of times before. I tried to run the uninstaller from DVD setup file (SetupRST.exe), or directly run setup for latest version; still got the same message.

Is there a way, maybe, to bypass the "reboot-check mechanism" so I could fully uninstall IRST?

Thank you,

Gabriel

Edited: Change "program" to "product".

Hi,

I have a problem with a S2600gz server.

I can't access RAID options on boot. I don't see key combination to make.

I follow this article : Not Prompted to Enter the Intel® RAID BIOS Console During POST for...

But no way, I can't access RAID options, so I can't create RAID 1 to setup my storage.

Do you have any tip to help me ?

Thanks

Chipset Device Software 10.1.1.32 & 10.1.1.5002

Intel 100 Series/C230 Series Chipset Family Thermal Subsystem - A131 driver date is 1970/1/1?

Hi People!

I hope that i can explain the issue with my broken english but i give my best

I own the Sapphire Radeon 390X Nitro and build up a whole complete new system.

Specs are:

Intel I7 6800K

First Mainboard (why first, i'll explain a little later): ASUS X99-A II

Second Mainboard: ASRock Fatal1ty X99X Killer

RAM: 32 GB G.Skill RipJaws 4 RED (DDR4 2400 MHz)

GPU 1: Sapphire Radeon R9 390X Nitro

GPU 2: NVIDIA GeForce 660 (for CUDA)

Issue: Even if i install Windows 10 with the whole bunch of drivers i got terrible DPC / ISR Lags (tested with LatencyMon). The reported files are: dxgkrnl.sys and HDAudBus.sys (sometimes some NVIDIA drivers). The latency spikes are such as great that when i start a game which uses DirectX 11 (maybe 12 too) the sound ingame from the onboard soundcard (Realtek ALC1150) start crackling and popping like an old vinyl, 'caused by Sounddropouts of some drivers.

To prevent some hardware issues i uninstalled the NVIDIA Card and reinstalled Windows 10 completely. The Issue was still there.

I reinstalled windows 10 again and installed only the newest drivers of all components (Intel Chipset, AMD, (tried without and with NVIDIA Card) and so on). The Issue was everytime the same.

After getting frustrated i installed Windows 7 and inside the Games the weird sound crackling was gone. I thought the issue is fixed and gone but i been taught of a better one. I stream sometimes with OBS Studio (Open Broadcaster Software) to Twitch. When i start OBS and put a mediasource into the scene (f.e. a MP4 Animation) the whole system starts to lag and sound crackling again from the finest sort of. LatencyMon say everytime the same two files. Sometimes USBPort.sys where i believe that it depend on the HDAudBus.sys 'cause the drivers, where it doesn't matter if its from microsoft or intel, new or old, fix the issue. Under Advanced Options of  OBS there's a menuepoint which calls: Renderer. Instead of Direct3D 11 i choosed OpenGL and believe it or not - everything works fine. But the Issue is still there 'cause i got sometimes system lags.

After all the problems i been very frustrated and contacted my hardware dealer. I asked him for any solution and he said, that it can depend on the mainboard and want to change it.

So i bought another one, because i read very much problems in the wide net with ASUS and Sound Issues, that i choosed the option to change the whole mainboard manufacturer. So the new second board is finally the ASRock Fatal1ty X99X Killer.

I tested with the new board windows 7 first. And hey... same issue as before. Windows 10 it's the same.

After crawling the whole wide net again i found, that NVIDIA got some problems with Windows 10 and DPC / ISR Latency which results in Sound Dropouts and system lags but i tested it everytime twice. With and without NVIDIA Card and driver after a new reinstall of Windows 7 and Windows 10. I can't see the installation screen anymore of any windows so often i installed it in one month.

So... whats the problem? I posted it synchron in the microsoft forum, obs forum and don't want to put it down in the nvidia forum too, 'cause i don't think that it depend on it.

The Realtek Sounddriver is currently the newest one from the Realtek FTP and should work fine (and believe it - i tried maaaaaaany of them). Tried the Intel USB Drivers old and new ones, AsMedia USB 3 old and new ones. Chipset drivers old and new ones (or even stock installations of windows itself). Shortly: I tried so many things that i don't know what i can do next.

So now my question:

Does anyone has the same issues with an X99/C610 Chipset in combination with an Intel I7 6800K or above? How can i fix it? What can i try next?

And yeah... i overclocked it but the issue is still there when i don't overclock it. The RAM works currently with XMP Profile (for 2400 MHz) but without (2133 MHz) the issue persist too.

It seems that Microsoft implemented some issues with the anniversary update of Windows 10. When Microsoft updated DirectX 11 to DirectX 11.4 (and i read something about a new communication with the drivers) that there are some issues with the communication and produce the high driver latency so that every driver which came after the dxgkrnl.sys and hdaudbus.sys will start to lag because the executiontime of the both drivers are horrible rising. But when they updated DirectX 11 in Windows 10 i think they updated in  Windows 7 too and so the issue is in windows 7 too. Thats the only explanation which i have. Or does someone got another? I hope so or i'll change the CPU too (for preventing an hardware issue if i got a monday cpu).

UPDATE: After changing the CPU to a new one the issue is still there.

Now i'm currently at a state where i don't know what i can do next and need some help.

I recognize that the USB 3 XHCI Drivers for the X79 / X99 Chipset (Enterprise Enthusiast Model) is not stable? Not the Windows 7 Online Drivers nor the Intel Drivers from the Website itself and produce Output / Display Lags too.

Greetings from Germany

Chris

PS: If you reached this line of reading the whole bunch of text then: CONGRATULATION AND RESPECT! Thank you that you want to help me

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!

How can I get RAID alarms in my software? I have Intel Rapid Storage 14.8 on Windows 7; in previous version there was a Command Line Intarface, but I can't find it for this driver version, is there some API that I can use in my software?

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

Hi all. First time posting a message.  I was running Windows XP with two 500gb Seagate Barracuda drives in RAID 1.  I know system is old, but I only use it at work for one small purpose, and it'll be too much expense and effort to upgrade entire system.  Anyway, IRST informed me that one drive could have potential for failure.  With the potential of not finding exact new 500gb drives, I decided to upgrade to 1tb drives.

I followed Intel's instructions at  http://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/000005837.html

I was cruising along and able to get all the way to instruction #16. (so I rebuilt data to new drive, restarted, reset disks to non-raid, removed old drive so it had one drive, rebooted and partitioned new drive to include unallocated space, ie: going from 500gb to 1tb,  turned off system, attached second new drive, and booted up)

When I booted up, first thing I noticed was that the "Control I" option no longer appeared during boot.  Then, at desktop, when I opened up the IRST icon at bottom right of screen, and clicked the "Manage" option (so that I could create new Raid 1 and migrate data to new drive), I got the IAStorUI error message and IRST then closes.  When I go into Disk Management, both disks are active. 

My IRST version is 10.8.0.1003.  Since I am running XP, I am limited as to the upgrade versions.  I don't know if upgrading is the answer, trying to reinstall version 10.8.0.1003, or something else. I need to get this finalized so I can start using this PC. Any suggestions????

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

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.

So I used Intel RST and created my RAID on my win10(idk how but the app says it doesnt support win10 after i clicked into system requirements), but soon I found out my hdd is missing in windows explorer, even though I can still see it in RST for some reasons. I wonder why this would happened, also I am not sure what type of RAID did I create.

For several years I have been happily running a 3-disk RAID5 using Intel Matrix Storage Manager on my office Dell Precision T3500 under Windows 7-64 bit. In May the Microsoft upgrade tool migrated it to Windows 10 (unprompted), and a few weeks later I noticed that the Intel matrix storage console was no longer available, so I can no longer monitor the status of individual disks other than via the BIOS Ctrl-I facility. I can't roll back to Windows 7 because Microsoft has deleted the windows.old data (which I now understand happens after a month).

Last week a disk failure occurred (array degraded notice during startup, slow computer, Error ocurred message by one of the disks), so I have replaced one of the 3 hard drives (WD black 1TB), expecting it to be rebuilt into the array as occurs under Windows 7. This doesn't seem to happen, despite a successful message when the new disk is recognised saying the disk will now be rebuilt in the operating system.

What actually happens is a BSOD immediately after the drive change (I have had two BSODs so far, UNEXPECTED_STORE_EXCEPTION and KERNEL_DATA_INPAGE_ERROR). After an error report/reboot all appears fine but the drive never gets rebuilt and on subsequent reboots shows up as an Unknown Disk in the BIOS utility.

Device manager reports my RAID controller (Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller) is on version 8.9.2.1002 from August 2009. I am unsure whether newer versions (I see it is now called Intel RST) will be compatible with my hardware and am nervous to try in case I end up with a brick. I can't find any advice from Intel. Dell won't help because it's an old system. Microsoft, whose fault this is, said they would get back to me within 2 days but their latest response doesn't fill me with confidence ("Sure, I will look for all the possible solution to get this issue fix and I will email it to you once I found any good solution.").

So my immediate question is:

How can I get my replacement disk recognised and rebuilt into the array?

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!

Hope someone can help me here.

After a fresh install of Windows 8.1 Pro my media type is correctly set under the analyse and optimise function. This is using the in box drivers of Windows 8.1. When I install the latest RST and update the RAID drivers, the media type changes to SSD which is incorrect. The analyse and optimise buttons are now greyed out and I can no longer defrag the hard drives.

I have taken many steps to try and correct this issue but still no luck. The BIOS is set to UEFI and it correctly identifies the HDD. I have also used the F6 driver installation of the latest RAID driver during the Windows install. Media type is still set to SSD.

Intel RST status correctly states that SATA HDD are connected. So is it a Windows problem?

Very frustrating. Any help would be appreciated.

Surely Im not the only person in the world with this problem.

Kind Regards

System Specs

Motherboard: MSI Z87-G45

CPU: Intel 4770K

Memory: Corsair Dominator 32GB

HDD: WD Black 500GB (Raid 0) 128KB Stripe

GPU: Geforce GTX 770

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 attempted to use both the Intel Driver Update Utility to go from 9.2.3.1032 to 10.1.1.14 and the ASUS AsusSetup.exe for MEI_Consumer_V11051189 and both produce an unknown error.

2016:09:23 13:07:32:691:   ME FW Version: 8.1.40.1416

2016:09:23 13:07:32:696:   SKU: DAL. 

2016:09:23 13:07:32:701:   Resolving Dependencies

2016:09:23 13:07:32:706:     Launching '"C:\Users\TheBeast\AppData\Local\Temp\IIFF144.tmp\vc_redist.x86.exe" /install /quiet /norestart'

2016:09:23 13:07:33:243:       Return code: 1638

2016:09:23 13:07:33:248: W   Aborting install

2016:09:23 13:07:33:254:   Updating ME Components size (ARP).

2016:09:23 13:07:33:260:   Setting application size to 24188 kb

2016:09:23 13:07:33:272:   Showing page: Error

2016:09:23 13:07:36:896:   Link: Launching 'C:\Users\TheBeast\Intel\Logs'

-this is from IntelME.log

Action start 13:07:32: WixCheckRebootRequired.

Action ended 13:07:32: WixCheckRebootRequired. Return value 1.

Action ended 13:07:32: INSTALL. Return value 1.

MSI (s) (AC:88) [13:07:32:545]: Note: 1: 1707

MSI (s) (AC:88) [13:07:32:545]: Note: 1: 2205 2:  3: Error

MSI (s) (AC:88) [13:07:32:545]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1707

MSI (s) (AC:88) [13:07:32:545]: Note: 1: 2205 2:  3: Error

MSI (s) (AC:88) [13:07:32:545]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

MSI (s) (AC:88) [13:07:32:545]: Product: Intel(R) Management Engine Components -- Installation completed successfully.

MSI (s) (AC:88) [13:07:32:546]: Windows Installer installed the product. Product Name: Intel(R) Management Engine Components. Product Version: 11.0.6.1194. Product Language: 1033. Manufacturer: Intel Corporation. Installation success or error status: 0.

MSI (s) (AC:88) [13:07:32:549]: Deferring clean up of packages/files, if any exist

MSI (s) (AC:88) [13:07:32:549]: MainEngineThread is returning 0

MSI (s) (AC:D4) [13:07:32:551]: RESTART MANAGER: Session closed.

MSI (s) (AC:D4) [13:07:32:552]: RESTART MANAGER: Session closed.

MSI (s) (AC:D4) [13:07:32:552]: No System Restore sequence number for this installation.

=== Logging stopped: 9/23/2016  13:07:32 ===

MSI (s) (AC:D4) [13:07:32:554]: User policy value 'DisableRollback' is 0

MSI (s) (AC:D4) [13:07:32:554]: Machine policy value 'DisableRollback' is 0

MSI (s) (AC:D4) [13:07:32:554]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (AC:D4) [13:07:32:554]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (AC:D4) [13:07:32:555]: Note: 1: 2265 2:  3: -2147287035

MSI (s) (AC:D4) [13:07:32:555]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (AC:D4) [13:07:32:556]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (s) (AC:D4) [13:07:32:556]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\ac496.msi'

MSI (s) (AC:D4) [13:07:32:557]: Destroying RemoteAPI object.

MSI (s) (AC:54) [13:07:32:557]: Custom Action Manager thread ending.

MSI (c) (3C:54) [13:07:32:558]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (3C:54) [13:07:32:558]: MainEngineThread is returning 0

=== Verbose logging stopped: 9/23/2016  13:07:32 ===

-this is from IntelME_MSI.log

Specs:

Mobo: Asus Sabertooth x79

CPU: Intel i7-3930k

GPU: EVGA 980 SC x2 in SLi

RAM: G.SKILL Ripjaws X Series 32GB (4 x 8GB)

Bootable Hard Disks: Kingston SSDNow V300 120GB SSD x2 in Raid0

Hi,

I recently upgraded to Windows10 Pro 64bit and I noticed that the RST service is not running (icon has a yellow "!" mark) and my computer was slightly slower than before. I'm not very good in these stuff but I feel something's wrong when a driver is not working. I tried restarting the service manually, ran it in compatibility mode, and it all failed. I tried the Intel Update Utility but it did not detect any new drivers. I also tried to install the latest 14.5.0.1081 driver (SetupRST.exe) manually from Intel's download site but it showed a failure message and says "This platform is not supported"

I really need help with this, thanks!

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.