How to disable creation of BootCKCL.etl

[7uui8uy7]

Hi,

I've disabled Circular Kernel Context Logger from Performance Monitor but the file in C:\Windows\System32\wdi\LogFiles is still getting created and the size of it increases over time while using the computer.
I pretty often get errors in Event Logger about it. Like:

The maximum file size for session "Circular Kernel Context Logger" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\system32\WDI\LogFiles\BootCKCL.etl". The maximum files size is currently set to 104857600 bytes.

and

Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188

How can I disable creation of that log file or how to get rid of the errors?

Thanks!

 

[cluberti]

1st, that isn't really going to do anything as the CKCL perfmon log you see there isn't the same one creating the bootckcl.etl file (just look at the properties of it ), so disabling that isn't going to get you anywhere. Second, the log should stop when the machine is "idle", which should be about 7-10 seconds of little CPU and disk activity.

The real curious bit is why isn't the machine hitting idle or timing out the log? I've never heard of this before, although I suppose anything is possible. Let me ping some people who are far smarter than me about what they think about this - in the meantime, can you gather / upload a boot trace as per this tutorial?

 

[7uui8uy7]

1st, that isn't really going to do anything as the CKCL perfmon log you see there isn't the same one creating the bootckcl.etl file (just look at the properties of it ), so disabling that isn't going to get you anywhere. Second, the log should stop when the machine is "idle", which should be about 7-10 seconds of little CPU and disk activity.

The real curious bit is why isn't the machine hitting idle or timing out the log? I've never heard of this before, although I suppose anything is possible. Let me ping some people who are far smarter than me about what they think about this - in the meantime, can you gather / upload a boot trace as per this tutorial?

Currently I got rid of the error with expanding the log file size from 20 to 60. I'll do a boot trace later.

https://rapidshare.com/files/57915011/Boottrace.rar

Second boottrace is taken after I modified minimum processor state under power settings from 100% to 5%

https://rapidshare.com/files/1339149699/Boottrace2.rar

 

[sheed36]

1st, that isn't really going to do anything as the CKCL perfmon log you see there isn't the same one creating the bootckcl.etl file (just look at the properties of it ), so disabling that isn't going to get you anywhere. Second, the log should stop when the machine is "idle", which should be about 7-10 seconds of little CPU and disk activity.

The real curious bit is why isn't the machine hitting idle or timing out the log? I've never heard of this before, although I suppose anything is possible. Let me ping some people who are far smarter than me about what they think about this - in the meantime, can you gather / upload a boot trace as per this tutorial?

Currently I got rid of the error with expanding the log file size from 20 to 60. I'll do a boot trace later.

https://rapidshare.com/files/57915011/Boottrace.rar

Second boottrace is taken after I modified minimum processor state under power settings from 100% to 5%

https://rapidshare.com/files/1339149699/Boottrace2.rar

Hi!
I got the same problem. How could you modify log file size?

 

[greggo 12]

BootCKCL.eti

Does anyone have a solution that will stop BootCKCL.eti from growing? The file can be deleted but on reboot, it is regenerated at the last size. It would be nice if it started all over again a zero. No such luck.

 

[drugo]

1st, that isn't really going to do anything as the CKCL perfmon log you see there isn't the same one creating the bootckcl.etl file (just look at the properties of it ), so disabling that isn't going to get you anywhere. Second, the log should stop when the machine is "idle", which should be about 7-10 seconds of little CPU and disk activity.

The real curious bit is why isn't the machine hitting idle or timing out the log? I've never heard of this before, although I suppose anything is possible. Let me ping some people who are far smarter than me about what they think about this - in the meantime, can you gather / upload a boot trace as per this tutorial?

but there is not a way to disable it?
thanks

 

[Callender]

Disable BootCKCL.etl creation

Hi,

Well I managed to disable creation but I should point out that I made a system image backup and a copy of the file first!

Deleted the file and created a new one using notepad. Then changed owner to PC\ Administrators.

From an elevated command prompt, changed to Windows directory and then typed:

attrib -h -s "C:\Windows\System32\wdi\LogFiles\BootCKCL.etl" /s /d

ENTER

Then made Administrators owner and with full control. Denied SYSTEM any control.

After testing - rebooted several times - the file remains at zero bytes in size.

Note for other users: This is not recommended. It has been done for test purposes.