C Windows Prefetch Readyboot Readyboot Etl

0602
C Windows Prefetch Readyboot Readyboot Etl Average ratng: 4,0/5 8682 votes
  1. Disable Readyboot Win 7

Microsoft-Microsoft-Windows-Kernel-EventTracing/AdminWindows-Kernel-EveLog Name. (not logged) to file 'C: Windows Prefetch ReadyBoot ReadyBoot.etl'.

AirSpaceChannel log

Applications and Service Logs/Microsoft/Office/AirSpace

Readyboot

Disable Readyboot Win 7

Jan 28, 2016  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. Sep 26, 2011  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'.

Search 'Computer Management' or type compmgmt.msc to launch Computer Management.

Under 'Performance' is the 'Startup Event Trace Sessions' that contains the 'EventLog-AirSpaceChannel' properties.

Right-click choose Properties and set the log more to 'Circular'. Uncheck another setting such as 'Append' to toggle it to Circular if necessary. Click OK to save your change.

There is also an entry under the Event Viewer > Applications and Services > Right-click and select View > Show Analytic and Debug Logs > then under Microsoft > Office > AirSpace are the other properties. It can also be set to Overwrite as needed. But setting it to Circular is the same thing.

But that is all there is to this error. A remnant leftover from a log setting mistake.




READYBOOT ISSUES

You are getting message that The maximum file size for session 'ReadyBoot' has been reached.

I have to let you know that ReadyBoot.etl log that tracks all file activity at boot time.

Since all file activities done at boot time (even system updates and 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.

To do so:

a. Click start, click control panel

b. Click administrative tools, performance monitor

c. Expand left side tree entry for Data Collection Sets

d. Highlight Startup Event Trace Sessions

e. Open the ReadyBoot line (click it)

C Windows Prefetch Readyboot Readyboot Etl

f. Select the File tab

g. Select the circular option

h. Click apply and ok and restart the computer.

Superfetch service improves the performance and hence it is suggested to set its startup as automatic.

Changing the registry value would increase the max size and it will reach the limit again and then again he may change the registry value.

Disclaimer: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:


Change 'Circular' logging to end those events and maybe keep ReadyBoot from stopping

Computer Management > Performance > Data Collect... > Event Trace ... then double click the listed item for ReadyBoot .

Recently event viewer has been showing:

Disable readyboot win 7

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

I see questions about this frequently and the normal fix is to change the default value for MaxFileSize to 60 or so in

HKEY_LOCAL_MACHINEsystemCurrentControlSetControlWMIAutologgerReady Boot

So I recently built my system. Asus Maximus viii, Corei7 6800k, 16gb pc3200 ram (not OC'd), kingston hyperx 480gb SSD (C:), Kingston M.2 SSD 480gb (D:), overspecced PSU (can't remember brand) Nvidia 980 TI 6gb (Factory OC).
Updated mobo, gpu and hdd firmwares. Running Windows 10 with latest patches. Latest driver versions as far as I can tell.
Occaisonally windows freezes and a reboot fixes it.
Occaisonaly windows freezes and then the machine won't boot. Blank screen not even a POST screen. Its weird when it happens as I have to leave it a day before it'll come back on again. Not even a few hours - a day.
Pretty Annoying. It freezes about once a week where the reboot fixes it. Every couple of weeks it does a mega freeze. Any ideas how I can track down what is causing this? I've been keeping an eye on heat and its not really getting hot. Sometimes I game and it'll happily game on max settings for hours.
No dodgy software installed (EVER!). Im stumped. Pretty annoying seeing as I tipped so much money into this!
This entry was posted on 6/2/2019.