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.

Photo

Microsoft windows 7 won't boot past startup repair


  • Please log in to reply
18 replies to this topic

#1 ratroder

ratroder

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 11:53 AM

So I have encountered a computer problem, go figure. The issue started yesterday and still persists today.

 

Background:

                I am running windows 7 on a boot solid state drive for my desktop. I recently (yesterday) installed two drivers. One for a wacom intuos 3 tablet and one fore a wacom bamboo touch tablet (all drivers were gotten from the offical wacom website). Further back I installed adobe Photoshop cs5 and adobe premiere pro cc. I do not have a restore point and my network back up drive is not functioning at the moment (shame on me, I know).  The system was fine before and after the adobe installs and there seemed to be no issues. The system was running great. I had restarted a few times in that period and not problems. The issue started after I installed the wacom table drivers, after I went to restart.

 

The Problem:

 

        Upon the restart windows 7 will not boot. After the motherboard screen flashes a black screen appears and says windows is loading files.  Then a green block style bar appears and shows a loading pattern. After that the system goes into startup repair and tries to search for the problem as well as attempting repairs. Once that is complete I get a message that says “Start up repair cannot repair this computer automatically". I have the option to send a report or not. The problem details show:

 

            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: 9

     Problem Signature 05: AutoFailover

     Problem Signature 06: 1

     Problem Signature 07: NoOsInstalled

     Os Version:                    6.1.7600.2.0.0.256.1

     Local ID:                          1033

 

     Read our privacy statement online

                Link to Microsoft

     If online privacy statement is not available, please read our privacy statement offline:

                Another link

            After closing that window I can then view the stratup repair which still says: windows cannot repair this computer automatically. Form here I can: view diagnostic and repair details, view advanced options for system recovery and support, finish, and cancel.

 

            If I click on view advanced options for system recovery and support I get the options to choose a recovery tool. Under that prompt it displays: Operating systems; windows 7 on (E:) Local Disk. Then there are the following options: Startup repair, System Restore, System image recovery, Windows memory diagnostic, Command Prompt, and the options to restart or shutdown.

 

                The Diagnosis and repair details that startup repair gives:

 

                        Startup Repair diagnosis and repair log

                        ------------------------------

                        Number of repair attempts: 1

                               

                        Session details

------------------------------

System Disk = \Device\Harddisk1

Windows directory = E:\Windows

AutoChk Run = 0

Number of root causes = 1

 

Test Performed:

----------------------------

Name: System disk test

Result: Completed successfully. Error code = 0x0

Time taken = 32 ms

 

Test Performed:

---------------------------

Name: Disk metadata test

Result: Completed successfully. Error code = 0x0

Time taken = 15 ms

 

Test Performed:

----------------------------

Name: Volume content check

Result: Completed successfully. Error code = 0x0

Time taken = 8112 ms

 

Root cause found:

--------------------------

No OS files found on disk.

 

Repair action: Partition table repair

Result: Failed. Error code = 0x490

Time taken = 4743 ms

 

----------------------------

----------------------------

 

 

                Now yesterday after the problem started I hooked the drive to my laptop via esata and a bench supply and was able to read the drive from my laptop. I got the IMPORTANT data off that I didn’t want to lose. The file structure looked like it was all there (to me at least……not too versed in software, better with hardware). I did find the wacom drivers and took them off to see if that fixed it to no avail. Then I ran avast! on the drive as a removable drive and it found 6 infected files. I do not have the names of them. It was able to remove several, but not all of the files that had a problem. I can boot to the laptop and rerun avast! on the drive to get the names of the files if that would help.

 

                So at this point I have a main OS boot drive that will not boot past startup repair. I can not access any form of safe mode by the means of pressing f8. I can access the drive from my laptop as drive (E:). If i hook the drive back up to the desktop, the boot problem also happens.

 

A little about the system:

          Processor: AMD FX 8350

          Mother Board: msi 970a-g46

          Boot drive: OCZ onyx series SATA II solid state drive 64 GB

          Programs drive: Samgsung HD 130sj 1 Tb

          Windows 7 Professional (only OS)

 

Any and all help is really appreciated. If there is anything else that I need to get just let me know and I will get it as soon as I can. Thank you!

 


 

 



BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:59 AM

Posted 19 January 2014 - 12:07 PM

Do you have a Windows 7 installation CD?

#3 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 12:17 PM

Yes I do. 64 and 32 Bit.



#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:59 AM

Posted 19 January 2014 - 12:20 PM

You will need to boot up to it, and enter the repair console and determine the letter of the windows drive, and then perform the following:

chkdsk /f <driverletter>

Then let it do its job.

#5 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 12:58 PM

Just to make sure I am entering this right:

 

chkdsk /f <D>

 

I get this message in return: The driver, the path, or the file name is not valid. The disk is (D:) as windows detected it to be.

 

The command prompt module displays this at the beginning of each line X:\Sources>

 

So should the command be: X:\Sources>chkdsk (space) /f (space) <D>



#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:59 AM

Posted 19 January 2014 - 01:15 PM

You need the : after drive letter

#7 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 01:48 PM

Ok, sorry about that. But as typed: chkdsk /f <D:> I recieve the same responce. The full command appears: X:\Sources>chkdsk /f <D:>

 

I included some pictures to show you what I am seeing. Sorry fo the bad quality on the last one.

 

photo1_zpsdb304e1b.jpgphoto2_zpsf347f30a.jpgphoto3_zps58e73e86.jpg



#8 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 02:01 PM

I am using parentheses () around the drive letter (just to be clear). So the command would look like this chkdsk (space) /f (space) (D:)


Edited by ratroder, 19 January 2014 - 02:10 PM.


#9 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 02:25 PM

So while I was searching for the drive leter after hooking the drive to my laptop (I was using the desktop for a little) I was prmpted with the folloing message after the system recovery options module seached for instulations of windows.

 

These are the details from the window that poped up:

 

System Recovery Options (window title)

 

Repair Details:

The following startup option will be repaired:

Name: Windows Boot Manager

Identifer: {9DEA862C-5CDD-4E70-ACC1-F32B344D4795}

 

The following start up options will be added:

Name: Windows 7 Professional (recovered)

Path: Windows

Windows Device: Partition =E: (650955 MB)

 

Name: WIndows Recovery Enviroment (Recovered)

Path: Revovery \b9872b24-facd-11e2-8e3c-d7087fb636e0\Winre.wim

Windows Device: Patition =E: (60955 MB)

 

A copy of the current boot configuration data will be saved as F:\Boot\BCD.Backup.0001

 

In the main window where the details link that gave me the above information, I have the option to: Repair and restart or No.

 

When the drive is hooked to my laptop it is reconized as drive E:


Edited by ratroder, 19 January 2014 - 02:26 PM.


#10 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 04:24 PM

So I figured out what i was doing wrong with the command. It was the parentheses. The final command was chkdsk /f D:.

 

That has now finshed running. Should I post that, and if so how?



#11 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 19 January 2014 - 08:05 PM

Here is a screenshot of the results from the chkdsk /f D:

 

photo_zpsbf7b762d.jpg



#12 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:59 AM

Posted 19 January 2014 - 09:22 PM

Does the machine boot up now?

#13 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 20 January 2014 - 11:40 AM

I went and hooked the drive ack into the desktop and reran the chkdsk /f D: from the windows install cd. This time the process found and fixed a whole bunch of files. Once that was done the system did boot and now is up and running.



#14 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:59 AM

Posted 20 January 2014 - 11:42 AM

Good to hear, if you have any more questions please post back to this topic.

#15 ratroder

ratroder
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:06:59 AM

Posted 20 January 2014 - 11:50 AM

I thank you very much for the help.

Is there anything that I can do from this point or that you would recommend I do to make sure that the system is running correctly?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users