Windows 7 won't boot, corrupt file message

Hi Win 7 Experts,
Have a machine that ran great last week and over the weekend it somehow got itself into a loop where it won't boot.  It'spossible the last user on it downloaded something, really hard to say but the user rememebers using it fine on Friday but over the weekend now in a reboot it displays Windows System Repair everytime and eventually leads to a message that Windows can't  boot . . .startup repair offline - problem signature (bunch of data here) - and the mesage in the end is corrupt file - os version.  It doesn't list the file though.

Is there any information that it posts here that we can use to narrow down the error?  If not, what's the best way to proceed?  Hardware diagnostics (built in OEM stuff) seems to think the machine is okay.

Who is Participating?
IanThConnect With a Mentor Commented:
does your domain have a good virus program installed

I have seen a rise in virus's, rootkits and spam this year  
JsmplyAuthor Commented:
Stand alone PC in this case.
JsmplyAuthor Commented:
Here is the exact info:
problem signature1 :  6.1.7600.16385
problem signature2:   6.1.7600.16385
problem signature3: unknown
problem signature4: 21.200.816
problem signature5:  auto failover
problem signature6:: 19
problem signature7: corrupt file

Tried fixmbr, fixboot, and rebuildbcd already.
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Gerwin Jansen, EE MVEConnect With a Mentor Topic Advisor Commented:
Hi, did you try booting from the W7 install DVD and choose Repair Computer and then System Restore to a previously working restore point?
JsmplyAuthor Commented:
Yep, didn't get anywhere.  
ded9Connect With a Mentor Commented:
Problem signature points to corrupt boot entry

Can be a corrupt mbr...mbr troubleshooting can be done after backing up the data in WINRE mode.

First  rename the bcd to bcd.old ...after that do not run the rebuild command the /scanos command from D prompt....if it is able to detect the arc patch then run the rebuild command from D prompt.

JsmplyAuthor Commented:
Thanks.  Turns out that after a full surface scan bad sectors were found on the hard drive.  The first time the user ran diagnostics they didn't do the surface scan.  Looks like it was the HDD afterall.  Will divide up points, thanks.
JsmplyAuthor Commented:
Turned out to be a bad HDD but any of those answers could have helped if it wasn't, so divided up the points.  Thx
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.