Troubleshooting: Device Not Detected

Tutorials › Device Not Detected

Troubleshooting: Device Not Detected

Green light is on, but Windows still won’t show the ZDMA in Device Manager? Work through the checks below before opening a ticket. Nine times out of ten it is the wrong port, the Thunderbolt driver, or a BIOS switch — all of which you can fix yourself in a few minutes.

1. First, which PC is which

A ZDMA setup uses two computers. Getting them straight avoids most of the confusion:

  • Debug PC — the PC you operate. The ZDMA connects to it over a Thunderbolt cable, and the device must appear in its Device Manager. Every step on this page happens here.
  • Target PC — the PC the ZDMA card is plugged into (the machine being read or tested). You install nothing on it.
How it is connectedThe ZDMA card sits in the Target PC, and a Thunderbolt cable runs from the ZDMA to the Debug PC that you operate. So the Thunderbolt port, driver and BIOS settings that matter are all on the Debug PC side.

2. Read the card’s lights first

The ZDMA has two Thunderbolt ports and one JTAG port. Each Thunderbolt port has its own green LED, and there is a separate amber status LED. Because of compatibility, usually only one of the two Thunderbolt ports actually works — so let the lights tell you which port to use instead of guessing.

What a healthy card looks likeOne amber LED solid, plus the green LED next to the port you are using solid. Everything solid means good. Anything other than solid — off or blinking — is not normal.
  • Amber solid — card is powered and running normally. Not tied to a specific port.
  • Port green solid — this is the working port; the link is good.
  • Port green off or blinking — that port is not the effective one.

If a port shows solid green but Device Manager is still empty, the physical link is fine and the problem is the driver — see step 4. If neither port ever goes solid green, move the cable to the other Thunderbolt port and continue with the steps below.

JTAG port won’t recognize?JTAG runs at USB 2.0 only. A high-spec cable — including the bundled Thunderbolt cable — is “too good” for it and often will not work. Connect JTAG with an ordinary, cheaper USB cable instead.

3. Six-step self-check

Do these in order and stop as soon as the device shows up in Device Manager. Everything below happens on the Debug PC — the one you operate, with the Thunderbolt cable from the ZDMA plugged into it.

Step 1 — Have you flashed firmware? Restore the factory firmware

Always rule this out first: a wrong or failed flash produces exactly the same “not detected” symptom as a cable or driver fault, and no amount of driver work will fix it.

  1. A brand-new ZDMA should be tested first, before flashing anything. Only update the firmware after the card tests good.
  2. If you already flashed FPGA firmware and things stopped working afterwards, restore the factory / default firmware first, then retest. See the ZDMA Firmware Flashing Guide.
  3. Never flashed anything? Skip to step 2.

Step 2 — Confirm the Debug PC port really is Thunderbolt / USB4

The ZDMA can only be reached through a genuine Thunderbolt or USB4 port on the Debug PC. A plain USB-C port looks identical but will never work.

  1. Look for a small lightning-bolt icon printed next to the Debug PC’s USB-C port. No bolt usually means no Thunderbolt.
  2. Not sure? Search your exact motherboard or laptop model plus “Thunderbolt”, or use the AI method in the next section — it identifies your hardware for you.
  3. A USB-C port that is only USB 3.x will never work — that is not a fault, it is the wrong port.

Step 3 — Try both ZDMA ports and get a solid green LED

Settle the physical link before you look at Windows at all. Only one of the ZDMA’s two Thunderbolt ports usually works.

  1. Move the Thunderbolt cable between the ZDMA’s two Thunderbolt ports and watch the lights. The working port shows a solid green next to it, with the amber LED solid as well.
  2. No solid green on either port? Try a certified 40 Gbps Thunderbolt 4 cable, and boot the Debug PC first, then connect the cable.
  3. Is the Debug PC a laptop? Set it to High Performance power mode and plug it into wall power.
Got solid green?The physical link is good — go on to step 4 to find out whether Windows can see it. If neither port ever goes solid green, the link is not coming up at all: skip to the BIOS in step 5.

Step 4 — Re-plug the cable and watch Device Manager

This one test tells you which half of the problem you have.

  1. Open Device Manager on the Debug PC and keep it visible.
  2. Unplug the Thunderbolt cable, wait a moment, then plug it back in.
  3. Watch the list closely as you re-plug.
Does the list refresh by itself?Then the link is alive and Windows is seeing something — this is a driver problem, and reinstalling the Thunderbolt driver is all you need. Install the Thunderbolt / USB4 driver and Control Center for your exact model from your motherboard or laptop maker’s support page, on the Debug PC (not the Target PC), then reboot and reconnect the cable. Most cases end right here.

No reaction at all when you re-plug? Continue with steps 5 and 6.

Step 5 — Turn Thunderbolt on in the BIOS

  1. Enter BIOS/UEFI, find Thunderbolt Support (or USB4) and set it to Enabled.
  2. Set Security Level to No Security. “User Authorization” silently blocks the card when Control Center is not installed.
  3. Save and exit, then reboot before testing again.
NoteOn many AMD USB4 boards this option is buried or named differently — the AI method below is the fastest way to find yours.

Step 6 — Check the Windows event log

  1. Open Event Viewer → Windows Logs → System and filter by source Kernel-PnP and WHEA-Logger.
  2. Those errors tell you whether the failure is link, power or firmware. Include them in your ticket, or paste them to an AI using the method below.

4. Don’t know your model? Let AI read your PC

Thunderbolt driver and BIOS problems depend on your exact motherboard, and the settings hide in different menus on every brand. The most accurate approach is to let an AI look at your real system and work it out — you do not need to know your model at all. Two ways, easiest first.

Option 1 — Generate a system report, hand it to any AI

Press the Win key, type PowerShell, open it, then paste the block below and press Enter. A Notepad file opens on your desktop — that is your report. It only reads information; it changes nothing.

$o = "$env:USERPROFILE\Desktop\zdma-report.txt"
"=== System ===" | Out-File $o
Get-CimInstance Win32_ComputerSystem | Select Manufacturer,Model | Out-File $o -Append
Get-CimInstance Win32_BaseBoard | Select Manufacturer,Product | Out-File $o -Append
(Get-CimInstance Win32_OperatingSystem).Caption | Out-File $o -Append
"`n=== Thunderbolt / USB4 controllers ===" | Out-File $o -Append
Get-PnpDevice | ? { $_.FriendlyName -match 'Thunderbolt|USB4|JHL|Ridge' } | Select Status,Class,FriendlyName | Format-Table -Auto | Out-File $o -Append
"`n=== Devices with a problem ===" | Out-File $o -Append
Get-PnpDevice | ? { $_.Present -and $_.Status -ne 'OK' } | Select Status,Class,FriendlyName | Format-Table -Auto | Out-File $o -Append
"`n=== Recent PnP / WHEA errors ===" | Out-File $o -Append
Get-WinEvent -FilterHashtable @{ LogName='System'; ProviderName='Microsoft-Windows-Kernel-PnP','Microsoft-Windows-WHEA-Logger' } -MaxEvents 15 -EA SilentlyContinue | Select TimeCreated,Id,Message | Format-List | Out-File $o -Append
notepad $o

Copy everything in that report and send it to an AI together with this prompt:

I have a ZDMA card (a Thunderbolt/USB4 DMA device) plugged into my Target PC, connected by a Thunderbolt cable to my Debug PC (the computer I operate), and the Debug PC's Windows won't detect the device. Below is a system report from that Debug PC. Based on it, tell me in plain language:
1. Does this machine actually have real Thunderbolt/USB4, and which port should I use?
2. The exact BIOS steps for THIS motherboard to enable Thunderbolt Support and set Security Level to No Security.
3. The exact Thunderbolt/USB4 driver + Control Center download for THIS model, and the install order.
4. What the Kernel-PnP / WHEA errors in the report mean - link, power, or firmware?
Ask me only for what's missing.

--- SYSTEM REPORT ---
[paste the whole report here]

Option 2 — Install an AI that reads your PC by itself

These tools can run commands on your PC, so you paste nothing — the AI collects the hardware information itself and diagnoses from it.

Chinese

Doubao

Free desktop assistant that can inspect your PC. The easiest choice if you prefer Chinese.


Technical

Claude Code

Runs in a terminal, reads your system and walks through fixes with you.


Technical

OpenAI Codex

An agent CLI that can run commands and troubleshoot on your machine.

Once installed, give it this prompt:

You can run PowerShell commands on my Windows PC. This PC is my Debug PC - the one I operate. A ZDMA card (a Thunderbolt/USB4 DMA device) is plugged into a separate Target PC and connected to this Debug PC by a Thunderbolt cable, but this Debug PC's Windows won't detect the device (it doesn't show in Device Manager, though the device's green light is on).

Don't ask me for hardware details - find them yourself. Run commands to collect: motherboard and system model, Windows version, any Thunderbolt/USB4 controllers and their driver status, any present devices whose status isn't OK, and recent Kernel-PnP and WHEA-Logger errors from the System event log.

Then tell me, in plain language:
1. Whether this machine has real Thunderbolt/USB4 and which port to use.
2. The exact BIOS steps for this motherboard to enable Thunderbolt Support and set Security Level to No Security.
3. The exact driver + Thunderbolt Control Center download for this model, and the install order.
Explain each step simply and wait for my confirmation before making any change.
Why this works betterWhen the AI reads your real system instead of a model number typed from memory, it cannot get your hardware wrong — and that is exactly the part that normally needs a PC expert.

5. Still stuck? Open a ticket with these ready

If all six steps and the AI still don’t get you there, it may be a hardware problem. Open a ticket and include the following so we can help on the first reply instead of asking back and forth:

  • Your motherboard or laptop model, exact — for example ASUS ProArt X870E.
  • Device Manager screenshot, with the card connected.
  • BIOS screenshot of the Thunderbolt / Security Level setting.
  • LED state — solid, blinking or off, and which port you used.
  • Your device SID, the number printed on the label.
  • Firmware history — did you flash any firmware, or is it still factory?
  • What you already tried, including the AI’s suggestions.

← Back to all tutorials

Scroll to Top