Overview
The Kernel EventTracing Event ID 2, with the error code STATUS_OBJECT_NAME_COLLISION (0xC0000035), indicates a conflict between identical domain security identifiers (SIDs) detected by the event logger. This error occurs when the “Circular Kernel Context Logger” fails to start due to the event logger being full.
Causes
The error can be triggered by various factors, including:
- Failure of certain processes to start, such as PerfDiag Logger, NetCfgTrace, Microsoft.Windows.Remediation, or sensorframework.
- Network-related issues.
- Third-party antivirus software.
- Outdated Intel or other network drivers.
Solutions
To resolve the error, multiple approaches can be taken:
1. Modify Autologg Registry Key
- Navigate to the following registry key:
Copy
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}
- Set the Enabled and EnableProperly values to 0.
2. Disable or Remove Third-Party Antivirus
- Disable or uninstall your third-party antivirus software.
3. Update Network Drivers
- Check for and install any available updates for Intel or other network drivers.
4. Run Network Reset
- Reset your network settings to restore default configurations.
5. Run DISM Scan
- Use the Deployment Imaging and Servicing Management (DISM) tool to repair the system image.
Additional Considerations
- If the error does not cause any noticeable issues, consider preventing its appearance by modifying the Autologg registry key as described in Solution 1.
- The error may also be associated with a “Kernel power critical error.” To resolve this, disable Fast startup and run the CHSDSK tool.
- Ensure that your power supply unit (PSU) is functioning correctly.
FAQ
What is Kernel EventTracing Event ID 2?
Kernel EventTracing Event ID 2 is an error code (STATUS_OBJECT_NAME_COLLISION, 0xC0000035) that indicates a conflict between identical domain security identifiers (SIDs) detected by the event logger.
What causes Kernel EventTracing Event ID 2?
The error can be caused by various factors, including:
* Failure of certain processes to start
* Network-related issues
* Third-party antivirus software
* Outdated network drivers
How can I resolve Kernel EventTracing Event ID 2?
To resolve the error, try the following solutions:
* Modify the Autologg registry key
* Disable or remove third-party antivirus software
* Update network drivers
* Run Network Reset
* Run DISM scan
Can Kernel EventTracing Event ID 2 be prevented?
If the error does not cause any noticeable issues, consider preventing its appearance by modifying the Autologg registry key.
What is the relationship between Kernel EventTracing Event ID 2 and “Kernel power critical error”?
The error may also be associated with a “Kernel power critical error.” To resolve this, disable Fast startup and run the CHSDSK tool.
What should I do if I suspect a hardware issue related to Kernel EventTracing Event ID 2?
Ensure that your power supply unit (PSU) is functioning correctly.
