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

Running Startup Repair


  • Please log in to reply
2 replies to this topic

#1 SableMR

SableMR

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:37 PM

Posted 21 August 2008 - 08:15 AM

Hi, I have an HP with Vista home (13 months old). My computer had been locking up from time to time and I would have to cut it off and then restart. Tuesday night when I did this the computer would not come on. I got a screen stating that the computer had not shut down correctly and suggested I run 'Startup Repair". So now this program has been running (very slowly) for over 24 hours. :huh: It says it might take several minutes.
Has anyone else had problems like this? How did you solve this problem. Both the 'startup repair' and the origional problem of lockingup?
I am sitting here with the laptop, watching the bar slowly go from one end to the other and start over. Under the bar is a note that says Attempting repairs....
PLEASE HELP!! :huh: :huh:

BC AdBot (Login to Remove)

 


m

#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:37 PM

Posted 21 August 2008 - 11:17 AM

Vista runs many different tests in Startup Repair - so it's difficult to tell where it's hung up at.
You can locate the logfile in C:\Windows\System32\LogFiles\Srt\SrtTrail.txt

Here's a log I ran when my system wouldn't boot not long ago (note that the 0x0 error code means success):

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: 8/9/2008 4:34:15 PM (GMT)
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = E:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 266 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 110 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 532 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 2406 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 625 ms

Test Performed:
---------------------------
Name: Access control test
Result: Completed successfully. Error code = 0x0
Time taken = 8797 ms

Test Performed:
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Fallback diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x2
Time taken = 456172 ms


I'd suspect that it's doing chkdsk /r - and that it's having difficulties with it. Chkdsk /r can take a long time on a drive that's operating correctly - but not 24 hours. I'd suggest terminating the test and running a bootable hard drive diagnostic. These are usually available for free from the manufacturer of your hard drive.

I prefer the test from the manufacturer of the hard drive as it's been designed for that hard drive (and manufacturer's often insert extra diagnostic routines that only apply to their drives). In the event that you cannot locate the diagnostics for your drive, I'd suggest the Hitachi Drive Fitness Test (free) and, on the rare occasions when it won't work, the SeaGate SeaTools diagnostics.

Also, just FYI, I had a corrupted SD card connected to my system via a USB adapter (and USB booting was enabled). The corruption would lock the system up during the boot process. After getting frustrated over this, I removed all USB devices and the system was able to boot. I ran SFC.EXE /SCANNOW immediately afterwards and have been running OK for a week or two.

Edited by usasma, 21 August 2008 - 11:21 AM.
added last paragraph

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 SableMR

SableMR
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:37 PM

Posted 21 August 2008 - 12:55 PM

Thanks for your suggestions. I'll see what I can figure out.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users