Configuring new SSD to AHCI on Gigabyte 890GPA-UD3H

rwhipple08

Distinguished
Mar 6, 2010
47
0
18,530
Sorry for another of these similar threads, but I've done my homework and can't seem to find the answers pertaining to my exact situation.

I installed Windows 7 on a Sumsung 840 Pro in IDE mode on a Gigabyte 890GPA-UD3H motherboard. I'm trying to change to AHCI, and running into some barriers.

1) As per http://support.microsoft.com/kb/922976, msachi and iastorv are set to "0"
2) When I change BIOS to AHCI mode on the SATA port the SSD is on, system hangs at POST screen.
3) When I change BIOS to AHCI mode on all SATA ports, including the one my HDD and DVD drive are on, it gets past POST screen but hangs saying it can't find BOOTMGR.

From my research, I understand that I need to install AHCI drivers for my motherboard, but I am unsure where they are or how to tell if I have them already. AMD says they took them out of their most recent Catalyst build because they were causing problems, and I've read people say the AMD ones are bad anyway. Gigabyte's drivers require me to launch Catalyst, which then promptly crashes.

At this point I'm not even sure I know what the right questions to ask are, but I *think* I need help finding out:
-How do I tell what drivers I have?
-Which drivers do I actually need?
-What BIOS settings do I change?
-Am I going to need to move some physical connections around?
 

rwhipple08

Distinguished
Mar 6, 2010
47
0
18,530
One more bit of information: after I get the BOOTMGR error and go back into BIOS to change SATA modes from AHCI back to IDE, I also have to fix the boot order of the drives; somehow the HDD moves ahead of the SSD (which has the OS) in the priority order. Does this have anything to do with the HDD being IDE channel 1 master and the SSD being channel 2 slave? (How is this even possible with the SSD being plugged into SATA_0 on its own cable, and the HDD being plugged into SATA_4 on its own cable?). Could this possibly be the source of the BOOTMGR error when I set to AHCI? If something about booting in AHCI switches the order of the drives and therefore causes the system to not see the SSD with the OS, that would explain the problem, but I'm not sure when the switching takes place or if that's really the cause.