http://support.amd.com/en-us/download/ch…ws%207%20-%2064
I guess these are…
Update of the start post
Changelog:
- new: 32/64bit Win8/8.1 AMD AHCI drivers v1.3.1.276 WHQL dated 03/19/2015, suitable for AMD AHCI Controllers DEV_ 4391/4394, DEV_7801/7804 and DEV_7901/7904
- new: 32/64bit Win7 AMD AHCI drivers v1.2.1.402 WHQL dated 03/19/2015, suitable for AMD AHCI Controllers DEV_ 4391/4394, DEV_7801/7804 and DEV_7901/7904
It has to be checked and reported by users with an AMD Chipset, whether these new AHCI drivers are better than the older AMD AHCI drivers v1.3.1.220 (for Win8/8.1) resp. v1.2.1.359 (for Win7). Until I get a feedback, I will still offer them within the start post.
Good luck with these AMD AHCI drivers!
Fernando
Today Station-Drivers has published new Marvell 91xx/92xx SATA3 drivers. Thanks for having done it!
Update of the start post
Changelog:
- new: 32/64bit Marvell 91xx/92xx SATA3 AHCI/RAID drivers v1.2.0.1047 WHQL dated
06/26/2015 (shown as being dated 04/14 resp. 04/30/2015)05/05/2015 (replaced on 07/19/2015)
Since we do not yet know, whether these new Marvell AHCI drivers do support TRIM or not, it would be fine, if we would get a report by a Marvell SATA3 user, who has tested it.
If these latest drivers should support TRIM, I would remove the much older Marvell 91xx/92xx SATA3 drivers v1.2.0.1035 from the start post.
Update:
1. According to RoughBoy’s report the Marvell AHCI drivers v1.2.0.1047 do not support TRIM. So I will not remove the much older v1.2.0.1035 ones, which do support TRIM.
2. Since Station-Drivers yesterday published an obviously newer driverpack, which definitively contains WHQL certified drivers v1.2.0.1037 dated 05/05/2015, I have replaced the yesterday uploaded driverpacks by the updated ones.
Enjoy the new Marvell AHCI and RAID drivers!
Dieter (alias Fernando)
@Fernando
I tested both new Marvell drivers: Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1046 WHQL and Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1047 WHQL. 
I did it on my Asus P8P67 Rev3.1 which has an onboard SATA controller Marvell 88SE9120 with an updated Marvell AHCI-ROM and BIOS version 1.0.0.0034 and with a 256 GB SSD Samsung 830. 
Unfortunately both drivers do not support TRIM. 
Besides the Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1047 is not WHQL. The setup software did not work too. So I had to do the installation manually with the device manager. 
I also did a control test with the older Marvell 91xx/92xx SATA3 drivers version 1.2.0.1035 and there is TRIM support.
@ RoughBoy:
Thanks for your report, which will help other users.
That is a pity.
That seems to be not true.
Look here:
@Fernando
In my Windows 7 device manager the driver Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1047 is not digitally signed.
Maybe ASUS has changed anything after having gotten the digital signature from Microsoft.
Update:
Obviously my speculation regarding the reason for the broken digital signature was correct.
Today (07/19/2015) Station-Drivers has published a newer package with Marvell’s SATA3 AHCI/RAID drivers v1.2.0.1047 WHQL and this time all drivers are dated 05/05/2015 and correctly digitally signed by Microsoft.
As a consequence I have replaced the 32/64bit Marvell AHCI/RAID drivers v1.2.0.1047, which I am offering within the start post, by these ones, which should have a correct WHQL certificate.
@Fernando
I tested the second new Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1047 WHQL (2).
I did it again on my Asus P8P67 Rev3.1 which has an onboard SATA controller Marvell 88SE9120 with an updated Marvell AHCI-ROM and BIOS version 1.0.0.0034 and with a 256 GB SSD Samsung 830.
Unfortunately and as expected the new driver does not support TRIM.
Besides the second new Marvell MV-91xx/92xx SATA 6G Controller version 1.2.0.1047 WHQL (2) is really WHQL now. There is also no error message after the manual installation with the device manager anymore.
I also did again a control test with the older Marvell 91xx/92xx SATA3 drivers version 1.2.0.1035 and there is TRIM support.
Update of the start post
Changelog:
- new: 32/64bit Win10 ASMedia 106x AHCI drivers v3.1.6.0 WHQL dated 06/17/2015
Thanks to Station-Drivers for having offered the source package.
Meanwhile I have installed the 64bit variant of this brandnew ASMedia AHCI driver onto my Z97 system running Win10 and found, that it is runing fine.
Here is a picture with the driver details:
Notes:
- After the installation the ASMedia 106x SATA Controller will be listed within the “Storage Controllers” section of the Device Manager (and not anymore within the “IDE ATA/ATAPI Controllers” section). This is an SCSI feature and not an issue.
- According to the INF file entries these drivers may be usable with Win7 and Win8/8.1 as well. I will test it and report later.
Update: The Win10 Drivers do not work while running Win8.1!
This is the message I got:
Good luck with these AMD AHCI drivers!
Fernando
The AMD AHCI drivers for Windows XP provided by Asus seem to work fine, but they do NOT make the S.M.A.R.T. information available. Do the drivers available for download on this website do so?
@ cdg:
Welcome at Win-RAID Forum!
Probably not, because they are all made by Intel, but if you want S.M.A.R.T. informations about the disks, you can use the tool CrystalDiskInfo.
Regards
Dieter (alias Fernando)
The ASMedia 106x driver causes my second hard drive to unexpectedly dismount and then remount about every hour on the dot… when I check the event viewer I am met with a warning message that says “disk 1 has been surprise removed” I’ve had this error with VM disks but I’ve never experienced this with my physical hardware… any suggestions on how to resolve this? For now I just uninstalled the driver which got rid of the issue…
edit: motherboard is a VII Hero (BIOS 2702) and I’m running Windows 10
@ Strelok:
Welcome at Win-RAID Forum and than you for your report.!
Please let us know about which ASMedia 106x AHCI driver version you are talking.
Then we will have the chance to get more reports about the same issue.
Regards
Dieter (alias Fernando)
It’s Asmedia SATA Controller Driver V3.1.6.0 for Windows 7/8/8.1/10 32bit & 64bit it was made available on my motherboard driver page 2015/07/28
@ all users, who have installed the ASMedia 106x AHCI driver v3.1.6.0:
Please report here about your experiences with this AHCI driver. Did you get the same problem as Strelok (see his post #213)?
Another one having problems with the latest ASMedia driver. Using the ASMedia 106x AHCI X64 driver v3.1.6.0 on Windows 10 Pro, I have connected to an eSATA ASMedia port a backplane of 4 drives using the port multiplier functionality and also using 2 internal ASMEDIA sata ports for drives
I got 30 errors in the event log for 2 of the drives in the backplane (The IO operation at logical block address 0xa5dec2d8 for Disk 10 (PDO name: \Device\0000003d) was retried) in between and at the 1 hour mark I get an error (Disk 5 has been surprise removed) for one of the internal sata ports and Windows 10 immediately bluescreens.
No problems with the same setup in Windows 7, Windows 8.1. Uninstalling the ASMedia driver from Windows 10 and using the default STORAHCI driver (doesn’t support port multiplier and have no access to 3 drives) also stops the errors and BSOD.
@ Jackson:
Welcome at Win-RAID Forum and thank you for your interesting report!
I will add a related remark to the start post of this thread.
Regards
Dieter (alias Fernando)
@ Fernando
Some updates. The ASMedia drivers that I used and had problems were the archived ones from station-drivers, inside the achive there are different executable instalataions for W10 and W7,W8 and I used the W10 executable setup which installed the ASSTAHCI64.SYS driver.
Inside the W10 driver folder there are also subfolders contaning various drivers for manual installation, one of them has an alternate ASSTOR64.SYS driver which I manually installed.
I have been running the ASSTOR64.SYS drivers for 5 hours and the only event errors I had, was 2 warnings for each of my 2 internal ports ("Reset to device, \Device\RaidPort1, was issued" & "The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\00000037) was retried."). No more BSOD and I have back my port multiplier functionality.
According to my knowedge this is a RAID driver and not an AHCI driver.
So your ASMedia 106x SATA Controller is obviously running in RAID mode.
This would explain, why you ran into problems after the installation of the Win10 AHCI driver.
According to my knowedge this is a RAID driver and not an AHCI driver.
So your ASMedia 106x SATA Controller is obviously running in RAID mode.
This would explain, why you ran into problems after the installation of the Win10 AHCI driver.
Could be a particularity of my MB, the settings for my ASMedia 106x SATA Controller in my BIOS are Disabled/IDE/AHCI with my selection being AHCI and I have disabled the ASMedia OPROM. My Windows 8.1 install is also using the ASSTOR64.SYS driver (3.0.2.0) where I am pretty sure also used the setup method. Maybe the setup program for the drivers is broken and installing the wrong drivers.