> For the complete documentation index, see [llms.txt](https://docs.dexa.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexa.im/dma/dma-setup-guide/troubleshooting.md).

# Troubleshooting

## Flea Power Drain/Cold Boot

{% hint style="info" %}
This will resolve most issues with your DMA card.
{% endhint %}

* Shutdown BOTH PCs
* Unplug the power cable from BOTH PCs
* Wait 60 seconds
* Press and/or hold the power button on BOTH PCs to ensure all power is drained from the PC and no LEDs remain lit

## \[FAIL] VMM INIT FAILED. <a href="#fail-vmm-init-failed" id="fail-vmm-init-failed"></a>

The DMA card and/or USB connection is stuck, often due to a fast reboot or system waking from sleep.

<figure><img src="/files/6wzDa3yzGIgFapOzSPki" alt="" width="481"><figcaption><p>[FAIL] VMM INIT FAILED.</p></figcaption></figure>

* Perform a [#flea-power-drain-cold-boot](#flea-power-drain-cold-boot "mention")

## FPGA: ERROR: Unable to connect to USB/FT601 device <a href="#fpga-error-unable-to-connect-to-usb-ft601-device-0-v0.0-0000" id="fpga-error-unable-to-connect-to-usb-ft601-device-0-v0.0-0000"></a>

The FTDI driver is not installed or incorrect DMA card port used.

* verify the DMA PC has the [latest drivers](#user-content-fn-1)[^1] installed from [DMA Setup Guide](/dma/dma-setup-guide.md#prepare-windows-1)
* verify the USB port being used on the DMA card is the `DATA` port

## Failed to retrieve Physical Memory Map <a href="#failed-to-retrieve-physical-memory-map" id="failed-to-retrieve-physical-memory-map"></a>

Unstable or faulty USB connection.

* Reseat the USB cable on both ends (DMA PC and GAMING PC)
* Try a different available USB 3.2 (or better) port on the DMA PC
* Replace the USB cable; [we recommend a Thunderbolt 4 (or better) cable](https://amzn.to/49dUPoI)
* Perform a [#flea-power-drain-cold-boot](#flea-power-drain-cold-boot "mention")
* On the GAMING PC, [Reinstall Windows](/learn/resources/windows-10-and-11-guides/reinstall-windows.md)

## \[SYMBOL] Offline symbols unavailable - file 'info.db' not found <a href="#symbol-offline-symbols-unavailable-file-info.db-not-found" id="symbol-offline-symbols-unavailable-file-info.db-not-found"></a>

PCILeech cannot retrieve symbol data for memory interpretation.

* Download the latest version of `info.db` and `MemProcFS` and place them in the same folder as the test tool
  * ufrisk [info.db, ](https://github.com/ufrisk/MemProcFS/releases)[MemProcFS\_files\_and\_binaries-win\_x64-latest](https://github.com/ufrisk/MemProcFS/releases/download/v5.16/MemProcFS_files_and_binaries-win_x64-latest.zip)

## FPGA: TINY PCIe TLP Algorithm auto-selected <a href="#fpga-tiny-pcie-tlp-algorithm-auto-selected" id="fpga-tiny-pcie-tlp-algorithm-auto-selected"></a>

The DMA card is running at slower speeds due to poor USB connection or firmware.

* Reseat the USB cable on both ends (DMA PC and GAMING PC)
* Try a different available USB 3.2 (or better) port on the DMA PC
* Replace the USB cable; [we recommend a Thunderbolt 4 (or better) cable](https://amzn.to/49dUPoI)
* Re-flash the card's firmware
  * sometimes, re-flashing the same firmware will not resolve this. To validate the card is not experiencing issues:&#x20;
    * flash a test/diagnostic firmware
    * run a test on the card using the test tool
    * verify the card tests OK
    * re-flash your firmware
    * test again, verify the card tests OK
* Perform a [#flea-power-drain-cold-boot](#flea-power-drain-cold-boot "mention")

## \[CORE] Initialization Failed. Unable to locate valid DTB / auto-identify OS <a href="#core-initialization-failed.-unable-to-locate-valid-dtb-auto-identify-os" id="core-initialization-failed.-unable-to-locate-valid-dtb-auto-identify-os"></a>

Incorrect BIOS settings or unstable USB link.

* Review **all required BIOS changes** on the **GAMING PC:** [DMA Setup Guide](/dma/dma-setup-guide.md#disable-virtualization-iommu-etc)
* Reseat the USB cable on both ends (DMA PC and GAMING PC)
* Try a different available USB 3.2 (or better) port on the DMA PC
* Replace the USB cable; [we recommend a Thunderbolt 4 (or better) cable](https://amzn.to/49dUPoI)
* Perform a [#flea-power-drain-cold-boot](#flea-power-drain-cold-boot "mention")
* On the GAMING PC, [Reinstall Windows](/learn/resources/windows-10-and-11-guides/reinstall-windows.md)

## FTDI SuperSpeed-FIFO Bridge

* verify the DMA PC has the [latest drivers](#user-content-fn-1)[^1] installed from [DMA Setup Guide](/dma/dma-setup-guide.md#prepare-windows-1)
* verify the USB slot being used on the DMA PC is at least USB 3.2 or better
* manually uninstall the `FTDI SuperSpeed-FIFO Bridge` device in device manager
  * right click -> uninstall device
  * click `Action` menu -> `scan for hardware changes`
  * validate the device shows correctly in device manager
* verify the GAMING PC is fully updated and no Windows updates are pending

[^1]: You will need to verify the DMA PC has the FTDI chip drivers, WCH CH341 and CH343 drivers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dexa.im/dma/dma-setup-guide/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.