DMA troubleshooting: card not found, DTB errors, low FPS
5 min read, updated 1 November 2026
Most DMA problems come down to a handful of causes. Work through the one that matches your log.
The card is not found
- Use a USB 3 port on the second PC, directly on the motherboard, with the cable that came with the card.
- Make sure the card sits firmly in its PCIe slot and the gaming PC is on.
- Let the loader install the runtime: start QOWED through the loader, not the client directly.
- Custom firmware or RDMA: put your vendor's runtime files and .ini next to the loader.
"Unable to locate valid DTB"
The card is talking, but the memory map of the gaming PC could not be resolved. This usually depends on the Windows build and how its memory is laid out, not on QOWED.
- Restart the gaming PC and start the client again once Windows has fully loaded.
- Send a log to support. A memory map from the gaming PC (support will tell you how to take one) usually fixes it for good.
Low FPS or a stuttering overlay
- Check the link speed your card reports in the log. Slow links (gen1 x1) work, but every read costs more time.
- Close other programs on the second PC that use the card or the USB controller.
- Turn off features you do not use; each one costs reads per frame.
The mouse device does not move
- Open the Devices page and use the test move. If that fails, the device or its port is the problem, not the aim settings.
- Check the COM port or IP address, and that the device runs the firmware it shipped with.
- Check that the aim key is set and that the aimbot is on for the current game.
Still stuck
Press "Send log to support" in the menu or the loader and post the code in a Discord ticket. The log tells support more than any screenshot.