Windows 7 freezes turn into inability to boot into anything

[gregrocker]

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.

 

[Jacee]

From Intel forum Intel i5 760 Quad Core BSOD Error

 

[Jacee]

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

This is about all I could find too.

 

[cnauta]

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.

 

[gregrocker]

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.

 

[cnauta]

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.

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]

You May want to read this thread particularly Post# 5 which says

View attachment 194129

Edit: seeing how you have 'nuked' the OS, it is a safe bet that there is no software or driver causing this problem.

 

[cnauta]

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.

 

[essenbe]

It is an extreme rarity that any windows driver will cause a BSOD. In many dump files they get blamed, but that is only because the real driver causing the BSOD is unknown, so it is blame on a system driver. But again, It is highly unlikely it is a system driver or software.

 

[gregrocker]

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.

 

[essenbe]

To explain. You have no software on the computer. The OS is nuked and therefore all software and drivers are gone. I'm not an expert, but as I see it, you have a hardware problem, which we have suspected from the beginning.

 

[writhziden]

Mind if I make a suggestion? I am not sure if this has been tried, but it can sometimes resolve install and boot issues.

1. Go into your BIOS and load default settings to clear the CMOS memory.
2. Save Settings and exit the BIOS.
3. Shut down and turn off the computer.
4. Unplug the computer from the wall or surge protector.
5. Hold down the power button for 30 seconds to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory. This closes the circuit and ensures all power from components is drained.
6. Plug the computer back into the wall.
7. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back whether you are able to install Windows.

 

[cnauta]

Completely removed - ate lunch and feel a little better.

 

[cnauta]

Update:

Booted up and went into the BIOS to check temps.

CPU temp would climb as high as 27C/80F and then go back down to 25/77.
System temp would get as high as 30/86 but would fluctuate between that and 29/84.

I then followed writhziden's suggestion and it almost worked!

It got through the EWF, booted up and then almost completed "Finishing Installation" (the green bar was about 90-95% done!)

That might have been worse than it freezing during EWF (I really thought it was going to work this time).

So what is the recommendation now?

I think I'll try installation one more time, but after that I don't know.

Should I still get a new HDD, or is the prevailing thought that the problem is something/somewhere else?

UPDATE 3:13 PM EST
~sigh~

Tried the installation again and again got the "clock interrupt" BSOD.

So, does that mean it's the CPU?

If so, how do I diagnose that to make sure?

Also, if so, can I fix it or do I simply buy a new chip?

Oh, and if it is the CPU, would that explain our previous problems or do I ALSO have a faulty HDD?

 

[writhziden]

The fact that my suggestion helped leads me to believe you have one of two possible problems:
1. Memory is bad/incompatible...
2. Hardware is faulting or something is not seated properly...

Your temperatures look good, so I doubt they are to blame for the installation issue. You could follow steps 3-5 (for your safety this time and the safety of the components) and this time take off your case and remove all cards, modules, peripherals, etc. and then re-seat them in the slots to make sure they are seated properly.

Edit: Also, make double sure all power lines are plugged in properly and in the right place. I had a NB fan plugged into a CPU fan plug once, and my computer kept thinking it was overheating because the NB fan could not spin fast enough, but the CPU was actually not getting above 40C.

 

[cnauta]

The fact that my suggestion helped leads me to believe you have one of two possible problems:
1. Memory is bad/incompatible...
2. Hardware is faulting or something is not seated properly...

I ran Memtest last night (7 passes (almost 8)) and there were no errors.

I would assume this removes the first option (then again, I've been wrong almost this entire time).

Your temperatures look good, so I doubt they are to blame for the installation issue. You could follow steps 3-5 (for your safety this time and the safety of the components) and this time take off your case and remove all cards, modules, peripherals, etc. and then re-seat them in the slots to make sure they are seated properly.

I will get right to this.

BTW - did you see the update to my previous post. Does that change anything?

 

[writhziden]

The fact that my suggestion helped leads me to believe you have one of two possible problems:
1. Memory is bad/incompatible...
2. Hardware is faulting or something is not seated properly...

I ran Memtest last night (7 passes (almost 8)) and there were no errors.

I would assume this removes the first option (then again, I've been wrong almost this entire time).

Your temperatures look good, so I doubt they are to blame for the installation issue. You could follow steps 3-5 (for your safety this time and the safety of the components) and this time take off your case and remove all cards, modules, peripherals, etc. and then re-seat them in the slots to make sure they are seated properly.

I will get right to this.

BTW - did you see the update to my previous post. Does that change anything?

Any possibility the CPU is not seated properly? That could account for the problems, though I would find it unlikely since the cooling fan usually applies enough pressure to push it into place if it is not seated properly to begin with. If you reseat it, be careful removing and re-seating it as it may be hot, and make sure to apply the coolant paste again. I will look into other possible causes of that error code, as well.

As to the RAM, Memtest86+ is not 100% accurate. I'd say it is probably 95% accurate. I usually recommend the Windows Memory Diagnostic as a secondary check to make sure Memtest86+ did not miss anything. Even both together can miss incompatibilities or bad RAM. Sometimes diagnosing memory problems can come down to removing modules and just seeing if the system behaves in a more stable manner.

I'll need to re-read this thread to see what the hard disk errors are. I'm not up to speed on that, but someone else who has been helping you might be able to make a suggestion to the hard disk problems.

This information may be relevant: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received --- which points to a possible CPU Vcore calibration issue. It's a different board, but it may be worth looking into. You may also want to contact the Motherboard manufacturer, MSI, and ask for assistance. Maybe this is a known problem with the board. CPU problems are very rare (though I have seen one bad CPU in my two+ months on these forums), so I would blame the motherboard before the CPU.

 

[gregrocker]

These are pretty good vid for those who haven't done it before:

 

[writhziden]

Also, further information about the blue screen crash done by usasma, who is very good with hardware problems: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

 

[writhziden]

Okay, I'm a little more up to speed. Your Western Digital diagnostics came up clean, meaning the drive may be fine. You were unable to run disk check initially. Have you run since? You can do so through Windows Installation by pressing Shift + f10 to access the command prompt, see http://www.sevenforums.com/tutorials/682-command-prompt-startup.html. chkdsk /r (driveletter): You may have to determine the drive letter by typing letters and Dir commands in the prompt. I also note a virus was on your system. You will want to do a clean all using Diskpart to make sure the virus cannot be in the rootkits.
Command prompt example.

C:
dir
D:
dir
E:
dir
chkdsk /r C:
chkdsk /r D:
chkdsk /r E:​

Run the chkdsk on the disk/volume you are installing to.
For diskpart clean all, see http://www.sevenforums.com/tutorials/52129-disk-clean-clean-all-diskpart-command.html which is also run in the command prompt.