looks like the reading of the hibernation file is slow:

hiberread="77696000"

your Hitachi Travelstar 5K250 160GB is not the fastest HDD.

Oh yeah, those HDD is my secondary Drive and I installed at HDD Caddy, I got it from my old laptop. My Primary is SSD Team Xtreem S3 120GB and I install windows 8 in SSD.

Maybe I will try to tweak hibermate settings :-/ (size to 100%)

<unexpectedLonglived>

<process name="smss.exe" startTime="5376" endTime="-1" lifetime="-1"/>

<process name="csrss.exe" startTime="426505" endTime="-1" lifetime="-1"/>

<process name="csrss.exe" startTime="428346" endTime="-1" lifetime="-1"/>

is this normal?

is this normal?

yes, those are 3 critical Windows processes which run all the time. Ignore this.

is this normal?

yes, those are 3 critical Windows processes which run all the time. Ignore this.

I was asking because my fresh install of Windows 8 takes 5+ minutes or so to boot.

summary_boot.xml

SMSSInit is very slow.

<interval name="SMSSInit" startTime="5376" endTime="429690" duration="424314">

I need the ETL file to see more. Why are you not using the new fast startup?

SMSSInit is very slow.

<interval name="SMSSInit" startTime="5376" endTime="429690" duration="424314">

I need the ETL file to see more. Why are you not using the new fast startup?

The fast startup option in the power options? I am using it.

My ETL is 100mb

Edited December 6, 201213 yr by asdfdsa

you have disk IO. Check if Autochk.exe is the cause (click on the left icon next to the disk io graph)

If you use fast boot, run the faststartup xbootmgr command at the end of the guide. You did the normal "old-school" boot.

you have disk IO. Check if Autochk.exe is the cause (click on the left icon next to the disk io graph)

If you use fast boot, run the faststartup xbootmgr command at the end of the guide. You did the normal "old-school" boot.

All I got from the graph was ' System Processes (4) '

Also I renamed Autochk.exe, but there was no difference in the boot time.

Edited December 8, 201213 yr by asdfdsa

compress the ETL file, upload it to SkyDrive or Dropbox and send me the link.

the trace shows autochk runs at this time. Delete the autochk entry from BootExecute in the registry and run chkdsk yourself.

the trace shows autochk runs at this time. Delete the autochk entry from BootExecute in the registry and run chkdsk yourself.

Again there was little to no difference in boot time.

Any idea why smss.exe would be taking so long?

smss.exe runs so long because autochk runs during boot (smss:BootExecute)

smss.exe runs so long because autochk runs during boot (smss:BootExecute)

I stopped autochk from running, there is no difference in boot time.

make a new boottrace.

this time InitializeRegistry takes so much time.

Add +Registry+REG_HIVE to the command (after POWER) and -stackwalk RegQueryKey+RegDeleteKey+RegCreateKey+RegOpenKey+RegSetValue+RegDeleteValue+RegQueryValue+RegCloseKey+RegCloseKey

xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER+Registry+REG_HIVE -stackwalk RegQueryKey+RegDeleteKey+RegCreateKey+RegOpenKey+RegSetValue+RegDeleteValue+RegQueryValue+RegCloseKey -resultPath C:\TEMP

this activates registry data collection.