Anti-cheats are not perfect. Sometimes they flag software that has nothing to do with cheating — a frustrating outcome known as a false positive.
Why false positives happen
An anti-cheat watches for software that reads or modifies the game's memory, injects code, or behaves like a known cheat. The problem is that legitimate software sometimes does similar things. An overlay draws on top of the game; a macro tool sends input; a monitoring utility reads memory. To an anti-cheat, the technique can look the same whether the intent is innocent or not.
Common culprits
The usual suspects are overlays and capture tools, hardware-monitoring utilities, input-macro software, and certain memory or debugging tools. Driver conflicts cause trouble too — an outdated or unusual driver can behave in ways an anti-cheat does not expect. None of these are cheats, but any can draw attention.
How to reduce the risk
A few habits help. Close overlays and monitoring tools you do not need while playing. Keep graphics and chipset drivers current. Avoid running memory editors or debugging tools alongside an online game, even for unrelated reasons. The goal is simply to not look like a cheater to an automated system.
If you are flagged anyway
If you believe you were wrongly flagged, the route is an honest appeal: open a support ticket, describe your setup plainly, and name the software that was running. That context is exactly what a reviewer needs to recognise a false positive.
The takeaway
A false positive is the anti-cheat seeing a suspicious technique without seeing intent. You cannot control its judgement, but you can reduce the risk — run a clean game session, keep drivers updated, and if it happens anyway, appeal honestly and specifically.