Writing a support ticket that gets solved on the first reply
What to put in your first message about a DMA or firmware problem. Includes a template you can copy and the habits that turn a five-minute fix into a five-day thread.
Short answer
Send all seven facts in one message and one thread: order ID, card model, motherboard model, and both Windows versions with build numbers. Add what changed since it last worked, what you already tried, and the exact error string as text, not a screenshot.
On this page9
- Why the first message decides how long a fix takes
- What to include in your first message
- A ticket template you can copy
- Where to find each fact
- Why you should copy the error as text
- What changed since it last worked?
- Habits that slow a ticket down
- Keep one problem in one ticket
- Common questions about support tickets
Why the first message decides how long a fix takes
Support for this kind of product is a diagnostic conversation, and every round trip costs you a day of waiting. A message that only says it does not work forces the first reply to be a list of questions. A message that answers those questions in advance lets the first reply be an answer instead. The information is the same either way, but giving it in the right order can save several days.
What to include in your first message
Put these seven things in the first message. If one of them is genuinely unknown, say so rather than leaving it out, because a stated unknown is also information.
- Your order ID on the first line, because it identifies what you own, which version you are entitled to, and your licence state
- The card model exactly as printed on the board, with a clear photo of the silkscreen and the FPGA marking
- The Windows version and build number for BOTH machines, using the full line from winver rather than just 10 or 11
- The motherboard model of the game PC, and of the second PC unless it is a laptop or mini PC
- The exact error string copied as text, including any numbers, brackets and hex values, plus the line before and after it
- What changed since it last worked. The candidates are a Windows update, a BIOS update, new RAM, a moved card, a new cable, a game patch, or nothing at all
- What you have already tried, with the result of each attempt rather than just a list
A ticket template you can copy
Fill in the lines and send them as one plain-text message. Every field is there because leaving it out has cost somebody a week.
ORDER ID: 12345
PRODUCT: (which firmware / kit / licence this ticket is about)
CARD: (model exactly as printed on the board, photo attached)
FIRMWARE: (image name and version, and the date it was flashed)
GAME PC: (motherboard model, CPU, RAM size)
GAME PC WINDOWS: (full line from winver, e.g. Version 24H2 Build 26100.xxxx)
SECOND PC: (model or motherboard, CPU)
SECOND PC WINDOWS: (full line from winver)
INPUT DEVICE: (model, and which port each cable is in)
DISPLAY PATH: (fuser or capture device model, or none)
ERROR (copied as text, not a screenshot):
DEVICE: FPGA: ERROR: Unable to connect to USB/FT601 device [0,v0.0,0000]
WHEN IT HAPPENS: (at launch / after N minutes / only in game / only after a restart)
LAST WORKED: (date, and what changed since)
ALREADY TRIED:
1. Full cold boot of both machines - no change
2. Second known-good USB 3 cable, rear port - no change
3. Regenerated the memory map - error moved to DTB
4. Disabled VT-d and VT-x in the game PC BIOS - not yet triedWhere to find each fact
All of these are read-only lookups, and together they take under a minute.
- Windows version and build
- Run winver. Send the whole line, including the build number after the dot
- Motherboard model
- Run msinfo32 and read the Baseboard rows, or read it off the board itself
- Card model
- The silkscreen printing on the PCB. Photograph it rather than transcribing it
- Error string
- Select it in the console window, copy, paste as text. Do not retype it from memory
- Read rate
- The figure from your read-speed tool, taken twice, with both numbers sent
- Order ID
- Your order confirmation, or the orders area of your account
Warning
Why you should copy the error as text
A screenshot cannot be searched or pasted into a bug tracker, and it loses the surrounding lines that identify which attempt failed. The numbers matter too. All-zero device values mean nothing came back over USB, while a real version number with a zero PCIe ID means the opposite. The digit after a DTB failure also says which method gave up. Select the text in the console window and copy it. If the window closes too fast to read, run the software from a command prompt so the output stays on screen.
Tip
What changed since it last worked?
Your answer to this question is the single most valuable sentence in a ticket. A build that never worked is a setup problem and gets a setup answer. A build that worked yesterday but not today is a regression, and the fix is usually whatever changed. Look for a Windows update on either machine, a game patch, a BIOS update, a reseated card, a swapped cable or a new monitor. If nothing changed, say exactly that. It is a legitimate and useful answer, and it points to heat, a marginal cable, or a card that is coming loose.
Habits that slow a ticket down
None of these habits are rude, but each one costs time, so the right-hand column shows what to send instead.
| Habit | Why it stalls the ticket | Send this instead |
|---|---|---|
| A screenshot of a chat message where someone else described your problem | It is second-hand, has no version information, and cannot be searched | Your own console output as text, plus the template fields |
| "It doesn't work" | It does not identify a layer, so the first reply has to be a questionnaire | The last thing that worked and the first thing that failed, with the exact string |
| Three tickets for the same problem | The history splits, and each responder sees a third of the facts | One thread, updated with new findings as replies |
| Pinging staff directly or in public channels | It moves you out of the queue and out of the thread that has your history in it | One message in the correct channel, then wait for the reply |
| Reporting five changes at once | Nobody can tell which change caused which result | One change per test, with the result of each |
| A photo of a monitor showing a console window | Unreadable numbers, and the numbers are the diagnostic | Copied text, and a photo only for physical things like the card silkscreen |
Keep one problem in one ticket
If a second, unrelated problem appears, open a separate ticket for it. Mixing a licence question, a card fault and an overlay alignment issue in one thread guarantees that two of the three are forgotten. Once a thread is open, keep adding to it instead of starting again, because its history is what stops you being asked the same question twice.
Common questions about support tickets
Do I need the order ID if I am asking a general question?
For a general question, no. For anything about a product you own, yes, because it identifies the version and licence state and saves a whole round trip.
How long should I wait before following up?
Wait one working day before you follow up, and make the follow-up new information rather than a reminder. Adding a test result moves the ticket forward, while asking whether anyone is there does not.
Should I include a video?
Only for something that is genuinely visual, such as an overlay drawing in the wrong place. For error messages, text is always better than video.
What if I cannot read the card model because the card is installed?
Say so and send what you have: the seller's listing name, the order, and a photo of whatever is visible. Do not guess at a model number, because a wrong model sends the whole ticket in the wrong direction.
Is it all right to admit I skipped a step?
Yes, and it is better than the alternative. An honest "not yet tried" leads to a fast fix, while a claimed step that was never done costs days.
Sources
This describes how this store's own support works, based on the tickets the team answers rather than on a published document.
Read next
Still stuck? Open a ticket on Discord
All guides