Skip to content

Hardware

Updated 2 min read

Windows-first hardware guides — buying, CPU, memory, storage, graphics, displays, laptops, builds, homelab servers and diagnostics, plus vendor hubs.

Hardware decisions and hardware evidence for Windows: what to buy, what Windows actually does with it, and how to prove a part is failing. No paper benchmarks, no logo walls.

55 guides · 10 topics · 2 vendor hubs · E1 documentation + E2 lab observations

Browse by topic

Where do you want to start?

Buying decisions, part-by-part references, and the diagnosis path when something is already broken.

Start with the boundary

Two vendor hubs, two support tiers

Tier is about official support and hardware availability, not brand preference. No performance claim without the hardware on the bench.

Why a vendor page

The driver is the platform

Windows does not ship the GPU driver; the vendor does. A “Windows tweak” that ignores the driver version is measuring the wrong thing.

  1. 01

    Driver branch

    Record the exact branch and package, not “latest”.

  2. 02

    Control panel

    Know which app owns the settings before changing them.

  3. 03

    Known issues

    Separate vendor bugs from Windows bugs.

  4. 04

    Build checks

    Record the Windows build and evidence level for each claim.

01

No logo wall

Vendor names are used for identification; no logo implies endorsement.

02

No paper benchmarks

No FPS number without the card, driver and test method.

03

Tier is explicit

Tier B is not “bad”; it is a different support and evidence boundary.