Solved: Error Code 0xC0000035 Kernel Event Tracing Issue on Windows

Solved: Error Code 0xC0000035 Kernel Event Tracing Issue on Windows

The “Error Code: 0XC0000035” Kernel Event Tracing message is a common warning found in Event Viewer on Windows 10 and Windows 11. Many users discover it while checking system logs after startup delays, performance issues, gaming crashes, or random system instability. Seeing repeated errors can be concerning, especially when the message references the Windows kernel.

In most cases, this issue is related to Event Tracing for Windows (ETW) sessions that fail to start properly because of duplicate sessions, corrupted logs, driver conflicts, or system misconfiguration. While it may look serious, it does not always mean your computer is damaged.

The good news is that this error is often fixable with several safe troubleshooting methods. In this guide, you’ll learn what causes Kernel Event Tracing error 0XC0000035 and how to resolve it.

What Does Error Code 0XC0000035 Mean?

This error typically appears when Windows tries to start a tracing session that already exists or cannot be initialized correctly.

Kernel Event Tracing is used by Windows to record performance and diagnostic data. If a session conflicts with another active trace or damaged log files, Event Viewer may record 0XC0000035.

Common associated messages include:

• Session already exists
• Failed to start tracing session
• Kernel Event Tracing warning
• Repeated Event Viewer errors after boot

Is This Error Dangerous?

Usually, no. Many systems run normally while logging this warning.

However, if it appears with symptoms such as:

• Slow boot times
• Freezing
• Driver crashes
• High CPU usage
• Random shutdowns

Then troubleshooting is recommended.

Common Causes of 0XC0000035 Kernel Event Tracing Error

Duplicate Trace Sessions

Windows or software tries to start an already-running trace session.

Corrupted Log Files

Damaged ETL or diagnostic logs can cause failures.

Outdated Drivers

Network, chipset, and storage drivers often contribute.

Third-Party Monitoring Tools

Performance utilities or RGB/control software may create conflicts.

System File Corruption

Damaged Windows components may affect tracing services.

How To Fix Error Code 0XC0000035 on Windows

Try the following methods in order.

Restart Your PC

A restart can clear temporary trace session conflicts.

Steps

1. Save your work
2. Restart Windows
3. Check if the warning returns later

Update Windows

Microsoft often fixes logging and kernel-related bugs.

Steps

1. Open Settings
2. Go to Windows Update
3. Click Check for updates
4. Install all available updates
5. Restart your PC

Run System File Checker

Repair damaged Windows files.

Steps

Open Command Prompt as administrator and run:

sfc /scannow

Wait for completion and restart.

Use DISM Repair Tool

If system corruption remains:

Steps

Run:

DISM /Online /Cleanup-Image /RestoreHealth

Restart afterward.

Clear Temporary Log Files

Corrupted logs may trigger repeated warnings.

Steps

1. Press Windows + R
2. Type:

%temp%

3. Delete temporary files where possible

Also run Disk Cleanup to remove system temp files.

Delete ETL Log Files Carefully

Event trace logs may become corrupted.

Common Folder

C:\Windows\System32\LogFiles\WMI

You may see .etl files. Restart first, then remove only non-essential logs if safe and if they are not in use.

Update Device Drivers

Old drivers often generate Event Viewer warnings.

Focus on Updating

• Chipset drivers
• Network adapter drivers
• Storage controller drivers
• Graphics drivers

Use manufacturer sources when possible.

Disable Fast Startup

Fast Startup sometimes causes repeated boot-time warnings.

Steps

1. Open Control Panel
2. Go to Power Options
3. Choose What the power buttons do
4. Click Change settings currently unavailable
5. Disable Turn on fast startup
6. Save changes

Restart and test.

Perform a Clean Boot

Third-party software may create tracing conflicts.

Steps

1. Press Windows + R
2. Type msconfig
3. Hide Microsoft services
4. Disable remaining services
5. Disable startup apps in Task Manager
6. Restart PC

If the warning disappears, another app is causing it.

Check Monitoring or RGB Utilities

Some utilities create tracing sessions.

Examples

• Hardware monitoring tools
• RGB lighting software
• Fan control apps
• Gaming overlays
• Performance tuners

Update or temporarily remove them for testing.

Use Performance Monitor to Check Data Collector Sets

Advanced users can inspect active traces.

Steps

1. Search Performance Monitor
2. Expand Data Collector Sets
3. Look for duplicate or failed sessions

Only disable entries if you understand their purpose.

Reset Network Stack

Some tracing errors are linked to networking.

Steps

Run:

netsh winsock reset
netsh int ip reset

Restart afterward.

Check Event Viewer for Related Errors

The 0XC0000035 warning may not be the real issue.

Look For

• Driver failures
• Disk errors
• Service crashes
• Network disconnects

Fixing the related issue may stop the tracing warning.

Run CHKDSK

Disk problems may corrupt logs.

Steps

Open Command Prompt as administrator:

chkdsk /f

You may need to restart.

Create a New User Profile

If the warning happens only on one account:

Steps

1. Open Settings
2. Go to Accounts
3. Add a new user
4. Test behavior there

When to Ignore the Warning

If:

• PC runs normally
• No crashes occur
• Performance is stable
• Only Event Viewer shows the warning occasionally

Then it may be harmless and not urgent.

Tips to Prevent Future Kernel Event Tracing Errors

To reduce future warnings:

• Keep Windows updated
• Update drivers regularly
• Avoid too many monitoring tools
• Restart PC periodically
• Maintain healthy storage drives
• Remove unused startup utilities

When to Seek Advanced Help

Consider further support if:

• Error appears hundreds of times daily
• System freezes or blue screens occur
• Boot times become extremely slow
• Disk or hardware issues are suspected

Final Thoughts

The 0XC0000035 Kernel Event Tracing error on Windows usually relates to duplicate tracing sessions, corrupted logs, outdated drivers, or software conflicts. While the message may look alarming, it is often a warning rather than a critical failure.

By updating Windows, repairing system files, clearing logs, updating drivers, and disabling conflicting software, most users can reduce or eliminate the error.

Related articles

Fix Outlook Password Prompt Issue in Office 365

How to Fix Mobile Hotspot Not Working in Windows 10

Solved: MySQL Shutdown Unexpectedly Issue in MySQL