Gathering a Startup, Shutdown, Sleep, Hibernate, or Reboot Trace

Once logged in, the system will present a dialog box letting you know that it is waiting 120 seconds (it will count down) before finishing the trace

Isn't the command line setting a 300 sec delay? This is for Boot trace.
A week ago the traces were working and now after the delay expires I get a window saying it can't stop the trace and it can't find various kernel loggers. I checked the registry edit and that is still there. Also did a few repair installs but still the same. Any ideas or have you seen this issue before?

Code:

[2013/05/14-16:26:21.006] Couldn't find user-mode logger in active logger list.
[2013/05/14-16:26:21.019] Unable to stop trace.
[2013/05/14-16:26:21.020] Stopping trace...
[2013/05/14-16:26:21.131] Couldn't find kernel logger in active logger list.
[2013/05/14-16:26:21.131] Couldn't find user-mode logger in active logger list.
[2013/05/14-16:26:21.132] Unregistering auto-run...
[2013/05/14-16:26:21.133] Completed auto-run change.
[2013/05/14-16:28:16.775] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started.
[2013/05/14-16:28:16.786] Registering for auto-run with a 300000 msec delay...
[2013/05/14-16:28:16.786] Completed auto-run change.
[2013/05/14-16:28:16.819] Starting trace...
[2013/05/14-16:28:17.036] Enabled boot logging to 'C:\Boot_Trace\boot_LATENCY+DISPATCHER+DISK_IO_INIT+NETWORKTRACE+MEMINFO+POWER+PERF_COUNTER+PRIORITY+REGISTRY+FILE_IO+FILE_IO_INIT_1_km_premerge.etl'
[2013/05/14-16:36:22.151] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started.
[2013/05/14-16:36:22.179] Stopping trace...
[2013/05/14-16:36:24.768] Stopped kernel logger.
[2013/05/14-16:36:24.769] Couldn't find user-mode logger in active logger list.
[2013/05/14-16:36:24.783] Unable to stop trace.
[2013/05/14-16:36:24.784] Stopping trace...
[2013/05/14-16:36:24.891] Couldn't find kernel logger in active logger list.
[2013/05/14-16:36:24.891] Couldn't find user-mode logger in active logger list.
[2013/05/14-16:36:24.892] Unregistering auto-run...
[2013/05/14-16:36:24.893] Completed auto-run change.

EDIT: ok so the traces were produced, but when I open them it says that 7 buffers were lost and it may not be reliable data. Recommended increasing these buffers, which I'm not familiar with but sounds like it's disk related. I have a 3 month old seagate ST2000 which tests out fine. Hmmmm.......

Bob Pickering said:

How do I find the 'tick Mark this thread as solved'? I keep getting messages that are no longer relevant.

That is only available for threads you start. :)

keyboardcowboy said:

Can anyone help me out understanding the trace, my system takes 7 minutes to resume from hibernation.. It hibernates in only under a minute

The Trace files can be downloaded here https://mega.co.nz/#!0o032ThK!CBpbj1...b8leLqVbL8A1Eg

Yes, but please post this in another thread, so people can find and follow it. Thank you.

It looks like there's a scheduled task running during shutdown, but I can't tell what or from where. Open a new thread and post a link here, and I'll provide some other tshooting steps to follow.

It appears that it's complaining about something on the box pre-existing that's breaking it's ability to self-register properly. If you have Visual C++ runtimes installed, that could be causing it. I can't advise you to remove them, unless you can reinstall the exact same package (if they're installed, something installed probably needs them there), but that's the usual fix for such errors.