Windows 10: Kernel-EventTracing 0xC0000188

Session "ReadyBoot" stopped due to the following error: 0xC0000188

- <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="2019-02-21T16:49:01.965540700Z" />
<EventRecordID>312</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="160" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>DESKTOP-GBS0FMA</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="SessionName">ReadyBoot</Data>
<Data Name="FileName">C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">276824064</Data>
<Data Name="FailureReason">0</Data>
</EventData>
</Event>
- Provider
[ Name] Microsoft-Windows-Kernel-EventTracing
[ Guid] {B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}
EventID 3
Version 1
Level 2
Task 2
Opcode 14
Keywords 0x8000000000000010
- TimeCreated
[ SystemTime] 2019-02-21T16:49:01.965540700Z
EventRecordID 312
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 160
Channel Microsoft-Windows-Kernel-EventTracing/Admin
Computer DESKTOP-GBS0FMA
- Security
[ UserID] S-1-5-18

:)

 

Windows-Kernel-EventTracing/Admin

Microsoft-Windows-Kernel-EventTracing/Admin

 

Kernel-EventTracing error

I had also this problem with two Kernel-EventTracing (id 2) error after each Windows10 start since last Windows 10 update 1709. I got rid of it only changing one OneDrive setting. I ensured in Settings tab that the Files On-Demand checkbox is not checked.
This was enought for me and id 2 errors disappeared from the event viewer.

Thanks for you suggestions that help me to find correct route for the problem.

 

Kernel-EventTracing error

A total reinstall is not a practical solution to this benign error and likely would make no difference. Others have reported it, so it's not unique to my system. The error was never seen after earlier system upgrades.

Better to either ignore it or disable Kernel-EventTracing logging for now.