BSOD during "completing installation", First build, clean install. Heavily demoralized.

[lustyargonian]

Well hello. First PC build, very excited, I've waited far too long for this moment, and have invested too much to give up at this point. So 3 weeks ago I got all of my parts in. Asus Mobo was faulty, returned it. Learned to never trust used ebay computer hardware, (everything else was from newegg and has worked). Got new Mobo in, booted fine, started install on Windows 7. Computer restarts and stays on "completing installation" for a few seconds and then BSOD. This was a week ago. After reading many of these helpful forums and already running my memtest, I had been led to believe it was a defective HDD. So I went out with my new paycheck and dropped 150$ on the Samsung 840 EVO SSD 250GB. It's magical, at least in appearance and in weight. I wouldn't really know how an SSD boots up or anything because I have the same BSOD at the same time during " completing installation". I've searched far and wide on forum after forum to no avail and figured I should ask for help myself. Please, computer wizards, grant this noob the power to finish building this system that I've longed for in all my years of gaming. Please help me. Please.

FX-6300(stock, crap cooler)
Gigabyte 990fx ud3 rev4
Avexir core series ram ddr3 1600 Mhz 8GB (2x4)
Corsair CX500w PSU
INWIN GRONE case
GTX Galaxy 660
Samsung 840 EVO 250GB SSD


P.S. I think I've tried most of the common and/or obvious solutions, but by all means, shoot my with what you've got. I greatly appreciate your help whoever you are. This adventure has been one of both demoralization, embarrassment, and learning the hard way.

 

[Phillip Corcoran]

Tested the RAM modules? No? Use this: http://www.memtest.org/

You'll have to make your own bootable CD from the downloadable CD Image. Use "IMGBurn" to accomplish that:
http://www.filehippo.com/download_imgburn

Boot your new build from that CD and memtest will run automatically, it won't stop until you press the <Esc> key.
Any RAM errors will usually show on the screen within the first five passes, but you can run more passes than that if you want, just to be sure.

Each RAM module should be tested on it's own by removing the others before running memtest. This is so you'll know which module, if any, is faulty.