Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Windows 7 Infinite Startup Repair Loop

  • Please log in to reply




  • Member
  • PipPipPip
  • 169 posts
My brother's computer recently stopped booting past the BIOS logo, it almost immediately goes into startup recovery. I've tried booting into safe mode, but it immediately redirects to startup repair again. If I use a Windows 7 repair disk, the repair program finds no errors, but if I use the program on the computer's hard drive, it gives the following error:

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: 21200658
Problem Signature 05: AutoFailOver
Problem Signature 06: 11
Problem Signature 07: CorruptFile

OS Version 6.1.7600.

Local ID: 1033

I'm assuming that an important Windows file was corrupted recently on his computer. I'm also assuming that it has something to do with (what he swears is) the only change he has made withing the last few days, which was a new driver he installed for a used DeathAdder mouse he received from his "hacker" friend (who loves to prank people/steal their Steam accounts, so I question anything he does when he visits my brother.)

I've also run the CMD command Check Disk, but it found no errors, and neither did the memory diagnoistic.

P.S. I noticed that choosing the OS while using the recovery CD gave the drive as the D: drive, even though the normal drive letter is C:, and the check disk command ran normal while in the D:\ directory, but I could still acsess a C drive in the cmd, and on that drive, check disk ran suspiciously fast.

*edit* P.P.S. I forgot to mention that I removed the drive from the computer and scanned both partitions on the drive 4 times each, twice with MalwareByte's Antimalware, and twice with Avast! Antivirus, removing a total of 10 infections, but there was no effect.

Edited by WhydoIask?, 11 May 2011 - 06:01 PM.

  • 0


Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP