Intel Rapid Storage Technology Preinstall Driver (RAID) 11.7.0.1013 x64 Download
Posted at November 21, 2024 by PCI-DB Team
Install Driver Automatically| Device Name | Intel Rapid Storage Technology Preinstall Driver (RAID) 11.7.0.1013 x64 |
|---|
| Category | Motherboard |
|---|
| Manufacturer | Intel |
|---|
| File Size | 354 KB |
|---|
| Supported OS | Windows 2008 ,Windows 7 64 bit ,Windows 8 64 bit |
|---|
Intel Rapid Storage Technology Preinstall Driver (RAID) 11.7.0.1013 x64 Description
Fixes:
Resolved Issues:
- SRT Incorrectly trying to stage frames past end of volume
- IAStoraIcon.exe error pos up and stress tool stops testing during Video Stress + AC/DC Cycling test.
- 11.6 driver .inf needs FeatureScore to ensure the driver outweighs the 11.2 driver in Windows installation
- Accelerating OS after cache disassociation from missing passthrough disk induces BSOD F4
- failure to format BD-R (Blu-ray) disk
- Some ODD under ZPODD state does not eject by pressing tray button after resuming from hibernation.
- 0x9F bluescreen when run S3 to S4 Timeout Focus+AP/LAN+ACDC.
- SRT causing extra cache misses on partial writes - extra spinups in AOAC
- UI disallows preservation of system disk during CVFD migrations of ANY RAID volume on Desktop systems
- UI allows acceleration with a custom cache even when the custom field is grayed out
- CLI returns success after failing to delete metadata with SRT enabled
- Some instructions in RST GUI help are incorrect as the steps are for Win7 not for Win8.
- Topic is unexpected to be changed to another topic in RST help
- F4 BSOD during S3 and during checking disk spin status intermittently
Known Issues
- BSOD 0xD1 during hybrid sleep
- Error Recovery Policy Causing Black Screen While Booting From S4 Mode
- UI unknown error after accelerating OS drive, rebooting, and disabling acceleration
- Driver is not enabling DIPM if CAP.SALP is 0, but CAP.SALP only pertains to HIPM.
- GPT only- Unexpected 2GB data volume created with <64GB SSDs and Full SSD space selected for cache
- Pioneer BDC-TD04: After resuming from S3, ZPODD disappears from Device Manager or Disk Manager
- RRT failed master disk goes offline when setting disks to normal
- RST 11.5+ Drivers fail to interoperate with OPAL drives in win7
- Roxio ejects ODD automatically before media is detected
- System fails to burn medias with Roxio Creator repeatedly with ZPODD devices
- Unknown Error when enabling acceleration in Win 7 / Win 8 on specific SSDs
- Volume write-cache available on RRT Configure Volume page with Windows WC buffer flushing on
- WHQL: RST not compliant with Device.DevFund.Memory.DriverFootprint requirements for x86
- iSRT configuration after S3/S5 stress, system will BSOD D1(iaStorA.sys) (DPPM: 400)
- A1h command (IDENTIFY PACKET DEVICE) failure on ODD with Win8 RST driver
- Driver Verifier Violation BSOD encountered during SGIO tests on CPT-S
- Hot-unplugging the SSD after switching mode from maximized to enhanced leaves the SSD marked as either a failed or a normal disk in the UI; resetting the absent disk to available and reaccelerating the system disk induces a BSOD or a system hang
- Placing OS on 2-drive RAID0 volume at end of matrix array causes RST to construe incorrect HDD as the system
- SRT Driver Fails "No Spin" TIME IOCTL request on FIRST S0 following S3 with PUIS enabled
- SRT caching example files for OEMs contain mistakes that need fixing
- SRT volumes do not report disk RPM = 1, breaks Win8 Connected Standby
- System Tray notification does not occur on Boot up on Recovery drive: OS = Rapid Recover Technology
- The write caching of SSD will auto check after resume from S3/S4/CB
- RST driver issues non-queued commands with NCQ commands outstanding
- System gets BSOD 0x9F after driver fails to reestablish communication with drives intermittently
- Driver: If IRRTm OS volume is restarted while accessing files on the recovery disk the recovery disk is not re-associated back into the IRRTm volume.
- Accelerating OS after cache disassociation from missing passthrough disk induces BSOD F4 intermittently
- CrashDump causes G2TB OS Volume to become failed or degraded intermittently
It is highly recommended to always use the most recent driver version available.
Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.
Related Intel Drivers