I have reported this already about 8 months ago while being in the insider program over the Microsoft feedback tools, so I am very pleased that this bug still is present in the final version...

The problem is simple, Dell Venue 8 Pro shows this problem. I also have found reports about this on other forums by Lenovo and Asus, so I think it's a problem with the Intel BayTrail or DPTF drivers.

The problem is simple:

1.) Let Windows idle

2.) Open TaskManager (or for example CPUz) and monitor CPU throttling

Under Windows 10, the CPU throttling seems to be broken for at least Intel Atom BayTrail (3700 series). The CPU always stays around 1.3-1.7GHz @ 1-3% CPU load.

The same (normal) idle behavior under Windows 8.1 results in the processor correctly using the lowest energy states between 0.5-0.8GHz.

This results in a way noticeable faster battery drain.

2nd bug, mostly related: The battery drain in connected standby is about 3 times higher (~1.1mW/h), compared to Windows 8.1 (~0.33mW/h). The normal drain, by Microsoft itself, is 0.3mW/h for a device supporting connected standby mode.

Heres a video showing problem 1:

https://dl.dropboxusercontent.com/u/14937594/win10cpubug.mp4

You can see how the CPU throttling is not working properly always staying at mid-highe throttling state of the Atom CPU. Normal throttling would be 0.8GHz.

Here is how it should correctly be:

https://dl.dropboxusercontent.com/u/14937594/normal-idle-throttling.mp4

(sorry for the bad quality)

On my desktop PC and my Ultrabook the throttling work fine, so it seems a problem related to the Atom BayTrail drivers under Windows 10 or a combination of things.

Windows 8.1 64bit PRO updated to Windows 10 PRO - Intel Rapid Start Technology 3.0.0.1053_WHQL

I see this irstrtsv error in the Event Viewer.

id event 0

The description for Event ID 0 from source irstrtsv cannot be found. Either the component that raises this event is not installed on your local computer, or the installation is corrupted. You can install or repair the component on the local computer.

irstrtsv
"Error: Unable to read LBA sector directly. : The parameter is incorrect."

I do not see a performance issue due to the error.

This irstrtsv error occurs when the system starts, there is a cluster of 5 errors repeats every 5 minutes with another cluster of 5 irstrtsv errors and continues until I shut it down.

I tried to uninstall and reinstall intel rapid start software but always with the same result.

Mainboard: Asus Z87 deluxe

IRST driver installed: intel rst 14.5.2.1088 WHQL

IRS  driver installed:  intel Rapid Start Technology 3.0.0.1053_WHQL

bios mode: RAID

HDD: 2 SSD + 3 HDD (2TB) RAID 5

Sorry for my english, I'm having trouble installing the latest version of the Intel ® Rapid Storage Technology 13.2.4.100 on my Asus Z87 Deluxe and Windows 8.1 64bit.

The setup ends up saying that the installation is complete but in device manager, in the properties of the drivers I still see the old version 13.1.0.1058.

So I manually installed the drivers through the "update drivers" in "Device Manager" by selecting the inf file, now the version of the drivers in "Device Manager" is correct, but when I start the client Intel ® Rapid Storage Technology (help -> about) I still see the old version 13.1.0.1058, how do I update everything completely?

In add / remove programs I can not find IRST to remove it and try to reinstall !!

Help me please. Thanks !

I havent been able to install AHCI driver for my laptop and its working like crap, the disk charge rises to 100% wich makes practically impossible to work, thanks in advance for any help that can be provided,

Sorry for my bad English, I'm From Colombia

Hi

I did a clean install of windows 10 pro today, and installed the Intel RSTe Drivers & Software Set v14.5.0.1081 WHQL.

When I try to enable the adapter write back cache mode (disabling the Windows write cache), after a few seconds Windows shows 100% disk usage, becomes super slow and crashes after 10 minutes.

I tried reinstall the drivers, I also tried with older drivers with the same result

Anyone else or is this just me? I have been browsing Google and forums without any solution.

I'm using 2x Intel 520 SSD @ raid0 with my z87 chipset

I have attached a dxdiag for full specs

I started a discussion over at Logitech's support form about the fact that the Logitech G35 headset is not compatible with the USB 3.0 Drivers for the Z97 (Intel® USB 3.0 eXtensible Host Controller Driver).

It was suggested that I contact Intel about the issue, considering the headset works prior to the installation of the USB3.0 drivers. Once the drivers are installed, the headset no longer is recognizable by the computer. The common suggested solution would be to go to Device Manager, expand the sound, video and game controllers category, click on the headset and update the driver, however this is not an option because the Logitech G35 no longer shows up under the sound, video and game controllers. Instead it shows up under Universal Serial Bus Controllers as "unknown device" and you are unable to install, reinstall, or update the drivers automatically, or select the specific driver for it to use (which would be the standard USB Audio Device Driver).

This also is also seeming to be not just an issue with me, but with anyone using the Logitech G35 and the Z97 motherboard, as it has been tested with several configuration.

It should be noted that this is not an issue with other Logitech Headsets, such as the G930. They work fine with the USB 3.0 Drivers installed.

Thanks,

Dane

Ispecified the problem in aprevious post (Intel Z97 Chipset USB 3.0 drivers and Logitech G35 Headset incompatible.) butI have notreceived anyresponse, so I'lldescribethe problemagain. I ownheadphones A4Tech Bloody G501. I noticed thatthe headphonesdriveris incompatiblewithIntelUSB 3.0driver. InWindows7 SP1after anewinstallationof the operating system (without installing theIntelUSB 3.0driver) headphonesworks perfectly, as well as their software. AfterIinstall theIntelUSB 3.0driver, the headphonesare notrecognized by the system. If Iuninstall theIntelUSB 3.0driver,headsetworks perfectly inUSB 2.0 port and in USB3.0 port. On my systemmotherboard (Gigabyte GA Z97X Gaming 3) I have Z97 chipset. There alsohave anolderdesktopthatheadphonesworks perfectly, motherboard'snot haveUSB3.0 (sodid notneedIntel USB 3.0driver)and I haveaDell Inspiron N5110 laptop, it hasUSB 3.0 but usestheUSB 3.0driver from Renesas, theheadsetalsoworks perfectlyon mylaptop. NowI useWindows8.1 andtheIntelUSB 3.0driveris integratedin OS(no separateinstallation required),my problem isthat I can notuninstall the drivertouseheadphonesthatcan not usethe mouseand keyboard (USB connected). Howeverthiscould notbe a solution becausewhenIuninstall the IntelUSB3.0driver USB 3.0 portsbecomes USB 2.0 (transfer rate is reducedto the value ofUSB2.0).Itried to install Intel(R) USB 3.0 eXtensible Host Controller:  3.0.4.65, Intel(R) USB 3.0 eXtensible Host Controller:  3.0.5.69 and the driver from my motherboard CD (I'm not surewhich version) butwith the same result, headphonesdo not workafterinstalling the driver.

What can we do? Ialso needheadphonesandUSB 3.0!! I think thedriverhas someproblems since it isincompatible withtwo or maybe more manufacturers, in this case Logitech G35 and A4TechBloodyG501, totally differentmanufacturers !! See here: Intel Z97 Chipset USB 3.0 drivers and Logitech G35 Headset incompatible.

Intel Z3700 Driver for Asus T200TA Windows 10 Pro 64Bit.

Downloaded from Asus site but while installing on Windows 10 Pro. not allow to install it.. getting some error.

So my touch screen and display and other chip-set related are not working...

Pls provice me link for driver for Intel Z3700   Windows 10 Pro 64Bit.

Trying to install Windows 8.1 (64Bit) Chipset on Windows 10 Pro.

getting blow error.

The setup program ended prematurely because of the following error:

LOG FILE:

13:16:50:218:   Dumping MSI properties (0 total)
13:16:50:226:   Exit code: 1603
13:16:50:238:   >>> Log End
13:17:37:869:   >>> Log start
13:17:37:869:   Core version: 2.0.5
13:17:37:885:   Setup version: 2.0.0.11
13:17:37:885:   Command line: "C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Setup.exe"
13:17:37:900:   OS data: 6-2-1-0 64-bit
13:17:37:900:   System up time: 810 sec
13:17:37:916:   Current UI language: 0809
13:17:37:932:   Language folder: C:\Users\KARTIK~1\AppData\Local\Temp\IIF5FF8.tmp
13:17:37:994:     Found C:\Users\KARTIK~1\AppData\Local\Temp\IIF5FF8.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 2
13:17:38:025:   Relaunching setup as elevated
13:17:38:541:   Dumping MSI properties (0 total)
13:17:38:557:   Exit code: 0
13:17:38:557:   >>> Log End
13:17:38:603:   >>> Log start
13:17:38:603:   Core version: 2.0.5
13:17:38:619:   Setup version: 2.0.0.11
13:17:38:619:   Command line: "C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Setup.exe"
13:17:38:635:   OS data: 6-2-1-0 64-bit
13:17:38:635:   System up time: 811 sec
13:17:38:650:   Current UI language: 0809
13:17:38:650:   Language folder: C:\Users\KARTIK~1\AppData\Local\Temp\IIF62D6.tmp
13:17:38:697:     Found C:\Users\KARTIK~1\AppData\Local\Temp\IIF62D6.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 2
13:17:38:713:   Package version: 2.0.1.14
13:17:38:728:   Installed version: <Not installed>
13:17:38:744:   This is a clean install
13:17:38:744:   Setup mode: Installation
13:17:38:760:   Looking for OS: 6.0
13:17:38:760:   OS check passed
13:17:38:775:   .NET not required, skipping requirement check
13:17:38:775:   Driver source is C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Drivers
13:17:38:791:   Using folder 'C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Drivers' as the driver source
13:17:38:791:   Scanning all active devices
13:17:38:838:   Scanning Audio\isstrtc.inf (Name: Audio\isstrtc.inf, Version: 603.9600.1948.44046)
13:17:38:853:     Section with the best match: IntelSST.NTamd64
13:17:38:853:       Device: ACPI\VEN_8086&DEV_0F28&SUBSYS_1043173D (Intel SST Audio Device (WDM))
13:17:38:869:       Device: ACPI\VEN_8086&DEV_0F28&SUBSYS_1043175D (Intel SST Audio Device (WDM))
13:17:38:869:       Device: ACPI\VEN_8086&DEV_0F28&SUBSYS_104317CD (Intel SST Audio Device (WDM))
13:17:38:885:       Device: ACPI\VEN_8086&DEV_0F28&SUBSYS_1043182D (Intel SST Audio Device (WDM))
13:17:38:900:     MUP OS bits: 0x3FFFF
13:17:38:900:   Adding Audio\isstrtc.inf to the map...
13:17:38:916:   Scanning Camera\ar0543.inf (Name: Camera\ar0543.inf, Version: 13.11.48.883)
13:17:38:932:     Section with the best match: Standard.NTamd64
13:17:38:932:       Device: ACPI\VEN_INT&DEV_33F3&SUBSYS_173D1043 (Camera Sensor AR0543)
13:17:38:947:       Device: ACPI\VEN_INT&DEV_33F3&SUBSYS_175D1043 (Camera Sensor AR0543)
13:17:38:963:       Device: ACPI\VEN_INT&DEV_33F3&SUBSYS_17CD1043 (Camera Sensor AR0543)
13:17:38:963:     MUP OS bits: 0x36D54
13:17:38:978:   Adding Camera\ar0543.inf to the map...
13:17:38:994:   Scanning Camera\camera.inf (Name: Camera\camera.inf, Version: 13.12.7.931)
13:17:39:010:     Section with the best match: Device.NTamd64
13:17:39:010:       Device: VIDEO\INT0F38 (Intel(R) Imaging Signal Processor 2400)
13:17:39:041:         Matched with: VIDEO\INT0F38
13:17:39:057:         Current driver: oem46.inf
13:17:39:057:           Name: , Provider: Intel, Version: 603.9600.1948.34944, Section: camera
13:17:39:072:         This is a downgrade
13:17:39:072:     MUP OS bits: 0x3FFFF
13:17:39:088:   Adding Camera\camera.inf to the map...
13:17:39:103:   Scanning Camera\hm2056.inf (Name: Camera\hm2056.inf, Version: 13.11.48.679)
13:17:39:119:     Section with the best match: Standard.NTamd64
13:17:39:119:       Device: ACPI\VEN_HIMX&DEV_2056&SUBSYS_17CD1043 (Camera Sensor HM2056)
13:17:39:135:       Device: ACPI\VEN_HIMX&DEV_2056&SUBSYS_173D1043 (Camera Sensor HM2056)
13:17:39:135:     MUP OS bits: 0x36D54
13:17:39:150:   Adding Camera\hm2056.inf to the map...
13:17:39:182:   Scanning DPTF\Dptf.inf (Name: DPTF\Dptf.inf, Version: 07.1.0.171)
13:17:39:197:     Section with the best match: IntelDevice.NTamd64.6.1
13:17:39:197:       Device: ACPI\INT3400 (Intel(R) Dynamic Platform & Thermal Framework Driver)
13:17:39:213:       Device: ACPI\INT3403 (Intel(R) Dynamic Platform & Thermal Framework Generic Participant Driver)
13:17:39:213:       Device: ACPI\INT3401 (Intel(R) Dynamic Platform & Thermal Framework Processor Participant Driver)
13:17:39:228:       Device: ACPI\INT3406 (Intel(R) Dynamic Platform & Thermal Framework Display Participant Driver)
13:17:39:228:       Device: ACPI\INT3407 (Intel(R) Dynamic Platform & Thermal Framework Power Participant Driver)
13:17:39:244:       Device: ACPI\INT3409 (Intel(R) Dynamic Platform & Thermal Framework Ambient Participant Driver)
13:17:39:260:     MUP OS bits: 0x3FE00
13:17:39:260:   Adding DPTF\Dptf.inf to the map...
13:17:39:353:   Scanning GFX\60398.inf (Name: GFX\60398.inf, Version: 10.18.10.3740)
13:17:39:353:     No section match
13:17:39:369:     MUP OS bits: 0x30000
13:17:39:385:   Adding GFX\60398.inf to the map...
13:17:39:416:   Scanning GPIO\iaiogpioe.inf (Name: GPIO\iaiogpioe.inf, Version: 603.9600.1948.30590)
13:17:39:416:     Section with the best match: Intel.NTamd64
13:17:39:432:       Device: ACPI\INT33FC (GPIO Controller)
13:17:39:463:         Matched with: ACPI\INT33FC
13:17:39:478:         Current driver: oem51.inf
13:17:39:494:           Name: , Provider: Intel Corporation, Version: 603.9600.1948.30590, Section: GPIO_Device.NT
13:17:39:494:     MUP OS bits: 0x36D54
13:17:39:510:   Adding GPIO\iaiogpioe.inf to the map...
13:17:39:541:   Scanning GPIOVirtual\iaiogpiovirtual.inf (Name: GPIOVirtual\iaiogpiovirtual.inf, Version: 603.9600.1948.30590)
13:17:39:541:     Section with the best match: Intel.NTamd64
13:17:39:557:       Device: ACPI\INT0002 (GpioVirtual Controller)
13:17:39:588:         Matched with: ACPI\INT0002
13:17:39:588:         Current driver: oem52.inf
13:17:39:603:           Name: , Provider: Intel Corporation, Version: 603.9600.1948.30590, Section: Driver.NT
13:17:39:619:     MUP OS bits: 0x36D54
13:17:39:619:   Adding GPIOVirtual\iaiogpiovirtual.inf to the map...
13:17:39:650:   Scanning I2C\iaioi2ce.inf (Name: I2C\iaioi2ce.inf, Version: 603.9600.1948.29470)
13:17:39:650:     Section with the best match: Intel.NTamd64
13:17:39:666:       Device: ACPI\VEN_8086&DEV_0F41&REV_0002 (I2C ES2 Controller)
13:17:39:666:       Device: ACPI\VEN_8086&DEV_0F41&REV_0003 (I2C Controller)
13:17:39:682:       Device: ACPI\VEN_8086&DEV_0F41&REV_0004 (I2C Controller)
13:17:39:697:       Device: ACPI\VEN_8086&DEV_0F41 (I2C Controller)
13:17:39:713:         Matched with: ACPI\VEN_8086&DEV_0F41&REV_0006
13:17:39:728:         Current driver: oem6.inf
13:17:39:728:           Name: Chipset, Provider: INTEL, Version: 10.1.1.10, Section: Needs_NO_DRV
13:17:39:744:     MUP OS bits: 0x36D54
13:17:39:744:   Adding I2C\iaioi2ce.inf to the map...
13:17:39:775:   Scanning MBI\MBI.inf (Name: MBI\MBI.inf, Version: 603.9600.1948.15591)
13:17:39:775:     Section with the best match: Standard.NTamd64
13:17:39:791:       Device: ACPI\VEN_INT&DEV_33BD&REV_0002 (Intel(R) Sideband Fabric Device)
13:17:39:822:         Matched with: ACPI\VEN_INT&DEV_33BD&REV_0002
13:17:39:822:         Current driver: oem8.inf
13:17:39:838:           Name: Standard, Provider: Intel Corporation, Version: 603.9600.1001.61374, Section: MBI_Device.NT
13:17:39:853:     MUP OS bits: 0x36D54
13:17:39:853:   Adding MBI\MBI.inf to the map...
13:17:39:869:   Scanning NFC\NXP\NxpNfpProvider_Win8.inf (Name: NFC\NXP\NxpNfpProvider_Win8.inf, Version: 6.5.9.0)
13:17:39:885:     Section with the best match: Standard.NTAMD64
13:17:39:900:       Device: ACPI\NXP5442 (NXP NearFieldProximity Provider)
13:17:39:900:     MUP OS bits: 0x3FFFF
13:17:39:916:   Adding NFC\NXP\NxpNfpProvider_Win8.inf to the map...
13:17:39:932:   Scanning PMIC\pmic.inf (Name: PMIC\pmic.inf, Version: 603.9600.1948.27988)
13:17:39:947:     Section with the best match: Intel.NTamd64
13:17:39:947:       Device: ACPI\VEN_INT&DEV_33FD&REV_0002 (Intel(R) Power Management IC Device)
13:17:39:963:     MUP OS bits: 0x36D54
13:17:39:963:   Adding PMIC\pmic.inf to the map...
13:17:39:994:   Scanning SPI\iaiospi.inf (Name: SPI\iaiospi.inf, Version: 603.9600.1948.28229)
13:17:40:010:     Section with the best match: Intel.NTamd64
13:17:40:010:       Device: ACPI\VEN_8086&DEV_0F0E&REV_0000 (SPI ES0 Controller)
13:17:40:025:       Device: ACPI\VEN_8086&DEV_0F0E&REV_0001 (SPI ES1 Controller)
13:17:40:025:       Device: ACPI\VEN_8086&DEV_0F0E&REV_0002 (SPI ES2 Controller)
13:17:40:041:       Device: ACPI\VEN_8086&DEV_0F0E&REV_0003 (SPI Controller)
13:17:40:041:       Device: ACPI\VEN_8086&DEV_0F0E&REV_0004 (SPI Controller)
13:17:40:057:       Device: ACPI\VEN_8086&DEV_0F0E (SPI Controller)
13:17:40:072:     MUP OS bits: 0x36D54
13:17:40:072:   Adding SPI\iaiospi.inf to the map...
13:17:40:103:   Scanning TXEI\TXEI.inf (Name: TXEI\TXEI.inf, Version: 1.0.0.1064)
13:17:40:103:     Section with the best match: Intel.NTamd64.6.1
13:17:40:119:       Device: PCI\VEN_8086&DEV_0F18 (Intel(R) Trusted Execution Engine Interface )
13:17:40:151:         Matched with: PCI\VEN_8086&DEV_0F18&SUBSYS_173D1043&REV_0D
13:17:40:151:         Current driver: oem56.inf
13:17:40:166:           Name: TXEI64, Provider: Intel, Version: 1.1.0.1064, Section: TEE_DDI_x64
13:17:40:166:         This is a downgrade
13:17:40:182:     MUP OS bits: 0x36C00
13:17:40:197:   Adding TXEI\TXEI.inf to the map...
13:17:40:213:   Scanning UART\iaiouart.inf (Name: UART\iaiouart.inf, Version: 603.9600.1948.32979)
13:17:40:213:     Section with the best match: Intel.NTamd64
13:17:40:229:       Device: ACPI\80860F0A (UART Controller)
13:17:40:260:         Matched with: ACPI\80860F0A
13:17:40:276:         Current driver: oem24.inf
13:17:40:276:           Name: Chipset, Provider: Intel, Version: 9.4.4.1005, Section: COM
13:17:40:291:     MUP OS bits: 0x36D54
13:17:40:291:   Adding UART\iaiouart.inf to the map...
13:17:40:322:   Scanning WCE\MonzaX.inf (Name: WCE\MonzaX.inf, Version: 1.0.11.0)
13:17:40:322:     Section with the best match: Impinj.NTamd64
13:17:40:338:       Device: ACPI\IMPJ0001 (Impinj RFID Device (MonzaX 2K) A)
13:17:40:338:       Device: ACPI\IMPJ0002 (Impinj RFID Device (MonzaX 2K) B)
13:17:40:354:       Device: ACPI\IMPJ0003 (Impinj RFID Device (MonzaX 8K))
13:17:40:369:     MUP OS bits: 0x36D54
13:17:40:369:   Adding WCE\MonzaX.inf to the map...
13:17:40:385:   Hardware check: Older version of some INFs are being installed.
13:17:40:385:   Reading config file : C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Config.xml
13:17:40:401:   Read SocPackageInfo Version : 0x102
13:17:40:416:   Reading string value
13:17:40:432:   Read XML SocPackageInfo Root : HKEY_LOCAL_MACHINE, Key : SOFTWARE\Intel\SOCPackageInfo, Value : VersionNumber, Version string name : Version, version string : 102
13:17:40:432:   Registry key SOFTWARE\Intel\SOCPackageInfo does not exist or can not be read. Error : Unable to read registry value : VersionNumber - Error Code : 2. Assuming the installed version is oldest. Proceeding with installation.
13:17:40:447:   Preparing UI
13:17:40:463:   Reading config file : C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Config.xml
13:17:40:463:   /Configuration/TitleOverride section in the configuration file is either missing or contains no data. Skipping version title override.
13:17:40:479:   Reading config file : C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Config.xml
13:17:40:494:   /Configuration/TitleOverride section in the configuration file is either missing or contains no data. Skipping version title override.
13:17:40:525:   Showing dialog: WELCOME
13:17:43:301:   Showing dialog: LICENSE
13:17:46:129:   Showing dialog: CONFIRM
13:17:46:988:   Started installation thread
13:17:47:004:   Setup mode
13:17:47:004:   Showing dialog: PROGRESS
13:17:47:020:   Read INF file name : iaioi2ce.inf
13:17:47:035:   Read INF file name : iaiogpioe.inf
13:17:47:035:   Read INF file name : iaiouart.inf
13:17:47:051:   Read INF file name : iaiospi.inf
13:17:47:051:   Read INF file name : iaiogpiovirtual.inf
13:17:47:067:   Read INF file name : MBI.inf
13:17:47:082:   Read INF file name : pmic.inf
13:17:47:082:   Read INF file name : isstrtc.inf
13:17:47:098:   Read INF file name : 60398.inf
13:17:47:113:   Read INF file name : camera.inf
13:17:47:113:   Read INF file name : hm2056.inf
13:17:47:129:   Read INF file name : ar0543.inf
13:17:47:145:   Read INF file name : TXEI.inf
13:17:47:145:   Read INF file name : NxpNfpProvider_Win8.inf
13:17:47:160:   Read INF file name : Dptf.inf
13:17:47:176:   Read INF file name : MonzaX.inf
13:17:47:176:   NO BIOS File to install!
13:17:47:192:   Pre-Installing Drivers...
13:17:47:192:   Pre-installing driver file C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Drivers\I2C\iaioi2ce.inf
13:17:47:207:   x64 OS running
13:17:47:223:   Difx64 execute cmd "C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\x64\Drv64.exe" -driverinf C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Drivers\I2C\iaioi2ce.inf -flags 0 -keypath Software\Intel\Difx64 -preinstall
13:17:47:270:   Read registry subkey Code and value 2
13:17:47:285:   Read registry subkey Reboot and value 0
13:17:47:301: E Unable to pre-install driver file : C:\Users\kartikpatts\Desktop\Asus BD\Asus Driver\SOCPackage_Intel_BayT_T200TA_Win81_64_VER102_2\SOCPackage_Intel_Win81_64_VER102\Drivers\I2C\iaioi2ce.inf - error code : 2

13:17:47:301: E Uninstalling drivers that were previously pre-installed by DriverPackagePreInstall...
13:17:47:317: E Setup aborted!
13:17:47:332:   m_nCurrentIndex : 4
13:17:47:363:   Showing dialog: FINISH

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 want to upgrade BIOS for an Asus Z87-A motherboard with Haswell Core i7 -4770 processor. The latest BIOS version on Asus website is from June 2014. But I don't want to use the BIOS version that includes microcode that disables TSX as per errata HSW136. Can I safely assume that since this errata was published in August 2014, the BIOS upgrade doesn't contain that microcode? I just want to be sure since the owner of this motherboard will kill me if I manage to disable TSX on his computer.

Hi.

So, Windows 10 just released and while most Intel product are compatible in this Chipset INF Update:

Intel® Download Center

And there's also quite the older Xeon supported too.

But... Where is the X58 Express Chipset?! (First-gen High-End Core i7 line - 920, 950...)

I want to do the update to Windows 10 but I can't do so without the chipset driver.

Will Intel support it sometime soon? Or will the Windows 7 driver even work?

Thanks!

My computer:

Motherboard: Gigabyte X58A-UD3R (rev 1)

CPU: Core i7 950

RAM: 6GB (3*2GB) of DDR3 1333MHz (Downclocked @ 1066MHz)

GPU: EVGA nVidia GeForce 680 2GB

Storage: 1*Sata 3Gbps 90GB OCZ, 1*4TB HGST 7200rpm, 1*1TB WD Green, 1*1TB WD Blue 7200rpm

Since Intel RST RAID driver 13.x >> 14.x, my RAID 1 disk is shown as SSD on the program Optimization of Windows, therefore I can't defrag the files on it.

With the old 12.9.x RAID driver, the disks are shown correctly (I've tried every version and last working w/o the problem is the 12.9.x).

The same problem is reported on Microsoft forum, and it is confirmed as Intel RST driver problem.

Any suggestion?

My configuration:
Intel Chipset Z77 (AsRock Extreme 6), 2x1TB WD Black Caviar, 1x Crucial SSD 480GB SATA3, Intel i7 3770k cpu.
Windows 8/8.1/10 Pro 64 bit.

I have reported this already about 8 months ago while being in the insider program over the Microsoft feedback tools, so I am very pleased that this bug still is present in the final version...

The problem is simple, Dell Venue 8 Pro shows this problem. I also have found reports about this on other forums by Lenovo and Asus, so I think it's a problem with the Intel BayTrail or DPTF drivers.

The problem is simple:

1.) Let Windows idle

2.) Open TaskManager (or for example CPUz) and monitor CPU throttling

Under Windows 10, the CPU throttling seems to be broken for at least Intel Atom BayTrail (3700 series). The CPU always stays around 1.3-1.7GHz @ 1-3% CPU load.

The same (normal) idle behavior under Windows 8.1 results in the processor correctly using the lowest energy states between 0.5-0.8GHz.

This results in a way noticeable faster battery drain.

2nd bug, mostly related: The battery drain in connected standby is about 3 times higher (~1.1mW/h), compared to Windows 8.1 (~0.33mW/h). The normal drain, by Microsoft itself, is 0.3mW/h for a device supporting connected standby mode.

Heres a video showing problem 1:

https://dl.dropboxusercontent.com/u/14937594/win10cpubug.mp4

You can see how the CPU throttling is not working properly always staying at mid-highe throttling state of the Atom CPU. Normal throttling would be 0.8GHz.

Here is how it should correctly be:

https://dl.dropboxusercontent.com/u/14937594/normal-idle-throttling.mp4

(sorry for the bad quality)

On my desktop PC and my Ultrabook the throttling work fine, so it seems a problem related to the Atom BayTrail drivers under Windows 10 or a combination of things.

I have a server with a RAID10 array.  It was setup using the Intel Matrix Storage software.  There are (4) 160G Seagate drives configured for a total of 300G.   The current drive has two partitions of 45G and 255G and the 45G partition only has about 7G of free space.  I would like to know the process to increase the size of the array.

Any help would be appreciated. 

I'm getting a shutdown bug on a Z77 Chipset. (Gigabyte g1 sniper 3)

Before my computer is shutting down i hear my harddrives just spinning on again before my PC is going off.

They do not start completely again, they are being interrupted by the shutdown then.

I tested these versions:

12.5.0.1066

12.8.0.1016

12.8.4.1000

12.8.6.1000

With the original version of windows instalacion (12.0.1.1019), this bug not appear.

I updated Orom of the Main Board to 12.7.0.1936 but some error appear of shutdown.

In Bios, Sata it´s configured at RAID mode

Windows 8 or 8.1 - OS makes no difference. Fresh instalation to test diferent version drivers.

x2 SSD M4-CT128M4SSD2 RAID-0

x2 HDDs ST500DM002 RAID-0

x2 HDDs ST3250620AS

Can help me?

A Greeting

PS: 12.8.0.1016 (the release offered officially by the motherboard manufacturer, already double-checked this file (SetupRST.exe) matches the one downloaded from downloadcenter.intel.com)

El mensaje fue editado por: Ra·l E. Added more information. PS

Will Intel update the Graphics accerlerator for the Samsung 11.6” ATIV Smart PC (XE500T1C-A02CA) so we can upgrade to Windows 10?

Hi!

I have a pretty silent PC, so the only noise when it's idling or browsing the web is my storage HDD spin, so I use the Windows power options to spin it down and stop the noise after 1 minute.

This is not working in Windows 10 however. It works as it should with RST uninstalled. I've haven't tried previous RST drivers (13.x, 12.x), since I suppose they weren't built for Windows 10.

Am I missing some option, or is this some kind of bug? Everything is properly configured in the BIOS and, as I said, the HDD will spin down if RST is uninstalled.

Motherboard is Maximus VI Gene (z87).

I installed the new RST 14.0.0.1143 on my Z87 Mainboard with Windows 8.1 yesterday. Since there are no F6 drivers yet, i started the setup and then looked in %temp%, and there were the familiar x86 and x64 folders, just like in the F6 drivers. So i updated the driver from there via the device manager.

Something i soon noticed was wrong: The HDDs didn't spin down anymore after the 30 minutes i defined in the power savings plan.

At first i thought there could be something wrong with the extracted F6 driver files, but the folder content matched with the previous F6 drivers, and there was nothing unusual in the INF files either, which i compared. Just some new strings for newer chipsets.

I then made a roll-back to the old 13.6.0.1002 driver via device manager. The HDDs spun down after 30 minutes, everything normal.

To rule out that the 14.0.0.1143 drivers actually require the RST software to function properly, i installed the whole RST 14.0.0.1143. But with that, there is another problem, so i couldn't analyze the original problem further. The RST software keeps polling the SMART data from the HDDs and thus prevents them from spinning down anyway.

In Process Monitor, it looks like so:

1. 23:21:55,2169899IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk0\DR0 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
2. 23:21:55,2170929IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk0\DR0 SUCCESS Control: SMART_RCV_DRIVE_DATA
3. 23:21:55,2172062IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk0\DR0 SUCCESS Control: IOCTL_SCSI_PASS_THROUGH_DIRECT
4. 23:21:55,2175240IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk0\DR0 SUCCESS
5. 23:21:55,2196952IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk1\DR1 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
6. 23:21:55,2197896IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk1\DR1 SUCCESS Control: SMART_RCV_DRIVE_DATA
7. 23:21:55,2198977IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk1\DR1 SUCCESS
8. 23:21:55,2220264IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk2\DR2 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
9. 23:21:55,2221176IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk2\DR2 SUCCESS Control: SMART_RCV_DRIVE_DATA
10. 23:21:55,2222212IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk2\DR2 SUCCESS
11. 23:21:55,2244052IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk3\DR3 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
12. 23:21:55,2244945IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk3\DR3 SUCCESS Control: SMART_RCV_DRIVE_DATA
13. 23:21:55,2245982IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk3\DR3 SUCCESS

So i uninstalled RST and went back to the 14.0 F6 drivers only for analyzing. But no matter what i tried, even setting the spin-down to 1 minute in the power management, the HDDs won't spin down with the new driver.

I read a bit more about the mechanism here: http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/Disk_Idle_Detection.doc

Apparently the power manager, after the defined time, sends a request packet to the disk driver, asking for the HDD to go from D0 state (fully on) to D3 state (standby, stop spinning). Then the disk driver should convert this packet into an ATA command, telling the drive to enter standby. But from what i see, the drive never receives this command with the RST 14.0. When i roll back to 13.6.0.1002, it works fine again. With the 14.0, no go, i tried everything. And contrary to when you install the full RST software, with just the F6 driver there is also no SMART data polling that could interrupt things.

I'm at a loss here. Sadly i don't have the "PwrTest" tool from the Windows Driver Kit to test the mechanisms any further. But i'm hoping for someone else to know what's going on, or at least reproduce this possible bug.

Folks, I have an Asus P6T Deluxe V2 MB using (all SATA drives) 2 - 2TB drives as RAID 1 boot drive, running Windows 7 64 bit. I also have my 2nd RAID2 (we will call it) as a data drive, 2 - 2TB drives as well, no issues at all... I've been running this configuration for some time. Last night, I swapped out the 2nd Raid (2-2tb data drives), and installed 2-3TB drives). Recap now I have my Boot Raid of 2 - 2tb drives, data Raid of 2 - 3TB drives.

When I boot up during POST, I see the Intel ICH10R Rom 8.0.0.1038 shows my boot Raid as the 2 - 2tb drives, HOWEVER the 3TB drives show as 746.5 GB, which one I don't recall. ** however when I boot into Windows 7, 64 bit, the Operating System sees my drives all fine, the correct data size, period, no issue. Even prior to upgrading Intel RST to version 11.7.0.1013, Intels software still shows the correct size. I only upgraded RST to a slightly newer version, thinking perhaps it may initiate a change to the Intel ROM version, which I figured it probably wouldn't and it didn't. I realize typically ROM or BIOS updates run via a utility, etc.. (I work in IT for over 20+ years, so I am familiar).

I looked at ASUS Bios updates and was already running the version of BIOS update that stated about showing the correct/updated hard drive size. I am at a loss here, as I would expect it to be a BIOS issue, I would think. However not sure if updating or if there is an update to the Raid Option Rom that would correct the issue or not? I found an article somewhere on Intels site, somewhere (sorry), that stated something similar to the Raid Option Rom does not need to be updated because.... Maybe someone has some insight? Perhaps the same issue and you can tell me what solved it? Thanks a ton!

(update: 6/7/15 - updated to the last BIOS version from 12/22/2010 on Asus website. Have to mention their tech support, though I did get an email response from them, about a 0+ out of 5)... updated to the 2010 BIOS didn't change anything. thank you

Initial Intel RST Application view, after simply installing the 3TB drives. Keeping in mind I will have 2 RAID sets, Boot Raid (2TB drives) , Data Raid (3TB drives)

Update from shortly after posting: I decided to go into the Raid Configuration Utility during Boot up, since this is where you Configure the RAID sets so the OS (Windows 7-64 bit) can see them...  As you see from the screen shot the Config Utility during POST shows 746.5GB, so I figured I would select them and configure my 2nd RAID set, just to see what would happen.

Here is after I selected the 3TB drives (ports 2 & 3) for my data RAID1 set. Again, you see 746.5GB, however each drive is 3TB.

Now here is what Windows 7 still sees nothing has changed. Since installing and prior to configuring the 3TB drives, Windows 7 and Intel RST Application has always seen the 3TB drives, as 3TB drives, period.. Now after configuring this 2nd RAID called 3TB, Windows still sees the drives individually and doesn't even recognize the 3TB RAID set..

INTEL RST Application (which I can NOT configure the RAID set inside this application for whatever reason, even if I run it as Admin), which I am the Admin anyhow.

Windows 8.1 64bit PRO updated to Windows 10 PRO - Intel Rapid Start Technology 3.0.0.1053_WHQL

I see this irstrtsv error in the Event Viewer.

id event 0

The description for Event ID 0 from source irstrtsv cannot be found. Either the component that raises this event is not installed on your local computer, or the installation is corrupted. You can install or repair the component on the local computer.

irstrtsv
"Error: Unable to read LBA sector directly. : The parameter is incorrect."

I do not see a performance issue due to the error.

This irstrtsv error occurs when the system starts, there is a cluster of 5 errors repeats every 5 minutes with another cluster of 5 irstrtsv errors and continues until I shut it down.

I tried to uninstall and reinstall intel rapid start software but always with the same result.

Mainboard: Asus Z87 deluxe

IRST driver installed: intel rst 14.5.2.1088 WHQL

IRS  driver installed:  intel Rapid Start Technology 3.0.0.1053_WHQL

bios mode: RAID

HDD: 2 SSD + 3 HDD (2TB) RAID 5