MSFN Forum: Trace Windows 7 boot/shutdown/hibernate/standby/resume issues

Jump to content






Icon Latest News Comments


Icon MSFN Statistics

  • Total Posts 802580
  • Total Members 102337
  • Newest Member wonka123 
  • Online At Once Record 17869
  • Online Now: 2561



    Icon Recommended Sites

    AskVG.com Bink Filehorse FreewareFiles IT Magazine lunarsoft Where unprofessional journalism looks better OSNN TechLog The Windows Club WinBeta

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

Posted on Dec 08 2009 02:23 AM by MagicAndre1981  in Guides | Viewed 6838 Times


The MainPathBoot Phase

Quote

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.


Posted Image

PreSMSS Subphase

Quote

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 node which driver is loading too slowly.

SMSSInit Subphase

Quote


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.







0 Comments

Page 1 of 1

No comments have been made yet

You do not have permission to leave comments on this article
Page 1 of 1



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy