I've been trying to update my graphic driver basically since I forever. I tried using Intel Driver Update Utility and found what's called "Intel Chipset Device Software (INF Update Utility-EXE Only)". So of course, I downloaded it. However, when I'm downloading the actual driver, the progress bar dropped back down and said there's an "Unknown error". I viewed the log file and this is what it says at the end:

[1D68:1A48][2017-07-21T15:43:00]e000: Error 0x80070643: Failed to install MSI package.

[1D68:1A48][2017-07-21T15:43:00]e000: Error 0x80070643: Failed to execute MSI package.

[158C:1E3C][2017-07-21T15:43:00]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[158C:1E3C][2017-07-21T15:43:00]i319: Applied execute package: SetupChipsetx86.msi, result: 0x80070643, restart: None

[158C:1E3C][2017-07-21T15:43:00]e000: Error 0x80070643: Failed to execute MSI package.

[1D68:1A48][2017-07-21T15:43:00]i301: Applying rollback package: SetupChipsetx86.msi, action: Uninstall, path: (null), arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[1D68:1A48][2017-07-21T15:43:01]e000: Error 0x80070643: Failed to uninstall MSI package.

[1D68:1A48][2017-07-21T15:43:01]e000: Error 0x80070643: Failed to execute MSI package.

[158C:1E3C][2017-07-21T15:43:01]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[158C:1E3C][2017-07-21T15:43:01]i319: Applied rollback package: SetupChipsetx86.msi, result: 0x80070643, restart: None

[1D68:1A48][2017-07-21T15:43:01]i329: Removed package dependency provider: {2230F0A4-4566-448D-8F7E-40588907934D}, package: SetupChipsetx86.msi

[1D68:1A48][2017-07-21T15:43:01]i351: Removing cached package: SetupChipsetx86.msi, from path: C:\ProgramData\Package Cache\{2230F0A4-4566-448D-8F7E-40588907934D}v10.1.2.86\

[1D68:1A48][2017-07-21T15:43:01]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{26c576b1-592d-4155-b546-d623123cbe8c}, resume: None, restart: None, disable resume: No

[1D68:1A48][2017-07-21T15:43:01]i330: Removed bundle dependency provider: {26c576b1-592d-4155-b546-d623123cbe8c}

[1D68:1A48][2017-07-21T15:43:01]i352: Removing cached bundle: {26c576b1-592d-4155-b546-d623123cbe8c}, from path: C:\ProgramData\Package Cache\{26c576b1-592d-4155-b546-d623123cbe8c}\

[1D68:1A48][2017-07-21T15:43:01]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{26c576b1-592d-4155-b546-d623123cbe8c}, resume: None, restart initiated: No, disable resume: No

[158C:1E3C][2017-07-21T15:43:01]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[158C:1E3C][2017-07-21T15:43:01]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[158C:1B44][2017-07-21T15:43:01]e000: ** MBA ** Unknown error.

I did not open any other application, as recommended. So how can I fixed this?!

Hi, I have HP Envy 15 with Win 10.

The problem is when I want to turn off the system. The screen goes off but the keyboard is still lit and nothing can be done, only thing is to remove the battery or turn off  "hard".
I am sending an SSU report in the attachment

Hi.

Like many others I tried to upgrade my B960 to i3 2328m & i7 2670m.

Like many others I got 30 min perfectly working laptop after upgrade. (it restarts each 30 minutes).

Downgrade back to B960 solves this problem (no unwilling restarts)

Some users say that its a "low budget laptop" restriction for upgrade incorporated by Intel in HM 70 (at least as an option for oem vendors).

Many others say that resoldering to HM 75/76/77 chipset is the only option to upgrade to "I" CPUs (that reaffirms "low budget" statement)

I tried to think about it for a moment:
we have "limited" chipset
it has a timer, that turns off the power

I bet it is part of the BIOS that checks for "right" plugged CPU.

Also I guess its a chipset firmware CPU verification - so that must be (un / modified) Intel ME firmware.

So my question is:

Where can I get functional description of the HM-70 CPU binding feature in ME firmware?

Olá,

Comprei recentemente um laptop e observei que antes o Intel RST funcionava corretamente. Mas agora ele de repente não está mais funcionando e aparece uma mensagem de erro, aparece que  o Intel RST não está em execução. Gostaria de solucionar isto, pois percebi que o laptop desde então está lento na inicialização e caiu o rendimento dele. Desde já agradeço.

Hi,

I like to set up my C222 RAID controller to be used with XenServer 7.2 but I failed.

I managed to set it up with CentOS7.2 ( kernel 3.10 ) with the packages provided.
But I do not succeed with XEN as it runs on CentOS7.2 but with a 4.4 kernel:

1/ hardware
00:1f.2 RAID bus controller: Intel Corporation 8 Series/C220 Series Chipset Family SATA Controller 1 [RAID mode] (rev 05)
        Subsystem: ASUSTeK Computer Inc. Device 8552
        Kernel driver in use: ahci
# instead of ahci this should become the compiled megasr module

2/ xen
[root@tstxen ~]# cat /etc/redhat-release
XenServer release 7.2.0 (xenenterprise)

[root@tstxen ~]# uname -a
Linux tstxen 4.4.0+10 #1 SMP Thu May 11 16:35:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

So I went to " http://https://downloadcenter.intel.com/ " and downloaded
the Embedded Server RAID Technology 2 RAID Driver for Linux: "ESRT2_Linux_DRV_v17.01.2016.0216_r3.tgz"
#for 7.3 there is another available

Unpacked this on XenServer DDK ( Driver Development Kit ) VM and executed: " make -C /usr/src/kernels/4.4.0+10-x86_64 M=/tmp/megasr-raid5/shim/library/rhel7-64 "
This resulted in modules built, but with lots of warnings ( see logs attached ).

[root@localhost rhel7-64]# ls -l /tmp/megasr-raid5/shim/library/rhel7-64
total 37496
-rw-r--r-- 1 root root        8 Jul 30 08:34 built-in.o
-rw-r--r-- 1 root root      248 Feb 16  2016 Makefile
-rw-r--r-- 1 root root 12828544 Jul 30 08:34 megasr.ko
-rw-r--r-- 1 root root 12581296 Feb 16  2016 megasr-lib.a
-rw-r--r-- 1 root root    70110 Jul 30 08:34 megasr.mod.c
-rw-r--r-- 1 root root   254048 Jul 30 08:34 megasr.mod.o
-rw-r--r-- 1 root root 12576043 Jul 30 08:34 megasr.o
-rw-r--r-- 1 root root       57 Jul 30 08:34 modules.order
-rw-r--r-- 1 root root        0 Jul 30 08:34 Module.symvers

Executing " insmod megasr.ko " results in:

[root@localhost rhel7-64]# insmod megasr.ko
insmod: ERROR: could not insert module megasr.ko: Unknown symbol in module

Therefore can one guide me building a proper kernel module please, perhaps using dkms instead ( /tmp/megasr-raid5/RPM )?

thanks

I am using 7700K this time.

The main board is Asrock Fatality Gaming K6

The OS is Windows 10 Home.

But in Device Manager, there is an exclamation point.

So if you look

"KabyLake PCI Express Root Port # 10 - A2b1" This is the message."

So if you look at properties

"The device does not work properly because Windows can not load the required driver (code 31).

The specified request is an invalid operation on the target device. "

I get this message.

How does this exclamation disappear?

Is there no problem without using this?

I've reinstalled Windows several times to fix this.

But it did not work out.

I want you to solve it.

Thanks for reading.

I tried to update my intel drivers with the uptdate utility, everything went well, but when I tried to install the update an unexpected error didn't let me. Here I attached the logs and my computer information.

Have anyone known Yocto bsp when will support for Intel® Atom™ Processor C3000 Product Family?

Thanks.

I have a Lenovo Thinkpad Yoga 14. Lenovo supplies a tool for keeping the laptop up to date, which is called "System Update 5". This tool indicates there's a critical update for "Intel Management Engine 11.0 Firmware -7 [32,64]/8.1/10 [64]".

When downloading and installing the update by using the Lenovo tool, I get the following error message: "error 8743 Unknown or unsupported platform".

I've installed the Intel driver update manager because I thaught maybe installing it via Intel instead of a Lenovo tool, might help. But the Intel tool indicates that no drivers need to be updated.

What should I do to update the Intel Management Engine? Is there perhaps another Intel tool I could use to update?

P.S. I googled the error message but am unable to understand the complex discussions I found for it, nor any good pointers how to get Intel Management Engine to update.

Computer is an HP Compaq 8200 Elite CMT PC (Model XL508AV) that contains Bus Adapters Intel Desktop/Workstation/Server Express Chipset SATA RAID Controller along with Intel 6 Series/C200 Series Chipset Family USB Enhanced Host Controllers 1C26 and 1C2D.  System was upgraded from the original Win 7 OS to Win 10 and recently upgraded to the latest Win 10 Creators Edition 1703.

System was received from manufacturer with RAID1 installed on two Seagate 7000.120 hard disks (I am the original owner).  POST reports RAID1 as being DEGRADED.  System does not have the Intel Rapid Storage Console software installed.  I accessed your download website, but could not interpret which version of software is appropriate. 

Would appreciate your advice on which version of the Intel Rapid Storage Console/Driver software would be applicable to the above described system to facilitate repair to the RAID system.

Thank you in advance.

Stan

I am updating an old Dell XPS 420 up to win 7 x64 and according to online manuals etc it's based on a X38 Express chipset, i have grabbed the latest version and it comes up at the end with an error saying "Unknown Error", in a nutshell it fails to install.

So i thought about going back a few versions and trying them one by one but for the life of me i can't find anywhere that has a list of old software, so can anyone shed some light on where i may be able to find this software?

To give you a bit more info so you may be able to see the problem i have tried the latest version 10.1.1.42 and here is the log from that install.

[0238:014C][2017-08-05T01:22:07]i001: Burn v3.10.0.1519, Windows v6.1 (Build 7601: Service Pack 1), path: D:\SetupChipset.exe, cmdline: ''

[0238:014C][2017-08-05T01:22:07]i000: Initializing string variable 'CHIPSET_PRODUCT_VERSION' to value '10.1.1.42'

[0238:014C][2017-08-05T01:22:07]i000: Initializing string variable 'INSTALLER_BUILD_VERSION' to value '3.1'

[0238:014C][2017-08-05T01:22:07]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[0238:014C][2017-08-05T01:22:07]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[0238:014C][2017-08-05T01:22:07]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\USERS NAME REMOVED\AppData\Local\Temp\Intel\Logs\Chipset_20170805012207.log'

[0238:014C][2017-08-05T01:22:07]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\SetupChipset.exe'

[0238:014C][2017-08-05T01:22:07]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'D:\'

[0238:014C][2017-08-05T01:22:07]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[0238:014C][2017-08-05T01:22:07]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[0238:014C][2017-08-05T01:22:07]i000: Loading managed bootstrapper application.

[0238:014C][2017-08-05T01:22:07]i000: Creating BA thread to run asynchronously.

[0238:0674][2017-08-05T01:22:07]i000: ** MBA ** Command line:

[0238:0674][2017-08-05T01:22:07]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[0238:0674][2017-08-05T01:22:08]i000: ** MBA ** Calling Engine.Detect()

[0238:014C][2017-08-05T01:22:08]i100: Detect begin, 3 packages

[0238:014C][2017-08-05T01:22:08]i000: Setting string variable 'DotNet35' to value '1'

[0238:014C][2017-08-05T01:22:08]i000: Setting string variable 'DotNet40Client' to value '1'

[0238:014C][2017-08-05T01:22:08]i000: Setting string variable 'DotNet40Full' to value '1'

[0238:014C][2017-08-05T01:22:08]i000: Setting string variable 'DotNet45' to value '460805'

[0238:014C][2017-08-05T01:22:08]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[0238:014C][2017-08-05T01:22:08]i101: Detected package: DotNet45, state: Present, cached: None

[0238:014C][2017-08-05T01:22:08]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent

[0238:014C][2017-08-05T01:22:08]i199: Detect complete, result: 0x0

[0238:014C][2017-08-05T01:23:56]i200: Plan begin, 3 packages, action: Install

[0238:014C][2017-08-05T01:23:56]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[0238:014C][2017-08-05T01:23:56]i052: Condition 'NOT VersionNT64' evaluates to false.

[0238:014C][2017-08-05T01:23:56]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i052: Condition 'VersionNT64' evaluates to true.

[0238:014C][2017-08-05T01:23:56]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[0238:014C][2017-08-05T01:23:56]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\USERS NAME REMOVED\AppData\Local\Temp\Intel\Logs\Chipset_20170805012207_000_SetupChipsetx64.msi_rollback.log'

[0238:014C][2017-08-05T01:23:56]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\USERS NAME REMOVED\AppData\Local\Temp\Intel\Logs\Chipset_20170805012207_000_SetupChipsetx64.msi.log'

[0238:014C][2017-08-05T01:23:56]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[0238:014C][2017-08-05T01:23:56]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[0238:014C][2017-08-05T01:23:56]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[0238:014C][2017-08-05T01:23:56]i299: Plan complete, result: 0x0

[0238:0674][2017-08-05T01:23:56]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[0238:0674][2017-08-05T01:23:56]i000: ** MBA ** Getting window handle.

[0238:0674][2017-08-05T01:23:56]i000: ** MBA ** Calling Engine.Apply(). Window handle: 197312

[0238:014C][2017-08-05T01:23:56]i300: Apply begin

[04D8:08D0][2017-08-05T01:23:59]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, options: 0x7, disable resume: No

[04D8:08D0][2017-08-05T01:23:59]i000: Caching bundle from: 'C:\Users\USERS NAME REMOVED\AppData\Local\Temp\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\SetupChipset.exe'

[04D8:08D0][2017-08-05T01:23:59]i320: Registering bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, version: 10.1.1.42

[04D8:08D0][2017-08-05T01:23:59]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: Active, restart initiated: No, disable resume: No

[04D8:0B64][2017-08-05T01:23:59]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi.

[04D8:0B64][2017-08-05T01:23:59]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\media1.cab.

[04D8:08D0][2017-08-05T01:23:59]i323: Registering package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, version: 10.1.1.42, package: SetupChipsetx64.msi

[04D8:08D0][2017-08-05T01:23:59]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[04D8:08D0][2017-08-05T01:24:02]e000: Error 0x80070643: Failed to install MSI package.

[04D8:08D0][2017-08-05T01:24:02]e000: Error 0x80070643: Failed to execute MSI package.

[0238:014C][2017-08-05T01:24:02]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[0238:014C][2017-08-05T01:24:02]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[0238:014C][2017-08-05T01:24:02]e000: Error 0x80070643: Failed to execute MSI package.

[04D8:08D0][2017-08-05T01:24:02]i301: Applying rollback package: SetupChipsetx64.msi, action: Uninstall, path: (null), arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[04D8:08D0][2017-08-05T01:24:03]e000: Error 0x80070643: Failed to uninstall MSI package.

[04D8:08D0][2017-08-05T01:24:03]e000: Error 0x80070643: Failed to execute MSI package.

[0238:014C][2017-08-05T01:24:03]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[0238:014C][2017-08-05T01:24:03]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[04D8:08D0][2017-08-05T01:24:03]i329: Removed package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, package: SetupChipsetx64.msi

[04D8:08D0][2017-08-05T01:24:03]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\

[04D8:08D0][2017-08-05T01:24:03]i329: Removed package dependency provider: {1B02E5E5-D964-4018-9CB0-9836B78BB375}, package: SetupChipsetx86.msi

[04D8:08D0][2017-08-05T01:24:03]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart: None, disable resume: No

[04D8:08D0][2017-08-05T01:24:03]i330: Removed bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}

[04D8:08D0][2017-08-05T01:24:03]i352: Removing cached bundle: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, from path: C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\

[04D8:08D0][2017-08-05T01:24:03]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart initiated: No, disable resume: No

[0238:014C][2017-08-05T01:24:03]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[0238:014C][2017-08-05T01:24:03]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[0238:0674][2017-08-05T01:24:03]e000: ** MBA ** Unknown error.

Hope it helps a bit

All1

I have run the Intel driver update utility and it suggests "updating" to lower version numbers for all drivers except one for which it recommends the exact same driver. Did Intel forget how to count or what? I chose not to "update" these drivers but if I wasn't paying attention, I'd have ended up downgradingt to older versions.

The issue pertains to both chipset and graphics drivers but there's no subforum for this scenario and category 'chipset' is the only thing that comes close.

I have a Asus desktop running Win 7 that has become curiously slow over the past year or so. I suspect that it has to do with Microsoft updates somewhere down the line, and that the slowness is HDD-related.

Having tried all the usual tricks including full system reinstall and disk repartitioning, I wanted to try and update the chipset drivers, but Asus has no updates to offer. So I tried the generic Chipset_10.1.1.42_Public downloadable instead. The installer runs fine but proceeds to fail with an "Unknown error". I get a bunch of logs but haven't been able to decipher them.

I will enclose a few files for more background information. First, the logs themselves are enclosed in a zip file. Next, I downloaded and run the Intel SSU utility, the output of which enclosed as well. Also, Intel ChipUtil.exe prints the following output:

As noted, this is a fresh re-install of Windows 7 (Home Premium edition, 32-bit) from the Asus recovery DVD, as I got tired of trying to fix the old installation and instead opted to start again from scratch. However, this hasn't cured the lethargic slowness, and I am still struggling at snail pace. Please help if you can in any way.

Hello

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

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

Yet it has been reported long time ago !

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

Thank you

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.

Hi,

We have few HP Z440 workstations with RAID 1+0 configuration. We have 32GB RAM, 4 x 3TB SATA HDD, Intel Xeon CPU E5-1603 v3 @ 2.80GHz and Intel C600+/C220+ series chipset SATA RAID Controller. We are using Intel Rapid Storage Technology tool to configure RAID volume. We have one volume and the volume should be 5.3TB in size.

The problem is after installation of Windows OS and our application, the computer becomes very slow and this is occurring very often. If I check the RAID status, it shows "Initialize" in Rapid Intel Storage Technology console.

Can we get the reason why RAID moves to "Initialize" automatically. And is there anyway we can stop or optimize this activity. We have observed that when RAID status is "Normal", the computer runs fast.

Can anybody tell me the reason and how can we improve the RAID performance or stop or configure the Initialization?

Any help would be appreciated.

Thanks & Regards,

Sourav

Hello,

We are a startup company for digital marketing training courses in bangalore btm Koramangala and is looking to buy around 5 PCs - The tasks that will be performed light video creation, light to medium photoshop tools, and few Internet based marketing tools. Which Intel chipset can you guys suggest, I got a quote from a local retailer for Intel Dual core chips - Is that fine or I need to consider latest gen i3 chipsets. Please advice and also if you can suggest the RAM/Video card to go along with it.

Any help will be appreciated.

Regards,

Sandeep

Intel RST 14.8.16.1063 is reporting one or more events but not showing me what those events are.

I am running Windows 10 using an ASUS motherboard with a simple 2-drive RAID mirror.

I have been tasked with rebuilding a handful of old(ish) Dell E6330 laptops. All with the same hardware specs, 7 series/C216 chipset family. I am losing sleep over this and could really use a fresh perspective.

I am starting from a base Win 7 64 bit OS, provided by Dell. I have been able to update all of the drivers including BIOS except the "Intel 3.0 extensible host controller" whenever i try to install it, it gives me the BSOD just after installation.

When i go into device manager, it shows installed, but none of the usb 3.0 ports work (which is all of them). However, when i hook the laptop up to a docking station, i can get the 2.0 ports to work, so i have a work around.

I noticed that after i get the BSOD, under "Universal Serial Bus Controllers" in device manager, there is a Unknown Device listed in there. Though there is no yellow exclamation identifying there is something wrong, when i open it, it says "No drivers are installed for this device" when i select update driver it says the best driver software for your device is already installed (Intel R USB 3.0 Root Hub).

Any help is appreciated!

Please help me configure RST 13.1.0.1058 on W10 x64 OS after moving SSD from C:\ to G:\.

"Intel RST Service is not running"

I'm lost. Please clue me in. :-) Thanks! -Ynot?-