Jump to content

Trace Windows 7 boot/shutdown/hibernate/standby/resume issues


MagicAndre1981

Recommended Posts

  • 3 weeks later...

I upgraded my hdd to a hybrid SSD and rebuilt my system and ever since resuming from hibernation has been horrible taking up to 2 min. However, booting takes ~20 seconds consistently.

I ran the performance tool and not really knowing what I'm looking for I can't see anything at first scan that seems obviously wrong.

Here is a link of my etl file for review:

https://dl.dropboxusercontent.com/u/5698994/hibernate_BASE%2BCSWITCH%2BDRIVERS%2BPOWER_1.zip

Any help would be greatly appreciated!

Thanks,

Jesse

Link to comment
Share on other sites

This was a fresh install of windows. However, I tried your suggestion, de-fragmented my hd, rebooted and then tested going into hibernation, things are still slow. I next totally disabled hibernation and rebooted, re-enabled hibernation and tested, the restart from hibernation was still slow.

Thanks for any help

Link to comment
Share on other sites

Drivers do not exist from my HDD. It is a SATA Momentus XT ST750LX003 750 Gb.

I do however have installed Intel Rapid storage drivers, and have updated this to the latest version.

I have Write-caching enabled on the drive.

But I'm still not seeing any improvement. =(

Link to comment
Share on other sites

  • 4 weeks later...

I'll start by saying thanks so much for this tutorial. Really easy to follow.

I'm a bit stuck now though. My issue is in the "Please wait" part of the bootup (logon screen background is up but you can't logon yet), it takes about 50 seconds on a brand new laptop with SSD. I may be crazy but I was sure it was booting up lightning fast yesterday before I installed some applications. But system restoring to before those applications didn't do anything.

Anyways, it seems that all the time is taken up in the Winlogon Init, but pulling up the services graphs shows long periods of nothing happening:

http://i.imgur.com/npG2uRD.png

What should my next step be to track this down? If it helps, I am on a domain managed computer (work laptop, has a bunch of locked settings set by the domain) but not connected to the domain (and won't be 99% of the time).

Edit: some other information I've found from the windows event viewer is that "BootMachineProfileProcessingTime" is taking 53113ms. Currently investigating this.

Edit2: It seems that the profile processing time includes all device drivers and such, so that tells me much less than this boot tracing.

Edited by ScottyDoesKnow
Link to comment
Share on other sites

Thanks for the quick reply. I've edited this post about 20 times and here's where we're at. This is the original screenshot:

http://i.imgur.com/1KT7mbH.png

It looks like there's just magical missing time from 6 - 60 seconds.

I edited because I thought I found something else, but in the end I think I just did a sort at some point and screwed it up:

http://i.imgur.com/Xvz0Ysf.png

Update: I've been looking into some warnings that GPClient is taking a long time. Going from there I found that GroupPolicy startup scripts are taking 59 seconds. Running gpedit.msc I can't find any startup scripts. So still stumped.

Update again: gpscript.exe is running for around 36 seconds of it. As far as I can tell there are no scripts on the local computer or on the server, though I can only connect to the server through VPN so it may be a case of it trying to contact the server for scripts and failing.

Edited by ScottyDoesKnow
Link to comment
Share on other sites

Here you go: https://db.tt/cBsfOIUU

Thanks for taking the time. Unfortunately I think I may have gone as far as I can with the boot stuff. It seems to be centered around group policies from the server (which I am almost never connected to). I've traced it as far as gpclient and gpscript, and searching those reveals a host of different problems that are all slightly different from mine. My current suspicion is that the delay is just it trying to connect to the server, but I don't know how (or if it's possible) to reduce the timeout on that.

Edit: I'm no longer so sure I know what the problem is. It seems that windows 7 has a feature (http://support.microsoft.com/kb/305293) to prevent this from happening. It grabs the group policy stuff asynchronously and swaps over when it finally connects. I also tried forcing the policy to disabled to make sure, but no luck. So I'm back to being clueless.

Edited by ScottyDoesKnow
Link to comment
Share on other sites

Yes, the trace shows the GP client/gpscript as cause:

- <groupPolicy>  <process name="gpscript.exe" pid="4768" startTime="25673" endTime="60349" duration="34676" localLowPriCPUTime="0" localRegPriCPUTime="55" localLowPriDiskBytes="0" localRegPriDiskBytes="838144" />   <process name="gpscript.exe" pid="4292" startTime="66468" endTime="66525" duration="57" localLowPriCPUTime="0" localRegPriCPUTime="23" localLowPriDiskBytes="0" localRegPriDiskBytes="1054720" />   </groupPolicy>

I have no experience with GP so I can't help.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...