Win7 startup repair fails, but doesn't say what file is corrupt
After a power failure win7 boots into startup repair, which fails with the following problem signature: Problem signature: Problem Event Name: StartupRepairOffline Problem Signature 01: 6.1.7100.0 Problem Signature 02: 6.1.7100.0 Problem Signature 03: unknown Problem Signature 04: 10 Problem Signature 05: AutoFailover Problem Signature 06: 1 Problem Signature 07: CorruptFile OS Version: 6.1.7100.2.0.0.256.1 Locale ID: 1033 Startup repair on the installation DVD claims there is nothing wrong with the system. I have full access to the filesystem via alternate OS install, but win7 is giving me no idea what needs to be fixed. Searches have turned up no answers as to what is actually wrong. How do I fix this if it won't tell me what's wrong?
June 17th, 2009 4:54pm

After attempting to repair the boot blocks as recommended elsewhere here the system still fails to boot or repair the boot error, but the Problem signature has changed. Problem signature: Problem Event Name: StartupRepairOffline Problem Signature 01: 6.1.7100.0 Problem Signature 02: 6.1.7100.0 Problem Signature 03: unknown Problem Signature 04: 21201254 Problem Signature 05: AutoFailover Problem Signature 06: 4 Problem Signature 07: CorruptFile OS Version: 6.1.7100.2.0.0.256.1 Locale ID: 1033 I would really hate to have to wipe this partition clean and start over, and I was just beginning to like Win7... <g>
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2009 7:19pm

A power failure always has the potential to be catastrophic on a running system. This really isn't much different than any other Windows OS in the past ten years. If the OS starts up and says it can't, and wants to do a repair, and cannot self-repair, there's not much else you can do except "wipe and start over".Even if you could get it "repaired", or to boot up, there's always the question of "what else was damaged that's not yet been discovered".And.. please.. don't blame this issue on the operating system, when the real issue is not having adequate power-failure protection on the computer in the first place. :)Lawrence Garvin, M.S., MCITP:EA, MCDBA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009)
June 17th, 2009 7:44pm

Well, thanks for the useful pointers. I dug through the system until I found the log files for the diag code myself, figured out which file was corrupt, fixed the corrupted file, and the system is working just fine now, no thanks to the diagnostics that didn't tell me what was in the log file or your fine suggestion on how to proceed. If that stupid Win7 diagnostic code had simply displayed what was wrong I would have had this fixed twenty minutes after it happened rather than over twenty hours later. FYI: It was on a UPS and now that the system is running again I can see from that log file that it did indeed do a clean shutdown before the power went out. Why Win7 decided to corrupt a file during the shutdown, I have no idea. So, the real issue was a poorly written diagnostic that doesn't display any useful information, even though it knows what the problem is.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 5:19am

Hi! I am gld this worked out for you. I ma having the same issue. Do you recall what the corrupted file was and what you did to get it to boot? Any help would be greatly appreciated. JMU1998
July 28th, 2009 5:07pm

i am having exactly the same problems as you areProblem signature: Problem Event Name: StartupRepairOffline Problem Signature 01: 6.1.7100.0 Problem Signature 02: 6.1.7100.0 Problem Signature 03: unknown Problem Signature 04:21201061Problem Signature 05: AutoFailover Problem Signature 06:2Problem Signature 07: CorruptFile OS Version: 6.1.7100.2.0.0.256.1 Locale ID: 1033i was wondering how you fixed this, or how can this be fixed. do you know of any sites that can direct someone through the repair process? i have searched through so may sites looking for an answer, but nothing has helped. i have reinstalled windows seven and it didnt work, i have also ran repair checks and all that, the same stuff you did. also i never had a power faliure or anything like that, it was just after the first few times i logged in and shut down after using the computer that it began to stuff up. the only way i can use my computer is to start up with last known good configuration, and it works fine until after the next shut down. please, ANY help is appreciated
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 12:05pm

I have a Toshiba Satellite L505D-S5983 computer that as of Thursday will not boot. It has Windows 7, AMD Athlon II Dual Core M300, 3 GB DDR2 RAM, amd 320 GB HDD. Thursday evening upon returning home my laptop had died because it was unplugged. I attempted to turn it on and it gave me two options to run the Startup Repair or Start windows normally. Selecting either option gives me the startup repair. I have attempted to press F8 and boot from all of the options but to no avail it still sends me to the Startup Repair. Has my harddrive failed? Or do I need to order a copy of Windows 7 from Toshiba and reinstall? I am not sure but I believe I had a windows update before I left the house Thursday. Nothing else new has been installed recently nor do I attach anything to my pc via USB. I have nothing to attach is the reason. This laptop is not a year old yet. It was purchased around Christmas time last year so all of it is fairly new.
July 13th, 2010 12:09am

can any body pls help.. Problem signature: Problem Event Name: StartupRepairOffline Problem Signature 01: 6.1.7600.16385 Problem Signature 02: 6.1.7600.16385 Problem Signature 03: unknown Problem Signature 04: -1 Problem Signature 05: AutoFailover Problem Signature 06: 9 Problem Signature 07: CorruptRegistry OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2010 6:50am

BillSC Could you please explain the location of the log files that you talk of. You said that you dug through the system until you found the log files for the diag code yourself. And then figured out which file was corrupt, fixed the corrupted file, and the system was operational again. I have a similar problem and have looked at the C:\Windows\System32\LogFiles and have not found and info besides what appears to be some corrupt .txt and .log files Thanks for your time in advance, and hopefully you are still active on these boards. I do agree that Microsoft dropped the ball on incomplete information ... Rick
June 21st, 2011 8:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics