Windows 7 freezes turn into inability to boot into anything

[essenbe]

Since you have already run the clean all once, In order to speed it up for you, just run the clean command, just type clean instead of clean all.It will take almost no time. Also, when you get to the formatting stage of diskpart run format fs=ntfs quick. That will do a quick format and is what the installer would do anyway. When you get to the installation phase, just install, don't format. You won't get the 100MB partition.

 

[cnauta]

Status Update:

With one stick (only) of 4 GB RAM installed, my 2 external hard drives disconnected and using my USB stick with the Windows 7 SP1 ISO here is my latest series of attempts to install Windows 7:

- My last "Clean all" attempt (see previous post) hung up. I gave up around 5:45 and found out the screen was frozen.

- Re-booted and decided to skip "clean all" and went to create the partition (successful) and format (successful) and activate the partition (successful). Exited out of Disk Part and began installation. It got to "Expanding Windows Files" (EWF for future use) and hung almost immediately.

- Noticing that I might have a pattern going on here (each time I re-boot I get a little further), I re-boot, go straight to Windows install, get to EWF which starts the "..." animation and then hangs.

- Re-boot, into Windows install, get to WEF which gets all the way to 18%. I do a little googling on Windows install hanging at this step and find several directions to remove as much as possible (all USB drives, 1 stick of RAM, etc.) The only USB attachment I still had was my Wireless Adapter, which I then disconnected.

- Re-boot, into Windows install, get WEF which actually FINISHES!!! Woo Hoo!! Computer re-boots itself, gets past the Window's start screen to the "finishing Windows install" screen where it appears to have hung almost immediately (I can't speak for the exact timing, I stepped away from the computer for a moment).

- Re-boot, starts Windows, get an error message that the install is bad and I need to re-start it.

- Re-boot, I let it go right to Windows (I thought this was the way to re-start the installation once it had started), and get the error message again.

- Re-boot into Windows install off of the USB stick, get to EWF where it hangs at 16%. I'm really getting discouraged now and am ready to throw the computer out the window. I remember some other notes about Windows hanging at this point wherein the ISO is questioned. While I would love to avoid all the lengthy updates, I decide to try installing from my OEM (pre SP1) DVD.

- Re-boot to Windows install off of the DVD, get to EWF where it hangs at 0% after starting the "..." animation.

I really don't know what to do now. I really thought this (re-installing) would be the easy part. I'm just stubborn enough to continue to re-boot (as long as I keep getting a little further each time), but I don't know why that would work (and wonder if I could/would trust my installation after this).

I can't get to a store today, but I'm just about locked in to go and buy a new hard drive tomorrow.

But, again, I'm not totally sure that would solve the problem.

So, again, any/all help/advice is greatly appreciated.


UPDATE (7:15 PM EST)
Using Essenbe's "shortened" DiskPart instructions, I successfully completed them and am installing (got past EWF and the computer just re-booted itself and starting Windows). I'll update as events warrant.

Essenbe, any thoughts on those BIOS settings?
If/when I get Windows installed, can I, SHOULD I reinstall the second stick of RAM?

 

[gregrocker]

We've had users run it thousands of times here and the only time I've heard of Diskpart faiilng is with a failing HD. I dont' know why else it would fail repeatedly.

You said Disk Check has found dozens of errors but none recently. This makes the HD doubly suspect.

I would try another HD before beating up myself and hardware any further.

 

[essenbe]

I think I would use tonight to run memtest86. Let it run for 7 passes or until you get an error. here is the tutorial on it. Just boot into the CD or USB whichever you have and let it run as long as you can. Remember you are not only testing the ram sticks, but also the motherboard dimm slots. It is very possible that you have a ram problem. As I remember, yesterday you couldn't boot into windows until you removed 2 of the sticks. If you suspect the Hard drive, you could disconnect the power cable from it. That way if you BSOD, you will know it is not the hard drive.
That's just a suggestion. We are really trying to tell which piece of hardware is causing you issues. hard drives are rather expensive right now. If you have another or know someone you could borrow a hard drive from temporarily, you could try to install on it, and not have to buy something unnecessarily.

 

[cnauta]

My install attempt (see my update on my previous post) hung (again) on the "Completing Installation" screen.

So, I re-inserted my USB Windows install ISO and re-booted. Again used the "shortened" Disk part instructions, exited out and it again hung on the EWF (0% but it had started the animation).

I am going to take Greg's advice and pick up a new hard drive tomorrow (any suggestions for a good SATA internal HD?)

(Hopefully) final thoughts for tonight:
- I'm sold that the HD is bad. Any explanation, though, on why it passed the Life Guard test 3 times? Again, I'm not questioning the need for a new HD, I just don't know what to make of a diagnostic test not working (or being trustworthy)

- Any comments/suggestions on those BIOS settings?

- Should I put the other RAM stick in or wait until the new HD is installed and Windows successfully installed?

Again, thanks SO much for all your help (especially Greg and Essenbe). You always hope (and even think!) that you can solve it yourself (and that there is only one problem to fix!). It's nice to have experts there to help you, though, when you can't.

 

[cnauta]

I think I would use tonight to run memtest86. Let it run for 7 passes or until you get an error.

I currently have only 1 stick of RAM installed.

Should I install 1 more or 3 more before I run memtest?

 

[essenbe]

Conventional wisdom, I think is run 1 stick at a time, but I believe I would run 2. If those pass, I would run the other 2. The only problem with that is if you get an error, you won't know which stick it is. But, if you don't really think it is ram, run 2 and if they pass, install with them.

 

[cnauta]

I put one stick back in and started running Memtest about 12 minutes ago (a little after 8:00 PM EST). I usually go to be close to 11, so it should get through a couple of passes before that. I'll update this post with that info. Essenbe, I'm not saying that it ISN'T the RAM (I suspect a bad DIMM, in fact), but I also have a problem believing that I just bought 4 bad sticks of Crucial memory. That said, this entire experience has been maddening for me. There have been numerous clues (many that have been inconsistent in their appearance) that have pointed to several different things. Was it a virus? The RAM? The HD? Right now the answer looks like "Yes, a little of all of the above." BUT... ...I will continue my diagnosing. Hopefully I can trust Memtest more than Life Guard.

 

[essenbe]

That's what makes it very difficult to work on a computer with more than 1 problrm. You never know what is causing which problem.

 

[gregrocker]

Jonathan sorts out the way to test RAM sticks and slots with multiple sticks here: RAM - Test with Memtest86+

Dave also had some important steps for you to consider earlier.

I regret the clean reinstall didn't get you past the problem. As I mainly specialize in Installation I'll leave you in Essenbe's capable hands.

My comment to change HD's is what I would do in this situation to eliminate it as the possible problem.

 

[cnauta]

So here it is, almost quarter after 11 (EST), and Memtest is slowly working its way toward finishing its 3rd pass. No errors yet, but I'm learning that that might not mean much. I'm hoping and praying that when I get up tomorrow morning that I'll find no errors. I'm thinking that if the RAM passes then the last suspect is the HD and I'll head out tomorrow to pick up a new one. I'm hoping that it's not some kind of MB error - I don't have the time, money or energy to replace the MB. Anyway, before I head off to bed, a quick question for anyone - why is it recommended to run Memtest 7 times (or over-night)? Can you really find errors on the 7th pass that didn't show up the other 6 times? I'm not being sarcastic, just genuinely wondering. Thanks!

 

[Dave76]

Memtest86+ runs many different tests, I have seen many times that RAM will get errors on the later passes and seem like test #5 & #7 show more errors, generally speaking.

The can be issues with running 4GB of RAM or more, since you have 4X4GB cards, even a single RAM card may be causing these issues.

When these motherboards were designed the average RAM card size was 1 or 2GB, now you are running a single card with 4GB of memory chips on it, that takes more power (voltage). Depending on your motherboard specs, build quality and design, this might be affecting your system stability and OS installation.

Do you have any old RAM lying around?
A 1GB or 2GB RAM card, one single card, may allow your system to get the OS installed. Then it will be easier to analyze the hardware.

Can you post the part number of your RAM?

Have you disconnected everything that is not essential, sound card, speakers, printer, etc.?
Do you have another graphics card to test with?

Your BIOS settings look good, just change the RAM frequency back to motherboard stock 1333MHz.
Change the CPU VTT to 1.20v.
This will reduce the chance of any RAM issues.

What BIOS version are you running?
There are a lot of memory related BIOS updates listed: MSI P55-GD80

From your last crash: STOP 0x0000009C: MACHINE_CHECK_EXCEPTION
Starting with Windows Vista, this bug check is no longer supported, and has been replaced with bug Check 0x124: WHEA_UNCORRECTABLE_ERROR.
Usual causes: Hardware error,
Which doesn't help much.

From the problems you've had with your HDD I would start there, try another HDD or as you mentioned get a new one.

 

[cnauta]

Good morning! So I ran Memtest with 2 RAM modules (2x4GB) installed (DIMMs 1 & 3). It ran all night, completing 7 passes and almost completing the 8th. There were NO errors. I suppose this now points the spotlight to the HD. So before I run up and buy a new one, any other tests, diagnostics, etc. I can do/run/check in order to rule anything else out? And I again thank you all for your time and help!

 

[cnauta]

Do you have any old RAM lying around?
A 1GB or 2GB RAM card, one single card, may allow your system to get the OS installed. Then it will be easier to analyze the hardware.

Can you post the part number of your RAM?

I would be more than happy to do this, but with the RAM passing Memtest is it necessary anymore?

Have you disconnected everything that is not essential, sound card, speakers, printer, etc.?
Do you have another graphics card to test with?

I had disconnected just about everything but the sound card.

I don't have another graphics card to test with, unfortunately.

Your BIOS settings look good, just change the RAM frequency back to motherboard stock 1333MHz.
Change the CPU VTT to 1.20v.
This will reduce the chance of any RAM issues.

Thanks! I'll change that the next time I boot up.

What BIOS version are you running?
There are a lot of memory related BIOS updates listed: MSI P55-GD80

I'll have to check the next time I boot up. It's not the original version but neither is it the most up-to-date.

I need to say, though, that I'm a bit 'squeamish' when it comes to flashing the BIOS.

I DID successfully update this MB's BIOS once, but I also 'killed' a previous computer of mine when attempting to flash the BIOS.

If you think I should update my BIOS, though, I'll go ahead.

From the problems you've had with your HDD I would start there, try another HDD or as you mentioned get a new one.

Any suggestions/recommendations on brand?

I've been partial to WD and Seagate. Your thoughts?

 

[essenbe]

I use both WD and Seagate. I think either one would be OK. I am parial to Samsung 1TB HD103SJ though. I have several of them and they seem to do very well and are pretty fast.

 

[cnauta]

I use both WD and Seagate. I think either one would be OK. I am parial to Samsung 1TB HD103SJ though. I have several of them and they seem to do very well and are pretty fast.

Thanks! I'll look for the Samsung when I go out later.

Before I do that, though, after everything we've done here, all the diagnostics and attempts to get my computer to run...

...how confident are you that the (remaining) problem is the HDD?

I'm beginning to worry that it may be the MB, but I don't know how to diagnose that without a new/different HDD.

Oh, and one more bit of information:
After Memtest finished running I shut the computer down for awhile and then attempted one more time to install Windows (this time with the 2 sticks of RAM).

It AGAIN hung on the EWF step.

 

[Jacee]

If you can get into Windows, see if these processes are listed:

[%PROFILE_TEMP%]\winlogon.exe <-- malware intruder
[%SYSTEM%]\qch29sr.dll <--- could be another random .dll file
[%WINDOWS%]\inetloader.dll ('C:\WINDOWS\inetloader.dll')


​

 

[cnauta]

If you can get into Windows, see if these processes are listed:

[%PROFILE_TEMP%]\winlogon.exe <-- malware intruder
[%SYSTEM%]\qch29sr.dll <--- could be another random .dll file
[%WINDOWS%]\inetloader.dll ('C:\WINDOWS\inetloader.dll')


​

Jacee,
Thanks for the information, unfortunately my situation is that I've 'nuked' my HDD (Diskpart Clean All) and have been unable to re-install windows (hangs on the Expanding Windows Files step).

 

[essenbe]

Jacee, He dosen't have a Windows installation right now. We ran a clean all on his hard drive to try to get rid of the virus/trojan. He reportedly had Win32/Small.CA virus. We ran scans with Malwarebytes, MSE and Microsoft standalone system aweeper. None detected the virus. Is there a program that can scan his computer that will detect it? We backed up his personal files to an external hard drive, and would like to find some way of being sure that they do not contain the virus before transfering them back. Thank you for helping here. We were going to post in the Security thread as soon as we got these problems sorted out. Now that we have a security expert like you, that won't be necessary.

 

[cnauta]

Hey, I got a new BSOD!

I was reading up on the "Windows 7 Install hangs on Expanding Windows Files step" issue and there was a lot of advice to strip the PC down (remove all unnecessary HW) and try again.

Now, I already had most all of my USB attachments removed (all but my keyboard and mouse).

I then removed my 2nd RAM stick (leaving just 1), my sound card and unplugged my CD/DVD player.

Oh, I also used a can of compressed air to clean out some of the accumulated dust inside my case.

So, I boot into Windows Install from my USB stick, get to a command prompt, do the quick & dirty Diskpart routine (clean vs clean all, format quick vs format), exit out and it again hangs on the EWF step (0%).

This time, though, it goes to a BSOD:

A clock interrupt was not received on a secondary processor within the allocated time interval

0x00000101 (0x0000000000000031, 0x0000000000000000, 0XFFFFF88003963180, 0X0000000000000002)

I'm going now to google this.