Share via

Circular Kernel Context Logger

Anonymous
2018-05-18T21:10:58+00:00

The Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188 I back from the death. I just turn on my computer and is heavy

I want to try to get these fix since more and more windows errors are starting to appear. 

these is one

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\ShutdownCKCL.etl". The maximum files size is currently set to 20971520 bytes.

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

And com. is annoying.

I try all. IF someone from MS can see these and help me to make these go away I can arrange something. so we can work these out.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-05-28T22:05:47+00:00

    Hello Carlos,

    Some possible causes for this error message can be due to user’s display drivers are not working properly, the maximum file size of the Startup Event Trace Sessionsbeing too small and the affected computer’s SETUP.ETLfile being corrupt. To help resolve the issue, we suggest that you try these methods:

    Method 1: We suggest you to check if the Superfetch service is enabled

    1.  On the desktop, press Windows key + R to open the Run Dialog.

    2.  Type services.msc in the Run Dialog, and then press Enter to open Services.

    3.  Right-click the Superfetch service, and then click Properties.

    4.  If the Startup type box is set to Disabled, change it to Automatic or Manual.

    5.  Click OK to close the Properties window.

    6.  Right-click the Superfetch service, and then click Start. The service should start without errors.

    Method 2: Increase the maximum files size of the Startup Event Trace Sessions.

    1. On the desktop, press Windows key + R and type cmd to open the Command Prompt.
    2. On the left panel of the Performance Monitor window, expand Data Collector Sets.

    3.  Click on Startup Event Trace Sessions.

    1. Open ReadyBoot Trace Session Property Sheet.
    2. Click on the Stop Condition tab and increase the Maximum Size to 40.
    3. Click on Apply and OK.

    Restart the computer and check if the issue is resolved.

    Let us know how it goes.

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-06-01T23:54:51+00:00

    Thank you for providing us an update, Carlos. We suggest that you contact your device manufacturer for advanced technical assistance as this might be an issue already with your BIOS.

    Feel free to create a new thread should a new issue arise.

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-05-29T00:18:30+00:00

    Hi Anna. I did. but did not fix. I test both scenarios and even add the 40 as recommended but still. 

    Display drivers, you main the display monitors itself of nvidia drivers.   If display drivers... there are non. Most of the time brands like Viewsonic does not push drivers since are old. most generic are updated. Acer..... all are generic. there are none. 

    Unless MS send feedback of the error to manufactures, there is  no fixes. 

    As far is my investigation, Viewsonic does not have drivers that works on window 10. I try to loaded but does not detect it.

    1 person found this answer helpful.
    0 comments