MSI Big Bang-XPower: Errors and Bluescreens Trying to Install Windows 7 64-bit

Question

Hello!  This is my first build since... Well, Pentium 3 really.  It's been an adventure learning the new hardware.  The PC components listed in my signature are the pieces to the machine I'm working on currently, and the one related to this issue.
It boots up just dandy, all the bright and shiny mobo lights blinking reassuringly, recognizes the full 12 GB of RAM in setup, and everything seems peachy until I get to loading the Windows 7 install.
I've tried using an old Vista disc I had lying around, no go.  Same issues.  I tried loading a different Windows 7 Pro 64-bit disc.  Same issues.
These are the error messages I'm receiving most often:
"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1.) Insert your windows installation disc and restart your computer.
2.) Choose your language settings, and then click 'next'.
3.) Click "repair your computer".
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \windows\system32\ntoskrnl.exe ((This changes every now and then, as does the status number. Always in the system32 file though))
Status: 0xc0000098
Info: Windows failed to load because the kernel is missing, or corrupt."
The error is inconsistent in the files it mentions, also often referring to:
"File: \windows\system32\config\system
Status:  0xc0000001
Info:  Windows failed to load because the system registry file is missing, or corrupt."
The HDD is still brand new and entirely blank, not yet even formatted.  I have not done much changing things around in the BIOS, because I haven't done much in the BIOS in a very long time, and I'd rather not accidentally make things worse without first obtaining external help.  I do not currently intend to overclock the machine, as I am a huge wuss and don't want to screw up my shiny new equipment with my noobsauce. XD
I did some searching around the Interwebs, and found references to similar problems where it was suggested that the person remove all but one stick of RAM and try loading the OS at that point, but it was also mentioned that one stick for that person would be 2 GB.  The least I have available to me is 4 GB, and I have attempted this with no change.  In this instance, flashing the BIOS to a new version was also recommended.  However, I have never flashed a BIOS before and am leaving that as a last resort unless otherwise advised.
Setup currently lists my BIOS Version as V1.2 060910.
It has on a few attempts made it past the 'Starting Windows' screen, and this is the kind of error I generally receive there on a bluescreen:
"STOP: c00002221 Unknown Hard Error
\Systemroot\System32\ntdll.dll"
Over the course of this build, I found that the two previous HDDs that I'd ordered from Newegg were dead and were neither consistently spinning up nor being detected by the mobo, but the current one seems to be recognized just fine.  I'd been worried it was a mobo issue, that it just wasn't recognizing them.
I've also read around, and am wondering if perhaps this could be related to a RAM incompatibility issue with the mobo and processor?  The RAM that was recommended to me for this build was Triple Channel DDR3 PC 1333, and is supposedly low voltage enough to play happily with the current equipment.
I'd thought to plug the HDD into another machine and format it/install the OS there, then hook it back up and see if it boots, but I have serious doubts as to whether that will ultimately solve the problem, and solving the problem is really what I'm after.
All the equipment save for the power supply and HDD were bought on Newegg.com.
Any assistance would be incredibly appreciated.  I'd really like to get the new baby up and running. 
:D

Answer 1

Welp, I wasn't a moron bios flasher >.>... It was stable when I flashed it, and it said it was successful... I cleared CMOS after it was done, did the reboot and load optimized thing and reboot again...
Aaaaand it won't go into Windows.  Now, I went back at that point and set all the settings back to what let it boot originally:  9-9-9-20, 1.6v, CR of 2... made sure it was booting in the right order, unplugged the USB...
And it freezes midway through the little windows icon forming, bluescreens, and shuts down.  I haven't been able to catch what it is yet, since it's crashing so fast. 
I tried to run the windows repair thing when the option was given after the crash, and it gets partway through loading the files and then crashes again, sending me right back to the same place.
*facedesk*
On the bright side, what files it does load seem to be loading quickly. _ _;
Edit:  Tried booting into my Ubuntu drive, no luck.  Just sits stuck at the startup screen.  Tried loading Failsafe Defaults... still crashes.  Still fiddling with it.  I'm hoping the fact that I can get into the BIOS at all means I didn't bust it, but never done this before.
Edit:  Managed to load into Startup Repair with just one stick of RAM in it, fiddling with it still and seeing what happens.
Edit:  _ _;; Bluescreened and restarted.  *facedesk... facedesk...* 
Edit:  Tried Startup Repair again, and it said 'Startup Repair cannot repair this this computer automatically.'  This was the information it gave:
Quote
Problem signature:
     Problem Event Name:          StartupRepairOffline
     Problem Signature 01:         6.1.7600.16385
     Problem Signature 02:         6.1.7600.16385
     Problem Signature 03:         unknown
     Problem Signature 04:         21200765
     Problem Signature 05:         AutoFailover
     Problem Signature 06:         2
     Problem Signature 07:         NoRootCause
     OS Version:                       6.1.7600.2.0.0.256.1
     Locale ID:                         1033
The mouse isn't lagging across the screen anymore at least, I guess.
Edit... Again >.>: After some searching around the web, it seems as though there have been other people with similar problems with other boards, etc.  Most suggested a repair or reinstall of Windows.  I don't have much on the drive installed yet that can't be redone, so I'm going to venture a reinstall.  Will post results.