This is a reply to the thread: forums dot evga dot com/Motherboard-code-starts-up-at-quotFFquot-but-computer-doesn39t-boot-m1249346.aspx
 
Specs:
Mobo: Asus Rampage III Black Edition
CPU: Intel i7 920 @ 2.67 GHz
GPU: EVGA Geforce GTX-680 2GB
RAM: 3x4GB Corsair Vengeance 1600MHz
Case: Thermaltake Level 10
OS: Windows 7 Ultimate x64
 
I didn't want to necro that post and I'm not sure where to post this so here's what happened in reply to that post:
 
I was indeed getting that FF post error code, the exact same problem "The_Guy" was having and it all started when I decided to install a Windows update. The Windows update in question was "silex technology, Inc. - Other hardware - SXUPTP Driver." After a short google search, I found out this update has something to do with handling USB. And it seemed innocent, it was also the only major update my system needed so I decided to go ahead and install. The installation started for about 10 seconds and then I was hit with a BSOD, couldn't catch the error code and my mini-dump was already deleted because of CCleaner (my fault for clicking it's popup).
 
Just like The_Guy in that thread, my computer did the turn-on-turn-off thing twice then turned back on and booted normally. The error code on my mobo said "F.A." which, according to my manual, means "Invalid Recovery Capsule" and I have no idea what that means only that it has something to do with the BIOS. I used a USB drive to flash my BIOS with an update and my computer restarted. It did the turn-on-turn-off thing again but only once then booted normally with a post code of "F.F." which can either be good or bad according to most forum searches... Then I found the thread up there with The_Guy having a similar problem. I used nick1551's solution to remove the CMOS battery for 10 minutes. After doing that I turned my computer on and was delighted to see it posted normally with no hiccups. I reset the time in my BIOS and all is well now.
 
This was quite an ordeal, I still don't know why that Windows update gave me such a headache but I'm hiding that update from now on. If you have any ideas as to why it might've given me a BSOD, I'm open to hear it. I'm just glad I could fix the problem it caused.
 
The only thing I can think of that is related to my USB is one or two of my USB slots is damaged. A few years ago, I had my iPhone connected to it and I accidentally jerked on it really hard. Now, one of the USB slots only works from a certain angle. I can't remember which one though, the Level 10 has too many USB slots on it. But how a silex update can cause a BSOD from that I have no clue.
 
I'd like to thank JeffreyHam, nick1551, and rblaes_99 for the solution in this mess. Thank you all very much! I would hug you fellas if I could. You deserve a thumbs up! My computer is working normally again and I'm happily back to gaming and searching cooking recipes... Speaking of, it's 3:45 AM and this ordeal has cost me all night to fix and I never had a chance to cook dinner. Time to eat, thanks for reading and see you all later.