• 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

I thought about that, but didn't do it.  I'll pm the new link.

0

Share this post


Link to post
Share on other sites

yes, AVG seams to be the cause. The driver avgmfx64.sys casues a long delay:

 

avg_driver.png

 

Contact their support for an update.

0

Share this post


Link to post
Share on other sites

With the AVG uninstalled the pre login delay drops to 40 seconds.  Anything you can see causing that?

0

Share this post


Link to post
Share on other sites

capture a new trace, this time with tis command:

 

xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER+LATENCY+DISK_IO_INIT+DISPATCHER+FILE_IO+FILENAME -stackwalk profile+CSwitch+ReadyThread+DiskReadInit+DiskWriteInit -resultPath C:\TEMP

 

Here I see more details about hangs/waits.

0

Share this post


Link to post
Share on other sites

First of all i'd like to give my compliments to MagicAndre, you've helped a lot of people here :D

 

Anyway: i've been experiencing some weird issue during resume from hibernation, my hiberread times are over 700 seconds. I made a trace summary (https://www.dropbox.com/s/6sfhjv0g2qe3hew/summary_hibernate.xml?dl=0) but i can't find any details from what happens while reading the hiberfile.

Edit: boot is pretty quick by the way, nothing wrong with that.

 

By the way: windows is an almost fresh install, i've had this issue since i installed it. The drive is a Samsung 840 Evo SSD, in an (a bit old) Dell Latitude E6510 laptop.

 

When i look at my HD led it blinks slowly during a minute or 6, and after that it suddenly starts lighting up (in the same fashion as it does when writing the hiberfile), and after about 20 seconds i've got the login screen in front of me.

 

So right now i'm trying to figure out what happens during the hiberread process.

 

Here's the trace itself by the way: https://www.dropbox.com/s/0e24p8k3s6w5dio/hibernate_BASE%2BCSWITCH%2BDRIVERS%2BPOWER_1.7z?dl=0

Edited by mogas
0

Share this post


Link to post
Share on other sites

reading the hiberfile.sys takes a long time (752 seconds):

hiberread="752062000" 

Please apply the Performance restauration Firmware to your Samsung SSD 840 EVO 500G:

 

https://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/support/downloads.html

 

Does this improve it?

The trace was actually made after i did that. I also installed some of the hotfixes (not the one regarding to the large disks, both disks in the system are 500GB).

I also did a defrag with consolidating free space, after i removed the hiberfile. Then i activated hibernate again, to no avail...

0

Share this post


Link to post
Share on other sites

update the BIOS and install the latest AHCI driver.

0

Share this post


Link to post
Share on other sites

update the BIOS and install the latest AHCI driver. 

Done and done, sadly no difference :(.

 

The fun thing is: i had a fresh install due to the addition of the SSD to the system. Before that hibernate has always worked.

0

Share this post


Link to post
Share on other sites

I don't have this Samsung SSD (only Crucial MX100 and the older Samsung 830 and with both I don't have such a delay). Do you have a a 2nd PC/Laptop where you can insert the SSD and test if it also happens there?

0

Share this post


Link to post
Share on other sites

I'm hoping I can get some answers and fix my SUPER slow boot time (15 mins!). I've done a few things found in forums including this one, but honestly a lot of it is over my head and nothing has helped so far. I'm not computer illiterate, but I'm also no programmer, so please bare with me. :}

 

Windows 7 Home Premium 64-bit

2.20GHz VISION Technology from AMD with AMD Athlon II Dual-Core Processor

 

I've done a boot trace and attached the summary file....can someone read it for me and tell me (in layman's terms) what to do?? TIA!

 

OH and I also tried the tips on "How to speed up boot process under Windows Vista or Windows 7".

summary_boot.xml

Edited by hllewis
0

Share this post


Link to post
Share on other sites

I need the ETL file to see more details.

 

xbootmgr -trace boot -traceFlags BASE+LATENCY+DISK_IO_INIT+DISPATCHER+FILE_IO+FILENAME+POWER -stackwalk profile+CSwitch+ReadyThread+DiskReadInit+DiskWriteInit  -resultPath C:\TEMP

0

Share this post


Link to post
Share on other sites

Ok done, but the file is too big for upload?

Also some updates were done during the reboot so let me know if you need it redone.

Thanks so much for your help.

 

0

Share this post


Link to post
Share on other sites

compress the ETL file as zip/RAR, upload the zip to a cloud service (OneDrive, dropbox, or a 1 Click Hoster like Zippyshare.com) and post a link here.

0

Share this post


Link to post
Share on other sites

ok, in WinlogonInit Phase the function UpdatePerUserSystemParameters takes over 300s to finish.

 

But the underlaying issue is your 320GB 5400RPM WD3200BEVT-60A23T0 HDD. It is busy all the time. Replace it with a SSD.

0

Share this post


Link to post
Share on other sites

THANK YOU! I'll replace and see how it goes. Can the function UpdatePerUserSystemParameters be changed or deleted?

0

Share this post


Link to post
Share on other sites

no, this is a normal Windows function. Your slow 5400rpm drive slows down the system too much.

1

Share this post


Link to post
Share on other sites
@MagicAndre1981:

 

Firstly, thanks for your help everyone.

 

I have dual windows: Server2003 (NT5.2) and Win7. 

NT5's boot time is quick (it's very lightweight. Lovely!).

NT6's boot time more spend long. (Before, I tried Win8.x. Both it's same.)

 

I did trace to Win7 with xbootmgr. I can't solve why slowing of NT6.

Could you analyze my ETL file?

Edited by ilkertezcan
0

Share this post


Link to post
Share on other sites

your HDD is busy during boot. This is the bootleneck. It's time for a SSD.

0

Share this post


Link to post
Share on other sites

@MagicAndre1981:
Thank you for your interest and analyze.
I got it. I already would be buy a SSD. :) I know, boot times definitely will be change.

Thanks again.
Best regards.
 

 

 

0

Share this post


Link to post
Share on other sites

Good day Andre, I have posted here as requested.

0

Share this post


Link to post
Share on other sites

so, first the enumeration of IDE devices takes over 5s:

- <phase name="bootStart" startTime="17" endTime="5113" duration="5096">  <pnpObject name="PCIIDE\IDEChannel\4+bff9540+0+0" type="Device" activity="Enum" startTime="223" endTime="2730" duration="2507" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" />   <pnpObject name="PCIIDE\IDEChannel\4+bff9540+0+1" type="Device" activity="Enum" startTime="223" endTime="2730" duration="2507" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> 

But the longest delay is the WinLogonInit phase:

<interval name="WinlogonInit" startTime="8880" endTime="37095" duration="28215">

Here I can see that restoring the network connections is slow:

 

networkconnections.png

 

 

This is the main cause of the boot delay. Only connect the network drives on demand with

net use X: \\server\share /persistent:no
0

Share this post


Link to post
Share on other sites

Hi Andre,

 

Thank you for your time and expertise. Yes, I have mapped several network drives to the home server, connected via Gigabit and set to "reconnect". I use these drives regularly for work and entertainment so it is not convenient to re-map them each time they are required. Is there any other way to make this more efficient, some form of Delayed Start perhaps? For most of the time I don't need the drives immediately after logging on.

0

Share this post


Link to post
Share on other sites

Hmmm an idea is you can use a scheduled task to map the drive using the /persistant:no option. When creating a task with an "at startup" or "at logon" trigger you have an option to delay the task from executing

See here for more on triggers:

https://technet.microsoft.com/en-us/library/cc748841.aspx?f=255&MSPPError=-2147217396

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.