Event trace session components

C

calamity852

New Member
Messages
5
Reaction score
1
what component or setting fully eliminates "data collector set > event trace session?" I'm looking to prevent FACEIT anti-cheat from creating traces of "Circular Kernel Context Logger" upon launching supported titles.
 
Removing ETW kills off the event trace logging facility. But I seriously doubt this type of futzing will defeat more advanced anti-cheat's.

Circular loggers are normal for most event logging, it prevents a chatty log from getting swamped by allocating a fixed buffer size, and allowing more recent events to overwrite the oldest ones. Otherwise a full log buffer will negatively impact the system, because it has to wait until the pending log events are flushed to disk before allowing new events (or actions).

You breaking another kernel process' expected behavior would likely cause the anti-cheat to flag you as cheating...
 
garlin said:
Removing ETW kills off the event trace logging facility. But I seriously doubt this type of futzing will defeat more advanced anti-cheat's.

Circular loggers are normal for most event logging, it prevents a chatty log from getting swamped by allocating a fixed buffer size, and allowing more recent events to overwrite the oldest ones. Otherwise a full log buffer will negatively impact the system, because it has to wait until the pending log events are flushed to disk before allowing new events (or actions).

You breaking another kernel process' expected behavior would likely cause the anti-cheat to flag you as cheating...
Click to expand...
Oops, didn't mean to come off like that.

My Intent is minimizing unnecessary logging for the anti-cheat to retrieve lost performance from potential overhead. The idea is "I got nothing to hide despite having extra unused device logs. No need to check those as I will never activate/use them in any situation." I've been manually disabling each launch without issues for over half a year.

As for the possible solution, seems like it's no longer creating itself after denying ownership for this kernel logger's GUID.
 
You must log in or register to reply here.
Back
Top