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

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

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.

@ 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.

Zitat von Fernando im Beitrag #220

---

Zitat von Jackson im Beitrag #219

---

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.

---

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.

---

After configuring write-back buffer flashing and write-back caching using the Intel Rapid Storage technology console, I can go ahead and uninstall it already without losing those settings, right?

Zitat von Fernando im Beitrag #223

---

Please check the HardwareIDs of your ASMedia 106x SATA Controller. (right click onto it > "Properties" > "Details" > "Property" > "HardwareIDs").

---

Zitat

---

PCI\VEN_1B21&DEV_0612&SUBSYS_84B71043&REV_01
PCI\VEN_1B21&DEV_0612&SUBSYS_84B71043
PCI\VEN_1B21&DEV_0612&CC_010601
PCI\VEN_1B21&DEV_0612&CC_0106

---

Today the ASMedia controller for the internal ports disconnected the 2 disks attached with the event errors (Disk 5 has been surprise removed) & (Disk 6 has been surprise removed) and now I am trying a mix of the Microsoft STORHCI.SYS for the internal ASMedia ports and ASSTOR64.SYS for the ASMedia eSATA.

@Fernando

I'm familiar with the "normal" write caching policies of Windows in device manager but where do you set the write-back caching itself? Is it a registry entry in Windows?