Skip to content
Back to Learn

DMA card not working? Fixes for VMM INIT FAILED

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.
GuideUpdated · phantom · 812 reads

Cold boot both PCs first. When your card isn't showing up, fails its speed test or gives you VMM INIT FAILED, it's usually stuck after a restart. It can also be the cable, the USB port or the PCIe slot. If the cold boot doesn't fix it, find your problem in the table and go down its list in order.

Warning. While you get your DNA ID or flash, keep your main PC in the BIOS so your card has power. Never boot into Windows on your main PC with a card that isn't flashed with our firmware yet. If you already did, read Booted Windows with an unflashed card and reinstall Windows on your main PC before launching any games.

Find your problem

What you seeWhere the fix is
An error message, like VMM INIT FAILED or TINY PCIe TLPDMA error messages
Your card isn't in Device Manager on your second computerDMA card not showing
No lights on your card, or the PCIe light blinksThe card's lights are off
"Unable to connect to USB/FT601 device"Unable to connect
VMM INIT FAILEDVMM INIT FAILED
Speed test SLOWSpeed test failing or slow
Windows won't let MewTools openMewTools blocked by Windows
MewTools' JTAG/flash dot isn't green, or the flash failsMewTools will not flash
Your main PC won't start, freezes or blue screensMain PC will not boot
It worked yesterday and stopped todayIt worked yesterday
It stopped after a new PC or a Windows reinstallMoving to a new PC
Everything passes but the software can't find the gameThe software can't find the game
MAKCU or FERRUM does nothingMAKCU or FERRUM
No picture through the fuserFuser setup

Cold boot both PCs first

A normal restart or waking from sleep can leave your card, or its link to your second PC, stuck. Both PCs look fine, but your card stops answering. A cold boot of both PCs fixes most problems, so do it before anything else.

If your card isn't flashed yet, start your main PC into the BIOS instead, never Windows, and skip the activator. Do a cold boot after any Windows update, BIOS update or crash, and whenever something that worked stops.

DMA card not showing in Device Manager

The GODLIKE 100T's bracket seen from outside the PC: DATA port first, then the JTAG port, then the kill switch nearest the gold strip end

Check this on your second computer. Open Device Manager (right-click the Start button, then Device Manager), unplug the USB from your second computer, plug it back in and watch for something disappearing and coming back.

  • Which port the cable is in.
    Data is the port furthest from the gold strip. On the data port, a flashed card shows as FTDI FT601 USB 3.0 Bridge Device under Universal Serial Bus controllers once the data driver is in. On the JTAG port it's a different device, and before it has a driver Windows may list it under Other devices with a yellow triangle. On the 100T it shows as USB To UART+JTAG, and as the CH347 JTAG interface once the JTAG driver is in.
  • The driver.
    In MewTools open Drivers and press Install next to Card data cable for the data port, or Card firmware cable for the JTAG port.
  • The kill switch.
    If your card has one, it has to be on, and never switch it while your PC is on (the kill switch).
  • Your main PC is on.
    Your card gets its power from the slot, so with your main PC off there's nothing to see.
  • The cable.
    Use the one that came with your card, because a USB-C charging cable often has USB 2.0 wiring inside and won't work. Flipping the USB-C plug over at your card's end can also fix a bad connection.
  • The port.
    Use a rear USB 3 port on your second computer with no hub. Front and top ports go through a cable inside the case and can cause dropouts.
  • Cold boot both PCs.
    A card stuck after a restart or sleep doesn't show up. How
  • The slot.
    If none of that works, your card may not be coming up on your main PC at all, so go to the lights section. Slots that share lanes are in Your Main PC.

For a brand new card, the same checks are in Main PC Setup.

The card's lights are off

The GODLIKE 100T: 1 data port, 2 JTAG port, 3 power switch, 4 data light, 5 PCIe status light, 6 power light, 7 ambient light, 8 PCIe connector

What each light on the GODLIKE 100T means, going by GODLIKE's own notes on the card:

LightWhat it tells you
PowerOn: your card has power. Off: no power, so check the switch and how your card sits in the slot
PCIe statusOn: your card is properly connected to the motherboard. Blinking: the connection failed. Off: your card is faulty, or the firmware is missing or incompatible
Data transferOn while data moves to your second computer, like during a speed test, and off the rest of the time
AmbientOnly for looks
  • No lights at all.
    Make sure the kill switch is on. Then shut down, unplug your main PC, touch a bare metal part of the case and reseat your card, pushing it in until no gold shows above the slot.
  • Still nothing.
    Try another slot. Some slots share lanes with an M.2 socket (where a flat SSD screws in) and switch off when that socket is used (Which slot to pick).
  • On a riser.
    Take out the riser (the extension cable for the slot) and put your card directly in a slot, because cheap or long risers make cards unstable or stop them working.
  • The PCIe status light blinks.
    Your card has power but its connection to the slot failed. Shut down and reseat it, then try another slot, or step the slot's speed down one at a time in the BIOS. Your software may show Unable to retrieve required Device PCIe ID when this happens.
  • Power light on, PCIe status light off.
    The firmware is missing or doesn't suit your card. Send a photo of your card in your ticket, with a screenshot of Card Check in MewTools after you press Read card.

"Unable to connect to USB/FT601 device"

The software on your second computer can't reach your card's data link. Newer versions of the software say "Unable to connect to FPGA device" for the same thing.

  • The cable is in the JTAG port.
    Move it to the data port, JTAG is only for flashing.
  • The FTDI data driver is missing.
    Install it from MewTools, then check Device Manager shows the FTDI device with no warning triangle.
  • The cable or the port.
    Use the cable that came with your card in a different rear USB 3 port, and try flipping the USB-C plug over at your card's end.
  • Then cold boot both PCs, from the top of this page.

VMM INIT FAILED

VMM INIT FAILED, or "[CORE] Initialization Failed", means the software on your second computer couldn't start reading your main PC's memory.

  • Cold boot both PCs first.
    A card stuck after a restart or sleep is the most common cause.
  • Run the activator.
    If the log above the error says TINY PCIe TLP algorithm auto-selected, your card hasn't been activated. What that means.
  • Check your card came up on your main PC.
    Its power and PCIe status lights should be on steady, and the FTDI device should show on your second computer.
  • The cable and the port.
    An unstable link can fail here as well as in the speed test, so check Ports and cables.
  • The slot.
    A slot sharing lanes with a drive you use can give your card a bad link, so try another.
  • Check Device Manager on your main PC.
    Your card shows there as the device your firmware makes, usually under Network adapters. A yellow mark means its driver is missing, which is common after a Windows reinstall or on a new PC. Some of our devices use Windows' own driver and some need one installed by hand. A device never changes drivers, so if yours needed one, install that same driver again. Turn on View, Show hidden devices, uninstall any greyed-out copies of it with delete the driver unticked, then cold boot.
  • Your BIOS settings.
    Turn off Fast Boot in the BIOS, since it's the one setting that causes trouble with every firmware (the Windows Fast Startup option is something else). Every firmware works with SVM and NX on, but turning them off helps stability unless you need them. Above 4G makes no difference, so leave the rest alone. How to open your BIOS shows where Fast Boot is on each brand. If your drive uses BitLocker, read this first.
  • The PCIe speed of that slot.
    In the BIOS each slot has a speed setting shown as Gen1, Gen2, Gen3 and so on. Start at the fastest and step it down one at a time until your card works.

If it still fails after all of that, your board and your firmware may not get along. Open a ticket with everything in What to send us and we'll work on it with you, and replace your firmware if we need to.

Speed test failing or slow

A slow result in the MewTools speed test usually means a problem with the link between your card and your second computer. Other tools show the same problem as "Failed to retrieve Physical Memory Map" or "TINY PCIe TLP algorithm auto-selected". If you see TINY PCIe TLP right after you flash, run the activator first (what it means).

  • The cable.
    Use the one that came with your card, with no extension.
  • The port.
    Try a different rear USB 3 port. If you get random stutters, try a port in a different group on the back, since it may be on a different USB controller.
  • Nothing else on that controller.
    No hub, and nothing that streams all the time like a webcam or a capture card.
  • The USB-C plug.
    Flip it over at your card's end and test again.
  • Watch the data light.
    It should come on while the test runs. If it stays off, nothing is reaching your second computer, so check the cable is on the data port and the FTDI driver is in.
  • Cold boot both PCs, then test again.

On a USB 3 port plugged in directly, under 80 MB/s is SLOW and GOOD starts at 140. Every cutoff is in What a normal speed looks like, and Run a speed test shows a good result. If the cable and port are right and it still fails, say so in your ticket so we can look at your firmware.

MewTools will not flash, or JTAG is not active

  • The JTAG/flash dot in Card Check isn't green.
    The cable has to be in the JTAG port, and your main PC has to be on so your card has power and its power light is on.
  • The driver is missing.
    Open Drivers, press Install next to Card firmware cable, then press Check again in Card Check. If MewTools says it isn't running as admin, close it and open it again as admin (MT-601).
  • Windows blocked MewTools.
    Go to MewTools blocked by Windows for SmartScreen, Smart App Control and antivirus.
  • The kill switch is off.
    Shut your main PC down, turn the kill switch on, then start your PC again.
  • Still not green.
    Cold boot both PCs, with your main PC going back into the BIOS, then press Check again in Card Check.
  • MewTools says the file is for another chip.
    It stops before it writes anything. Use the firmware made for your card, and ask in your ticket if that's the file you picked. The rest is under MT-302.
  • An older MewTools.
    Flashing on 75T and 100T cards was fixed in the newest version, and the JTAG port now gets set up by itself. Download the latest and try again.
  • The flash failed.
    Leave everything plugged in, replug the JTAG/flash cable and press Try again. If it fails again, send the summary from Something's Wrong in your ticket. Every flashing code is in MewTools flashing errors.
  • It flashed, but nothing changed.
    A normal restart doesn't load new firmware. Shut your main PC down fully, wait for the timer in MewTools, then turn it back on. While your PC is off, plug your card's data port (port 1) into your second PC.
  • The DNA it reads doesn't match the one you sent.
    Stop and tell us in your ticket, because firmware for a different card will flash fine and then not work.

Only run MewTools on your second computer. Every step with screenshots is in Flashing your firmware.

Main PC will not boot, freezes or blue screens with the card in

  • Fans spin but no picture.
    Turn your power supply off, unplug it and reseat your card. If it's the same with your card out, something else got knocked, so press your graphics card and RAM back in.
  • A drive disappeared.
    The slot shares its lanes with that M.2 socket. Your files are still on your drive, and it comes back once you move your card to another slot.
  • It freezes or crashes on a riser.
    Try your card directly in a slot. If that fixes it, the riser is the problem.
  • You used the kill switch with your PC on.
    PCIe slots in a normal desktop aren't built for that. Shut down fully, set the switch, and start again.
  • The first start takes a few minutes, or it goes into the BIOS by itself.
    That happens after a hardware change.
  • DRIVER_VERIFIER_DMA_VIOLATION.
    It's Windows stop code 0xE6. Most of the causes Microsoft lists for it are driver bugs, but one is the IOMMU blocking a device's memory access, so with a card in, don't ignore it. Do the check below, then tell us in your ticket. More in What that blue screen means.

To find out if it's your card at all, shut down, switch your card off with the kill switch or take it out, and use your PC for a while. If the problem stays, it's not your card. PC won't boot after installing a DMA card goes through each case, including the motherboard's debug lights and a missing boot drive.

If it crashes or freezes in Windows or in a game with your card in, go through DMA firmware troubleshooting.

It worked yesterday and stopped today

  • Cold boot both PCs, then run the activator. That fixes it most of the time.
  • Windows or a BIOS update.
    A BIOS update can turn Fast Boot back on, so check it's still off.
  • The cable got knocked, or moved to a different port on either PC.
  • A Windows reinstall, a new PC or a tweaked Windows.
    Some of our devices use Windows' own driver and some need one installed by hand. A device never changes drivers, so after a reinstall or on a new main PC, one that needed a driver gets that same driver installed again. Debloated or "gaming" Windows builds often block drivers, and a normal Windows 10 or 11 install fixes that.
  • Your firmware was blocked or detected.
    A real detection usually looks like a 24-hour ban that turns into a 365-day ban. If you were offline when it landed, it can go directly to 365 days, and sometimes it's a manual ban. If nothing was banned and your card stopped working, it's usually a stuck card or the cable. If you were banned, tell us in your ticket what happened and when, with your DNA ID. A ban the firmware didn't cause, like raging, manual reports, a spoof problem or a wrong set-up, gets one replacement during your warranty: the same firmware with new serials. What happens when we confirm a detection is in Firmware warranty and upgrades.

The software can't find the game, or the game crashes

  • Run the speed test first.
    If it passes, your card and cable are fine and the problem is on the software side.
  • Activate again.
    Run the activator on your second computer again after every restart of your main PC.
  • The game crashes or freezes on your main PC.
    Do the check at the end of Main PC will not boot to rule your card out.
  • The software.
    Blurred handles its own configs, updates and license in Blurred's Discord, and Streck does the same through tickets in Streck's Discord. If they say the problem is your card, tell us in your ticket what they said.
  • It only drops in a match.
    Run the speed test while the game sits in the lobby. If it still passes, your card's link is fine and it's the software's side, like its memory map. If it drops, go through the power settings and USB port in Low DMA speed.
  • The anti-cheat may have blocked it.
    What a real detection looks like is under It worked yesterday and stopped today. Open a ticket with the game, what happened and when.

Booted Windows with an unflashed card

Windows records all plugged in devices in many places, and we can't be sure that ever gets fully cleaned up.

If you booted into Windows with your unflashed card, tell us in your ticket. The fix is to reinstall Windows on your main PC, so back up anything you want to keep first with Back up and reinstall Windows.

What to send us

Open a ticket in our Discord with:

If you bought your card somewhere else and have never bought from us, we can't help with it in a ticket. What we know is in Already own a DMA card?. If you haven't bought yet and want to know if something will work, post on the support forum.

Hardware we sold you has three months of warranty, and we replace faulty parts if you send proof like photos or a video. Read about each type of claim in Firmware warranty and upgrades.

Common questions

  • What is a cold boot?
    Shut both PCs down, unplug their power cables, hold each power button for 15 seconds, then plug them back in and turn them on, your main PC first. Then run the activator on your second PC.
  • Why did my DMA card stop working after a BIOS update?
    A BIOS update can turn settings back on, like Fast Boot or virtualization. Go into your BIOS and turn them off again.
  • Why did my DMA card stop working after a Windows update?
    Windows may have installed a driver on your card. Open a ticket in our Discord and we'll check which one.
  • What does a blinking PCIe light on a DMA card mean?
    Your card has power and its connection to the slot failed. Reseat it, try another slot, or step the slot's speed down in the BIOS.
  • How do I know if my firmware was detected?
    A real detection usually looks like a 24-hour ban that turns into a 365-day ban. If nothing was banned and your card stopped working, it's usually a stuck card or the cable.
Are we missing something?

Tell us what you came looking for and couldn't find, or what we got wrong, and we'll look into it. No account needed.

Did this help?

You don't need an account, this tells us what to write more of.