Common problems
Find the fix for a card missing from Device Manager, VMM INIT FAILED, FT601 errors or a failing speed test. Start with a cold boot, then check the port, cable and slot.
Fix crashes, freezes and blue screens with DMA firmware. Check your BIOS settings, Link State Power Management, shared lanes, your cable and your anti-cheats in order.
A DMA card tops out around 200 MB/s on USB 3. If yours is slower, the cause is usually the cable or USB port, so work through these six checks in order.
Black screen, a debug light that stays on, a boot loop or straight to the BIOS after you put in a DMA card. Find what you see and work down the fixes in order.
Where to find your 48 digit BitLocker recovery key after you put in a DMA card or change the BIOS, and what to do if you can't find it.
Fix freezing, stuttering, missing firmware or driver problems with your DMA card. Check stock Windows, BIOS updates, Wi-Fi and your motherboard in order.
Fix a black screen or No signal on a GODLIKE video fuser. Reset both PCs to 1080p at 60Hz, check the inputs, cables and modes, then fix a black screen when a game starts.
Fix RDMA that won't connect, stops after about 30 seconds with VMM INIT FAILED, runs slow or leaves your PC with no internet. Cold boot, power saving, ports and link speed.
When DMA software won't open, won't log in or can't reach your card, check the runtimes, clock, driver, activator and antivirus on your second PC.
If Windows SmartScreen, Smart App Control or your antivirus stopped MewTools from opening, here's why and how to let it run on your second computer.
What a DMA memory map does, when errors such as "Unable to locate valid DTB" mean you need one, how to make mmap.txt for Blurred, and when to make a new file.
Error messages
Find your DMA error by its exact text, like VMM INIT FAILED, Unable to locate valid DTB or TINY PCIe TLP, with what it means and how to fix it.
VMM INIT FAILED means your DMA software couldn't start reading your main PC. Check the log for TINY PCIe TLP, then work through the cold boot, cable, port and BIOS checks.
Your DMA software fell back to tiny, slow reads because your card can't read memory. The most common cause is a card that hasn't been activated, so check the activator first.
Your second PC can't reach your DMA card's data port. Check the cable is in the data port, then check the FTDI driver, other programs using the card, power and the USB port.
Failed to initialize DMA means your software couldn't connect to your card. Restart both PCs, then check the data port, the FTDI driver and other programs.
Your DMA software couldn't read where your main PC's RAM sits, usually because the USB link is unstable. Check that link first, then see whether a memory map helps.
Your DMA software connected but can't find Windows in your main PC's memory. Check for TINY PCIe TLP, cold boot, then make a memory map.
Your second PC reached the DMA card, but the card isn't linked to your main PC's slot. Cold boot, check the lights, reseat it and try another slot.
A file is missing from your DMA software's folder and it couldn't download symbols either. Extract everything, check your antivirus and connection.
Your DMA software can't find the FTDI file it uses to talk to the card. It's a file missing from the software's folder, not your card or your cable.
Your DMA software needs Microsoft's Visual C++ runtime, and your second PC doesn't have it. Install it from Microsoft's own site, then restart.
FTDI SuperSpeed-FIFO Bridge under Other devices means your DMA card's data driver isn't installed. You can install it from MewTools with one click.
USB To UART+JTAG under Other devices is your DMA card's JTAG port without its driver. Install the CH347 driver in MewTools and its dot turns green.
Device Descriptor Request Failed means your second PC saw your DMA card but couldn't read it. It's usually the cable, the USB port or a stuck card.
DRIVER_VERIFIER_DMA_VIOLATION is a blue screen with stop code 0xE6. How to check if your DMA card is the cause, and what to send us if it is.
