• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
MagicAndre1981

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

1,275 posts in this topic

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. =(

0

Share this post


Link to post
Share on other sites

I have no idea how to fix this. is this an OEM PC? if yes, phone their support.

0

Share this post


Link to post
Share on other sites

slow boot? Your Windows boots in 10s to the desktop and is fully booted in 11s:

- <timing bootDoneViaExplorer="10486" bootDoneViaPostBoot="21086" postBootDisturbance="600"

Your Samsung SSD 840 PRO does a very good job.

0

Share this post


Link to post
Share on other sites

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
0

Share this post


Link to post
Share on other sites

ok, Winlogoninit is slow. Open the generic graph and look under Microsoft-Windows-Winlogon for Task Name with a long Time during the Opcode Start and Stop.

Here is an example where RequestCredentials (entering the password) takes too long:

winlogonInit_delay_example.png

0

Share this post


Link to post
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
0

Share this post


Link to post
Share on other sites

zip and uplaod the ETL file, I'll take a look at it.

0

Share this post


Link to post
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
0

Share this post


Link to post
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.

0

Share this post


Link to post
Share on other sites

Hello, Andre, I just want to say I've read almost this whole thread and you sir, are an absolutely amazing individual.

I would be eternally grateful if you would take a look at my boot times and help me figure out what is taking so long. I followed this guide and ran the optimization and I did notice a significant improvement in boot times but I fear there may still be some issues.

Here is a link to my boot trace.

Thank you

Edited by Wario567
0

Share this post


Link to post
Share on other sites

in your case the PreSMSS is slow:

+ <interval name="PreSMSS" startTime="0" endTime="65805" duration="65805">

When you look at the bootStart etry in the XML you see that starting your WD drive is slow with 61s:

- <phase name="bootStart" startTime="40" endTime="62878" duration="62838">  <pnpObject name="IDE\DiskWDC_WD10EADS-65M2BX_____________________01.00A01\5+333ee88f+0+1.0.0" type="Device" activity="Start" startTime="543" endTime="61785" duration="61242" prePendTime="61242" description="Disk drive" friendlyName="WDC WD10EADS-65M2BX ATA Device" /> 

try a different SATA port/cable and see if this fixes it.

0

Share this post


Link to post
Share on other sites

If I may, instead of calling WDC_WD10EADS a "Caviar green" they would call them "slow molasses" the name would be appropriate, however there is a record for these "family" of drives to start becoming not responsive at boot time.

I would thus additionally check the drive with the Western Digital test tools as the symptom may be connected to an actual drive issue.

jaclaz

0

Share this post


Link to post
Share on other sites

I tried using a brand new sata cable on two different ports and I fear the boot times remain largely unchanged

I'm running a WD extended diagnostic test, will post when it finishes.

Thankyou both for the quick responses!

0

Share this post


Link to post
Share on other sites

Tested the drive with WD and the drive passed... after 6 hours of checking

A significant improvement in boot time after installing some more windows updates (including some in the optional tab which I did not notice) This appears to have fixed my issue, here is a link to a fresh trace after rerunning the optimizer, everything look okay to you guys?

https://docs.google.com/file/d/0B7_UvLVLVqKtTFdWajJndU5ZLVU/edit?usp=sharing

0

Share this post


Link to post
Share on other sites

Your issue is fixed. Boot is fast:

- <timing bootDoneViaExplorer="22986" bootDoneViaPostBoot="39586" osLoaderDuration="2361" postBootDisturbance="6600"

23s to the desktop and 30s to be fully booted. This is fine

0

Share this post


Link to post
Share on other sites

Hello

I just installed Win 8.1 x64 on my computer.
Sabertooth x79 + 3930k + Samsung SSD 500Go (and SSD Intel 160GB)

Both sata are connected on SATA GBPS (brown sata)

Link of my boot :

http://pastebin.com/2kXHSVeU

THe PreSMSS time is very long.
What can i do ? Unplug Hard Disk to check the difference ? and ?
Every HDD are on Intel Chipset, nothing are connected on Marvell Chipset.

My system are installed in UEFI.

But if i format HDD in GPT, does it change anything ?

Edited by ordimans
0

Share this post


Link to post
Share on other sites

disable the Marvel completely and try to connect the Samsung 840 Evo SSD to different ports. You also use a lot of older Samsung HDDs (HD204UI, HD154UI). Try to remove them and look if this makes a difference.Those green drives are really slow and may cause it.

0

Share this post


Link to post
Share on other sites

Hello there, awesome guide.

Sadly i have a problem with making the html file of the Boot log.

When i enter the generate html command into cmd i get the following error message. (note: please ignore the first error in the pic as i mistyped the command)cmd%20error.JPG

So how do i go about increasing the buffer size and the log size? I had a poke around in "xperf -help start" but everything i tried just spat out failure messages.

Many, many thanks in advance,

Bentree.

0

Share this post


Link to post
Share on other sites

disable the Marvel completely and try to connect the Samsung 840 Evo SSD to different ports. You also use a lot of older Samsung HDDs (HD204UI, HD154UI). Try to remove them and look if this makes a difference.Those green drives are really slow and may cause it.

I did.

I unplug all HDDs, and disable Marvell, ASmed chipset, everything i could.

Now i have this :

http://pastebin.com/Zs4AJdBi

What do you think ?

Edited by ordimans
0

Share this post


Link to post
Share on other sites

So how do i go about increasing the buffer size and the log size? I had a poke around in "xperf -help start" but everything i tried just spat out failure messages.

I never figured this out. Open the ETL file directly in the viewer. It has a graph with the boot phases. Here you can see how long which phase takes.

Now i have this :

http://pastebin.com/Zs4AJdBi

What do you think ?

boot is very fast now (9s):

- <timing bootDoneViaExplorer="9359" bootDoneViaPostBoot="19259" 
0

Share this post


Link to post
Share on other sites

So how do i go about increasing the buffer size and the log size? I had a poke around in "xperf -help start" but everything i tried just spat out failure messages.

I never figured this out. Open the ETL file directly in the viewer. It has a graph with the boot phases. Here you can see how long which phase takes.

OK, thanks will give that a shot. is it usual for the etl file to be half a gig or so in size?

0

Share this post


Link to post
Share on other sites

yes, if boot is very slow and a lot of data are written into the file.

0

Share this post


Link to post
Share on other sites

MagicAndre: ok i opened the etl file, i was warned that 4807 events were lost. any way it opened up and i was greeted with about 40 different colored lines of various lengths. long story short i couldn't make head nor tale of the info. so i would very much appreciate it if you could look at the file for me. the link for the etl file is here https://dl.dropboxusercontent.com/u/28370259/boot_BASE%2BCSWITCH%2BPOWER_1.etl

I apologize for the size. i didn't change size when i tried to zip it.

Many Thanks, Ben.

0

Share this post


Link to post
Share on other sites

the HDD is busy all the time. You should stop all tools that you don't need to reduce the disk activity pressure.

0

Share this post


Link to post
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.