Error strings, cold boots, and how to write a support ticket that gets read.
Paste your error string into the index and start from there. These pages work from symptom to cause to fix, one layer at a time, so you find the first broken link instead of guessing. There is also a page on writing a ticket that gets solved on the first reply.
7 guidesBeginner 4Intermediate 3
Match the exact DMA error string to its layer to find the real cause and the cheapest fix. Most have one of four causes: the wrong USB port, a missing driver, a missing memory map, or virtualisation enabled in the game PC's BIOS.
The DTB error means the reader read memory through your card but could not find the Windows kernel's Directory Table Base. Work in order: generate a memory map, disable VT-d/VT-x or SVM/IOMMU in the game PC's BIOS, prove USB stability, then cold-boot both machines.
A Windows restart leaves a hung DMA card hung: the PCIe slot stays powered, so the FPGA can stay stuck. Shut both machines down fully, pull the mains lead or switch off the PSU for ten seconds, then boot the game PC first.
Intermittent DMA failures are almost always the USB path, not the card, and have four causes: selective suspend, shared controllers, marginal cables and heat. Change one variable at a time and record when each drop happens, because the timing pattern tells them apart.
Send all seven facts in one message and one thread: order ID, card model, motherboard model, and both Windows versions with build numbers. Add what changed since it last worked, what you already tried, and the exact error string as text, not a screenshot.
Test the nine links in order: card powered, card enumerated, driver bound, reader connected, DTB found, process found, features drawing, cursor moving, overlay visible. Stop at the first link that fails and work on that one, because every link after it fails regardless.
When you need a new MMAP, how to build one on the gaming PC, and where the loader expects mmap.txt.