Event ID: 4, Source: Microsoft-Windows-Kernel-EventTracing, maximum file size for session "ReadyBoot" has been reached. Network Steve Forum Event ID: 4, Source: Microsoft-Windows-Kernel-EventTrac ing, maximum file size for session "ReadyBoot" has been reached. Hello, I upgraded my machine to Win7 x64 Pro about 3 weeks ago. The boot drives are two Raptors configured as RAID01. All the drivers are the latest available from Intel, Asus and 3rd party vendors. My WEI is 5. The maximum files size is currently set to 20971520 bytes. My searches have turned up similar events listed but no solutions. Any help would be appreciated. Hi Vivian,Thanks for the reply. This error is popping up about every other day. I did get the ReadyBoot error this morning too. Thanks,Herb You can ignore this. This only shows, that the log file is too small and the kernel can't save all ETW Event Tracing for Windows Events for ReadyBoot not ReadyBoost. ReadyBoot is the improved Bootprefetcher, you know from XP. I don't want to ignore it. Wouldn't I want the system to log events that need to be logged??? If a log file is too big, shouldn't it rollover automatically? I did disable Superfetch a couple of weeks ago when I was trying unsuccessfully to address the constant disk activity light. When I read about superfetch at the time, I concluded it was not necessary for my system needs. If that's the culprit to this issue, why are these things optional? But may not be related as the OP has superfetch enabled. Also, I use hibernate nearly all the time. WHen I just came out of hibernation now, an alert on the screen flashed by, but it was too fast to read it. Something about "last boot. That's when I went to the Event Viewer to see what that alert was, but nothing applicable seen, except maybe this. And I don't exactly know if its applicable to the ReadyBoot error because I couldn't read the screen error. I just want to drive the car. If a light comes on and says I need an oil change, okay, I can handle that. I am running Windows 7 x64bit with 12 GB of RAM. Superfetch is already in Auto. I assume this is just a Windows 7 quirk. Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035 As suggested above I assume this is a microsoft issue? It has been discussed here and other forums for quite some time. I never have seen a fix? I wish when we received errors of this nature microsoft would tell us what they were. How is this related to superfetch? Why would superfetch have changed? Superfetch is on started is on automatic and logs on as local system. So this is not the cause of my issue. Also what is readyboot? Please update if you have any ideas. Sorry gang - I will have to report results back as they roll in for changing the MaxFileSize key. It is almost time to can this bleeding edge jive and go back to an OS that works. The maximum file size for session "ReadyBoot" has been reached. The maximum files size is currently set to 20971520 bytes. Session "ReadyBoot" stopped due to the following error: 0xC0000188 Change the setting in the registry, please. Thanks, Rob, your non-regedit suggestion was very clearly written. Changed Readyboot to 60, now let's see if pc quiets down. Erin I ran into this as well and just wanted to suggest another way to set the MaxFileSize without having to use regedit. Hope this is helpful. Regards, Rob Rob, Great tip. Would it not help if I check the checkbox next to "Circular" in the Log Mode on File tab. That would keep the file at 20 MB and eliminate the errors, right? Remote Administration For Windows. Easy remote access of Windows 7, XP, 2008, 2000, and Vista Computers.