Share via

Event 2 - Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000035

Peskycross 25 Reputation points
2025-10-05T20:42:58.12+00:00

RESOLVED: run steam as administrator and the issue does not happen, Apex runs better (it is still Apex legends)

keep gettting graphical & lag issues in game and when checking Event veiwer I keep getting this error:

Kernal event 2 -Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000035

Main game this seems to course errors with is Apex Legends, run from Steam. At randoms times my game play seems slow and I get reduced frame rates plus lag. It's like the whole game is running on a different system

Device specs:

Processor AMD Ryzen 9 5900X 12-Core Processor (3.70 GHz)

Installed RAM 32.0 GB

System type 64-bit operating system, x64-based processor

Storage: Gen 4 NVMe

Graphics Nvidia 3080

Edition Windows 11 Pro

Version 24H2

Installed on ‎31/‎08/‎2025

OS build 26100.6725

Experience Windows Feature Experience Pack 1000.26100.253.0

Steps taken to resolve:

  • I have tried a fresh install of Windows, SFC/ scannow, DISM.exe /Online /Cleanup-image /Restorehealth.
  • Tried disabling all none Windows services and rebooting.
  • Updating drivers or back dating drivers
  • Reinstalling Steam & Apex Legends
  • I've used monitoring software to check for heat related issues.
  • I've disabled XMP and enabled it.

I'm honestly at a total loss with this

Windows for home | Windows 11 | Gaming

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Francisco Montilla 17,440 Reputation points Independent Advisor
    2025-10-05T22:16:37.8633333+00:00

    Hello,

    You are seeing a Kernel-EventTracing ID 2 with 0xC0000035 because an ETW tracing session with that exact name is already present. Code 0xC0000035 maps to STATUS_OBJECT_NAME_COLLISION. In other words, Windows tried to start a trace session that already exists. It is usually benign, but if a game or driver keeps creating a duplicate session it can spam logs and sometimes coincide with hitching. Let's clean up the stale ETW session so it cannot collide again.

    First, close Apex and Steam. Open an elevated Command Prompt. Run this to see if the session is currently registered.

    logman query -ets | findstr /i dfa2c640-651d-488d-a479-2fd7a7ca6e29

    If you see a match, stop it, then delete its definition.

    logman stop "dfa2c640-651d-488d-a479-2fd7a7ca6e29" -ets
logman delete "dfa2c640-651d-488d-a479-2fd7a7ca6e29"

    Now restart Windows and play as normal. If the same Event 2 comes back with the very same GUID right after boot, it means something is auto-creating that session at startup. In that case, disable the autologger entry instead of deleting random drivers. Open an elevated Command Prompt and run the following. This simply flips the session startup flag to off and is reversible.

    reg query "HKLM\System\CurrentControlSet\Control\WMI\Autologger\dfa2c640-651d-488d-a479-2fd7a7ca6e29"
reg add "HKLM\System\CurrentControlSet\Control\WMI\Autologger\dfa2c640-651d-488d-a479-2fd7a7ca6e29" /v Start /t REG_DWORD /d 0 /f

    Reboot again and test. If you prefer to re-enable later, set Start to 1.

    A quick note for context: Players have reported this same GUID firing while gaming, so it is not unique to your PC. That supports the idea that a game component or overlay tries to start the same trace twice.

    If performance is still choppy after this cleanup, the Event 2 entry was likely a symptom, not the cause. Next step, I can walk you through a focused GPU and CPU trace with Windows Performance Recorder to pinpoint the bottleneck.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.