How it works
DMA Cheats: The Hardware Setup, Why Detection Is Harder, and Who It Suits
DMA is not a build, it is a rig. Nothing foreign runs on the gaming PC because the cheat lives on a second machine and reads memory through an expansion card.
DMA stands for Direct Memory Access — the ability of a PCIe device to reach system RAM without going through the CPU. The technology itself is entirely ordinary: network cards, storage controllers and capture devices all use it. In the cheating context it gets repurposed. A card sits in the gaming PC and reads the game’s memory; a second computer processes that data and draws the picture.
The difference from an ordinary external cheat is structural: no foreign process runs on the gaming machine, no third-party driver is loaded, no handle is opened to the game. An anti-cheat observing the system from the inside has, quite literally, nothing local to observe.
What the rig consists of
| Component | Purpose | Notes |
|---|---|---|
| DMA card (FPGA) | reads the gaming PC’s memory | installs in a PCIe or M.2 slot on the gaming machine |
| Second computer | runs the cheat | a weak one is fine; it displays rather than computes |
| Link cable | data channel between machines | type depends on the card |
| Input device (KMBox and similar) | emulates a mouse as a physical HID device | needed only if you want aim assistance |
| Monitor or capture card | lets you see the game on the second PC | either a second display or HDMI capture |
Hence the first honest conclusion: DMA is a bench build, not a software purchase. The software is the cheapest and simplest part of the whole arrangement.
Why client-side detection is harder
- Nothing executes on the observed machine. Memory scanners, process integrity checks, module and handle enumeration find nothing because there is nothing to find.
- Input looks physical. A dedicated input device presents itself as a real mouse, so there is no software emulation to spot.
- The overlay is not drawn over the game. It lives on a second screen, out of reach of screen capture and of anti-cheat screenshots — see the streamproof guide.
Why detection still happens
Product pages rarely cover this part, and it is the part worth planning around.
- The card is visible on the bus. Every PCIe device exposes configuration space: vendor and device identifiers, class code, BAR sizes. A kernel-level anti-cheat can enumerate devices and compare them against what consumer hardware normally looks like.
- Access patterns. Bulk sequential reads of the memory regions that hold game entities do not look like the way the game itself touches that memory.
- Input analysis. Even movement delivered through a physical device has statistics — trajectories, acceleration curves, reaction latency. Server-side analytics work on that regardless of how the signal entered the system.
- Decisions. Radar knowledge shows in behaviour: pre-aiming, impossible awareness, rotations that make no sense without information. This is the oldest detection method and it is entirely hardware-agnostic.
So: DMA meaningfully reduces client-side detection and barely affects server-side analytics or player reports. “DMA cannot be detected” is false. “DMA shifts the risk from the client to your behaviour” is accurate.
Who it makes sense for
- Players who invest heavy hours in one title with an expensive account — Escape from Tarkov, PUBG, Arena Breakout Infinite, DayZ — and prefer one large outlay to losing accounts repeatedly.
- Players who specifically want the information layer: radar, loot, positions. In Rust and tactical shooters that is the valuable part anyway.
- Players who already own a second PC and are comfortable troubleshooting compatibility.
Who it does not suit
- Casual players. Two hours a week will never repay the hardware.
- Feature maximalists. The approach is strong at reading and weak at interfering.
- Anyone expecting “buy once, forget”. Cards and firmware live in the same update race as ordinary builds and break just as thoroughly when an anti-cheat updates.
Questions to ask the seller before paying
- Exactly which card and which revisions are supported.
- Whether a separate input controller is required, and which one.
- What is shown on the second screen versus what still demands attention on the main one.
- How the setup behaves on game update day and how quickly fixes ship.
- Whether your Windows build on the gaming machine is supported.
“It all just works, don’t worry” is a sufficient reason not to buy. The rest of the pre-purchase questions live in the build selection checklist.