• 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

PreSMSS is explained in the first post. here all drivers are loaded and the devices are started. Try to use the Marvell chip, too. Play a bit with combinations of connecting devices to Intel and Marvell. Does this make a difference?

Yes, your USB drive also slows down boot. So try to connect it to a different uSB port or attach it after boot.

0

Share this post


Link to post
Share on other sites

normal HDD likes your WD are not slow-downed by SATA2. No normal HDD is so fast. Only SSDs reach the limits.

You can try to update the BIOS and load the default setting and try to install never AHCI drivers. If nothing helps, try a PCIe card which provides additional SATA ports.

I deleted the active partition of WD 3 TB drive and created two partitions of 2 and 1 TB. The system now boots in less than 23 s. I guessing this has something to do with how Win 7 64 bit handles drives greater than the 2 TB limit for non 64 bit OS. Not real happy with this solution but I haven't found another one yet.

0

Share this post


Link to post
Share on other sites

ok, thanks for the feedback. I don't have a 3TB HDD so I can't really test this.

0

Share this post


Link to post
Share on other sites

Hi all,

Currently, I found my WIN7 has a issue that "UMBus Enumerator" appears in Device Manager slowly sometimes.

Please kindly refer to my attach files. umbus1.png is shown the beginning of bootup and wait 2~3 minutes the "UMBus Enumerator" will show up as shown in umbus2.png.

I tried to use below command to trace what is going on here, but the recording time is too short for this case.

xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP

Does any way to increase the recording time? Or any one met this issue before?

Thanks.

post-359558-0-67852400-1344493969_thumb.

post-359558-0-99619600-1344493979_thumb.

0

Share this post


Link to post
Share on other sites

You can add the -postBootDelay XYZ Parameter to the command. This sets the post-boot delay (in seconds) before stopping the trace. So add 180-240s to capture 3-4 minutes after Windows booted completely.

0

Share this post


Link to post
Share on other sites

Hi MagicAndre, thanks for this guide.

I'm having a problem where W7 is taking ages to boot to the GUI. I recently installed the ATI SB drivers and then my PC wouldn't boot anymore (BSOD) so I had to boot to Last Known Configuration which worked and has now become the default, with ControlSet001 marked as failed.

I obviously haven't tried installing the ATI SB Drivers again as I don't want to mess it up again, so it's using the MS AHCI SATA driver at the moment. I've set the boot options, NoGUI and OS Boot Information and the last thing I see loading is atipcie.sys and then it doesn't seem to do anything for ages before the Welcome screen appears.

Looking at the trace, PreSMSS takes 5.9s, SMSSInit 11s, WinlogonInit 5.7s, ExplorerInit 8.3s, PostExplorerPeriod 40s, TraceTail 84s. As the delay I'm concerned about is in the pre-GUI stages, I'm guessing the problems in the SMSSInit stage but it sure feels like longer than 11s. I'll go and time it to check.

I also checked the start parameters of the AHCI/ATI drivers in the two ControlSets and this is what I found:

ControlSet001 (Failed/BSOD):

amdsata - 0

amdide - 3

atipcie - 0

msahci - 0

ControlSet002 (Current/Working Set):

amdsata - 3

amdide - 3

atipcie - 0

msahci - 0

Can I upload the trace for you to look at? Will the summary_boot.xml be sufficient or do you need the 377MB .etl?

EDIT: As I suspected, the delay is much longer than the trace suggests. From the boot.ini countdown finishing to the last driver in the list (atipcie.sys) being shown was 5s, then the GUI didn't appear for another 1min22s and it was about another 35s until everything finished loading.

Edited by doveman
0

Share this post


Link to post
Share on other sites

compress the large ETL as 7z, this dramatically reduces the size.

0

Share this post


Link to post
Share on other sites

the only delay you may see is the run of the program which his added in the key BootExecuteList and the Initialization of the registry:

post-70718-0-81544700-1345152219_thumb.p

There is also a small delay (2.5s) where Windows tries to enum all IDE divices:

<phase name="bootStart" startTime="30" endTime="3249" duration="3218">
<pnpObject name="PCIIDE\IDEChannel\4+21254128+0+0" type="Device" activity="Enum" startTime="267" endTime="2779" duration="2511" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" />

Also starting AntiVir service takes 11s:

post-70718-0-62325500-1345152301_thumb.p

The largest delay is the run of all startup programs which takes 30.5s ( postBootDisturbance="30500")

Uninstall tools like the AMD Control Center and other stuff you don't need.

0

Share this post


Link to post
Share on other sites

Thanks for analysing it for me but that doesn't seem to explain the 1min22s delay between atipcie.sys loading and the GUI / Welcome screen appearing, which is what I'm bothered about.

0

Share this post


Link to post
Share on other sites

I can't see such an delay. Your Windows boots in 31s to the desktop and is fully booted in 61s:

timing bootDoneViaExplorer="31063" bootDoneViaPostBoot="71563"

:blink:

0

Share this post


Link to post
Share on other sites

I can't see such an delay. Your Windows boots in 31s to the desktop and is fully booted in 61s:

timing bootDoneViaExplorer="31063" bootDoneViaPostBoot="71563"

:blink:

I wish it did ;) Wierd the delay's not captured in the trace. I'll try and make another one as I didn't actually time it when making that one but rebooted and timed it then. The delay happens every time I boot though.

0

Share this post


Link to post
Share on other sites

Well I've double-checked and whether I'm doing the trace or booting normally, there's a 1min26s delay between atipcie.sys loading and the Welcome screen appearing, so the bootDoneViaExplorer="32867" is nonsense :huh:

0

Share this post


Link to post
Share on other sites

can you make some more traces? Add -numRuns X to the commandline (replace X with a number) to make several traces. Do you see the delay and xbootmgr doesn't capture them?

0

Share this post


Link to post
Share on other sites

Do you see the delay and xbootmgr doesn't capture them?

If you're asking whether xbootmgr's trace is showing the 1min26s delay that happens on every boot, no it doesn't.

can you make some more traces? Add -numRuns X to the commandline (replace X with a number) to make several traces.

I could do but I'm not sure I see any point. The delay happens every boot and neither of the two traces I've done so far reflect it, so for whatever reason xbootmgr doesn't appear to notice it and I don't see why making it repeat x times would change that.

0

Share this post


Link to post
Share on other sites

I think it doesn't show because the delay only occurs when you activate the boot logging with F8. Now Windows runs in old 640*480 pixel mode which is slow to switch to the full resolution. This was also the cause for slow Vista boot issues. And I think this logging causes the issues.

0

Share this post


Link to post
Share on other sites

I think it doesn't show because the delay only occurs when you activate the boot logging with F8. Now Windows runs in old 640*480 pixel mode which is slow to switch to the full resolution. This was also the cause for slow Vista boot issues. And I think this logging causes the issues.

Ah OK, maybe that's it. I can't recall if I had the delay before and that's why I activated the logging (with the bootlog option in msconfig, rather than F8) but I'll try deactivating that and see if it speeds it up.

0

Share this post


Link to post
Share on other sites

I think it doesn't show because the delay only occurs when you activate the boot logging with F8. Now Windows runs in old 640*480 pixel mode which is slow to switch to the full resolution. This was also the cause for slow Vista boot issues. And I think this logging causes the issues.

Well I disabled the Noguiboot and Show Boot Info options in msconfig and now it takes just as long but just doesn't show anything for about 1.5mins until the Windows loading animation appears, followed not too long after by the Welcome screen.

0

Share this post


Link to post
Share on other sites

make a new boot trace

0

Share this post


Link to post
Share on other sites

Hi MagicAndre!

Thanks for this tutorial!

I've got an ASUS X53SV that takes about 2 min to boot. I've been checking Event Handler and boot logs but I cant figure it out. Now I have tried to do a boot trace and I cant make out what take so long time booting.

I wonder if you could take a look at it?

The laptop got Intel Core i5 2410M, Geforce GT 540M graphics card, 6 GB RAM.

Best regards

0

Share this post


Link to post
Share on other sites

Run the xbootmgr command and try to follow the steps.

If this is too complicated, compress the ETl as 7z or RAR and upload it to Dropbox and post the link here.

0

Share this post


Link to post
Share on other sites

Run the xbootmgr command and try to follow the steps.

If this is too complicated, compress the ETl as 7z or RAR and upload it to Dropbox and post the link here.

I've sent a PM with a link to you.

I have been checking the etl but I cant figure out why it is taking so long to boot. Also I couldnt put DRIVERS in the command because I got blue screen...

Thanks for looking into it!

Edited by robe
0

Share this post


Link to post
Share on other sites

the trace doesn't include all data. The services.exe causes a high CPU usage and I need the callstack data. Disable Paging Executive first:

REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f 

reboot and next run this command:


xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -stackwalk profile

and upload the trace.

0

Share this post


Link to post
Share on other sites

the trace doesn't include all data. The services.exe causes a high CPU usage and I need the callstack data. Disable Paging Executive first:

REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f 

reboot and next run this command:


xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -stackwalk profile

and upload the trace.

I tried the commands but I got a blue screen, said something about USB drivers.

After restarting the laptop it booted up with latest working config.

Tried it again without DRIVERS in the command. Sent you a PM with the link to the new boot trace.

Edited by robe
0

Share this post


Link to post
Share on other sites

the new trace doesn't show the high CPU usage of services.exe for such a long time, only some smal spikes :wacko:

The high CPu usage spikes show reguistry issus:

ntkrnlmp.exe!NtInitializeRegistry and later ntkrnlmp.exe!CmpSaveBootControlSet caus the high CPU usage. So Windows hangs while scanning the registry keys.

According to it, it boots in45s to the desktop and is fully booted in 98s.


<timing bootDoneViaExplorer="45570" bootDoneViaPostBoot="108170" osLoaderDuration="3227" postBootRequiredIdleTime="10000" postBootDisturbance="52600"

Here I can see that the Avast, the Atheros and the Windows Image Acquisition service cause delays:

post-70718-0-00287800-1346424895_thumb.p

The Windows Image Acquisition service hang maybe caused by your Logitech USB Camera (HD Webcam C270), so disable the webcam and enable it only if you need it).

The largest delay is the amount of tools you run at startup. Use AutoRuns to disable useless tools.

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.