What a DMA Installation Service Involves

The card is seated, the second PC is powered, the cable is plugged in, and Device Manager still shows an unknown device with a yellow triangle next to it. That is the moment most people start searching for a DMA installation service, usually at 2am, usually after the third BIOS reboot.

This page covers what a setup actually consists of, the four separate paths that have to work before anything appears on your second monitor, where each one tends to break, and what a guided session covers. It also covers the simpler case: a normal internal product that will not launch because Windows is eating the loader.

Nothing here promises that a setup is quick, because how long one runs depends entirely on what your hardware is doing. A rig that only needs a BIOS toggle behaves nothing like one where the firmware does not match the card revision, and you usually cannot tell which you have until someone looks. What follows is the diagnostic map. The live category page is where the current lineup lives.

What a DMA installation service actually does

A DMA rig is not one thing that either works or does not. It is four independent paths, and a setup session is really four smaller jobs. Understanding which one is broken is most of the work, and it is the part people get wrong when they try to fix it alone by reflashing at random.

The memory path

This is the card itself. A DMA card sits in a PCIe slot on your game PC and reads that machine's memory directly, then sends what it reads down a cable to your second PC. Nothing about it runs as a process on the game machine, which is the entire point of the approach.

The memory path breaks in predictable places. The slot matters: some boards run their lower slots off the chipset, or drop lanes entirely when an M.2 drive is populated, so a card that works in the top slot is dead in the bottom one. BIOS settings matter too, and Above 4G Decoding, Resizable BAR and IOMMU or VT-d all change whether the card enumerates and whether reads come back clean. Then there is the firmware. Firmware is what gives the card its identity on the PCIe bus, and it has to match your exact card revision. Flash the wrong build and you get a card that either does not appear at all or appears wrong, and recovering from that usually means going in over JTAG rather than trying again through the normal flasher.

When someone says their card "stopped working after an update", it is almost always this path, and almost always either a BIOS setting that reset or firmware that no longer matches what the software expects. Windows updates and motherboard BIOS updates both do this, and a BIOS update in particular tends to wipe the exact toggles the card depends on back to their defaults without telling you.

The video path

Your second PC has to see the game. That means a capture route: the game PC's video output is duplicated, typically through an HDMI fuser or splitter, with one leg going to your normal monitor and the other into a capture card on the second machine. The overlay you are paying for gets drawn on that captured feed, on the second screen, not on the game itself.

What goes wrong here is boring and physical. Resolution and refresh rate have to be something the capture device actually accepts, and a 1440p 240Hz output into a capture card rated lower gives you a black screen or a feed that tears. HDCP handshakes cause blank captures. Cheap cables cause dropouts at higher refresh rates that look exactly like a software fault. Splitters that advertise a resolution on the box often only pass it on one port, so the leg feeding your monitor looks perfect while the leg feeding the capture card negotiates something lower. A good chunk of setup time is spent proving the video path is fine so you can stop blaming it.

The input path

If you want anything that moves the mouse, the second PC needs a way to send input to the game PC without software on the game PC receiving it. That is what a KMBox or Makcu class device does. It presents itself as a normal USB mouse and keyboard to the game machine, and takes commands from the second PC over serial.

Wiring order is the thing people miss. Your physical mouse plugs into the device, and the device plugs into the game PC, so your real movement passes through it. Get that backwards and you have a device that is connected but has no passthrough, which produces the confusing result of aim assistance working while your own mouse stops responding. Beyond wiring there is COM port assignment, baud rate and device firmware, all of which have to agree with the software on the second PC. COM port numbers also move when you change USB ports, so a rig that worked yesterday can come up mute purely because the cable went into a different socket.

The software and config path

Last comes the actual product: the reader software on the second PC, your key, and the configuration. This is the part everyone assumes is the hard part and it is usually the easiest, provided the three paths underneath it are clean. Radar windows need positioning. Overlay scaling has to match the captured resolution or your boxes sit offset from the players they are drawing on, and offsets that look like a broken read are frequently just a scaling mismatch. Feature settings need tuning to something sane rather than the maximum values, which is a separate conversation and one worth having during setup rather than mid raid.

For a normal internal product the list is shorter but the failures are just as common. Windows Defender and Smart App Control quarantine loaders on sight. Core Isolation and memory integrity block driver mapping. Secure Boot and virtualisation based security interfere. Loaders are built against specific Windows builds, so being several updates ahead or behind causes silent failures. If you are also running a spoofer, the order of operations matters, and doing it in the wrong sequence wastes the spoof.

DMA vs internal: which setup you actually need

Internal means the software runs on the same machine you play on. One PC, no capture chain, no second workstation, no firmware to flash. Setup, when it goes smoothly, is minutes rather than an evening, because there is a single path to get wrong instead of four. The tradeoff is that something is present on the game machine while you play, and it has to survive whatever the anti cheat does while looking for it.

DMA means a second computer, a DMA card, a capture route and usually an input device. Nothing executes on the game PC. That separation is why people move to it, and it is also why the barrier to entry is real: you are buying hardware, learning a firmware flashing process, and building a small second workstation next to your desk.

Honest recommendation. If you have never run either, start internal. There is no hardware to source, it teaches you how the software side behaves, and buying the shortest duration available first lets you find out whether you enjoy playing this way at all before you commit to building a rig. Plenty of people assemble a full DMA setup, use it briefly, lose interest, and discover the hardware does not refund itself.

Move to DMA when one of two things is true: you play a title where you have decided the separation is worth the cost, or you already own a second PC and the only thing standing between you and a working rig is the card and the capture gear. If you are buying a second machine purely to run DMA, cost the whole build honestly before you commit, because the second PC, the splitter, the capture card and the input device are all separate purchases rather than things that arrive with the card. Either way, the setup burden lands on the DMA side, which is why a paid session exists at all.

Installation help at CamUnlocks

The store carries setup help for both sides of that split: guided work on a full DMA rig, and shorter jobs for a normal internal product that refuses to launch. Which one you want follows from the fault, not from what you already bought.

Take the internal route when the software is the thing misbehaving, meaning Windows removing a loader, memory integrity blocking a driver map, or a spoofer sequence that is not taking. Those have a known shape and a known list of things to check. Take the DMA route when the rig itself is the problem: card detection, BIOS, firmware, capture or input, in whatever order the fault turns out to be in.

Before you buy either, join the Discord and describe the symptom, because a good number of problems are a single BIOS toggle and you should not pay for that. The written guides at guides.camunlocks.com cover the standard flows and cost nothing to read. If you do want a session, start with the narrowest one that covers your fault rather than the broadest, and check the status page first so you are not booking time to configure something that is down anyway.

What is available now, and what each option covers, is listed on the Installation Services category page. That page is the source of truth for the current lineup.

Getting set up

Delivery runs through the store itself, so once payment clears you have what you bought without a manual approval step to sit through. For a guided session, the ticket is where the work actually gets scoped and scheduled, so open one as soon as you have the purchase.

From there the sequence is straightforward. Take your key to the product's own loader or panel and register it there. For internal products that is usually all there is. For DMA you will need the hardware in place first: a card in a working PCIe slot, a second PC with a free USB 3 port, a capture path from the game PC, and an input device if the product uses one. None of that ships with a software key, so buy the hardware before you buy time on it.

Support runs through Discord, 24/7. Open a ticket, say what you have, what you tried and what the exact error or symptom is, and include a photo of the card in the slot if the card is the suspect. That single detail saves more time than any other. Written walkthroughs live at guides.camunlocks.com and are worth reading before the session so you are not learning the vocabulary while the clock runs.

Staying safe

Account risk is real, and no setup, paid or free, removes it. Anti cheat systems change, products get flagged, and anyone telling you otherwise is selling you something. What you can do is stack the odds.

• Check the public status page before every session. Not weekly, before every session. Statuses change fast and the page is updated publicly rather than being something you have to ask about in a ticket.
• Use a maintained product. Something abandoned falls behind the moment the game patches, and no amount of careful setup compensates for software nobody is updating any more.
• Do not queue with obvious behaviour. Most reports come from other players, not from automated detection, and behaviour that looks impossible in a killcam generates reports regardless of what you are running.
• Do not stream or record. Overlays end up in clips, clips end up in report threads.
• Buy the shortest duration available before committing to a longer one, and test on an account you can afford to lose rather than a main.

A properly configured setup helps here in one specific way: badly configured settings are the fastest route to a report, and setup time spent on sane values is not wasted.

Frequently asked questions

What does a DMA installation service actually include?

It covers getting a working DMA rig from wherever it is currently stuck: card detection and PCIe slot issues, BIOS settings, firmware matched to your card revision, the capture path from game PC to second PC, input device wiring and serial config, and finally the product configuration. How the session runs is agreed in your ticket, because the answer depends on which of those is broken.

Do I need a second PC for DMA?

Yes. A DMA setup reads memory from the game PC and processes it somewhere else, and that somewhere else is a second computer with the reader software, the capture card and the overlay on its own monitor. It does not need to be powerful, but it does need to exist. If you only have one machine, an internal product is your option.

Can you fix a card I already flashed with the wrong firmware?

Often, yes. A mismatched flash usually leaves the card unresponsive to the normal flashing tool, and recovery means going in over JTAG with the correct build for your exact card revision. Bring the card model and revision to your ticket, plus what you flashed and where you got it, because that determines whether it is a straightforward recovery or a longer one.

How long does a setup take?

Anywhere from a few minutes to an evening, and the variable is your hardware rather than the product. A BIOS toggle is a five minute fix. A wrong firmware flash plus a capture card that will not accept your resolution is a long session. Anyone quoting you a fixed time before seeing your setup is guessing.

Do I need an installation service for a normal internal product?

Usually not. Most internal products install by running a loader and entering your key, and the written guides cover the common blockers like Defender quarantining files or memory integrity being enabled. The paid option exists for the cases where those steps do not work, or where a spoofer sequence needs to happen in a specific order and is not taking.

What should I have ready before the session?

Your card model and revision, your motherboard model, which PCIe slot the card is in, what your capture device is and what resolution and refresh rate you output, whether you have an input device and how it is wired, and the exact error text or symptom. Photos of the physical setup help more than descriptions do.

Does a paid setup make me safer?

Not by itself. A correct setup removes the failure modes that come from a broken configuration, and sane settings reduce how obvious you look to other players, but account risk does not go away. Check the status page before every session and keep expectations realistic about what any product or setup can do.

If you know which of the four paths is giving you trouble, the Installation Services category page shows what is on offer and what each one covers. If you do not know yet, describe the symptom in the Discord first and find out whether it is something you can fix in two minutes for nothing.