Windows 7 ReadyBoot.etl

Posted: Mon Sep 26, 2011 10:49 am

Error:

Kernel-Event Tracing:

The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

Solution 1: found on MS Social from user voxmuta is as follows:

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/ad58fb17-ee50-4353-9967-f70b24e2d87f/

Quote:

Hey guys, the solution is simple - just increase the max file size! Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\ReadyBoot

The MaxFileSize key is a DWORD with a default decimal value of 20. Increase this to, say 60, and the problem will go away.

Luck to ya!

Solution 2: From AbsoluteJoe on Just2good

http://www.just2good.co.uk/forum/index.php?s=c1a99a2aa9aa97a727dff0e93b265283&showtopic=5955&pid=30683&st=0&#entry30683

Quote:

Kernel-Event Tracing:

The maximum file size for session "ReadyBoot" has been reached.
As a result, events might be lost (not logged) to file
"C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl".
The maximum files size is currently set to 20971520 bytes.

The problem is is that the ReadyBoot.etl log that tracks all file
activity at boot time fills up and is not bring reset or cleared.
This log file provides information to optimize boot time file
placement for disk anaylsis and defragmention. Since all file
activity at done at boot time (even system updates, AV or
spyware scans) accumulates in this file, it may fill with obsolete
information. The fix is to set the ReadyBoot.etl into Circular logging
mode, so that only the most recent file access activity is tracked.

How to fix in Vista or Windows 7 using an Administrator account:

Open the Control Panel, Administrative Tools, Performance Monitor

Expand left side tree entry for Data Collection Sets

Highlight Startup Event Trace Sessions

Open the ReadyBoot line (click on it)

Select the File tab (click on it)

Select the Circular option (check on the check box)

Click on Apply and OK

Reboot the system

After the reboot, the "\Windows\Prefetch\ReadyBoot\ReadyBoot.etl"
should be reset and should only contain file access information from
the last boot. You may have to wait a few minutes after boot for the
data to be updated and the ReadyBoot.etl file buffers flushed.

Any disk defragmenter that is ReadyBoot.etl aware will use this data
to place the files accessed at boot time together to increase bootup performance.

Quote:

After some additional defrag testing, my post about ReadyBoot.etl needs clarification.

If you set the logging mode to Circular, the newest file access events will overwrite the oldest.
While this makes the log full error disappear, it also results in only the
last events being present in the log (about 40K entries for a 20 meg log).
If a defrag program uses the circularly logged ReadyBoot.etl to relocate files,
it will place only the last accessed files, rather than the files
accessed since boot, in the preferred location.

If the Circular attribute is NOT set (the default), then the kernel file accessed since boot until the ReadyBoot.etl log fills will be logged.
Defragmentation will move the files accessed since boot to in the preferred location.
On my system a 2 to 3 meg ReadyBoot.etl is big enough to hold all boot time file access events.
If you want the defrag utility order files by boot access sequence, then you'll have to live with the ReadyBoot.etl full message in the event log until Microsoft decides to provide a way to suppress it.

Note that the defragmentation file activity may also be tracked by the kernel, so re-running the defrag one or more times without a reboot may produce some unexpected or unusual file placement results.