The loader installs its runtime to C:\PureDMA\ and writes a launch log to C:\PureDMA\dayzdmalog.txt. If a launch fails, that file is usually the first place to look.
Launch takes a long time after pressing Play
If the loader sits on "Waiting for product connection" or "Waiting for Windows to create the product process" for a long time, the delay is almost always the DMA card itself being slow to read what it needs to initialize — not the loader hanging.
To confirm it's the card, close the loader and run a standalone DMA speed test (for example Lones DMA Speed Test). If the speed test also takes a long time to start or finish, the card is the bottleneck.
Common causes: a USB-C cable that's not plugged into the data port on the DMA card, a weak USB port on the second PC, or firmware that's gotten slow after a long session. Try a different USB port on the second PC first, then a different cable.
Launch stuck on "Waiting for product connection" / DMA not detected
If a launch times out at "Waiting for product connection" or the log says VMMDLL_Initialize failed, the product couldn't talk to your DMA card. Work through these in order:
1. Cable: the USB-C cable must be plugged into the DATA port of the DMA card (not the power-only port) and into the second PC. Try a different cable if in doubt.
2. FTDI drivers: install the Winusb D3XX drivers (version 1.4.0.0 or newer) on the second PC. Without them, Windows will not enumerate the card.
3. Standalone speed test: run a DMA speed test (for example Lones DMA Speed Test). If it fails outright, the problem is hardware-side — continue below. If it passes, the problem is in the PureDMA stack; re-launch from the loader so C:\PureDMA\leechcore.dll / vmm.dll / FTD3XX.dll are re-installed, and check C:\PureDMA\dayzdmalog.txt.
4. Main PC check: the DMA card should show a solid green light. If it's flashing any other colour, the card did not initialize on the main PC. Cold-boot the main PC (shut down, unplug the power cable, hold the power button for a minute, plug back in, boot). Try a different PCIe slot. If the card still doesn't appear in Device Manager, suspect bad firmware, a faulty card, or an incompatible motherboard.
5. Reflash: as a last resort, reflash the DMA card with its firmware.
6. ZDMA / Ditto / custom firmware: replace C:\PureDMA\leechcore.dll with the one your firmware vendor provided (see the Custom firmware page).