New
#51
Your Z68 board supports an SSD assist to the hard drive. Do you have that set up?
If the SSD runs good alone and the only time you have problems is with both drives attached, it seems to me that there is somthing wrong with the WD drive or the sata controllers on the board.
I checked my Diagnostics-Performance logs to see whether getting my SSD properly recognized as the system drive made any difference in boot times. That one change seems to have fixed the OtherKernelInitDuration problem but created another, albeit less time consuming, delay in a metric called SessionInitOtherDuration. My total boot time dropped by six seconds in the exchange.
Anyone care to hazard a guess as to what SessionInitOtherDuration is supposed to be measuring? It increased from 345 to 19358 milliseconds.
-
EventData
BootTsVersion
2
BootStartTime
2011-10-25T00:14:04.624800200Z
BootEndTime
2011-10-25T00:15:59.527641700Z
SystemBootInstance
130
UserBootInstance
124
BootTime
36659
MainPathBootTime
23859
BootKernelInitTime
21
BootDriverInitTime
227
BootDevicesInitTime
1221
BootPrefetchInitTime
0
BootPrefetchBytes
0
BootAutoChkTime
0
BootSmssInitTime
20632
BootCriticalServicesInitTime
290
BootUserProfileProcessingTime
366
BootMachineProfileProcessingTime
0
BootExplorerInitTime
855
BootNumStartupApps
11
BootPostBootTime
12800
BootIsRebootAfterInstall
false
BootRootCauseStepImprovementBits
0
BootRootCauseGradualImprovementBits
0
BootRootCauseStepDegradationBits
0
BootRootCauseGradualDegradationBits
0
BootIsDegradation
false
BootIsStepDegradation
false
BootIsGradualDegradation
false
BootImprovementDelta
0
BootDegradationDelta
0
BootIsRootCauseIdentified
false
OSLoaderDuration
563
BootPNPInitStartTimeMS
21
BootPNPInitDuration
1239
OtherKernelInitDuration
161
SystemPNPInitStartTimeMS
1391
SystemPNPInitDuration
208
SessionInitStartTimeMS
1609
Session0InitDuration
875
Session1InitDuration
398
SessionInitOtherDuration
19358
WinLogonStartTimeMS
22242
OtherLogonInitActivityDuration
396
UserLogonWaitDuration
141
Last edited by Raillex; 24 Oct 2011 at 20:49.
It measures the time it takes winlogon to start, minus smss.exe start time, minus session 0 and session 1 init time. If you take another trace and look at the Boot Phases graph, you should see what I'm talking about.
Uploading the new Boot Trace report to Rapidshare right now. I'm wondering whether this is some sort of logon related delay.
Here is my latest Boot Trace report. I don't have the skills necessary to interpret the results, much less formulate an opinion as to what might be causing the high SessionInitOtherDuration reading. Could you help?
https://rapidshare.com/files/1063463...REGISTRY_1.etl