Startup Repair Offline help

DruggedPanda

Honorable
Mar 17, 2012
26
0
10,530
Hey everyone,

Over the past few weeks I've been having some problems with my Computer. about two weeks ago, my computers F drive couldn't be recognized. As I use this as a slave drive, I thought I would just restart it and see if that would fix the problem and show the drive again. Unfortunately, every time my computer would start back up after the restart, everything would work (mouse, keyboard, the beep from the motherboard) except for the monitors; I would never get an image on the screen. I decided to just leave the computer off over night, and the next morning it started to work. It had actually worked, including the F drive, all the way up to today. I'm not sure if this contributed to the problem, but I thought I would include the fact. about two days ago, I decided to optimize my drive to try and gain space on it. I went into my C drive properties and deleted the recommended items windows said to delete. I did so and gained enough space to be happy. With that said, today I woke up to my computer doing the same thing as before; everything would work (at least from what I understand about computers), but nothing would show up on the screen. Since I had my computer connected to my graphics card, I thought I would just start up the computer connected to my motherboard to see if the GTX 570 was the problem. Initially it worked, but agian my F drive wouldn't show up. I restarted the computer. This time I was able to see what it was trying to do since I was connected to the motherboard, not the graphics card. Unfortunately, the computer would go into systems recovery and then start startup repair.

This is the problem signature I got:

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

At this point I have no clue what this means. I tried to just exit startup repair, but every time I press, "Finished" the computer crashes and enters startup repair again, and again, and again... I have a feeling that nothing but my drives are screwed up, which is good and bad news. Fortunately, all my school work is on my Microsoft OneDrive, But unfortunately, my photos and videos are on my F drive....

If anyone could help me that would be awesome!

Thanks everyone,

Alex

P.S.

My computer components are:

C Drive: Kingston 126gb SSD
F Drive: Segate 1TB HDD
Intel Core i5 2500k
EVGA GTX 570
Gigabyte Z58AP-D3

The computer is about 3-4 years old.
 
Well, if this were happening to me, the first thing I would do (or attempt to do) is a clean install of the operating system, hoping its nothing more than a software related problem. Fortunately, because your photos are on the 'F' drive, if you format and reinstall the OS to your 'C' drive, the photos will remain intact on the 'F' drive.

Once Windows destroys/corrupts itself, it is often very difficult to fully recover the OS to a usable state, even if you are able to get into Windows again, you will most likely exhibit strange issues, like drivers not working, random crashes, and general poor performance. A clean install is the best way to fix software issues.
 
Hey Brandon, Thanks for the comment. I've been thinking about doing the same thing, but wanted to see if anyone had any other imputes! thanks for the help though; it's increasingly apparent that it might be my only option haha. I also forgot to mention that my keyboard actually only works once I am in Startup Repair. For some reason it wont work before hand so I can't start in safe mode or open my BIOS.
 


Thanks Scout, I took out my F drive and it started up perfectly! Now I need to figure out how to save my photos... Oh, I also left my Graphics card in and its working fine.
 
Concerning the keyboard issue, this is often caused by not having legacy USB support enabled in the BIOS. Which is cured once the USB drivers are loaded by windows. If you have access to a PS/2 Keyboard, you should be able to enter the BIOS/Safemode.
 


Thanks, I'll give that a try. Do you have any idea what could be wrong with the F drive that's causing the problem? It might be useful to know that when I went into Diagnosis and repair detail I get the message:

Root Cause Found:
------------------------------------------
A Recent Driver installation or Upgrade may be preventing the system from starting
------------------------------------------
------------------------------------------
System Disk = \device\harddisk0
Windows Directory = E:\Windows
AutoChk Run = 0
Number of root causes = 1

Thank man,

Alex
 


Thanks man for the tip. The keyboard started working right as I turned on the computer after I pulled out the F drive.
 
Because you were able to boot fine after removing your F drive, this could be caused by a few things, software or hardware.

If its software related (driver issue/corruption) you could attempt plugging the drive into another port on the motherboard which would hopefully side step the faulty driver.

If its hardware related, this is a sign of potential component damage/failure, sadly storage drives do not last forever.

I would still attempt to plug the drive into another slot on the motherboard.

As scout_03 recommended, an external USB enclosure is often successful in accessing a drive that is beginning to be problematic (side steps drivers, motherboard SATA controllers, and potential PSU issues).
 
Sweet. Thanks guys for all the help. I think I'm just going to extract as much information I can get from the drive and get a new one. This one has been super problematic over the years, and I think it's time for an upgrade. Thank again.
 
If your keyboard issue was resolved by removing the drive, this points to a BIOS/hardware(HDD/Motherboard) issue most likely. If the issue persists if you switch to a different motherboard sata port, I would try a different data and power cable, if the problem persists, I would absolutely try the USB external enclosure route in an attempt to backup the stuff you cant live without on the drive, because at that point, I would assume the drive was at fault, and is failing.