Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows fails to start; startuo3 repair cannot discover the problem

  • Please log in to reply
1 reply to this topic

#1 J.Love


  • Members
  • 1 posts
  • Local time:01:34 AM

Posted 08 October 2012 - 04:36 PM

This laptop keyboard made me mess up the topic name.
"Windows fails to start; Startup Repair cannot repair this computer automatically"
In trying to boot up my computer, be it normally, in safe mode, or in minimum graphics mode, I'm taken to automatic system startup repair. I receive the following 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: 21200655
Problem Signature 05: AutoFailover
Problem Signature 06: 7
Problem Signature 07: CorruptFile
OS Version: 6.1.7600.
Locale ID: 1033

I'm unsure as to what caused the problem, as this began occurring on system startup after a few days' period of disuse. Any help or advice is appreciated.

Edited by hamluis, 08 October 2012 - 05:45 PM.
Moved from Malware Removal Logs to Internal Hardware - Hamluis.

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,567 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:34 AM

Posted 08 October 2012 - 05:51 PM

FWIW: http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/b4c07920-4800-4d6c-9b3e-c47a0b79c907

First thing that I would do...run the appropriate diagnostic on the hard drive.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users