DMA cheat setup guide — from card to first ESP.
A DMA setup is four steps: the card goes in the gaming PC, the second PC is prepared, the game runs on the gaming machine, and the software loads on the second one. Here is the order that works, and the things that waste an evening.
Most failed DMA setups fail at the same three points: the card is not seated properly, the second PC cannot see the card over USB, or the software is started before the game. Work through the steps below in order and you will skip nearly all of the usual frustration.
What do you need before starting?
Two computers, one DMA card, a USB cable to link the card to the second machine, a fuser if you want the overlay on your main display, and a Windows install on the second PC. The gaming PC needs a free PCIe slot — ideally one that is not sharing lanes with your GPU, since a slot starved of bandwidth will still work but can behave oddly. If you are unsure whether your spare machine is up to the job, the second-PC guide covers the specs honestly: it is a modest bar, because the second machine renders a box overlay and little else.
Step 1 — seat the card in the gaming PC, powered off
Power down and unplug the gaming PC before touching anything. Seat the DMA card firmly in a PCIe slot and make sure it is fully engaged; a card that is not clicked home will enumerate intermittently, which produces symptoms that look exactly like software problems. Take the card's USB cable out to where the second PC will sit. Boot the gaming PC and confirm Windows does not complain about the new device — a DMA card is designed to be invisible to the host it reads, so an error here usually means the card is not seated properly rather than a driver issue.
Step 2 — prepare the second PC
The second machine is where all the software lives, so this is where the real preparation happens: a clean Windows install, your anti-virus exclusions set sensibly, and the DMA reading library that talks to the card. Plug the card's USB cable in here and confirm the reading software can see the card at all before you involve the game. Debugging a card problem and a game-offset problem at the same time is how people lose an evening.
Step 3 — start the game on the gaming PC
Launch the game and get to a state where it is actually running the session you want — in a match, or in a world with entities loaded. Entity lists are frequently empty or partial on menus and loading screens, so testing before you are properly in-game will show you nothing and look like a broken setup. This is also the moment to confirm your fuser is passing the second PC's signal through to your monitor.
Step 4 — load the software and verify the read
Only now start the reader on the second PC. What you want to see first is entities being found — a count in the tool that moves as the world changes. That proves the memory read works before any overlay rendering is involved. If you get an entity count, you are essentially done: turn on ESP and tune it. If the count stays at zero, the problem is the read, and how DMA cheats work explains what the reader is actually doing. With us, the loader and updater handle the software half and we walk you through your first run in the Discord — see the games we support.
What actually goes wrong, most of the time
In order of frequency: the card is not fully seated; the reading software was started before the game so it latched onto a menu-state memory layout; the fuser is passing the wrong input to the monitor; or the game patched and the offsets moved, which is a waiting-for-an-update problem rather than a setup problem. The last one is worth recognising, because the fix is never a reinstall of your own hardware — it is the software update. That is the maintenance cost that the cost guide explains, and it is the reason a signed auto-updater matters more than any individual feature.