How to Get PC Build or Troubleshooting Help on the Linus Tech Tips Forums

Post in the right subforum, include your full hardware list and the exact symptoms, and treat replies as community advice rather than official support. The Linus Tech Tips (LTT) forums are a large, busy community — the excerpt shows post counts in the hundreds of thousands to over a million per section — so a clear, well-placed post is what gets you useful answers.

Pick the correct subforum first

The forum is split into sections, and posting in the wrong one is the most common reason a thread gets ignored or moved. Based on the forum index:

Your problem Where to post
Planning a new PC, asking for part lists or appraisals New Builds and Planning (under The Workbench)
Something is broken or behaving oddly Troubleshooting (under The Workbench)
GPU questions, overclocking, GPU faults Graphics Cards (under Computer Hardware)
CPU, motherboard, or RAM issues CPUs, Motherboards, and Memory
PSU questions or RMA experiences Power Supplies
Cooling, AIOs, custom loops Cooling
General tech chat that doesn't fit elsewhere General Discussion (The Hub)

The index also notes a general rule for The Hub: "Please check other subforums before posting." That applies across the board — scan the list before you commit to a section.

Before you post

  1. Search existing threads. With over a million posts in several sections, your exact problem has likely been discussed. The forum's own guidance is to check other subforums first, and the same logic applies to searching before starting a new topic.
  2. Read a few recent threads in your target subforum. Look at how solved problems are formatted — what details the original poster gave, and what responders asked for. This tells you what your post needs.
  3. Note that LTTStore.com merch questions are not handled here. The index states that section is "Not for support" and directs people to email [email protected]. Don't post store or order issues in the tech sections.

What to put in your post

A vague post like "my PC crashes" gets vague answers. Include:

  • Full hardware list — CPU, GPU, motherboard, RAM (capacity and speed), PSU (model and wattage), storage, and case. For build-planning posts, also state your budget and what the machine is for.
  • Exact symptoms — when it happens, how often, and whether it's reproducible. A thread in the excerpt, for example, is titled "360 Hz Monitor Black Screen Crash when Gaming" — that title alone tells a reader the trigger and the symptom.
  • What you've already tried — driver versions, reseating parts, BIOS settings, swapping components. This stops people from suggesting things you've done.
  • Error messages or codes — copy them exactly rather than paraphrasing.
  • Relevant context — was it working before? Did it start after a change (new part, update, overclock)?

For build-planning posts, add: target resolution and refresh rate, any size constraints (the excerpt shows a small-form-factor request that had to "fit in a backpack"), noise or aesthetics preferences, and your region if pricing matters.

What to expect from replies

  • Replies come from community members, not LTT staff. The forums are a peer-help space. There is no guaranteed official one-to-one technical support, and no promised response time.
  • Threads move fast. The index shows topics with timestamps ranging from "1 minute ago" to hours and days old, so a post can drop off the front page quickly. If you get no answer, add new information (a bump with a test result is more useful than a bare bump).
  • You may be redirected. If a moderator or user points you to a different subforum, repost there rather than arguing about placement.
  • Answers vary in quality. Cross-check advice against your hardware's official documentation before acting on it, especially for anything involving power, BIOS flashing, or overclocking.

Common pitfalls

  • Posting a build request in Troubleshooting (or vice versa) — it gets moved and you lose time.
  • Leaving out the PSU model. It's one of the most common causes of crashes and instability, and responders will ask for it anyway.
  • Assuming the forum is an official support channel. For warranty or RMA issues, contact the manufacturer directly — the excerpt shows users sharing RMA experiences (for example, a Seasonic RMA thread), but that's discussion, not a support ticket.
  • Posting merch or order problems in tech sections. Use the LTTStore support email instead.

Quick checklist

  • [ ] Problem type identified → correct subforum chosen
  • [ ] Existing threads searched first
  • [ ] Full hardware list included
  • [ ] Symptoms, triggers, and frequency described
  • [ ] Steps already tried listed
  • [ ] Error text copied exactly
  • [ ] Budget and use case included (for build planning)
  • [ ] Expectation set: community help, not official support
linustechtips.com