Hi,
Your case is very unusual because once the OS has been installed by using RAID the system should not boot if you change the SATA controller to ACHI .
If your motherboard had randomly booting issues then I recommend you testing the different devices individually in order to avoid future problems (e.g. power supply, ram, etc..) additionally you may considering a bios update to your motherboard as well.
As you mentioned the only way to get access to the Intel(R) Rapid Storage Technology and Intel(R) Smart Response Technology again will be reinstalling the OS since the scratch selecting RAID, I recommend you using the F6 drivers in case you have not installed them the first time.
Regards,
Dago MC.
Dago,
Thank you for the reply... since posting this I have solved the problem. Maybe this will provide some clue to someone if they have a similar issue.
A Windows Critical Update was the last system change prior to the problem starting, following the update the system either crash and reboots (just once), or simply rebooted, there is no random reboot issue on my machine, apologies if I mis stated that. After this happens I'm stuck in the situation above.
After getting the machine to boot by reverting to ACHI mode on the SATA, I took a look at disk management (Control Panel > Administrative Tools > Computer Management) and I noticed that the SSD was listed as "unallocated" and no longer had a drive letter. This seems odd as it was showing up when running diskpart from the command line, however I decided to format, allocate, and assign a drive letter to the SSD... this worked no problem.
I rebooted, everything still fine. Rebooted again, switched SATA mode back to RAID... computer boots to Windows, no problem.
Re-installed Rapid Storage (10.8)... no problem.
Launched the program... no problems. On the status screen it reports that my system is accellerated. Apparently the previous uninstall left some registry settings (or something) behind such that I did not have to enable accelleration again. Everything seems to be working, the accelleration is definitely working.
I'm not sure what went wrong to begin with, but I suspect the Windows Update caused a hiccup which set this all in motion. I have created a restore point, and I hope I don't need to use it.
