This Used CPU Came With a Val Ban Attached

Nah. A CPU cannot ban you. That is the claim doing laps since yesterday though, and it got loud enough that Riot stepped in and said the story does not hold up the way it was told. A player says they bought a secondhand processor and inherited the previous owner's cheating ban. Riot disputes parts of it. Both halves of that sentence matter, and only one of them is getting attention.

What Actually Happened

The short version: a Val player says they picked up a used CPU, built the rig, launched the game, and ran straight into a ban that was never theirs. The claim is that the hardware carried the old owner's punishment across to a completely new account. It spread off a Dexerto writeup yesterday, and you know how this goes. Screenshot, caption, thirty thousand people furious before lunch.

Then Riot replied. Not with a shrug, either. Riot disputes parts of the story, which in corporate speak means the timeline or the details do not match what their side shows. That is a careful sentence and it was chosen carefully. Notice what it is not, though, because it is not a blanket denial that hardware matters at all.

And that is where this gets thin. The reporting does not hand us the full technical trail, the account history, or whatever Riot is looking at internally. We have a player's version and a publisher's rebuttal. Everything else is the comment section inventing physics. I mean, half the replies were explaining kernel drivers to each other with total confidence and zero evidence.

Look, the reason this story travels is not the CPU. It is that everyone reading it has bought a used part at some point. Marketplace GPU, hand-me-down motherboard, the whole PC your cousin stopped using. The idea that a stranger's history rides along inside your machine is genuinely unsettling, true or not.

Why This One Hits Different

Hardware bans are the strongest tool a kernel-level anti-cheat has. Account bans are a joke to a determined cheater because accounts are free and smurfs are a weekend hobby. Tying the punishment to the machine is the only thing that actually costs money. That is the entire point, and it works.

But the secondhand market is enormous, right? Parts get resold, rebuilt, flipped and bundled constantly. If a ban really can travel with a component, then every used-parts buyer is rolling dice, and Riot owes everyone a way to check. If it cannot, Riot still has a communication problem, because clearly nobody believes the answer.

Here is where it gets interesting: the real grievance in the thread was never the physics. It was the appeal. Ban appeals in this game are a black box, and when a player gets a one-line response to a decision that kills their whole account, they go public. That is not entitlement, that is the only lever they have left.

There is an upside nobody wants to say out loud. Bans that stick mean fewer repeat offenders queueing into your games with a fresh account and the same cheat loaded. I will take sticky bans over a revolving door every single time. Even when the sticky part occasionally bites somebody who did not deserve it, which is the uncomfortable bit.

Real Talk: What It Means for Your Climb

Practical stuff first. A clean Windows install does not reset your identity to the anti-cheat, and anyone telling you it does is selling something. Your account is one signal among several. So if you buy used, buy with a receipt and a seller you can actually contact, because that paper trail is the only thing that makes an appeal readable.

Pro teams treat this like boring admin, and that is exactly the habit to steal. One player, one account, one machine, nobody else logs in, ever. No letting your mate run your placements because he is better at the role. No borrowed rig for a tournament without telling the org. It is unglamorous and it is why their accounts never get surprise-flagged.

The climb part is simpler than people pretend. Your rank is only yours if nobody else has touched the account, and most of the rank anxiety in this community comes from games you did not actually control. You cannot buy pro game sense, but you also do not have to keep coinflipping teammates to find your real ceiling. If solo queue is the thing breaking you, a Val boost exists for exactly that.

Then do the boring work. Same sens across every session, same crosshair, same refresh rate, no fiddling with settings after a loss. Ten minutes of pure crosshair placement and counter-strafing before you queue, not a deathmatch you leave halfway through. Consistency is a mechanic. It just does not feel like one.

The Verdict

My honest read? The technical claim is probably wrong and Riot is probably right on the details. Bans do not jump between accounts through a chunk of silicon on a whim, and the simplest explanation for most of these stories is boring. Someone bought more than a CPU, or someone is not telling the full version. Happens constantly.

And Riot still comes out of this looking bad, which is the part that should sting over there. You cannot run the most invasive anti-cheat in the genre and then handle the fallout with one careful paragraph. If your enforcement is strong enough to kill hardware, your explanation has to be strong enough to survive Reddit. Right now it is not.

I will die on this hill anyway: kernel anti-cheat is worth it. I said this months back during the last ban-wave discourse and I will say it again. I would rather accept a small risk of a bad flag than go back to lobbies where every third smurf is obviously spinning. The tradeoff is real and it is still the right trade.

What would actually fix it is so cheap it is embarrassing. A public page that explains what a hardware flag is, a form for used-hardware buyers with proof of purchase, and a response longer than a sentence. That is a weekend of work for a company this size. The silence is a choice.

So, prediction: within two weeks another used-hardware ban thread goes viral in exactly the same shape, and Riot's reply will be one careful paragraph again. No transfer process, no public appeal page, no technical breakdown. Screenshot the thread when it lands and tell me I was wrong.