SInce a recent Intel Driver Update run, each bootup of my Win 7 Pro 64-bit generates these errors and warnings - and please do not ask me for generic information - others have this problem and I want Intel to fix this.
Log Name: | Microsoft-Windows-Kernel-EventTracing/Admin |
Source: | Microsoft-Windows-Kernel-EventTracing |
Date: | 2/4/2017 9:52:44 PM |
Event ID: | 3 |
Task Category: Session
Level: | Error |
Keywords: | Session |
User: | SYSTEM |
Computer: | WINDOWS-B686H5R |
Description:
Session "NT Kernel 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>0</Version> | |
<Level>2</Level> | |
<Task>2</Task> | |
<Opcode>14</Opcode> | |
<Keywords>0x8000000000000010</Keywords> | |
<TimeCreated SystemTime="2017-02-05T02:52:44.748453100Z" /> | |
<EventRecordID>171</EventRecordID> | |
<Correlation /> | |
<Execution ProcessID="4" ThreadID="188" /> | |
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel> | |
<Computer>WINDOWS-B686H5R</Computer> | |
<Security UserID="S-1-5-18" /> |
</System>
<EventData>
<Data Name="SessionName">NT Kernel Logger</Data> | |
<Data Name="FileName">C:\ProgramData\Intel\SUR\QUEENCREEK\IntelData\temp\2017_01_28__15_57_17_boot.etl</Data> | |
<Data Name="ErrorCode">3221225864</Data> | |
<Data Name="LoggingMode">5</Data> |
</EventData>
</Event>
Log Name: | Microsoft-Windows-Kernel-EventTracing/Admin |
Source: | Microsoft-Windows-Kernel-EventTracing |
Date: | 2/4/2017 9:52:44 PM |
Event ID: | 4 |
Task Category: Logging
Level: | Warning |
Keywords: | Session |
User: | SYSTEM |
Computer: | WINDOWS-B686H5R |
Description:
The maximum file size for session "NT Kernel Logger" has been reached. As a result, events might be lost (not logged) to file "C:\ProgramData\Intel\SUR\QUEENCREEK\IntelData\temp\2017_01_28__15_57_17_boot.etl". The maximum files size is currently set to 104857600 bytes.
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>4</EventID> | |
<Version>0</Version> | |
<Level>3</Level> | |
<Task>1</Task> | |
<Opcode>10</Opcode> | |
<Keywords>0x8000000000000010</Keywords> | |
<TimeCreated SystemTime="2017-02-05T02:52:44.748453100Z" /> | |
<EventRecordID>170</EventRecordID> | |
<Correlation /> | |
<Execution ProcessID="4" ThreadID="188" /> | |
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel> | |
<Computer>WINDOWS-B686H5R</Computer> | |
<Security UserID="S-1-5-18" /> |
</System>
<EventData>
<Data Name="SessionName">NT Kernel Logger</Data> | |
<Data Name="FileName">C:\ProgramData\Intel\SUR\QUEENCREEK\IntelData\temp\2017_01_28__15_57_17_boot.etl</Data> | |
<Data Name="ErrorCode">3221225864</Data> | |
<Data Name="LoggingMode">5</Data> | |
<Data Name="MaxFileSize">104857600</Data> |
</EventData>
</Event>
_______________
As I said, I do NOT want Intel to ask me any questions - I have a normal Dell Optiplex with plenty of RAM, and this is Intel's fault.