[SOLVED]MoBo or OS stopped recognizing RAID 0

[soulsabr]

CPU : AMD FX 8150
GFX : Nvidia GeForce 560
MoBo : Asus Crosshair V Formula
RAM : 16 GB Corsair Vengeance
OS : Win 7 Ultimate
Tech Skill : moderate but rusty

So, I have a pair of WD Black Caviar 1GB drives set up in a RAID 0 config running on my system that I set up sometime last fall. No problems for about 7 months. Then, two days before finals, my system won't boot. Turned off the splash screen in my bios, which was back on for some reason, and got the no OS message. Rebooted to get into the bios again and noticed that the info screen for the RAID setup wasn't being displayed. Both drives are being recognized by the system but am unsure if one is corrupted or dead. Also not sure how to check without nuking the drives which would force me to re down load over half a terabyte of games and what not.

What was I doing, you may find yourself asking. What did I install? Well, I installed GNU Octave a week before the problem occurred. Octave ran well and I had no issues. No other installed or removed programs or hardware. No signs of trouble. Just one night I was up studying. I powered down. Next day I couldn't boot. I'm hoping it is a corrupted driver so a simple rescue will work but I'm not holding my breath. Any tips or advice would be greatly appreciated.

Current status : Staring at the Windows repair screen and getting ready to load the RAID driver from USB all while praying I can recover my raid partition

[soulsabr]

Ok, so the issue occured to me when I wrote the problem post. If my ROG splash screen was back up what else had changed in the bios. A quick look around revealed that the bios wasn't set to recognize the RAIDed drives. Setting it back to RAID solved the issue. I'm still wondering why the bios changed to start with. Any clues here would be appreciated as this makes me wonder if my bios is ok.

[HiVizMan]

It is possible that a power surge or some other unexpected power fluctuation could have caused your BIOS to have a moment. I have had this happen when one of my kids accidentally removed a connected piece of hardware while the system was powered up. In that instance it was a powered USB device.