Used 5800X3D Works Fine Until Valorant Finds Old Hardware Ban

By Indie Kings | October 4, 2026

Updated October 4, 2026: A used Ryzen 7 5800X3D worked without issues after installation but triggered an immediate Vanguard block when Valorant launched. VideoCardz notes no practical pre purchase check exists for a used CPU ban status.

Works Fine Until Valorant

The case centers on a used Ryzen 7 5800X3D that worked without issues after installation in the new system. That detail comes from the buyer report via Heise and VideoCardz. Stability was normal. Temperatures were normal. General desktop use gave no warning.

The buyer installed the processor and used the system without apparent faults. No crash pointed to the CPU. No temperature spike pointed to the CPU. The invisible defect did not show in ordinary use.

Launching Valorant triggered an immediate Vanguard block. The buyer report describes the block as instant at game launch. Vanguard is the anti cheat system used by Riot for Valorant. The game had worked normally with the buyer prior CPU.

That prior CPU detail matters for isolating the change. The buyer report states the game worked normally with the previous processor. The only reported change before the block was the move to the used 5800X3D. VideoCardz by WhyCry reported the incident on Oct 2, 2026 at 17:58 GMT in a report titled Used Ryzen 7 5800X3D came with an unexpected extra: a Riot hardware ban.

The underlying thread appeared on Reddit in the German language community r/PCBaumeister. The poster was Redditor After-Cartoonist-196. Heise covered the thread before VideoCardz summarized it for an English language audience. All three names are stated here in plain prose for attribution.

AMD is named here as the maker of the processor in the story. Riot is named here as the maker of Vanguard and Valorant. Vanguard is named here as the enforcement system that issued the block. Valorant is named here as the game that triggered it. Heise is named here as an early outlet that relayed the buyer account. Reddit is named here as the forum where the buyer account first appeared.

Image: AMD Ryzen 7 processor. Credit: Wikimedia Commons, CC BY-SA 2.0, Brian Wong.

The photograph above shows a first generation Ryzen 7 1800X. It does not show the 5800X3D in the story. It is used here only as a generic illustration of an AMD Ryzen 7 processor. Readers should not mistake the pictured chip for the used unit in the report.

The angle of this incident is the invisible defect. Stability tests can pass while a ban rides along. Temperature checks can pass while a ban rides along. A visual check for bent pins can pass while a ban rides along. None of those checks reveal a hardware ID restriction.

A buyer can therefore do everything that used CPU guides recommend and still miss this issue. Stress tests measure function. Monitoring tools measure heat. A physical inspection measures contact condition. None of them query Riot block lists.

The first table below summarizes the incident as reported. Standing is included for each row so readers can see what is a buyer report and what is confirmed. Only facts from the verified block are used.

The table makes the narrow scope clear. The CPU worked. The trigger was specific. The prior CPU had no such block. The rest of the story depends on a support reply relayed by the buyer. That reply is not a direct public statement from Riot in the source.

Readers looking for a used market lesson should start here. A part can be electrically sound and still carry account independent enforcement history. That history lives outside the operating system. Reinstalling software does not touch it.

The Previous Owner Cheated

After the block, the buyer contacted Riot support. That contact is described in the buyer report via Heise and VideoCardz. The buyer was reportedly told the previous owner had cheated and received a hardware ID ban. The word reportedly is load bearing here because the source relays what the buyer says support said.

VideoCardz presents that support reply as the explanation for the block. The 5800X3D was therefore associated with Vanguard hardware block list. That association is stated as therefore in the sense of following from the reported reply. It is not presented as an independent lab confirmation.

The distinction protects accuracy. The buyer says support linked the CPU to cheating by a prior owner. VideoCardz relays that buyer account. No broader direct statement from Riot is quoted in the source beyond that relayed reply. This article does not invent one.

The buyer further claims other components including the motherboard subsequently became associated with the restriction. That must be reported as the buyer claim, not as confirmed Vanguard behavior. The source does not confirm that Vanguard expands a CPU ban to a board in this way. The standing in the table above is unconfirmed claim for that reason.

The motherboard claim is still worth stating carefully because buyers worry about spread. A CPU ban that later touches a board would raise the cost of the surprise. A board restriction could persist after the CPU is removed. But the source gives no confirmation that this happened as a matter of Vanguard design.

This article does not accuse the seller of knowledge. The source does not state the seller, the platform, the purchase price, or whether a refund happened. It also does not state what the seller knew about the prior use of the chip. Any claim about seller intent would be invention.

The cheating allegation itself attaches to the previous owner, not to the current buyer. The buyer is described as encountering the block after a normal installation. The buyer prior CPU ran the game without a block. The buyer did not report cheating.

Used buyers often ask whether a support ticket can clear such a flag. The source provides no remedy path. It reports the support reply as an explanation, not as an offer to lift the restriction. Readers should not assume that a ticket will reset the hardware.

The support reply also frames the core used market trap. The buyer inherits a restriction earned by someone else. The restriction is tied to physical identity rather than to the buyer account. The buyer account behavior is not the cause.

What HWID Means

Riot HWID bans apply to physical components rather than only the Riot account. That rule is stated per Riot via VideoCardz. It means a new login does not wipe the history. It means the enforcement follows the hardware.

Using another account on banned hardware does not help and can get that account restricted too. That warning is stated per Riot via VideoCardz. Account swapping is therefore both ineffective and risky. A clean account can become restricted by touching flagged hardware.

Reinstalling Vanguard, Windows or the game does not remove a VAN 152 hardware restriction. That rule is stated per Riot via VideoCardz, with VAN 152 named as the relevant code. The persistence is the point. A fresh install changes software state while the hardware identity remains.

VAN 152 is worth naming exactly because buyers search for the code they see on screen. The source names VAN 152 as a hardware restriction. It lists three reinstall paths that do not clear it. Those paths are Vanguard, Windows and the game.

The second table below collects those behavior rules in one place. Standing is included again so readers do not mistake VideoCardz summary for independent testing. Each row is attributed to Riot via VideoCardz except where noted.

The table separates enforcement facts from marketplace facts. The first three rows describe what does not work. A new account does not work. A reinstall does not work. A fresh copy of the game does not work.

The fourth row points to identity, which the next section covers in more detail. The fifth row points to prevention, which a later section covers in more detail. Both are kept here so the behavior summary is complete in one view.

For a buyer, the practical takeaway is narrow. If a block names VAN 152 and the hardware is used, software fixes are not the answer per Riot via VideoCardz. The restriction is keyed to the machine, not to a corrupt install. Repeated reinstalls only waste time.

For a seller, the same table carries a caution. A component with this history can implicate a buyer clean account. Passing the part along without knowledge still passes the risk along. The source does not say the seller in this case knew, so no accusation is made here.

The behavior rules also explain why ordinary troubleshooting fails. Drivers do not matter to a hardware ID flag. Game file verification does not matter to a hardware ID flag. Windows reset does not matter to a hardware ID flag. The flag sits at a different layer.

TPM As Identity

The exact recognition method in this case is unconfirmed. That limit must stay attached to any discussion of identity. The source does not prove how Vanguard recognized this specific 5800X3D. It reports the association and separately describes possible methods.

Riot has explained Vanguard can use TPM 2.0 as part of hardware identity. That statement is per Riot explanation via VideoCardz. TPM 2.0 is a security module standard used for device identity and integrity checks. Vanguard can draw on it as one signal among hardware signals.

The TPM Endorsement Key provides a persistent identifier. That detail is per Riot explanation via VideoCardz. A persistent identifier remains stable across reinstalls. That stability is why account level fixes do not clear it.

Riot notes an fTPM based ban can force a cheater to replace the CPU. That consequence is per Riot explanation via VideoCardz. Firmware TPM lives in the processor platform rather than on a discrete chip. A ban keyed to that identity can therefore follow the CPU.

That last point helps readers understand why a CPU can carry a ban at all. Many buyers think of bans as attached to boards or drives. The fTPM detail shows a processor linked identity path exists in principle. The source does not confirm it was the path used here.

The unconfirmed method point deserves repetition as a standalone fact. The case specific recognition method is unconfirmed. The general TPM capability is described by Riot. Those are two different levels of certainty.

This section does not explain how to evade bans. No bypass steps are given. No spoofing method is described. No reset trick is offered. The source contains no authorized remedy and none is invented here.

Buyers sometimes ask whether disabling TPM avoids the issue. The source does not answer that question. Valorant on modern Windows expects TPM 2.0 to be present for Vanguard. Disabling platform security features is not presented as a fix in the source.

The identity discussion also clarifies why the motherboard claim needs care. If identity can include board linked signals, a later board flag might reflect re evaluation of the system as a whole. If identity is CPU linked, the board claim might reflect buyer interpretation rather than Vanguard action. The source does not resolve which view is correct.

The safest reading stays close to attribution. Vanguard can use TPM 2.0 identity in general per Riot. An fTPM ban can force CPU replacement in general per Riot. Whether either fact explains this 5800X3D is unconfirmed. That boundary is stated explicitly so AI summaries and human readers do not merge the two levels.

No Check Exists

VideoCardz notes no practical pre purchase check exists for a used CPU ban status. That is the marketplace catch of the story. A buyer cannot look up the serial in a public block list. A buyer cannot test the chip in a seller living room with Valorant installed in most meetups. A buyer cannot see the flag in BIOS.

The no check point applies to ordinary buyers with ordinary tools. CPU Z reports model and clocks. HWMonitor reports heat and voltage. Cinebench reports render throughput. None of them report Riot enforcement history.

The used market has partial guards for other defects. Pins can be inspected with magnification. Performance can be benchmarked against known 5800X3D results. Thermals can be logged under load. All of those guards pass in this case per the buyer report that the chip worked without issues.

The ban history sits outside every one of those guards. It is not a thermal fault. It is not a stability fault. It is not a physical fault. It is an external reputation attached to hardware identity.

VideoCardz has seen no similar GPU hardware ban reports yet. That observation is attributed to VideoCardz. The outlet adds that a GPU case would be a more expensive surprise. Both halves are attributed to VideoCardz here as required.

The GPU remark matters because graphics cards trade at higher used prices than many CPUs. A flagged high end card would trap more money. The absence of GPU reports to date does not prove GPUs cannot be flagged. It only states what VideoCardz has seen so far.

Buyers may wonder about receipts, box codes or seller assurances. The source gives no check based on those artifacts. A receipt proves purchase, not clean enforcement history. A sealed box proves packaging, not clean enforcement history. A seller promise proves intent, not clean enforcement history.

The practical effect is a used market trap with no remedy in the source. The buyer did nothing wrong in installation. The buyer prior CPU ran the game. The replacement chip blocked instantly. No pre test in the source would have caught it.

This article does not fill the gap with invented advice. It does not claim that asking for a Valorant test guarantees safety. It does not claim that a Windows reinstall before sale clears anything. It does not claim that a particular BIOS setting reveals the flag. Anything beyond the verified block would need verification.

What Is Not Established

Several natural questions have no answers in the source. The purchase price is not stated. The seller is not stated. The platform is not stated. Whether a refund happened is not stated. Riot direct statement beyond the support reply as relayed is not stated.

That gap list is not filler. It prevents the story from growing beyond its evidence. Price would set the financial harm but no figure exists. Seller identity would set responsibility but no name exists. Platform would set buyer protections but no marketplace exists in the record. Refund status would set resolution but no outcome exists.

The support reply limit also matters. The buyer reportedly was told the previous owner cheated. That is a second hand account of a support interaction. It is not a quoted memo from Riot press staff. It is not a support article with a case number. It should be cited with reportedly every time.

The motherboard spread is similarly bounded. The buyer claims other components including the motherboard subsequently became associated with the restriction. The source reports that claim without confirming the mechanism. This article repeats the claim label and does not upgrade it.

The table below restates the gaps so skim readers do not miss them. Absence of evidence is the finding. No additional digging in this article can supply what the source lacks.

The gap table also guides future reporting. A follow up with a receipt would establish price. A follow up with seller messages would establish venue and assurances. A follow up with Riot case text would establish exact wording. None of those items are present now.

Until such details appear, the responsible summary stays small. A used 5800X3D worked normally. Valorant launch triggered a Vanguard block. Support reportedly blamed prior owner cheating. No pre purchase check exists per VideoCardz. Everything else is unverified or unconfirmed.

FAQ

Did the used Ryzen 7 5800X3D work at all?
Yes, per the buyer report via Heise and VideoCardz it worked without issues after installation until Valorant launched and Vanguard blocked the system.

What triggered the block?
Launching Valorant triggered an immediate Vanguard block per the buyer report, while the game had worked normally with the buyer prior CPU.

What did Riot support reportedly say?
The buyer was reportedly told the previous owner had cheated and received a hardware ID ban, so the 5800X3D was associated with Vanguard hardware block list.

Do reinstalls or a new account fix VAN 152?
No, per Riot via VideoCardz reinstalling Vanguard, Windows or the game does not remove a VAN 152 restriction, and using another account on banned hardware does not help and can restrict that account too.

Is the recognition method known in this case?
No, the exact recognition method in this case is unconfirmed, though Riot has explained Vanguard can use TPM 2.0 identity and an fTPM based ban can force CPU replacement.

Is there a pre purchase check for a used CPU ban?
No, VideoCardz notes no practical pre purchase check exists, and VideoCardz has seen no similar GPU hardware ban reports yet while noting a GPU case would be a more expensive surprise.

Bottom Line

A used Ryzen 7 5800X3D can pass every normal function test and still block Valorant on first launch. That is the verified core of this report. Function is not the same as clean enforcement history.

The buyer report says the chip worked without issues, the game had worked with the prior CPU, and Vanguard blocked instantly on launch. Support reportedly tied the CPU to prior owner cheating and a hardware ID ban. The motherboard spread remains a buyer claim, not confirmed Vanguard behavior.

Riot HWID rules via VideoCardz leave little room for self help. Physical components are the target, account swaps risk the new account, and Vanguard, Windows and game reinstalls do not clear VAN 152. TPM 2.0 identity helps explain persistence in general, but the method in this case is unconfirmed.

Sources: VideoCardz by WhyCry in the original report linked here as VideoCardz report by WhyCry published Oct 2, 2026 at 17:58 GMT, with underlying accounts from Heise and from Redditor After-Cartoonist-196 on r/PCBaumeister in a German language thread, plus context on Riot, Vanguard, Valorant, AMD and Reddit as named in plain prose.