For any of you who might be using an ASMedia-based PCI-e SATA controller (2-port, SATA 2/3), you might want to read this:
I have a PCI-e SATA controller (SY-PEX40039, sold under the brand name of IO Crest) controlling two hdds. The default driver loaded by Win10 dated back to 2006 which seemed . . . quite a bit older than the product in question. In fact, it is so old that it predates the Windows 7 and Windows 8/8.1 driver models. So I decided to replace it with something from the vendor.
What I found was SY-PEX40039.zip, containing a driver from 2011. Much better. As an added bonus, the file was provided by the manufacturer, so no (well, less) concern over malware. It's meant for Windows 7, so I skipped using the packaged installer utility and installed it by hand. My efforts were rewarded with the sight of "ASMedia 106x SATA controller" in Device Manager. All there was left was to reboot . . .
Sadly, after rebooting, Win10 would give me the "frowny face of not booting" no matter how often I rebooted or what my UEFI settings. Hmm! So I booted to Safe Mode. Win10 then greeted me with a warning, which I'll paraphrase: "Explorer has suffered an unexpected hard fault". Oh goody. Now the start button won't work, nor will any other icon associated with the task bar. So I right clicked the desktop, opened up the screen resolution control, and used the bar at the top of that screen to browse to All Control Panel Items so I could then get to Device Manager. I uninstalled the ASMedia 106x SATA Controller driver and rebooted.
Win10 started up just fine. I went back to Device Manager to see what was there, and I found that the controller still registered as ASMedia 106x SATA Controller. Hmm. Several test boots later, I find the machine as responsive as before, if not a bit moreso (assuming the driver is working without fault, one would hope a proper driver would result in improved drive performance).
TLDR summary: ASMedia 106x drivers meant for Win7 will work, but it may be a pita to get them to work. I am still not sure why the driver ever caused a problem in the first place, since it is working so nicely now.
Oh, and today is the second time that Windows Update has forced me to install an old Catalyst version, which I prompty "rolled back" (forward?) to the latest 14.12 . Sigh.