15 rows  This utility supports the Intel® RAID Controller, Intel® Integrated RAID, Intel ITIR RAID. Stickman vs mouse game. 2, What OS require Intel VROC OS drivers? Lane coffee table serial number. 10, For 1023US-TR4, do you have any chipset driver for Win 2012 64bit? If Win2012 x64 is not.

Intel Sas Controller Driver Windows 10 1

Intel sas controller driver windows 10 64Intel

Marvell 92XX SATA Controller 6GB Driver for Windows 10 (x64) 1.2.0.1039-WHQL (9/5/2013 a.k.a. 6/19/2014)
In Windows 10, the driver for the Marvell SATA Controller may not get installed automatically which leads us on a wild goose chase as to where to find it.
Marvell's driver download page only lists this driver as for Windows Server 2008 SP2, Windows 7, and Windows 8. The Windows 8 driver will work fine on Windows 10 but the driver at Marvell is slightly older than the driver provided here.
This driver is found at EVGA's driver download page (EVGA - Download Center) and is for the Z87 FTW motherboard. Also, it is listed as a Windows 8/8.1 driver named 'SATA 3/6G (Non-Intel)'but works flawlessly on Windows 10.
The actual driver date listed in Windows after the driver is installed is 9/5/2013, but many download sites list the driver release date as 6/9/2014.
Oddly, the driver is listed as 'SATA 3/6G (Non-Intel)', which is kind of ridiculous because the only other controller besides Intel on this board is Marvell, so instead of saying 'Non-Intel' wouldn't it be just as easy to say 'Marvell'? And in fact, when you click 'Download', the file that downloads is named 'Marvell_1.2.0.1039-WHQL.zip'
However, I believe this Marvell driver will work fine on many platforms other than EVGA motherboards, as it is for the Marvell 92xx SATA 6GB Controller and there is very little chance that a vendor has modified this chipset. (which would require their own driver, of course.)
I had no problems with a controller not working, drives not being recognized, not utilizing the correct speed of the controller, etc.
On the contrary, the only reason I began my search for this proper driver was that I saw it as a missing driver in Device Manager and was listed as 'Other Devices > Unknown Device'. The Hardware ID was quite cryptic listed as 'SCSI/PCI..' something. It did not look like a normal Hardware ID.
After the driver provided here is installed, the true hardware ID of the Marvell SATA 6GB Controller listed in Device Manager is as below:
PCIVEN_1B4B&DEV_9220&SUBSYS_92201B4B&REV_10
PCIVEN_1B4B&DEV_9220&SUBSYS_92201B4B
PCIVEN_1B4B&DEV_9220&CC_010601
PCIVEN_1B4B&DEV_9220&CC_0106
The drivers installed are:
C:Windowssystem32DRIVERSmvs91xx.sys (File version: 1.2.0.1039, Size: 319KB, Date modified: 9/5/2013 6:47 PM)
C:Windowssystem32DRIVERSmvxxmm.sys (File version: 1.0.0.1204, Size: 16.2KB, Date modified: 9/5/2013 6:47 PM)
C:Windowssystem32mv91xxm.dll (File version: 1.0.0.3, Size: 35.5KB, Date modified: 9/30/2013 1:51 AM)
1) To install this driver, simply download this file to a folder where you can easily find it, such as the Desktop or Downloads.
2) Right click it and select 'Extract..' to use the Windows built-in .zip file handler or whatever command you normally use to unzip files if you are using WinZip, WinRAR, 7-Zip, or similar.
3) Double-click to open the folder that is just created, which will be named the same as the zip file was.
4) Double-click the file named 'drvSetup.exe'. The installation is quick.
Done!
You should now see the proper Marvell SATA 6GB Controller listed in Device Manager under 'Storage Controllers'.
Driver file attached:
IMPORTANT EDIT: After I made this post, I discovered a newer version of the Marvell SATA 6GB Controller talked about in this post. It is dated 2015 versus the 2013 driver I originally posted.
However, I will leave that older driver attached here also. The newer driver (2015) is installed by the 'Right-click on the device in Device Manager and select 'Update driver software..' and browse to the folder where the files are located' method. I have to install this older driver first for the device to even show up in Device Manager.
So in short, I have to install the 2013 driver then the 2015 one.
To be clear, the 2013 driver attached here is named Marvell_1.2.0.1039-WHQL.zip and the newer 2015 driver is named Marvell_SATA_V1.2.0.1047 - Windows 10.zip.
.
Attached FilesController
  • Marvell_1.2.0.1039-WHQL.zip (1.58 MB, 924 views)
  • Marvell_SATA_V1.2.0.1047 - Windows 10.zip (6.49 MB, 1513 views)

Intel Sas Controller Driver Windows 10


Hi,
I have a PC with Asus P9X79 Deluxe motherboard. It has Intel chipset and Intel BIOS RAID (RSTe) and 6 SATA ports connected to it. The chipset IDE controller lists in Linux as:
Intel Corporation C600/X79 series chipset SATA RAID Controller (rev 06),
and the PCI ID is:
0104: 8086:2826 (rev 06).
My RAID configuration is 2xOCZ-VERTEX4 256GB SSD's in RAID0, as boot drive (C: drive), and 2 (quite old) WDC WD2500KS 250GB disks in RAID0 for extra storage (games, movies etc) (J: drive).
So yesterday I decided to upgrade my Windows 7 Ultimate to Windows 10 Pro. All seemingly went well during the upgrade process, and the system booted fine, and most stuff seemed to work as it should. But after a while when I accessed files on the J: drive I started experiencing random (temporary) freezes.
Then after a while it got more serious and the whole system froze, I had to hit the reset button.
So I rebooted and looked in the event log, I get see tons of errors there saying that the disk has a bad sector.
Then I try using the J-drive again, by viewing some videos there, and it works fine, but after a while there are some freezes and then I see in the event log, that the drive was reset. After this it works again for a while but then another of those resets comes, and freezes everything for a short while (like 30 seconds).
But when I try to copy some large files off the J-drive, another reset comes, and then the event log starts showing a lot of the error messages from before, with 'the disk has an bad sector'. (I will post screenshots of these errors after I reboot back into Windows).
After this I can't access the J-drive at all, and Windows gives me error messages when I try to.
So, I figure that I might have just got unlucky and the old WDC drive actually developed read errors, although it's strange that it happens exactly when I install Windows 10 (these drives are something like 7 years old).
Well I can't copy the contents off the disk from Windows since it keeps failing as described above, so I boot into Ubuntu Linux from a USB stick, so I can use ntfsclone to image the J-drive to another disk. I start it running expecting that I'll start seeing read errors, but to my surprise there are NONE. It also copies all files off the J-drive without any problems from inside Linux!
So it was after all not the old drive that had failed, but instead Windows 10/Intel had failed me in a big way.
I trawled the web for updated Intel chipset drivers and installed those from the Asus site, but it made no difference at all. I couldn't find any other Intel drivers and when I searched for the RST drivers on Intel's own site, I could only find ones for Windows XP upto Windows 8.1, but none for Windows 10.
For now I'm left with a PC that I can't use, because I can't go back to Windows 7 and Windows 10 is not working with my RAID arrays. I got some spare 2TB disks, and I'm right now copying all the data from the old J-drive (the RAID1 about 500GB) over to this, hopefully I can then work in Win 10, but I am VERY concerned because the same RAID and drivers are used for my master boot drive with the two OCZ SSD's.
I can't believe my setup is so rare, that they haven't tested this, and that it's failing in such an abysmal way, easily causing data corruption. Well I guess I made a mistake when I thought Windows 10 was ready for prime time, now I am paying the price. Thanks MS and Intel!
Any suggestions to what I can do to fix this? I doubt there is an easy fix and I just wanted to put this out here so that ohters can be warned.
Cheers,
Thomas