Windows 7 freezes turn into inability to boot into anything

The error can relate to overclocked processor, faulty RAM and outdated BIOS.

Try also setting HD first to boot in BIOS, then trigger the DVD installer using one-time BIOS Boot Menu key.

I went and made the BIOS tweak that Dave76 suggested and re-booted. Same steps as above (except I didn't do the Diskpart step) and it hung again in the same spot, but this time no BSOD.

I'm initial google findings on this BSOD is that it most often happens with OC'ing and NOT during a Windows Install.

As I stated earlier, I'm not OC'ing my board (still using the Fail-Safe Defaults with the RAM values adjusted).

I'm ready to take the whole thing to the dump right now!!

Oh, one other thing that I haven't mentioned because I didn't think it had anything to do with my problem.

For about a month, month and a half when my computer 'wakes up' in the morning, I have something like wavy vertical lines on my monitor. This usually lasts about 5 minutes until it goes away. I ONLY see this when the computer 'goes asleep' for any real length of time (30 minutes plus, but I've never actually timed it).

My LCD monitor is something like 5,6 years old so I was thinking it might be the monitor.

I notice no other graphics issues, although I don't really strain the card - I play an occasional game of Doom and Doom 2 plus some FaceBook games. My oldest son will play StarCraft 2 and WarCraft 3 with no problems, but again, I don't know what kind/type of stress that really puts on a video card.

I mention this now because there isn't much else connected to my PC that might be causing my problems.

What about the BIOS version update, and have you tried install with HD set to boot first in BIOS as well as flash stick install with OD unplugged?

All possibilities need to be eliminated until the finger points at mobo.

gregrocker said:

The error can relate to overclocked processor, faulty RAM and outdated BIOS.

Try also setting HD first to boot in BIOS, then trigger the DVD installer using one-time BIOS Boot Menu key.

My BIOS is version 1.8.

The current MSI BIOS is version 1.C

Again, I'll flash the BIOS if you think I need to, but I don't really like doing that (prior bad experiences).

My HD is already the first in the boot sequence.

gregrocker said:

What about the BIOS version update, and have you tried install with HD set to boot first in BIOS as well as flash stick install with OD unplugged?

All possibilities need to be eliminated until the finger points at mobo.

My HD is listed first in the boot sequence.
I've unplugged my OD and hit F11 to get to the boot menu and then boot with my USB stick.

Does it matter that I've never seen that BSOD before?

Essenbe,
One of the items in that post you highlighted that caught my eye was a comment about dust.

Recall that I stated that I had taken a can of compressed air to blow out some dust.

Now, you guys are the experts and I'll do what you suggest...

...but I'm wondering if this just may be a one-time thing and we shouldn't let it get in the way of trying to figure out why Windows 7 keeps hanging on install.

And if I read and understood that post correctly (a BIG 'if') it seems that the BSOD may even be caused by software (the Windows Install hanging?).

Anyway, like I said, you guys are the experts, I'll do what you recommend.

Dust comes into play with overheating. Can you enter BIOS setup to see if temps are given? Blowing out the dust can not solve the problem if the heatsink is clogged or CPU needs repasting. The error starts pointing the finger at the CPU if it wasn't already.

Do you have another computer you can move HD into, install Win7 with all other HD's unplugged, then SysPrep it to move it back to problem computer? SysPrep to move HD to another computer

The reason is that you have more options for reading BSOD, temps, more safely updating BIOS, etc. from an OS. What happens when it starts up fresh will also be instructive.

You can also start another machine's image on the HD if you first boot Paragon Adaptive Restore CD to prepare it on the problem PC.