What lives on your gaming PC
Drivers, processes, and games on one machine, each explained in plain words.
What it is, and how to read itVera's own mark, made from the whole catalog. It changes as the guide grows. ac2d b8ac af2d
Every driver on a public risk list, explained simply.
What a game asks of your system, and why. The reader decides; we describe.
The real processes Vera observes running, classified by what each one does. Published only after it is seen on more than one machine.
A gaming PC quietly runs hundreds of things you never installed by name and never see: kernel drivers, background daemons, the anti-cheat that loads before the game does. The Field Guide gives every one of them a plate. Type a driver, a process, or a game and you get the plain story: what it is, who makes it, how deep into your system it reaches, and what the public record says about it. Plain enough to read without an engineering degree, deep enough to follow all the way down to the kernel. So the next time something you don't recognize asks for the keys to your machine, you are not guessing. You can look it up.
Longer reads that untangle one thing at a time. Plain words, public sources, no verdicts.
Why “not caught” can never mean “clean,” and what proves a fair game instead.
Read it Field noteWhat anti-cheat can and cannot seeThe cheat families, sorted by the one line where a record beats detection.
Read it Field noteLobby crashing, untangledOne phrase hides three problems, from a crash bug to a game taken offline. How to tell them apart.
Read it Field noteDoxxing, untangledFour words wear one fear. What each really is, and what actually keeps a person safe.
Read itI. Drivers come from a public risk list, the LOLDrivers project (refreshed July 10, 2026). II. Games are researched from each maker's own anti-cheat docs and named reporting. III. Processes come from what Vera actually sees running. No verdicts: what is here is public evidence, never an accusation about a person.