Hard drive faliure after Windows Updates

April 10, 2012 at 18:51:19
Specs: Windows 7
Have a very weird problem.....

After installing Windows 7 Ulitmate 32 bit successfully and validating licence, I installed all of the available windows updates (inc. all optional updates). After successfully installing all of the updates, I received the BSOD when restarting the machine.

Now...when it restarts, it gets to the windows 7 logo and just hangs until I reboot machine and repeats.

The bad part it that startup repair cannot sort the problem, trying to re-install windows 7 doesn't work as the hard drive is not recognised at the installation screen, and in the bios it is not recognised either. Plugging the drive into a desktop pc via sata results in desktop crashing and wont reboot until the hard drive is disconnected.

If it was truly a dead drive, it wouldn't get as far as the windows 7 logo at all would it? Very confused by this one. Any help would be appreciated


See More: Hard drive faliure after Windows Updates

Report •

#1
April 10, 2012 at 21:10:11
It does sound like it may be a bad drive. Run the hard drive manufactures utility via a bootable CD or DVD and let it test the hard drive. If it recognizes it, it may be able to tell you for sure if there is a problem and if it is a minor problem, then it may actually be able to fix it. If it is not recognized by your BIOS, the utility will not see it at all. If the drive is really bad, you may get little information about it, but that will at least tell you something.
Note also that a memory issue can also appear to be a hard drive issue so you may want to run Memtest first via a bootable CD to see if that is the problem (though the test you already did with the desktop should indicate it is probably in the hard drive).

You have to be a little bit crazy to keep you from going insane.


Report •

#2
April 11, 2012 at 02:19:54
Is this a new drive or one from an older system? If it is new see about returning it. If it is older I'm sorry but mechanical parts fail sometimes. Have you heard any ticking from the drive before?

Likely


Report •

#3
April 11, 2012 at 08:35:28
You have not provided any info about the system this hard drive is on.

What make and model is the brand name system, or if it's a generic desktop system, what make and model is the mboard ?

Was the same computer with the same hard dive working successfully with Windows 7 previously ?

If yes, have you changed which ram you have installed ?

If it's a desktop system, and a SATA hard drive...

Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)

The same thing applies for the SATA power connection.


Report •

Related Solutions

#4
April 11, 2012 at 12:57:45
Use hard drive diags if you feel it is the hard drive. Try memtest also.

The only reason an update would bork it is either some data or hard drive issue.

Do tests, complete tests and then reload again from scratch.

Text, talk, drive...CRASH.

Hang up and drive @#$%^^


Report •

#5
April 11, 2012 at 20:50:26
Jefro: Like:
"Text, talk, drive...CRASH.
Hang up and drive @#$%^^ "
I had not noticed it before.

You have to be a little bit crazy to keep you from going insane.


Report •

#6
April 12, 2012 at 03:57:48
Run Smart test from BIOS if available.

Report •

#7
April 12, 2012 at 12:55:03
I really hate people on phones. Every day I risk my life when I see them change lanes on me, follow in my blind spot, and basically drive worse than a drunk person. I have even had the finger flown when I blow the horn on them.

Only 1/3 of fatal car deaths are caused by alcohol. The other 2/3's are just as bad as a drunk person.

Text, talk, drive...CRASH.

Hang up and drive @#$%^^


Report •

#8
April 12, 2012 at 13:39:22
Where I am, the province recently passed a law that allows law enforcement to charge a driver with "Distracted " driving, for which you pay a substantial fine. It covers "Distraction " caused by many things, but the primary reason for it was because of the excessive number of idiots talkng on cell phones and texting while driving, and not while the vehicle was not moving, which is the common sense thing to do.
However, drivers ARE allowed to use "hands free" methods of answering or calling from a cell phone, despite the fact that studies have shown that's nearly as distracting as having the cell phone in your hand next to your head, and our law enforcement officers (local police, provincial sherrifs, the RCMP, etc.) were already overburdened before the law was passed (the governments have not been hiring enough people for many years).

Before that law was passed, there were lots of people I was following behind who weren't just answering a cell phone, they were making one call after another, sometimes the entire time I was following them.
I've seen no one using a cell phone next to their head since the law was passed, but on the other hand, I drive a lot less than most people, and I avoid driving in "rush hour" periods nearly all the time. According to the local media, some people are still using the cell phone next to their head and texting on the sly while driving.


Report •

Ask Question