New
#1
Reboot has become very slow
recently my reboot time has went from 66-79 seconds to this or higher.
Attachment 153514
Is there a tool I can run to tell me what is taking time on reboots?
Last edited by Britton30; 11 May 2011 at 20:22.
Reboot has become very slow
-
-
New #2
Hi Britton30. Good to see you again. One program I have used on occasion to analyze my boot times is from Sysinternals. Very comprehensive. You might give it a try.
Autoruns for Windows
Regards
JohnnyA
-
New #3
Hello again to you. Thanks for the linnk I ran the Autoruns program, but that isn't quite what I want. I want not only to see what is starting, but where the most resources are being used. My system takes about 100 seconds just to shut down. After that the BIOS stuff and post, Windows starting goes fairly fast. Should've put that in my first post.
EDIT I went to msconfig and disabled nVIDIA driver helper and Driver update. Then in BIOS I disabled all boot sequences except for the C\: drive. After all that I got a restart time of 79 seconds, on the right track with things. Thanks for your input!:)Last edited by Britton30; 08 May 2011 at 22:03.
-
New #4
Trace Windows 7 boot-shutdown-hibernate-standby-resume issues - MSFN Forums
Use the tutorial to interpret the output charts, or post up the .etl file on a file share like Windows Live then link it here for Cluberti to read for you.
IN the meantime, uncheck all startup items in msconfig>Startup except AV and gadgets. After restarting, go back to startup tab to see if anything has written itself back in and turn it off in its program preferences.
Next on the msconfig>Services tab "Hide all MS Services" to see what is running without permission. Uncheck these items, see if they turn themselves back on after restarts, turn them off in their Preferences or uninstall them.
Beyond that, all will be revealed in the trace.
-
New #5
For a very broad analysis, soluto can be used.
www.soluto.com
For more granular, event viewer can be used.
What
-
New #6
Attachment 153555
Here is what happened with the boot trace.
Read the EDIT in my 2nd post.Last edited by Britton30; 11 May 2011 at 20:22.
-
New #7
I PM'd Cluberti to look at the trace failure. This is the second identical failure today.
Double check to be sure it was installed correctly, with the .msi file run from the SDK install as given: Install the Windows Performance Tools Kit - MSFN Forum
-
-
New #9
Working on it Greg
Kado only a scanner, mouse, keyboard and printer. All these were present before the time went askew.
-
New #10
Greg thank for you trying to help. I did as suggested with the windows SDK...I think. I don't know how to install from the.msi which was generated. I ran the boot trace again, BAM, BSOD. Ran it again without the drivers tag and got the result as I posted before.
Startup repair couldn't fix the no-start situation, so did a restore point.
For now I will just run as is, with the virtualization disabled in BIOS the boot time has went to 79-88 seconds. At this time I am too frazzled to try anymore since I just found a fix for my resolution probeln. I need a rest from fixins.
Quote
Related Discussions