Thank you for your help.
It appears that I have a problem with ReadyBoot or prefetcher (perhaps these are the same).
I downloaded the WPT and entered this command from an elevated command prompt ...xbootmgr -trace boot -traceFlags BASE+CSWITCH+POWER -resultPath C:\TEMP
My computer then shutdown and rebooted.
After the desktop was displayed, a dialog box was shown saying: Waiting for prefetcher ...
After 5 minutes, another dialog box was displayed saying:Gave up waiting for Win7RTM physical prefetcher after 300 seconds.
Could not wait for prefetcher.
Couldn't find kernel logger in active logger list.
Couldn't find user-mode logger in active logger list.
I clicked OK. No further automatic boots happened after the first one.
I checked my ReadyBoost - Operational event log, and (as usual) it had this entry (indicating a 0x6F reason code):Boot plan calculation completed in 5523 ms.
Boot Plan Timestamp: 2012-03-05T20:16:16.039824500Z
Reason: System boot completion
And indicating that ReadyBoot was not caching anything ...Summary of ReadyBoot Performance:
Io Read Count: 32000
Io Read Bytes: 724031488
Cache Hit Count: 0
Cache Hit Bytes: 0
Cache Hit Percentage: 0
Boot Prefetch Time (us): 0
Boot Prefetch Bytes: 0
Boot Prefetch Read Count: 0
An xbootmgr.log was created from the one and only boot ... here it is:
[2012/03/05-19:48:15.250] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started.
[2012/03/05-19:48:15.250] Registering for auto-run with a 120000 msec delay...
[2012/03/05-19:48:15.250] Completed auto-run change.
[2012/03/05-19:48:15.250] Starting trace...
[2012/03/05-19:48:15.516] Enabled boot logging to 'C:\TEMP\boot_BASE+CSWITCH+POWER_1_km_premerge.etl'
[2012/03/05-19:53:31.513] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started.
[2012/03/05-19:53:31.513] Stopping trace...
[2012/03/05-19:53:33.604] Stopped kernel logger.
[2012/03/05-19:53:33.728] Stopped user-mode logger.
[2012/03/05-19:53:33.728] The trace you are capturing "C:\TEMP\boot_BASE+CSWITCH+POWER_1.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people.
[2012/03/05-19:54:02.384] Merged ETL file to 'C:\TEMP\boot_BASE+CSWITCH+POWER_1.etl'
[2012/03/05-19:54:02.399] Waiting for prefetcher...
[2012/03/05-19:58:52.841] Gave up waiting for Win7RTM physical prefetcher after 300 seconds.
[2012/03/05-19:58:52.841] Could not wait for prefetcher.
[2012/03/05-19:58:52.841] Stopping trace...
[2012/03/05-19:58:52.856] Couldn't find kernel logger in active logger list.
[2012/03/05-19:58:52.856] Couldn't find user-mode logger in active logger list.
[2012/03/05-19:58:52.856] Unregistering auto-run...
[2012/03/05-19:58:52.856] Completed auto-run change.
The log shows the same problem .... boot manager gave up waiting for prefetcher.
An ETL file (boot_BASE+CSWITCH+POWER_1.etl) was created (from the single boot). I used this command:xperf /tti -i boot_BASE+CSWITCH+POWER_1.etl -o summary_boot.xml -a boot
... to create a summary_boot.xml file, and I will attach that file to this post for your review. The file only represents one boot, so it might not be very useful for analyzing areas to improve my boot time .... but perhaps it contains a hint on what is causing ReadyBoot and/or prefetcher to throw a non-zero result code and/or not respond. I think that once I fix the problem with ReadyBoot (and it starts to function as it should by caching), my boot time will be greatly reduced.
Boot Manager timed out waiting for the prefetcher. Could that have something to do with the 0x6F return code we are seeing in the event log?
Like I said, I think I have a problem with ReadyBoot and/or prefetcher. It (they) are failing to complete properly. I think this (the lack of proper caching) is resulting in my long (> 2 minutes) boot times, and it appears this caused the boot manager to terminate (after one boot) because the prefetcher did not respond.
Any thoughts or suggestions on what I can do to figure out the cause of this ReadyBoot/prefetcher problem would be appreciated. I know I could just re-install Windows, but at this point I'd rather tolerate a 2 minute boot than deal with reinstalling Windows (easy) and reinstalling/re-customizing apps, etc.
Edited by geekster51, 05 March 2012 - 10:09 PM.