There’s no need to remove the entries without the underscore (amdsata and amdxsata). From HKLM/SYSTEM/CurrentControlSet/services delete amd_sata and amd_xsata.In order to remove the directory, you need to either elevate your explorer / shell to SYSTEM privileges, or take the ownership of the driver directory, add proper permissions, then delete it.
#Amd sata controller driver 1.3.1.276 windows 8 drivers#
The folders with older AMD AHCI drivers are named something like: amd_sata.inf_amd64_neutral_c85cc6046149a413 (i386 on 32-bit and most probably another hash). Delete any older version of the amd_ahci driver from here: C:\Windows\System32\DriverStore\FileRepository.Fortunately I found this post on .įor the sake of avoiding the link rot, I’m going to reproduce the essentials for posterity, with the same disclaimer as the original – you’re on your own if you mess up your machine and I’m not taking any responsibility if you follow these: Uninstalling the driver that broke my installation and installing a driver that works proved to be a non-trivial task. Even more, their engineers didn’t grasp the concept of backward compatibility. When it comes to drivers, AMD is still a shitty company. The most important: the SSD performance is hurt under IDE mode, the TRIM command won’t work under IDE mode without 3rd party software since only the MSAHCI driver implements TRIM from Windows 7, and the fact that my HDD array doesn’t support NCQ under IDE mode.
Had to disable the AHCI in BIOS and revert to using IDE mode for the SATA ports. I had the lack of inspiration to check that too instead of simply ignoring it, like I usually do with Bing Desktop and Silverlight. You know, like the stuff that comes from the vendor and it isn’t properly tested. Until Microsoft delivered a 3rd party driver update via an optional package. Of course, I dismissed all of them with the classic “worksforme” as didn’t happen to me. I heard a lot of urban legends about the Windows Update service that messes up your machine.
0 kommentar(er)
