Troubleshooting

ERROR - [FAIL] VMM INIT FAILED.

The most common cause of this error is that your DMA Card/Connection is ‘hung’. This most commonly occurs after your Game PC does a fast reboot, or if your Game PC was previously in sleep mode.

Shutdown your Game PC (do not reboot), wait 5 seconds and power it back on. This is known as a ‘cold boot’.
This should resolve this issue 99% of the time.

ERROR - DEVICE: FPGA: ERROR: Unable to connect to USB/FT601 device [0,v0.0,0000]

Make sure you installed the FTDI Driver on your Radar PC (See the setup guide above for details).
Make sure you are plugged into the DATA PORT on your DMA Card.

Failed to retrieve Physical Memory Map!

Troubleshoot your USB Connection.
If all else fails, re-install windows on your Game PC.

[SYMBOL] Offline symbols unavailable - file 'info.db' not found.

This means that PCILeech was unable to download symbols from the Microsoft Symbol Server. This assists PCILeech in reading memory from your Game PC System
Make sure you unzipped the folder and all files.
Make sure symsrv.dll and dbghelp.dll are present in the folder.
Make sure you have internet connectivity and your firewall(s) are not blocking any connections.
If all else fails, you can download the latest info.db file from the MemProcFS repository (https://github.com/ufrisk/MemProcFS/releases win-x64), and include

FPGA: TINY PCIe TLP Algorithm auto-selected!

This indicates that your DMA Card is operating at lower speeds. This can sometimes be due to a firmware issue, or more commonly a poor usb connection.
Make sure your USB Cable is seated securely on both ends. Try different USB Port(s).

[CORE] Initialization Failed. Unable to locate valid DTB / Unable to auto-identify operating system.

Make sure you made the BIOS Adjustments on Game PC per the setup steps.
Troubleshoot your USB Connection.
Last resort: Re-install windows on Game PC.

DMA Test Tool - Test Result: FAIL / General Failures

If the DMA Test is giving you a failure message, it is most commonly due to your speed/throughput being too low. i. Speed under 4000 Mem/Sec. ii. Throughput under 125 MB/s.
This is most commonly due to a poor USB Connection: i. Make sure your USB Cable is a data-rated (not charging-only!) USB 3.0 Cable, and is securely seated on both ends (DMA Card / Radar PC). ii. On your Radar PC go into Power Plans and set your Power Plan to High Performance. This can improve CPU / USB speeds. iii. Try different USB Ports / USB Cables. iv. Keep playing with it! Most people resolve slow speeds by re-seating their DMA Card, reseating the USB Cable, and/or sometimes the DMA Card bracket may get in the way of the USB Cable fitting securely. v. If your Radar PC is significantly below recommended specs, this can diminish DMA Speed/Throughput.
c. This can be less commonly caused by the Firmware on your DMA Card. i. Some Vanguard / Faceit ‘bypass’ firmwares will reduce the speed/throughput of your card.
In some cases DMA Software may still run fine with lower speeds/throughputs (particularly if you are close to the cutoffs). i. We recommend running a Speed Test for ~360 or more seconds, and looking for any ‘drop outs’. If the connection is stable you may be fine even if you are getting reduced speeds.

DMA Software – Not loading up, entities disappearing or not showing, other anomalous behavior:

This is most commonly caused by Paged Out Memory.
When your system / target process are under High Memory Pressure, assets in memory may get shifted to your Page File.
The Page File is a file located on your hard drive that contains low priority / less commonly accessed items.
Since the Page File is located on your hard drive, your DMA Card cannot read from it.
This can cause undefined behavior in many DMA Software(s), and lead to a lot of frustration.
This is most commonly resolved by installing additional System Memory (RAM) in your Game PC.
You can also disable the System Page File in Windows on your Game PC (Not Recommended: Your system can BSOD if Memory Commits exceed available memory).

If you encounter any issues, please don’t hesitate to open a support ticket.

PreviousTesting (2nd PC)NextFirmware Flashing

Last updated 4 months ago

Troubleshooting

ERROR - [FAIL] VMM INIT FAILED.

The most common cause of this error is that your DMA Card/Connection is ‘hung’. This most commonly occurs after your Game PC does a fast reboot, or if your Game PC was previously in sleep mode.

Shutdown your Game PC (do not reboot), wait 5 seconds and power it back on. This is known as a ‘cold boot’.
This should resolve this issue 99% of the time.

ERROR - DEVICE: FPGA: ERROR: Unable to connect to USB/FT601 device [0,v0.0,0000]

Make sure you installed the FTDI Driver on your Radar PC (See the setup guide above for details).
Make sure you are plugged into the DATA PORT on your DMA Card.

Failed to retrieve Physical Memory Map!

Troubleshoot your USB Connection.
If all else fails, re-install windows on your Game PC.

[SYMBOL] Offline symbols unavailable - file 'info.db' not found.

This means that PCILeech was unable to download symbols from the Microsoft Symbol Server. This assists PCILeech in reading memory from your Game PC System
Make sure you unzipped the folder and all files.
Make sure symsrv.dll and dbghelp.dll are present in the folder.
Make sure you have internet connectivity and your firewall(s) are not blocking any connections.
If all else fails, you can download the latest info.db file from the MemProcFS repository (https://github.com/ufrisk/MemProcFS/releases win-x64), and include

FPGA: TINY PCIe TLP Algorithm auto-selected!

This indicates that your DMA Card is operating at lower speeds. This can sometimes be due to a firmware issue, or more commonly a poor usb connection.
Make sure your USB Cable is seated securely on both ends. Try different USB Port(s).

[CORE] Initialization Failed. Unable to locate valid DTB / Unable to auto-identify operating system.

Make sure you made the BIOS Adjustments on Game PC per the setup steps.
Troubleshoot your USB Connection.
Last resort: Re-install windows on Game PC.

DMA Test Tool - Test Result: FAIL / General Failures

If the DMA Test is giving you a failure message, it is most commonly due to your speed/throughput being too low. i. Speed under 4000 Mem/Sec. ii. Throughput under 125 MB/s.
This is most commonly due to a poor USB Connection: i. Make sure your USB Cable is a data-rated (not charging-only!) USB 3.0 Cable, and is securely seated on both ends (DMA Card / Radar PC). ii. On your Radar PC go into Power Plans and set your Power Plan to High Performance. This can improve CPU / USB speeds. iii. Try different USB Ports / USB Cables. iv. Keep playing with it! Most people resolve slow speeds by re-seating their DMA Card, reseating the USB Cable, and/or sometimes the DMA Card bracket may get in the way of the USB Cable fitting securely. v. If your Radar PC is significantly below recommended specs, this can diminish DMA Speed/Throughput.
c. This can be less commonly caused by the Firmware on your DMA Card. i. Some Vanguard / Faceit ‘bypass’ firmwares will reduce the speed/throughput of your card.
In some cases DMA Software may still run fine with lower speeds/throughputs (particularly if you are close to the cutoffs). i. We recommend running a Speed Test for ~360 or more seconds, and looking for any ‘drop outs’. If the connection is stable you may be fine even if you are getting reduced speeds.

DMA Software – Not loading up, entities disappearing or not showing, other anomalous behavior:

This is most commonly caused by Paged Out Memory.
When your system / target process are under High Memory Pressure, assets in memory may get shifted to your Page File.
The Page File is a file located on your hard drive that contains low priority / less commonly accessed items.
Since the Page File is located on your hard drive, your DMA Card cannot read from it.
This can cause undefined behavior in many DMA Software(s), and lead to a lot of frustration.
This is most commonly resolved by installing additional System Memory (RAM) in your Game PC.
You can also disable the System Page File in Windows on your Game PC (Not Recommended: Your system can BSOD if Memory Commits exceed available memory).

If you encounter any issues, please don’t hesitate to open a support ticket.

PreviousTesting (2nd PC)NextFirmware Flashing

Last updated 4 months ago