Guide 07 M2 to PCIe

Documentation snapshot: November 5, 2026. Community-reported guidance; GPU drivers, capture card firmware and Veyra versions may have changed. See Home for current links.

Veyra User Guide — 07 — M.2 to PCIe Guide

---

I. What Problem This Solution Solves

Internal (PCIe) capture cards have low latency and support 4K60 HDR, but plenty of people have no second PCIe slot at all:

• ITX / MATX boards where the single x16 slot is taken by the graphics card;
• the graphics card is so thick that it covers the x4 / x1 slots underneath;
• a small case where the side panel won't close once the card is in.

M.2 to PCIe simply means "borrowing an M.2 slot and using it as a PCIe x4 slot": you turn an M.2 slot on the motherboard (an NVMe drive slot) into a PCIe x4 slot and plug the capture card into it.

A group member's take: "If an M.2-to-PCIe adapter can run a graphics card, a capture card should work too, right?" — later testing showed that it does.

---

II. Can It Run at Full Bandwidth? Do the Math First

Capture format	Bandwidth required	Is M.2 to PCIe x4 enough?
4K60 NV12	~12.5 Gbps of payload	✅ Enough (PCIe 3.0 x4 ≈ 32Gbps)
4K60 YUY2	~16 Gbps	✅ Enough, but note that the card itself can't saturate a 10G port
4K30 HDR (P010)	~10 Gbps	✅ Enough
4K60 RGB24	~25 Gbps	⚠️ Marginal, and a motherboard Wi-Fi card pushes Max Payload down to 128B, so it may not run at full speed

Real-world test on record (group member Milk, 2026-10-10):

Running an AVerMedia GC573 through an M.2-to-PCIe adapter, it runs perfectly in SDR; in HDR it flashes white dots — but this card flashes white dots in an ordinary PCIe slot too, so it's not the adapter's fault (see the GC573 entry in document 04). The verdict, verbatim: "So M.2 to PCIe is workable."

The PCIe generation is not the issue: the GC573 needs x4, and testing showed "even 2.0 x4 works" (HM, 2026-10-28). But when bandwidth drops to 2.0 x4, YUY2 only reaches 50 fps and latency rises — working is not the same as working well.

---

III. Choosing an Adapter Board

Point	Notes
Connector type	An M.2 NVMe (M-Key) → PCIe x4 adapter board / riser socket, not SATA M.2
Length	The short version (10–20cm flexible ribbon) suits small cases; a rigid adapter socket needs no cable but is limited by case height
Power	Capture cards draw little power (most <10W), so no external power is usually needed; models with a 6pin connector are meant for graphics cards — they work with a capture card but aren't necessary
Mounting	⚠️ The adapter board has no bracket mount, so the card just "floats". A group member warned: "That external x4 thing of yours has nothing holding it — won't it fall out?" — do secure it with zip ties / double-sided tape / an acrylic bracket, and don't let the card's own weight press down on the adapter board
Price	30–120 yuan (adapter board) + optional bracket

---

IV. Which M.2 Slot to Use: The Most Critical Step

Prefer an M.2 slot wired directly to the CPU (usually the first M.2 slot, closest to the CPU, on the CPU's own PCIe lanes); an M.2 slot fed by the chipset (southbridge) takes a longer path, and both latency and stability are somewhat worse.

A group member, verbatim:

"Plug it into the M.2 that goes straight to the CPU." (Milk) "The design intent was surely the chipset slot — M.2 is just an unorthodox hack." (Remote_Sky) — a reminder: M.2 to PCIe is a tinkerer's workaround, not the officially recommended path; if you can use a real slot, use a real slot.

---

V. BIOS and System Settings (Where People Trip Up Most)

1. Disable the motherboard Wi-Fi card (if the adapter board sits on a chipset lane)

• Symptom: in HWiNFO, the PCIe "Max/Current Link Width" shows only a 128B Max Payload, and RGB24 4K60 doesn't reach full speed.
• Fix: turn Wi-Fi off in the BIOS (or keep only Bluetooth); someone in the group solved it by "disabling the wireless card, bridging wirelessly through the router, and then plugging in an Ethernet cable".
• How to tell: it should read 256/256; if you see 128, it's being throttled.

2. Turn on Above 4G Decoding / Resizable BAR (some boards won't detect the capture card without it).

3. PCIe link speed: Auto is fine; if the card isn't detected, try manually dropping it to Gen3.

4. Bifurcation: only needed if you want to split one x16 into x8+x8; an M.2 adapter doesn't require it.

---

VI. What You Give Up

• One M.2 drive slot (if it's your only system-drive slot, you can't play this game).
• One more dangling card and a ribbon cable inside the case; airflow and looks get worse.
• On some boards the M.2 slot sits below the graphics card, so you have to remove the graphics card to install or remove anything — which is exactly the problem the next document (08 PCIe Riser Guide) solves.

---

VII. Recommended Combinations (Verified in the Group)

Scenario	Combination	Notes
ITX board + want a 573	M.2-to-PCIe x4 adapter board + GC573	Perfect in SDR; the HDR white dots are the card's own problem
MATX + slots blocked by the graphics card	Use an M.2 adapter first, or run a riser cable down to the bottom of the case	See document 08
Only want 4K60 NV12	No need to bother: a 10G-port USB card is enough (T911 / G50)	Cheaper and simpler, 30–40ms latency

In one sentence: if all you want is 4K60 NV12, don't fiddle with M.2 — just get a T911 / G50; only for 4K60 HDR (P010) or ~5ms-class latency is M.2 to PCIe worth it.

---

VIII. Quick Fault Reference

Symptom	Cause	Fix
Capture card not visible in Device Manager	Adapter board not fully seated / M.2 slot disabled / Above 4G required	Reseat it, enable Above 4G in the BIOS, try another M.2 slot
Detected, but the capture software throws errors	The link only runs at x1 or 2.0	Switch to a CPU-direct M.2 slot; check whether it shares lanes with the graphics card
4K60 drops frames / only reaches 55 fps	Insufficient bandwidth or a 128B Max Payload	Disable the Wi-Fi card, change slots, drop the format to NV12
HDR flashing white dots / corrupted picture	Usually the capture card's own HDR compatibility problem (573)	Switch to SDR, or change the card
Not detected after waking from sleep	Power sequencing on the adapter board	Reboot, or disable USB/PCIe selective suspend