/*********************************************************************************************************************************/
I know this is an old thread, but I had to post. I found the solution to this problem.
On my previous motherboard, an Asrock Extreme3 with an Athlon II, I was having this same problem. I thought it was just a buggy UEFI implementation on the board. I didn't think of trying to unplug my 2nd drive, I just knew that the install would seem to go fine, but I could never get it to boot once installed. I always got either 0xc0000225 or 0x000000c codes.
With my tax refund, I rebuilt my computer. I upgraded my SSD from a 64 GB Crucial to a 256 GB Samsung 840 Pro, and the processor is an i5 3570k. My 2nd drive is the same SATA 1.5 TB hard drive. But I had the same problem.
I finally found the post and tried to boot without plugging the 2nd drive in - success! But when I plugged it back in, no boot.
After a couple days of fighting with this, I solved it. The problem is that Windows 7 (I'm not sure about 8) does not like mixing GPT and MBR disks. If your boot drive is going to be GPT you must have your extra drive(s) GPT as well.
The solution: There is no easy way to convert the 2nd drive to GPT without data loss. I dual boot linux. Linux could still boot a GPT install while the 2nd drive is connected. Linux has a GPT-enabled partitioner called gdisk. Gdisk can convert MBR to GPT without touching the data.
All you have to do is run gdisk on the 2nd disk (the disk, not the partition) as in "gdisk /dev/sdb." Once it opens, it will list the disks (including removable disks) and whether it can tell if they're MBR or GPT, then it will have a warning box saying that it's going to convert to GPT and there's a potential of data loss. Of course, there always is potential if you're messing with partitions. If you don't want to risk it, press q to quit without doing anything.
Once you say yes, immediate press w to save it, then quit. Now you're done. That's it. Reboot and make sure you're booting the Windows Boot Manager (unless you have another EFI boot manager like grub working). Now, windows will boot without crashing and your other drive will be there. The only downside is that gdisk just assumes all partitions are windows partitions, so windows will show your non-windows partitions, but if you try to go into them, it will ask you to format them. You'll have to go back into Linux and change the partition types. I'm not sure if you can get away with that unless you format.
Thanks, Skullcraft. This was the only post I could find that helped me.