- The session circular kernel context logger failed to start with the following error: 0xc0000035 message is a very common appearance.
- To find out the details about how this error can be solved, scroll down, and read on.
- Acquaint yourself with more useful software fixes by exploring our thorough Software Hub.
- To see how to fix other software and problems, we recommend our Troubleshooting Tech Issues section.
The session circular kernel context logger failed to start with the following error: 0xc0000035is a ghost that has haunted the last three major releases of Windows. It’s an error that Windows 10 essentially inherited from Windows 7.
While it occurs less frequently on Windows 10, it still shows up to cause a blue screen of death from time to time. But why and how can you fix it? In this guide, we’ll answer these questions and more.
How do I fix a session circular kernel context logger error?
What is a session circular kernel context logger error: 0xc0000035?
In most cases, the context logger error: 0xc0000035 is caused by the system detecting a duplicate domain security identifier (SID). That’s why it seems to be more prevalent in computers hooked up to a local area network.
In most cases, this error isn’t fatal and won’t impact the way your computer runs. However, on some rare occasions, y0ur computer may crash, run sluggishly or its output devices may not be able to function properly.
You can find the error in Windows Event Viewer.
How to find session circular kernel context logger error: 0xc0000035 message?
Identify the location:
- Right-click on the Windows Start icon.
- Select Event Viewer from the menu.
- On the left panel, expand the Custom Views branch and click on Administrative Events.
- Sort the list according to Event ID.
- Look through every error with the Event ID of 2 till you find the latest 0xc0000035 error message.
To fix this issue:
1. Reboot your computer completely
2. Delete the MSSEOOBE.etl file
- Navigate to the ProgramData folder in your local (C:) drive.
- Click on Microsoft and then Microsoft Security Essentials.
- Click on Support.
- Delete the MSSEOOBE.etl file.
- Reboot your computer.
Note: This solution only works for users running Microsoft Security Essentials.
3. Enable the Superfetch/SysMain service
- Open the Run dialog (Win + R).
- Type services.msc into the open field and press Enter.
- Sort the values according to name.
- Look for a service labeled Superfetch or SysMain.
- Double-click on it to open its properties.
- Make sure that it’s running according to the Service status. If not, click on the Start button to see if it produces any error messages.
- Set the Startup type to Automatic.
- Click on OK.
- Restart your PC.
Don’t be alarmed. In later versions of Windows 10, the Superfetch service is named SysMain. They virtually do the same thing.
4. Adjust the maximum file size of the startup event trace sessions
- Open the Windows Run Dialog.
- Type perfmon into the open text field and press enter.
- Expand Data Collector Sets from the left tree.
- Click on Startup Even Trace Sessions.
- In the main panel, scroll down till you find the ReadyBoot entry and then double click on it.
- Click on the Stop Condition tab.
- Set maximum size to 40MB (or more).
- Click on OK and close the Performance Monitor.
The session circular kernel context logger failed to start with the following error: 0xc0000035 message may be appearing because the maximum file size of the Startup Event Trace Sessions isn’t enough. You can use this solution to fix it.
5. Disable IPv6
- Open the Windows Run Dialog (Win + R).
- Type in Control Panel and then hit Enter.
- On the left panel, click on Change adapter settings.
- Right-click on the first connection you see and click on Properties.
- Under the this connection uses the following items panel, find Internet Protocol Version 6 (TCP/IPV6) and uncheck it.
- Click on OK.
- Follow steps 4-6 for the rest of the connections in the list.
6. Update your network drivers
- Right-click on the Start Menu to open the Windows Power Menu.
- Select Device Manager.
- Right-click on your main LAN device and select Update driver from the context menu.
- Click on Search automatically for updated driver software.
- Confirm any prompts from Windows.
- Close the window.
- Restart your PC.
If none of the solutions in this guide worked for you, then your only other option is to reinstall or upgrade Windows if you’re using an older version.
However, if this error persists but doesn’t impact the way your system runs, then it’s okay to ignore it.
So which solution worked for you? Would you like to point out a blind spot on our side?
Please don’t hesitate to leave a comment down below. As always, thank you for reading.