BSOD Newly installed OS various error codes

you are as fast as google dear sir! as I started to download I these exact links from mydigital life I came back to see if you knew of an official way to obtain these ISO's. Great minds think alike!! Once more thank you very much!

You're welcome. Let us know how the system responds after the repair install is finished. :)

So I downloaded the media and I still had issues installing, FINALLY I decided to stop ignoring a message I was receiving while trying to format a drive during install, something about UEFI and MBR so I googled it. One thing I found is that my recently purchased motherboard, that comes with new UEFI BIOS, has two forms of booting from disc, legacy and UEFI; well i was choosing UEFI without thinking about the message I went with legacy and windows installed better than before, HOWEVER I am still having some issues and they always come up when I am trying to use windows update so I ran SFC again and I am still getting some unrepairable corruption.

Code:

2012-04-21 11:42:46, Info                  CSI    000000a2 [SR] Cannot repair member file [l:30{15}]"StaticCache.dat" of Microsoft-Windows-Font-StaticCache, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-04-21 11:42:49, Info                  CSI    000000a4 [SR] Cannot repair member file [l:30{15}]"StaticCache.dat" of Microsoft-Windows-Font-StaticCache, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-04-21 11:42:49, Info                  CSI    000000a5 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-04-21 11:42:49, Info                  CSI    000000a7 [SR] Verify complete

You have some bad RAM. Try running with two modules at a time. Avoid Static Damage to Your PC when swapping out RAM. Also, when you bought the RAM, did you make sure it was compatible with AMD processors?

I figured, I bought it all together its still under warranty I will just change it all. BTW any recommendation on the code below?

Code:

2012-04-21 11:42:46, Info                  CSI    000000a2 [SR] Cannot repair member file [l:30{15}]"StaticCache.dat" of Microsoft-Windows-Font-StaticCache, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-04-21 11:42:49, Info                  CSI    000000a4 [SR] Cannot repair member file [l:30{15}]"StaticCache.dat" of Microsoft-Windows-Font-StaticCache, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-04-21 11:42:49, Info                  CSI    000000a5 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-04-21 11:42:49, Info                  CSI    000000a7 [SR] Verify complete

Would bad ram affect a windows install?

It can. RAM swaps data with the hard disk as Windows is installed and as Windows runs, so if you had corrupted RAM data during installation, it could have resulted in a bad install.

Marking this as solved, finally found the culprit, one bad memory stick and using UEFI booting were the culprits of all the corrupt installs therefore causing the BSODs. I used legacy boot and took out the one bad stick and now we are back to 100% much thanks to writhziden and all his patience and technical knowledge.

You're welcome. I am happy to see you were able to do further troubleshooting and resolve the crashes. :)