To automatically install your Standard SATA AHCI Controller driver, simply double-click on the file you previously downloaded, which should have a (.exe) file extension. This is automatically going to install the latest driver you downloaded.
On a Windows based system, the operating system detects the SATA controllers during boot and loads device drivers supporting the configured SATA mode. For the purpose of this article, only AMD SATA controller for AHCI mode is covered.
Ahci 1.0 Serial Ata Controller Driver Download
The AMD SATA controller component is not compatible with and will not be offered nor installed by the chipset driver package on AMD desktop systems running Window 10 or using AMD Socket AM4 and Socket TR4 chipsets. Forcing a manual driver installation via Device Manager on these systems is not supported and may cause stability and performance issues with some mass storage devices, such as solid-state drives (SSD).
If the system is not using Standard SATA AHCI Controller driver and is experiencing stability and performance issues with connected SATA devices, use the Roll Back Driver option to restore to the default controller.
My real question boils down to this: When I attempt to downloadDrivers from the Dell website's Drivers & Downloads page, how do Iknow what I should be installing and not installing? Obviously I shouldn't be installing everything that has 'recommended' next to it, but none of the programs listed seem to fit what I'm apparently missing. Also, what in the world can I do about my Network Controller?Allowing Dell to try to find an update for the driver on its own hasbeen unsuccessful.
AHCI is supported on Windows Vista and later versions of Windows; Linux since version 2.6.19; OS X; and various open source operating systems, such as OpenBSD, NetBSD and FreeBSD. While Windows Vista and Windows 7 include the AHCI driver, those OSes won't install AHCI if it's not enabled on the boot drive's controller.
Sometimes installing Windows can be a truly challenging problem. For example, if you need to install Windows XP (because it's an old hardware uncapable of running something better), and you need to install operating system to the SATA HDD in AHCI mode or to the RAID controller (with appropriate F6 floppy drivers), but you have neither CD/DVD nor floppy drive available, just USB ports!
Windows already contains hundreeds of drivers for wide range of supported hardware, but not for everything, unfortunately. For example, Windows has builtin support for ATA disk controllers (see figure above in this article).
Q: Which operating systems are supported/recommended? A: None of pre-Windows 2000 (Windows 3.11, Windows 95/98 and Windows ME). Windows 2000 may work with some Intel drivers. It's recommended to use Windows XP (32/64bit) or Windows Server 2003 (32/64bit), depending on availability of Text Mode Drivers from the vendor of your SATA/RAID controller.
Q: It's still not detected. A: Some motherboards have multiple SATA controllers. For example Intel X58-based ASUS P6T has SATA controller in southbridge Intel ICH10R and also JMicron JMB363 as a separate onboard chip. Please make sure you've attached your harddisk(s) to the same controller you are installing drivers for. Consult your mainboard manual if you are unsure about that.
I checked the drivers and pciide.sys was enabled, as was msahci.sys. But iastorv.sys was not. I have tested enabling it and enabling Intel AHCI in BIOS setup. It did not help. It still gets stuck at AHCI BIOS device detection.
With the same drivers enabled (pciide.sys, msahci.sys, iastorv.sys), I tested connecting to the Gigabyte SATA controller with AHCI enabled in BIOS setup. Windows Vista started to load and the progress bar came up, but it ran into a BSOD soon after and rebooted. It just kept looping like that.
Some web forums will tell you to have all of the AHCI related drivers enabled in Windows (iastor.sys, iastorv.sys, msahci.sys) for easy switching between AHCI and IDE (pciide.sys is usually enabled by default on most installations, for compatibility I guess). But as you can see, it is sometimes wiser to disable one of them or all of the drivers you are not using and do not plan on using.
The Intel SATA controller is listed as Standard AHCI 1.0 Serial ATA Controller. Ignore the exclamation mark next to it. That's only because I disabled the msahci.sys driver that it was using so it is complaining. But I was running Windows Vista from the Gigabyte controller in IDE mode, so it didn't matter. I have enabled it again before rebooting.
So I rebooted and enabled the AHCI mode for the Gigabyte controller and Windows Vista loaded normally. No problems what so ever. I can confidently say that the Gigabyte controller works in both IDE and AHCI (RAID not tested, but expected to work of course) mode, with either Microsoft generic AHCI driver (msahci.sys) or the Gigabyte controller specific driver (jraid.sys), which is really a JMicron driver.
Note that the iastorv.sys driver previously conflicted with the msahci.sys driver when I tested having them both enabled and using the Gigabyte controller in AHCI to boot into Windows, and I was getting the BSOD slap. I have not tested and do not care to test this with the new driver. Maybe it has been sorted out now, maybe not. The point is, it is best to disable iastorv.sys if and when using the Gigabyte controller in AHCI (or even RAID).
After successfully testing the Gigabyte controller it was time for the Intel controller. I started off with pciide.sys enabled, msahci.sys enabled, and iastorv.sys disabled. I used the f6flpy6489.zip package to install the driver manually. The driver version was 8.9.0.1023. The new driver is named iastor.sys without the V in the name.
Many SATA controllers offer selectable modes of operation: legacy Parallel ATA emulation (more commonly called IDE Mode), standard AHCI mode (also known as Native Mode), or vendor-specific RAID (which generally enables AHCI in order to take advantage of its capabilities). Intel recommends choosing RAID mode on their motherboards (which also enables AHCI) rather than AHCI/SATA mode for maximum flexibility.[3] Legacy mode is a software backward-compatibility mechanism intended to allow the SATA controller to run in legacy operating systems which are not SATA-aware or where a driver does not exist to make the operating system SATA-aware.
Some operating systems, notably Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10, do not configure themselves to load the AHCI driver upon boot if the SATA controller was not in AHCI mode at the time the operating system was installed. Although this is an easily rectifiable condition, it remains an ongoing issue with the AHCI standard.
Technically speaking, this is an implementation bug with AHCI that can be avoided, but it has not been fixed yet. As an interim resolution, Intel recommends changing the drive controller to AHCI or RAID before installing an operating system.[3] (It may also be necessary to load chipset-specific AHCI or RAID drivers at installation time, for example from a USB flash drive).
On Windows Vista and Windows 7, this can be fixed by configuring the msahci device driver to start at boot time (rather than on-demand). Setting non-AHCI mode (i.e. IDE or Combined mode) in the BIOS will allow the user to boot into Windows, and thereby the required registry change can be performed. Consequently, the user then has the option of continuing to use the system in Combined mode or switching to AHCI mode.[8]Inter alia with Windows 10 and 8, this can be fixed by forcing the correct drivers to reload during Safe Mode.[9]
In Windows 8, Windows 8.1 and Windows Server 2012, the controller driver has changed from msahci to storahci,[10] and the procedures to upgrade to the AHCI controller is similar to that of Windows 7.[11] On Windows 8, 8.1 and Windows Server 2012, changing from IDE mode to AHCI mode without first updating the registry will make the boot drive inaccessible (i.e. resulting in a recurring boot loop, which begins with a Blue Screen error).
A similar problem can occur on Linux systems if the AHCI driver is compiled as a kernel module rather than built into the kernel image, as it may not be included in the initrd (initial RAM disk) created when the controller is configured to run in Legacy Mode. The solution is either to build a new initrd containing the AHCI module, or to build the AHCI driver into the kernel image.[12]
A quick Google search of the problem would indicate that this is merely a driver issue. However, I went to my manufacturer's website (Asus), and downloaded all relevant drivers possible and installed all out of date ones (chipset drivers, SATA drivers, etc.). The problem persists. Here's a screenshot:
One more thing I noticed. The "Standard" AHCI controller is actually provided by Microsoft and NOT Intel. The could mean that Microsoft Update installed the wrong one (yet again). The question then would be, what is the correct driver? Is it supposed to be an Intel driver? Where should I download it from?
Our partner site Station-Drivers has just published brandnew WHQL certified Intel RST(e) drivers v12.0.0.1036 dated 06/27/2013.Meanwhile I have put the download links to the 32/64bit Intel RST(e) drivers and the complete Drivers & Software Set v12.7.0.1036 WHQL into the start post of this thread.With these newest RST(e) drivers of the v12.7 development branch many issues (bugs) of previous builds/versions have been solved. They are listed within the related ReleaseNotes, which you can download from >here
[[File:Intel RST(e) Console v12.8.0.1008.pngnoneauto]]You will find the direct download links to the 32/64bit drivers and complete Drivers & Software Set within the start post of this thread.Have fun with these brandnew Intel AHCI/RAID drivers!Fernando 2ff7e9595c
Commentaires