Windows7 getting corrupted! Every time!

[DanF]

Startup Repair again!!!

All I did was put on the chassis' side panel on. Not sure if it's coincidence, but it stopped working exactly when I put it in place. Mouse not working, keyboard not working, everything stuck

Restarted, got the Startup Repair GUI. Fixed and restarted. It's no OK again.

According to Event Viewer:

Startup Repair successfully completed repairs.
The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\tcpip.sys
Copied the following file from backup files:
Restored system to an earlier restore point.


and

Installation Failure: Windows failed to install the following update with error 0x800f0816: Security Update for Windows 7 (KB2506212).

What's strange is that D: is the optical disk. Copied the following file refers to nothing.

 

[andcorptech]

In my opinion its bad RAM. I could have missed it but i dont think you said it was replaced. I know you have tested it but i have seen computers with weird issues have RAM test fine but the problems only go away after its replaced.

 

[DanF]

Could be, but it's strange cause I did a 17 hour test.

Something else happened now. The OS crashed again and the display is just jammed, but I heard a POST beep as if the computer is just turned on and passed POST... but the display is still jammed on Windows!



EDIT: Pressed the Reset button and the the display just went on idle, but no POST.
EDIT 2: Turned off the system, turned it on again but nothing on screen. Num Lock LED is on but stuck.
EDIT 3: Left if off for a couple of minutes and turned it on again. POST passed, beeped and logged into Windows again.

 

[johnrobert]

You must have a few decent desktops kicking around in your shop
Give them one of those at a good price and be done with it.
Computers are so easy to fix once you have time and the heat is off.

 

[Mr.Mike]

An extended test was done on the HDD for around 1.5 hours... again, no errors.

Just wondering, what HDD test did you do? If I use CrystalDisk or HDTune it can take as much as 4 or more hours for long tests. I know you said you replaced the original HDD, but maybe try a more extensive and lengthier test.

My 2 cents.

 

[DanF]

UBCDs Western Digital tool.

 

[andcorptech]

Could be, but it's strange cause I did a 17 hour test.
.

Like i said ive seen them test fine and it still be the issue. Also i had a machine once that took nearly 2 days on memtest to finally fail. That machine was a pain also.

 

[DanF]

According to CrystalDiskInfo it is giving a caution on the Reallocated Sectors Count.

There are also 3 errors from DISK in the EventViewer, stating that the driver detected a controller error on \Device\Harddisk5\DR5.

What do you think?

EDIT: It seems like Disk5 in Windows Management is a flash drive, cause the one and only HDD is Disk0.
EDIT 2: According to WD's LifeGuard Diagnostics there are no errors, not even with the Reallocated Sectors (although to be honest CrystalDisk was only giving out a caution sign).

 

[Mr.Mike]

Hmmm. Not enough evidence of sector-related problems. Are you sure the media you are loading Win 7 with is good?

 

[PCX]

Hey, I just found out that a HDD we tested several times with different utilities and passed was actually defective. We had a similar issues and we eventually had to just send the laptop in for warranty and after several weeks they found out the HDD was defective, but it would not show up on any normal tests. So, I can't remember if you tried a different hard drive, but you may want to consider it.

 

[DanF]

HDD was replaced. No problems so far, so the DISK5 might have been the flash drive.

I just informed the client that will be keeping it for another 2 days, just to see what happens. I will be using it occasionally and will prepare a log sheet for the clients to fill.

 

[PCX]

Like i said ive seen them test fine and it still be the issue. Also i had a machine once that took nearly 2 days on memtest to finally fail. That machine was a pain also.

On that note, I have seen it where some piece of hardware are OBVIOUSLY failing, but not quite enough to be picked up by most diagnostics. This typically means you have to keep running diagnostics and stress tests till it finally does. This is fairly rare, but it happens. I am thinking that if the new hard drive works perfectly fine, then you either have run into one of those situations or you have a defective drive that you would not have been able to test properly anyways.