Circular Kernel Context Logger" failed to start with the following

[odaatom1]

Circular Kernel Context Logger" failed to start with the following

I am sure someone has had this error , it is related to a driver I believe. Can not get it to go away. Any suggestions?


Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 11/7/2010 4:33:49 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: tom-home
Description:
Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035
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>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2010-11-07T22:33:49.004882800Z" />
<EventRecordID>80</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="64" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>tom-home</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Circular Kernel Context Logger</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225525</Data>
<Data Name="LoggingMode">268436608</Data>
</EventData>
</Event>

 

[zigzag3143]

I am sure someone has had this error , it is related to a driver I believe. Can not get it to go away. Any suggestions?


Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 11/7/2010 4:33:49 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: tom-home
Description:
Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035
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>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2010-11-07T22:33:49.004882800Z" />
<EventRecordID>80</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="64" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>tom-home</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Circular Kernel Context Logger</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225525</Data>
<Data Name="LoggingMode">268436608</Data>
</EventData>
</Event>

There are way too many reasons for event ID 2. when does it happen what are the symptoms,etc

 

[odaatom1]

This is happening after the pc is idle for a while and goes into screen saver and sleep modes. It is just an error, I am not experiencing any other issues. I just want to know why it is giving the error.

 

[stormy13]

IPv6, Homegroup, printer driver, shared or not shared printer; seen lots of suggestions but have never seen a definite solution. This is just a few previous threads about this one on this forum,

http://www.sevenforums.com/installation-setup/62762-kernel-event-tracing-error-0xc0000035.html

http://www.sevenforums.com/general-discussion/2189-event-viewer-errors.html

http://www.sevenforums.com/crashes-debugging/96186-constant-errors-event-viewer.html

http://www.sevenforums.com/network-sharing/58645-delayed-network-connection-issue.html

I get this one too and got tired of seeing it and never really finding a solution so I just disabled that log in Event Viewer, that and it was the only error coming from that particular log so it may well still be happening but I don't have to see it any time I look there.

 

[odaatom1]

Thanks

I have read a lot of threads related to this also and have not heard any solutions. I did read one where an MS moderator said to just ignore it. But , I really want to find the cause. I have updated the Network card drivers and disabled IPV6 in the network protocols list as well, and still got the same error. I just noticed that there is a setting in the network card properties, under device manager, to "allow the computer to turn off this device to save power" I have unchecked this option and when the computer went into power save mode and woke up I did not get the error again. This is what I believe to be the cause, power management. SO, I will see if this is the cure or not and let you know..thanks all for your input.

 

[odaatom1]

Humm-baffled

Well, this is happening again. But, only when you log off and the PC goes to sleep, and then upon waking and login it produces the same error.

Baffled!

 

[Cato]

If you are running Microsoft Security Essentials, this MAY help. I was getting the same error along with an error telling me that MSSEOOBE had stopped running.

If you go to:

C:\ProgramData\Microsoft\Microsoft Security Essentials\Support\MSSEOOBE.etl and delete MSSEOOBE.etl (or better yet, rename it to MSSEOOBE.old) then reboot the MSSOOBE file will rebuild itself. After doing this I've gotten neither the Circular Kernel Context Logger error or the MSSEOOBE error.

I honestly don't know how they could be connected, or if they are. All I know is that it worked for me. I did it mainly because of the MSSEOOBE errors I was getting, but it stopped the other one, too.

I have seen it said that in the event of a hard shutdown, or BSOD, that the MSSEOOBE file would be corrupted again and it would be necessary to repeat the above.

I hope this helps. It did for me, but it would take someone smarter than me to have the answer why.

 

[odaatom1]

no security essentials

I am not running Security essentials, so I don't think it has anything to do with that. I am starting to think it is a permissions issue, something to do with power management.

Thanks

 

[frozenreads]

Did you ever get to the bottom of this error? I am experiencing the same thing, it sometimes happens when I log off and log back into my user account, but not always. The error does not appear to be anything serious but I am just curious as to what causes it