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

1,275 posts in this topic

This is an updated tutorial of the one cluberti posted here.

To get started you need the Windows Performance Tools Kit. Read here how to install it:

Now open a command prompt with admin rights and run the following commands:

For boot tracing:

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

Attention: Some users reported that they get a bugcheck (BSOD) when using the DRIVERS flag in the boot trace command. If you get this, use system restore to go back to a working Windows and run the command without DRIVERS

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

Also change the name in the command to generate the XML.

I've send some dumps to Microsoft, they look at the issue right now.

For shutdown tracing:

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

For Standby+Resume:

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

For Hibernate+Resume:

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

replace C:\TEMP with any temp directory on your machine as necessary to store the output files

All of these will shutdown, hibernate, or standby your box, and then reboot to finish tracing. Once Vista/Server 2008(R2) or Windows 7 does reboot, log back in as necessary and once the countdown timer finishes, you should now have some tracing files in C:\TEMP. If asked, upload or provide the file(s) generated in C:\TEMP (or the directory you chose) on a download share for analysis.

Analyses of the boot trace:

To start create a summary xml file, run this command (replace the name with the name of your etl file)

xperf /tti -i boot_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_boot.xml -a boot

Now you see this picture.:


You have too look at the timing node. All time values are in ms.

The value timing bootDoneViaExplorer shows the time, Windows needs to boot to the desktop.

The value bootDoneViaPostBoot is the time (+10s idle detection) which Windows needs to boot completly after finishing all startup applications.

During the OSLoader phase (shown in the value osLoaderDuration), the Windows loader binary (Winload.exe) loads essential system drivers that are required to read minimal data from the disk and initializes the system to the point where the Windows kernel can begin execution. When the kernel starts to run, the loader loads into memory the system registry hive and additional drivers that are marked as BOOT_START.

Visual Cues

This phase begins approximately when the BIOS splash and diagnostic screens are cleared and ends approximately when the “Loading Windows” splash screen appears.

those values show you a summary.

The MainPathBoot Phase

What Happens in This Phase
During the MainPathBoot phase, most of the operating system work occurs. This phase involves kernel initialization, Plug and Play activity, service start, logon, and Explorer (desktop) initialization. To simplify analysis, we divide the MainPathBoot phase into four subphases, as show in the next picture. Each subphase has unique characteristics and performance vulnerabilities.

Visual Cues

Visually, the MainPathBoot phase begins when the “Starting Windows” splash screen appears and lasts until the desktop appears. If auto-logon is not enabled, the time that elapses while the logon screen is displayed affects the measured boot time in a trace.


PreSMSS Subphase

What Happens in This Subphase
The PreSMSS subphase begins when the kernel is invoked. During this subphase, the kernel initializes data structures and components. It also starts the PnP manager, which initializes the BOOT_START drivers that were loaded during the OSLoader phase. When the PnP manager detects a device, it loads and initializes the device’s drivers

Visual Cues
PreSMSS begins approximately when the “Loading Windows” splash screen appears. There are no explicit visual cues for the end of PreSMSS.

So if the time takes too long for you, look inside the <PNP> node which driver is loading too slowly.

SMSSInit Subphase

What Happens in This Subphase
The SMSSInit subphase begins when the kernel passes control to the session manager process (Smss.exe). During this subphase, the system initializes the registry, loads and starts the devices and drivers that are not marked BOOT_START, and starts the subsystem processes. SMSSInit ends when control is passed to Winlogon.exe.

Visual Cues
There are no explicit visual cues for the start of SMSSInit, but the blank screen that appears between the splash screen and the logon screen is part of SMSSInit. It ends before the logon screen appears.

SMSSInit Performance Vulnerabilities
Video drivers are a common source of performance problems in the SMSSInit subphase. The video driver must be initialized first in the system session and then in the user session. Reduction of video driver initialization time leads to a direct wall-clock reduction in boot time.
Initialization in the user session is typically much faster than in the system session because Windows performs common initialization tasks during the system session.

So if the SMSSInit Phase takes too long, try to get an graphic card driver update.

WinLogonInit Subphase

What Happens in This Subphase
The WinLogonInit subphase begins when SMSSInit completes and starts Winlogon.exe. During WinLogonInit, the user logon screen appears, the service control manager starts services, and Group Policy scripts run. WinLogonInit ends when the Explorer process starts.

Visual Cues
WinLogonInit begins shortly before the logon screen appears. It ends just before the desktop appears for the first time.

WinLogonInit Performance Vulnerabilities
Many operations occur in parallel during WinLogonInit. On many systems, this subphase is CPU bound and has large I/O demands. Good citizenship from the services that start in this phase is critical for optimized boot times.
Services can declare dependencies or use load order groups to ensure that they start in a specific order. Windows processes load order groups in serial order. Service initialization delays in an early load order group block subsequent load order groups and can possibly block the boot process .

If you have too long WinLogonInit Time, open the etl file and scroll to the service graph and look for a long delay.


In this example the service SavService (Sophos Anti-Virus\SavService.exe) is part of the Plug and Play group and causes a delay because the service takes too long to start. Try to get an update for the hanging service or remove the software.

ExplorerInit Subphase

What Happens in This Subphase

The ExplorerInit subphase begins when Explorer.exe starts. During ExplorerInit, the system creates the desktop window manager (DWM) process, which initializes the desktop and displays it for the first time.
This phase is CPU intensive
. The initialization of DWM and desktop occurs in the foreground, while in the background the service control manager (SCM) starts services and the memory manager prefetches code and data. On most systems ExplorerInit is CPU bound, and timing issues are likely the result of a simple resource bottleneck.
Visual Cues
ExplorerInit begins just before the desktop appears for the first time. There is no clear visual cue to indicate the end of ExplorerInit.

ExplorerInit Performance Analysis

Applications—such as antivirus programs or application servers—that are created during service start in this or previous phases can consume CPU resources during ExplorerInit. Some services might not be started yet when ExplorerInit is complete.

So if the ExplorerInit phase takes too long, make sure you minimize the services which use a lot of CPU power and make sure your AV Tool doesn't hurt too much. If it doesn't change the tool and try a different.

The PostBoot Phase

What Happens in This Phase
The PostBoot phase includes all background activity that occurs after the desktop is ready. The user can interact with the desktop, but the system might still be starting services, tray icons, and application code in the background.
Specifically, Xperf samples the system every 100 ms during the PostBoot phase. If the system is 80-percent or more idle (excluding low-priority CPU and disk activity) at the time of the sample, Xperf considers the system to be “idle” for that 100 ms interval. The phase persists until the system accumulates 10 seconds of idle time.
Note: When you review traces and report timing results, you should subtract the 10 second idle time that accumulated during PostBoot to determine total boot time.

Visual Cues
There are no explicit visual cues for PostBoot. The phase begins after the user’s desktop appears and ends after satisfying the 10-second metric that was explained earlier.

PostBoot Performance Vulnerabilities
During PostBoot, Windows examines the entries in the various Run and RunOnce keys (Run, RunOnce, RunOnceEx, RunServices, and so on) in the registry and the Startup folder in the file system, and then starts the listed applications.

If post boot takes too long, reduce the number of running applications at startup with the help of msconfig.exe or AutoRuns.

When you have a HDD (no SSD!) and you want to speedup the boot, run the optimization from this guide:

Analyses of the shutdown trace:

The shutdown is divided into this 3 parts:


To generate an XML summary of shutdown, use the -a shutdown action with Xperf:

xperf /tti -i shutdown_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_shutdown.xml -a shutdown

Open the XML and you see this:


It shows you the most relevant data.

<timing shutdownTime="23184" servicesShutdownDuration="1513">

The shutdownTime is in this example 23s. Stopping the services takes 1.5s which is fast.

Next you have an entry for all sessions. Starting with Vista, all services run in Session 0 (Session 0 Isolation) and each user gets his one Session (1,2,..,n).

sessionShutdown sessionID="1" duration="3321">

shows the time which it takes to stop all applications which the user is running. In this example it takes 3.3seconds.

UserSession Phase

What Happens in UserSession
During this phase, the Client/Server Runtime Server Subsystem (Csrss.exe) shuts down all applications that are running in the user session—that is, all applications that have session ID 1.

If after 5 seconds any application blocks shut down, Windows displays the dialog box in Figure 24 so that users can choose to force or cancel shutdown.


UserSession Performance Vulnerabilities

Because Windows serially shuts down applications, any delay in a process’s shutdown path contributes to the total shutdown duration. To ensure a speedy shutdown, every application must respond quickly to shutdown notification messages (WM_QUERYENDSESSION and WM_ENDSESSION).
Windows uses long time-outs so that applications have sufficient time to shut down and save user data. Therefore, applications can have a significant effect on shutdown performance.

sessionShutdown sessionID="0" duration="1513">

The value sessionShutdown sessionID="0" shows the servicesShutdownDuration. So you can see which service takes too long to stop.

SystemSession Phase

What Happens in SystemSession

This phase includes two subphases:
• Preshutdown notification. Windows serially shuts down all services that registered to receive preshutdown notifications. Ordered services—services that have set up the shutdown order of dependent services—are shut down before non-ordered services.
• Shutdown notification. All services that registered to receive shutdown notifications are shut down in parallel.

If all services have not exited after 20 seconds (in Windows Vista) or 12 seconds (in Windows 7), the system continues the shutdown. Processes and services that do not shut down in a timely manner are left running as the system shuts down.

SystemSession Performance Vulnerabilities

In the preshutdown notification subphase, the SCM serializes the waits. Therefore, these services block system shutdown until they exit or until the wait hint time-out expires.
Services are not guaranteed to have enough time to finish all their work in the shutdown notification subphase before the system shuts down.

In both cases expand the node and look at the shutdownDuration value.

It helps you to identify a hanging application are service.

KernelShutdown Phase

What Happens in KernelShutdown
In the KernelShutdown phase, the rest of the system, including all devices and drivers, is shut down.

To calculate the time spent in KernelShutdown, subtract the time that is required to shut down the system and user sessions from shutdownTime.

In my example:

KernelShutdown = 23184 - 3321 - 1513 = 18350

In this case the 18.35 seconds are very slow. In the <interval> you see an entry ZeroHiberFile which takes too long. In this expample the user enabled the Option ClearPageFileAtShutdown under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management to 1. This overrides the hiberbation file with 0 to delete personal data. This causes the huge slowdown. Setting this option to 0 would save 12.64 seconds of shutdown time.

That is all you need to analyze slow shutdown issues.

Analyses of the Hibernation trace::

To generate the XML, run this command:

xperf /tti -i hibernate_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_hibernation.xml -a suspend

Analyses of the Sleep/Resume trace::

xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspend

Open the XMLs and look for long BIOS init times and services/application which take very long to suspend and resume.

For deeper analysis refer to the Sleep and Hibernate Transitions part of theWindows On/Off Transition Performance Analysis Guide from Microsoft.

The pictures Shutdown_cancel.png, Shutdown_picture.png and Boot_MainPathBoot.png were taken from this Windows On/Off Transition Performance Analysis Guide. Read it if you need more information.

// Edit: 2010-11-28

Add the explanation of the boot process

// Edit: 2010-10-11

added the optimization guide

// Edit: 2010-10-09

If you get a BSOD (Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) while making traces, REMOVE ALL USB DEVICES and reboot! When making a new trace remove the DRIVERS flag from the command line!

// Edit: 2010-02-04

Added the -noPrepReboot command at shutdown tracing to prevent the preparatory reboot during a shutdown/rebootCycle trace. Usually, the reboot is required to ensure a consistent machine state before the first shutdown if multiple traces are being taken.

// Edit: 2010-05-08

Added the link to the Visual Studio 2010 Diagnostic Tool as alternative download to get the Windows Performance Toolkit Installers.

Added some pictures.

Edited by MagicAndre1981

Share this post

Link to post
Share on other sites

I came across this by accident and have been wondering how to get Load time on each Process during Boot. Thanks for posting this tutorial, was exactly what I was looking for

I have also posted this tutorial at The Windows Club as well as linked back to here. Thanks for putting this tutorial up


Share this post

Link to post
Share on other sites

if you have issues with boot, shutdown, resume, make a trace and upload it. I can take a look at it.


Share this post

Link to post
Share on other sites

I've linked to the Web installer, because its much smaller compared to the ISO. There are still people with limited Internet access.


Share this post

Link to post
Share on other sites

This is not the old one (command line ) to boot trace i liked that one better

it did a boot trace in a 6 time cycle and that one worked for me.

It was also posted on msfn but since the site changed the post was removed and changed into this but it's not the same one.

so can anyone give me the old boot trace code please

Edited by tbusters

Share this post

Link to post
Share on other sites

What should I give you? Sorry I don't understand what you want :blushing:


Share this post

Link to post
Share on other sites

what? That's the same like in old xperf toolkit found in the Windows Server 2008 SDK. I only removed the -noPrepReboot option from boot trace, because this parameter is no longer needed in the new WPT version.

Please explain in detail what's wrong and what do you want to have back!


Share this post

Link to post
Share on other sites

whats wrong I already explained, I would really would have like the command line for the boot trace with the 6x restart. This command line was posted on ur old post that has been removed

these are some of the lines I found on the internet:

xbootmgr.exe –trace boot –prepSystem

xbootmgr.exe -trace boot -numruns 5

but i dont know what the difference is between all the lines

Edited by tbusters

Share this post

Link to post
Share on other sites

-numruns defines the number of test runs!

-prepSystem optimizes the Windows Vista/7 startup as I show here:

Look into the documentation of the Windows Performance Toolkit if you want to know what all the command line option mean!


Share this post

Link to post
Share on other sites

I have also posted this tutorial at The Windows Club as well as linked back to here. Thanks for putting this tutorial up


Share this post

Link to post
Share on other sites

could you please send me the link?


Share this post

Link to post
Share on other sites

Hello MagicAndre,

I got winsdk_web.exe from your link and I tried to install it. The installation failed. To be sure, I made searches for the paths, directories and files included on your links, but nothing was there, of course. I tried to install three times.

Then I downloaded the GRMSDKX ISO version, tried again, same result. As I wanted to clean up anything that might have stayed between these failed installation, I tried to do it with the Windows Install Clean Up tool, but the tool found nothing to clean.

I transcribe the final part of the log file below. I have windows 7, and an ASUS motherboard with the AMD 64 II X3 440 CPU and AMD chipset. All updated.

Could you, please, tell me what else I’ll have to do to make it install, so that I could perform your tests?

At the end of the failed installation I received this message:

A problem occurred while installing selected Windows SDK components.

Setup could not find the file WinSDK\WinSDK_x86.msi at any of the specified source locations C:\Users\......\Desktop\GRMSDKX_EN_DVD\Setup

[This file is found nowhere in the computer]

This is the end of the log:

23:37:12 07 May 2010: [sDKSetup:Info] Config_Products_DetermineFeatureState: Feature: WinSDKInterop_x86Libs; Installed: Absent; Request: Local;

23:37:12 07 May 2010: [sDKSetup:Info] Config_Products_DetermineFeatureState_End: Feature: WinSDKInterop_x86Libs

23:37:12 07 May 2010: [sDKSetup:Info] Config_Products_DetermineFeatureState_Begin: Feature: WinSDKInterop_IA64Libs

23:37:12 07 May 2010: [sDKSetup:Info] Config_Products_DetermineFeatureState: Feature: WinSDKInterop_IA64Libs; Installed: Absent; Request: Local;

23:37:12 07 May 2010: [sDKSetup:Info] Config_Products_DetermineFeatureState_End: Feature: WinSDKInterop_IA64Libs

23:37:13 07 May 2010: [sDKSetup:Info] Config_Products_Detect: Windows SDK Setup (detected)

23:37:28 07 May 2010: [sDKSetup:Info] Config_OS_Install: Operating system configuration (installed)

23:37:28 07 May 2010: [sDKSetup:Info] Config_MSI_Install: Windows Installer Setup (installed)

Edited by Andrews

Share this post

Link to post
Share on other sites

ok, I'll update the tutorial later to an alternative download which is only 100MB.

// Edit

I've updated the tutorial with a Link to the Visual Studio 2010 Diagnostic Tool.

Edited by MagicAndre1981

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.