Share via

Microsoft-Windows-Kernel-EventTracing/Admin Error Code 3221225864 Win10p64b V1809(OS Build 17763.55)

Question

Sunday, October 21, 2018 6:06 PM

Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
Source:        Microsoft-Windows-Kernel-EventTracing
Date:          10/20/2018 4:34:03 PM
Event ID:      3
Task Category: Session
Level:         Error
Keywords:      Session
User:          SYSTEM
Computer:      HP1520T1
Description:
Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
    <EventID>3</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>14</Opcode>
    <Keywords>0x8000000000000010</Keywords>
    <TimeCreated SystemTime="2018-10-20T23:34:03.904176900Z" />
    <EventRecordID>125</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="2240" />
    <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
    <Computer>HP1520T1</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="SessionName">Circular Kernel Context Logger</Data>
    <Data Name="FileName">C:\WINDOWS\system32\WDI\LogFiles\ShutdownCKCL.etl</Data>
    <Data Name="ErrorCode">3221225864</Data>
    <Data Name="LoggingMode">41943168</Data>
    <Data Name="FailureReason">0</Data>
  </EventData>
</Event>

All replies (7)

Sunday, October 21, 2018 7:29 PM

possibly a duplicate of:
Event ID 3, Circular Kernel Context logger stopped

Thursday, October 25, 2018 8:31 PM

Hi

I follow the instruction at that location

According to the current situation, I suggest that you set file size by the following steps:

 

1. Open the Start Menu and search for cmd.

2. Right-click on the search result titled **cmd **and click on Run as administrator.

3. Type **perfmon.msc /s **and press Enter.

4. The **Performance Monitor **should now show up on your screen. In the left pane of the Performance Monitor, double-click on **Data Collector Sets **to expand it.

5. Click on **Startup Event Trace Sessions **under Data Collector Sets.

6. In the right pane of the Performance Monitor, locate the **ReadyBoot **entry and double-click on it.

7. Navigate to the **Stop Condition **tab and replace whatever is in the **Maximum Size **field with 40.

8. Click on **Apply **and then on OK, close the Performance Monitor, close the elevated Command Prompt and **restart **your computer.

 

Hope these are helpful.

Error still show up, so this is different 

Friday, October 26, 2018 9:44 AM

Hi,

Thanks for posting in our forum.

please follow the steps below as a test:

1. Open services.msc

2. Make sure Superfetch service startup type is Automatic and is in a running state.

3. Please open %windir%\panther, find a file named setup.etl, rename the file to setup.old and press Enter to confirm the action.

4. Schedule a reboot check if the error recurs.

Thanks for your time.

Best regards,

Otto 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, October 30, 2018 5:26 AM

Hi,

Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

Best Regards,

Otto Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, November 1, 2018 6:24 AM

Hi,

Was your issue resolved?

If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

If no, please reply and tell us the current situation in order to provide further help.

Best Regards,

Otto Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, November 1, 2018 11:09 PM

Error still showed up. I tried as you instructed. I am waiting for Win10 new release might fix it.

Thanks

Friday, November 2, 2018 7:10 AM

Hi,

Thanks for your reply.

Hope it will fix it soon.

Best Regards,

Otto Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].