Strange Problem with winload.exe

Running Windows 7 Ultimate x64. I have setup a partition which I transfered from on drive to another and now my boot partition is on an SSD Raid array connected to an LSI 9260 controller.

Here is what is funky:

If I boot the computer with the RAID Array first, the computer will just hang there. No message no nothing after the Verify DMI success message.

If I setup my computer to boot from CD first and the the RAID Array second and with a bootable CD in the drive, the BIOS will display the "Press any key to boot from CD" If I don't touch anything, then windows will load just fine when the boot sequence switches to the RAID Array.

It would all sound like I have a RAID Card problem until I ran into this:
If I put no CD in the CDROM Drive, then the computer will hang on a little longer on after the DMI message and Windows will start trying to boot from the RAID array and post me the Winload.exe is corrupt or missing message with error code 0xc0000001e.
I have tried all the startup repairs which found nothing wrong, visited all the bcdedit tricks as well as all the bootrec (all 4 of them).
If Winload.exe is corrupted then how does it boot when I have a CD in there? Does it read the winload from the CD even though it is not booting from it?

This is what my BCD looks like


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {fa432900-89bc-11e0-aaa5-8d4d80542ab6}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\System32\Winload.exe
description Windows 7
locale en-US
recoverysequence {fa432902-89bc-11e0-aaa5-8d4d80542ab6}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {7edce3c7-8a7f-11e0-8b68-806e6f6e6963}

Try
Reinstalling the RAID drivers.
Remaking your RAID.

I personally would stay away from RAID, as it seems to more problems than it is worth.

Agree with Ray: I would break the RAID and install to single HD with other unplugged. RAID provides no redundancy and can cause you to lose everything if one HD goes. I'd use the other HD to store Win7 backup image.

To attempt to repair, boot into DVD/Repair CD Repair Console, run Startup Repair repeatedly making sure Win7 partition or it's 100mb System Reserved boot partition (preferred) is marked Active:
Partition - Mark as Active
Startup Repair - Run 3 Separate Times

Installing into a single drive is not an option. I want the performance benefit of my RAID array on my boot drive (I am getting 1.7GB/s seq read). I have run RAID arrays as boot drive for years and I am not going back. It has never brought me any trouble until this one. I am no newb.
Again I have already tried the windows recovery console route multiple times and it does not find any problem. Yes the drive is marked as system and active.
I have also just tried reinstalling the driver but somehow it does not make any sense: The error occurs before any driver is even being loaded.
I also tried the same experiment using another boot CD and I observe the same thing: If I boot from the CD and ask the CD to be bypassed and move on to the next boot drive, Windows boots fine. What really puzzles me is why it cannot find the Winload.exe when I boot from the drive without a CD in. I am suspecting some drive letter assignment problems with the partition or the BIOS on my motherboard or the RAID card.