Link to home
Start Free TrialLog in
Avatar of Jsmply
Jsmply

asked on

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.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of IanTh
IanTh
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jsmply
Jsmply

ASKER

Stand alone PC in this case.
Avatar of Jsmply

ASKER

Here is the exact info:
startuprepairoffline
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.
SOLUTION
Avatar of Gerwin Jansen
Gerwin Jansen
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jsmply

ASKER

Yep, didn't get anywhere.  
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jsmply

ASKER

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.
Avatar of Jsmply

ASKER

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