TechFuel HQ

Name: "TechFuelHQ Community GPU Undervolt Results"
Creator: TechFuelHQ
License: https://creativecommons.org/licenses/by/4.0/

Self-Hosted Read-It-Later Apps: Life After Pocket (2026)

LK Wood IV — Sat, 25 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-25 · Updated 2026-07-25 · ~11 min read · St. Louis County, MO

TL;DR · Decide whether you want to read or to organize

Pocket is gone — shut down 2025-07-08, data deleted from 2025-11-12 (not the October 8 date most write-ups repeat).
The export was URLs only. Mozilla's CSV did not contain your article text, so no migration carries your saved reading across.
Want to read? Readeck (0.22.3, AGPL-3.0) or wallabag (2.6.14, MIT) — both extract and store the readable article.
Want to organize links? linkding (1.45.0, MIT — one container on SQLite) or Shiori (1.8.0, MIT, single Go binary).
Want archive-everything at scale? That is the bookmark-manager end — see Karakeep vs Linkwarden.

Versions checked 2026-07-25 against each project's release API. Check the changelog before copying a compose file.

What actually happened to Pocket

Mozilla announced the phase-out on 2025-05-22, writing that it had “made the difficult decision to phase out two products: Pocket, our read-it-later and content discovery app, and Fakespot” (Mozilla). The service shut down on 2025-07-08 and dropped into export-only mode.

Here is the part almost every write-up gets wrong. The original announcement said data would be deleted after October 8, 2025, and that date is what got copied across the internet. It was superseded. Mozilla’s own support article states plainly: “As of November 12, 2025, user data export has been disabled, and all user data has been queued for permanent deletion” — the same date the Pocket API was switched off (Mozilla Support, via Internet Archive). If you are reading this in 2026 wondering whether your list is still recoverable: it is not.

Two details matter more than the dates, because they shape what a replacement can actually do for you:

The export was a CSV of links. Mozilla’s instructions told users to click “Export CSV file” at getpocket.com/export, and the support article is explicit that the file contains the URLs of saved items rather than the article text (Mozilla Support, via Internet Archive). Ten years of saved reading came back as a spreadsheet of addresses.

Every official escape route was another cloud. Mozilla published a list of “third-party services that we understand support the import of Pocket data” — GoodLinks, Futurwise, Instapaper, Matter, Raindrop.io and Readwise — while explicitly stating it had not vetted them (Mozilla Support, via Internet Archive). Every one is hosted. Not a single self-hosted option appeared — which is the whole reason this page exists.

Read-it-later or bookmark manager? Answer this first

Most “Pocket alternative” lists quietly mix two different products, and it is the single biggest source of disappointment when people migrate.

A read-it-later app is built around consuming an article. It extracts the readable text, strips navigation and ads, and gives you a reader view — the thing Pocket actually was.
A bookmark manager is built around organizing and preserving links, usually with a full-page snapshot so the page survives link rot. Excellent at recall; not necessarily a nice place to read.

Self-hosting threads keep re-litigating this, with people pointing out that a given “Pocket alternatives” roundup is mostly bookmark managers, and others arriving at the same conclusion after trying half a dozen tools. If your goal is “I want to read these six articles on the couch tonight,” a bookmark manager will technically store them and still leave you unsatisfied.

This page covers the reading end, plus the lightweight link-organizers people most often reach for as Pocket replacements — some of which describe themselves as bookmark managers, and are included here precisely because that overlap is where the confusion lives. What this page does not try to settle is heavyweight archival at scale: the two strongest options there get a dedicated head-to-head in Karakeep vs Linkwarden, which resolves the organize-versus-archive split within that category.

The tools, by the job they do

Readeck — the closest thing to “Pocket, self-hosted”

Readeck describes itself as an app that “lets you save the precious readable content of web pages you like and want to keep forever” (Readeck on Codeberg). That framing is the point: it is a reader first, an archive second.

Current stable is 0.22.3, released 2026-04-16, under AGPL-3.0, with the repository actively updated as of this writing (verified via the Codeberg API on 2026-07-25). It is the tool that comes up most often in self-hosting threads as the recommendation over the heavier options, usually on resource-efficiency grounds — though that is community sentiment, not a benchmark.

wallabag — the veteran, and the one with real export

wallabag is the veteran option here. It is explicitly a content-extraction app — its README describes saving a web page and keeping only readable content, built on the Graby and php-readability extraction stack (wallabag README).

Current stable is 2.6.14, released 2025-10-07, under the MIT license, with commits on the default branch as recently as 2026-07-24. It is a PHP application requiring PHP 7.4+ and a PDO database — SQLite, MySQL/MariaDB, or PostgreSQL (requirements) — and the documented Docker quick-start runs on SQLite (installation).

Two things wallabag has that most of this field does not: in-article annotations and highlights (annotations docs), and per-article export to ePUB, PDF, XML, JSON and CSV, including exporting a whole category at once (download docs). If you want saved articles on an e-reader, that is the feature to look at. It also ships first-party Android and iOS apps plus the wallabagger browser extension.

Honest counterweight, from self-hosting threads rather than the docs: wallabag’s initial setup gets criticised for requiring an OAuth client ID and secret on top of a username and password, and one long-time user reported Android sync degrading past roughly fifteen thousand saved articles. Both are single data points, but the scale ceiling is the only concrete one anyone named in this space.

linkding — minimal, fast, and archiving is opt-in

linkding is positioned as a minimal, fast, Docker-first bookmark manager, and it is the tool the community reliably names when someone asks which is snappiest. Current stable is 1.45.0, released 2026-01-06, under the MIT license, on a steady cadence (five stable releases between 2025-08-16 and that date). It is a Django app using SQLite by default, with PostgreSQL optional (no MySQL), and its image runs on ARM including Raspberry Pi.

The detail that surprises people: server-side archiving is not in the base image. HTML snapshots live in the latest-plus variant, which drives singlefile-cli against a headless Chromium, and whose documentation asks for at least 1 GB of RAM to run that Chromium (linkding archiving docs). linkding can also push pages to the Internet Archive instead of storing snapshots locally. So the “linkding is light” reputation applies to the base image — which is not the archiving one.

Shiori — one Go binary, slow and steady

Shiori is a bookmark manager distributed as a single Go binary, usable as a CLI or a web app, and explicitly modelled on Pocket (Shiori README). It does archive page content by default, parsing readable content and storing an offline copy. Current stable is 1.8.0, released 2025-09-26, MIT licensed, with SQLite by default and PostgreSQL/MySQL/MariaDB available.

The honest caveat is velocity: the project’s own FAQ describes it as maintained but slow-moving, with a single primary active maintainer (Shiori FAQ), and the browser extension is self-declared beta. The last stable release is the oldest of the four here — though the default branch had commits as recently as 2026-07-10, so this is a pace-and-bus-factor risk, not an abandoned project.

Footprint and capability, side by side

Versions verified 2026-07-25 from each project’s release API.

	Readeck 0.22.3	wallabag 2.6.14	linkding 1.45.0	Shiori 1.8.0
Primary job	Read saved articles	Read + annotate + export	Organize links fast	Organize links, single binary
License	AGPL-3.0	MIT	MIT	MIT
Latest release	2026-04-16	2025-10-07	2026-01-06	2025-09-26
Stores readable text	Yes	Yes (Graby extraction)	Base image: no; `latest-plus`: HTML snapshot	Yes, offline archive by default
Database	See Readeck docs	SQLite / MySQL / PostgreSQL	SQLite default, PostgreSQL optional	SQLite default, PostgreSQL / MySQL
Notable extra	Reader-first design	ePUB export, annotations	Internet Archive integration, ARM/Pi	CLI + web from one binary
Documented RAM figure	none published	none published	≥1 GB for `latest-plus` (Chromium)	none published

Nobody in this category except linkding publishes a RAM figure, and linkding’s is specifically for the archiving image. Treat any “uses only X MB” claim you read elsewhere as unverified unless it names a version and a workload.

What the Pocket export actually gives you

If you still have a CSV you exported before 2025-11-12, understand what it is before you plan a migration.

It is a list of URLs and metadata. Your new app will re-fetch each page itself — which means the result depends entirely on whether those pages still exist and still serve their content to a server-side fetcher. Pages that died, went behind a paywall, or now require JavaScript in the years since you saved them will not come back. One self-hoster hit exactly this warning while importing into Readeck; another reported a painless import into Karakeep. Both are single data points, and they are not contradictory — the import mechanics differ by tool, but the missing-article-text problem is Pocket’s, not the importer’s.

The lesson generalises past Pocket: a service that only stores your links is one shutdown away from being a list of 404s. That is the argument for running a tool that extracts and stores the article text — Readeck, wallabag, Shiori’s default archive, or linkding in its archiving image — rather than one that keeps only the URL.

Gotchas the project docs don’t mention

These come from self-hosting community threads rather than documentation. Each is one or a few data points — corroborate before betting on them.

Paywalled and JS-heavy pages need the browser, not the server. The recurring workaround is the SingleFile browser extension: your logged-in browser renders the page, then pushes that snapshot into the app. Server-side crawlers get blocked precisely because they are not you. This one is not folklore — linkding documents the SingleFile-to-API upload path directly (linkding archiving docs).
Cookie banners get archived too. They are part of the rendered page, and users report consent overlays dominating captured copies at scale.
Reddit archiving was broken across tools as of June 2026 — one user reported Karakeep, Readeck with SingleFile, Linkwarden and linkding all failing to render post content, with a maintainer replying in the same thread (r/selfhosted). Timestamped deliberately: this is the kind of thing that gets fixed, so re-check before assuming.
“Archived” and “readable offline in the app” are different claims. One Karakeep user found the offline copy existed server-side but was not viewable in the iOS app. Test the phone path specifically.
Resume-reading position is a feature people repeatedly miss. Its absence is cited across separate threads as the reason users abandoned an otherwise good tool.

Which one should you run?

Choose Readeck if you want the closest thing to what Pocket was — a reader-first app whose job is making saved articles pleasant to read, with a current release and an active repo.

Choose wallabag if you want the mature option, annotations, and above all ePUB export to get saved articles onto an e-reader. Accept a heavier PHP stack and a fiddlier initial setup.

Choose linkding if speed and a tiny footprint matter more than reading experience, and you either do not need local archiving or are willing to run the latest-plus image with the RAM that Chromium wants.

Choose Shiori if you want one binary, no database server, and a CLI — with open eyes about a single-maintainer pace.

Choose neither, and read the bookmark-manager comparison instead, if what you actually want is durable full-page archival with heavy organization across thousands of links. That is a different job, and Karakeep vs Linkwarden resolves it.

Whichever you pick, it belongs on the same box as the rest of your stack — see self-hosted apps that replace SaaS for how this fits alongside the other dozen services worth running, and back it up: a reading archive you never backed up is a reading archive you will eventually lose, which is exactly what the 3-2-1 backup rule is for.

Karakeep vs Linkwarden — the bookmark-manager end of this category, organize vs archive
Self-hosted apps that replace SaaS — where a read-later app ranks against the other candidates
BookStack on Docker — for docs you write, rather than pages you save
Paperless-ngx setup — the same archive-and-search idea, for scanned paper
The 3-2-1 backup rule — because a self-hosted archive is only as good as its backups

Sources

https://blog.mozilla.org/en/mozilla/building-whats-next/ — Mozilla’s phase-out announcement (2025-05-22)
https://web.archive.org/web/20260502145211id_/https://support.mozilla.org/en-US/kb/future-of-pocket — Mozilla Support, shutdown and deletion dates (archived; the live host is behind a bot challenge)
https://web.archive.org/web/20250802094606id_/https://support.mozilla.org/en-US/kb/future-of-pocket — earlier capture of the same page, carrying the third-party import list (archived)
https://web.archive.org/web/20260420164430id_/https://support.mozilla.org/en-US/kb/exporting-your-pocket-list — Mozilla Support, export format (archived)
https://codeberg.org/readeck/readeck — Readeck source, releases and license
https://readeck.org/en/docs/ — Readeck documentation
https://raw.githubusercontent.com/wallabag/wallabag/master/README.md — wallabag extraction stack
https://doc.wallabag.org/admin/installation/requirements/ — wallabag requirements
https://doc.wallabag.org/admin/installation/installation/ — wallabag Docker quick-start (SQLite)
https://doc.wallabag.org/user/articles/annotations/ — wallabag annotations
https://doc.wallabag.org/user/articles/download/ — wallabag export formats
https://github.com/sissbruecker/linkding — linkding source, releases and license
https://linkding.link/installation/ — linkding installation and image variants
https://linkding.link/archiving/ — linkding archiving, latest-plus, SingleFile and the 1 GB RAM figure
https://raw.githubusercontent.com/go-shiori/shiori/master/README.md — Shiori design, storage backends and license
https://raw.githubusercontent.com/go-shiori/shiori/master/docs/faq.md — Shiori FAQ, maintenance pace

Community reports. The gotchas section and the tool-by-tool caveats draw on r/selfhosted threads read via a front-end mirror; the canonical thread URLs are below. Each is community sentiment — usually one or a few data points — not an authority, and is labelled as such in the body.

https://www.reddit.com/r/selfhosted/comments/1ktgzpf/ — the Pocket-shutdown thread
https://www.reddit.com/r/selfhosted/comments/1sc0vpd/ — “What bookmark manager are you currently using?”
https://www.reddit.com/r/selfhosted/comments/1ea8w8o/ — “Current favourite read-it-later app — Readeck”
https://www.reddit.com/r/selfhosted/comments/1u4a11c/ — Reddit archiving broken across tools (June 2026)
https://www.reddit.com/r/selfhosted/comments/1pqspwj/ — “Still no true Omnivore read-it-later replacement?”
https://www.reddit.com/r/selfhosted/comments/1gr87l0/ — “Read it later application”
https://www.reddit.com/r/selfhosted/comments/1fu8l1s/ — self-hosted read-it-later recommendations
https://www.reddit.com/r/selfhosted/comments/186rsrv/ — wallabag scale and sync reports
https://www.reddit.com/r/selfhosted/comments/1q12fw3/ — Karakeep 2025 wrapped (maintainer post; treat as vendor claim)
https://www.reddit.com/r/selfhosted/comments/1pi72bt/ — Linkwarden mobile launch (maintainer post; treat as vendor claim)

What PSU Does an RTX 5070 Need? (2026)

LK Wood IV — Sat, 25 Jul 2026 00:00:00 -0500

650W. That is NVIDIA’s own minimum system power figure for the RTX 5070, a card rated at 250W total graphics power, and for most builds it is the right number to buy rather than a bare floor. Where it stops being right is a 200W-plus processor or a planned upgrade to a bigger card — both push you to 750W. A genuinely efficient build can sit on 550W, with one caveat worth knowing before you shop.

Here is where each of those numbers comes from.

The card’s actual power specification

Specification	RTX 5070
Total graphics power (TGP)	250W
NVIDIA required system power	650W
Power connectors	2x PCIe 8-pin (adapter in box), or one 300W-or-greater PCIe Gen 5 cable

Two things in that table matter more than the headline. First, the 250W is the card, while the 650W is the system — NVIDIA’s figure already carries an allowance for a processor, drives, and fans, which is why it lands 400W above the card itself. Second, the 5070 does not force you onto a 12V-2x6 cable: it ships with an adapter for two ordinary 8-pin PCIe connectors, so an older quality supply is still in play.

What a 5070 build actually draws

The graphics card is the biggest single number but not the whole story, and the processor swings the total more than anything else. Summing real component draw the way our PSU calculator does — 45W for an ATX motherboard, 5W per RAM stick, 8W for a Gen4 M.2 drive, 2W per case fan, 12W for an AIO, plus a 10W miscellaneous allowance — a reference build of two RAM sticks, one M.2 drive, four fans and an AIO adds 93W on top of the card and processor. That puts a 5070 build here:

Your processor	Example	System peak	Smallest PSU that works	Comfortable choice
65W	Ryzen 5 9600X	~408W	550W	650W
120W	Ryzen 7 7800X3D	~463W	650W	750W
170W	Ryzen 9 9950X	~513W	650W	750W
250W	Core i9-14900K, unrestricted	~593W	750W	850W

“Smallest that works” is peak draw plus a 20% margin, rounded up to a size actually sold. “Comfortable” is one size above that, putting your peak near 60-70% of the rating — workable and quiet, with room for a future card. Worth knowing if you also run the tool: its headline recommendation targets nearer half load, so it will suggest a larger unit than this column. Both are defensible; this table is the smaller, cheaper end of the range.

Whether a given processor will hold the card back in games is a separate question from what it costs you in watts — the PC bottleneck calculator answers that one for a specific pairing.

Notice that the mainstream gaming row lands exactly on NVIDIA’s 650W — a useful cross-check on the arithmetic, though NVIDIA does not publish the build behind its figure. Vendor minimums tend to be deliberately worst-case, so treat the agreement as confirmation rather than as proof they assumed this exact build. Either way, the recommendation moves the moment your CPU does.

When 650W is not the answer

Go to 750W if your CPU is a flagship. A 9950X or an unrestricted 14900K can pull more than double what an X3D gaming chip draws, and that difference lands entirely on your power budget. The 250W row above peaks at 593W — on a 650W unit that is 91% load, past the point where a supply is working hard enough to get loud and to risk tripping protection.

Go to 750W if you plan to upgrade the card. A 5070 Ti is a 300W card and NVIDIA’s minimum for it is 750W — so that upgrade costs you nothing extra if you buy 750W now. A 5080 is different: 360W, and NVIDIA asks for 850W, so stepping up to one is a power-supply purchase as well as a card purchase. If you are weighing that decision now, the RTX 5070 vs 5070 Ti comparison covers what the extra 50W buys you.

You can consider 550W if the build is genuinely lean — an efficient 65W processor, one drive, no AIO. The arithmetic supports it — that build peaks near 394W, which a 550W unit covers with margin. The practical caveat is a shopping one rather than an electrical one: in our experience shopping the category, quality ATX 3.x units below 650W are thin on the ground, so the 550W shelf skews older. If a good 550W and a good 650W are twenty dollars apart, take the 650W.

Transient spikes, honestly

Graphics cards draw in bursts rather than a flat line, and this is where PSU advice usually turns into “buy double.” It should not.

Intel’s ATX 3.0 design guide requires a compliant unit to survive excursions up to 200% of its rated wattage for 100 microseconds, with lower brackets for longer events. That headroom is already in the standard, but only under both conditions at once: the unit must be above 450W and ship a native 12V-2x6 connector. A 650W supply with that cable meets the bar; a 650W supply without one does not. Smaller units, or ones lacking the connector, are held to a lower requirement.

The practical translation for a 5070: on a compliant modern unit, size for your sustained peak plus the headroom in the table above and stop padding for spikes. On an older ATX 2.x supply, leave more room, because it was never designed against those brackets. The full methodology, including where every coefficient comes from, is published on the PSU calculator.

The connector

The 5070 accepts either two PCIe 8-pin cables — an adapter is in the box — or a single PCIe Gen 5 cable rated 300W or higher. Neither is more “correct”; the native Gen 5 cable is simply tidier and avoids stacking an adapter behind the card.

If you use the 12V-2x6 connector, seat it fully until it clicks and do not put a sharp bend right at the plug. The current design shortens the sense pins specifically so that a plug which is not fully seated fails to deliver full power rather than making partial, high-resistance contact.

If you already own the power supply

Check the label on the unit itself rather than guessing from the case badge. Most supplies report nothing to Windows — there is no standard sensor for it — so the label is the reliable answer; only high-end units with digital monitoring report telemetry, and then through their own software. What you want is the continuous 12V rating, not the peak sticker number. If the unit is multi-rail, follow the manual’s rail distribution and give the card its own cables instead of daisy-chaining one pigtail.

A supply that is merely old is not automatically a problem, but one that is failing looks a lot like one that is undersized — random shutdowns under load, reboots in games. PSU failure symptoms covers how to tell those two apart before you spend money on the wrong fix.

Lowering the number

Undervolting is the one free lever here. Dropping a card’s voltage cuts real wattage while holding clocks, and the effect is big enough to matter: at the roughly 50W our own results database reports for a mid-range card, the 120W-CPU build above falls from 463W to 413W — enough to drop it a PSU size — while running cooler and quieter. The complete GPU undervolting guide covers the method, and our undervolt results database lists what other owners actually measured card by card.

For where the 5070 sits against its alternatives on raw speed, see the GPU hierarchy; for the AMD side of this decision, the RTX 5070 vs RX 9070 comparison covers both power and performance.

Sources

NVIDIA GeForce RTX 5070 official specifications — total graphics power, required system power, and supplementary power connectors — RTX 5070 family specifications, verified live 2026-07-25. The RTX 5070 Ti figures (300W, 750W) come from the same page.
NVIDIA GeForce RTX 5080 official specifications — the 360W total graphics power and 850W required system power cited in the upgrade section — RTX 5080 specifications, verified live 2026-07-25.
Intel ATX 3.0 desktop power supply design guide — the power-excursion brackets and the wattage/connector conditions that qualify a unit for them (Intel ATX 3.0 PSU power excursion).
Component draw coefficients and the sizing rules used in the build table are this site’s own published figures, listed in full in the PSU calculator methodology.

What PSU Does an RTX 5080 Need? (2026)

LK Wood IV — Sat, 25 Jul 2026 00:00:00 -0500

850W. That is NVIDIA’s required system power for the RTX 5080, a card rated at 360W, and for a normal build it is the number to buy rather than a floor to argue with. The variable that catches people out is not the processor — it is which 5080 you bought. A factory-overclocked board draws roughly 60W more than a Founders Edition, and at the top of the CPU range that difference is worth an entire power-supply tier.

The card’s actual power specification

Specification	RTX 5080
Total graphics power (TGP)	360W
NVIDIA required system power	850W
Power connectors	3x PCIe 8-pin (adapter in box), or one 450W-or-greater PCIe Gen 5 cable

Both connector figures moved up from the RTX 5070, which asks for two 8-pins or a 300W Gen 5 cable. That matters on an upgrade: an older supply with two spare 8-pin cables may not have a third, and a Gen 5 cable rated for a 5070 is not necessarily rated for this card. Check the cable, not just the wattage on the box.

Which 5080 did you buy?

This is the question that decides your answer, and it is specific to this tier. Summing component draw the way our PSU calculator does — 45W for an ATX board, 5W per RAM stick, 8W for a Gen4 M.2, 2W per fan, 12W for an AIO, plus a 10W miscellaneous allowance, so 93W for a reference build of two sticks, one drive, four fans and an AIO — the two variants land like this:

Your processor	360W Founders-class card	~420W factory-OC card
65W	518W peak → 650W	578W peak → 750W
120W	573W peak → 750W	633W peak → 850W
170W	623W peak → 750W	683W peak → 850W
250W	703W peak → 850W	763W peak → 1000W

Sizes are peak draw plus a 20% margin, rounded up to a wattage actually sold — the smallest unit that works, in the calculator’s language, not the most comfortable one. As on the 5070 page, one tier above each figure is the quieter, longer-lived choice. Read across any row: the overclocked board costs you a tier on its own — same silicon, different power target.

Our own reference card is the overclocked kind, and we have logged it. Across a 25-minute gaming session on the ASUS ROG Astral RTX 5080 OC — 308 HWiNFO64 samples on the hand-tuned profile — board power averaged 261W and peaked at 326W. That is comfortably under the ~420W the calculator uses for an overclocked board, which is the point: you size a supply for the worst case it must survive, not for the average it will usually see.

Notice that our arithmetic for a Founders-class card with a mainstream CPU lands at 750W, below NVIDIA’s 850W. That is not a gap to exploit. Vendor minimums tend to be worst-case, and NVIDIA’s note on the RTX 5090 is the one place they show their assumption — that figure is based on a system built around a Ryzen 9 9950X, a flagship chip. Read their 850W as covering the bottom of that table rather than the middle, and buy it.

When 850W becomes 1000W

Three things push you up, and they stack:

A factory-overclocked board — roughly 60W over a Founders-class card.
A processor at or above 200W. A Ryzen 9 9950X sits right around 200W by our calculator’s figure; an unrestricted Core i9 goes well past it and lands you in the bottom row.
Manual overclocking or a raised power limit, which moves the card past its stock target entirely.

Any two together make 1000W the sensible buy. Whether a given processor limits your frame rate rather than your power budget is a different question — the PC bottleneck calculator covers that one.

Transient spikes, honestly

A 360W card draws in bursts rather than a flat line, and this is where PSU advice usually becomes “buy double.” It should not.

Intel’s ATX 3.0 design guide requires a compliant unit to survive excursions to 200% of its rated wattage for 100 microseconds, with lower brackets for longer events — but only where both conditions hold: the unit is above 450W and ships a native 12VHPWR / 12V-2x6 connector. An 850W ATX 3.x supply with that cable meets the bar; one without the native cable does not, whatever its wattage.

So on a compliant modern unit, size for sustained peak plus the headroom in the table and stop padding for spikes. On an older ATX 2.x supply paired with a 5080, leave more room — it was never designed against those brackets. The full methodology is published on the PSU calculator.

The undervolt that can buy a tier back

The 5080 sits right on a tier boundary, which makes undervolting worth more here than the raw watts suggest. Curve undervolting a 5080 is widely reported to cut 30–70W depending on where your silicon lands, and our own RTX 5080 undervolt guide uses that published range rather than a single number, because the spread between chips is the whole point.

Against the table above, even the middle of that range matters. A ~420W overclocked card with a 120W processor peaks near 633W and wants 850W; take 50W off and it peaks near 583W, which a 750W unit covers.

The honest caveat is that you cannot bank it in advance. Silicon varies, the range is wide, and a PSU has to cover the case where your card undervolts poorly. Buy for the stock figure, undervolt afterwards, and treat the saving as headroom you gained rather than money you saved. Our undervolt results database lists what specific cards achieved, with the source behind each row.

If you are coming from a smaller card

Sizing for an RTX 5070 is a different exercise — 250W, 650W of system power, two 8-pins — and it is covered in what PSU an RTX 5070 needs. Moving from a 5070 to a 5080 is genuinely a power-supply purchase as well as a card purchase, worth budgeting before the card arrives rather than after. For where both land on raw speed, see the GPU hierarchy.

Sources

NVIDIA GeForce RTX 5080 official specifications — total graphics power, required system power, and supplementary power connectors — RTX 5080 specifications, verified live 2026-07-25.
NVIDIA GeForce RTX 5070 specifications, for the upgrade comparison — RTX 5070 family, verified live 2026-07-25.
Intel ATX 3.0 desktop power supply design guide — the excursion brackets and the wattage/connector conditions that qualify a unit (Intel ATX 3.0 PSU power excursion).
NVIDIA GeForce RTX 5090 specifications — the note stating its minimum-system-power figure is based on a system configured with a Ryzen 9 9950X — RTX 5090, verified live 2026-07-25.
The ~420W figure for a factory-overclocked 5080 is this site’s own sizing estimate, taken from the GPU list in the PSU calculator; it is a conservative peak for sizing, not a measured gaming draw.
The 261W average / 326W peak board-power figures are our own first-party telemetry: 308 HWiNFO64 samples across a 25-minute gaming session on the hand-tuned profile, published in the ROG Astral RTX 5080 OC review with the raw dataset.
The 30–70W curve-undervolting range is the published community range cited in our RTX 5080 undervolt guide.
Component draw coefficients and sizing rules are this site’s own published figures, listed in full in the PSU calculator methodology.

GPU Undervolt Settings Database: Real Results by Card (2026)

LK Wood IV — Fri, 24 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-24 · ~6 min read · St. Louis County, MO

Undervolting is one of the highest-value ten-minute tweaks in a PC — but the single question everyone asks is “what settings should I actually use for my card?” Published guides give a method; this page gives data: an open, crowdsourced table of real undervolt settings and the results people measured, one row per tested configuration.

It is the data companion to our complete guide to undervolting your GPU, which walks through the method itself on both NVIDIA and AMD. Use that to learn how; use the table below to see where other people’s cards landed.

The results

Each row is a real, sourced result. NVIDIA rows list the MSI Afterburner voltage-frequency point (voltage @ clock); AMD rows list the Adrenalin offset (or, on RDNA 3, the absolute max voltage) plus any power-limit change. Where a number was not measured, the cell is blank rather than guessed.

8 verified results CC BY 4.0 · updated 2026-07-24 · open dataset

Community GPU undervolt results — measured settings and outcomes, one row per tested configuration. Sourced; contribute your card by pull request.
GPU	Method & setting	Power saved	Temp drop	FPS change	Stability test	Source
RTX 5080ASUS ROG Astral OC	950 mV @ 2750 MHz, power limit 90%MSI Afterburner V/F curve	~50 W	—	±0% (parity)	Settings follow the worked example in our RTX 5080 undervolt guide; the ~50W saving sits inside the 30-70W range that guide cites from community testing at hardware review sites. Not a logged before/after measurement on our own card.	TechFuel HQ
RX 9070 XTSapphire NITRO+	-100 mV offset (power limit left at stock)AMD Adrenalin voltage offset	—	—	+10%	Stress-tested in a demanding game after stepping the offset down from -40 mV; validated in real play, not just a short benchmark	www.xda-developers.com · 2
RTX 4090	940 mV @ 2700 MHz (+1200 memory)MSI Afterburner V/F curve	~100 W	—	±0% (parity)	Loop a demanding title / stress test (instability shows as crashes or black screens). FE silicon often stable ~925 mV; AIB cards ~950-975 mV.	forums.overclockers.co.uk · 2
RTX 4080 Super	950 mV @ 2760 MHzMSI Afterburner V/F curve	~50 W	~8°C	±0% (parity)	Extended in-game / ray-tracing stress test (not just synthetics); some cards need +12-25 mV in heavy RT titles.	evezone.evetech.co.za · 2
RTX 5090	900 mV @ 2800 MHz (flatten curve above the point)MSI Afterburner V/F curve	~100 W	~10°C	-2%	Several hours in a memory-heavy title (Cyberpunk 2077 / Monster Hunter). Verify your Afterburner build supports 50-series curve editing.	www.overclock.net · 2
RTX 5070 Ti	935 mV @ 2955 MHz (via +450 MHz core offset), +1500 memoryMSI Afterburner V/F curve	~50 W	—	+4%	Flatten the V/F curve at the target point; achievable clock at 935 mV varies by card (~2932-2945 MHz measured on the source unit).	www.esportstales.com · 2
RX 7900 XTX	1100 mV max voltage (~-50 mV vs ~1150 mV stock), power limit +15%AMD Adrenalin max voltage (RDNA3 absolute)	—	—	±0% (parity)	Lower max voltage in 10-15 mV steps; if it crashes/black-screens, raise 10-15 mV and retest (an invalid UV just resets on reboot). Validate with 15-20 min stress + 20-30 min gameplay.	tier1settings.com · 2
RX 9070	-100 mV offset, -30% power limit (efficiency-biased)AMD Adrenalin voltage offset	—	—	-7%	-100 mV reported daily-stable; community reports crashes past ~-170 mV. This is an EFFICIENCY tune: the -30% power limit trades ~7% FPS for large power/thermal savings. A milder -80 to -100 mV at 0% power limit is the performance-neutral option.	www.notebookcheck.net · 2

Have results for your card? This is an open dataset — add a row by pull request against data/undervolt_results.json. Submit a pull request against https://github.com/iBlessi/gpu-undervolt-db adding one object to the "results" array in data/undervolt_results.json. The repository's .github/PULL_REQUEST_TEMPLATE.md fills in automatically with the required fields and methodology, and an automated check validates schema, plausibility, and sourcing on every PR. Every numeric value must cite a resolvable source.

How to read it

Method & setting — the exact tune. NVIDIA cards undervolt through the MSI Afterburner voltage-frequency curve (pin a low-voltage point to your stock clock); AMD cards use a negative voltage offset in Adrenalin.
Power saved / temp drop — the efficiency win at the same performance. This is where the value is on most cards.
FPS change — usually ±0% (same frames, cooler and quieter). A positive number means the card was power-limited, so freeing voltage let it boost higher — the reason the RX 9070 XT can gain about 10% FPS.
Silicon lottery — treat every row as a starting point, not a guarantee. Two identical cards can need 25–50mV apart. Start conservative, test, and step down.

None of the seed rows is a logged first-party before/after run yet — they are community-consensus settings, community-verified results, and review-measured values, each with its source linked in the table. Our own RTX 5080 and RX 9070 XT guides are where those settings are worked through. First-party measured rows are exactly what this database is built to accumulate, starting with submissions.

Contribute your card

This dataset grows by submission, and the submissions repository is now open: github.com/iBlessi/gpu-undervolt-db. There is no login to create, no account, and no backend — git is the moderation queue. To add your result:

Undervolt your card (our guide covers the method) and record what you changed and what you measured.
Fork the repo and add one object to the results array in data/undervolt_results.json, then open a pull request. The submission template fills in automatically with the field guide and checklist — the card, the offset or voltage curve you set, and the numbers you measured.
An automated check runs on your PR. It blocks on hard problems — malformed schema, impossible values, a missing source — and warns on statistical outliers, which can still merge but are held out of the table above until a maintainer confirms them. You can run the same check locally with python scripts/undervolt_outlier_flag.py --check.

Prefer not to use GitHub? Email hello@techfuelhq.com with the same information and we will open the pull request for you.

The only hard rule is honesty: every number should trace to something real — a review, a forum thread, or your own screenshot. Unmeasured fields stay null. Implausible submissions are flagged and held out of the table until reviewed.

What the data shows so far

Undervolting is almost free performance. Across every card here, the tuned result is the same frames (or a few more) at meaningfully lower power and temperature.
The bigger the card, the bigger the win. A 575W RTX 5090 or 450W RTX 4090 reclaims ~100W; a mid-range card saves ~50W. The power & cost calculator turns those watts into dollars per year.
Power-limited cards gain FPS. The RX 9070 XT is the clearest example — undervolting lets it hold higher clocks within its power budget.
The consensus voltages are tight. Modern NVIDIA cards cluster at 900–950mV; RDNA 4 AMD cards at -80 to -100mV. That convergence is exactly what a crowdsourced dataset is good at confirming.

Sources and methodology

Every row cites its source in the table. Community rows link to the review or forum thread the numbers came from; rows drawn from our own guides link to the guide that works the settings through. The dataset is published under CC BY 4.0, and the field definitions and contribution rules travel with it in the file’s own meta block. If you find an error, open a pull request against the repository or email hello@techfuelhq.com with the card and the correction — corrections are treated the same as new submissions and are checked against a source before the table changes.

How to Undervolt Your GPU: The Complete Guide (2026)

LK Wood IV — Fri, 24 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-24 · ~9 min read · St. Louis County, MO

What undervolting actually does

Every graphics card leaves the factory with more voltage than it strictly needs. AMD and NVIDIA program a voltage-frequency curve that has to keep the worst chip of a given model stable, so most cards run higher voltage at a given clock than their particular silicon requires. Undervolting reclaims that margin: you tell the card to run the same clocks at a lower voltage.

The payoff comes in one of two forms, depending on your card:

Lower heat, power, and noise at the same performance. Less voltage means less power turned into heat, so temperatures drop, fans spin slower, and the card is quieter — with the same frame rates.
A few more frames. On a card that runs into its power limit under load (common on higher-end GPUs), lowering voltage frees up power budget, and the boost algorithm spends it on higher sustained clocks. That’s why undervolting can come out slightly faster, not slower.

It is one of the highest-value ten-minute tweaks in a PC, it costs nothing, and it’s fully reversible. This guide covers the method for both brands; for card-specific settings and measured results, it links down to our worked examples on a NVIDIA RTX 5080 and an AMD RX 9070 XT.

Before you start: baseline your card

You can’t tell an improvement from a placebo without a reference point. Run a demanding game or a benchmark for 10–15 minutes with a monitoring overlay (HWiNFO64, or AMD’s built-in metrics), and note four numbers under sustained load:

Core clock (the sustained clock, not the momentary boost spike)
Core voltage (VID / SVI)
Power draw (board watts)
Temperature — watch the hotspot / junction temperature, not just the edge temperature

Those are the numbers you’re trying to beat: same or higher clock, at lower power and temperature.

NVIDIA: the MSI Afterburner curve

NVIDIA cards are undervolted through MSI Afterburner’s voltage-frequency curve editor — the same tool works across every NVIDIA card, and on AMD cards too. The method:

Download and open MSI Afterburner and press Ctrl+F to open the curve editor — a graph of clock (MHz) against voltage (mV).
Note where your card runs at stock under load (from your baseline). Pick a lower voltage target — around 0.9V (900mV) is a widely used, safe starting point — and drag that point up to your stock sustained clock.
Flatten the curve to the right of your chosen point so the card can’t climb back to higher voltages, then click Apply.
Stress test (below). Once stable, save the profile and enable “apply at startup” so it loads every boot.

The idea is simple: you’re forcing the card to hit its normal clock at a lower voltage, and capping it there. For the full curve-editor walkthrough with measured before/after numbers on a current card, see the RTX 5080 undervolt guide.

AMD: the Adrenalin voltage offset

AMD makes this easier — everything is built into AMD Software: Adrenalin Edition, so there’s no third-party tool. Rather than editing a curve point by point, you apply a negative voltage offset across the whole curve:

Press Alt+R to open Adrenalin, go to Performance → Tuning, and set the Tuning Control to Custom.
Enable GPU Tuning and lower the voltage with a negative offset — start conservative at around -40mV.
Optionally enable Power Tuning and trim the power limit (around -10% as a mild starting cut keeps performance closest to stock while lowering temperatures; deeper cuts trade performance for efficiency).
Apply, stress test, and step the offset deeper (toward -80 to -100mV) as stability allows.

The RX 9070 XT undervolt guide covers the Adrenalin controls, the community-converged offsets, and the efficiency-versus-performance trade in full. Older AMD cards and ASUS cards can also use GPU Tweak III, but the Adrenalin route works on any modern Radeon.

Test for stability (don’t skip this)

An undervolt that looks fine for five minutes and crashes an hour into a game is worse than no undervolt. Test it properly:

Run a demanding, real game or a benchmark like 3DMark for at least 15 minutes — longer is better.
Watch for crashes, driver timeouts (a black screen that recovers), or artifacts — these mean the voltage is too low for the clock you set. Raise the voltage (NVIDIA) or reduce the negative offset (AMD) slightly and retest.
A common trap: an undervolt can pass a heavy all-core stress test but crash at lighter loads, so play normally for a few hours before you trust it.

When a setting survives real use, you’ve found your card’s stable point. Save it.

What to expect

Results vary by chip and by game — no two cards are identical — but the pattern is consistent: lower temperatures and power draw, quieter fans, and either the same or slightly better performance. On efficiency-focused cards the win is mostly thermal and acoustic; on power-limited, higher-end cards, undervolting can recover a few percent of performance on top. The power & cost calculator turns the watts you save into an annual dollar figure, and the PSU wattage calculator sizes a supply for the card’s real peak.

Card-specific guides and the CPU too

The steps above are the general method; the exact voltages and results depend on your specific card. For measured, step-by-step walkthroughs:

RTX 5080 undervolt guide — the NVIDIA / MSI Afterburner curve, tuned for efficiency and 24/7 AI-inference use.
RX 9070 XT undervolt guide — the AMD / Adrenalin offset, including why this power-limited card can gain FPS.

And to see where other people’s cards landed — the RTX 4090, 5090, RX 7900 XTX and more — the GPU undervolt settings database is an open, crowdsourced table of real settings and their measured results. Look up your card, or add yours by pull request.

And undervolting isn’t only for the GPU. Modern AMD CPUs undervolt through Curve Optimizer, which follows the same logic — lower voltage, freed headroom, cooler or faster. If you run a Ryzen X3D chip, the 9800X3D undervolt guide applies the same idea to the processor.

Pick your card, follow the method, and test it honestly. Ten minutes buys a cooler, quieter, and often slightly faster GPU, for free.

Sources

The general method (MSI Afterburner voltage-frequency curve for NVIDIA; ~0.9V as a common safe starting target; AMD Adrenalin for Radeon cards) reflects the long-established, widely-documented consensus across community guides and vendor documentation, and is applied with measured, card-specific numbers in our linked RTX 5080 and RX 9070 XT guides.
How-To Geek — 8 Tips for Undervolting Your Gaming GPU (AMD Adrenalin method; per-game profiles) — verified live 2026-07-24
MSI Afterburner is the free NVIDIA/AMD tuning utility used for the curve method; download it from MSI’s official Afterburner page.
Card-specific measurements and community-consensus settings are cited in the linked RTX 5080 and RX 9070 XT undervolt guides.

PC Part Prices 2026: Verified Reference Dataset

LK Wood IV — Fri, 24 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-24 · Updated 2026-07-25 · ~6 min read · St. Louis County, MO

What this is — verified 2026 PC part prices, honestly dated

30 parts, 7 categories — CPU, GPU, motherboard, RAM, storage, PSU, case — with real 2026 street prices.
Most re-verified 2026-07-24 (23 of 30 parts); the other 7 keep their earlier 2026-06-09 date. Each part carries its own last_verified date — check it before you rely on a number.
This is a point-in-time reference, not a live tracker. We date the prices instead of pretending they are real-time.
Open data (CC BY 4.0). Fork it, remix it, or build your own tracker on top of it — attribution required.

Prices move — GPUs, RAM, and SSDs most of all. Confirm the live price at the retailer before you buy.

The short version

This page is a browsable window into the TechFuelHQ PC Builder parts dataset — 30 off-the-shelf components with verified 2026 street prices. The one thing most price pages get wrong is freshness honesty: they show a number without telling you when it was true. Every price here is stamped with the date it was last checked, and most of those dates are now 2026-07-24 — the prices were re-verified against live US retailer listings that day — while a few parts whose exact new SKU couldn’t be re-confirmed keep an earlier 2026-06-09 date.

That means two things, stated plainly. First, on their verification date these were real, sourced street prices — not MSRP fiction. Second, prices move, and a figure verified weeks ago is a planning reference, not a checkout guarantee. Confirm the live price at the retailer before you buy. Honest data freshness is the whole point of this page.

When these prices were last verified

23 of the 30 parts were re-verified on 2026-07-24, against live US retailer listings (primarily Amazon). The other 7 keep their earlier 2026-06-09 date — we only move a date when we actually re-confirm the price, never as a cosmetic bump. The parts still at 2026-06-09, because their exact new standalone SKU couldn’t be confirmed at re-verification, are the Intel Core i5-14600K and Core Ultra 7 265K, the RTX 5080 Founders Edition (not sold at Amazon retail), the Corsair Vengeance DDR5-7200 kit, the Corsair HX1000i power supply, and the Fractal Pop Air Mini and Meshify 2 Compact cases. There is no live scraping — verification is a deliberate manual pass, which is why we show each date rather than hide it.

How to read the staleness:

Within ~30 days of the verified date — treat the figures as current-enough for build planning.
30–90 days out — still a useful band, but re-check anything volatile (GPUs, DDR5 kits, NVMe SSDs) at the retailer, because 2026’s memory-price swings have been sharp.
Beyond ~90 days — use the ranges for rough planning only, and expect the next verification pass to have moved several numbers.

The prices are street prices, not manufacturer MSRP — compiled from retailer listings and manufacturer pages, so they reflect the discounts and markups you would actually pay, as of the verification date.

2026 PC part prices by category

Most parts re-verified 2026-07-24 (the dataset carries per-part dates). These are mid-to-upper mainstream picks — a realistic build-planning band, not the cheapest possible part or the halo flagship.

Category	Parts	Price range	Re-verified 2026-07-24
CPU	6	$176 – $445	4 of 6
GPU	6	$445 – $1,844	5 of 6
Motherboard	5	$176 – $549	5 of 5
RAM (DDR5)	3	$149 – $1,000	2 of 3
Storage (NVMe SSD)	3	$350 – $600	3 of 3
Power supply	3	$115 – $239	2 of 3
Case	4	$79 – $160	2 of 4
Whole dataset	30	$79 – $1,844	23 of 30

For the individual parts — exact model, price, socket, TDP, and its own last_verified date — the interactive PC Builder is built on the same dataset and does the compatibility math for you, or you can read the raw JSON directly.

Why a verified snapshot, and not a live tracker

A live price tracker sounds better than a dated snapshot until you ask what keeps it honest. A tracker that scrapes prices continuously is only as trustworthy as its last successful scrape — and when a scrape silently fails, it shows a stale number with no warning that it is stale. A dated snapshot has the opposite failure mode: the number might be old, but you always know exactly how old, because the date is right next to it.

For a reference dataset that other people cite and build on, that trade is worth making. This is the deliberate, light version: verified dates and honest staleness labels, not a real-time feed we cannot promise to keep accurate. If and when a live tracker is warranted, it will be built as its own thing — not bolted onto a reference dataset where it would quietly erode the one property that makes the data worth trusting.

Where the prices come from

Per the dataset’s own methodology note, 2026 street prices are compiled from manufacturer product pages, TechPowerUp, Tom’s Hardware, and verified retailer listings (Amazon, Newegg, Micro Center). Performance-tier labels in the dataset are TechFuelHQ editorial assessments based on aggregate review consensus — except where a part appears in a TechFuelHQ open bench dataset, in which case its tier is anchored to first-party measurements. Treat them as rough tiering, not head-to-head benchmark claims.

Use the data (CC BY 4.0)

The PC Builder parts dataset is released under Creative Commons Attribution 4.0. You may share and adapt it, including commercially and including building your own price tracker on top of it, as long as you attribute TechFuelHQ and link back.

Attribution line (copy-paste):

TechFuelHQ PC Builder Parts Dataset (CC BY 4.0). https://techfuelhq.com/tools/pc-builder/

The raw JSON carries the per-part last_verified dates, so a downstream tracker can key off them directly.

PC Builder — interactive parts picker — the same dataset, with interactive compatibility and PSU-wattage checks
TechFuelHQ Datasets — the dataset home, license posture, and provenance
DDR5 RAM buying guide — why RAM prices sit high in 2026
$2,500 7800X3D + RTX 5080 4K build — where these parts land in a real build

Sources

https://techfuelhq.com/data/pc-builder-parts.json — the dataset, with per-part last_verified dates
https://creativecommons.org/licenses/by/4.0/ — CC BY 4.0 license
https://www.techpowerup.com/ and https://www.tomshardware.com/ — price-compilation sources named in the dataset methodology
The dataset’s _meta methodology note is the canonical, full source list (it also names manufacturer product pages and the retailer listings — Amazon, Newegg, Micro Center — the street prices were checked against)

The 3-2-1 Backup Rule for Homelabs (2026)

LK Wood IV — Fri, 24 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-24 · Updated 2026-07-24 · ~12 min read · St. Louis County, MO

TL;DR · 3 copies, 2 devices, 1 off-site — and RAID is none of them

The rule. Three copies of your data, on two different devices, with one copy off-site. Your live data is copy 1, so you still need two more.
RAID is not a backup. It is redundancy for uptime. A deletion, a ransomware run or a bad update hits every disk in the array at once.
A snapshot on the same box is not a backup either. A ZFS snapshot lives in the same pool it protects — it dies with the pool.
The off-site copy is the one people skip, and it is the one that survives fire, theft and flood. Cloud object storage (B2, S3) or a box at another building.
3-2-1-1-0 adds one immutable/air-gapped copy (defeats ransomware) and zero errors (verify and test-restore).

This page is the platform-agnostic strategy. The tool and per-platform how-tos live in the linked guides — pick your three copies here first, then go implement them.

The short version

The 3-2-1 rule is one sentence: keep three copies of your data, on two different media, with one copy off-site (Backblaze). It is usually traced to photographer Peter Krogh’s The DAM Book, though vendors hedge the attribution and even disagree on the year, so treat the origin as folklore and the rule as the point.

Almost every explanation of it online is written by an enterprise backup vendor selling immutable cloud storage. The rule is sound; the framing assumes a data center. This guide translates it for the machine in your basement — and spends most of its length on the two things those pages gloss over, because they are the two things homelabbers actually get wrong: RAID is not one of the three copies, and neither is a snapshot on the same box.

Get the three copies right conceptually first. The tool you use to move bytes is a later, smaller decision.

What the three numbers actually mean

3 — three copies, and your live data is one of them. Your three copies are your original production data plus two more (Backblaze). In a homelab, the files on your NAS or server that you use every day are copy 1. So you already hold one of the three — you need two more copies, not three from scratch. Enterprise framing counts differently: it treats the production data as the data rather than a copy at all — a distinction homelabbers argue over directly (r/DataHoarder). For a home lab, three copies including the original is the usual and reasonable target.

2 — two different media, which today means two different devices. The original rule said two media types — the classic example was disk plus tape. Modern guidance relaxes that: you store the data on two different storage media “such as a local drive and a cloud storage service” (Backblaze). So a local disk and a cloud bucket already satisfy the “2.” The reason the “2” exists at all is common-mode failure: two identical drives, bought together and run under identical conditions, tend to fail together. Nakivo puts it plainly — keeping all your backups “on the same type of storage media makes it more likely that both devices would fail at about the same time due to a defect or simple wear and tear” (Nakivo). The homelab-practical reading of the “2”: don’t put every copy on drives from the same batch.

1 — one copy off-site, far enough that one disaster can’t take all three. Keep one copy “off-site in a remote location, ideally more than a few miles away from your other two copies to protect against natural and physical disasters” (Backblaze). A NAS and a second backup disk in the same room are still one house fire away from total loss. This is the copy people skip, and it is the copy that matters most.

RAID is not a backup. Neither is a snapshot on the same box.

This is the heart of it, and it is where the homelab community is as close to unanimous as it ever gets.

RAID gives you redundancy for uptime — the array keeps serving while you swap a failed drive. That is genuinely valuable, and it is not a backup. On a fresh r/selfhosted thread asking exactly whether RAIDZ counts as one of the 3-2-1 copies, the original poster was downvoted to zero and the answers were blunt: “Raid is NOT a backup! Raid is a redundancy against a drive failure and nothing more” (r/selfhosted). The clearest statement of why came from someone actively replacing a dead drive: “raid is for uptime… But if I change a file or delete it on accident then it’ll still be gone from the entire system. Raid doesn’t help with that” (r/selfhosted).

The list of what RAID does not protect against is exactly the list of things that actually kill homelab data: “fat-fingering an rm -rf, ransomware encrypting the array, a bad update corrupting data, or the whole box getting stolen or fried in a fire. All of those replicate across every disk in the array instantly because RAID doesn’t know the difference between a good write and a mistake” (r/selfhosted). A mirror is the same trap: delete a file and it is deleted on the mirror too.

Snapshots are the subtler version of the same mistake. A ZFS snapshot is “a read-only copy of a file system or volume” (OpenZFS) — but it lives inside the same pool as the data it captures. It “initially consume[s] no additional space within the pool,” growing as the active data changes (OpenZFS). Because it shares the pool’s disks, it shares the pool’s fate: pool fails, snapshots gone. A snapshot protects against you deleting a file by accident. It does nothing about the disks themselves dying, or the machine being stolen. It is not one of your three copies until it has been sent somewhere else.

So: run RAID for availability if you want it, take snapshots for fast rollback — both are good. Just count zero of your three copies against either one.

Choose your three copies before you choose a tool

The mistake is starting from “which backup software should I use.” Start from where each copy physically lives, and the tool falls out of that almost automatically.

Copy 1 — live data: already exists, on your NAS, server or desktop.
Copy 2 — local backup: a separate disk or a separate box, on-site. This is the copy you restore from fastest when something breaks, because it is on your own network rather than at the far end of a home internet connection. One r/DataHoarder commenter framed the whole point of the on-site copy cleanly: “The primary backup is the one that provides the fastest data recovery” (r/DataHoarder).
Copy 3 — off-site: cloud object storage, or a machine somewhere else.

Only once you know where a copy lands do you pick the software, and the destination decides it: a cloud bucket points you at restic or Kopia, an SSH box at Borg — that comparison picks the file-level tool by where the backup lands, and corrects the four-year-stale myth that restic has no compression. restic writes directly to Amazon S3 and Backblaze B2 (restic docs); Kopia targets S3-compatible storage, B2, GCS and Azure (Kopia docs); and rclone bridges to “over 70 cloud storage products” if you just need to push an existing backup set off-site (rclone).

The off-site copy: how to actually build copy 3

This is the copy most homelabs never finish, so make it the one you automate first.

For a file-level off-site copy, automated off-site backups with restic builds exactly this leg end to end — a Backblaze B2 repository on a systemd timer, client-side encryption and deduplication, a 7-daily / 4-weekly / 6-monthly retention policy, and monitoring on failure, at roughly $1.40/month for 200 GB (Backblaze B2 is $6.95/TB/month). It assumes copies 1 and 2 already exist and builds copy 3.

Two things the tutorials can’t decide for you, but this strategy layer should flag:

If your backup client holds credentials that can delete, so can whatever compromises that client. If the machine being backed up is breached, unrestricted credentials sitting on it can wipe the repository — the exact scenario off-site backup exists to survive. Turn on object lock or versioning at the bucket, and scope the client’s key to write-and-list without delete. Hardening the off-site copy this way is also how most homelabs satisfy the “+1 immutable” of 3-2-1-1-0 — the same copy 3, made immutable, rather than a separate fourth copy.
Egress costs at restore time. Cold-storage tiers are cheap to fill and expensive to empty. As one r/DataHoarder thread warned about Glacier specifically: “Before you store anything at all in Glacier make sure you understand the cost of getting your files out” (r/DataHoarder). The cheapest storage tier is not the cheapest backup if you ever have to restore from it in a hurry.

The per-platform how-tos

The strategy is platform-agnostic; the implementation is not. Two common homelab stacks have a native path:

Proxmox. If your data lives in VMs and LXC containers, Proxmox Backup Server in a 3-2-1 layout builds copies 2 and 3 for you — a deduplicated local datastore, incremental backups that read and send only the delta, SHA-256 verification, and an off-site leg via a sync job to a second PBS or restic to B2. PBS deduplication means “periodic backups produce large amounts of duplicate data… the deduplication layer avoids redundancy and minimizes the storage space used” (PBS docs), so retaining many restore points stays affordable.

ZFS. If you are on ZFS, Sanoid and Syncoid automate the snapshot policy and then replicate it off the box — Syncoid “facilitates the asynchronous incremental replication of ZFS filesystems” (sanoid). That replication step is the important one: it is what turns a same-pool snapshot (not a backup) into a genuine second or third copy on separate hardware.

Both are implementations of the same three copies. Neither replaces the strategy on this page; they execute two legs of it.

3-2-1-1-0: the modern extension, and why ransomware forced it

The classic rule predates ransomware that specifically hunts backups. So vendors extended it. Veeam’s version: “we extended the rule to 3-2-1-1-0. It adds one immutable copy, and results in zero recovery errors” (Veeam).

The extra 1 — one offline, air-gapped or immutable copy (Veeam community). This is the copy malware cannot reach or rewrite. One mechanism is write-once-read-many storage: immutable backups “cannot be modified or deleted” (Nakivo), which matters because “ransomware increasingly targets backups. If your only protection is connected to your network, it can be compromised” (Veeam). In a homelab this is typically your off-site copy 3 with object lock on a B2 or S3 bucket, or a copy you physically disconnect — you harden an existing copy rather than add a whole new one. Sync alone is not enough — if a device is compromised and its files are encrypted, “if you don’t notice in time then it will eventually propagate to ALL your backups being unreadable” (r/DataHoarder).

The 0 — zero errors, which means you verify and test-restore. A job that reported success is not a backup you can restore until you have proven it. For restic, run check regularly, and add --read-data so it verifies “the actual pack files on disk,” catching bit rot rather than only structural consistency (restic docs). For Proxmox Backup Server, “it is recommended that you reverify all backups at least monthly, even if a previous verification was successful” (PBS docs). And beyond automated checks, restore a real file on a schedule. The pointed r/DataHoarder version of this: “So… have you tested your restore processes?” (r/DataHoarder).

The gotchas that never make it into the diagram

Five things from real homelab setups that the clean vendor version omits:

Two copies on drives from the same batch can fail as one. During the SanDisk Extreme SSD failures, people “were getting bitten by having all three copies of their data on three different Sandisk Extreme SSDs, all of which were from the defective batch” (r/DataHoarder). This is the real reason the “2” exists — mix brands or manufacture dates.
The RAID rebuild is when the second drive dies. A real anecdote of a second disk failing mid-rebuild, twice: “The first time it was rebuilding a raid5 and everything was lost. The second time it was rebuilding a raid6 because I learned” (r/DataHoarder). Redundancy is most fragile exactly when you are leaning on it.
Paying a cloud provider is not the same as them backing up your data. “Unless specified in the SLA for whatever you pay for, it’s better to assume that there is no backup of your data” (r/DataHoarder). Commodity object storage is durable, not versioned-for-you.
On-site is usually the primary because it restores fastest, not because it’s safer. “restoring 100TB from a local backup takes me a couple days vs a few weeks to restore from an off-site backup over the internet” (r/DataHoarder). Bandwidth, not location, decides which copy you reach for first.
A backup that doesn’t run automatically doesn’t run. Schedule it, monitor it, and alert on failure — the difference between a backup plan and a good intention is a timer and a notification.

restic vs Borg vs Kopia: which backup tool — pick the file-level tool by where the backup lands
Automated off-site backups with restic — build copy 3 to Backblaze B2, scheduled and monitored
Proxmox Backup Server in a 3-2-1 layout — copies 2 and 3 for VMs and LXCs, with dedup and verify jobs
Sanoid and Syncoid for ZFS snapshots — the snapshot layer, and the replication that turns it into a backup
Proxmox vs TrueNAS vs Unraid as a storage backend — picking the box these copies live on
Best NAS hard drives — and why they shouldn’t all come from the same batch

Sources

9800X3D Undervolt Guide: Curve Optimizer Done Right

LK Wood IV — Thu, 23 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-23 · ~9 min read · St. Louis County, MO

The first X3D chip AMD actually let you tune

For two generations, X3D tuning was only half available. The 5800X3D and 7800X3D stacked 3D V-Cache on top of the compute die, which trapped heat, so AMD locked manual multiplier and voltage control to protect the cache. Curve Optimizer itself was not off-limits — plenty of 7800X3D owners ran PBO with negative offsets — but you could not set a fixed clock above AMD’s boost ceiling.

The Ryzen 7 9800X3D removed that last limit. AMD reversed the stack this generation, placing the cache beneath the cores for better heat transfer, and the chip ships with full official overclocking support — as SkatterBencher puts it, “for the first time, the X3D also gets official overclocking support.” So here you get Curve Optimizer and real multiplier and PBO headroom. (If you’re still deciding whether to make the jump, we covered that in 7800X3D vs 9800X3D.)

Decide which outcome you want first

This is where most guides go wrong. Undervolting a 9800X3D does not automatically make it cooler — what the freed headroom becomes depends entirely on your power limits:

The efficiency path. Apply a negative offset and leave the stock limits alone (120W TDP, PPT 162W). The chip needs less voltage for the same clocks, so it draws less power and runs cooler at effectively the same performance. This is what most people actually want.
The performance path. Apply a negative offset and let Precision Boost Overdrive spend the headroom. The chip converts the savings into higher sustained clocks. SkatterBencher measured a -40 all-core offset taking voltage from about 1.13V down to ~0.998V at 5.1 GHz, landing roughly 5,425 MHz all-core and a geomean gain near 4.8% over stock. Temperatures did not fall — they logged 84.6°C average in OCCT, because PBO deliberately spends thermal headroom on frequency.

Pick one before you start. “Undervolted and still hitting 85°C” is not a failure; it means you chose the performance path.

Know your stock numbers

Worth having in front of you. The architecture and clock figures are AMD’s published specs; the Precision Boost 2 limits below are SkatterBencher’s measurements of the stock configuration:

Stock parameter	Value
Cores / architecture	8-core Zen 5, 3D V-Cache
Base / boost clock	4.7 GHz / up to 5.2 GHz
TDP	120W
PPT / TDC / EDC	162W / 120A / 180A
Programmed Fmax	5,250 MHz
Maximum VID	1.40V

Step 1: Baseline before you touch anything

Run a repeatable load for 10–15 minutes and record it. HWiNFO64 alongside your workload is what most tuners use. Note:

Effective clock under sustained all-core load (not the idle boost spike)
Core voltage (VID / SVI) at that load
Package power and peak temperature
A score you can repeat — Cinebench multi-core, or your actual game with a benchmark scene

Without a baseline you can’t tell an improvement from a placebo. For where the chip sits against other CPUs before you tune, the CPU comparison tool and CPU hierarchy give you the stock reference points.

Step 2: Find Curve Optimizer in your BIOS

Curve Optimizer lives under Precision Boost Overdrive, but every vendor buries it slightly differently, and menu names shift between BIOS versions. The usual paths:

ASUS: Ai Tweaker → Precision Boost Overdrive → Curve Optimizer
MSI: OC → Advanced CPU Configuration → AMD Overclocking → Precision Boost Overdrive → Curve Optimizer
Gigabyte: Tweaker → Advanced CPU Settings → AMD Overclocking → PBO → Curve Optimizer
ASRock: OC Tweaker → AMD Overclocking → Precision Boost Overdrive → Curve Optimizer

On most boards you must first set Precision Boost Overdrive to Advanced (or Enabled) before the Curve Optimizer submenu appears. If you’d rather test from Windows first, AMD Ryzen Master exposes the same control — find your value there, then commit it in BIOS so it applies at boot.

Step 3: Set a conservative negative offset

The setting has two parts: a sign (Positive or Negative — you want Negative) and a magnitude (a unit-less number, larger = more aggressive undervolt).

Set sign to Negative, magnitude to 10. Save and reboot.
Test (Step 5). If stable, step the magnitude down by 5 at a time.
Stop one or two steps above your first instability, not at it.

Most owners settle somewhere between -15 and -30. SkatterBencher ran -40 all-core on their sample — good silicon, and part of a full overclocking configuration rather than a daily-driver efficiency profile. Published values are starting points to test, never settings to copy: the entire reason Curve Optimizer exists is that no two chips are identical.

All-core vs per-core. All-core applies one number everywhere and is limited by your weakest core. Per-core lets you push strong cores harder while keeping weak ones stable, which is why experienced tuners increasingly favour it — at the cost of considerably more testing time. Start all-core to get the easy win; move to per-core if you want the last few percent.

Step 4: Only if you want the performance path

If you chose performance rather than efficiency, this is where you spend the headroom. SkatterBencher’s configuration used:

PBO Scalar: 10X — raises the ceiling on how much voltage the chip may request (SkatterBencher’s run moved maximum all-core voltage from roughly 1.35V to about 1.370V). Be clear on what this setting actually does: it relaxes AMD’s silicon reliability target, taking FIT from 1,991.1 to 19,911 in the same measurements — a tenfold increase in the accepted failure-in-time budget. That is a longevity trade, not a free lever.
Max CPU Boost Clock Override: +200 MHz
PBO limits: Motherboard profile

This step is overclocking, not undervolting. AMD classifies Precision Boost Overdrive as an overclocking feature, and overclocking sits outside AMD’s standard processor warranty — check AMD’s current warranty terms before you enable it. A negative Curve Optimizer offset on stock limits is a different proposition; this is the part that carries real cost.

Understand the trade before you apply it: this configuration is what produced ~5,425 MHz all-core and ~4.8% more performance — and 84.6°C in OCCT. You are converting your undervolt into clock speed, not into cooling. Skip this section entirely if lower temperatures were the goal.

Step 5: Test for stability the right way

Curve Optimizer has a genuinely counterintuitive failure mode: an unstable undervolt usually crashes at idle or light load, not under an all-core stress test. When that instability shows up as a blue screen rather than a silent reboot, the stop code is usually CLOCK_WATCHDOG_TIMEOUT — a core that stopped responding, which is exactly what a too-deep offset produces. The reason is where each load sits on the voltage-frequency curve. A sustained all-core load actually runs at a lower voltage — roughly 1.13V at 5.1 GHz on this chip — while light and single-threaded work boosts to the highest clocks at much higher VID, up toward the 1.40V ceiling in the table above. Those light-load, high-frequency points, and the rapid boost transitions around them, are where a too-deep offset leaves a core short. So:

Do run a heavy load (OCCT, Cinebench, Prime95) — it catches thermal and power problems
But also leave the machine idling on the desktop, browsing, and playing normally for a few hours — that’s where an over-aggressive offset shows itself
Watch for random reboots, WHEA errors in Event Viewer, or crashes on wake — all classic signs the offset is too deep
Fix by reducing magnitude by 5 and retesting

A single-core load test (Cinebench single-core, or CoreCycler if you want to be thorough per-core) is more revealing here than an all-core one.

What to expect

Realistically, on the efficiency path most owners report a meaningful drop in load temperatures at effectively unchanged performance — community reports on r/overclocking describe all-core temperatures falling roughly 10°C with the same or slightly better performance. On the performance path, SkatterBencher’s verified figure is the reference: ~4.8% geomean for a -40 offset with PBO pushed.

Neither result is guaranteed on your chip. Silicon lottery is real, your cooler and case airflow set the ceiling, and a board with a weak VRM will limit what’s achievable regardless of offset. For thermal context on what X3D parts should actually be running at, see safe CPU temperatures in 2026.

Worth doing?

For a chip this thermally dense, yes — it’s ten minutes in BIOS for either a cooler, quieter machine or a few percent more performance, with a clean rollback (clear CMOS). Note the split above, though: the undervolt itself is the free part — the Step 4 PBO settings are overclocking, and carry a warranty and longevity trade. It’s the same logic that makes GPU tuning worthwhile on power-limited cards — see how to undervolt your GPU for the graphics-card side, or the RX 9070 XT undervolt guide for a worked example. Just decide which of the two outcomes you’re chasing before you start, and test at idle as seriously as you test under load.

Sources

SkatterBencher — SkatterBencher #82: Ryzen 7 9800X3D Overclocked to 5750 MHz (stock PB2 parameters, Curve Optimizer -40 voltage/frequency results, PBO Scalar and boost-override settings, OCCT temperature and the +4.84% geomean figure) — verified live 2026-07-23
Ryzen 7 9800X3D specifications (8-core Zen 5, 4.7 GHz base / 5.2 GHz boost, 120W TDP, 96MB L3, AM5, second-generation 3D V-Cache with the cache relocated beneath the cores — the change that makes it the first overclockable X3D part) reflect AMD’s published figures, cross-checked across multiple independent launch reviews and corroborated by the stock measurements in the cited SkatterBencher article.
Community-reported undervolt outcomes (typical -15 to -30 offsets, ~10°C load-temperature reductions, per-core preferred over all-core, and the well-documented pattern that Curve Optimizer instability surfaces at idle or light load rather than under an all-core stress test) are drawn from the r/overclocking and r/pcmasterrace AM5 tuning threads and are presented as community consensus, not first-party measurements.

Authelia vs Authentik: Which Self-Hosted SSO (2026)

LK Wood IV — Thu, 23 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-23 · Updated 2026-07-23 · ~11 min read · St. Louis County, MO

TL;DR · The whole SERP is arguing about a stale fact

"Authelia is only forward-auth" is wrong. Authelia has shipped an OpenID Connect provider since v4.29.0 (May 2021) and is OpenID Certified to five profiles. Apps that speak OIDC can use it directly.
But it is still an open beta. Authelia's own roadmap says so, with General Availability not yet started and no single-logout. Certified and beta are both true — every other guide picks one and drops the other.
Authentik no longer needs Redis — removed entirely in 2025.10. The current compose file is three services: PostgreSQL, server, worker. Every guide still listing Redis is out of date.
Ignore the quoted RAM figures. The 30MB-to-1GB spread across other guides comes with no config, no version and no method on any of them. Authelia on a SQLite file is one container, which plausibly explains the low end — but only Authentik publishes a documented minimum (2 CPU / 2GB, for its Compose install). Authelia publishes none.
Authentik's free tier is complete for a homelab. OIDC, SAML, LDAP, SCIM, RADIUS are all open source; Enterprise gates provisioning and compliance, not the protocols.

Versions verified against the GitHub release APIs on 2026-07-23: Authelia v4.39.20, Authentik 2026.5.6. The OIDC beta status is on Authelia's live roadmap; re-check it before you build, because that is the one fact most likely to change.

The short version

Every article ranking for this comparison repeats the same personality sketch: Authelia is the light, simple one; Authentik is the heavy, powerful one. That sketch is not wrong, but it is built on top of a fact that stopped being true five years ago, and the whole search result has been copying it forward ever since.

The stale fact is this: Authelia is described as a forward-auth gateway that cannot be a real identity provider. One of the pages currently ranking states flatly that Authelia cannot issue OAuth2 or OIDC tokens at all. It can, it has since 2021, and it is certified. So the useful version of this comparison starts by getting that straight, because it changes who each tool is actually for.

The correction: Authelia is an OIDC provider — and still a beta

Authelia’s documentation says it plainly: “Authelia can act as an [OpenID Connect 1.0] Provider as part of an open beta” (OIDC introduction). This is not a forward-auth trick with headers — it is the real thing. Applications that implement the OIDC relying-party role “can use Authelia as an [OpenID Connect 1.0] Provider similar to how you may use social media or development platforms for login” (provider config).

It is also independently verified. Authelia “is [OpenID Certified™] to the Basic OP / Implicit OP / Hybrid OP / Form Post OP / Config OP profiles” (OIDC introduction). That certification is why the pages calling Authelia “not a real IdP” are simply wrong.

Here is the part no page on the first page of Google states, and it is the whole story: certified and beta are true at the same time. Authelia’s roadmap is explicit — “we have decided to implement [OAuth 2.0] and [OpenID Connect 1.0] as a beta feature. While it’s relatively stable there may inevitably be the occasional breaking change,” and the endpoints “are not enabled by default” (OIDC roadmap). The provider first shipped in v4.29.0, which the GitHub release API dates to 2021-05-05 (release). The roadmap tracks it through numbered beta stages, with General Availability defined as a future stage that “will signify official stability guarantees” and has no version attached yet.

So one set of articles tells you Authelia can’t do OIDC (false), and another tells you it’s certified and therefore production-ready (an overstatement). The accurate statement is the paradox: Authelia’s OIDC provider is OpenID Certified and officially still an open beta, off by default, with occasional breaking changes possible.

The two facts stop fighting once you know what certification actually measures. OpenID Certification tests protocol conformance — that an implementation correctly speaks the spec’s profiles. It says nothing about a project’s own stability commitments, which is what a beta label governs. Authelia’s provider conforms to the specification and carries no stability guarantee, at the same time, without contradiction. That is why quoting only the certification or only the beta tag both mislead.

If you run a handful of apps, can absorb an occasional breaking change at upgrade time, and do not need centralized sign-out, that trade is usually fine. If you need a stability guarantee in writing, it is not there yet.

The clearest gap in Authelia’s provider: single logout

The beta status carries three separate costs — the provider is off until you configure it, breaking changes are possible at upgrade time, and one capability is missing outright. The missing capability is the most concrete of the three, and the sharpest reason to pick Authentik instead. Authelia’s OIDC support chart marks RP-Initiated Logout, Session Management, Front-Channel Logout and Back-Channel Logout all as unsupported (OIDC introduction), and the roadmap places them in a later beta stage that has not started.

In practice: logging out of one application does not sign you out of the others. Each app’s session lives until it expires on its own. For a home setup with a handful of trusted users who close their own browser sessions, that is usually acceptable; if you share access with people who will not, or you need a revoked account to lose access everywhere immediately, it is not. For anything where a real single sign-out matters, it is a genuine limitation, and Authentik’s provider implements front-channel and back-channel logout (Authentik logout docs) where Authelia’s does not. None of the six ranking comparisons we reviewed on 2026-07-21 mentions it — it is the highest-value operational detail on the page.

Authentik: the fuller provider that quietly dropped Redis

Authentik is the broader tool, and its documented architecture is simpler than its reputation. A standard deployment is the server container (which bundles the Core plus an embedded outpost), the worker container, and PostgreSQL (architecture). The current official Docker Compose file defines exactly three services — postgresql, server and worker — plus one volume, and pins the 2026.5.6 image (compose file).

Note what is missing: Redis. Authentik removed it entirely. Caching, the embedded outpost session store and WebSockets all moved to PostgreSQL in release 2025.10, after background tasks moved there in 2025.8 (2025.10 release notes). This matters for the comparison because nearly every third-party writeup — and any AI summary trained before late 2025 — still lists Redis as a hard Authentik dependency. It is not one anymore. The documented trade is roughly 50% more PostgreSQL connections, and a 2026.5 change to a Rust-based worker cut about 200MB of memory per worker container on top of that (2026.5 release notes).

The current stable release is 2026.5.6, published 2026-07-22 (release API). Two upgrade hazards are worth knowing before you commit: Authentik does not support downgrades, and major-version upgrades must be done sequentially — you cannot jump an old install straight to current. Outpost containers, if you run separate ones, must match the server version exactly (upgrade docs).

Footprint: the number everyone quotes and nobody explains

The resource figures across the ranking pages are a mess — Authelia is quoted anywhere from sub-30MB to over 1GB of idle RAM, a tenfold spread for the same product, with no page reconciling it. Before trusting any of them, note what none of those pages provide: not one publishes a config file, a docker stats output, a version, or even whether the figure is idle or under load. They are unsourced numbers.

What we can state from primary docs is the mechanism that most likely explains the spread. Authelia can use SQLite as a file-based embedded backend that needs no separate database server (storage docs). Configured that way it is a single container with a single config file. The same storage doc is candid that SQLite leaves Authelia stateful and steers production and high-availability deployments to PostgreSQL, so the one-container shape is a small-deployment convenience, not a recommended ceiling. Point it at LDAP and other services and the container count and memory climb. So a 30MB figure and a 300MB figure can plausibly both be honest — different deployments rather than different measurements of one thing. We cannot prove that mapping for any specific published figure, because none of them disclose their configuration. Treat the range as a range, and measure your own.

The documented-requirements comparison is cleaner, and it cuts one way: Authentik publishes a minimum and Authelia publishes none. Authentik’s install docs state “2 CPU cores” and “2 GB of RAM” for the Docker Compose deployment (install docs) — scoped to that install path rather than a global floor, and cited by not one ranking page. Authelia’s docs carry no hardware requirements page at all, so its low numbers are community reports, not specification. If you are sizing the machine, our mini PC picks for a home server apply; on a Pi-class board Authentik’s documented 2GB is the constraint to plan around.

What actually costs money in Authentik

Authentik has a paid Enterprise tier, and the ranking pages that mention it name at most a feature or two, leaving a vague impression that “the good stuff is paywalled.” The docs are specific, so we can be too.

The Open Source (free) tier covers OIDC, SAML, LDAP, SCIM, RADIUS, Kerberos and the Proxy/forward-auth outpost, plus browser-based RDP and SSH via RAC — the only listed exclusion is vendor support (pricing). Enterprise, at a documented “$5 / user / month” billed annually, gates ten features on its own published list — enhanced audit logging, viewing and exporting logs, Google Workspace and Microsoft Entra ID provisioning, embedding external OAuth/SAML sources, Chrome Enterprise Device Trust, the Shared Signals Framework, password-history compliance checks, and mTLS client certificates (enterprise features, pricing). Three further gates are announced in release notes rather than on that list, and this is worth knowing because their own provider pages carry no Enterprise badge: WS-Federation (2026.2), SCIM OAuth-token authentication (SCIM provider) and RADIUS EAP-TLS (2025.10). A couple of details cut the other way: base RADIUS with PAP is free (only EAP-TLS is Enterprise), base SCIM with a static token is free (only OAuth-token mode is Enterprise), and the served LDAP directory carries no Enterprise marker at all.

The takeaway for a homelab reader: the free tier is complete. Every authentication protocol you would want is open source. What you pay for is outbound provisioning into corporate directories and a set of compliance features — the things a business needs and a home lab does not.

What the community actually says

Across the r/selfhosted threads on this matchup (community sentiment, not verified fact, read via a mirror on 2026-07-21), the split is consistent and it is not about capability. The most-cited decider is configuration style: Authelia’s single declarative YAML file versus Authentik’s clicked-together GUI. People who ran both tend to land on one honest line — Authentik is more capable, Authelia is easier.

Resource use is the most repeated concrete complaint, and it runs one direction: Authentik’s multi-container stack near 1GB idle versus an Authelia instance a small fraction of that. Two migration patterns show up. People leave Authentik for Authelia to cut resource use and shrink the attack surface, often pairing Authelia with LLDAP for a single-file backup story. People leave Authelia for Authentik when they tire of hand-editing config and want a GUI, per-user self-service password reset (which Authelia plus LLDAP does not offer end users), and a maintained app-integration catalog.

One migration gotcha deserves a callout because vendor docs gloss it: OIDC apps key each account to the issuer plus the identity provider’s opaque sub claim, so switching IdPs changes every user’s sub and can strand existing app-side accounts. There is no clean user-export path between the two; the durable answer people land on is to put users in an external LDAP so the IdP only does authentication and the next migration is painless. If you are choosing now, choosing an external directory early is the move that saves you later.

Run Authelia if / run Authentik if

Run Authelia if a light single-container deployment covers your needs, you prefer one declarative config file you can version-control and back up as a single artifact, and your apps either sit behind a reverse proxy for forward-auth or speak OIDC natively. Accept the trade: the OIDC provider is a certified beta, and there is no single sign-out yet. (If footprint is the only thing you care about, note that the community increasingly points at even lighter single-purpose tools like Pocket ID or Tinyauth — neither is a full IdP, but neither pretends to be.) If you already run a reverse proxy, our Caddy vs Nginx Proxy Manager vs Traefik comparison covers the layer Authelia’s forward-auth sits behind.

Run Authentik if you want a web GUI over YAML, the widest protocol coverage — including a served LDAP directory and RADIUS, not just LDAP as a login backend — self-service password reset for non-technical users, or working single logout. Budget 2GB of RAM for it, and if you are standing it up, our Authentik SSO setup guide walks the deployment end to end.

Whichever you pick, an auth server is the front door to everything else you self-host, so it belongs in your backup rotation from day one — encrypted offsite copies via restic are the minimum bar, and a self-hosted password manager like Vaultwarden pairs naturally with either behind SSO.

What competing guides skip (our angle)

Four things almost never make it into other comparisons, and they are the four that actually decide it.

First, the certified-and-beta paradox. The SERP is split between pages saying Authelia can’t do OIDC (false) and pages calling it production-ready (incomplete). The accurate statement is both: OpenID Certified and officially an open beta, off by default. Stating only half misroutes readers in both directions.

Second, the single-logout gap. Authelia’s provider does not implement RP-initiated or channel logout yet, so signing out of one app leaves the others signed in. It is the clearest capability reason to choose Authentik, and no ranking page names it.

Third, Authentik dropped Redis. Removed in 2025.10; the current stack is three services. Every guide still listing Redis is describing a 2025-and-earlier Authentik.

Fourth, the resource figures on this SERP are unsourced. Not one of the six ranking pages discloses a config, a version, or an idle-versus-load distinction behind its RAM numbers, which is why the same product is quoted across a tenfold range. The documented comparison is the one worth having: Authentik states 2 CPU and 2GB for its Compose install, Authelia publishes no hardware requirements at all, and no ranking page reports either fact.

Authentik SSO: self-hosted setup guide — the step-by-step deployment for the heavier of the two
Vaultwarden vs Bitwarden — the password manager to put behind your new SSO
Caddy vs Nginx Proxy Manager vs Traefik — the reverse proxy Authelia’s forward-auth sits behind
Tailscale vs Cloudflare Tunnel — how people reach these services from outside the LAN
Automated offsite backups with restic — because an auth server belongs in your backups

Sources

Jellyfin vs Emby: What Free Actually Gets You (2026)

LK Wood IV — Thu, 23 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-23 · Updated 2026-07-23 · ~12 min read · St. Louis County, MO

TL;DR · Shared ancestry, client-dependent freemium

They share a codebase, and have diverged for eight years since. Jellyfin forked Emby 3.5.2 in December 2018 after Emby took 4.x closed-source. Emby's public repo stops dead in September 2018 at tag 3.5.3.
"Free Emby" depends on which client you open. Full playback is free in a web browser and on Roku/Apple TV/LG/Samsung TVs. The native iOS, Android, Windows, Linux and macOS apps stop after one minute. Live TV needs Premiere everywhere.
Hardware transcoding is a Premiere feature (Nvidia Shield and WD NAS excepted). Jellyfin gates nothing — QuickSync, NVENC, AMF, VA-API and more are plain settings.
Premiere in 2026: $4.99/mo, $54/yr, or $119 lifetime — single household, 30 devices, counted per app rather than per machine.
Migration is officially unsupported. Jellyfin's docs say so in capitals. Your files and sidecar metadata survive; your watch history and users do not.

Versions verified against the projects' own release feeds on 2026-07-23: Jellyfin 10.11.11 stable (12.0 is still release-candidate), Emby Server 4.9.5.0. Emby's prices and feature matrix move — re-check the linked pages before you buy.

The short version

Most comparisons of these two open on personality — Jellyfin is the free community one, Emby is the polished paid one — and stop there. That framing is not wrong, but it skips the two things that actually decide it: what the free tier of Emby does and does not let you do, and the fact that these are not two products that happen to be similar. They are one product that split.

Get the split straight and the rest follows.

Jellyfin’s own documentation is direct about the origin: the project “was started in early December 2018 primarily as a result of Emby’s decision to take their next release (4.x) closed-source” (about). On that announcement, the group “quickly gathered to fork as many repositories as (legally) possible and begin the process of renaming the project Jellyfin.”

The precise lineage matters, and almost nobody states it correctly: Jellyfin descends from Emby 3.5.2, not from 4.x, and was “ported to the .NET Core framework to enable full cross-platform support” (about). Jellyfin also cites reasons beyond the licence change — previously-reported GPL violations, a paywall added for gratis users in an early 3.x release, and the progressive removal of client and server source code.

Emby confirms the same event from its own side. Its developer blog states that “in 2018, Emby made a significant decision: it moved from being an open-source project to a proprietary, closed-source model” (Emby history). The hard corroboration is the repository itself: Emby’s public server repo is GPL-2.0 licensed, and its final commit is dated September 2018, tagged 3.5.3 (MediaBrowser/Emby). No source for 3.6 or any 4.x release was ever published.

So the two projects diverged from adjacent commits. That shared ancestry explains a great deal of what follows — including a port collision nobody warns you about.

What “free Emby” actually means

This is the part the search results get wrong, and it is the single most useful thing on this page. Emby is free to install, and every comparison says so. What none of them say is that the free tier’s limits depend entirely on which screen you watch on.

From Emby’s own Premiere Feature Matrix (feature matrix):

Client	Free tier	Needs Premiere
PC or mobile web browser	Full playback	Live TV, TV Mode
Roku, Apple TV, LG & Samsung smart TVs	Full playback	Live TV only
Android TV, Fire TV	Full playback, capped at 5 TV devices	Live TV, offline media
iOS, Android (native apps)	One-minute playback only	Full playback (or a one-off per-app purchase), offline downloads, CarPlay/Android Auto, Apple Watch, camera upload
Windows, Linux, macOS (native apps)	One-minute playback only	Full playback, Live TV, offline media (listed for Windows and macOS; the Linux row lists none)

Read the first row, because it is the one no competing page mentions: the web browser is a fully unrestricted free client for playback. Your whole library, no licence, no time limit. Live TV and TV Mode are the only things it withholds — and Live TV is Premiere-gated on every client, so that is not a browser limitation.

The cap lands on the native apps. Open Emby’s iOS, Android, Windows, Linux or macOS application unlicensed and playback stops after one minute. Emby sells a per-app purchase that buys full playback on that one app, or Premiere covers everything at once.

So “free Emby” is a real, usable product — provided you watch in a browser tab or on a TV. What Premiere buys on a phone or desktop is the native app experience, offline downloads and Live TV on those clients. That is a defensible model, and considerably more nuanced than either “Emby is free” or “Emby is crippled.”

Jellyfin has no equivalent table, because it has no tiers. Its docs put it plainly: “There are no strings attached, no premium licenses or features, and no hidden agendas” (about), and the project has committed that features “will never be hidden behind a paywall” (10.6.0 release post).

Hardware transcoding is the expensive difference

Everything above is about convenience. This one is about whether your hardware copes.

Emby’s feature matrix lists hardware accelerated transcoding as a Premiere feature, with a footnoted exception: Nvidia Shield and WD NAS devices do not require Premiere for it. Everyone else transcodes in software until they pay.

Jellyfin documents hardware acceleration as a plain configuration option for all users, listing Intel QuickSync, NVIDIA NVDEC/NVENC, AMD AMF, Intel/AMD VA-API on Linux, Apple VideoToolbox on macOS, and Rockchip RKMPP (hardware acceleration). One honest scope note: Jellyfin documents full acceleration for a specific list — mainstream Intel and NVIDIA GPUs on Windows and Linux, AMD Polaris and newer on Linux, older AMD on Windows, RK3588, and Intel and Apple Silicon on macOS 12+. And it requires its own bundled FFmpeg: “using FFmpeg binaries downloaded from somewhere else will result in partial acceleration.”

If you run a low-power box — an N100 mini PC, a Pi-class board, an older NAS — this is the whole comparison. Software transcoding is what makes cheap servers stutter, and one product charges to avoid it. If you are choosing hardware around this, our GPU picks for Plex and Jellyfin transcoding cover what actually accelerates.

About that viral “Emby transcoding is 3x slower” thread

If you have researched this comparison, you have probably seen a thread on Emby’s own community forum titled roughly why is Emby’s transcoding engine so far behind Jellyfin, and why I’m switching back, claiming Jellyfin hits ~80 fps where Emby manages ~30. It surfaces high in search precisely because it sits on Emby’s own turf.

We read the whole thread, and its own contents defeat the claim. One problem is disqualifying on its own; the rest is context:

It is self-refuting. The author’s own description establishes that Emby was performing a software transcode while Jellyfin used the GPU. That is a software-versus-hardware measurement, not an engine-efficiency comparison.
There is a confound that explains it entirely. As a forum contributor pointed out and Emby’s docs confirm, hardware transcoding requires Premiere outside the Nvidia Shield and WD NAS exception. The author never stated whether the Emby install was licensed — and without a licence it could not have used the GPU at all.
Context worth knowing, though it does not by itself refute a measurement: the post is not first-hand text. A responder flagged it as machine-generated and the author conceded it — “My English is not good, so I let AI help me express what I mean.” An Emby administrator rejected the post’s accuracy and requested diagnostics; the author never supplied any, and the thread died without resolution.

There is exactly one narrow corroboration: a later commenter reported that on Rockchip RK3588 hardware, “jellyfin hw transcodes 4k to 4k HEVC at 4.8x. Emby won’t even let me do this on rk3588.” That is one unverified single report, but it is at least consistent with something documented — see the next section.

We are flagging this because it is widely linked and worthless as a benchmark. Anyone repeating the fps figures is repeating an AI-written post that Emby staff rejected and nobody ever reproduced.

What is actually documented about transcoding

Discarding that thread leaves the performance question open — no public benchmark we found settles it. What we can document is not a performance result but a difference in release cadence, which is a narrower claim and worth stating as such.

Jellyfin does not use system FFmpeg. It ships and requires jellyfin-ffmpeg, its own maintained fork. Be precise about what that means today: the current stable build is v7.1.4-3 (2026-06-06), which is what stable Jellyfin 10.11.x installs. The fork’s 8.1.x line — v8.1.2-2 as of 2026-07-21 — is still flagged pre-release and pairs with the Jellyfin 12.0 release candidates (jellyfin-ffmpeg releases). That fork carries patches that matter for exactly the workloads people complain about: PGS and graphical subtitle overlay moved into hardware filters so subtitle burn-in stays on the GPU, hardware HDR tone-mapping across four vendor stacks, and a documented end-to-end hardware pipeline for Rockchip RK3588 — which is precisely the case the one corroborating commenter hit.

Emby also maintains its own patched FFmpeg fork rather than shipping stale vanilla binaries. But its announced base version lags: the last Emby release announcing an FFmpeg base upgrade is 4.7.0.60, dated 2022-05-17 (“Update to ffmpeg 5.0”), and no Emby release note we could find since then — through the 4.10.0.20 beta of 2026-07-17 — announces a further base bump (Emby releases). Emby backports fixes into its own fork, so the announced base version understates how current the shipped code actually is. Treat this as a base-version lag, not abandonment.

The fair summary: Jellyfin adopts new upstream FFmpeg capability faster. That is a documented difference in release cadence, not a measured performance gap, and we are not aware of a controlled benchmark that turns one into the other. On mainstream Intel or NVIDIA hardware, both products lean on the same vendor APIs and you are unlikely to see a difference. The one concrete case in evidence is Rockchip RK3588, where jellyfin-ffmpeg documents an end-to-end hardware pipeline and a user reported Emby would not hardware-transcode at all.

Two practical traps from the shared ancestry

They collide on the same ports. Jellyfin documents TCP 8096 for HTTP, TCP 8920 for HTTPS and UDP 7359 for LAN discovery. Emby’s connectivity documentation specifies the identical three. Both inherited them from the 3.5.2 fork point (Jellyfin networking, Emby connectivity). Install both on one host to compare them and the second fails to bind. Across the top-10 Google results for “jellyfin vs emby” that we checked on 2026-07-23, none mentions a port number at all.

Migration is officially unsupported. One competing guide tells readers that moving between these servers is straightforward because they read the same file structures. Jellyfin’s own migration doc contradicts it in capitals: “Direct database migration from Emby (of any version) to Jellyfin is NOT SUPPORTED” (migrate). It goes further and advises against migrating even Emby 3.5.2-era configuration — the one version the shared lineage would theoretically permit — “due to subtle and weird bugs reported after such attempts.”

The half-truth in the competing claim is that your media and any NFO and image sidecar files do carry over, because they live beside the files. What does not carry over is the database: watch history, user accounts, playback positions and server settings. Plan on a fresh library scan.

One more thing worth knowing before you buy

Emby Premiere requires online licence validation, and not only from the server. Emby documents that “each of your devices will need access to the internet and, specifically, mb3admin.com in order to validate the limit” (Premiere limits), and the server itself must reach the same host or the key reports as invalid.

The 30-device limit is contractual and counted per unique device ID per application, so one physical machine can consume several slots (Premiere terms). Premiere is keyed to the server rather than to a user account, and the device limit is counted per key across every server that key is used on.

If a fully offline or air-gapped setup is a requirement, that is the constraint to weigh. We found no Emby documentation describing offline activation. Jellyfin has nothing to validate.

Run Jellyfin if / run Emby if

Run Jellyfin if you want everything free with nothing gated, you want GPU transcoding without a subscription on hardware outside Emby’s Shield/WD-NAS exemption, you run newer or ARM-based silicon where FFmpeg cadence matters, or you simply want no licence server in the path. Accept the trade: client polish is uneven and you may end up pairing it with a third-party player on some platforms. Our Jellyfin Docker setup guide covers the build.

Run Emby free if your household watches your own library in a browser or on Roku, Apple TV or a Samsung/LG TV. Playback there is unrestricted and costs nothing — a genuinely viable setup that most comparisons write off.

Buy Emby Premiere if you additionally want Live TV, offline downloads, the native phone and desktop apps without the one-minute cap, or hardware transcoding on anything other than an Nvidia Shield or WD NAS (which are exempt). At $119 once, that is a real product for a real user, and the polish is not imaginary.

And if you have not committed to either, note that most of this decision is upstream of both: our Jellyfin vs Plex comparison covers the third option most people are actually choosing between, and the box matters more than the software — see the best NAS for Plex and Jellyfin.

What competing guides skip (our angle)

Five things — three that change which product you pick, two that change how you deploy it.

First, the free tier is client-dependent. Full playback free in a web browser and on TV apps; one minute in the native phone and desktop apps; Live TV behind Premiere everywhere. Across the top-10 results we checked on 2026-07-23, none published that split — and it is the difference between “free Emby works” and “free Emby is a demo.”

Second, the fork lineage is specific, and none of the pages we checked states it. Emby 3.5.2, December 2018, ported to .NET Core. Emby’s own repo stopping at 3.5.3 in September 2018 is the corroboration from the other side.

Third, the most-cited performance evidence is worthless. The viral Emby-forum thread is AI-written, self-refuting on its own description, and was rejected by Emby staff. The real difference is FFmpeg release cadence, which is a narrower and more honest claim.

Fourth, migration is officially unsupported, in capitals, in Jellyfin’s own docs — directly contradicting the one ranking page that addresses migration at all.

Fifth, they share default ports and collide on a single host, because they share an ancestor. None of the pages we checked mentions a port number.

Jellyfin vs Plex (2026) — the comparison most people actually need first
Jellyfin setup with Docker — the build, end to end
Best NAS for Plex and Jellyfin — the hardware that decides transcoding
Best GPU for Plex/Jellyfin transcoding — what actually accelerates
Best mini PC for a home server — sizing a low-power box

Sources

Tailscale vs Cloudflare Tunnel for Homelab (2026)

LK Wood IV — Wed, 22 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-22 · Updated 2026-07-22 · ~10 min read · St. Louis County, MO

TL;DR · They overlap, but they are built for different jobs

Publishing a service to people who should not need an account or client? Cloudflare Tunnel. A plain HTTPS URL in any browser, no software on the far end — but put a Cloudflare Access policy in front of it unless you genuinely intend the service to be public. A tunnel with no policy is a public URL.
Reaching your own machines privately? Tailscale. End-to-end WireGuard, any protocol, any port, no domain required.
Who holds plaintext: Cloudflare states it must decrypt traffic to cache and filter it; Tailscale's relays never access unencrypted data.
Neither opens inbound ports, and both survive CGNAT — that shared property is why the comparison exists at all.
If you have both needs, run both: public apps via the Tunnel, admin and SSH via Tailscale. If everything you reach is your own, Tailscale alone is enough — and if you publish one public app and administer nothing remotely, so is the Tunnel.

Free-tier terms and product limits move. Every number below is cited to a source we read live on 2026-07-20 — re-check the linked page before you plan around it.

The short version

Most comparisons treat Tailscale and Cloudflare Tunnel as competitors picking off the same job. They aren’t. Ask one question first: are you publishing a service to people who should not need an account or client software, or are you reaching your own machines privately? If it’s the first, Cloudflare Tunnel is the tool — an unmodified browser hits a normal HTTPS hostname and Cloudflare Access decides who gets through. If it’s the second, Tailscale is the tool — every device runs a client, traffic is end-to-end WireGuard, and every protocol works because you are on a network, not behind a web proxy.

They overlap on exactly one property, and that overlap is what makes people compare them: neither requires an inbound port on your router. cloudflared “initiates an outbound connection through your firewall from the origin to the Cloudflare global network” (Cloudflare Tunnel docs), and Tailscale connections work across firewalls and NAT “without requiring port forwarding or complex firewall rules” (What is Tailscale). Everything past that point diverges.

Side by side, from the vendors’ own docs

Dimension	Cloudflare Tunnel	Tailscale
Inbound ports on your router	None — outbound-only connector	None — NAT traversal, no port forwarding
Client on the accessing device	None for HTTP/HTTPS; required (cloudflared or the Cloudflare One client) for TCP/SSH/RDP	Required on every device, unless reached via a subnet router
Encryption model	TLS terminated at Cloudflare’s edge; Cloudflare decrypts to cache and filter	End-to-end WireGuard; relays only carry already-encrypted packets
Public clientless web access	A plain HTTPS URL — pair with an Access policy	Via Funnel (public, ports 443, 8443, 10000 only)
Private access for invited people	Access policy + IdP or email OTP	Add them to the tailnet; they install a client
Built-in auth	Cloudflare Access, deny-by-default; email one-time PIN needs no third-party IdP	Tailnet policy file ACLs — but new tailnets default to allow-all
Free tier (checked 2026-07-20)	$0 forever, 50-user limit, logs up to 24 hours	$0 forever, up to 6 users, unlimited user devices
Domain required	Yes — you must add a website to Cloudflare	No — MagicDNS / ts.net name
Large uploads	100 MB body on Free and Pro, 200 MB Business	Not capped by that mechanism; Funnel has undisclosed bandwidth limits
Whole-LAN access	Private network routes plus a client on-ramp	Subnet router; exit node for full-tunnel

Who can decrypt your traffic

This is the sharpest differentiator and the one most comparisons bury under a feature grid.

Cloudflare is a reverse proxy. Its SSL FAQ says it plainly: “Cloudflare must decrypt traffic in order to cache and filter malicious traffic. Cloudflare either re-encrypts traffic or sends plain text traffic to the origin web server depending on your domain’s encryption mode” (SSL FAQ). The architecture is two separate TLS legs with two certificates — an edge certificate presented to visitors, and an origin certificate covering the Cloudflare-to-origin hop (SSL concepts). Under Flexible mode, “traffic from visitors to Cloudflare can be encrypted via HTTPS, but traffic from Cloudflare to the origin server is not” (SSL modes). Cloudflare does not publish a Tunnel-specific page stating it terminates TLS for tunnel traffic in those words, so treat this as what the reverse-proxy architecture implies rather than a Tunnel-page quote.

Tailscale goes the other way. Its data plane “uses WireGuard as its primary mechanism to encrypt communication between Tailscale devices,” and it provides end-to-end encryption “whether devices connect directly or through a relayed connection” (Tailscale encryption). Relays are explicitly blind: “DERP servers never access your unencrypted data; they only handle WireGuard packets that are already encrypted.” Policy enforcement is local too — ACLs are enforced “on each device directly, without further involvement from Tailscale’s coordination server” (ACLs).

Neither position is the safe one in the abstract. Cloudflare’s decryption is what buys you WAF, bot filtering, and Access policies evaluated before a packet reaches your origin. Tailscale’s refusal to decrypt is what forces client software onto every participant. That is the trade, stated honestly.

One caveat worth knowing: Tailscale Funnel is the exception that proves the rule. When you publish a service publicly with Funnel, “the Tailscale server running on your device receives the encrypted request from the TCP proxy. It then terminates the TLS connection and passes the decrypted request to the local service” (Funnel). TLS ends on your hardware, not Tailscale’s.

Protocol coverage: HTTP-first vs anything

Cloudflare Tunnel “can connect HTTP web servers, SSH servers, remote desktops, and other protocols,” and has full WebSocket support (Tunnel docs, Tunnel FAQ). The catch homelabbers hit is how those non-HTTP protocols are reached. For arbitrary TCP, “cloudflared will need to be installed on each user device that will connect” (arbitrary TCP). For private network routes — the CIDR-style path that exposes non-HTTP resources — “end users must connect their device to Cloudflare and enroll in your Zero Trust organization,” most commonly by installing the Cloudflare One Client (private networks).

SSH has four documented paths: client-side cloudflared (no Cloudflare One client needed), Access for Infrastructure and self-managed SSH keys (both requiring a client on-ramp), and a browser-rendered terminal that needs no SSH client at all (SSH use case). RDP mirrors this with browser-based, Cloudflare One client, and client-side cloudflared options (RDP use case).

The net: HTTP/HTTPS is the only category an arbitrary unmodified browser reaches. Everything else needs client software or Cloudflare’s browser-rendered terminal. On Tailscale, once the client is installed, there is nothing to configure per-protocol — SMB, NFS, rsync, a game server, a database port, whatever. That is the practical meaning of “network” versus “web proxy,” and it’s the same distinction we draw in Tailscale vs WireGuard.

The client requirement and its escape hatches

Tailscale’s own subnet-router page states the constraint outright: subnet routers exist to “extend your Tailscale network to include devices that don’t or can’t run the Tailscale client,” citing printers and large VPC or legacy environments where “installing clients on every endpoint becomes impractical” (subnets). Routes must be approved in the admin console or auto-approved via autoApprovers, and there is a failure mode worth planning around: “Tailscale does not fall back to a less-specific route when the subnet router for a more-specific route goes offline.”

Exit nodes are the other lever — one device routes all your public internet traffic using default routes 0.0.0.0/0 and ::/0, which requires IP forwarding on Linux and explicit opt-in on both ends. Tailscale flags real platform limits here: macOS exit nodes are “limited to userspace routing” and need sleep prevention to hold a connection, Windows carries its own caveat around per-query DNS thread usage, and “running an exit node on an Android device is not performant” (exit nodes).

Cloudflare’s escape hatch from the domain requirement doesn’t exist: “Before you publish an application through your tunnel, you must add a website to Cloudflare” (create a remote tunnel). If you don’t own a domain and don’t want to, that ends the conversation.

Auth, and one default that surprises people

Before anything else in this section: a Cloudflare Tunnel does not authenticate anyone by itself. Access is a separate product you put in front of it. Publish a hostname through a tunnel with no Access policy and no application-level login, and you have put that service on the public internet — indexed, scanned, and reachable by anyone who learns the name. This is the single most common way homelabs get burned by the “no client needed” pitch, and it is why the clientless convenience is not free. Before you point anything at a tunnel, decide explicitly whether it is meant to be public; if it is not, attach an Access policy or make sure the app’s own authentication is one you would trust facing the open internet. Admin surfaces — Proxmox, routers, Portainer, container dashboards — should not be published this way at all. Put those on the tailnet.

Cloudflare Access is deny-by-default and validates identity against an IdP (Access policies). You do not need a third-party IdP for a homelab: Access can send a one-time PIN to approved email addresses instead. The PIN expires 10 minutes after request, is single-use, and requesting a new one invalidates the previous — and Cloudflare only sends the email if the user is already allowed by a policy (one-time PIN).

Tailscale’s ACL system is deny-by-default in principle, but new tailnets are not: “When you first create your tailnet, the default tailnet policy file enables communication between all devices within the tailnet,” and “in the absence of an acls section in the tailnet policy file, Tailscale applies the default allow all policy” (ACLs). If you have added a family member’s laptop or a VPS to your tailnet and never touched the policy file, every node can reach every other node on every port. Fixing that is a 20-minute job and it’s the first thing we do in our Tailscale homelab setup guide.

Free tiers, as verified on 2026-07-20

Cloudflare’s Zero Trust free plan reads “$0” “forever,” a “50 user limit,” “Community forums and Discord server” support, and standard log retention “up to 24 hours”; the next tier is pay-as-you-go at “$7 per user/month (paid annually)” with logs “up to 30 days” (Access plans, Zero Trust plans). Note the annual-billing qualifier on that $7 — monthly billing is higher. Onboarding still asks for payment details — Cloudflare notes that if you chose the Free plan “this step is still needed but you will not be charged” (Cloudflare One setup). Free-plan DEX limits are 10 tests per account and 100 remote captures per day (account limits).

Tailscale’s Personal plan currently reads “$0 / Free forever,” “Up to 6 users,” “Unlimited user devices,” up to 3 ACL groups, “Up to 50 tagged resources to start,” and 1,000 minutes per month for ephemeral resources, with subnet routers, exit nodes, and Funnel included (Tailscale pricing). Note this supersedes the 3-user / 100-device figures still repeated across older comparisons — those are stale.

Seat accounting on Cloudflare is worth reading before you invite people: “A user consumes a seat when they perform an authentication event,” one seat regardless of how many apps they open, and once seats are exhausted “additional users who attempt to log in are blocked” (seat management). Whether a tunnel with no Access policy in front of it consumes a seat is not stated in the docs we read — treat it as unverified.

The two limits that actually bite homelabs

The 100 MB body cap. Maximum upload size is 100 MB on Free and Pro, 200 MB on Business, and 500+ MB on Enterprise; exceeding it returns 413 Request Entity Too Large. Documented workarounds are chunking requests, switching the DNS record to DNS-only, or upgrading (error 413). Immich and Nextcloud users hit this constantly.

The CDN media term. Cloudflare’s service-specific terms state it “reserves the right to disable or limit your access to or use of the CDN… if you use or are suspected of using the CDN without such Paid Services to serve video or a disproportionate percentage of pictures, audio files, or other large files,” naming the Developer Platform, Images, and Stream as the qualifying paid services (service-specific terms). That is the text; we found no published enforcement threshold anywhere in Cloudflare’s terms, so any specific TB/month figure you see quoted is anecdote, not policy. This is why Plex and Jellyfin over a Tunnel is a recurring warning in self-hosting communities.

We could not verify a bandwidth cap for Cloudflare Tunnel itself, and Tailscale states only that Funnel traffic “is subject to non-configurable bandwidth limits” without publishing a number. Don’t plan capacity on either.

The split most people actually run

Across three self-hosting and homelab threads we read on 2026-07-20 (community opinion, not verified fact), the dominant recommendation among people who have both needs is not a winner — it’s a division of labor. That is a statement about what experienced self-hosters recommend in those threads, not a claim that most homelabs run both; plenty need only one. A highly-upvoted framing in the r/selfhosted Cloudflare-Tunnels-vs-Tailscale thread splits the estate into applications you consume (website, wiki, photo management) behind Cloudflare, and management planes (Proxmox, terminal, remote desktop, Portainer) behind Tailscale. Since neither opens inbound ports, the argument runs, the real difference is that one path demands a client on the far end and the other only demands authentication. The identical split appears independently in a separate r/selfhosted thread, with replies naming the exact division: Overseerr and Mealie public via Tunnel, Portainer private via Tailscale. Vote rankings drift, so treat “highly-upvoted” as a snapshot of that date, not a standing fact.

Credential stores are the clearest case of all. A self-hosted password manager is the last thing to publish through a proxy that terminates TLS — keep Vaultwarden on the tailnet and reachable only by devices you control, whatever you do with the rest of the estate.

The recurring tiebreaker is blunt: can you install a client on the accessing device? Work laptops, a partner’s phone, a friend’s browser — those push you to the Tunnel. Second is household UX: toggling a VPN is friction for non-technical family, though the counter-argument in-thread is that Tailscale can simply be left running. Third is CGNAT, which even WireGuard purists concede is where Tailscale earns its place.

If you go the both-tools route, the public side still needs a reverse proxy behind cloudflared for host-based routing; our Caddy vs Nginx Proxy Manager vs Traefik comparison covers that layer.

What competing guides skip (our angle)

Four things get consistently glossed over:

They are not the same category. Cloudflare Tunnel publishes a service; Tailscale joins a network. Comparing their properties side by side is fine — we do it above — but scoring them on a shared grid and declaring a winner is the framing error, because half the rows are measuring each tool against a job it was never built to do. Tailscale’s public-publishing answer is Funnel, which is restricted to ports 443, 8443, and 10000 and requires MagicDNS plus tailnet HTTPS certificates (Funnel); its private equivalent, Serve, adds identity headers that Funnel deliberately omits (Serve).
Stale free-tier numbers. The 3-user / 100-device Tailscale figures are everywhere and are wrong as of 2026-07-20; the live pricing page reads 6 users and unlimited user devices.
The “no client needed” claim is HTTP-only. SSH, RDP, and arbitrary TCP through Cloudflare all need client-side cloudflared, the Cloudflare One client, or Cloudflare’s browser terminal. Say that up front and half the comparison resolves itself.
Tailscale’s allow-all default. A brand-new tailnet permits every device to reach every other device. Guides that present Tailscale as deny-by-default without noting the initial policy file are describing a state you have to create.

If Tailscale’s control plane is the part you object to, the adjacent options are worth a look: ZeroTier vs Tailscale and NetBird vs Tailscale cover the mesh alternatives, and Tailscale vs WireGuard covers rolling it yourself.

Tailscale vs WireGuard (2026) — when the managed control plane is worth it and when plain WireGuard wins.
Tailscale remote access for your homelab: setup guide — our step-by-step install, ACL lockdown, subnet router, and exit node.
ZeroTier vs Tailscale (2026)
NetBird vs Tailscale (2026)
Caddy vs Nginx Proxy Manager vs Traefik (2026) — the reverse proxy that sits behind cloudflared.
Home Assistant on Proxmox (2026) — the host side of the Home Assistant remote-access question.
Vaultwarden vs Bitwarden (2026) — the one service to keep off the public tunnel entirely.

Sources

Restic vs Borg vs Kopia: Which Backup Tool (2026)

LK Wood IV — Tue, 21 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-21 · Updated 2026-07-21 · ~11 min read · St. Louis County, MO

TL;DR · Filter by destination first, then decide on the rest

restic has compression. It landed in v0.14.0 on 2022-08-25 with repository format version 2. Every guide still saying otherwise is four years stale.
Backing up to a bucket (S3, B2, Azure, GCS)? restic or Kopia. Borg documents no native object-storage backend at all.
Backing up to a Linux box over SSH? Borg, and install Borg on both ends — that is how it is designed to run.
Backing up Windows? restic (with VSS via --use-fs-snapshot) or Kopia. Borg on Windows is WSL/Cygwin only, both labelled experimental.
Borg 2.0 is still beta at 2.0.0b21 (2026-03-15). Stable is 1.4.5 (mid-July 2026). Do not build a 2026 backup plan on the beta.

Versions move fast: restic 0.19.1 shipped 2026-07-05 and Kopia 0.23.1 on 2026-06-16. Every spec here traces to vendor docs or the GitHub release API on the date above — check the changelog before you copy a flag.

The short version

Most comparisons of these three tools open with a feature grid and close with “it depends.” That grid is where the errors live. The single most-repeated claim in this search result — that restic has no compression — has been wrong since August 2022, and it is still sitting in AI summaries and in blog posts updated this year.

So here is the correction first, then a decision framework that actually resolves.

restic added compression in v0.14.0, released 2022-08-25, tied to repository format version 2. The release notes call it “the most requested feature: compression” (restic v0.14.0 release notes). Repository format 2 is now the current default for new repositories (restic docs). All three tools compress. That axis is dead.

The axis that narrows it fastest is where the backup lands. restic and Kopia can write directly into cloud object storage. Borg cannot — its documented transports are a local path or an SSH remote. That one difference eliminates a candidate for most people in about thirty seconds.

Be clear about what that buys you, though: destination is a compatibility filter, not the whole decision. It tells you which tools are even eligible. What separates the survivors is everything after — whether you need a GUI, which operating systems you have to cover, how much CLI you want to learn, and how you intend to scope compression. This guide runs the filter first because it is the cheapest way to cut the field, then does the real comparison on what remains.

Why the “restic has no compression” myth persists

There is a real fact underneath the wrong claim, and it is worth knowing because it may apply to you.

Compression only works on a repository at format version 2 or later. Old repositories are not auto-upgraded. To get compression on a repository created before 0.14.0 you run migrate upgrade_repo_v2, which verifies integrity and bumps the version, then prune to compress existing metadata. After that, new backup data is compressed, and the repository compresses progressively over time. If you would rather not wait for that drift, prune --repack-uncompressed forces existing data to be rewritten compressed in one pass. Format 2 repositories are readable only by restic 0.14.0 and newer (restic docs).

So a repository someone created in 2020 and never migrated genuinely stores uncompressed data in 2026. That is almost certainly where the folklore comes from — that, and the 2019-era third-party comparisons still in circulation, whose restic criticisms predate compression entirely. Commenters passing those around on r/selfhosted routinely flag the date themselves.

Current restic exposes --compression with five settings: off, fastest, auto (the default), better, max, also settable via RESTIC_COMPRESSION. Each step up spends more CPU to save bandwidth and space (restic tuning docs). Two of those — fastest and better — are new; restic 0.19.0 on 2026-06-09 added the extra zstd levels (changelog). The original 0.14.0 set was just auto/max/off.

If you want the working setup rather than the theory, our automated offsite backups with restic walk-through covers repository init, retention and scheduling end to end.

Decide by where the backup lands

The target is a bucket (S3, B2, Wasabi, Azure, GCS)

restic and Kopia. Not Borg.

restic documents native support for local paths, SFTP, its own REST Server, Amazon S3, MinIO, any S3-compatible endpoint, Wasabi, Alibaba Cloud OSS, OpenStack Swift, Backblaze B2, Azure Blob Storage, Google Cloud Storage, and rclone as a bridge to everything else (restic docs). One documented gotcha worth acting on: because of error handling in the B2 library restic uses, the project recommends reaching Backblaze B2 through its S3-compatible API rather than the native B2 backend. Same source.

Before you pick either, one requirement that belongs in this decision and almost never appears in these comparisons: a bucket your backup client can write to is a bucket your backup client can delete. If the machine being backed up is compromised, credentials sitting on it can be used to wipe the repository — which is exactly the scenario offsite backup exists to survive. Neither restic nor Kopia solves that for you; the storage layer does. Turn on object lock or versioning at the bucket (Backblaze B2 and S3 both support it), give the backup client an application key scoped to write-and-list without delete, and run pruning as a separate privileged job rather than from the client. Then actually test a restore. A bucket target without those three things is a copy, not a backup.

Kopia documents S3 and S3-compatible storage, Azure Blob, Backblaze B2, Google Cloud Storage, Google Drive (native, experimental), WebDAV, SFTP, rclone, plain filesystem targets, and the Kopia Repository Server (Kopia docs). Kopia’s rclone support is marked experimental, with only Dropbox, OneDrive and Google Drive confirmed tested — which matches the community report of a user moving from Kopia to restic after OneDrive-over-rclone proved unreliable.

Borg documents no object-storage backend anywhere in its quickstart or FAQ. Note the phrasing: this is established by absence, not by an explicit statement from the project. But the FAQ actively points the other direction, recommending you run the Borg client where the source data is local and borg serve over SSH where the repository storage is local, and avoid NFS or other network filesystems for repository storage (Borg FAQ).

The target is an SSH box you control

Borg is at home here, and this is the case where it wins on merit rather than on habit.

Borg initializes and accesses repositories on remote hosts over SSH, and the docs are explicit that this is fastest and easiest when Borg is installed on the remote host (Borg quickstart). If you cannot install Borg at the far end, you can mount the remote filesystem with something like sshfs and treat it as local — with the documented caution that not every filesystem is stable enough for backup use.

Borg also has the widest compression menu of the three (Borg help docs):

none
lz4 — very high speed, very low ratio; this is the default
zstd[,L] — levels 1 to 22, default 3
zlib[,L] — levels 0 to 9, default 6
lzma[,L] — levels 0 to 9, default 6
auto,C[,L] — per-chunk heuristic that tries lz4 first to see whether data compresses
obfuscate,SPEC,C[,L] — pads compressed size to frustrate fingerprinting attacks based on observable chunk sizes

That last one has no advertised equivalent in restic or Kopia. If your threat model includes an adversary who can see stored chunk sizes on a repository host you do not fully trust, it is a genuine reason to pick Borg.

Borg also documents borg mount, which exposes a repository or archive as a FUSE filesystem for browsing and single-file restores. Limitation: the current FUSE implementation does not carry special filesystem flags or ACLs, and the docs recommend the nosymfollow mount option (or a container/chroot) so symlinks inside a mounted archive cannot reach outside it (Borg mount docs).

If your SSH box is a NAS or a ZFS server, the storage layer choices under it matter as much as the backup tool — see Proxmox vs TrueNAS vs Unraid as a storage backend and the NAS drives worth buying.

The fleet includes Windows

Borg is out. Its official standalone binaries cover Linux, FreeBSD and macOS on x86-64, with ARM via a third-party builder. Windows 10’s Linux Subsystem is described as experimental and not much tested, with FUSE omitted; Cygwin carries the identical experimental disclaimer (Borg installation docs).

restic backs up from Linux, BSD, macOS and Windows (restic.net), and on Windows the --use-fs-snapshot option drives Volume Shadow Copy Service, with -o vss.timeout (default 120 seconds) and -o vss.exclude-volumes to tune it (restic backup docs). Kopia supports Windows 10 or later 64-bit via CLI binary, GUI installer, Scoop and winget; macOS 10.11+ via binary, installer and Homebrew; and Linux amd64/armhf/arm64 via RPM and DEB repos, AUR and Docker images (Kopia installation).

One more restic detail that matters for mixed fleets: multiple hosts writing into one repository is officially supported and encouraged, because it increases deduplication across machines (restic backup docs).

What each tool needs installed on the far end

This is the question feature grids never answer, and it is the one that breaks deployments.

	restic 0.19.1	Borg 1.4.5	Kopia 0.23.1
Latest stable (date)	0.19.1, 2026-07-05	1.4.5, 2026-07-18/19	0.23.1, 2026-06-16
Software required on the target	None for S3/B2/Azure/GCS; SSH server for SFTP; REST Server if you use that backend	Borg itself, run via `borg serve` over SSH (or a mounted remote FS as fallback)	None for cloud backends; SSH server for SFTP; optional Kopia Repository Server
Native cloud object storage	Yes — S3, MinIO, S3-compatible, Wasabi, OSS, Swift, B2, Azure, GCS	Not documented	Yes — S3/S3-compatible, Azure, B2, GCS, Drive, WebDAV
Compression	Yes, since 0.14.0 (repo format v2)	Yes — lz4, zstd, zlib, lzma, auto, obfuscate	Yes — zstd, s2, pgzip, deflate, gzip families
Compression scope	Global flag / env var	Per-archive at create time	Per policy, with file-size and extension filters
Official GUI	No	No	Yes — KopiaUI
Native Windows	Yes, with VSS	No (WSL/Cygwin, experimental)	Yes, Windows 10+
Multi-host, one repo	Yes, officially encouraged	Yes	Yes, unlimited policies per repo
Mount as a filesystem	Yes — `restic mount`	Yes — `borg mount`	Yes — `kopia mount` (WebDAV fallback where FUSE is unavailable)
Next major version status	Shipping normally	2.0 still beta (2.0.0b21)	Shipping normally

The Borg row is the whole story. Borg is a client/server design in practice: to get its performance you want the Borg binary at both ends. restic and Kopia treat the far end as dumb storage. If your offsite target is a friend’s NAS, a rented VPS, or a Backblaze bucket where you cannot install arbitrary software, that constraint decides for you before any benchmark does.

Version status is a real differentiator right now

Borg’s current stable is 1.4.5, published 2026-07-18 at 22:36 UTC per the GitHub release API — Borg’s own changelog dates it 2026-07-19, which is the same release read in a different timezone. Borg 2.0 has been in beta for years and the newest prerelease is 2.0.0b21, published 2026-03-15 — no release candidate, no stable 2.0 (Borg releases API). The project’s own release page tells you it is beta quality, for testing, and not to point it at production backup repositories (2.0.0b21 release notes).

Community reports corroborate the cost of ignoring that. At least one r/selfhosted user upgraded to a Borg 2 beta and got stranded on a repository that was neither forward nor backward compatible; another user corrected the thread by pointing out the betas are not compatible with each other. Treat that as anecdote, not spec — the official warning says only “not for production,” not that the betas are mutually incompatible — but it lines up with the direction of that warning.

restic 0.19.1 (2026-07-05) and Kopia 0.23.1 (2026-06-16) are both on normal release cadences. The Kopia release is a bugfix for a rare race condition that could cause data loss, which is a reason to be current rather than a reason to avoid it.

What the benchmarks actually show (and what they don’t)

Thin, and contradictory. Here is everything credible we found.

deajan/backup-bench is the only reproducible-by-design suite, but it is stale — last updated 2022-10-03. Dataset: Linux kernel sources checked out at v5.19 then v5.18, 4.18 and v3.10, with the initial git directory at 4.1 GB across 5,039 directories and 76,951 files. Source host a Xeon E3-1275 with 64 GB RAM on XFS; remote target an AMD Turion II Neo N54L with 6 GB RAM on ZFS+XFS. Local initial backup: Borg 1.2.2 at 41s / 257,300, restic 0.14.0 at 23s / 260,520, Kopia 0.12.0 at 10s / 259,780 (the README’s size column carries no unit, so we do not supply one). Remote restore: Borg 244s, restic 28s, Kopia 258s (backup-bench README).

computingforgeeks is recent (updated 2026-03-31) and states its method — Ubuntu 24.04.4 LTS, 2 vCPU, 4 GB RAM, 30 GB SSD, BorgBackup 1.2.8, restic 0.16.4, Kopia 0.22.3, local filesystem repos, timed with /usr/bin/time -v. First backup: Borg 7.81s, restic 8.10s, Kopia 4.65s. Incremental: Borg 0.70s, restic 0.81s, Kopia 0.28s. Restore: Borg 0.16s, restic 3.67s, Kopia 4.39s. Peak memory on first backup: Borg 75 MB, restic 111 MB, Kopia 176 MB (computingforgeeks). The dataset is 370 MB across 1,957 files — far too small to project onto a multi-terabyte homelab, and the tool versions already trail current releases.

Those two sources point in opposite directions on restore, and they are not measuring the same thing: one has restic restoring roughly 9x faster than Borg over a remote transport, the other has Borg restoring roughly 23x faster than restic from a local repository. Different transports, datasets and versions — which is exactly why neither settles the question. Restore speed is unsettled. Anyone who ranks these three tools on speed with confidence is reading one benchmark and ignoring the other.

We also found a widely linked comparison publishing throughput figures like “180-220 MB/s” with no named author, no hardware spec, no tool versions and no reproducible commands. We are not citing it as evidence.

What competing guides skip (our angle)

One. The compression correction, with the version. restic 0.14.0, 2022-08-25, repository format v2, five modes today. Stating “all three compress” is not enough — readers need to know their old repository needs migrate upgrade_repo_v2 plus prune, and that after migration the repository only becomes readable by restic 0.14.0 or newer.

Two. The memory claims. The persistent line that restic’s RAM appetite makes it unsuitable for a small VPS traces to 2019-era write-ups that predate repository format v2 and compression entirely. restic’s official docs contain no RAM formula and no per-terabyte figure — only that limiting usable CPU cores slightly reduces memory use, that the backend can add a similar amount, and that temporary space equals the pack size multiplied by the number of backend connections plus one. Default pack size is 16 MiB, tunable with --pack-size or $RESTIC_PACK_SIZE; larger packs mean fewer files in the repository and better upload performance (restic tuning docs). Borg’s guidance is equally qualitative: have enough RAM for the repository index, chunks cache and files cache. Nobody publishes numbers. Treat the 111 MB / 75 MB / 176 MB peaks above as one 370 MB test, not as a spec.

Three. Plenty of people don’t run these bare. In the r/selfhosted threads we read, Backrest (a restic wrapper) is the single most-recommended answer, with autorestic and borgmatic close behind, and Vorta as the Borg desktop GUI. Comparing only the three binaries misses a layer that a lot of real deployments actually have. That is community sentiment from two 2024 threads with a small, self-selected sample — corroborate before betting on it — but it matches how homelabs actually look.

Four. Cloud egress. Kopia’s periodic maintenance reads from the repository. On a provider that charges for egress, that is a recurring line item nobody puts in the feature grid. Community-reported, not vendor-documented, but easy to verify against your own bill.

Five. Kopia’s honesty about its own encryption is a decent signal of doc quality: AES-256 and ChaCha20, with a footnote that the marketing term for this arrangement is imprecise (Kopia features). Kopia also scopes compression per policy — algorithm, minimum and maximum file size, and which extensions to compress — rather than one global setting (Kopia compression docs). For a laptop full of already-compressed media next to a server full of text logs, that is the more precise control.

Our call. Two of these are close enough that the tiebreaker has to be named honestly rather than asserted.

Bucket destination, command-line comfortable, mixed OS: restic — not because Kopia can’t do it, but because restic’s single-binary, one-flag operation has less surface to learn and its VSS handling on Windows is documented in more depth. If you would rather have a GUI and per-policy control than a smaller CLI, Kopia is the better fit for the same job, and calling it a tie would be fair.

Bucket destination, non-technical users or desktops to cover: Kopia — KopiaUI is the only official GUI of the three, and per-policy compression means one repository can hold a media laptop and a log server without compromise.

SSH destination you fully control: Borg 1.4.5 — not 2.0. Be precise about why: Borg has the widest choice of compression algorithms (including obfuscate, which nothing else advertises), while Kopia has the finest compression scoping (per policy, by file size and extension). Those are different axes. Pick Borg for the algorithm menu and the SSH-native design, not on a general “most control” claim. And whichever you pick, the tool that matters is the one that restores — in the threads we read, the single most-cited reason people arrive at all three is a Duplicati restore that failed when it was needed.

Backups are a layer, not a product, and the 3-2-1 backup rule is the strategy that layer serves — three copies, two devices, one off-site, and RAID is none of them. Snapshots on the source and a proper 3-2-1 target are separate jobs — see Sanoid and Syncoid for ZFS snapshots and Proxmox Backup Server in a 3-2-1 layout.

The 3-2-1 backup rule for homelabs — the strategy this tool choice serves: three copies, two devices, one off-site
Automated offsite backups with restic — our step-by-step restic setup, including repository format v2 and retention
Vaultwarden vs Bitwarden — your password vault is the first thing that belongs in these backups
Proxmox Backup Server in a 3-2-1 layout — where a file-level tool fits next to VM-level backup
Sanoid and Syncoid for ZFS snapshots — snapshot layer under any of these three
Best NAS hard drives — the drives your SSH-reachable repository should live on
Proxmox vs TrueNAS vs Unraid as a storage backend — picking the box that hosts the repository

Sources

Vaultwarden vs Bitwarden: Which Self-Hosted Server?

LK Wood IV — Tue, 21 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-21 · Updated 2026-07-21 · ~10 min read · St. Louis County, MO

TL;DR · One client, three servers

Vaultwarden and Bitwarden are not rival apps. You run the same official Bitwarden extension, desktop and mobile clients against a different backend.
There are three server shapes, not two: Bitwarden standard (eleven Docker containers, documented 2GB minimum / 4GB recommended RAM, 12GB minimum storage), Bitwarden lite (1 container, 200MB RAM, SQLite, ARM), and Vaultwarden (1 Rust container, no published hardware spec at all).
What you give up with Vaultwarden: SAML SSO, SCIM, custom roles, several enterprise policies, passkey login, and vendor support. What you gain for free: Emergency Access and Directory Connector support.
Security is a trade, not a win: smaller surface and two published 2024 audits on one side, SOC 2 Type II / SOC 3 / ISO 27001 and yearly named third-party audits on the other. Those are vendor attestations — self-hosting does not inherit them.
Running official clients against an unofficial backend is a standing commitment: Bitwarden does not guarantee the pairing, so pin your client versions, test updates before rolling them out, and keep a rollback path.

Note on sources: every figure below is pulled from vendor documentation, repository files or project wikis current as of 2026-07-20. Versions and requirements move; the Sources list at the bottom is the canonical set to re-check before you build.

The short version

The reason the vaultwarden vs bitwarden question feels unanswerable on most sites is that it is framed wrong. These are not two password managers. Vaultwarden is described by its own README as “an alternative server implementation of the Bitwarden Client API, written in Rust and compatible with official Bitwarden clients” (README). You install the exact same Bitwarden browser extension and phone app in both cases. The only thing you are choosing is which server those clients sync against, and therefore what that server costs you in RAM, features, licensing and personal responsibility.

Same clients, different server

Hold this straight and everything else falls into place. Vaultwarden even ships a patched build of Bitwarden’s own web vault rather than writing its own, and the project states plainly it is “not associated with, endorsed by, or affiliated with Bitwarden, Inc.” with “no collaboration” between the two (Vaultwarden FAQs). Bitwarden’s side of that non-relationship is documented too: it “cannot guarantee that official clients will work perfectly with non-official servers,” and says its support may be limited in helping with client issues on a non-official server (Bitwarden hosting FAQs).

That cuts both directions. The Vaultwarden wiki warns that filing a client bug on a Bitwarden repository will most likely be closed on the grounds that they do not support alternative servers (client troubleshooting), and the README carries a bolded instruction to report everything to Vaultwarden instead, whatever client you are on. Choosing Vaultwarden means accepting that you are now the integration point between two projects that do not talk to each other.

That has a practical cost worth planning for rather than discovering. Client compatibility is not a contract — it is a property that has held well in practice because Vaultwarden tracks the client API closely, but nothing obliges Bitwarden to preserve it across a client or API change. Treat client updates the way you would treat any dependency you do not control: pin the versions your household actually runs, let a new browser-extension or mobile release sit for a few days before you push it to everyone, keep a Vaultwarden release you know works, and make sure your export is current before any upgrade on either side. None of that is onerous. It is simply the maintenance you took on in exchange for the single container.

The resource gap is the real decision

Bitwarden’s own blog says it directly: the lite route deploys a single container, where the standard deployment uses eleven different Docker containers (Bitwarden blog). Reading the current setup template, the eleven that blog post refers to are mssql (emitted only when the built-in SQL Server is enabled), web, attachments, api, identity, sso, admin, icons, notifications, events and nginx, plus two feature-flagged services, key-connector and scim (DockerCompose.hbs).

Documented minimums for that standard Linux deployment are an x64 1.4GHz processor, 2GB RAM and 12GB storage, with 2GHz dual core, 4GB RAM and 25GB recommended, on Docker Engine 26+ (install on-premise Linux). It ships an MSSQL Express image with a 10GB maximum database size, and a standard deployment can be pointed at an external database instead of the bundled one — but SQLite, PostgreSQL and MySQL/MariaDB are documented only for lite (lite docs).

Vaultwarden is one container, and since 1.17.0 a single unified image covers SQLite, MySQL and PostgreSQL, in Debian and slimmer Alpine variants across x86_64, armv6, armv7 and aarch64 (image guide). Here is the honest gap: Vaultwarden publishes no minimum hardware table at all. As of 2026-07-20 the wiki index carries no hardware-requirements page. The only numbers available are forum posts, and they should be labelled as such. Collaborator BlackDex suggested 2 vCPUs and 1GB of memory with storage sized to attachments, and noted that in theory Vaultwarden can run on well under 100MB by itself (forum). In a separate discussion the same collaborator put a single core at “probably fine” without heavy load, one user reported 512MB working, and another warned that 1GB “could become a problem” if you build the container yourself (discussion 2903). Treat those as community opinion, not specification.

Practically, that footprint is why Vaultwarden lands on a Pi or a small node next to everything else. If you are sizing that box, the same reasoning we used for picking a mini PC for Home Assistant applies to any small always-on server, and our Vaultwarden on Proxmox setup guide walks the LXC-and-reverse-proxy build end to end.

Head to head

Dimension	Bitwarden self-hosted (standard)	Bitwarden lite	Vaultwarden
Containers	11 base (+2 conditional: key-connector, scim)	1	1
Min RAM (documented)	2GB (rec. 4GB)	200 MB	not documented
Min storage (documented)	12GB (rec. 25GB)	1GB	not documented
Min CPU (documented)	x64 1.4GHz (rec. 2GHz dual core)	not stated	not documented
Database	MSSQL (bundled Express or external)	MSSQL / PostgreSQL / SQLite / MySQL-MariaDB	SQLite / MySQL / PostgreSQL
ARM / Raspberry Pi	no — x64 required	yes	yes (multi-arch)
Vendor stance on business use	no personal-use restriction stated	“not for use in business contexts”	individuals, families, smaller organizations
SCIM	yes (Teams/Enterprise)	n/a	not documented as supported
SSO	yes (Enterprise, `/bitwarden_license`)	n/a	OIDC only, master password still required
Emergency Access	premium / paid org only	premium	included
Vendor compliance attestations	SOC 2 Type II, SOC 3, ISO 27001, HIPAA	same	none claimed
Audits	annual third-party, named firms 2018–2025	same	BSI CAOS (v1.30.3, Oct 2024), ERNW pentest (Oct 2024)
License	AGPL-3.0 + Bitwarden License for `/bitwarden_license`	same	AGPL-3.0
Latest verified version	v2026.6.2 (2026-07-08)	same repo	1.36.0 (2026-05-03)

Version data is from the GitHub release APIs for bitwarden/server and dani-garcia/vaultwarden.

What you actually give up

Vaultwarden’s supported list is longer than most comparisons admit: organization vaults, groups, collections, event logs, attachments, TOTP, Bitwarden Send, trash, master password re-prompt, personal API keys, 2FA via email, Duo, YubiKey, FIDO2 WebAuthn and authenticator apps, WebSocket live sync, admin account recovery, and a subset of enterprise policies (wiki Home).

The gaps are specific. Login with Passkeys, New Device Login Protection and the full Bitwarden Public API / Organization API key sit under “may be added over time,” with the public API only partially implemented. Custom roles and the require-SSO-authentication, vault-timeout and remove-individual-vault-export policies are “unlikely to be added without external contribution.” SSO is OpenID Connect only, with no SAML, and carries real caveats: “a master password will still be required and not controlled by the SSO,” signup is blocked when the provider reports an unverified email, and Auth0 is documented as not working because it “appear[s] not to follow the spec” (SSO wiki). Authentik is on the documented provider list, so if you already run our Authentik SSO build the OIDC path is realistic.

SCIM is the one to phrase carefully. It appears in neither the supported nor the not-implemented list, and no SCIM page appears in the wiki index as of 2026-07-20, so the correct statement is “not documented as supported,” not “explicitly unsupported.” On the official side, SCIM v2 and Directory Connector are both Teams/Enterprise features (SCIM, Directory Connector).

Two things run the other way. Emergency Access is included in Vaultwarden but is premium or paid-organization only on official Bitwarden (Emergency Access). Directory Connector is listed as supported against Vaultwarden despite being Teams/Enterprise-gated upstream. Maintainer jjlin’s summary of getting enterprise features free is “Some, but not all,” alongside a warning about third-party projects that bypass Bitwarden’s license checks: “it seems almost certain that they’re breaking the terms of Bitwarden’s licenses” (discussion 4132).

The licensing detail people miss

Self-hosting Bitwarden is free, but “some features must be unlocked in your self-hosted instance with a registered license file,” and that license file comes from the Bitwarden-hosted web app via a premium subscription or an organization owner (licensing). Only Families and Enterprise organizations can be imported to self-hosted servers, organizations must first be created in the cloud web vault for billing, and license sync requires globalSettings__enableCloudCommunication=true (self-host an organization). An installation ID and key from bitwarden.com/host are mandatory either way. At the source level, files under /bitwarden_license (Commercial.Core, SSO) are not AGPL and production use requires a paid subscription (LICENSE_FAQ). Vaultwarden is AGPL-3.0 throughout (repo metadata).

The security trade

Bitwarden’s white paper documents a dedicated security engineering team, SOC 2 Type II and SOC 3 renewed annually, ISO 27001, third-party reviews at least once per year, AES-CBC 256-bit with HMAC, and a PBKDF2 SHA-256 default of 600,000 iterations with optional Argon2id (white paper). HIPAA is claimed separately, with annual third-party audits against the Security Rule (compliance) — worth noting because the white paper itself does not mention it.

One thing to be clear about, because it is the most expensive misreading in this whole comparison: those are attestations about Bitwarden the vendor and its hosted service, not about your server. Standing up the official code on your own hardware does not make your deployment SOC 2 or ISO 27001 compliant, and it does not make it HIPAA compliant. Compliance follows the controls you operate and the scope an auditor agrees to — your encryption at rest, your access control, your logging, your business-associate agreements. What the official server buys you is a vendor with attestations you can reference and a support contract to point at. The audit scope is still yours to earn. The audit page names firms by year, including a 2025 cryptography report from the Applied Cryptography Group at ETH Zurich, 2025 mobile work by Unit 42, and multiple Cure53 engagements back to 2018 (audits).

Vaultwarden’s counter is a smaller surface and real audit history. Two published reviews from October 2024: the German BSI’s CAOS code audit of v1.30.3, and an ERNW penetration test that “identified 3 vulnerabilities, including an authentication bypass,” responsibly disclosed (audits wiki). Release 1.36.0 shipped fixes for SSO login CSRF, user and organization enumeration, SSO existing-user binding, and SSRF via the icon endpoint (releases) — evidence of an active response process, not of an absence of bugs.

The burden shifts to you. The hardening guide states that Rocket’s built-in TLS is “intended for development use only” and not production-ready, so a reverse proxy is required for any public instance, and it recommends disabling registration, running containers as non-root, minimal volume mounts and fail2ban (hardening guide). One proxy gotcha: the WebSocket library does not honour X-Forwarded-For or Forwarded headers in any form (FAQs). Pick your proxy with that in mind — our Caddy vs Nginx Proxy Manager vs Traefik comparison covers the trade-offs. And take the README’s disclaimer literally: the project “cannot be held liable for any data loss,” and recommends regular backups. Encrypted offsite copies are the minimum bar for a password database — our restic setup walk-through is the fastest path there, and if you have not picked a tool yet, restic vs Borg vs Kopia settles it by where the backup lands.

Mobile push is the sneaky gotcha

Push notifications have worked since Vaultwarden 1.29.0, but they require an official Bitwarden installation ID and key from bitwarden.com/host, and they will not work with Bitwarden apps installed from F-Droid, Neo Store or other alternative stores, because those builds ship without Firebase Messaging support. The client also needs firebaseinstallations.googleapis.com reachable, apps connected before v1.30.2 must clear data or reinstall, and EU and US regions need different relay and identity URIs (push wiki). If your reason for self-hosting is to stay off Google services, that constraint deserves to be in the decision, not discovered afterward.

Run Vaultwarden if / run official Bitwarden if

Run Vaultwarden if you are one person, a family, or a small team; your hardware is a mini PC, a Pi or a modest VM; you want SQLite and a single container; you want Emergency Access without a subscription; and you accept full ownership of TLS, hardening, updates and backups. The project scopes itself the same way, targeting “individuals, families, and smaller organizations.” Community sizing is unremarkable at this scale — one contributor reported it running well on a Raspberry Pi and put 25 users comfortably inside its range, for a workload that mostly idles between syncs (forum).

Run official Bitwarden (standard) if you need SAML SSO, SCIM provisioning, custom roles, Key Connector, vendor support, or a compliance answer for an auditor; if you can supply 4GB RAM and 25GB storage comfortably; and if you would rather pay for a license file than own the incident. The community framing matches — the recurring argument for the official server is simply preferring to let Bitwarden maintain the infrastructure (Bitwarden forums).

Consider Bitwarden lite if you want the official codebase on Vaultwarden-class hardware: 1 container, at least 200MB RAM, 1GB storage, SQLite or PostgreSQL or MySQL, ARM supported. The catch is written into the docs: lite “is intended for personal use and home-labs, not for use in business contexts.”

What competing guides skip (our angle)

Four things almost never make it into other comparisons.

First, Bitwarden lite narrows the old resource argument for personal use. Most articles still compare Vaultwarden against the eleven-container stack, which has not been the only official option for a while. For a homelab, 1 container at 200MB is a genuinely competitive official answer. It does not erase the case for Vaultwarden, though — lite is scoped out of business use by its own docs, it does not close the Emergency-Access-for-free gap, and Vaultwarden still carries the broader multi-arch story. What changes is that “eleven containers” is no longer a reason on its own.

Second, the “Vaultwarden has never been audited” claim is stale. It traces to a 2022 community post and is contradicted by the 2024 BSI and ERNW work. Repeating it in 2026 is simply wrong.

Third, Vaultwarden’s own scope statement contradicts its feature list. The wiki says development of features “mainly useful to larger organizations (e.g., single sign-on, directory syncing, etc.) is not a priority” while the same page lists OIDC SSO and Directory Connector as implemented. Read that as positioning and prioritization, not as a current feature gap.

Fourth, one Bitwarden doc inconsistency is worth flagging rather than papering over. The self-hosting page says only Families and Enterprise organizations can be imported to self-hosted servers, yet Teams is listed as eligible for both SCIM and Directory Connector. We could not resolve that from the docs, so treat Teams self-hosting as unverified and confirm with Bitwarden before planning around it. We also verified no pricing figures for this article, so none appear here.

Vaultwarden on Proxmox: full setup guide
Self-hosted SSO with Authentik
Authelia vs Authentik: which self-hosted SSO
Caddy vs Nginx Proxy Manager vs Traefik
Automated offsite backups with restic
restic vs Borg vs Kopia: which backup tool
Best mini PC for Home Assistant — the sizing logic for any small always-on box

Sources

Best Mini PC for Home Assistant (2026)

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · Updated 2026-07-20 · ~13 min read · St. Louis County, MO

Some retailer links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate we earn from qualifying purchases. Commissions never influence which products get recommended — see our disclosure.

TL;DR · Which mini PC for Home Assistant

Best pick for most people (new): an Intel N100 mini PC with 16GB RAM + an SSD (e.g. Beelink S12 Pro, ~$339). Tiny, quiet, ~10–14W idle, and its Quick Sync runs Frigate.
Best value + headroom: a refurbished enterprise micro — Dell OptiPlex Micro or Lenovo ThinkCentre Tiny, 6-core i5, ~$150–250, with a Windows Pro license thrown in.
Home Assistant is tiny. It runs on a 2GB Raspberry Pi; the official Green box has 4GB. You are buying a mini PC for SSD reliability and headroom, not raw speed.
Only size up to a 6–8 core i5/Ryzen for heavy Frigate cameras or local voice — the two workloads that actually stress a small box.
The 2026 catch: buy a box that already includes RAM+SSD, not a barebone — the RAM shortage has flipped barebone economics upside down.

CPU specs are from Intel ARK; requirements from Home Assistant and Frigate docs. Prices are a live Amazon snapshot dated 2026-07-20 and move week to week — check the retailer link before buying.

The short version

Almost every “best mini PC for Home Assistant” list gets the framing backwards. They rank boxes by raw power, when the real story is that Home Assistant barely needs any. It runs happily on a 2GB Raspberry Pi, and the official Home Assistant Green appliance ships with a quad-core Arm chip and just 4GB of RAM. So the question is not “how much CPU do I need for Home Assistant?” — it is “what is the most reliable, low-power box that will still have headroom in three years?”

The answer, for most people, is a new Intel N100 mini PC with 16GB of RAM and an SSD. It’s cheap, sips 7–14 watts, is silent, and — importantly for cameras — its integrated GPU includes Intel Quick Sync. If you’re comfortable buying used, a refurbished enterprise micro (a Dell OptiPlex Micro or Lenovo ThinkCentre Tiny) gives you a 6-core i5 and a Windows license for a bit more idle power and often less money. You only step up to something bigger for two specific workloads — a busy Frigate camera setup or local voice — which we’ll size precisely below. If you plan to run Home Assistant as one VM among several services, our Home Assistant on Proxmox guide covers that install; if you want a bigger virtualization host in general, see the best mini PCs for a homelab. This page is specifically about the smart-home box.

What Home Assistant actually needs

Home Assistant doesn’t publish a single tidy “recommended specs” table for an x86 mini PC, so here is what the official docs do say, and what it means:

The only hard minimum is the Pi figure: the Raspberry Pi install page calls for “minimum 2 GB RAM” and a card “at least 32 GB.” That’s the floor for Home Assistant by itself.
The official appliance is 4GB. Home Assistant Green — the box the project sells for people who don’t want to think about hardware — has 4GB of RAM, 32GB of eMMC, and a modest quad-core Arm CPU. If that runs Home Assistant well, a 6-watt N100 with 16GB obliterates the requirement.
On x86, use an SSD, not an SD card. The generic x86-64 install docs assume an internal S-ATA/M.2 SSD or eMMC boot medium; the machine just needs to be 64-bit and boot via UEFI, which covers essentially every mini PC made in the last decade.

The practical takeaway: buy for headroom and reliability, not benchmarks. 16GB of RAM and a 256–512GB SSD is the community’s comfortable sweet spot — not because Home Assistant needs it, but because add-ons, a few months of history, and future tinkering do, and because RAM and an SSD are cheap insurance against ever thinking about it again.

Why a mini PC beats a Raspberry Pi

The single most common Home Assistant hardware story on the forums is an SD card dying. Home Assistant writes to its database constantly (every sensor update, every state change), and that steady write load chews through Raspberry Pi SD cards — users routinely report two or three dead cards in a year, even on premium and “industrial” cards. The fix is always the same: move to a real SSD.

A mini PC solves that by default — it boots from a SATA or NVMe SSD that laughs off Home Assistant’s write pattern. On top of that you get far more CPU and RAM headroom than a Pi, USB 3.0 ports, and a real SSD in place of a wear-prone card — and once you add a Pi’s case, power supply, and SSD, a used mini PC often isn’t much more expensive anyway. A Pi is a fine way to learn Home Assistant. A mini PC is where you put it when you want to stop maintaining the hardware.

The N100 (and N150): the low-power sweet spot

The chip at the center of nearly every good Home Assistant mini PC is the Intel Processor N100. Per Intel’s ARK spec page, it’s a 4-core / 4-thread part (all efficient Gracemont cores) with 6MB of cache, a 6-watt base power, up to 3.40GHz turbo, and an Intel UHD integrated GPU with 24 execution units. Two specs matter most for a smart-home box: it officially tops out at 16GB of RAM (single channel), and its iGPU includes Intel Quick Sync Video — the hardware video engine that makes Frigate practical (more on that next).

You’ll also see the newer Intel N150 in 2026 boxes. Don’t overthink it: per Intel ARK, the N150 (code-named Twin Lake) is a minor refresh of the same Alder Lake-N-class silicon. The only spec changes are a slightly higher CPU turbo (3.60GHz vs 3.40GHz) and a slightly higher iGPU clock (1.0GHz vs 750MHz). Same 4 cores, same 6-watt power, same 16GB memory ceiling, same 24-EU iGPU, same Quick Sync. For Home Assistant, an N100 and an N150 are functionally identical — buy whichever is cheaper.

One honest caveat on RAM: Intel’s official ceiling for both chips is 16GB, but many vendors advertise and ship 32GB single modules that work in practice. Treat anything above 16GB as board-dependent rather than an Intel guarantee — and for Home Assistant, 16GB is already more than you need.

When to actually size up: Frigate and voice

If you only run Home Assistant plus normal integrations and add-ons, an N100 is overkill and you can stop reading and buy one. Two workloads change the math:

Frigate NVR (cameras). Frigate is CPU-hungry in one specific way: decoding camera video streams. Frigate’s docs say it is “highly recommended to use an integrated or discrete GPU for hardware acceleration” because decoding camera streams is the CPU-heavy part. Here’s the good news that the buying guides bury: the N100’s Quick Sync already does this, and the same iGPU runs object detection through Frigate’s OpenVINO detector — so a single N100 box handles both jobs. That’s why Frigate’s own recommended hardware list includes an N100 mini PC (the Beelink EQ13), which “can run object detection on several 1080p cameras with low-medium activity.” Note what you don’t need: Frigate now says the Google Coral is “no longer recommended for new installations” (outside niche ultra-low-power builds) and points out that “the Coral does not help with decoding video streams” anyway. Skip it. You move up to a 6–8 core i5 or Ryzen (and more RAM) only when you run many cameras, higher resolutions, or high-activity scenes. Storage scales with exactly the same three inputs — the Frigate NVR storage calculator turns camera count, resolution, and retention days into a drive size and the /dev/shm value Frigate needs.

Local voice (Whisper). Running your own speech-to-text with Whisper is the other real load. Home Assistant is blunt about it: Whisper “is only a great option” if “you have powerful hardware at home,” noting that a task taking ~8 seconds on a Raspberry Pi 4 is “done in under a second” on an Intel NUC. And the largest Whisper models “require a GPU” and are “unusable on a Raspberry Pi or even an N100-class PC.” The lighter Piper text-to-speech is not the bottleneck. Translation: an N100 handles basic local voice fine, but a serious multi-language voice assistant is a reason to go bigger.

The recurring community wisdom, and it’s good advice: don’t pre-buy headroom. Start with an N100 or a refurb i5, measure your real CPU and RAM once your cameras and add-ons are running, and upgrade only if the numbers say so.

The picks — live Amazon snapshot, 2026-07-20

Prices below are a live US Amazon pull captured 2026-07-20 and move week to week — check the retailer link before buying. All of these ship complete (with RAM, SSD, and an OS), which in 2026 matters more than usual — see the barebone note after the table.

Pick	Why	CPU / RAM / SSD	Price	Link
Beelink S12 Pro (best for most, new)	The default N100 box: quiet, ~10–14W, Quick Sync for Frigate	N100 · 16GB DDR4 · 500GB SSD	$339	Amazon
Dell OptiPlex 7060 Micro (best value)	6-core i5 = more headroom than N100, plus a Win 11 Pro license	i5-8500T · 16GB · 256GB SSD (Renewed)	$195.89	Amazon
Lenovo ThinkCentre M720q (refurb alt)	Same class as the Dell; pick on price/condition	i5-8500T · 16GB · 256GB SSD (Renewed)	$220	Amazon
GMKtec M3 (step up, new)	For heavy Frigate + local voice: 8-core i5, room to grow	i5-12450H · 16GB DDR4 · 512GB SSD	$449.99	Amazon

Idle power, measured: an N100 box like the Beelink EQ12 was measured at 12–14W at the wall by CNX Software (real-world N100 idle runs roughly 10–14W depending on OS and peripherals, and a lean fanless box with a single RAM stick can dip lower). The refurbished Tiny/Mini/Micro machines idle a little higher — ServeTheHome measured the Dell OptiPlex 3050 Micro and Lenovo M720q at 11–14W, with 6-core i5 configs closer to 15–20W. Across a year of 24/7 running, that difference is only about $8–12 in electricity — real, but not decisive. Run your own numbers in the homelab power-cost calculator, and see the 24/7 idle-power breakdown for the full math.

The barebone trap (the one 2026 twist)

Here’s the money-saving detail every competing guide misses. Because of the 2026 memory shortage, RAM prices have spiked — so a “cheap” barebone mini PC is now the most expensive way to end up running. Buy the barebone, add your own RAM and SSD, and you often pay more than a complete box that already includes them. A live example from this same July 20 pull: GMKtec’s G3 Pro is $189.99 barebone (no RAM/SSD/OS) versus $329.99 complete with 16GB, a 512GB SSD, and Windows — and in 2026 that RAM, SSD, and license cost more than the $140 gap if you buy them separately. The rule: for a Home Assistant box, buy it complete, or buy a used machine that already comes with RAM. The sticker price on a barebone is a down payment, not the total.

The Zigbee / Z-Wave USB gotcha nobody warns you about

This one bites almost everyone, and it’s the difference between a rock-solid smart home and mysterious dropouts. When you plug a Zigbee or Z-Wave/Thread USB stick directly into a mini PC — especially next to a USB 3.0 or USB-C port — the high-speed USB signaling raises the noise floor in the 2.4GHz band and cripples your Zigbee/Thread network. This isn’t folklore; it’s official Home Assistant ZHA guidance: “Make sure to only connect the Zigbee USB adapter to a USB 2.0 port (and not to a USB 3.x port)”, and place it away from interference “preferably by using an adequately long shielded USB extension cable.” Home Assistant’s own Connect ZBT-2 adapter even ships with a 1.5-meter cable and a free-standing base specifically because “USB ports and nearby electronics can create interference.” So: USB 2.0 port + a meter of shielded extension cable, stick standing away from the box. It costs a few dollars and saves hours of debugging.

HAOS bare metal or a Proxmox VM?

Two good options, one clear loser:

Home Assistant OS, bare metal — the officially recommended install for most users. If the mini PC will only run Home Assistant, do this: it’s appliance-like, updates and backups live in the UI, and there’s no command line. This is the right default for an N100 box dedicated to the smart home.
HAOS in a Proxmox VM — the community favorite when the box will also run other things (Pi-hole, Plex, a Frigate container, a NAS role). You get VM snapshots, the ability to hard-restart Home Assistant remotely if it hangs, and room to run everything on one machine, with negligible performance loss. Our step-by-step Home Assistant on Proxmox guide walks through it, including USB passthrough for your Zigbee stick.
Supervised on Debian — the least-recommended path; you’re on your own for support if you install other software alongside it.

Simple rule: only Home Assistant → HAOS on the metal. Home Assistant plus other services → HAOS in a Proxmox VM.

What competing guides skip (our angle)

Most “best mini PC for Home Assistant” pages are a list of Beelink boxes with affiliate links. What they consistently miss, all covered above:

That Home Assistant is tiny — they rank by CPU power when the real buying axis is SSD reliability + headroom, and they never mention the official 4GB Green box as the baseline.
That Frigate needs no Coral on an N100 — the N100’s Quick Sync does the decode and OpenVINO does the detection on the same chip; Frigate itself now deprecates the Coral for new installs.
The Zigbee USB-3 interference fix — official ZHA guidance that turns a flaky network solid, absent from nearly every hardware list.
The 2026 barebone trap — with RAM prices spiking, a complete box beats a barebone, the opposite of the usual advice.

Home Assistant on Proxmox: install HAOS as a VM — the install guide for the box you just bought.
Best mini PC for a homelab 2026 — if you want a bigger virtualization host (MS-01, NUC, used SFF), not just a smart-home box.
24/7 homelab idle power costs — what an always-on mini PC really costs to run.
Best NAS for Plex and Jellyfin 2026 — where your camera recordings and media should actually live.
Homelab power-cost calculator — plug in idle watts and your electricity rate.

Sources

Hardware specifications (verified live):

Intel Processor N100 — Intel ARK: https://www.intel.com/content/www/us/en/products/sku/231803/intel-processor-n100-6m-cache-up-to-3-40-ghz/specifications.html
Intel Processor N150 — Intel ARK: https://www.intel.com/content/www/us/en/products/sku/241636/intel-processor-n150-6m-cache-up-to-3-60-ghz/specifications.html
Beelink EQ12 (N100) measured idle power — CNX Software: https://www.cnx-software.com/2023/05/16/beelink-eq12-review-intel-processor-n100-mini-pc-windows-11-truenas-pfsense-ubuntu/
Dell OptiPlex 3050 Micro / Lenovo M720q measured idle — ServeTheHome Project TinyMiniMicro: https://www.servethehome.com/dell-optiplex-3050-micro-project-tinyminimicro-guide-review/3/

Home Assistant + Frigate documentation:

Home Assistant install requirements (Pi + generic x86-64): https://www.home-assistant.io/installation/generic-x86-64/ and https://www.home-assistant.io/installation/raspberrypi/
Home Assistant Green specifications: https://www.home-assistant.io/green/
Home Assistant ZHA (Zigbee USB adapter guidance): https://www.home-assistant.io/integrations/zha/
Home Assistant local voice (Whisper/Piper): https://www.home-assistant.io/voice_control/voice_remote_local_assistant/
Frigate hardware + hardware-accelerated decoding + detectors: https://docs.frigate.video/frigate/hardware/, https://docs.frigate.video/configuration/hardware_acceleration_video/, and https://docs.frigate.video/configuration/object_detectors/

Community consensus (mini-PC choice, sizing, SD-card reliability, and Zigbee interference) was reviewed on the community.home-assistant.io forum and is cited inline as community opinion. Prices are a live Amazon snapshot dated 2026-07-20.

RTX 5070 vs RTX 5070 Ti: Is the Ti Worth It in 2026?

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · Updated 2026-07-20 · ~11 min read · St. Louis County, MO

TL;DR · The verdict in 2026

Performance gap: the 5070 Ti is ~20–22% faster at 1440p on average (range ~6% to ~30% by game), with more separation at 4K.
The real price gap isn't $200: at July-2026 street prices it's ~$300–450 (5070 ~$630–750, Ti ~$920–1,080). The "$200 more" everyone quotes is MSRP-only, and neither card sells at MSRP.
Buy the RTX 5070 for high-refresh 1440p on a budget — 12GB is fine there today (~$636, Amazon).
Buy the RTX 5070 Ti for 4K, VRAM longevity (16GB), heavy ray tracing, or CUDA/AI work (~$920, Amazon).
The spoiler: AMD's RX 9070 XT gives ~95% of the Ti's raster for hundreds less. Consider it unless you specifically need RT/DLSS/CUDA.

Specs are from NVIDIA; benchmark deltas are from independent testing (GamersNexus), cited inline. Prices are a live Amazon snapshot dated 2026-07-20 and move week to week — a GDDR7 shortage has GPU prices unusually volatile, so check the retailer link before buying.

The real question isn’t the specs — it’s the 2026 price

Every “5070 vs 5070 Ti” guide opens the same way: the Ti costs $200 more, so is it 20% faster? That framing is stale, and it’s the first thing to fix. The $200 figure is the MSRP gap — $549 vs $749 — and in mid-2026 neither card sells at MSRP.

In a live Amazon check on 2026-07-20, mainstream RTX 5070 partner cards ran roughly $630–750 (some dipping toward ~$580 with checkout coupons), while RTX 5070 Ti cards ran roughly $920–1,080, with premium models past $1,300. So the real-world “Ti tax” right now is about $300–450, not $200 — and the cheapest 5070 Ti often costs what an RTX 5080 launched at. A major driver is the worldwide GDDR7/DRAM shortage, fed by AI-datacenter demand, that has pushed GPU street prices well above late-2025 levels — with board-partner markups piling on top; SK Hynix has called 2027 the worst year for the crunch, so don’t count on near-term relief. Every guide still quoting “$200” was written before this, and it changes the value math completely.

So read the performance gap below through the real price gap, not the sticker one.

The specs, honestly

Both cards are Blackwell, built on the same architecture — the Ti simply has more of everything. Per NVIDIA’s spec page:

Spec	RTX 5070	RTX 5070 Ti	Delta
CUDA cores	6,144	8,960	+46%
VRAM	12GB GDDR7	16GB GDDR7	+4GB
Memory bus	192-bit	256-bit	wider
Bandwidth	672 GB/s	896 GB/s	+33%
TGP	250W	300W	+50W
MSRP	$549	$749	+$200

The +46% CUDA and +33% bandwidth look decisive on paper, but paper isn’t frames — and this is where most spec-sheet comparisons quietly overstate the gap. (NVIDIA asks for 650W of system power for the 5070 and 750W for the 5070 Ti; our PSU wattage calculator sizes the supply for your exact parts, and what PSU an RTX 5070 needs walks through where those numbers come from.)

How much faster is the Ti, really?

Independent testing lands well below the marketing math. In GamersNexus’s benchmark suite, the RTX 5070 Ti averages about 20–22% faster than the 5070 at 1440p rasterization — not the “up to 30%” you’ll see in card listings. The important part is the range, because it tells you where your money actually goes:

CPU-bound games (e.g. Final Fantasy XIV): as little as ~6% — both cards are waiting on the processor, so the Ti’s extra hardware barely moves.
Bandwidth- and VRAM-bound games (e.g. Resident Evil 4 ~+27%, Dying Light 2 ~+23%): the widest gaps, where the Ti’s 256-bit bus and 16GB stretch their legs.
At 4K: the gap is directionally larger than at 1440p, for the same reason — higher resolution leans harder on memory bandwidth and capacity.

So the honest read is “roughly a fifth faster at 1440p, more at 4K, and it depends heavily on the game.” That’s a real upgrade — but weigh it against a ~$300–450 real-world price gap, not a $200 one. For the broader picture of where both land against every other current card, see the 2026 GPU hierarchy.

The 12GB vs 16GB question — the part every 2025 guide skips

This is the single most future-facing difference, and it’s why the launch-era comparisons still ranking for this search feel dated. The RTX 5070’s 12GB is fine for most 1440p gaming today — most current games stay within it at high settings and 1440p, though path-traced titles and ultra-texture packs can pressure it even there. The problems show up in two places: 4K and time. Several 2026 titles already exceed 12GB at 4K with high-resolution textures or heavy ray tracing, and when a card runs out of VRAM it doesn’t slow down gracefully — it stutters and drops texture quality even when its raw speed says it should keep up.

The practical rule: if you game at 1440p and upgrade every couple of years, 12GB on the 5070 is genuinely enough. If you game at 4K, run RT-heavy titles, or want to keep the card 4+ years, the 5070 Ti’s 16GB is the safer place to put your money — and it’s a big reason the Ti ages better than the raw FPS gap suggests.

The AMD spoiler: RX 9070 XT

You can’t answer “5070 or 5070 Ti” in 2026 without naming the card that undercuts both. AMD’s RX 9070 XT carries the same 16GB of VRAM, and GamersNexus measured it at roughly 95% of the 5070 Ti’s rasterization in strong-case titles — while it sells at or near its $599 MSRP and the 5070 Ti does not. That routinely makes the AMD card $250–400 cheaper for nearly the same raster gaming.

The 5070 Ti earns its NVIDIA premium in specific places: ray tracing and path tracing, DLSS 4 multi-frame generation, and CUDA/NVENC for AI and content work — and note the Ti uses the RTX 5080’s larger GB203 die with dual NVENC video encoders, versus a single encoder on the 5070’s GB205, a real edge for streamers and video editors. If those are core to what you do, pay for them. If you mostly play rasterized games, the 9070 XT is the value pick — we break down that exact matchup in RTX 5070 Ti vs RX 9070 XT. And at the plain 5070’s own price tier, AMD’s direct rival is the RX 9070 — see RTX 5070 vs RX 9070 for that head-to-head.

Don’t get talked up into a 5080

One more guardrail, because the upsell doesn’t stop at the Ti. At 2026 street prices the RTX 5080 costs roughly 39% more than the 5070 Ti but is only about 14–17% faster in gaming (even at MSRP it’s ~33% more, $999 vs $749). Stepping from the 5070 to the 5070 Ti buys ~20% for its money; stepping from the 5070 Ti to the 5080 buys far less. The 5070 Ti is the sensible ceiling of the value stack — above it, you pay flagship prices for single-digit-to-mid-teens gains.

So which should you buy?

Play at 1440p, want the best value: the RTX 5070. 12GB holds up at 1440p, and at ~$630–650 you keep hundreds in your pocket versus the Ti (GIGABYTE RTX 5070 WINDFORCE, Amazon).
Game at 4K, want VRAM longevity, or do RT/CUDA/AI work: the RTX 5070 Ti. The 16GB and wider bus are worth it here (PNY RTX 5070 Ti, Amazon).
Just want the most raster per dollar: cross-shop the RX 9070 XT before committing to either NVIDIA card.

The one thing not to do is buy the 5070 Ti on the assumption it’s “only $200 more” — verify the live gap first. Prices here are a dated 2026-07-20 snapshot in a volatile GDDR7-shortage market; treat them as a method, not a promise, and check the current retailer price before you buy.

RTX 5070 vs RX 9070: The Honest 1440p Verdict 2026

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · Updated 2026-07-20 · ~11 min read · St. Louis County, MO

TL;DR · The verdict in 2026

Raster winner: the RX 9070 is ~11–15% faster at 1440p and leads at 4K too (roughly 0–18% by game), per independent testing.
VRAM & power: the 9070 has 16GB vs 12GB and a 220W vs 250W board rating — more headroom, better efficiency.
Where the 5070 wins: heavy ray tracing (up to ~57% ahead in path-traced Wukong), DLSS 4 multi-frame gen, and CUDA/NVENC for AI and video.
Buy the RX 9070 for pure 1440p value and VRAM longevity (~$620, XFX Swift RX 9070, Amazon).
Buy the RTX 5070 for ray tracing, DLSS 4, or creator/AI work (~$630, PNY RTX 5070, Amazon).

Specs are from NVIDIA and AMD; benchmark deltas are from independent testing (GamersNexus), cited inline. Prices are a live Amazon snapshot dated 2026-07-20 and move week to week in the current GDDR shortage — check the retailer link before buying.

The 2026 answer isn’t the launch-day answer

Nvidia and AMD launched these two cards a day apart in March 2025 at the exact same price — $549 — and the internet spent the following year repeating one line: the RX 9070 wins because it’s faster for the same money. At MSRP, that was simply true. In mid-2026 it’s more complicated, and the honest answer now turns on what you actually do with the card, not the sticker.

Two things changed. First, neither card reliably sells at $549 anymore — a worldwide GDDR/DRAM shortage fed by AI-datacenter demand has pushed street prices up and made them volatile, and board-partner markups vary by model. Second, AMD’s drivers have matured, nudging the 9070 a little further ahead in raster while NVIDIA’s software advantages (DLSS 4, CUDA) stayed put. So the matchup is less “which is cheaper” and more “which feature set fits you.” Let’s settle it with real numbers.

The specs, honestly

Both are current-generation cards — NVIDIA’s Blackwell against AMD’s RDNA 4 — aimed squarely at 1440p. They take opposite approaches: NVIDIA leans on software and ray tracing, AMD on raw memory and rasterization.

Spec	RTX 5070	RX 9070	Edge
Architecture	Blackwell (GB205)	RDNA 4 (Navi 48)	—
Shaders	6,144 CUDA	3,584 stream proc. (56 CU)	architecture-specific
VRAM	12GB GDDR7	16GB GDDR6	9070 (+4GB)
Memory bus	192-bit	256-bit	9070
Board power	250W	220W	9070 (–30W)
Upscaling	DLSS 4 (MFG)	FSR 4	5070
MSRP	$549	$549	tie

The spec sheet tells the story in miniature: the 9070 brings more memory, a wider bus, and lower power; the 5070 answers with DLSS 4 and NVIDIA’s ray tracing pedigree. Note that shader counts don’t compare across brands — a CUDA core and an RDNA stream processor do different amounts of work — so the only thing that settles the performance question is real game testing. (For a build around either 220–250W card, our PSU wattage calculator sizes the supply; both are happy on a quality 650W unit.)

How much faster is the RX 9070, really?

In GamersNexus’s launch review, the RX 9070 leads the RTX 5070 by roughly 11–15% at 1440p rasterization in the games that favor it — a couple land dead even — and the pattern holds at 4K. As always, the range is the useful part:

Starfield (1440p): RX 9070 ~96 FPS vs RTX 5070 ~83 FPS — about a 15% lead.
Cyberpunk 2077 (1440p): the 9070 leads by roughly 11%.
Black Myth: Wukong (raster): the two land within error of each other — effectively tied.
At 4K: the 9070 is generally ahead again — around +17% in Starfield and +14–15% in Cyberpunk and Dragon’s Dogma 2 — though Final Fantasy XIV flips it, with the RTX 5070 about 24% faster (a long-standing AMD weak spot).

So the honest read is “the 9070 is a bit faster than the 5070 in most rasterized games — call it low-double-digits — with the odd title going the other way.” That’s a real, repeatable edge, and it comes on top of 4GB more VRAM. For where both land against the rest of the stack, see the 2026 GPU hierarchy, or line them up head-to-head in our GPU comparison tool.

Ray tracing: where the RTX 5070 hits back

This is the one category that reliably flips the verdict. RDNA 4 narrowed AMD’s historic ray tracing deficit, and in lighter RT workloads the 9070 is genuinely competitive — GamersNexus even measured it ahead of the 5070 in Dragon’s Dogma 2 with RT enabled. But in heavy, path-traced titles the NVIDIA card still pulls away hard: in Black Myth: Wukong at 4K with ray tracing, the RTX 5070 was roughly 57% faster than the 9070.

The takeaway isn’t “AMD is bad at RT” — it’s that the gap scales with how aggressive the ray tracing is. Turn on a few reflections and shadows, and the cards are close. Turn on full path tracing in a showcase title, and the 5070 (plus DLSS 4) is in a different league. If ray tracing is central to what you play, that alone can justify the NVIDIA card.

The quiet wins: efficiency and VRAM

Two advantages don’t show up on an FPS bar but matter over the life of the card.

Efficiency. The 9070’s 220W board power isn’t just 30W lower on paper — it’s more frames per watt in practice. GamersNexus called the card “incredibly efficient,” recording it near RTX 5090-class efficiency in one 4K ray-traced test (about 0.21 FPS/W versus the RTX 5070’s 0.17 — roughly 24% better there). In a real build that means a little less heat, a little less fan noise, and more headroom on a modest PSU.

VRAM longevity. The 5070’s 12GB is fine for 1440p today, but it’s the tighter of the two, and VRAM pressure only grows. Several 2026 titles already brush past 12GB at 4K with ultra textures or ray tracing — and when a GPU runs out of memory it doesn’t slow down gracefully, it stutters and quietly drops texture quality. The 9070’s 16GB is the safer place to put your money if you game at 4K or plan to keep the card 4+ years. It’s the same reason the VRAM question dominates the tier below, in our RTX 5060 Ti vs RX 9060 XT showdown.

DLSS 4 vs FSR 4 — the software split

Upscaling is where NVIDIA keeps its clearest lead. The RTX 5070 supports DLSS 4, including multi-frame generation, which is widely implemented and generally the quality benchmark. The RX 9070 uses FSR 4, which on RDNA 4 closed much of the visual gap to DLSS but appears in fewer games. If a title you care about supports one but not the other well, let that break the tie. And if you use your GPU for more than games — AI inference, video encoding, apps built on CUDA/NVENC — that ecosystem is NVIDIA-only and a real reason to pick the 5070 despite its raster deficit.

The price picture in 2026

Here’s the part the launch-day guides get wrong today. Both cards carry a $549 MSRP, and at MSRP the math is easy: same price, AMD faster in raster, buy AMD. But in a live Amazon check on 2026-07-20, that clean gap had mostly closed:

RTX 5070 partner cards ran roughly $580–670 (a PNY model listed at $629.99 with a $50 checkout coupon; several others $630–670).
RX 9070 cards ran roughly $610–686 (XFX Swift ~$610–640, PowerColor Reaper ~$686).

In other words, they’re selling within a model’s margin of each other right now — sometimes the cheapest 5070 is actually a touch less than the cheapest 9070. That’s a meaningful shift from the MSRP narrative: the RX 9070’s old “faster and cheaper” pitch is now mostly just “faster in raster, similar price.” It’s still the value pick for rasterized gaming — you get more frames, more VRAM, and lower power for about the same outlay — but the decision is now feature-driven, so weigh ray tracing, DLSS, and CUDA honestly before you buy. Prices here are a dated snapshot in a volatile market; check the live retailer price before committing.

Don’t overlook the tier neighbors

Two cards sit one step away and are worth a glance before you commit. Above this pair, the RX 9070 XT and RTX 5070 Ti trade blows for a few hundred more — we cover that exact fight in RTX 5070 Ti vs RX 9070 XT, and the AMD-internal step up from this card in RX 9070 vs RX 9070 XT. And if you’re cross-shopping NVIDIA’s own stack, the RTX 5070 vs RTX 5070 Ti breakdown shows why the Ti’s real-world premium is bigger than its MSRP suggests. If your budget is firmly at this tier, though, the 5070-versus-9070 decision below is the one that matters.

So which should you buy?

Pure 1440p gaming, best value: the RX 9070. More frames, 16GB of VRAM, lower power, similar price (~$620, XFX Swift RX 9070, Amazon).
Ray tracing, DLSS 4, or creator/AI work: the RTX 5070. You give up a little raster to gain the RT crown, DLSS 4 frame gen, and CUDA/NVENC (~$630, PNY RTX 5070, Amazon).
Not sure yet: run both through the GPU comparison tool and check the live price gap — at these near-equal prices, the tiebreaker is which feature set you’ll actually use.

The one mistake to avoid is buying on the year-old “9070 is faster for less” headline without checking today’s prices. In 2026 the two cards cost about the same, so pick the one whose strengths match how you play — raw 1440p frames and VRAM (AMD), or ray tracing and DLSS (NVIDIA).

Sources

NVIDIA — GeForce RTX 5070 family specifications (RTX 5070 CUDA cores, 12GB GDDR7, 250W board power) — verified live 2026-07-20
GamersNexus — AMD RX 9070 GPU Review & Benchmarks vs. 9070 XT, RTX 5070 (RX 9070 architecture, 1440p/4K rasterization deltas, ray tracing, and per-watt efficiency) — verified live 2026-07-20
RX 9070 specifications (RDNA 4, 56 compute units, 16GB GDDR6 on a 256-bit bus, 220W board power) and the $549 launch MSRP it shares with the RTX 5070 reflect both companies’ March 2025 launches, cross-checked across multiple independent launch-day reports and the TechPowerUp GPU database.
Prices: live Amazon snapshot, 2026-07-20 (retailer links above)

RX 9070 vs RX 9070 XT: Which Radeon to Buy in 2026?

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · Updated 2026-07-20 · ~10 min read · St. Louis County, MO

TL;DR · The verdict in 2026

Performance: the XT is ~7–12% faster at 1440p (~9% at 4K, up to ~16% in ray tracing) — real, but smaller than the name implies.
The catch is power: the XT draws 84W more (304W vs 220W board power) for that ~10%, so it runs hotter and wants a bigger PSU.
VRAM is a tie: both are 16GB GDDR6 on a 256-bit bus, same Navi 48 die — neither ages better on memory.
Buy the RX 9070 XT for max out-of-box frames or 4K (~$690, PowerColor Reaper 9070 XT, Amazon).
Buy the RX 9070 for efficiency, a quieter build, and value (~$620, XFX Swift RX 9070, Amazon).

Specs are from AMD; benchmark deltas are from independent testing (GamersNexus, PCWorld), cited inline. Prices are a live Amazon snapshot dated 2026-07-20 and move week to week in the current GDDR shortage — check the retailer link before buying.

The 9070 family’s confusing middle

AMD’s RDNA 4 line put three cards within a hair of each other — the RX 9070, the RX 9070 XT, and the 12GB 9070 GRE — and the two that matter most for a mainstream build are the first two. They look nearly identical on a spec sheet, share the same Navi 48 GPU and the same 16GB of memory, and sell within about a hundred dollars of each other. So the real question isn’t “which is better” — the XT is, plainly — it’s “is the XT’s extra performance worth its extra power and price for you?” That’s a narrower, more answerable question, and the numbers settle it. (If you’re cross-shopping the plain 9070 against NVIDIA instead, we cover that in RTX 5070 vs RX 9070.)

The specs, honestly

Both cards are cut from the same silicon. The XT simply has more of it switched on, running faster:

Spec	RX 9070	RX 9070 XT	Edge
Architecture	RDNA 4 (Navi 48)	RDNA 4 (Navi 48)	same die
Compute units	56	64	XT (+14%)
Stream processors	3,584	4,096	XT (+512)
VRAM	16GB GDDR6	16GB GDDR6	tie
Memory bus	256-bit	256-bit	tie
Board power	220W	304W	9070 (–84W)
MSRP	$549	$599	+$50

The XT enables about 14% more compute units and stream processors and clocks higher out of the box — on paper a decent jump. But paper isn’t frames, and the same die plus identical memory means the two behave far more alike than, say, a 5070 versus a 5070 Ti (which differ in VRAM too). Line them up against the rest of the stack in the 2026 GPU hierarchy or the GPU comparison tool.

How much faster is the XT, really?

Independent testing lands in a tight, consistent band. GamersNexus measured the 9070 XT “roughly 9–12% better than the 9070 in most of the games we tested” at 1440p — for example Dragon’s Dogma 2 at 116 FPS (XT) vs 106 FPS (9070), a 9.3% gap. PCWorld put the average lower still, at about 7% across their suite. So the honest figure is roughly 7–12% at 1440p — GamersNexus saw a similar ~9% at 4K (Dragon’s Dogma 2 at 70 vs 64 FPS) and a wider gap in ray tracing, up to about 16%, where the XT’s extra compute stretches its legs.

That’s a real, repeatable edge — but it’s the kind of gap you measure with a frame counter, not one you feel across a session. Both cards clear high-refresh 1440p comfortably and handle entry 4K. Drivers have also matured since these March-2025 launch reviews, nudging RDNA 4 up a little across the board, but the relative order hasn’t changed.

The catch: 84 watts for ~10%

Here’s the trade the spec sheet makes plain. That ~7–12% comes at a 304W board power rating versus 220W — an 84W jump — and independent testing measured real draw around 310W (XT) versus 224W (9070). GamersNexus called the plain 9070 “incredibly efficient” and described it as sitting in “the so-called sweet spot of power and performance,” delivering more frames per watt than its bigger sibling.

In a real build that gap matters more than a single-digit FPS delta. The 9070 runs cooler and quieter, fits comfortably on a quality 550–650W supply, and puts less heat into a small case; the XT wants stronger cooling, better airflow, and headroom on the PSU. Size either one with our PSU wattage calculator before you buy — the XT’s draw is a real line item, not a rounding error.

The tiebreaker that isn’t: VRAM

One of the biggest levers in most GPU comparisons is simply off the table here. Both cards carry 16GB of GDDR6 on a 256-bit bus — identical memory, identical 640 GB/s of bandwidth. Neither will run out of VRAM before the other, and neither ages better on that axis. That’s the opposite of a cross-brand fight like RTX 5070 vs RX 9070, where the 12GB-vs-16GB question does real work. Between these two Radeons, forget VRAM and decide on performance, power, and price alone.

Undervolt and the value case

RDNA 4 responds unusually well to tuning, and it cuts both ways in this matchup. The RX 9070 XT is a popular undervolt target — dropping voltage trims its considerable power draw and temperatures with little performance loss (and, because the card is power-limited, often adds a few frames), taking the sting out of that 304W rating. But the same flexibility means the base RX 9070 overclocks well, so a tuned 9070 can close much of the gap to a stock XT. That’s why the community verdict — echoed in the buying advice that shows up right in Google’s own summary for this matchup — is that a cheaper 9070 you push a little is often the smarter money than paying up for the XT and leaving it stock.

The price picture in 2026

At MSRP this was an easy call: $549 vs $599 is a $50 (9%) step for ~7–12% more performance, so the XT was a textbook upsell. But like the rest of the market in 2026, neither sells at MSRP. In a live Amazon check on 2026-07-20:

RX 9070 cards ran roughly $610–686 (an XFX Swift near $620, a PowerColor Reaper toward $686).
RX 9070 XT cards ran roughly $690–750 for mainstream models (premium designs past $800).

So the street premium has widened to about $80–100, not $50 — enough that the 9070’s efficiency and lower price tilt the value math back toward it. The XT is still the right buy if you want the most frames out of the box or you game at 4K; the 9070 is the pick if the premium is real to you or efficiency matters. A GDDR shortage keeps these prices volatile, so treat the snapshot as a method and check the live price before you commit.

So which should you buy?

Want the most performance out of the box, or game at 4K: the RX 9070 XT. You pay ~$80–100 more and 84W more for ~~7–12% higher frames, more in ray tracing (~~$690, PowerColor Reaper RX 9070 XT, Amazon).
Value efficiency, a quiet build, or a smaller PSU: the RX 9070. Same 16GB, ~~90% of the frames, 84W less heat, and it undervolts-or-overclocks to taste (~~$620, XFX Swift RX 9070, Amazon).
Cross-shopping NVIDIA: see how the tier lines up in RTX 5070 Ti vs RX 9070 XT and RTX 5070 vs RX 9070.

The one thing not to do is buy the XT purely because it has the “XT” on the box. It’s the faster card, but the gap is single-digits-to-low-double-digits, the power cost is real, and at 2026 street prices the plain 9070 is often the smarter buy. Decide on the price gap in front of you, not the badge.

Sources

GamersNexus — Incredibly Efficient: AMD RX 9070 GPU Review & Benchmarks vs. 9070 XT, RTX 5070 (1440p/4K raster deltas, ray tracing, power draw and efficiency) — verified live 2026-07-20
PCWorld — AMD Radeon RX 9070 and 9070 XT review (the ~7% XT-over-9070 average) — verified live 2026-07-20
Core specs — 56 vs 64 compute units, 16GB GDDR6 on a 256-bit bus, and the ~224W vs ~310W measured power draw — are stated in the cited GamersNexus review; the $549 vs $599 MSRP is confirmed by the cited PCWorld review. Stream-processor counts (3,584 vs 4,096) follow from the compute-unit counts, and the 220W vs 304W board-power ratings are AMD’s published figures, corroborated by those measured draws.
Prices: live Amazon snapshot, 2026-07-20 (retailer links above)

RX 9070 XT Undervolt Guide: More FPS, Less Heat (2026)

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · ~9 min read · St. Louis County, MO

The one tweak that makes a 9070 XT both cooler and faster

The RX 9070 XT is a 304W card — the power-hungry end of AMD’s RDNA 4 stack, and the exact reason the plain RX 9070 wins on efficiency. But that high power draw hides an opportunity: the XT frequently runs into its power limit, throttling clocks to stay under the ceiling. Lower the voltage, and the card holds higher clocks at the same power — so undervolting a 9070 XT doesn’t just cut heat and noise, it can make the card faster.

That’s not the usual “undervolt for efficiency” story. XDA measured a 9070 XT (a Sapphire NITRO+) at a -100mV offset jumping from 58 to 64 FPS in Cyberpunk 2077 — roughly a 10% gain — while running cooler and quieter. Community testers on the r/radeon 9070 XT mega-thread report the same pattern across brands. Here’s how to do it safely, and the settings people converge on.

Why undervolting raises clocks on this card

Modern GPUs run a voltage-frequency relationship: every clock speed needs a minimum voltage to stay stable. AMD ships the 9070 XT with voltage headroom baked in for the worst-case chip, so most cards are running higher voltage than they actually need at a given clock.

When you lower that voltage, one of two things happens depending on what’s limiting the card:

If the card is power-limited (the common case on the 9070 XT under load), less voltage means less power at the same clock — so the card has budget left over, and its boost algorithm spends it climbing to higher clocks. That’s where the free FPS comes from.
If the card is thermally or voltage-limited, the undervolt mainly buys you lower temperatures and quieter fans at the same performance.

Either way you win. The only real cost is the time it takes to test for stability, because every chip is slightly different (the “silicon lottery”).

What you need

Just one tool: AMD Software: Adrenalin Edition, which is already installed with your Radeon driver. As How-To Geek notes, “AMD Software: Adrenalin Edition is all you need to undervolt your AMD GPU” — no MSI Afterburner or third-party utility required (that’s the NVIDIA workflow, which we cover in the RTX 5080 undervolt guide; for the method across both brands, start with how to undervolt your GPU). It helps to also have a monitoring overlay (Adrenalin’s own Performance Metrics, Alt+R → Performance, shows clock, voltage, power, and temperature under load).

Step 1: Record your baseline

Before changing anything, load the card and note where it sits. Run a demanding game or a benchmark for 10–15 minutes and record, from Adrenalin’s metrics overlay or HWiNFO64:

GPU clock (sustained under load)
GPU power (board power, watts)
Temperatures — watch the hotspot / junction temperature, not just the edge temperature
Average FPS in a repeatable test scene

These are the numbers you’re trying to beat: same or higher FPS, at lower power and temperature.

Step 2: Open the tuning controls

Press Alt+R to open AMD Software: Adrenalin Edition
Go to the Performance tab, then Tuning
Set the Tuning Control dropdown to Custom
Enable GPU Tuning

You’ll now see the manual controls. On RDNA 4 you adjust a voltage offset (in millivolts) applied across the curve, plus a separate power limit slider and optional VRAM controls.

Step 3: Apply a conservative undervolt first

Do not start at -100mV. Silicon varies, and a too-aggressive first pass just wastes time chasing crashes. Instead:

Set the voltage offset to -40mV as a safe first step
Enable Power Tuning and set the power limit to -10% (this keeps performance closest to stock while lowering temps)
Click Apply Changes
Test (Step 5). If it’s stable, come back and step the offset down by 10–15mV at a time — toward -60, -80, then -100mV — retesting at each step

The community-converged sweet spot for a stable, balanced daily profile is a -80mV to -100mV offset with the power limit between -10% and -30%. Use -10% power limit for maximum performance, or -30% if your priority is the lowest power and heat. Some owners, for instance, prefer a smaller ~-40mV offset paired with a deeper -30% power limit and a raised maximum frequency — the exact mix depends on your goal and your chip.

Step 4: (Optional) recover a little with VRAM and clocks

Two optional extras, once your undervolt is stable:

VRAM Fast Timing — enable it under Memory Tuning; it tightens memory timings for a small, free bump. Many 9070 XT cards also take a modest memory frequency increase.
Maximum frequency offset — because you’ve freed up power budget, you can nudge the max frequency up to push clocks higher still. Add this after the undervolt is proven stable, and test again.

Keep changes small and test between each one. The goal is a profile that’s rock-solid for months, not a benchmark screenshot that crashes on the third game.

Step 5: Test for stability (the part people skip)

An undervolt that looks great for five minutes and crashes an hour into a game is worse than no undervolt. Test properly:

Run a demanding, real game — Cyberpunk 2077, a Unreal Engine 5 title, or your actual most-played game — for 15–20 minutes, ideally longer
Or loop a benchmark like 3DMark Steel Nomad / Time Spy
Watch for driver timeouts, black screens, or crashes to desktop — these mean the voltage is too low for the clock. Raise the offset by 5–10mV and retest.

One important caution from How-To Geek: some games — Unreal Engine 5 titles especially — are more sensitive and will crash on an undervolt that every other game tolerates. Adrenalin supports per-game tuning profiles, so if one title is fussy you can give it a gentler undervolt without softening your global profile.

What to expect

Results vary by chip and by game — these are community-reported ranges, not first-party measurements — but the pattern is consistent:

Power draw: community testers report roughly 40–100W lower, depending on how far you push the offset and power limit.
Temperatures: commonly 5–10°C lower on the hotspot, which also lets fans spin slower and quieter; testers frequently note reduced coil whine too.
Performance: anywhere from unchanged to ~10% higher FPS in power-limited titles (XDA’s Cyberpunk 58→64 is a good example); synthetic and CPU-bound scenes show smaller gains.

For a card you might otherwise cross-shop against the plain 9070 purely on efficiency, an undervolt narrows that gap considerably — worth remembering when you read our RX 9070 vs RX 9070 XT breakdown or weigh the XT against NVIDIA in RTX 5070 Ti vs RX 9070 XT.

Make it stick, and size your build

Once you’ve settled on a profile, Adrenalin applies it automatically at startup — no manual step each boot. Two build notes:

The undervolt lowers sustained draw, but size your PSU for the card’s real peak, not its undervolted average — our PSU wattage calculator does the math for a 9070 XT build.
If you care about the running cost, the power & cost calculator turns “60W saved” into an actual dollar figure per year.

The 9070 XT rewards ten minutes in Adrenalin more than almost any card this generation: cooler, quieter, and often faster, for free. Just test it properly before you trust it. The same trade exists on the processor side — if you’re running a Ryzen X3D chip, the 9800X3D undervolt guide walks through Curve Optimizer the same way.

Sources

XDA — I undervolted my GPU and got the upgrade I actually wanted (RX 9070 XT at -100mV, Cyberpunk 2077 58→64 FPS, lower temps/noise) — verified live 2026-07-20
How-To Geek — 8 Tips for Undervolting Your Gaming GPU (the AMD Adrenalin method; per-game profiles; UE5 crash caution) — verified live 2026-07-20
r/radeon — 9070 XT Undervolt/Overclock/Brand mega-thread (community-converged -80 to -100mV offset / -10% to -30% power-limit settings across brands)
RX 9070 XT specs (RDNA 4, 64 compute units, 16GB GDDR6, 256-bit, 304W board power) as verified in our RX 9070 vs RX 9070 XT comparison (GamersNexus)

Seagate IronWolf vs IronWolf Pro vs Exos (2026)

LK Wood IV — Mon, 20 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-20 · Updated 2026-07-20 · ~13 min read · St. Louis County, MO

TL;DR · Which Seagate drive for your NAS

Light-duty home NAS (2–4 bays): standard IronWolf — 180TB/year is plenty, and it's one of the cheapest new NAS-rated CMR drives. Tops out at 16TB.
Heavy 24-7 use or a big array: IronWolf Pro — 550TB/year workload, 5-year warranty, 3 years of bundled Rescue Data Recovery, up to 32TB.
Best price-per-TB (the homelab move): a recertified enterprise Exos. A recertified 16TB Exos was $30.62/TB in our July 20 pull vs ~$43/TB for a new NAS drive — but check it's SATA, not SAS.
The reality: IronWolf Pro and Exos are the same base drive with different firmware, grade, and warranty. For most home NAS builds, buy on price and warranty channel, not the badge.
The one rule: whatever tier you pick, run redundancy and keep a real 3-2-1 backup. RAID is not a backup.

Spec numbers are from Seagate's current data sheets. Prices are a live Amazon snapshot dated 2026-07-20 and move week to week — check the retailer link before buying.

The short version

Seagate sells three families that all end up in NAS boxes, and the naming makes them sound like a simple good–better–best ladder. They mostly aren’t. Here is the 30-second version:

IronWolf is the home/SOHO NAS drive: CMR, 1-to-8-bay rated, capacities from 2TB to 16TB, a 180TB/year workload rating, and a 3-year warranty.
IronWolf Pro is the heavier-duty NAS drive: same CMR, but a 550TB/year workload, 2.5-million-hour MTBF on the big models, a 5-year warranty, and capacities all the way to 32TB.
Exos is the enterprise/datacenter drive that homelabbers buy for its price per terabyte — the same 7200-RPM CMR mechanics, rated to a 0.35% annual failure rate, but sold through channels where recertified units routinely undercut new NAS drives on $/TB.

The twist that the ranking forum threads and the AI Overview never quite pin down: IronWolf Pro and Exos are, on the spec sheet, essentially the same drive — and the current IronWolf Pro has quietly closed the reliability-rating gap that used to separate them. So the real decision is less “which is the better drive” and more “which capacity, at which price, through which warranty channel.” Let’s ground all of that in the actual data sheets and a dated price pull. For the box these drives go into, see our budget NAS build guide; for the cross-brand best-picks by use case (WD Red Plus, Toshiba N300, and where Seagate fits), see the best NAS hard drives guide. This page is specifically about choosing within the Seagate lineup.

The spec table — current Seagate data sheets

Every number below is from Seagate’s current data sheets (linked in Sources), not a reseller listing. Where Seagate lists a value only for certain capacities, that’s noted.

Spec	IronWolf	IronWolf Pro	Exos (X-series)
Role	Home / SOHO NAS	24-7 NAS, large arrays	Enterprise / datacenter
Capacities	2–16TB	2–32TB	~10–30TB
Recording	CMR	CMR	CMR
Spindle	7200 RPM (8TB+)	7200 RPM	7200 RPM
Workload rating	180 TB/yr	550 TB/yr	24-7 rated*
MTBF	1.0M hr	2.5M hr (12TB+)	2.5M hr
Rated AFR	not published	not published	0.35%
Warranty	3 yr	5 yr	5 yr
Rescue Data Recovery	3 yr included	3 yr included	none
RV sensors	yes (all current)	yes (all)	yes
Bays	1–8	unlimited	enterprise (unlimited)
Interface	SATA	SATA	SATA or SAS

*The Exos marketing data sheets cited here list a 0.35% annual failure rate and 24-7 operation (8,760 power-on hours/year) rather than a TB/year workload number; Exos is built for the same continuous-duty class as IronWolf Pro.

Three things worth pulling out of that table:

The standard IronWolf now reaches 16TB. Seagate’s September 2025 IronWolf data sheet lists 2, 4, 6, 8, 10, 12, and 16TB; the old 14TB and 18TB SKUs were dropped. If you see an 18TB “IronWolf” (non-Pro), it’s old stock, not the current line.
RV sensors are on every current model, even standard IronWolf. Older IronWolf data sheets marked the smallest capacities as lacking rotational-vibration sensors; the current sheet lists RV sensors as “yes” across the whole line. That’s a real improvement for anyone putting standard IronWolf into a multi-bay enclosure.
The workload gap is the clearest real difference. 180 vs 550 TB/year is the number that actually separates IronWolf from Pro/Exos. For a home NAS storing media and backups you will rarely approach even 180TB/year of writes; for a busy multi-user or surveillance array, the 550 rating (and the 5-year warranty that comes with it) is the honest reason to step up.

Are Exos and IronWolf Pro the same drive?

This is the single most-argued question in every Seagate NAS thread, and the forum answer — “they’re the same drive, Exos just has different firmware” — turns out to be mostly right, but nobody grounds it. Here’s the spec-sheet evidence.

Line up Seagate’s own data sheets for a matched 16TB Exos X16 and IronWolf Pro and the mechanical fingerprint is identical, down to the gram:

Weight: 670 g on both.
Dimensions: 26.11 × 101.85 × 146.99 mm on both.
Spindle / cache / latency: 7200 RPM, 256MB cache, 4.16 ms average latency — identical.
Read-error rate: 1 per 10^15 bits on both.
Vibration tolerance: 12.5 rad/s² on both.

That is not what two different drives look like. It’s what one base platform looks like, wearing two firmware loads and two labels. Seagate has never published a component-level bill of materials, so this is strong circumstantial evidence rather than a teardown — but a weight-to-the-gram, dimension-for-dimension, latency-for-latency match across two separate spec sheets is about as close as public documentation gets.

What actually differs is the grade and the software:

Validation / reliability rating. Exos is rated to a 0.35% AFR and 2.5M-hour MTBF; the older IronWolf Pro that shared the 16TB platform was rated 0.73% AFR / 1.2M-hour MTBF on its 2019 data sheet (linked in Sources). That’s an enterprise validation and binning difference, not a different mechanism.
Firmware and features. Exos adds enterprise-oriented features (PowerBalance, SuperParity, security/SED options, and a SAS variant). IronWolf Pro adds the consumer-friendly stack: IronWolf Health Management and 3 years of bundled Rescue Data Recovery.

Here’s the part the old threads miss: on the current data sheets, IronWolf Pro has caught up. Today’s IronWolf Pro (the “NT” models) is rated to the same 550 TB/year workload and the same 2.5-million-hour MTBF as Exos on the helium 12TB-and-up capacities. The historical “Exos is the more durable tier” gap is now largely a legacy-spec artifact — the current Pro is specced right alongside Exos, and simply adds Rescue and a retail warranty channel on top.

So the accurate way to say it: IronWolf Pro and Exos are the same base drive at similar grade; you’re really choosing a feature set and a purchase channel. Retail IronWolf Pro gets you Rescue, easy RMA, and a shelf full of new units. Exos gets you the enterprise feature options and — crucially — the recertified market, which is where the price story lives.

Two myths, spec-checked

Because Exos is an “enterprise” drive, two beliefs follow it around. Both fail against Seagate’s own numbers.

“Exos is louder.” At a matched generation, the Exos X-series and IronWolf Pro publish the same typical acoustics: about 2.8 bels idle and 3.2 bels seek. There is a genuine wrinkle worth flagging that no competitor mentions: Seagate reports acoustics inconsistently across its own lines — the consumer IronWolf sheet uses sound-pressure dBA, while the Pro and Exos sheets use sound-power bels — so a clean cross-line “X dBA vs Y dBA” comparison doesn’t actually exist in the source data. The honest read: all three are 7200-RPM drives, all are audible under seek, none is engineered to be quiet, and Exos’s louder reputation is mostly spin-up chatter plus the fact that people run bare enterprise drives in undampened cases. The homelab community consensus (r/DataHoarder, r/homelab) lands in the same place: recertified Exos “aren’t louder than IronWolf once spun up,” they’re just loud at boot — so isolate the NAS in a closet or a dampened case rather than choosing your drive by noise.

“Exos draws more power.” Also not supported at a matched size. At 16TB, idle power is identical (5.0W on both) the Exos X16 and IronWolf Pro. Their operating figures aren’t directly comparable because Seagate publishes “max operating” for Exos and “average operating” for IronWolf Pro — different definitions, not a real gap. The newer, denser Exos X24 does idle higher (about 6.3W) than the 2019-era 16TB drives, but that’s a generational change (bigger cache, denser platters), not an Exos-versus-IronWolf penalty.

Which one for your NAS

Sort by what your NAS actually is:

A quiet 2–4 bay home NAS for media and backups. Standard IronWolf is enough. You will not touch the 180TB/year ceiling, RV sensors are now standard across the line, and it’s among the cheapest new NAS-rated CMR drives. If a recertified Exos of the same size is meaningfully cheaper per TB and you run redundancy, take the Exos instead (see pricing below).
A busy always-on array, many users, virtualization, or 6+ bays. Step to IronWolf Pro (or Exos). The 550TB/year workload and 5-year warranty are the point, and the bundled 3-year Rescue is a genuine safety net. Between Pro and Exos here, it’s price and warranty channel: new-with-Rescue (Pro) versus cheapest-per-TB (recertified Exos).
Chasing maximum capacity per dollar and you run ZFS/parity + backups. Recertified enterprise Exos, full stop — it’s the homelab budget path and has been for years. Just confirm SATA vs SAS and treat the warranty as the seller’s, not Seagate’s.
Surveillance/NVR duty specifically. Neither of these three — that’s what SkyHawk is for — but if you’re mixing, an IronWolf/Pro handles light NVR loads fine.

Whatever you pick, size the array after redundancy, not before: a four-bay box of 16TB drives is not 64TB usable once you account for a parity or mirror drive. Run the real numbers in the NAS & RAID storage calculator before you buy.

The $/TB reality — live Amazon snapshot, 2026-07-20

Here’s where the decision usually gets made. Below is a live US Amazon price pull captured 2026-07-20; $/TB uses the drive’s marketed (decimal) capacity. Prices move week to week in the 2026 drive market — treat this as a method, not a promise, and check the retailer link before buying.

Drive (model)	Condition	Capacity	Price	$/TB	Link
Seagate IronWolf (ST12000VN0008)	New	12TB	$429.99	$35.83	Amazon
Seagate IronWolf (ST16000VN001)	New	16TB	$689.97	$43.12	Amazon
Seagate IronWolf Pro (ST12000NT001)	New	12TB	$459.99	$38.33	Amazon
Seagate IronWolf Pro (ST16000NT001)	New	16TB	$698.00	$43.63	Amazon
Seagate IronWolf Pro (ST20000NT001)	New	20TB	$669.99	$33.50	Amazon
Seagate Exos X18 (ST16000NM000J)	New	16TB	$685.00	$42.81	Amazon
Seagate Exos X16 (ST16000NM001G)	Recertified	16TB	$489.99	$30.62	Amazon
Seagate IronWolf Pro (ST16000NE000)	Recertified	16TB	$599.00	$37.44	Amazon
Seagate Exos (ST26000NM000C)	Recertified	26TB	$669.00	$25.73	Amazon

Three takeaways jump out:

Recertified enterprise Exos is the $/TB champion by a wide margin. A recertified 16TB Exos at $30.62/TB undercut a new IronWolf Pro 16TB ($43.63/TB) by about 30%, and a recertified 26TB Exos fell to $25.73/TB — the cheapest per terabyte in the table. This is exactly the play the homelab community leans on during the 2026 drive crunch.
Within the new drives, IronWolf and IronWolf Pro are nearly the same price at a given capacity (16TB: $689.97 vs $698.00). So if you’re buying new at 16TB, the Pro’s extra workload rating, 5-year warranty, and Rescue cost only a few dollars — an easy upgrade.
Bigger isn’t reliably cheaper per TB, but sometimes it is. The new IronWolf Pro 20TB ($33.50/TB) was cheaper per terabyte than the 16TB ($43.63/TB) in this pull — a shortage-pricing quirk. Always run the per-TB number for your target capacity on the day you buy.

The SATA-vs-SAS trap. One thing to check before you click on any cheap Exos: some Exos listings are SAS, not SATA. In this very pull, the “Exos X24 16TB” that surfaced first (ST16000NM002H) was a SAS drive — it will not plug into a standard SATA NAS bay without a SAS HBA. Recertified enterprise pulls are especially likely to be SAS. Read the interface in the title/specs; if it doesn’t say SATA, assume SAS.

For the recertified route specifically — the warranty reality, review-count trust signal, and which sellers homelabbers actually use — see the recertified section of the best NAS hard drives guide and the drive-buying breakdown in the budget NAS build guide, which also covers the burn-in test you should run the day a recertified drive arrives.

What the real-world failure data actually says

Spec-sheet MTBF is a modeled number, not a promise. The closest thing to real-world data is Backblaze’s Drive Stats, which tracks hundreds of thousands of drives in production. Their full-year 2025 failure-rate analysis covered 344,196 drives (the set left after excluding boot drives and thinly-populated models) and put the fleet-wide annualized failure rate at 1.36% (down from 1.55% in 2024), with a lifetime AFR of 1.30%.

Two honest caveats that most articles quoting Backblaze skip:

Backblaze runs Exos-class enterprise drives, not consumer IronWolf. Every Seagate model in their 2025 tables is an enterprise “ST…NM…” drive. Consumer IronWolf (ST…VN…) and IronWolf Pro (ST…NE…/NT…) don’t appear in the fleet at all — Backblaze buys enterprise. So “Backblaze shows Seagate is reliable” is really a statement about Exos-class drives, which is genuinely reassuring for the recertified-Exos route, but tells you little about the consumer IronWolf line.
The specific per-model annual percentages live in an image table that isn’t machine-readable, so we won’t quote a number we can’t verify — a good rule for any stat. What is verifiable from Backblaze’s own notes: several Exos-class Seagate models had a standout-low year (the 16TB ST16000NM002J logged a single failure across 2025 and zero in Q4), while an aging 10TB Exos-class model was flagged as a high-failure outlier at end-of-life. The pattern — modern high-capacity enterprise drives failing rarely, worn-out old ones failing more — is exactly what you’d expect, and it’s the argument for buying recertified drives that still have plenty of rated life and pairing them with redundancy.

Bottom line on reliability: Seagate rates Exos to 0.35% AFR, the current IronWolf Pro to the same 2.5M-hour MTBF, and Backblaze’s real fleet of enterprise Seagate drives runs well under a couple of percent a year. None of that replaces a backup. Every tier here fails eventually; the drive tier matters far less than running RAID/RAIDZ so one failure doesn’t lose data and keeping a real 3-2-1 backup.

What competing guides skip (our angle)

Most “IronWolf vs Pro vs Exos” pages are stale forum threads or generic “Pro has a longer warranty” listicles. Three things they consistently miss, all covered above:

The spec-grounded ‘same drive’ answer. We lined up the matched 16TB data sheets to show the identical mechanical fingerprint — and flagged that current IronWolf Pro has closed the old workload/MTBF gap with Exos, which most comparisons still describe using 2019-era numbers.
The unit-inconsistency behind the ‘Exos is louder’ myth. Seagate publishes acoustics in different units across its lines, so the common noise comparison is comparing sound pressure to sound power. We said so.
The SATA-vs-SAS trap and a dated, real $/TB table with the recertified-Exos value laid out honestly — including that recertified enterprise Exos beat new NAS drives by ~30% per terabyte in our July 20 pull.

Best NAS hard drives 2026 — the cross-brand picks (WD Red Plus, IronWolf Pro, Toshiba N300) by use case, with the CMR-vs-SMR history and the recertified warranty details.
Best budget NAS builds 2026 — the chassis and platform these drives go into, plus the new-vs-recertified-vs-shuck decision.
Best NAS for Plex and Jellyfin 2026 — when the media workload, not the disk, drives the build.
TrueNAS vs Unraid vs Proxmox storage backend — the OS/filesystem layer that turns these disks into a pool.
NAS & RAID storage calculator — real usable capacity after redundancy, before you buy.

Sources

Manufacturer specifications (Seagate data sheets, verified live):

Seagate IronWolf data sheet (DS1904.23-2509US, Sept 2025): https://www.seagate.com/content/dam/seagate/en/content-fragments/products/datasheets/ironwolf-12tb/ironwolf-16tb-DS1904-23-2509US-en_US.pdf
Seagate IronWolf Pro data sheet (DS2129.7-2510US, Oct 2025): https://www.seagate.com/content/dam/seagate/en/content-fragments/products/datasheets/ironwolf-pro-32-tb/ironwolf-pro-32-tb-DS2129-7-2510US-en_US.pdf
Seagate IronWolf Pro product page: https://www.seagate.com/products/nas-drives/ironwolf-pro-hard-drive/
Seagate IronWolf Pro 16TB data sheet (legacy DS1914.10-1905US — the 2019 sheet behind the matched-16TB comparison): https://www.seagate.com/www-content/datasheets/pdfs/ironwolf-pro-16tb-DS1914-10-1905US-en_US.pdf
Seagate Exos X24 data sheet (DS2080-2307US): https://www.seagate.com/content/dam/seagate/en/content-fragments/products/datasheets/exos-x24/exos-x24-DS2080-2307US-en_US.pdf
Seagate Exos X16 data sheet (DS2011.1-1904US): https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf

Real-world reliability:

Backblaze Drive Stats for 2025: https://www.backblaze.com/blog/backblaze-drive-stats-for-2025/

Community discussion (homelab consensus on overkill, noise, and recertified value) was reviewed on r/homelab and r/DataHoarder and is cited inline as community opinion, not spec fact. Prices are a live Amazon snapshot dated 2026-07-20.

Best NAS for Plex & Jellyfin 2026: Which Ones Actually Hardware-Transcode

LK Wood IV — Sun, 19 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-19 · Updated 2026-07-19 · ~13 min read · St. Louis County, MO

TL;DR · What to actually buy in 2026

Best budget (2-bay, real transcode): UGREEN NASync DXP2800 — Intel N100, 8GB DDR5, Quick Sync works (~$390 diskless, observed 2026-07-19).
Best mainstream (4-bay): UGREEN NASync DXP4800 Plus — Intel Pentium Gold 8505, 8GB DDR5, 10GbE, Quick Sync (~$657).
Best for heavy 4K / many streams: TerraMaster F4-424 Pro — Intel Core i3-N305 8-core, 32GB, 4K HW transcode (~$688).
Best value: an Intel N100/N150 mini-PC + a NAS/DAS for storage — same Quick Sync engine, more transcode-per-dollar than most appliances.
The one rule: buy Intel Quick Sync. In 2026 that means not a current Synology (see below), and never an ARM/Realtek box.

CPU and transcode facts are from manufacturer and Plex/Jellyfin documentation, cited inline. Prices are a live Amazon snapshot dated 2026-07-19 and move week to week — the 2026 memory/storage shortage has hardware prices unusually volatile, so check the retailer link before buying.

Start here: do you even need to transcode?

Almost every “best NAS for Plex” guide skips the one question that should drive the whole purchase, so let’s put it first. A media server does the least work when it Direct Plays — hands the file to your player untouched. The server’s effort climbs from there: Direct Play → Remux (swap the container) → Direct Stream (convert audio only) → Transcode (rebuild the video), per Jellyfin’s transcoding docs. Transcoding is the expensive one, and it’s a fallback — it only happens when the client can’t play the file as-is.

There are really only three triggers: an unsupported codec or container on the client, a bandwidth/bitrate cap (usually remote streaming), or subtitle burn-in — and note that image-based subtitles like PGS or VOBSUB force a full video transcode even when the video itself was fine. A modern player — Apple TV 4K, an NVIDIA Shield, a Fire TV Stick 4K Max — direct-plays most H.264 and HEVC natively, which means a lot of home setups rarely transcode at all. If that’s you, an ARM NAS is a perfectly good storage box.

So the honest buying rule is: match your player to your files first, then buy exactly as much transcode headroom as the cases you can’t avoid demand. The one case that will force your hand is 4K HDR tone-mapping (playing 4K HDR content on an SDR target). Jellyfin’s own hardware-selection guide is blunt about it: tone-mapping 4K60 Dolby Vision to H.264 SDR “requires a Ryzen 9 5950X for faster than real-time” in software, so “a GPU is ALWAYS recommended.” That single workload is why hardware transcoding — and therefore the CPU inside your NAS — is the spec that matters.

The one rule: Intel Quick Sync (and what it rules out in 2026)

Hardware transcoding on a NAS almost always means Intel Quick Sync, the video engine baked into Intel’s integrated graphics. It lets a low-power chip transcode several streams while the CPU stays near idle. The practical compatibility line is simple:

Intel with an iGPU (Quick Sync) → yes. N100, N150, N95, N5105, J4125, J6412, Pentium Gold 8505, Core i3-N305, Core i5-1235U, and friends.
ARM / Realtek → no. No Quick Sync at all; these choke after roughly one software-transcoded stream. Fine for storage and Direct Play only.
AMD without an iGPU → no. Some embedded Ryzen parts (see Synology below) have no integrated graphics, so every transcode falls back to the CPU.
AMD with a Radeon iGPU → it depends. Parts like the Ryzen Embedded R2514 (Radeon Vega 8) can hardware-transcode through VAAPI, which Jellyfin handles well but Plex supports inconsistently.

Which brings us to the trap that makes this guide necessary.

The 2026 Synology transcode trap

For a decade the default answer to “best NAS for Plex” was “a Synology.” In 2026 that answer is usually wrong, and almost no competing guide explains why — because it broke in two different ways at once.

Prong one — the AMD models have no iGPU. Synology’s 2025 Plus units moved to AMD Ryzen embedded chips with no integrated graphics. The DS925+ and DS1525+ use the Ryzen V1500B; the DS923+, DS723+ and DS725+ use the R1600. Reviewers put it plainly — the V1500B “does not have an embedded GPU… you will be unable to use the Plex hardware acceleration functionality.” Every transcode on these boxes is software-only, which a 40+ Mbps 10-bit 4K HEVC stream will not survive gracefully.

Prong two — the Intel models had their driver removed. The 2025 DS225+ and DS425+ still ship the same Intel Celeron J4125 with Quick Sync silicon as older units — but Synology stripped the i915 iGPU kernel driver out of DSM on the 25-series, disabling hardware H.264/HEVC transcoding at the software level. Synology’s own statement, quoted in a widely-shared Channels community PSA, is that “starting with products released in 2025 and beyond, even if the CPU supports hardware transcoding, we will no longer provide the driver required to enable it,” citing HEVC licensing. Threads on SynoForum document the same removal. The lone 2025 exception is the BeeStation Plus, for which Synology paid the codec licenses. A community SSH workaround exists to re-inject the driver on a DS225+/DS425+, but it’s unsupported and reapplies itself after every reboot or DSM update — a curiosity, not a reason to buy.

The result is a genuine consumer trap: the DS225+ is even marketed on Amazon with the title “Intel CPU for Hardware Transcoding,” which is true about the silicon and false about what DSM will actually let Plex or Jellyfin do. So: do not buy a current Synology as an out-of-box media transcoder. The DS225+ (~~$360), DS425+ (~~$545) and DS925+ (~$695) are fine NAS units for many jobs — hardware media transcoding is not one of them in 2026. (Older 24-series Intel boxes like the DS224+/DS423+ still transcode via Quick Sync, but the diskless SKUs are effectively gone from Amazon’s first-party listings and are being phased out — don’t build a 2026 purchase around finding one new.)

Picks by use case

Every pick below is a current, Intel Quick Sync box that actually hardware-transcodes on its shipping firmware. We haven’t lab-benchmarked these ourselves; CPU specs come from manufacturer pages and Amazon listings, and stream-count guidance is class-based, not a promise — real capacity depends on bitrate, HDR tone-mapping, and subtitle burn-in.

Best budget, 2-bay: UGREEN NASync DXP2800

An Intel N100 (quad-core Alder Lake-N with UHD Quick Sync), 8GB DDR5, 2.5GbE, and two M.2 slots — the cheapest appliance on this list with working hardware transcoding. The N100’s Quick Sync engine comfortably handles multiple 1080p transcodes and a 4K→1080p stream or two, all while the CPU barely registers. It ran ~$390 diskless (to ~$440) in our 2026-07-19 Amazon snapshot, with over a thousand reviews (Amazon). This is the box to buy instead of the Synology DS225+.

Best mainstream, 4-bay: UGREEN NASync DXP4800 Plus

The center of gravity for most media libraries. An Intel Pentium Gold 8505 (five-core Alder Lake with UHD Quick Sync), 8GB DDR5, a 128GB system SSD, and — unusually at this price — 10GbE plus 2.5GbE. Four bays give you room to grow, and the Quick Sync engine handles several simultaneous transcodes including 4K. It was ~$657 diskless (a variant to ~$730) with 640+ reviews on 2026-07-19 (Amazon). One caution: UGREEN sells a near-identically-named DXP4800 GT at almost the same price that uses an AMD Ryzen R2514 (Radeon Vega 8) — it transcodes through VAAPI on Jellyfin but is inconsistent on Plex, so if Plex is your app, pin the “Plus” SKU, not the GT.

Best for heavy 4K / many streams: TerraMaster F4-424 Pro

When you’re tone-mapping 4K HDR or feeding several transcoding clients at once, step up to an Intel Core i3-N305 — eight cores with a 32-EU UHD iGPU — paired with 32GB of DDR5 and dual 2.5GbE. TerraMaster’s spec page lists hardware transcoding for H.264/H.265/MPEG-4/VC-1 up to 4K, and the listing’s own comparison marks 4K hardware transcoding as supported. It was ~$688 diskless (to ~$860 on a variant) on 2026-07-19 (Amazon). If you want the same Quick Sync capability for less and can live with a plainer chassis, the TerraMaster F4-425 (Intel quad-core, 4K H.265 hardware decode, ~$365) is a strong value 4-bay.

Best value: a mini-PC + separate storage

The pick that most guides won’t tell you about, because it isn’t a NAS. An Intel N100 or N150 mini-PC has the exact same Quick Sync engine as the appliances above, costs $130-300, draws around 10W, and — because it isn’t simultaneously running a disk array — out-transcodes most sub-$700 NAS boxes. The homelab-standard setup is to keep bulk media on a cheaper NAS or DAS and run Plex or Jellyfin on the mini-PC over the network. It’s more moving parts and a little more setup, but it decouples transcode compute from your disks and is the most transcode-per-dollar you can buy. Our best mini-PCs for a homelab guide covers the boxes; pair one with the drives from our best NAS hard drives guide.

Plex vs Jellyfin: the transcode cost gap got wider in 2026

Pick the same Intel Quick Sync box and both apps transcode the same way — they ride the identical QSV/NVENC/VAAPI paths, so the ability is equivalent (we go deeper in Jellyfin vs Plex, and on the open-source side in Jellyfin vs Emby). What differs is the bill.

Plex gates hardware transcoding behind a paid Plex Pass, and that price moved sharply this year: as of July 1, 2026 the lifetime Plex Pass jumped to $749.99 from $249.99, with monthly ($6.99) and annual ($69.99) unchanged and a new 5-year plan at $249.99 — confirmed by Plex’s own pricing announcement and widely reported. Jellyfin does the same hardware transcoding for free, with no premium tier, per its hardware-acceleration docs. If you’re buying a Quick Sync NAS specifically to transcode, Jellyfin turns “free hardware acceleration” into a real line item against Plex’s now-$749.99 lifetime — worth weighing before you commit to an ecosystem.

The transcode compatibility table

The verdict every competitor’s spec-list leaves out — does the box actually hardware-transcode on the OS it ships with today?

Model	CPU	Quick Sync?	HW transcode OOTB?	~Price (2026-07-19)
UGREEN DXP2800	Intel N100	Yes	Yes	~$390
UGREEN DXP4800 Plus	Intel Pentium Gold 8505	Yes	Yes	~$657
TerraMaster F4-424 Pro	Intel Core i3-N305	Yes	Yes	~$688
UGREEN DXP4800 GT	AMD Ryzen R2514 (Vega 8)	No (VAAPI)	Jellyfin yes / Plex spotty	~$660
Synology DS225+ / DS425+	Intel Celeron J4125	Silicon yes, driver removed	No (DSM 25-series)	~$360 / ~$545
Synology DS925+	AMD Ryzen V1500B (no iGPU)	No	No	~$695
ARM/Realtek (e.g. Synology DS223)	ARM (no iGPU)	No	No (Direct Play only)	—

The bottom line

Buying a NAS for Plex or Jellyfin in 2026 is not the Synology default it used to be. Work it in this order: decide whether you even transcode (match your player to your files first), then — if you do — buy Intel Quick Sync, which today means a UGREEN or TerraMaster Intel box, an older Intel Synology while stock lasts, or, for the best transcode-per-dollar, an N100/N150 mini-PC paired with cheaper storage. Then pair it with the right disks from our NAS hard-drives guide, and if you’re still choosing apps, weigh Jellyfin’s free hardware transcoding against Plex’s now-$749.99 lifetime in Jellyfin vs Plex. Prices here are a dated 2026-07-19 snapshot in an unusually volatile year — treat them as a method, not a promise, and check the live retailer price before you buy.

Clock Watchdog Timeout? Revert the Overclock First (2026)

LK Wood IV — Mon, 13 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-13 · ~8 min read · St. Louis County, MO

CLOCK_WATCHDOG_TIMEOUT (stop code 0x00000101) has a precise meaning that most guides gloss over: a CPU core stopped responding — it missed an expected clock interrupt, and the system halted rather than wait on a hung core. That points somewhere very specific, and it isn’t “update your drivers” or “run sfc /scannow.” Nine times out of ten it’s CPU instability from tuning — an overclock, an undervolt, or a memory profile the chip can’t quite hold. The fix is to take the tuning back off, in order.

Why the generic advice doesn’t work here

Search this error and you’ll get the same rote list every blue screen gets: update Windows, update drivers, run SFC, scan for malware. For 0x101 that advice almost never lands, because a core hanging is a hardware-stability event, not a corrupted-file event. Software didn’t make a CPU core stop responding; running it outside its stable envelope did.

So the diagnosis flips: instead of adding fixes, you remove variables until the core is running at settings it’s guaranteed to hold.

Strip the tuning back to a stable floor

0x101 is a core that stopped responding. Turn off the four things that push a core past stable, top to bottom. Stable at the floor? Add them back one at a time to find the culprit.

OFF · 1

Manual CPU overclock

All-core OC set in BIOS → clear to Auto/default. The most direct cause.

OFF · 2

PBO + Curve Optimizer / undervolt

Set PBO and Curve Optimizer to zero/off. A too-negative curve crashes at idle, not just load.

OFF · 3

EXPO / XMP memory profile

Set memory to JEDEC. An unstable profile destabilizes the memory controller and hangs a core.

FLOOR

Stock CPU + JEDEC RAM + updated BIOS

Rock-solid here? Re-add one tuning at a time. Still crashing? Now suspect the CPU or PSU.

The counterintuitive one is #2: an AM5 undervolt/Curve Optimizer that’s too aggressive fails hardest at low load, so it can pass a stress test and still crash you at the desktop. techfuelhq.com

Step 1: Clear every CPU overclock

If you (or a “one-click OC” in the motherboard software) set a manual all-core overclock, that’s the first suspect. In BIOS, set the CPU ratio/frequency and voltage back to Auto or default. If you used a vendor tool like ASUS AI Overclocking, Ryzen Master, or Intel XTU, reset its profile to stock too. Reboot and use the PC. A manual overclock that was “stable” in a benchmark but not across every real workload is a textbook 0x101.

Step 2: Turn off PBO and Curve Optimizer (the undervolt trap)

On modern AMD (Ryzen 7000/9000) especially, the crash usually isn’t a classic overclock — it’s an undervolt via Curve Optimizer or an aggressive PBO profile. In BIOS, set PBO to Disabled/Auto and Curve Optimizer to 0 on all cores.

Here’s the part that fools people: a too-negative Curve Optimizer crashes at idle or light load, not under a stress test. The chip boosts to its highest clocks at low load, and that’s exactly where an under-volted core runs out of voltage and stops responding. So a machine that survives an hour of Cinebench can still throw CLOCK_WATCHDOG_TIMEOUT sitting on the desktop or browsing. If reverting the curve to zero stops the crashes, dial it back in less aggressively (for example, from −30 to −15) and re-test — including plenty of idle time, not just a benchmark. Our safe CPU temperature guide covers how to watch clocks and temps while you validate a curve.

Step 3: Disable EXPO / XMP (memory can hang a core too)

An EXPO (AMD) or XMP (Intel) profile the memory controller can’t quite hold destabilizes the whole CPU-memory subsystem, and it often shows up as a core hang rather than a memory error. Set memory to default JEDEC speed in BIOS and test. If the crashes stop, the profile was the problem — not the CPU. You can then try a milder profile, or add a touch of SoC/memory voltage. If you’re unsure what your kit is rated for versus what it’s running, the DDR5 buying guide walks through the EXPO/XMP-versus-JEDEC distinction and the AM5 6000-sweet-spot.

A brand-new build that has never been stable and throws 0x101 is very often an EXPO profile the board never truly validated.

Step 4: Update the BIOS

Once you’re at a stock floor, update your motherboard BIOS to the latest stable release. CPU stability on current platforms depends heavily on AGESA/microcode revisions, and a known stability bug — the kind that caused a wave of crashes on early AM5 or a new CPU generation — is often fixed in a BIOS update. Update, re-apply a clean load of stock defaults afterward, and only then reintroduce EXPO and any tuning.

Step 5: If a fully stock system still crashes

Only now does 0x101 become a hardware-replacement question:

Power: a marginal or failing PSU, or an under-seated CPU (EPS) power cable, can starve a core under load and hang it. Reseat the 8-pin EPS cable; if crashes are load-related, test with a known-good, adequately-rated PSU. Work our PC keeps restarting guide for the full power checklist and the isolation build.
Cooling: confirm the CPU isn’t thermal-throttling to instability under load with HWiNFO — see safe CPU temperatures.
The CPU itself: genuinely failing CPUs are rare, but a chip that crashes completely stock, at JEDEC memory, with an updated BIOS, healthy power, and good temps, is the remaining suspect — especially if it followed a period of heavy overclocking or a known-degradation batch.

The fix order, in one list

Clear manual CPU overclocks → Auto/default.
PBO + Curve Optimizer to 0/off — the undervolt that crashes at idle is the sneaky one.
EXPO/XMP off → JEDEC to rule out unstable memory.
Update the BIOS for AGESA/microcode stability fixes, then re-add tuning one at a time.
Stock and still crashing? Now check power (PSU, EPS cable), cooling, then the CPU.

Because 0x101 is a core that stopped responding, the entire fix is about getting that core back inside a stable envelope — which is why reverting tuning comes first and parts come last. If this blue screen is showing up alongside other stop codes or random reboots, the whole-system flow in PC keeps restarting and computer keeps freezing maps each code to its fix.

Sources

Stop code identity: Microsoft’s Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT reference — an expected clock interrupt on a processor was not received within the allocated interval (a core stopped responding). The tuning-first ordering reflects that this is a CPU-stability bug check, corroborated across Reddit r/overclocking and r/AMD, Tom’s Hardware and Level1Techs threads that repeatedly trace 0x101 to an unstable overclock, Curve Optimizer, or EXPO profile.
The AM5 Curve-Optimizer idle-instability behaviour (low-load boost exposing an under-volt) is well-documented community knowledge, self-verifiable by reverting the curve and observing the crash pattern. BIOS/AGESA microcode as a stability lever is standard platform behaviour. Temperature validation via HWiNFO; power checks per our first-party PC-keeps-restarting guide.

Steps are for Windows 10 and 11 in 2026; BIOS menu names vary by board. Found an error? Email hello@techfuelhq.com with the article URL.

DPC Watchdog Violation? The Storage-First Fix (2026)

LK Wood IV — Mon, 13 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-13 · ~9 min read · St. Louis County, MO

Some links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate we earn from qualifying purchases. Commissions never change what gets recommended — see our disclosure.

DPC_WATCHDOG_VIOLATION (stop code 0x00000133) reads like a hardware death sentence and almost never is one. The name is the whole diagnosis: a driver ran a Deferred Procedure Call for too long, and Windows’ watchdog timer killed the system to protect it. That means the fix is a driver — and the guides that send you straight to sfc /scannow are starting in the wrong place. Below is the order that actually clears it, front-loaded with the storage fix that resolves most cases.

What the stop code is actually telling you

A DPC is a low-priority task a driver defers to run a moment later — normal Windows plumbing. The DPC Watchdog is a timer that watches for one running too long: roughly 100 microseconds for a single DPC, or a longer cumulative budget across a run. When a driver blows past that, the watchdog fires 0x133 rather than let a stalled driver hang the whole machine.

So the question is never “which part is broken” — it’s “which driver stalled?” And the answer, statistically, is a storage driver. That is why the fix order below leads with storage, not with the generic scan-everything advice.

Which driver stalled the CPU? Work it top-down

0x133 is a driver holding the CPU too long. These are the culprits in rough order of how often they cause it — fix from the top, and stop when the crashes stop.

#1

Storage driver / SSD firmware

Wrong SATA AHCI driver, or outdated SSD/NVMe firmware. Steps 1–2.

#2

Network / Bluetooth driver

Crashes when Wi-Fi connects or a headset pairs? That driver. Step 3.

#3

A specific USB device driver

Only when a dock, printer, or external drive is plugged in. Step 3.

#4

Failing SSD or bad RAM (rare)

Only after the driver path is exhausted. Check drive health, then memory. Steps 5–6.

Don’t know which? The minidump names the exact .sys file — Step 4 reads it in two minutes. techfuelhq.com

Step 1: Change the SATA AHCI controller driver (fixes the most cases)

This one fix clears the largest share of DPC Watchdog Violations, and it costs nothing. Windows’ own Standard SATA AHCI Controller driver is more stable for this error than some vendor storage drivers (Intel’s iaStorAC, in particular).

Press Windows Key + X → Device Manager.
Expand IDE ATA/ATAPI controllers (on some systems, Storage controllers).
Right-click your SATA AHCI Controller → Update driver.
Choose Browse my computer for drivers → Let me pick from a list of available drivers.
Select Standard SATA AHCI Controller → Next, then reboot.

If “Standard SATA AHCI Controller” isn’t offered, your drive is on a vendor NVMe/RAID driver — leave it and move to Step 2, then the minidump in Step 4.

Step 2: Update your SSD / NVMe firmware

Outdated SSD firmware is the other half of the storage cause: an old firmware revision mishandles a TRIM, garbage-collection, or low-power transition and stalls its driver long enough to trip the watchdog. Update it from the manufacturer’s own tool — Windows Update won’t do this:

Samsung → Samsung Magician
WD / SanDisk → WD Dashboard
Crucial → Crucial Storage Executive
Kingston → Kingston SSD Manager

If your drive is a lesser-known brand with no utility, check whether it even is the boot drive causing the crashes — and if it’s an older drive throwing other symptoms too (slow boots, disappearing from Explorer), treat it as a storage-health problem and work our SSD not showing up guide, which covers the health checks that catch a failing drive.

Step 3: If it’s tied to one action, that names the driver

A DPC Watchdog Violation that fires on a specific trigger is the easiest kind to fix, because the trigger points straight at the guilty driver:

Crashes when Wi-Fi connects or Bluetooth pairs → the network or Bluetooth driver. Update it from the laptop or adapter maker’s site (Intel, Realtek, Qualcomm), not just Windows Update — the vendor’s build is usually newer.
Crashes when you plug in a dock, printer, or external drive → that device’s driver. Unplug the device to confirm the crashes stop, then update its driver from the maker.
Crashes at random with nothing obviously connected → move to the minidump in Step 4; guessing wastes days.

Step 4: Read the minidump — name the exact driver

You don’t have to guess which driver stalled. Every blue screen writes a small dump to C:\Windows\Minidump, and a free reader turns it into a filename. (Not every stop code makes you dig for it — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED usually prints the failing driver’s name right on the screen.)

Install WhoCrashed (free) or BlueScreenView (free, portable).
Point it at C:\Windows\Minidump.
Read the driver it names — the .sys file that was executing when the watchdog fired.

A result like netwtw10.sys (Intel Wi-Fi), rt640x64.sys (Realtek LAN), or a vendor storage .sys tells you exactly which driver to update or roll back. This is the difference between a targeted fix and a week of updating everything. If the dump names a graphics driver (nvlddmkm.sys, amdkmdag.sys), clean-reinstall it with the process in our GPU driver crash fix guide.

Step 5: Repair system files (only now)

If the driver path is genuinely exhausted, corrupt system files are the next check. Open Terminal (Admin) and run, in order:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Reboot after. These repair Windows’ own files — useful when a botched update damaged a system driver, but they will not fix a third-party driver that’s simply out of date, which is why they come after the driver work, not before it.

Step 6: Test the hardware (last, not first)

Only when every driver angle is exhausted does 0x133 become a hardware question:

Drive health: run CrystalDiskInfo. A boot SSD reading Caution (reallocated sectors, high error counts) can time out its own driver — back up now and plan a replacement.
Memory: unstable RAM can corrupt a driver mid-execution. Run Windows Memory Diagnostic (mdsched.exe) or MemTest86 overnight, and if you’re running an EXPO/XMP profile, set memory to default JEDEC speed to rule out an unstable overclock. Our DDR5 buying guide covers the EXPO/JEDEC distinction if you’re unsure what your kit is set to.

Hardware is genuinely the cause in a minority of DPC Watchdog Violations — which is exactly why it’s Step 6 and not Step 1.

The fix order, in one list

Swap to Standard SATA AHCI Controller (Device Manager) — clears the most cases.
Update SSD/NVMe firmware with the maker’s tool.
Tied to Wi-Fi / a USB device? Update that specific driver from the vendor.
Read the minidump (WhoCrashed / BlueScreenView) to name the exact .sys.
sfc /scannow + DISM for corrupt system files.
Test hardware last — CrystalDiskInfo for the SSD, MemTest86 for RAM, JEDEC to rule out EXPO/XMP.

Work it top-down and most DPC Watchdog Violations fall at Step 1 or 2. If yours survives to Step 6 and a drive- or memory-test comes back bad, that’s your answer — but you’ll have ruled out the far more likely driver causes first, instead of replacing parts on a hunch.

If the crashes are one symptom of a system that’s also rebooting or freezing on other stop codes, step back to the whole-system diagnosis in PC keeps restarting or computer keeps freezing — the stop-code decoder there maps each blue screen to the right fix.

Sources

Stop code identity and the watchdog mechanism: Microsoft’s Bug Check 0x133 DPC_WATCHDOG_VIOLATION reference — a single DPC exceeding its time allotment, or a run of DPCs exceeding the watchdog period.
The Standard SATA AHCI Controller swap and SSD-firmware fixes are the widely-corroborated first-line remedies across Microsoft Q&A, Tom’s Hardware and Level1Techs forum threads, and vendor guidance; all are non-destructive and self-verifiable on any Windows 10/11 PC.
Minidump reading uses the free WhoCrashed (Resplendence) and BlueScreenView (NirSoft) utilities against C:\Windows\Minidump. Drive health via CrystalDiskInfo SMART data; memory via Windows Memory Diagnostic (mdsched.exe) and MemTest86.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

Kernel Security Check Failure? Test RAM First (2026)

LK Wood IV — Mon, 13 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-13 · ~9 min read · St. Louis County, MO

KERNEL_SECURITY_CHECK_FAILURE (stop code 0x00000139) sounds like a virus or a hacked machine. It isn’t. The “security check” is Windows verifying the integrity of its own data structures — and this blue screen means one of them was found corrupted in memory. That single fact reorders the whole fix: the first thing you test is not drivers or malware, but the two things that corrupt memory — your RAM and any memory overclock.

Most guides bury RAM testing at step five behind sfc /scannow. For 0x139 specifically, that’s backwards.

What 0x139 is actually checking

Windows constantly validates critical kernel data — list pointers, buffers, control structures. A security check compares one of these against what it should be. When they don’t match, the kernel assumes something corrupted it and halts with 0x139 rather than keep running on bad data. It’s a smoke detector for memory corruption.

Corruption has a short list of sources, and they’re not equally likely:

Unstable or failing RAM — a bad stick, or a good stick pushed past what it can hold.
An XMP/EXPO overclock the kit or memory controller can’t quite sustain — the RAM is fine, the speed isn’t.
A bad driver writing where it shouldn’t.
Corrupt system files after a bad update.
Failing storage feeding corrupt data back to the kernel.

The order you test them in is the difference between a one-evening fix and a week of flailing. The same ordering carries over to the sibling stop code PAGE_FAULT_IN_NONPAGED_AREA (0x50), which shares the top two suspects — bad memory first, then failing storage.

Two questions decide where you start

0x139 is memory corruption. Before you touch anything, answer these — they route you to the fast path instead of testing all five causes blind.

Q1 · Did you change hardware, RAM, or an overclock?

New sticks, more sticks, a fresh XMP/EXPO profile, a CPU/RAM overclock, or a brand-new build that has never been stable → start at RAM + memory speed (Steps 1–2). This is the most common path, especially on a new AM5 or Intel build.

Q2 · Did it start after a driver or Windows update?

Crashes began right after a GPU driver, a device driver, or a Windows update → start at drivers + system files (Steps 3–4). A named driver in the minidump makes this a one-driver fix.

Answered neither, or not sure? Test RAM anyway — it’s free, non-destructive, and the top cause of 0x139. techfuelhq.com

Step 1: Test your RAM

Bad memory is the number-one cause, so this is where almost everyone should start.

MemTest86 (free, from a USB stick) is the thorough test — run at least one full overnight pass. A single error anywhere means a stick or a memory setting is bad.
Windows Memory Diagnostic (Windows Key + R → mdsched.exe → Restart now) is the quick built-in check — less thorough, but a fast first pass.
Reseat and isolate: power down, reseat both sticks firmly, then if the errors persist, test one stick at a time in the same slot to find the bad module. A single failing stick is a common, cheap fix — replace it (ideally with a matched kit).

If MemTest86 is clean at default speed, your physical RAM is probably fine — which points straight at Step 2.

Step 2: Drop XMP / EXPO to JEDEC

This is the step people skip, and it fixes a huge share of 0x139 on modern builds. XMP (Intel) and EXPO (AMD) are memory overclock profiles — the advertised DDR5-6000 or DDR5-6400 speed is not the RAM’s guaranteed-stable default. If your specific kit or your CPU’s memory controller can’t quite hold that profile, it silently corrupts data and throws 0x139, while the sticks themselves are perfectly good.

In BIOS, disable XMP/EXPO (or set the profile to Auto/Default) so memory runs at its JEDEC base speed (typically DDR5-4800 or 5600).
Boot and use the PC. If the crashes stop, the overclock was the problem — not the RAM.
From there you can try a milder profile, nudge SoC/DRAM voltage, or simply run at JEDEC. If you’re unsure what speed your kit is rated for versus running at, our DDR5 buying guide explains the XMP/EXPO-versus-JEDEC distinction and the AM5 6000-sweet-spot in plain terms.

A brand-new build that has never been stable and throws 0x139 is very often this — an EXPO profile the board never truly validated.

Step 3: Find a bad driver with Driver Verifier

If memory is clean and the overclock is ruled out, a misbehaving driver corrupting kernel memory is next. First, read the easy clue: open C:\Windows\Minidump with BlueScreenView (free) — if it names a specific .sys, update or roll back that driver and you may be done. A graphics driver (nvlddmkm.sys, amdkmdag.sys) gets a clean reinstall via our GPU driver crash fix guide.

When the dump is vague, Driver Verifier forces the guilty driver to reveal itself — but it’s a power tool, so use it safely:

Create a System Restore point first.
Run verifier → Create custom settings → select the standard tests → Select driver names from a list → check only non-Microsoft drivers.
Reboot. If a bad driver exists, Verifier will blue-screen and name it in the next minidump.
Know the escape hatch: if it boot-loops, enter Safe Mode and run verifier /reset to turn it off.

If you’re not comfortable recovering from a boot loop, skip Verifier and lean on Steps 1–2 and 4 — they resolve most cases without it.

Step 4: Repair system files and check storage

Corrupt system files (common after a failed update) — open Terminal (Admin) and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and reboot.
Failing storage — a dying boot SSD can feed corrupt data back to the kernel. Run CrystalDiskInfo; a drive reading Caution should be backed up and replaced. If the drive is also vanishing from Explorer or slowing down, work our SSD not showing up guide.
Malware — because “security” is in the name people jump here first, but it’s an uncommon cause. A full Windows Security scan rules it out; don’t let it distract from the RAM and driver work.

The fix order, in one list

Test RAM — MemTest86 overnight, reseat, one stick at a time.
Drop XMP/EXPO to JEDEC — rules out an unstable memory overclock (fixes many new builds).
Drivers — read the minidump (BlueScreenView); use Driver Verifier for the stubborn ones, with a restore point and the Safe-Mode reset ready.
System files + storage — sfc / DISM, then CrystalDiskInfo; a quick malware scan to close it out.

The reason RAM leads and malware trails is the stop code itself: 0x139 is a memory-integrity failure, and you test the things that corrupt memory before the things that rarely do. If this blue screen is showing up alongside other stop codes or random reboots, step up to the whole-system flow in PC keeps restarting or computer keeps freezing, where the stop-code decoder maps each code to its fix.

Sources

Stop code identity: Microsoft’s Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE reference — the kernel detected the corruption of a critical data structure. The RAM-first ordering reflects that this is a memory-integrity bug check, corroborated across Microsoft Q&A, Tom’s Hardware, Level1Techs and MSI forum threads that repeatedly trace 0x139 to bad RAM or an unstable XMP/EXPO profile.
Memory testing: MemTest86 (PassMark) from bootable USB, and Windows Memory Diagnostic (mdsched.exe). XMP/EXPO-versus-JEDEC behaviour is standard DDR5 platform behaviour, self-verifiable in BIOS. Driver Verifier (verifier.exe) and its verifier /reset recovery are documented Microsoft tools. Minidump reading via BlueScreenView (NirSoft); drive health via CrystalDiskInfo SMART data.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

Page Fault in Nonpaged Area? Test RAM & Storage (2026)

LK Wood IV — Mon, 13 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-13 · ~8 min read · St. Louis County, MO

PAGE_FAULT_IN_NONPAGED_AREA (stop code 0x00000050) has an unusually literal meaning. The “nonpaged area” is memory Windows keeps permanently resident — data too critical to ever swap to disk. This blue screen means Windows went to read something there and the data wasn’t valid. So the whole diagnosis is one question: why was the memory missing? There are only three real answers, and testing them in the right order saves you days.

The address was there a moment ago. Where did it go?

Windows asked for data at a specific memory address and got garbage or nothing. Three things cause that, and they’re not equally likely:

Bad RAM lost it. A failing or unstable stick corrupts the resident data. Most common.
Failing storage can’t supply it. The nonpaged area is backed by the drive; a dying SSD or bad sectors can’t serve the data back. Common, especially on boot.
A driver pointed at the wrong address. A buggy driver references freed or invalid memory. Common when the blue screen names a .sys.

That ordering is the fix order. The two most likely causes are hardware, so you test memory and storage before you start reinstalling drivers.

"The memory wasn't there" — three reasons, in order

0x50 is one symptom with three sources. Test top to bottom; the first two are hardware and cover most cases. A named driver jumps you straight to #3.

1 · RAM lost it MOST COMMON

A bad or XMP-unstable stick corrupts resident memory. MemTest86, one stick at a time, JEDEC to rule out the overclock. (Step 1.)

2 · Storage can't supply it COMMON ON BOOT

A failing drive or bad sectors can’t serve the paged-out data back. CrystalDiskInfo + chkdsk /f /r. (Step 2.)

3 · A driver pointed wrong IF A .SYS IS NAMED

nvlddmkm.sys (NVIDIA), vgk.sys (Vanguard anti-cheat), or another named driver. Fix that one driver. (Step 3.)

The blue screen sometimes prints a .sys name in parentheses — if it does, start at #3. No name — start at #1. techfuelhq.com

Step 1: Test RAM

The nonpaged area lives in physical memory, so a bad stick is the first and most likely suspect.

MemTest86 from a USB stick, at least one full overnight pass. A single error means a stick or a memory setting is bad.
Windows Memory Diagnostic (Windows Key + R → mdsched.exe) is the quick built-in first pass.
Reseat and isolate: power down, reseat both sticks, then test one at a time to find the bad module.
Rule out the overclock: if you run XMP/EXPO, set memory to default JEDEC speed. An unstable profile corrupts memory exactly like a bad stick while the RAM itself is fine — the same trap covered in kernel security check failure, the other memory-corruption blue screen. Our DDR5 buying guide explains the XMP/EXPO-versus-JEDEC distinction.

Step 2: Check storage health

Because the nonpaged area is backed by the drive, a failing disk is the second suspect — and the leading one when 0x50 hits on boot or when loading large files.

CrystalDiskInfo reads the drive’s SMART health. Anything reading Caution (reallocated sectors, high error counts) is a warning — back up now.
chkdsk /f /r from an admin Terminal scans for and repairs bad sectors (it schedules on the next reboot for the system drive).
If the drive is also disappearing from Explorer, slowing down, or dropping out, treat it as a storage-health problem and work our SSD not showing up guide.

Step 3: Name the driver from the minidump

If the blue screen printed a .sys in parentheses, or RAM and storage both test clean, read the dump:

Install BlueScreenView (free, portable) and point it at C:\Windows\Minidump.
Read the driver it names.

Two names come up constantly for 0x50:

nvlddmkm.sys — the NVIDIA graphics driver. Do a clean reinstall with DDU (Display Driver Uninstaller) in Safe Mode, then a fresh driver.
vgk.sys — Riot Vanguard, the Valorant/League anti-cheat that runs at the kernel level. Update or reinstall the game’s anti-cheat; uninstall it to confirm it’s the cause.

Any other .sys names its device — search the filename, then update or roll back that one driver.

Step 4: System files and paging file (last)

Repair system files: sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then reboot — useful after a bad update damaged a system file.
Reset the paging file: rarely the cause, but a corrupt paging file can glitch the nonpaged area. Under System Properties → Advanced → Performance Settings → Advanced → Virtual memory, toggle “Automatically manage” off and on (or set a custom size, then back to system-managed) to rebuild it.

The fix order, in one list

RAM — MemTest86, one stick at a time, JEDEC to rule out XMP/EXPO.
Storage — CrystalDiskInfo (SMART) + chkdsk /f /r.
Driver — BlueScreenView names the .sys; DDU for nvlddmkm.sys, reinstall anti-cheat for vgk.sys.
System files / paging file — sfc + DISM, rebuild the paging file.

Because 0x50 is invalid-memory-referenced, the two hardware causes lead and the driver work follows a named clue — no reinstalling every driver on a hunch. If this blue screen appears alongside other stop codes or random reboots, the whole-system flow in PC keeps restarting maps each code to its fix.

Sources

Stop code identity: Microsoft’s Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA — invalid system memory was referenced; the address is wrong or points at freed memory. The RAM-then-storage-then-driver ordering reflects that this is a memory/hardware-integrity bug check, corroborated across Microsoft Q&A, Tom’s Hardware, and Reddit r/techsupport / r/pchelp threads.
Memory testing: MemTest86 (PassMark) and Windows Memory Diagnostic (mdsched.exe). Storage: CrystalDiskInfo SMART data and chkdsk /f /r. Minidump reading via BlueScreenView (NirSoft). Driver names nvlddmkm.sys (NVIDIA) and vgk.sys (Riot Vanguard) are standard, self-verifiable identifications; DDU is the standard clean-reinstall tool for GPU drivers.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

System Thread Exception Not Handled? Read the Driver (2026)

LK Wood IV — Mon, 13 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-13 · ~8 min read · St. Louis County, MO

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (stop code 0x0000007E) is one of the friendlier blue screens, because it usually tells you what broke. A system thread threw an error nothing caught — and that thread almost always belongs to a driver. Better still, Windows often prints the guilty driver’s filename right there in parentheses. Your job is to read that name and fix that one driver, not to reinstall everything and hope.

The one thing that makes this error easy: the parentheses

Most blue screens give you a cryptic code and nothing else. This one frequently shows something like:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (nvlddmkm.sys)

That .sys in parentheses is the driver that crashed. It turns a vague “something’s wrong” into a one-driver fix. If you see a name, you’re most of the way there. If you don’t see one (the screen flashes too fast, or it’s blank), the minidump gives you the same answer — covered in Step 3.

Read the name in the parentheses

The .sys file on the blue screen names the driver that crashed. Match it below, then fix that one driver in Safe Mode.

nvlddmkm.sys NVIDIA graphics driver. Clean-reinstall with DDU. Most common by far.

atikmdag.sys AMD graphics driver. Same fix — DDU, then a fresh driver.

netwtw*.sys / rt*.sys Wi-Fi / LAN driver (Intel, Realtek). Update from the adapter maker, not just Windows Update.

any other .sys Search the filename to find the device. Update or roll back that one driver.

no name shown Read the minidump with BlueScreenView. It names the same .sys. (Step 3.)

Every fix below happens in Safe Mode — a boot-looping 0x7E can’t be fixed from a desktop it never reaches. techfuelhq.com

Step 1: Get into Safe Mode

If the system boots normally between crashes, you can work from the desktop. If it’s boot-looping, you need Safe Mode first:

Force-power-off during boot three times (hold the power button as Windows starts to load) to trigger Automatic Repair.
Choose Advanced options → Startup Settings → Restart.
Press 5 for Safe Mode with Networking (so you can download a driver).

Safe Mode loads Windows with generic drivers, so the crashing driver is inactive and you can replace it.

Step 2: Fix the named driver

With the .sys name in hand:

Graphics driver (nvlddmkm.sys / atikmdag.sys): the clean fix is DDU (Display Driver Uninstaller) in Safe Mode, then install a fresh driver — the full process is in our GPU driver crash fix guide. If the crash started right after a driver update, install the previous stable version rather than the newest.
Network / Wi-Fi driver (netwtw*.sys, rt*.sys): update it from the laptop or adapter maker’s site (Intel, Realtek, Qualcomm), which is usually newer than Windows Update’s build.
Any other driver: in Device Manager, find the device, open the Driver tab, and either Roll Back Driver (if it broke after an update) or Update driver. Roll Back is the fastest fix when a recent update caused it.

Step 3: If no driver is named, read the minidump

When the blue screen doesn’t show a name, the crash dump has it:

Install BlueScreenView (free, portable) and point it at C:\Windows\Minidump.
It lists the .sys that was executing when the thread threw — the same driver you’d have read on the blue screen.

Then fix that driver per Step 2. This is why you almost never need to reinstall every driver for 0x7E — the system tells you which one, one way or another.

Step 4: System files, then hardware (last)

If the driver path is genuinely exhausted:

Repair system files: in an admin Terminal, run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and reboot — useful when a bad update damaged a system driver.
Test RAM: unstable memory can make a driver throw exceptions. Run MemTest86 overnight, and if you run XMP/EXPO, test at default JEDEC speed.
Check GPU temperature: an overheating graphics card can crash its own driver — confirm temps are in range under load before blaming the card itself.

The fix order, in one list

Read the .sys in parentheses (or from the minidump).
Boot Safe Mode (Automatic Repair → Startup Settings → Safe Mode with Networking).
Fix that one driver — DDU for graphics, vendor update for network, Roll Back for a post-update break.
System files / hardware last — sfc + DISM, then MemTest86 and GPU temps.

Because 0x7E is a driver throwing an uncaught exception — and it usually names the driver — this is one of the fastest blue screens to fix once you know to read the parentheses. If it shows up alongside other stop codes or random reboots, the whole-system flow in PC keeps restarting and computer keeps freezing maps each code to its fix, and the storage-driver sibling DPC watchdog violation covers the other common driver-timeout blue screen.

Sources

Stop code identity: Microsoft’s Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — a system thread generated an exception the error handler did not catch; the parameters identify the exception and the driver. The driver-first ordering and the parenthetical-.sys behaviour are standard and self-verifiable, corroborated across Microsoft Q&A, Tom’s Hardware and Level1Techs threads that repeatedly trace 0x7E to a graphics or device driver.
Tools: BlueScreenView (NirSoft) for C:\Windows\Minidump; DDU (Wagnardsoft) for clean GPU-driver reinstalls; Windows Safe Mode and Device Manager Roll Back Driver are built-in. Driver identifiers nvlddmkm.sys (NVIDIA) and atikmdag.sys (AMD) are standard, verifiable names.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

Computer Randomly Turns Off? Fix the Sudden Shutdowns (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-11 · Updated 2026-07-13 · ~9 min read · St. Louis County, MO

A computer that suddenly turns itself off — no warning, no blue screen, just an instant black cut like the plug was pulled — is scary, but the way it dies is the biggest clue you have. A total, instant power-off that stays off is almost never a software crash. It’s a hardware protection circuit doing its job: something got too hot, drew too much power, or shorted, and the system killed power to protect itself. That narrows the whole diagnosis to a short, ordered checklist.

The shape of the shutdown

Each fault leaves a different trace on the power line. Read the shape of yours — when the power drops and whether it comes back — and you have named the cause before you open the case.

Fine, then an instant cut under load. Runs at idle, dies minutes into a game or render, won’t restart until it cools — overheating (Step 2).

Drops the instant load spikes. Cuts out exactly when a game or benchmark hits hard, never at idle — a strained or failing power supply (Step 3).

Dies seconds after the button. Off before anything reaches the screen, usually on a machine you just built or moved — a dead short (Step 4).

Random cut with no load, even at idle. No trigger, “not overheating” — a degrading PSU, unstable memory, or bad wall power (Steps 3, 5, 6).

Drops, then comes right back on its own. That is a restart, not a shutdown — a different fault list (Step 7).

Traces are illustrative — the pattern, not the exact voltage, is the diagnostic. techfuelhq.com

Step 1: Read the signature (this decides everything)

Before you touch a screwdriver, answer three questions — they route you to the right cause immediately:

Does it stay off, or power back on by itself? If it instantly reboots on its own (comes back to the Windows logo without you pressing anything), that’s a restart, not a shutdown — the cause list is different and starts with reading the crash code. Work the PC keeps restarting guide instead.
Do you see a blue screen first, or is it an instant black cut? A blue-screen-then-reboot is software or a driver reporting a fault. An instant black with no BSOD is power being cut faster than Windows can draw a screen — a hardware protection trip. This guide is for the instant-black kind.
Do the fans and lights die too, or keep running? A true shutdown kills fans and lights together, completely. If the fans keep spinning and only the screen goes black, you didn’t lose power — that’s a freeze or a display fault (see the FAQ above).

The rest of this guide assumes the signature that actually means “shutdown”: instant, complete power-off, no blue screen, stays off until you press the button. Now read when it happens:

Only under load / while gaming → heat or power supply (Steps 2 and 3).
Seconds after you turn it on, especially a new build → a short circuit (Step 4).
Random, including at idle — “not overheating” → PSU degradation, unstable memory, or wall power (Steps 3, 5, 6).

One log confirms it was really a power cut. Open Event Viewer (eventvwr.msc) → Windows Logs → System and look for Event ID 41, source Kernel-Power — “the system has rebooted without cleanly shutting down first.” That entry is Windows telling you power was lost before it could shut down properly, which rules out a clean/scheduled shutdown or a sleep setting masquerading as a crash. It’s a symptom marker, not a cause — a Kernel-Power 41 shows up for a thermal trip, a PSU drop, and a hard freeze alike — but seeing it confirms you’re chasing the right kind of fault and should keep working the signature below.

Which shutdown do you have?

Same symptom, three different whens — and each points somewhere different. The widest block in your row is the cause to check first.

Only under load / while gaming

Overheating

Power supply

Seconds after power-on / new build

Short circuit

PSU

Random / at idle / “not overheating”

Power supply

RAM / XMP

Wall power

Overheating Power supply Short circuit RAM / XMP-EXPO Wall power

Block width = diagnostic priority for that pattern, not survey data. techfuelhq.com

Step 2: Overheating (thermal shutdown)

Heat causes shutdowns in two stages. At its rated limit — roughly 95-100°C on the CPU — the chip first throttles, dropping clocks to shed heat (that alone never turns the PC off; modern CPUs are designed to sit at that limit). The hard power cut comes from a separate emergency trip (Intel calls it THERMTRIP) that fires only when throttling can’t hold the temperature down — a dead pump, a detached cooler, a blocked fan. That’s why this is the #1 cause of shutdowns that happen under load, and why the machine often refuses to restart until it has cooled for a minute or two — which is itself the giveaway.

Check temperatures under load with HWiNFO or HWMonitor and watch the peak right before it dies. Our safe CPU temperature guide covers what’s normal (Ryzen to ~95°C, Zen 4 X3D ~89°C, Intel ~100°C) and when heat is genuinely the fault — a chip parking at its limit and cutting out means cooling can’t keep up.
Clear dust from fans, heatsinks, and vents with a can of compressed air, and confirm every fan actually spins. A failed CPU-cooler fan or a dead AIO pump causes fast, hard thermal shutdowns.
Reapply thermal paste if it’s a few years old — dried-out paste is the classic reason a PC that used to run cool now overheats and shuts off. A single tube of Arctic MX-4 covers several repastes.

If it’s the graphics card getting too hot in games, confirm the GPU is really overheating with the core-vs-hotspot check before you pull the cooler apart — a card that only looks hot needs a different fix. And if the CPU is the one hitting its limit, the why is my CPU overheating walkthrough sorts the cause by when it happens.

Step 3: Power supply (the shutdown-specific big one)

The PSU is the single most under-suspected cause of sudden shutdowns — and the most likely one when there’s no blue screen and the crash is load-related. When the supply can’t hold the load, one of its protection circuits fires — over-current (OCP) on a rail, over-power (OPP) across the whole unit, or over-temperature (OTP) if a fan has died — and it drops every rail instantly to protect itself and your parts. A classic tell: after the shutdown you sometimes have to flip the PSU’s rear switch off and back on (or unplug it for a few seconds) before it will power up again — the protection has latched and needs a full power-cycle to reset. This is also the top suspect for a second-hand or aged supply: capacitors and regulation drift with years and heat, so a unit that was fine at purchase can start tripping under a load it used to hold.

Reseat every power cable — the 24-pin, the CPU (EPS) connector, and every GPU power cable, including all pins on a 12VHPWR / 12V-2x6 connector, which is notorious for partial seating and can drop a card under load.
Rule out undersizing. A new, power-hungry GPU on an older PSU is a textbook shutdown cause. Run your parts through the PSU wattage calculator — if you’re near or over the unit’s rating under load, that’s your answer. Leave headroom; transient spikes from modern GPUs briefly exceed their average draw.
Swap-test if needed. If temperatures are confirmed healthy and it still cuts out under load, a known-good, adequately-rated PSU is the definitive test.

On an RTX 40- or 50-series card, suspect the 16-pin connector specifically. The 12VHPWR / 12V-2x6 plug runs a 575 W RTX 5090 at roughly 96% of its 600 W rating — about a 1.1x safety margin, versus 1.7x or more on the old 8-pin — so a plug that isn’t fully seated, or a pin whose contact has degraded, concentrates current and heats up fast. The early warning signs are exactly the ones on this page: crashes, instability, and hard shutdowns under load before anything visibly melts. These failures are still being reported in 2026 even on native, first-party cables — UK outlet Club386 lost its own RTX 5090 and a 1,000 W supply to one in June 2026. If you have one of these cards and it cuts out under load: push the plug in until it clicks with no gap or exposed metal, use the native 12V-2x6 cable that came with an ATX 3.1 PSU rather than an adapter, keep the cable straight for at least ~35 mm out of the connector, and stop using any plug or socket that looks discolored or smells hot.

Want to confirm the supply is genuinely failing rather than just undersized? Our deep dive covers the tell-tale symptoms, why the paperclip test can give a false all-clear, and how to read the 12V rail under load: PSU Failure Symptoms: Is It Really the Power Supply?

Step 4: A short circuit (instant-off, especially new builds)

If the PC dies seconds after you press power — sometimes before anything reaches the screen — and especially on a machine you just built or moved, suspect a dead short. A loose case screw rolling around, a misplaced brass standoff touching the back of the motherboard, or a component grounding against the case makes the PSU’s protection cut power instantly to prevent damage.

Check the standoffs: there should be exactly one under each motherboard mounting hole and none anywhere else. A stray standoff under the board is the single most common new-build short.
Hunt for loose metal — spare screws behind the motherboard tray, a cable’s bare connector touching a fan header, anything metal resting on the board.
Breadboard test: if you can’t find it, pull the motherboard out of the case and run it on its box (a “breadboard” test) with just CPU, cooler, one stick of RAM, and the PSU. If it stays on outside the case, the case was shorting it.

Step 5: RAM and unstable memory profiles

Faulty memory or an unstable EXPO/XMP profile can cause hard shutdowns and crashes, and this is a prime suspect for the “random, not overheating” pattern.

Test it: run the built-in Windows Memory Diagnostic (Windows Key + R → mdsched.exe), or MemTest86 from a USB stick for a thorough overnight pass.
Disable XMP/EXPO in BIOS and run the memory at its default JEDEC speed. If the shutdowns stop, the kit or memory controller wasn’t holding the rated speed — a very common cause of instability that looks like a hardware fault.
Reseat and isolate: reseat both sticks, then test one stick at a time to find a bad module.

Step 6: Wall power, surges, and settings

If temps and the PSU check out and it still cuts at random — including at idle — look outside the case:

Try a different wall outlet, plugged in directly. A failing outlet, an overloaded circuit, or a dying UPS/surge protector can drop power to the PC. One quick test: bypass power strips and battery backups and go straight to the wall.
Check for a brown-out pattern — if shutdowns coincide with a big appliance (AC, microwave, space heater) kicking on, your circuit is sagging under load. A proper UPS with AVR fixes this; size it with our homelab UPS math.
Rule out “shutdown” that’s really sleep. If the machine powers down on a schedule or after idle, check Windows power settings and disable Fast Startup — a misbehaving sleep/hibernate can look like a random shutoff. (This only applies if the fans genuinely stop; a hard load-triggered cut is never a sleep setting.)

Step 7: When it’s actually a restart or a freeze

Two quick off-ramps, because the fix is completely different:

It reboots itself or shows a blue screen → that’s a restart, not a shutdown. Turn off Windows’ auto-restart so you can read the stop code, and work the PC keeps restarting guide.
The screen goes black but fans and lights stay on → that’s a freeze or a display dropout, not a power-off. Different checklist — start with our computer keeps freezing guide.

The fix order, in one list

Read the signature — stays-off + no-BSOD + instant = hardware protection trip (this guide). Reboots or BSOD = a restart.
Read the pattern — under-load = heat/PSU; seconds after power-on = short; idle/“not overheating” = PSU/RAM/wall power.
Overheating — temps under load, dust, fans, thermal paste.
PSU — reseat cables, check wattage headroom, then swap-test if load-related.
Short circuit — standoffs, loose metal, breadboard test (new builds first).
RAM — mdsched/MemTest86, disable XMP/EXPO, one stick at a time.
Wall power — different outlet direct, check for brown-outs, rule out sleep/Fast Startup.

Work it in the order your pattern points to and you’ll almost always find a single physical cause — no parts-cannon required.

Sources

The diagnostic uses Microsoft’s built-in Windows tools — the Windows Memory Diagnostic (mdsched.exe), Event Viewer (eventvwr.msc), and standard power settings — plus manufacturer-standard thermal and PSU-protection behavior, all self-verifiable on any Windows 10/11 PC. The ordered hardware causes (overheating, PSU overload/failure, short circuit, unstable memory, wall power) are cross-corroborated across community and vendor troubleshooting threads for sudden, no-blue-screen shutdowns, including the r/techsupport and r/pchelp random-shutdown threads where a failing or second-hand PSU is the recurring verdict and Kernel-Power Event 41 the recurring log entry.
PSU protection behavior (OCP / OPP / OTP) follows the standard defined in Tom’s Hardware’s PSU 101 protections reference and Corsair’s PSU protections explainer. The RTX 40/50-series 12VHPWR / 12V-2x6 connector risk and 2026 incident context draw on TechPowerUp and Club386’s own RTX 5090 connector-failure reporting.
Thermal limits and what “too hot” actually is: our safe CPU temperature guide (first-party). Confirming a genuinely failing supply: our PSU failure symptoms guide (first-party). The restart-vs-shutdown distinction: our PC keeps restarting guide (first-party).

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

External Hard Drive Not Showing Up? Find Where It Disappears — and Don't Format It (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~8 min read · St. Louis County, MO

Every “external hard drive not showing up” guide hands you the same twenty-step checklist and lets you flail through all of it. And near the end, most of them tell you to format the drive — advice that, applied to a drive full of your only copy of something, destroys the very thing you were trying to save. This guide is built around the two questions the checklists skip: where does the drive disappear, and is the drive failing or just misconfigured? Answer those two, in that order, and the correct fix falls out — usually a free one, and often without any risk to your data.

The reassuring part, echoed across the r/datarecovery and r/techsupport threads on this exact problem: an external drive that won’t show up is usually not a dead drive. Far more often it’s an underpowered port, a tired cable, a missing drive letter, a failing enclosure board, or a partition Windows suddenly can’t read. Each of those has a different fix, and the drive tells you which one — by where it stops appearing as you climb the detection ladder.

Step 1: The 60-second detection ladder

Before you change anything, find out how far up the ladder your drive gets. Plug it in and check these three places, in order. Where it first fails to appear is the single most useful fact you can gather.

File Explorer (This PC). If the drive shows here with a letter, it works — you’re done, or you’re chasing a “wrong letter / shows as the wrong thing” cosmetic issue.
Disk Management (right-click Start → Disk Management, or run diskmgmt.msc). If the drive is here but not in File Explorer, the hardware is fine and you have a disk-layer fix — Step 3. This is the best place to land.
Device Manager (right-click Start → Device Manager; look under Disk drives and Universal Serial Bus controllers). If the drive is here but not in Disk Management, you’re at the driver-and-enclosure layer — Step 4.

And if it appears in none of the three — often with no connection chime at all — you’re at the power-and-cable layer, or the drive is genuinely failing. That’s Steps 2 and 5.

Almost every “my external drive won’t show up” post is really one of these rungs, and people burn hours on power-and-cable fixes for what is actually a two-click drive-letter problem in Disk Management. Find the rung first.

Step 2: Not showing anywhere — the power and connection pass

If the drive is invisible across all three tools, start at the physical layer. This takes two minutes and clears a surprising share of cases.

Change the port — and use the rear of a desktop. Front-panel USB and unpowered hubs deliver less stable power than the ports wired directly to the motherboard on the back of the machine. Plug the drive straight into a rear port.
Swap the cable. A worn or partly-seated USB cable is one of the most common hidden culprits, and it’s free to rule out. Micro-USB and USB-C connectors on portable drives wear loose over years of use.
The bus-power trap on 2.5-inch drives. A portable drive that spins up for a second and then stops is almost always starved for power. A USB 2.0 port supplies about 500 mA and USB 3.x about 900 mA, but a mechanical drive draws a surge as it spins up — if the port can’t deliver it, the controller resets and the motor never ramps. The fix: use the drive’s Y-cable into two ports, plug into a powered USB hub with its own AC adapter, or, for a desktop drive with a barrel-plug adapter, use the wall adapter rather than bus power.
Try a second computer. If the drive appears on another machine, your original PC’s ports, power, or drivers are the problem, not the drive. If it appears on no machine, move to Step 5.

If a rear port, a fresh cable, or proper power brings the drive back into File Explorer, you’re finished. If it now appears but only in Disk Management or Device Manager, follow the matching step below.

Step 3: Shows in Disk Management — the disk layer (and two landmines)

This is the best rung to land on, because the drive is detected and talking. But it’s also where the standard advice gets dangerous, so read carefully. Open Disk Management and find the drive in the lower pane.

Healthy volume, no drive letter. Right-click the volume → Change Drive Letter and Paths → Add → pick a letter. It appears in File Explorer immediately. This is the happiest outcome and a genuinely common one.
“Offline.” Right-click the disk → Online. Windows occasionally marks an external disk offline after a bad disconnect.
Landmine 1 — “RAW” or “you need to format the disk.” Stop. RAW means Windows can no longer read the drive’s file system — not that your data is gone. Formatting lays a fresh, empty file system over your files and makes recovery much harder. If this drive held anything you care about, treat it as a recovery job: run reputable recovery software to pull your files to another disk first, and only format afterward to reuse the drive.
Landmine 2 — “Not Initialized” / “Unallocated” on a drive that had data. Windows will cheerfully offer to Initialize Disk. Do not click it on a drive that held data. Initializing writes a new, blank partition table over the existing one — the exact structure recovery software needs. Click Cancel and recover first. Initialize is only correct for a genuinely new, empty drive.

There’s a tell that separates a software problem from a hardware one here: if you try to initialize and Windows throws “The request failed due to a fatal device hardware error” or “Incorrect function,” that’s not a setting you can fix — the drive or its enclosure is physically failing. Don’t keep retrying. Jump to Step 5.

Step 4: Shows only in Device Manager — driver and enclosure

If Device Manager lists the drive but Disk Management doesn’t, the fault is in the connection layer — the enclosure’s USB-to-SATA bridge board or a driver, not the storage platters.

Reinstall the driver clean. In Device Manager, right-click the drive → Scan for hardware changes. If that fails, uninstall the device, then unplug and replug so Windows reinstalls the driver fresh. This clears a corrupt or half-loaded USB driver.
Check for a warning icon. A yellow mark, “This device cannot start (Code 10),” or a device that appears and vanishes points at the enclosure’s bridge board.
The enclosure-versus-drive test — the wedge for external drives specifically. A pre-built external drive is just a bare hard drive inside a plastic enclosure with a little USB bridge board. That board fails far more often than the drive itself. If the drive shows a heartbeat in Device Manager but never a usable disk, open the enclosure (or “shuck” it) and connect the bare drive to a USB-to-SATA adapter or an internal SATA port. If the drive comes to life that way, the enclosure was the whole problem, and a USB-to-SATA adapter costs a few dollars against a drive you’d otherwise have written off.

If this is a small USB flash drive or a non-storage gadget rather than a hard drive, the driver-and-descriptor angle is a slightly different animal — the USB device not recognized triage covers that error path in full.

Step 5: Nothing, noise, or a fatal error — is the drive dead?

If you’ve changed ports, swapped cables, given it proper power, and tried a second machine, and the drive is still invisible everywhere — or it makes noise — it’s time to decide between “failing” and “already failed,” and to stop doing anything that risks the data.

Repeated spin-up-and-stop, buzzing, or no chime at all after a proper power pass points at a dead enclosure board or a seized drive. Try the bare-drive test from Step 4 once; if it changes nothing, stop.
Clicking or beeping is a mechanical distress signal, not a detection quirk, and every power-on risks it further. A rhythmic click is usually a head problem — see hard drive clicking. A repeated beep with the drive not spinning is either a power problem or a seized motor, and it has its own fork — see hard drive beeping before you plug it in again.
A rising “Pending Sector” or “Reallocated Sector” count (visible in CrystalDiskInfo when the drive is readable enough to check) means the drive is actively deteriorating. Get what you can and retire it.
“Fatal device hardware error” on initialize — as in Step 3 — is a hardware verdict. It won’t clear with a setting.

For irreplaceable data on a drive that’s mechanically sick, the right move is a professional recovery service, not a fourth software attempt — DIY retries on a dying drive are the single most common way a recoverable problem becomes an unrecoverable one. If the data is expendable and the drive is simply worn out, replace it; a modern external hard drive is cheap insurance, and this time, keep a second copy.

(If the drive that won’t show up is an internal SSD rather than an external one, the detection ladder runs through BIOS instead of USB — see SSD not showing up for that layered triage.)

The bottom line

An external drive that won’t show up is rarely a dead drive, and you don’t need the giant checklist — you need to find the layer it disappears at and answer one safety question before you touch a format button. If it’s absent from all three tools, work the power-and-cable pass: rear port, fresh cable, and real power for a hungry 2.5-inch drive. If it’s in Disk Management, it’s usually two clicks — assign a letter or bring it online — with the hard rule that you never format or initialize a drive that still holds data. If it’s only in Device Manager, suspect the enclosure board and test the bare drive. And if it’s invisible everywhere or making noise, only then is the drive itself the answer — and protecting the data comes before everything else. Find the rung, answer the safety question, and most of the time the drive was never the problem at all.

Games Keep Crashing on PC? Sort the Crash by What It Looks Like First (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~9 min read · St. Louis County, MO

Search “games keep crashing pc” and you get the same twenty-item checklist over and over: update drivers, verify files, disable XMP, check temps, run SFC. It’s not wrong - but handing you all twenty at once, in no order, is why people “try everything” and still crash. The list ignores the one thing that actually narrows it down: what the crash looks like.

A game that quietly closes to the desktop, a blue screen with an error code, and a whole PC that hard-locks or reboots mid-game are three different failures with three different culprits. Sort your crash into the right one first and you can skip three-quarters of that checklist. Here’s the fork, then how to read the actual crash instead of guessing at it.

Step 1: what does the crash actually look like?

Before you change one setting, put your crash in a row. This is the fork nobody leads with, and it’s the whole game:

What happens	What it almost always means	Where to aim
One game closes to desktop, no blue screen, PC stays fine	Game files, GPU driver, or an overlay	Game-level fixes below
Every game crashes to desktop after a few minutes	Driver, memory/XMP, or heat	System-level fixes below
Blue screen (BSOD) with a stop code	Driver or hardware - read the code	Read the crash, then system fixes
Whole PC hard-locks (frozen, must hold power button)	Heat, RAM, or power delivery	Computer keeps freezing
Whole PC reboots instantly, no warning	Power supply or thermal shutdown	PC keeps restarting
Screen goes black, then game recovers or drops you out	GPU driver timeout (TDR)	GPU driver crash fix

The two most useful splits inside that table: one game versus every game, and crash-to-desktop versus the whole machine going down. If it’s one game closing to desktop, your hardware is almost certainly fine and you’re wasting time in the BIOS. If it’s every game plus blue screens or a dead machine, the problem is system-wide - memory, heat, or power - and no amount of reinstalling one game will fix it.

Step 2: read the crash - don’t guess at it

Windows writes down every crash. Almost nobody looks, which is how the twenty-item checklist survives. Two free, built-in tools turn a guess into a lead.

Reliability Monitor is the friendly one. Press Start, type Reliability History, and open it. You get a calendar with a red X on every crash. Click the day, and each failure shows a plain-language line plus a View technical details link. It’s the fastest way to see whether your crashes cluster right after a Windows update, a driver install, or a new program - which often is the answer.

Event Viewer is the precise one. Press Start, type Event Viewer, then open Windows Logs then Application, and find the red Application Error entry (Event ID 1000) stamped at your crash time. Two fields matter:

Faulting Application Name - which .exe actually died. If it’s the game, the crash is in the game or its renderer. If it’s an overlay or helper app, you just found your culprit.
Faulting Module Name - the specific file that broke. A graphics DLL like nvwgf2umx.dll (NVIDIA), atidxx64.dll (AMD), or d3d12.dll points at the GPU driver or DirectX. A third-party module - RGB software, a capture tool, antivirus - points at that program.

One more clue: the Exception Code. 0xc0000005 is an access violation, and when games throw it repeatedly it usually means bad memory or an unstable overclock - which tells you to go straight to the XMP test below. (Event ID 1001 next to 1000 is just Windows’ crash-reporting entry for the same event.)

If the game keeps its own crash logs - many do, in the game’s folder or Documents - read those too; they often name the exact subsystem that failed.

The game-level fixes (one game, or crash-to-desktop)

If a single game closes to desktop, or every game crashes to desktop without a blue screen, work this list. These are free and none of them touch your hardware:

Update the GPU driver - properly. Get it from NVIDIA, AMD, or Intel directly, not Windows Update (which often ships an older build). If crashes persist, do a clean install: wipe the current driver with Display Driver Uninstaller (DDU) in Safe Mode, then install the latest fresh. Corrupt or half-updated drivers are the single most common cause of crash-to-desktop.
Verify the game’s files. On Steam: right-click the game then Properties then Installed Files then Verify integrity of game files (other launchers have a “repair” button). This re-downloads anything corrupt - the top cause of one game crashing while the rest are fine.
Kill the overlays. Discord, the NVIDIA App/GeForce Experience, AMD Adrenalin, Steam overlay, Xbox Game Bar, and MSI Afterburner / RivaTuner (RTSS) all inject code into the game’s render pipeline. Under DirectX 12 especially, a single overlay can corrupt the command queue the game sends to the GPU and crash it - even if that overlay works fine in other games. Turn them all off, confirm the crash is gone, then re-enable one at a time to find the offender.
Delete the shader cache and update the game. A bad patch or a stale shader cache causes crashes that a driver update alone won’t fix. Clear the cache (NVIDIA Control Panel or the game’s own option) and make sure the game is current.
Check anti-cheat and compatibility. Some anti-cheat systems clash with overlays, virtual machines, or Windows’ Core Isolation. For older games, try running as administrator or in a compatibility mode.

The system-level fixes (every game, BSOD, or the whole PC goes down)

If every game crashes, you get blue screens, or the machine hard-locks or reboots, the problem is your hardware or its settings. Run these in order - cheapest and highest-hit first:

Disable XMP / EXPO and test. This is the highest-hit fix on the system side. Your RAM’s XMP (Intel) or EXPO (AMD) profile is a factory overclock; it can pass everyday use and fail under a game’s memory load. In the BIOS, set memory to default/Auto (JEDEC) speed and test. Crashes stop? Your kit couldn’t hold that overclock - re-enable XMP one speed tier lower, or nudge DRAM voltage up slightly.
Test the RAM itself. If it still crashes at default speed, run MemTest86 from a USB stick for several passes (or Windows Memory Diagnostic). Any error means a bad module - reseat the sticks, try one at a time, and RMA if a stick fails.
Rule out heat. A CPU or GPU hitting its thermal limit shuts down to protect itself, which reads as a mid-game crash or hard-lock. Watch temperatures with HWiNFO or HWMonitor during play; if the CPU or GPU is pinned at 90C+ when it dies, that’s your answer - see CPU overheating and GPU overheating.
Suspect the power supply. An aging or undersized PSU sags under the millisecond power spikes a modern GPU pulls when a game ramps up, dropping the whole system - a hard reboot with no blue screen is the classic signature. Our PSU failure symptoms guide covers how to confirm it and why the “paperclip test” won’t.
Remove every overclock and undervolt. GPU core/memory overclocks and CPU undervolts that seemed stable in a benchmark routinely crash under real game loads. Set everything back to stock and test before you blame a part - and if the blue screen you keep getting is CLOCK_WATCHDOG_TIMEOUT, that revert is not just a diagnostic step, it is the fix.

The quick-win order

If you’d rather have a sequence than a diagnosis, this catches most crashes fast:

Read the crash in Reliability Monitor / Event Viewer - note the faulting module and whether it’s one game or all.
One game only? Verify its files, update the GPU driver, disable overlays. Stop here - it’s not your hardware.
Every game or BSODs? Disable XMP/EXPO and test. This alone fixes a large share of “random” crashes.
Still crashing? Watch temps and test RAM with MemTest86.
Hard reboots with no blue screen? Look hard at the power supply.

Most crashes end in the first three steps. The people who “tried everything” almost always skipped step 1 - they never read the crash, so they were changing settings blind. Sixty seconds in Event Viewer usually tells you which half of this guide you actually needed.

If your game isn’t crashing but stuttering - running but hitching, with uneven frame times rather than a clean shut-down - that’s a different problem; start with why your PC stutters in games.

Hard Drive Beeping and Not Spinning? Power Problem vs Dead Motor (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~8 min read · St. Louis County, MO

Search “hard drive beeping” and almost every result says the same thing: your drive is dead, unplug it, and call a recovery lab right now. Look at who’s saying it — the pages ranking for this are overwhelmingly data-recovery companies, and “every beep is fatal, send it to us” is their business model, not the whole truth. Here’s what they bury: a beep only tells you one thing — the platters aren’t spinning up — and there are two very different reasons for that. On an external drive it’s frequently just starved for power, which is often a free fix. On an internal drive it’s usually a seized motor or stuck heads, which genuinely is mechanical failure. Same sound, opposite responses. This guide gives you the fork that tells them apart, then exactly what to do for each.

The one rule first: if this drive holds anything you can’t lose and it does still mount even briefly, start copying the important files now, before you finish reading. A beeping drive’s window can be short, and a backup helps you whether the beep turns out to be a cheap power fix or a dead motor.

What a beep actually means

A hard drive is a sealed stack of platters spun by a spindle motor to several thousand RPM, with read/write heads floating microns above the surface. A healthy modern drive is nearly silent. A beep — a repeated electronic-sounding tone, sometimes a chirp or squeak — is the sound of the spindle motor trying to spin the platters and failing. The motor draws power, strains against whatever is stopping it, and you hear that struggle. Data-recovery labs and Seagate’s own support notes agree on the two root causes:

It’s not getting enough power to spin. Common on external and USB-powered drives — the motor needs a certain current to reach speed, and if the port, cable, or adapter can’t deliver it, the drive browns out and beeps. This is the fixable one.
The mechanism is physically stuck. The heads have bonded to the platter surface (a state called stiction, often after a drop or a power loss mid-write), or the spindle bearing has seized. The motor can’t overcome it, so it strains and beeps. This one needs a lab.

Two quick sanity checks before you go further. Is it actually the drive, or your motherboard? A series of beeps at startup from the PC speaker is a POST error code (RAM, GPU, etc.), not the drive — that’s a different problem entirely. And SSDs don’t beep. They have no motor and no moving parts, so if a drive you think is an SSD is “beeping,” the sound is coming from something else in the case.

The 20-second triage: which beep do you have?

Answer three questions and you’ll know which section to read.

External/USB or internal? Is this a portable or desktop external drive on a USB cable (or its own wall adapter), or a bare drive inside your PC on SATA and power cables? External is far more likely to be a power problem.
Does it try to spin at all? Put a finger on it (gently): do you feel it attempt to spin up and then stall, or is it dead-still and silent apart from the beep? A motor that tries and browns out points to power; a completely dead, resistant feel points to a seized bearing or stuck heads.
What happened right before? Did you drop it, knock it, or lose power mid-copy — or did it just start beeping on its own during normal use? A drop or power-loss-mid-write strongly suggests stuck heads (mechanical); “it just started” leaves both branches open.

Match your answers:

External/USB drive → try the power fixes in Step 1 first. They’re free and safe.
Internal drive, or external that still beeps on good power → treat it as a mechanical failure (Steps 2–4).

Step 1: The power fork — the free fix (external/USB drives)

This is the outcome the recovery-lab pages don’t want to lead with, and it’s real. On r/datarecovery, one of the most useful replies on beeping-drive threads comes from a tech who’s seen dozens: “Quite a few of them just had bad or overloaded power bricks. Others had failed USB converter boards… transplanting them into generic enclosures fixed others.” An external drive that beeps is very often a drive that simply can’t pull enough current to spin. Try these in order, cheapest first — none of them risk the drive:

Plug directly into a rear motherboard USB port. Not a front-panel port, not an unpowered hub, not a monitor or keyboard passthrough. Rear ports wired straight to the board deliver the cleanest, strongest power.
Swap the USB cable. A thin, long, or damaged cable drops voltage before it reaches the motor. Use the shortest good-quality cable you have.
Combine two ports with a Y-cable. Many 2.5-inch portable drives ship with a USB Y-cable — a split cable with two USB-A ends. A single port is often limited to 500mA; plugging both ends of a Y-cable into two ports pools them for roughly 1000mA, which is frequently the difference between a beep and a clean spin-up. A powered USB hub does the same job.
Use the right adapter for a 3.5-inch drive. Desktop externals have their own AC power brick — make sure it’s the correct one, plugged into the wall (not a browning-out power strip), and try a known-good replacement brick if you have one.
Do the enclosure test. If good power still won’t wake it, the failure may be the USB-to-SATA bridge board inside the enclosure, not the drive. Carefully open the external case, remove the bare drive, and connect it directly to a PC’s SATA and power connectors (or a known-good USB-to-SATA adapter). If the bare drive spins up and shows up, the enclosure electronics were the whole problem and your data is fine.

If more power — or bypassing the enclosure — gets the drive spinning and mounting, you’re done; back up your files immediately and consider retiring that drive or enclosure. If it still beeps and won’t spin on every port, cable, adapter, and a direct SATA connection, the drive itself is mechanical, and the next steps apply.

Step 2: The mechanical fork — a seized motor or stuck heads

When power is ruled out, a beeping drive that won’t spin is telling you the mechanism is stuck. Two failures produce this:

Head stiction. The read/write heads are supposed to park off the platters when powered down, but if the drive lost power mid-operation or took a knock, a head can settle onto and bond to the platter surface. On the next power-up the motor tries to spin, the stuck head acts as a brake, and the motor strains and beeps instead of turning.
A seized spindle bearing. The bearing the platters spin on can jam or wear out of alignment, so the motor simply can’t rotate the stack. Same result: strain, beep, no spin.

Both are physical problems inside a sealed assembly. That single fact governs everything from here: there is no cable, no driver, and no software that un-sticks a head or frees a seized bearing. Attempts to “force” it only risk the platters, where your data actually lives.

Step 3: If it’s mechanical — do this right now (and what NOT to do)

The order of operations matters more than any single trick.

Stop power-cycling it. If it beeps and won’t spin on known-good power, every additional attempt risks dragging a stuck head across the platters. Resist the urge to keep trying “just once more.”
Decide how much the data is worth — now, before doing anything else. If the files are backed up or replaceable, you’re done: recycle the drive and replace it. If they’re irreplaceable, don’t experiment; the more the drive runs, the worse a recovery gets.
If the data is critical, go to a professional recovery lab. Opening a drive to free stuck heads or replace a motor requires a Class 100 / ISO 5 cleanroom — a speck of household dust is larger than the head-to-platter gap and will wreck the surface.

What NOT to do — every one of these is common online advice, and every one makes a genuinely stuck drive worse:

Don’t put it in the freezer. On any modern drive this condenses moisture onto the platters and causes a head crash on spin-up. It can turn a routine lab repair into an unrecoverable one.
Don’t keep power-cycling “to see if it catches.” Each attempt is another chance to score the platters.
Don’t run repair software or CHKDSK. Those fix logical/file-system errors; they can’t move a seized motor, and forcing reads hammers stuck heads against the surface.
Don’t open the drive yourself. Platters exposed to room air and dust are usually finished. Leave the case sealed for the cleanroom.

Step 4: Recovery, or replace?

Once you’ve decided the data’s fate, the choice is simple:

Irreplaceable data, no backup, drive is genuinely stuck → a professional data recovery service is the only path. It isn’t cheap — motor or head work typically runs several hundred to over a thousand dollars — so it’s worth it only for files you truly can’t lose. One tip from people who’ve been through it: the big, heavily-marketed recovery brands often charge two-to-four times what smaller, equally-capable cleanroom labs do. Get a couple of quotes before you commit; the flashiest name isn’t automatically the best value.
Data was backed up, or you can live without it → spend nothing on recovery. Recycle the drive responsibly and replace it.

For the replacement, a beeping drive is a good argument for leaving spinning disks behind wherever you can. A solid-state drive has no motor and no heads, so it can’t seize, stick, or beep — and our best NVMe SSDs for a homelab covers reliable picks. Keep spinning drives only where their capacity-per-dollar still wins — bulk and cold storage — and never as the single copy of anything you care about.

The bottom line

A beeping hard drive means one specific thing: the platters aren’t spinning up. Before you accept the “it’s dead, send it in” verdict the search results push, ask the two questions that actually matter — is it external or internal, and does it spin on good power? An external drive that beeps is very often just starved for power: rear port, better cable, a Y-cable or the right adapter, or pulling the bare drive out of a dead enclosure, and it comes right back to life. Only an internal drive — or an external that still won’t spin on known-good power — is the genuine mechanical failure, and there the move isn’t the freezer or repair software; it’s to stop power-cycling it and decide whether the data justifies a cleanroom lab. If the sound is a rhythmic click rather than a beep, that’s a related but distinct diagnosis — our hard drive clicking triage covers it. And if the drive is silent but simply not showing up, that’s a more hopeful problem with its own ladder. Match the fix to the cause, and most of the time your data — and sometimes the drive — wasn’t as doomed as the results made it sound.

Hard Drive Clicking? How to Tell Normal Noise From the Click of Death (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~8 min read · St. Louis County, MO

Search “hard drive clicking” and every result tells you the same thing: it’s the “click of death,” your drive is dying, stop everything and call a recovery lab. That advice isn’t wrong — but notice who’s giving it. The pages ranking for this are mostly data-recovery companies, and they have a commercial reason to make every click sound fatal. The truth is more useful: there are three different clicks, and they call for opposite responses. One is harmless. One is a free fix. Only the third is the drive actually dying — and if that’s the one you have, the recovery-lab pages still bury the single thing you should do right now.

This guide gives you the 30-second triage to tell which click you have, then exactly what to do for each. The good news, echoed by the top-voted reply on nearly every r/computers and r/techsupport thread about this: “People always immediately say it’s dying whenever a hard drive makes a sound, but sometimes it’s actually normal.”

First, the one rule that applies to all three: if this drive holds anything you can’t lose and you have a second working drive or cloud space, start backing up the important files now, before you finish reading. Whether the click turns out to be harmless or fatal, you’re better off with a backup either way — and if it is fatal, the window can close in minutes.

Step 1: The 30-second triage — which click do you have?

Before any fix, answer three questions. They pin your click to one of three causes and tell you which section to read.

Does the drive still work? Can you open files, and does the system see the drive in File Explorer or BIOS? Working = far more likely normal or power-related. Not detected or crawling = the dangerous one.
What’s the pattern? An occasional soft click during activity, then silence, is very different from a steady, rhythmic click-click-click every second or so that doesn’t stop. Occasional = usually normal. Rhythmic and persistent = classic click of death.
Internal or external/USB? Is this a drive inside your PC on a SATA/power cable, or an external/USB-powered drive? External drives that click and drop out are very often a power problem, not a failure.

Now match your answers:

Works fine + occasional click + any type → probably normal (Step 2).
External/USB + clicks and disconnects → probably power (Step 3).
Rhythmic click + not detected or very slow → treat as the click of death (Steps 4–6).
Not detected but silent (no click at all) → this isn’t a clicking problem — it’s a detection one, and the fix is different. Walk the external hard drive not showing up ladder instead.
A repeated beep rather than a click, and the drive isn’t spinning → that’s a different sound with its own fork (a power problem or a seized motor). See hard drive beeping instead.

Almost every clicking-drive panic is one of these three, and people routinely apply death-panic responses to a drive that was only parking its heads — or worse, keep power-cycling a genuinely failing drive and finish it off.

Step 2: Normal clicking — the drive is fine

A hard drive has moving parts, and moving parts make sound. The most common “is my drive dying?” click is simply the drive parking or repositioning its read/write heads. Power-saving drives are the usual suspects: features like Western Digital’s IntelliPark park the heads after just a few seconds of idle, and some drives do this aggressively — you’ll hear a brief whir and a soft click every so often. That’s the drive working as designed, not failing.

How to know it’s the harmless kind:

The click is occasional and relatively quiet, often during or just after disk activity, not a nonstop rhythm.
The drive still works normally — files open, copy speeds are normal, nothing freezes.
It’s been doing it for a while without getting worse or losing data.

What to do: confirm with data, don’t guess. Download the free CrystalDiskInfo (or HDD Sentinel) and check the drive’s SMART health. If it reads “Good” with no reallocated or pending sectors, relax — and take the click as a nudge to make sure your backups are current, because every drive dies eventually. If SMART reads “Caution” or shows rising bad-sector counts, jump to Step 5; the click is early wear, not just parking.

Step 3: The power-starved click — often a free fix

This one catches people constantly, and it’s the happiest outcome: an external or USB-powered hard drive that clicks and disconnects usually isn’t broken — it’s not getting enough power to spin up. The motor tries to start, browns out, and retries, which sounds exactly like clicking. Seagate and Ontrack both list undervoltage as a top cause of external-drive clicking, and forum threads on this are full of “I changed the USB port and it just started working.”

Try these in order, cheapest first:

Plug directly into a rear motherboard USB port, not a front-panel port, an unpowered hub, or a monitor/keyboard passthrough. Rear ports off the board give the cleanest power.
Swap the USB cable. A thin, long, or damaged cable drops voltage. Use the shortest good-quality cable you have.
Give it more power. Use the drive’s USB Y-cable (the split cable with two USB-A ends — both plug in) or a powered USB hub. A 3.5-inch external with its own AC adapter should be on that adapter, plugged into the wall, not a power strip that’s browning out.
Try a different computer. If it behaves on another machine, your original port or cable was the problem.

If more power makes the clicking stop and the drive mount reliably, you’re done — the drive was fine all along. If it still clicks rhythmically and won’t mount on any port or machine, treat it as the click of death below.

Step 4: The real click of death — what it actually is

The genuine article is unmistakable once you know it: a loud, steady, rhythmic click — often described as click…click…click every second or so, sometimes with a whir-and-reset between clicks — usually paired with the drive no longer being detected, mounting and then dropping, or reading painfully slowly.

Mechanically, this is the read/write heads failing to do their job. Every platter has servo tracks that tell the heads where they are; if the heads are damaged (commonly from a drop or impact) or can’t read the drive’s firmware zone, the arm sweeps to find its position, fails, resets, and tries again — over and over. That repeated sweep-and-reset is the clicking. It means the failure is physical, and that single fact determines everything about what you should and shouldn’t do next.

Step 5: If it might be dying — do this right now

If your triage points to failure — rhythmic click, drive dropping out, SMART in Caution — the order of operations matters more than any single fix.

If the drive is still readable at all, image or copy it immediately. Don’t cherry-pick files slowly; grab the most important data first, then attempt a full copy. Every minute a failing drive runs is borrowed time. If it’s an internal drive dropping out under load or heat, copy while it’s cold and visible.
Check SMART only if the drive is stable enough to stay powered. CrystalDiskInfo’s Reallocated Sector Count, Pending Sector Count, and health rating tell you how far gone it is. But don’t keep a rhythmically-clicking, undetected drive spinning just to run diagnostics — reading the data matters more.
Once you have what you can, power it down. A drive that’s clicking and undetected has nothing more to give you at home, and continued spinning risks scoring the platters.

The reason this ordering is non-negotiable: on a head-failed drive, the data is still on the platters right up until the heads physically damage them. Your job is to get bits off before that happens, not to “repair” the drive.

Step 6: What NOT to do (this is where people destroy their data)

Every one of these is common advice somewhere online, and every one makes a genuinely failing drive worse:

Don’t put it in the freezer. This myth won’t die, but on any drive made in the last ~20 years it’s actively harmful. Modern drives aren’t airtight — a breather filter means humid air is already inside — so cooling condenses water across the heads and platters, and spin-up causes a head crash. Recovery labs say the freezer can turn a simple firmware repair into a $1,000+ head swap. Skip it.
Don’t keep power-cycling it “to see if it catches.” Each restart of a head-crashed drive is another chance for the heads to gouge the platters. Repeated power cycling is one of the fastest ways to convert recoverable data into unrecoverable data.
Don’t run repair software or CHKDSK on a mechanically clicking drive. Software can’t fix a physical head failure, and forcing reads hammers the failing heads against the surface. Repair tools are for logical/file-system problems, not a clicking drive.
Don’t open the drive. Platters need a cleanroom; a speck of household dust larger than the head-to-platter gap will wreck them. Opening it at your desk guarantees the recovery lab’s job gets harder or impossible.

Step 7: Recover, or replace?

Once you’ve saved what you can (or confirmed it’s gone), it’s a simple decision:

Data you must have, no backup, drive is dead → a professional data recovery service is the only path once the heads have failed. It’s not cheap (often several hundred to over a thousand dollars), so it’s worth it only for genuinely irreplaceable files.
Data was backed up, or you can live without it → don’t spend a cent on recovery. Recycle the drive responsibly and replace it.

For the replacement, this is the moment to consider leaving spinning drives behind for anything you touch daily. A solid-state drive has no heads and no platters, so it can’t click and can’t suffer this failure mode — and our best NVMe SSDs for a homelab covers reliable picks. If you’re pricing drives right now, note that storage costs have moved a lot this year — our RAM and SSD price crisis breakdown explains what’s driving it. Keep a spinning drive only where it makes sense — bulk cold storage and backups — and never as the single copy of anything you care about.

The bottom line

A clicking hard drive is not automatically a dead one. Run the 30-second triage first: does it still work, is the click occasional or a steady rhythm, and is it internal or external? An occasional soft click on a working drive is normal head parking — verify with CrystalDiskInfo and move on. An external drive that clicks and drops out is usually starved for power — better cable, rear port, powered hub, and it comes back to life. Only a loud, rhythmic click on a drive that’s no longer detected is the true click of death — and if that’s you, the move isn’t the freezer or repair software, it’s to copy every file you can right now, then power down and decide between a recovery lab and a fresh drive. Find your click, act on that click, and most of the time your data — and often the drive — was never as doomed as the search results made it sound.

How Often Should You Replace Thermal Paste? Stop Using a Calendar (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~9 min read · St. Louis County, MO

Search “how often to replace thermal paste” and the top results openly contradict each other. A well-ranked guide tells you every 2 to 3 years. Corsair’s own page says paste “will typically last many, many years and the vast majority of users should never have to worry about it.” A veteran on the Linus Tech Tips forum swears by at least once a year. On r/buildapc, the single most-upvoted answer to this exact question is four words: “When your temps give you trouble.”

They’re not wrong — they’re answering slightly different questions and pretending it’s one answer. The useful version of this question isn’t “what’s the magic interval.” It’s “what actually tells me my paste needs replacing” — and the answer is a temperature, not a date.

The honest answer: repaste on a number, not a schedule

Here’s the thing the calendar-based advice skips. Thermal paste doesn’t degrade on a fixed timer like milk. It degrades based on how hot it runs and how many heat cycles it goes through — which is why a lightly-used office PC and a gaming laptop that throttles every night age their paste at completely different rates. A date can’t capture that. A temperature can.

So the real trigger is a rise in your temperatures over time on the same machine. If your CPU used to idle at 35 °C and sit at 65 °C in games, and now it idles at 45 °C and hits 85 °C on the same workload in the same room, something in the cooling path has degraded — and aging paste is one of the usual suspects. If those numbers haven’t moved in three years, your paste is fine no matter what the calendar says.

This is why the r/buildapc hive-mind lands on “if it ain’t broke, don’t fix it,” and why it’s genuinely good advice rather than laziness. Repasting isn’t free maintenance — it carries a small risk (more on that below), so doing it on a schedule when nothing’s wrong is accepting downside for no measured upside.

The one habit that makes all of this easy: know your baseline. Install HWiNFO (free) once, note your normal idle and load temperatures for the CPU and GPU when the machine is new or freshly cleaned, and you’ll have something to compare against later. Not sure what “normal” even is? Our safe CPU temperature guide lays out the real ranges. Without a baseline, you’re guessing; with one, “is it time to repaste?” becomes a two-minute check instead of a debate.

Why the intervals disagree: it depends on four things

The “2-3 years” versus “many years” gap isn’t people being careless. It’s real variation driven by four factors. Find yourself in this table and you’ll understand why your situation might call for a repaste at year two or year eight:

Factor	Repaste sooner	Repaste later (or never)
Paste quality	Cheap or factory pre-applied paste; some can harden in 1-2 years	Quality aftermarket paste (Arctic MX-4/MX-6, Thermal Grizzly); often 5+ years
Heat & load	Gaming hard daily, overclocked, hot room, small case	Light use, cool room, good airflow, modest clocks
Form factor	Laptops and consoles — tiny coolers, very high temps	Roomy desktop with a big air or liquid cooler
Component	GPUs (pump-out prone), especially RTX 30/40-series	Desktop CPUs under a well-mounted cooler

The pattern is clear: heat and paste quality dominate. A builder running premium paste in a cool, well-ventilated desktop can genuinely go the entire life of the PC without touching it — that’s the Corsair “never worry” camp, and for that person it’s correct. Someone with a factory-pasted prebuilt that games hard in a warm room is the “2-3 years” camp, and that’s correct too. Both answers are right for the person giving them; neither is universal.

One real-world example from the community that captures it perfectly: a builder reported the factory paste on a Gigabyte Windforce GPU turning to “solid cement” inside 12 months, while another has run the same aftermarket paste on a desktop CPU for nine years with no temperature increase at all. Same question, two honest answers, driven entirely by paste quality and heat.

Signs it’s actually time (the checklist that beats a date)

Rather than counting years, watch for these. Any one of them is a reason to investigate; the paste is the suspect only after you’ve ruled out the cheaper causes:

Temperatures crept up on the same workload compared to your baseline — the headline signal.
Fans are louder than they used to be at idle or under light load (the cooling system compensating for worse heat transfer).
The chip is throttling — clock speeds dropping under sustained load, or stutters and slowdowns during gaming. If your whole system locks up instead, that’s worth separating out; see why a PC keeps freezing.
Thermal shutdowns — the machine cutting off under heavy load to protect itself.

Crucial caveat: all of these can be caused by dust or a failing fan long before they’re caused by paste. A heatsink choked with dust raises temperatures far more often than aged paste does, and it’s a five-minute fix instead of a teardown. Blow out the dust with compressed air and confirm every fan actually spins (a stopped CPU fan will spike temps overnight) before you conclude it’s the paste. Repaste is the answer when temps are high, dust is ruled out, and the fans are working — not the first thing you reach for.

The GPU exception: pump-out is real

Graphics cards deserve their own note, because they age differently from desktop CPUs. GPUs are prone to pump-out — repeated heating and cooling slowly squeezes paste out from the center of the die, where it’s needed most. It’s common enough that RTX 30- and 40-series cards are known for it after roughly 18-24 months of hard use.

The giveaway isn’t the core temperature; it’s the hotspot-to-core delta. If the gap between your GPU’s hotspot (junction) and core temperature has widened over time — past about 20 °C on NVIDIA or 30 °C on AMD — the thermal interface has degraded, and a repaste often closes it by 5-15 °C. We walk through that exact measurement in the GPU overheating guide, and it’s the cleanest example of “measure, don’t guess” there is. The same logic applies to a hot CPU — confirm it’s genuinely overheating and rule out dust before you tear the cooler off.

One firm rule: if the card is still under warranty, don’t open it. Removing the shroud usually voids coverage, and a card that’s overheating under warranty should be an RMA, not a DIY repaste.

When you have no choice: after removing the cooler

There’s one scenario where “how often” doesn’t apply at all — any time you take the cooler off, you repaste, full stop. Lifting the heatsink breaks the thin, evenly-spread layer that was doing the work; pressing it back down onto disturbed paste leaves gaps and air pockets that make contact worse than before. So if you’re swapping a cooler, reseating a CPU, or opening a GPU for cleaning, factor a fresh application in every time, regardless of how old the existing paste is.

How much to use (since you’ll be at it anyway)

Over-application is the most common mistake, and it’s counterproductive — too much paste acts as an insulator and can ooze onto the socket. For most desktop CPUs, a pea-sized dot or a small dab in the center is right; the cooler’s mounting pressure spreads it into a thin, even layer as you tighten it down. You don’t manually smear it (that traps air). Larger chips like Threadripper or a big GPU die want a bit more, sometimes a thin line or an X, but the principle holds: a little, placed center, let pressure do the spreading. A single good tube of paste will last you many applications, so there’s no reason to be generous with any one of them.

The quick version

Ignore the calendar. Paste ages by heat and cycles, not by date, so “every X years” is a bad rule. A cool, lightly-used desktop with quality paste can go the life of the PC; a hot gaming laptop wants it every 2-4 years.
Repaste on a temperature. The real trigger is your idle and load temps creeping up 5-10 °C versus your machine’s own baseline — after you’ve ruled out dust and a failing fan, which cause the same symptoms far more often.
GPUs are the exception. Pump-out is real on RTX 30/40-series after ~18-24 months; watch the hotspot-to-core delta widening, not the years.
Don’t repaste for no reason. Pulling a cooler carries a small risk (lifting the CPU, ripping pads, voiding warranty). If temps are fine, leave a working thermal interface alone.
When you do open it, repaste every time — and use a pea-sized amount, center of the die, let mounting pressure spread it.

The builders who say “never” and the ones who say “every two years” are both telling the truth about their own machines. Learn your baseline temperatures, watch for them to rise, and you’ll replace your paste exactly when it needs it — which is the only schedule that was ever going to be right.

Low GPU Usage in Games? How to Tell a Real Bottleneck From a Fake One (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~9 min read · St. Louis County, MO

Search “low GPU usage” and the SERP splits down the middle. Half the results say the same three words - it’s a CPU bottleneck - and the other half are frustrated threads titled “Low GPU usage (NOT A CPU BOTTLENECK)” from people who checked and found their CPU wasn’t maxed either. Both camps are right, because low GPU usage has two completely different causes, and telling them apart takes one reading almost nobody explains: whether a single CPU thread is pegged while the rest coast.

Get that reading right and you’ll know in thirty seconds whether you have a real bottleneck (and roughly what to do about it) or one of the fake ones - an FPS cap, a power setting, or a laptop quietly running the game on its integrated graphics - that get misdiagnosed as bottlenecks every day.

First: is low GPU usage even a problem?

Before you fix anything, rule out the case where nothing is wrong. A GPU that sits below 100 percent is only a problem if your frame rate is also lower than it should be. Usage naturally drops in menus, on loading screens, in lightweight or older games, and - importantly - any time you’ve capped your frame rate below what the card can produce. If you cap to 60 FPS and the card could do 140, it will coast at 45 to 60 percent usage and hold a perfect 60. That’s the card working correctly, not a fault.

And while we’re here: 100 percent GPU usage is the goal, not a warning. A pinned GPU means the graphics card is the thing setting your frame rate and nothing else is holding it back - exactly what you want. It doesn’t wear the card out; GPUs are built to run at full load for hours, and their own temperature and power limits protect them. The only asterisk is thermal throttling: if 99 percent usage comes with temperatures hitting the card’s limit and clocks sagging, that’s a cooling problem, not a usage one (our CPU overheating guide has the same logic for the processor side).

So the real symptom worth chasing is narrow: GPU usage well under 90 percent and a frame rate below what your hardware should deliver. That’s the rest of this guide.

The reading everyone gets wrong: total CPU% lies

Here’s the mistake that sends people down the wrong path. They open Task Manager, see the CPU at 35 percent, conclude “not a CPU bottleneck,” and start blaming the GPU, the drivers, or the game.

The single system-wide CPU number is misleading for gaming. Modern processors have 8, 12, 16 cores - but most games lean hard on one or two main threads (a render thread, a main game-logic thread) and barely touch the rest. When that one thread hits 100 percent, it caps your frame rate no matter how idle the other cores are. On a 12-thread CPU, one fully-maxed thread shows up as roughly 8 percent system-wide. So a game can be completely CPU-limited while Task Manager’s headline number reads 30 or 40 percent.

Always look at per-core load, not the rolled-up percentage. In Task Manager, open the Performance tab, click CPU, then right-click the graph and choose “Change graph to → Logical processors” - now you see every thread. If one is slammed against the ceiling while the others loaf, that’s your bottleneck, full stop. (MSI Afterburner and HWiNFO can show per-core load as an in-game overlay if you’d rather watch it live.)

One more measurement trap: Task Manager’s GPU percentage itself is unreliable for games. It defaults to showing whichever GPU “engine” it feels like, and can display a low number while the 3D engine is actually busy. Trust MSI Afterburner / RivaTuner, GPU-Z, or your GPU vendor’s overlay for real GPU load, not the Task Manager tile.

The fork: one core pegged, or everything coasting?

This is the whole diagnosis. Watch per-core CPU load and true GPU load together during a minute of the actual game, and you land in one of these rows:

What you see	What it means	Where to go
GPU under 90%, one CPU thread near 100%	Real CPU bottleneck	The CPU-limit fixes below
GPU low, all CPU cores also low, and you’re at an FPS cap / refresh rate	Not a problem - the cap is doing its job	Nothing to fix (or raise the cap)
GPU low, all cores low, no cap but FPS still bad	Hidden limiter, power throttle, or wrong GPU	The “fake bottleneck” fixes below
GPU low on a laptop, dedicated card barely moving	Game is on the integrated GPU	Force the dedicated GPU
GPU pinned at 99% but FPS low	You’re GPU-limited (normal) or throttling	Lower settings, or check temps

The single most useful clue is whether any one CPU thread is maxed. If yes, it’s a genuine CPU limit. If nothing is working hard, stop looking for a bottleneck - something is capping or starving the game before either part gets busy.

When it’s a real CPU bottleneck (one thread pegged)

If a single core is slammed while the GPU coasts, the graphics card is idling because the CPU can’t feed it frames fast enough. This is normal in simulation, strategy, and busy open-world games, and at lower resolutions (1080p leans on the CPU far more than 4K). What actually helps:

Enable XMP (Intel) / EXPO (AMD) in the BIOS. The most common free win by far - memory left at its slow JEDEC default starves the CPU’s frame-feeding, and flipping the profile on often lifts 1% lows immediately.
Close background CPU load - browser tabs, Discord, capture/overlay tools, aggressive antivirus.
Make sure the CPU isn’t thermal-throttling. A hot CPU that drops clocks reads as exactly this symptom; see CPU overheating to rule it out.
Raise resolution or settings if you want the GPU busier. Counter-intuitive but real: pushing more graphics work shifts the limiter back onto the GPU. It won’t raise your FPS, but it puts the card you paid for to work.

What won’t help: lowering resolution or graphics settings. If dropping from High to Low gains you almost nothing, that’s the confirmation you’re CPU-bound - the GPU had headroom to spare. The only true fix for a hard CPU limit is a faster CPU (single-thread performance matters most for games).

The fake bottlenecks (nothing is working hard)

If both the GPU and every CPU core are coasting and your FPS is still bad, you’re not bottlenecked - something is holding the whole system back. Work through these:

A frame-rate limit you forgot about. An in-game FPS cap, V-Sync locking you to your refresh rate, a “Max Frame Rate” set in the NVIDIA/AMD control panel, or an RTSS/launcher cap will all make the GPU coast on purpose. Turn every cap off to test; if usage jumps and FPS climbs, a limiter was the “problem” all along.

Power throttling. Set the Windows power mode to Best Performance (Settings → System → Power). In the NVIDIA Control Panel under Manage 3D Settings, set Power Management Mode to “Prefer maximum performance” so the card doesn’t sit at low clocks (AMD’s equivalent is in Radeon Software). On a laptop, keep it plugged in - on battery, and in “quiet”/“battery boost” modes, the hardware is deliberately capped.

Running on the wrong GPU (laptops especially). This is a top cause of a good GPU showing almost no usage: the game is silently running on the Intel/AMD integrated graphics. Fix it in three places - (1) Windows Settings → System → Display → Graphics, add the game’s .exe and set it to High Performance; (2) NVIDIA Control Panel → Manage 3D Settings → preferred processor = High-performance NVIDIA processor; (3) power mode on Best Performance and plugged in. If it still won’t switch, check the BIOS/UEFI for a graphics/MUX setting and update the GPU driver.

A background thread stealing time or DPC latency. Less common when everything reads low, but a misbehaving network/audio/chipset driver can stall the pipeline; LatencyMon (free) points at the culprit.

VRAM overflow or a crippled PCIe link. If the card runs out of video memory it swaps textures over PCIe and usage gets erratic - drop texture quality and check dedicated VRAM against the card’s limit (our how much VRAM you need guide has the real numbers). And on desktops, a GPU seated in the wrong slot or on a bad riser can drop to PCIe x1 and choke - GPU-Z’s Bus Interface reading (run its render test) tells you the active link width.

The quick-win order

If you want a sequence instead of a diagnosis, run these free steps and re-check per-core CPU and true GPU load after each:

Confirm you’re not just at an FPS cap - turn off every V-Sync/FPS limit to test.
Read per-core CPU load (Task Manager → Logical processors). One pegged thread = CPU-limited; stop here.
Set Windows power mode to Best Performance; NVIDIA Power Management to Prefer maximum performance; laptop plugged in.
On a laptop, force the dedicated GPU for the game (Windows Graphics settings + control panel).
Enable XMP/EXPO in the BIOS and close background apps.

Most “low GPU usage” ends somewhere in the first four steps. The people who “tried everything” almost always skipped step 2 - they read one system-wide CPU percentage, saw 35 percent, and never looked at the maxed core underneath it.

If your frame rate is low but uneven - hitching and micro-stutter rather than a steady low number - that’s a different problem with its own diagnosis; start with why your PC stutters in games, which separates frame-pacing stutter from a genuinely weak GPU.

SSD Not Showing Up in BIOS or Windows? Find the Layer It Disappears At (2026)

LK Wood IV — Sat, 11 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-11 · ~8 min read · St. Louis County, MO

Here is the single question every “SSD not showing up” guide skips, and it’s the one that actually decides your fix: where does the drive disappear? A brand-new M.2 that never appears in BIOS is a completely different problem — with a completely different fix — from a drive that BIOS sees fine but Windows won’t show. Most articles jam every possible cause into one long checklist and let you flail through all of it. You don’t need the whole list. You need to find the lowest layer your drive fails to appear at, because that one observation pins the cause to hardware, firmware, or software — and rules out most of the checklist before you touch anything.

The good news up front, echoed across the r/buildapc and Tom’s Hardware threads on this exact problem: an SSD that won’t show up is usually not dead. Far more often it’s a loose M.2 screw, a keying or lane-sharing quirk in a specific slot, a BIOS storage mode, or a drive that’s detected but simply not initialized yet. This guide walks the detection ladder from the bottom up so you stop at the rung where your drive actually goes missing.

Step 1: Find the layer — the detection ladder

Before any fix, run this three-rung check. Where the drive first fails to appear tells you which section below to read and lets you ignore the rest.

Is it in the BIOS/UEFI at all? Restart, enter BIOS (usually Delete or F2 at boot), and look at the storage or boot device list. If the drive isn’t there, you’re at the hardware and firmware layer — Steps 2 and 3. This is where the M.2 traps live.
In BIOS, but not in Windows? If BIOS lists the drive but it’s absent from File Explorer, the hardware is fine — the drive is detected. You’re at the Windows disk layer — Step 4. This is the easiest fix and the least scary, so don’t panic if you land here.
In Disk Management, but as “Unallocated,” “Not Initialized,” or “RAW”? The drive is present and talking; it just has no usable partition or letter yet. Still Step 4 — with one important data-safety caveat.

Almost every “my SSD isn’t showing up” post is really one of these three, and people waste hours applying rung-1 hardware fixes to a rung-3 software problem. Find your rung first.

Step 2: Not in BIOS — the physical and connection checks

If the drive is absent from BIOS entirely, start at the physical layer. Power off at the PSU switch and mind static.

M.2 mounting screw and seat. An M.2 stick sits at a slight upward angle when it isn’t screwed down, and that angle is often enough to break contact. Remove it, check the slot for dust, re-insert at about a 30-degree angle, press it flat, and secure the standoff screw snugly. A loose or missing screw is one of the most common reasons a freshly installed M.2 never appears.
SATA cables (2.5-inch and 3.5-inch drives). Reseat both the data cable and the power cable at the drive and the board. Then — this is the step people skip — swap the SATA data cable for a known-good one. Cheap or partly-seated SATA cables are a notorious hidden culprit; Seagate’s own support note calls a damaged or loose data cable the first thing to check.
Power connector (SATA drives). Make sure the drive is actually getting power from the PSU. Try a different power lead from the supply; a dead modular cable or a daisy-chained connector can leave one drive unpowered.
Test the slot, not just the drive. If you have a second M.2 slot or a spare SATA port, move the drive there. If it appears in a different slot, you’ve localized the fault to the original slot — often a lane-sharing or keying issue, covered next.

If a reseat and a cable swap bring the drive back, you’re done. If it’s still missing from BIOS, the cause is usually one of the M.2 configuration traps.

Step 3: The M.2 traps most guides bury

This is where the differential diagnosis earns its keep, because these four causes look identical to a dead drive and none of them is one.

NVMe vs SATA keying — the drive fits but never registers. M.2 comes in two electrical flavors that share a physical connector. A SATA M.2 drive will slide into an NVMe-only slot and seat perfectly — and never be detected — and an NVMe drive won’t function in a SATA-only slot. The notch shape (B-key, M-key, B+M) does not tell you what the slot is electrically wired for; a slot can be SATA-only even with an M-key cutout. The authority is your motherboard manual’s M.2 specification, not the drive fitting. If a new M.2 fits snugly but is invisible, confirm the drive’s protocol matches what that specific slot supports.
PCIe lane-sharing — installing the M.2 killed a SATA port (or vice versa). Consumer chipsets don’t have enough PCIe lanes to run every slot and port simultaneously. So on many boards a given M.2 slot borrows its four lanes from specific SATA ports or from a second M.2 slot — and populating one disables the other. If your SATA SSD vanished right after you added an M.2 drive, that’s this. If your M.2 is dead in one slot, it may be sharing lanes with a SATA port you have populated. The manual’s storage block diagram lists exactly which combination disables what. Move the affected drive to a non-shared port.
VMD / RAID storage mode (Intel and ASUS boards). If the board’s SATA/storage mode is set to Intel VMD or RAID, an NVMe drive can be hidden behind that abstraction layer. Switching to AHCI exposes it. Read the VMD caution in the FAQ first — if Windows was installed under VMD, flipping this can make your boot drive unbootable.
CSM / UEFI mode and BIOS defaults. A mode mismatch can hide a drive from the boot list even when the board sees it. The fast reset that clears most of these at once: enter BIOS, load Optimized Defaults, set boot mode to UEFI, then re-check. If the board is older and the SSD is new and large, a BIOS/UEFI firmware update from the board maker’s support page is sometimes what’s needed for the board to recognize the newer drive.

Work these in order — keying, lanes, storage mode, defaults/firmware — and the great majority of “not in BIOS” drives come back without a single part swap.

Step 4: In BIOS but not in Windows — the disk layer

If BIOS lists the drive but Windows doesn’t show it, relax: the hard part is over. The drive is detected. It’s just not presented to you yet. Open Disk Management (right-click the Start button, choose Disk Management) and find the drive in the lower pane.

“Not Initialized.” A brand-new drive arrives with no partition table. Right-click it, initialize as GPT (the modern standard), then right-click the unallocated space, choose New Simple Volume, and assign a drive letter and file system. It’ll appear in File Explorer immediately.
Healthy volume, no drive letter. Right-click the volume, choose Change Drive Letter and Paths, and add a letter. Sometimes Windows just didn’t assign one.
“RAW” or unexpectedly “Unallocated” on a drive that had data. Stop. This is the one place the standard advice becomes dangerous. Initializing or formatting a drive that held data erases it. If this SSD was working and now reads as RAW or uninitialized, treat it as data recovery, not setup — don’t click initialize. Only initialize a drive you know is blank.

The takeaway: a drive that reaches BIOS is a hardware success. Everything from here is a few clicks in Disk Management — unless the drive had data and now looks empty, in which case protecting that data comes before anything else.

Step 5: Is the drive actually dead? The one test that settles it

If you’ve reseated, swapped cables, checked keying and lanes, and loaded BIOS defaults, and the drive is still invisible in BIOS in every slot, run the isolation test before you spend money. Put the SSD in an external USB enclosure or adapter, or connect it to a different computer.

(One note if you landed here about a spinning hard drive rather than an SSD: an SSD has no moving parts and is silent, so it can’t click. If your drive is a mechanical hard drive making a clicking or grinding noise, that points to physical head failure, not a detection quirk — see hard drive clicking for that triage.)

Appears elsewhere → the drive is alive. The fault is in your original system — a slot, a port, a cable, or a BIOS setting. Go back and work Steps 2 and 3 harder, and suspect the motherboard’s storage if a known-good slot won’t see a known-good drive. A dead M.2 slot or SATA controller is a board-level fault: see motherboard failure symptoms.
Appears nowhere → the SSD itself has failed. If it’s under warranty, RMA it. If it held data you need, a recovery service is the only path once the controller is gone. Then replace it — a current NVMe SSD is inexpensive, and our best NVMe SSDs for a homelab covers reliable picks.

This cross-check is the same logic that separates a bad slot from a bad card in a graphics card not detected situation: move the part to a known-good environment and let where it works tell you what’s broken. It takes ten minutes and it’s the difference between a $0 fix and buying a drive you didn’t need.

The bottom line

An SSD that won’t show up is rarely a dead SSD, and you don’t need the giant checklist — you need to find the layer it disappears at. If it’s absent from BIOS, you’re at the hardware layer: reseat the M.2 screw or swap the SATA cable, then check the traps that masquerade as failure — NVMe-vs-SATA keying for the slot, PCIe lane-sharing that disables ports, VMD/RAID mode hiding an NVMe drive, and a BIOS defaults reset. If BIOS sees it but Windows doesn’t, it’s a five-click job in Disk Management — initialize a blank drive, assign a letter — with the one hard rule that you never initialize a drive that still holds data. And if it’s invisible everywhere, in every slot and machine, only then is the drive itself the answer. Find the rung, fix the rung, and most of the time the drive was never broken at all.

Coil Whine: Is It Normal, and Where Is It Coming From? (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

You fire up a game, the frame counter shoots past 300 in the menu, and your PC starts singing — a high-pitched electronic zing that rises and falls with the action on screen. Search the noise and the internet splits into the same two camps every time: that’s coil whine, it’s totally normal, ignore it — or return that card immediately. Both answers skip the two questions that actually matter, and that’s why people either RMA a perfectly good card or spend weeks ignoring a genuine warning sign.

The two questions worth answering, in order, are: is it even coil whine? and where is it coming from? Get those right and everything else — whether to worry, whether to swap it, how to quiet it down — falls out cleanly. Here’s the diagnostic the “it’s normal, move on” articles skip.

Before the steps, the single most useful reframe — because the whole internet argument is really about this one axis. Almost the entire range of “my PC is making a noise” is harmless. A thin sliver at the far end isn’t. Here’s where the sounds actually fall:

The “should I worry?” spectrum

Nearly the whole range is a nuisance, not a fault. Only the far-right sliver is a real warning — and that part isn't coil whine at all. Find your noise on the bar, then read its card.

HARMLESS · ~95% OF CASES
DANGER

STEADY ZING

HARMLESS · DEFAULT

Rises with your frame rate, always been there. Won't hurt a thing. Ignore it — or cap FPS to quiet it.

LOUD & ANNOYING

STILL HARMLESS

Bugs you, but still tracks FPS. Cap frame rate, undervolt — or swap units inside the return window.

NEW PSU BUZZ + CRASHES

WATCH THIS ONE

A new, worsening buzz with random shutdowns can be a dying PSU, not benign whine. Test the power supply.

CRACKLE / POP / BURNING

NOT COIL WHINE · STOP

This is arcing, not whine. Power off and unplug the PC now. Don't power back on to “check.”

If the pitch tracks your frame counter, you're on the green end — decide on noise, not hardware. Only a crackle-pop or a crash-paired buzz earns real worry. techfuelhq.com

Step 1: Is it actually coil whine?

Coil whine has a signature, and it’s not the sound — it’s the behavior. The noise itself is a high-pitched buzzing, squealing, chirping, or zinging; sharp and electronic rather than mechanical. But lots of PC noises are high-pitched. What sets coil whine apart is that it changes with electrical load, not with temperature or fan speed.

Run this quick sort before you assume anything:

What you hear	What it tracks	Likely source
High-pitched zing/buzz, pitch changes with frame rate (spikes in menus, shifts when you alt-tab)	Electrical load	Coil whine
Whoosh or hum that rises smoothly with load	Fan RPM / temperature	A cooling fan
Grinding, rattling, or clicking	Worn bearing	A failing fan — see the fan-bearing test
Gurgling or bubbling	Coolant/air in the loop	AIO pump
Sharp crackle or pop, maybe a burning smell	Arcing — danger	Power off and unplug now

The single most reliable tell: does the pitch change when the frame rate changes? Open a game menu (frame rates there are often absurdly high — hundreds or thousands of fps with nothing to render), then load into the game. If the whine spikes in the menu and settles in-game, or shifts when you alt-tab and scroll, it’s coil whine. If instead the noise climbs with temperature and fan speed, you’re chasing a fan, not a coil — and a grinding one is a worn bearing you should deal with.

That last row matters most. Coil whine is harmless, but a crackle-pop with a burning smell is arcing electricity, and that’s the one PC noise you never wait out.

Step 2: Where is it coming from — GPU, PSU, or motherboard?

In a desktop, coil whine nearly always comes from one of three places, in this order of likelihood: the GPU, then the PSU, then the motherboard’s VRM. Knowing which one changes what you do about it — and which component you’d swap.

Use load type to narrow it down:

GPU — tracks frame rate and GPU load. It’s loudest in high-fps scenes, menus, and loading screens. This is by far the most common source, especially on modern high-wattage cards.
PSU — tracks total system power draw. It tends to show up under heavy combined CPU-and-GPU load, or at particular power states, rather than following your frame counter specifically.
Motherboard VRM — rarest, comes from around the CPU socket, and follows CPU load and voltage transitions.

The fastest GPU test: set your monitor to 60 Hz and turn on V-Sync, or cap your FPS in the driver. If the whine drops or vanishes, it’s frame-rate-driven and the GPU is your culprit. That one test resolves the majority of cases — and it looks like this:

The one test that settles it

Same card, two states. Cap the frame rate and listen. If the zing follows the FPS down, it's the GPU — and it's the harmless kind.

BEFORE · UNCAPPED

900 fps

in a menu with nothing to render

))) ZZZINNNG )))

The card thrashes its power delivery for frames you'll never see. Loudest whine.

SET 60 Hz
+ V-SYNC

→

AFTER · CAPPED

60 fps

matched to your refresh rate

· · · quiet · · ·

Whine drops or vanishes → it's the GPU, frame-rate-driven, harmless.

If the noise ignores the cap and tracks total power draw instead, it's not frame-rate-driven — look at the PSU. techfuelhq.com

To localize it physically, roll a sheet of A4 paper into a tube (or use a paper-towel roll), hold one end to your ear, and point the other at each component in turn — GPU, then PSU, then the VRM area above the CPU socket. The tube blocks surrounding noise and helps you home in. One big caveat: the coils sit on a circuit board, and the board acts like a speaker cone — so the whine resonates through the whole case and can genuinely sound like it’s coming from the wrong place. Don’t fully trust your ears; confirm with the load-type behavior above.

When you truly can’t tell, the definitive method is swapping. Start with the GPU (easiest and most likely) — drop in another card and see if the noise goes with it. If it persists, try a different PSU. The motherboard is the last and hardest swap, so it’s a diagnosis of exclusion: if the whine survives both a GPU and PSU swap, the board’s VRM is what’s singing.

On a laptop, the rules bend a little. You can’t swap the GPU or PSU, so localization matters less — but laptops have one tell desktops don’t: the whine often changes when you plug or unplug the charger. Because the charging circuit and the discharge-from-battery path deliver power differently, a laptop can whine only on AC, only on battery, or shift pitch between the two. If yours does that, it’s classic coil whine from the power delivery, not a fault. The fixes are the same load-smoothing ones — cap the frame rate first, then undervolt with your vendor’s utility (or a global FPS limit) — and since you can’t swap parts, the retailer return window is your main lever if it’s truly intolerable.

Step 3: Is it normal, or the one warning sign?

Here’s the reassuring part, and it’s well established: coil whine does not damage your hardware. It doesn’t hurt performance, it doesn’t shorten the component’s lifespan, and it isn’t a symptom of anything failing. It’s a physical quirk of how inductors behave under fluctuating current — annoying, harmless, and extremely common on powerful modern GPUs. If you’ve confirmed steady GPU coil whine that’s always been there and tracks your frame rate, you can genuinely stop worrying about the hardware and decide purely on how much the noise bothers you.

The exceptions are specific and worth memorizing:

New or worsening PSU buzz paired with crashes. Occasional light coil whine from a power supply is normal, but a buzz that’s new, getting louder, and accompanied by random shutdowns, BSODs, or instability under load can be a power supply on its way out — not benign coil whine. That combination is worth taking seriously: the signs of a failing PSU walk through how to confirm it’s the power supply and not a dying GPU or bad RAM.
A sharp crackle, pop, or sizzle — especially with a burning or electrical smell. This is not coil whine. It’s arcing or a component letting go. Shut the PC off and unplug it from the wall immediately; don’t power it back on to “check.”

Everything else — the steady zing that rises with your frame counter — is the harmless kind. The question becomes how to quiet it, not whether to panic.

Step 4: How to actually reduce it (and what to never do)

The fixes that genuinely work all do the same thing: reduce or smooth the electrical load hitting the coils. In rough order of effort-to-payoff:

Cap your frame rate. This is the big one. Uncapped frame rates — 900 fps in a menu, 400 in an old game — are the most common trigger, because the card is thrashing its power delivery to render frames you’ll never see. Turn on V-Sync, enable G-Sync/FreeSync, or set an FPS limit in the NVIDIA or AMD driver to match your monitor. Many people’s whine disappears entirely right here.
Undervolt the GPU. In MSI Afterburner (works on any brand), flatten the voltage/frequency curve so the card holds its clocks at a lower voltage. Less voltage means less current through the inductors and often less whine — and it lowers temperatures with little or no performance loss as a bonus. It’s the same trick that helps with GPU overheating, so it’s worth learning either way.
Consider the power supply. A cheap or aging PSU with sloppy voltage regulation can feed “dirty” power that makes whine worse across the whole system. A quality unit with tight regulation can help — though this is a bigger spend, so try the free fixes first.
Mechanical damping, carefully. Moving the PC further from your ears, closing a mesh case panel, or standing the tower on a soft surface can mask the sound. Some enthusiasts very carefully add non-conductive damping — but this is fiddly and easy to get wrong.

What to never do: do not apply superglue, hot glue, or nail polish directly to the coils. It’s a widely repeated bad tip — those adhesives wick under surrounding components, trap heat against parts designed to shed it, make any future repair impossible, and void the warranty; and anything actually conductive risks a dead short on top of that. BIOS clock tweaks by themselves also won’t touch coil whine — it’s a hardware characteristic, not a software setting (undervolting works because it changes power draw, not because it’s a “setting”).

The RMA reality

Almost every manufacturer treats coil whine as a normal characteristic, not a defect — so a warranty RMA for coil whine alone usually gets rejected. Your real lever is the retailer’s return window. Because whine varies from unit to unit even within the same exact model, swapping a whiny card for another copy inside a no-questions-asked return period (Amazon, Best Buy, Micro Center) is a legitimate gamble — the next one may be dead silent. Outside that window, a warranty claim generally only lands if the whine comes bundled with a real fault like crashing or artifacting. If you’re on a brand-new part and the whine is mild, it’s also reasonable to just live with it for a few weeks first — sometimes it settles down on its own.

The quick version

Confirm it’s coil whine, not a fan or arcing. Coil whine’s pitch changes with frame rate; fan noise tracks temperature and RPM (grinding = worn bearing); a crackle-pop with a burning smell is arcing — power off now.
Find the source by load type. Follows FPS → GPU (set 60 Hz + V-Sync to confirm). Follows total power draw → PSU. Around the CPU socket, follows CPU load → motherboard VRM. Use a paper tube to localize, but remember the case resonates.
Decide if it matters. Steady GPU whine that tracks frame rate is harmless — it won’t damage anything. New PSU buzz with crashes is a different story: check for PSU failure.
Reduce it the right way. Cap FPS (V-Sync/G-Sync/FreeSync), undervolt in Afterburner, quality PSU. Never glue the coils. RMA rarely works for whine alone — use the retailer’s return window and roll the dice on another unit.

Sort is it coil whine and where from before you do anything, and you’ll stop returning cards that were fine — and stop tuning out a power supply that was actually trying to warn you.

CPU Fan Not Spinning? Boot vs 'CPU Fan Error' Splits the Fix (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

A still CPU fan sets off two opposite reactions: the fan’s dead, my CPU is about to fry — or relax, that’s just a silent fan profile, it’s fine. Both happen, and picking the wrong one is expensive either way. Panic and you replace a perfectly good cooler; shrug it off on a genuinely dead fan and the CPU cooks itself in minutes.

“CPU fan not spinning” is really three different problems wearing the same description, and almost every guide skips the one question that tells them apart. Answer it first and the rest of the fix falls out.

Step 1: Does the PC boot, or stop on a “CPU Fan Error”?

Before you open the case, notice how far the PC gets. This single observation splits the whole problem into three lanes:

It halts at a “CPU Fan Error” / “CPU Fan Speed Error — press F1” and won’t continue. This is the most common real trigger, and it’s almost never a dead motor. The motherboard is running a safety check and refusing to boot — jump to Step 2.
It boots all the way into Windows but the fan sits still. Now it’s either a normal fan-stop profile or a fan that’s quietly died. Step 3 and Step 4 sort those.
The fan only starts when you nudge it with a finger (or a cable tie at boot). That’s a bearing on its way out — Step 4.

Notice what isn’t here: if the fan is off and you get no picture at all, that’s usually not a fan problem — the system isn’t POSTing, and the cause is more often power or a seating issue. That case has its own walk-through in PC turns on but no display.

Step 2: The “CPU Fan Error” — what it actually checks

Here’s the part the checklists get wrong: the motherboard isn’t checking whether your fan spins. It’s checking for an RPM signal on the header labeled CPU_FAN, and if it reads zero at boot it stops and throws the error. That safety feature exists so nobody powers on a CPU with no cooling attached. But it fires on several setups where the cooling is working perfectly:

The fan is on the wrong header. CPU cooler fans must go on CPU_FAN, not SYS_FAN / CHA_FAN (case-fan headers). The board sees CPU_FAN empty and panics even though your fan is spinning happily on a case header.
A very quiet fan spins below the alarm threshold. Low-noise fans (Noctua, be quiet!, and similar) can idle under ~300 RPM — below the minimum the board watches for — so it reports “no fan” despite the blades turning.
An AIO pump is plugged into CPU_FAN and reports 0 RPM by design (more on that in Step 3).

Fix, in order:

Power down and confirm the CPU cooler’s fan cable is seated on the CPU_FAN header specifically, pushed in until it clicks.
Reboot into BIOS/UEFI and open the fan section (ASUS Q-Fan Configuration, MSI Hardware Monitor, Gigabyte Smart Fan). Read the live CPU fan RPM. If it shows a real number, the fan is fine and the alarm threshold is just set too high.
Lower the “CPU Fan Speed Low Limit” to around 200 RPM, or — if and only if you’ve physically confirmed the fan or pump is running — set CPU_FAN monitoring to “Ignore.”

That last step carries a real warning: never set it to Ignore to make an error go away on a cooler you haven’t verified. The alarm is the only thing standing between a genuinely dead fan and a thermal-shutdown loop. Silence it only once you’ve seen the fan turn or the pump move coolant.

Step 3: The AIO trap — pump header vs fan header

Liquid coolers cause more false “dead fan” scares than anything else, because an AIO has two things to plug in and they don’t behave the same.

The pump should go on the AIO_PUMP (or W_PUMP) header, which runs it at full, constant power so coolant always flows.
The radiator fans go on CPU_FAN (and CPU_OPT for the second fan).

Two things follow from that. First, if your board has an AIO_PUMP header and the pump is on it, then CPU_FAN is driving the radiator fans — and if those fans are on a quiet “fan stop” curve, they legitimately sit still at idle and only spin up when the coolant warms. That’s a working AIO, not a broken one. Second, if you plugged the pump into CPU_FAN (common on boards with no dedicated pump header — and perfectly valid), the pump can report 0 RPM or wildly inconsistent values even while it’s pumping fine, which trips the same CPU Fan Error from Step 2.

The tell for a healthy-but-quiet AIO: the tubes and radiator warm up under load, and the fans engage as the temperature climbs. If the pump is on CPU_FAN and you’re chasing a phantom error, move the pump to AIO_PUMP (if the board has one) and put the radiator fans on CPU_FAN so the board watches an actual fan. A dead pump is the real emergency here — feel for coolant movement or a faint pump vibration, because a stopped pump overheats the CPU in seconds no matter what the fans do. When idle silence turns into a genuine thermal problem, work through CPU overheating next.

Step 4: Is the fan actually dead? Three checks

If the PC boots and a normal always-on air cooler fan is sitting still — or a fan only turns when nudged — treat it as a hardware fault and confirm it:

Spin it by hand (PC fully off). Gently flick the blades. A healthy fan coasts freely for a moment; a failing one is stiff, grinds, or won’t turn — that stiff-to-the-finger feel is the single most reliable sign the bearing is gone. This is exactly the diagnostic Tom’s Hardware regulars point to first.
Move the header. Plug the fan into a different fan header, or plug a known-good fan into CPU_FAN. If a good fan spins on that header and the suspect fan stays dead everywhere, the fan is the problem, not the board.
Read the RPM in BIOS. A fan that’s stiff by hand and reads 0 RPM on a header that drives other fans fine is confirmed dead.

Air coolers are the clear case: they don’t have a zero-RPM idle mode, so a still air-cooler fan is a real fault, full stop. Fan-stop profiles only apply to some AIO radiator fans and a few case setups. If you’re diagnosing the graphics card’s fans instead of the CPU cooler’s, that’s a different animal with its own idle behavior — see GPU fans not spinning.

Step 5: If it’s dead, replace it — don’t run it

A CPU with no working cooler fan is not something to limp along on. Unlike a GPU, which can idle safely with its fans off, a CPU heat-soaks almost instantly under load, throttles hard, and slams into thermal shutdown to save itself — and repeated overheating shortens its life. If the fan is confirmed dead, stop demanding work of the PC until it’s fixed.

Your options depend on the cooler. If it’s a standard tower cooler with a common 120 mm or 92 mm fan, you can usually just replace the fan (a 120 mm PWM cooling fan is inexpensive and clips onto the existing heatsink). If the whole cooler is old, weak, or it’s a failed AIO pump, replace the CPU cooler outright — an air tower with an always-on fan is the simplest, most reliable fix and removes the pump as a future failure point. Either way, re-seat with fresh thermal paste and confirm the new fan reads a real RPM in BIOS before you trust it.

If the CPU had already been running hot before the fan quit, don’t assume shutting it down undid the damage — read CPU overheating to confirm temps are back in a safe range, and if the machine had started power-cycling under the heat, PC keeps restarting covers the thermal-shutdown loop.

The bottom line

The fastest way to fix a still CPU fan is to stop treating “not spinning” as one problem. How far the PC boots tells you which of three it is: a “CPU Fan Error” halt is almost always a header or RPM-threshold issue, not a dead motor; a fan that idles on an AIO’s quiet profile is usually a working cooler; and only a stiff, silent fan on an always-on air cooler is the genuine hardware failure. Sort that first, confirm with the spin-by-hand and BIOS-RPM checks, and you’ll either clear a phantom error in two minutes or replace a $12 fan instead of a $200 CPU.

GPU Artifacts? Sort Software vs Dying VRAM Before You RMA (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~11 min read · St. Louis County, MO

The screen fills with colored lines, snow, or textures stretching into garbage, and the top of every search result says the same two things: it’s dying, RMA it — or just reinstall your drivers. Both are sometimes right. But “GPU artifacting” is really a handful of very different problems wearing one ugly symptom, and if you reach for the wrong one you’ll either bin a card that a five-minute fix would have saved, or keep reinstalling drivers on a card that’s physically failing.

Two questions sort almost the entire thing before you touch a setting: does the glitch show up in a screenshot, and does it stop when you back off the clocks? Answer those and you’ve already thrown out most of the advice on the internet.

But first, the question people actually type into the search bar: what am I even looking at? Artifacts come in a handful of recognizable shapes, and the shape tells you which lane to start in — the cable, the driver, the heat, a rendering setting, or the silicon itself. Here’s the field guide.

What kind of artifact are you seeing?

Seven shapes, and the colored tag on each says which lane to start in. The look narrows it; the two tests — does it capture, does backing off the clocks stop it — tell you for sure.

Colored lines & streaks

Bright bars darting across the screen.

START: DISPLAY PATH

Snow & colored dots

Scattered speckle, like TV static.

START: HARDWARE

Blocky pixelation

Mismatched corrupted chunks.

START: HARDWARE

Garbled textures

Stretched, smeared surfaces.

START: SOFTWARE

Misshapen polygons

Triangles shooting off geometry.

START: HARDWARE

Color-shift tint

Whole screen the wrong hue.

START: DISPLAY PATH

Ghosting / afterimages

Trails behind moving objects.

NOT A FAULT

■ SOFTWARE = free fix
■ RENDER FEATURE = not a fault
■ DISPLAY PATH = cable / monitor
■ HARDWARE = the card itself

“Start” is where the odds point, not a verdict — heat can trigger any of these, but only under load. If the glitch vanishes when the card idles and cools, it’s thermal, not the look. techfuelhq.com

Step 1: The 60-second test — is it even the GPU?

Artifacts you see on the monitor can be born in two completely different places: on the render side (the GPU rendered a broken frame) or on the display path (the GPU rendered a fine frame and it got corrupted on the way to the panel). One test splits them.

Take a screenshot while the artifacts are on screen — or better, record a couple of minutes with OBS Studio — then open the file on your phone or another PC. Screen capture grabs the frame before it leaves the graphics card:

What the capture shows	Where the problem lives	Where to go
Artifacts appear in the screenshot/recording, same as on screen	Render side — GPU, VRAM, driver, or game	Steps 2–5
Capture is clean; only the monitor looks glitchy	Display path — cable, port/adapter, refresh rate, or monitor	Step 6

A clean capture with a glitchy screen is a good result — it usually means a bad DisplayPort/HDMI cable, a flaky adapter, an over-aggressive refresh rate, or a failing monitor, none of which require a new graphics card. If the glitch is specifically lines rather than sparkles or blocks, our guide on lines on a monitor — cable, GPU, or dying panel has the one-button OSD test that isolates the display side in under a minute. (Some VRAM faults won’t always capture, so a clean shot isn’t an absolute guarantee — but a captured artifact almost always means the card.)

Then note where the artifacts appear, because that narrows it further:

Only in one game → most likely that game’s engine or a corrupted shader cache, not your hardware.
In every game, but the desktop is clean → driver, heat, overclock, or VRAM under load.
At the Windows desktop, or even in the BIOS/UEFI screen → this is the serious one. Desktop-level artifacting that isn’t tied to a 3D load points hard at failing hardware.

The 2026 curveball: ghosting and afterimages that aren’t a dying card

Before you walk the hardware ladder, rule out the “artifact” that panics the most people in 2026 and almost never means a failing card: ghosting — faint trailing afterimages or smears behind moving objects, lights, and highlights. This is usually not your GPU at all. It’s a side effect of how modern games render, and it’s the single most common “is my card cooked?” false alarm on r/pcmasterrace and r/nvidia right now.

Three rendering features blend information across frames, and that blending is exactly what you see trailing:

DLSS / FSR upscaling. The game renders at a lower resolution and reconstructs the rest; ghosting gets worse the more aggressive the preset (Performance trails more than Quality) and at lower output resolutions.
Frame Generation. Inserted frames can smear on fast motion and around the HUD — the more frames it’s generating, the more visible.
TAA (temporal anti-aliasing). It blends and jitters frames to smooth jagged edges, and that blend smears during fast movement. It leans on frame data, so it looks worse at 1080p than at 1440p and up.

The tell is dead simple, and it follows the same Step-1 logic: the trailing appears only in games with these features on, and vanishes the moment you switch to DLAA or native resolution, raise the DLSS preset, or turn Frame Generation off. If your game supports it, DLAA gives you NVIDIA’s anti-aliasing without the upscaling and usually kills the ghosting outright.

One lookalike is not render-side: monitor overdrive set too high also trails. The screenshot test separates them — render-side ghosting shows up in a screen recording, but overdrive ghosting does not (it happens on the panel, after the frame has already left the card), so it only appears when you point a phone camera at the screen. Drop the monitor’s overdrive / response-time setting a notch and it’s gone. Either way, none of this is a dying GPU: real VRAM or die failure looks like the lines, blocks, snow, and broken geometry in the gallery above, not soft motion trails.

Step 2: Rule out software first — it’s free

Before you spend a cent, clear the causes that cost nothing. In order:

Reset any overclock. If you’ve touched core clock, memory clock, or voltage in MSI Afterburner or your card’s software, set everything back to default (or hit the reset button). An unstable overclock is one of the most common artifact sources, and it’s invisible until you undo it. If the artifacts vanish at stock, that was your answer.

Do a clean driver reinstall with DDU. A corrupted or half-installed driver produces artifacts that look exactly like hardware failure. Download the latest driver from NVIDIA, AMD, or Intel first, then run Display Driver Uninstaller (DDU) in Windows Safe Mode to wipe the old driver completely, reboot, and install clean. This single step resolves a large share of “sudden” artifacting.

Clear the shader cache if it’s one specific game. Delete the game’s shader cache (Steam: right-click the game → Properties → Installed Files, or clear the driver’s cache in the NVIDIA/AMD control panel). A broken cache renders corrupted geometry in one title while everything else is fine.

If artifacts survive all three, the odds swing toward hardware — but there are still two free things to check before you write the card off.

Step 3: Check the temperature

Install HWiNFO and watch the GPU temperatures (and the separate memory junction / VRAM temp on cards that report it) while the artifacts appear. If the card is running hot and the glitches show up under load but vanish when it idles and cools, you’re looking at thermal-driven artifacting, not dead silicon. Not sure whether your card is actually running hot or just showing normal load temps? Check core vs hotspot first — see Is Your GPU Really Overheating?

The fixes are physical and cheap: blow the dust out of the heatsink and fans with a can of compressed air, confirm every fan actually spins (if one is dead or none spin under load, see GPU Fans Not Spinning), and improve case airflow. On an older card whose thermal paste has dried out, a thermal paste repaste (and fresh thermal pads on the VRAM/VRM) can drop temperatures 10–20 °C and stop heat-triggered artifacts entirely.

Step 4: Test the VRAM and confirm hardware

If it’s cool, at stock, freshly re-drivered, and still artifacting, it’s time to prove whether the memory or core is failing. There are two tools:

The underclock test. In MSI Afterburner, lower the memory clock by 100–300 MHz (and, if needed, the core by about 50 MHz), apply, and retest. If the artifacts stop at the reduced clock, the hardware can no longer hold its rated speed — that’s degrading VRAM or an unstable die. A modest undervolt/underclock can genuinely keep a fading card usable for months by cutting heat and electrical stress, but understand what it means: the card is on a downward path.

A stress test. Run OCCT (it has a dedicated VRAM test) or FurMark for a short session and watch closely. Stop immediately if temperatures spike fast, the screen goes black, the PC crashes, or the artifacting intensifies instead of settling — those are all signs of real instability, and there’s no benefit to cooking a failing card.

Two patterns confirm a hardware fault rather than a setting: artifacts that reproduce across multiple games, and artifacts that follow the card across different monitors and cables. When corruption shows up everywhere with no software trigger and survives a clean driver reinstall, the usual culprits are failing VRAM, a destabilizing GPU die, damaged board components (ceramic caps, memory-power circuitry), or a power-delivery fault on the card.

Step 5: The physical causes people skip

Before you accept “dead,” check the mechanical stuff that repair techs see constantly — none of it shows up in software:

Power-connector trouble. A PCIe or 12VHPWR / 12V-2×6 connector that isn’t fully seated, or one running through thin-gauge daisy-chained PSU wiring, can overheat and feed the card dirty or insufficient power — which shows up as artifacts and instability under load. Unplug and firmly re-seat every power cable at both ends, and look (and smell) for any browning or melting on the connector. A weak or aging power supply can also mimic a dying GPU.
Card sag and board flex. Heavy modern multi-slot cards slowly bend under their own weight, and that flex stresses the solder joints under the GPU and memory chips over years. A cheap GPU support bracket removes that stress and is worth fitting on any large card as prevention.
Cracked solder joints (BGA). The “dying” that people describe is often a cold or cracked BGA solder joint under the die, caused by years of heat cycling — heavy load to idle, over and over. That’s what a repair specialist actually fixes.

On a laptop, the playbook shrinks. You usually can’t reseat the GPU, repaste easily, or touch the core clock, and the dGPU is soldered to the board — so your real moves are the free ones (reset any overclock utility, clean-reinstall the driver, clear the shader cache, and blow the dust out of the vents) plus one hardware check: plug in an external monitor. If the artifacts show on the external screen too, it’s the laptop’s GPU or its memory; if the external screen is clean, the built-in panel or its ribbon cable is the fault, not the graphics chip. A soldered mobile GPU that artifacts across displays after a clean driver reinstall is usually a warranty/RMA or board-repair case, not a home fix.

Step 6: When it’s the display path (clean capture)

If your Step-1 capture came back clean, the GPU is rendering fine — chase the connection instead. Swap the video cable for a known-good one (cheap cables and worn connectors are a top cause), try a different port on the card and a different input on the monitor, drop the refresh rate to a standard value in case the current mode is out of the panel’s stable range, and test a second monitor entirely. If a different screen and cable are clean, the original monitor is the fault. This is a much happier outcome than a dead card — see Monitor Keeps Going Black? for the full display-side walk-through.

When it’s genuinely dying — RMA or repair

You’ve reset the clocks, reinstalled drivers clean, ruled out heat, re-seated power, and the card still throws artifacts at the desktop across multiple monitors. At that point it’s a hardware failure, and the path depends on warranty:

Under warranty → RMA it. That’s almost always the right call; the manufacturer replaces or repairs it and you’re not gambling on a fix.
Out of warranty → weigh repair vs replace. A GPU repair specialist can sometimes reflow or reball the core/VRAM to fix a cracked joint, but component-level work often costs more than a mid-range card is worth. If you’re replacing, match a current graphics card to your power supply and case, and if your testing implicated the PSU, fix that too — a failing power supply will happily kill the replacement card as well.

Before you spend anything, be sure: confirm the artifacts follow the card into a second PC. A failing PSU or a bad cable can frame a perfectly good GPU, and the whole point of the tests above is to make sure you only retire a card that’s actually done.

The elimination funnel

Assuming the glitch showed up in your screenshot (render-side). Each check you pass crosses suspects off until one is left. A clean screenshot instead? Skip straight to the display-path branch — it’s the cable or monitor, not the card.

Cable / Monitor Render feature Shader cache Overclock Driver Heat Power / Sag VRAM / die

Screenshot captures the glitch — it’s render-side, so it’s not the ~~Cable / Monitor~~.

7 left

Still there with DLSS / TAA / Frame-Gen off? Yes — rule out the ~~Render feature~~ (ghosting).

6 left

Happens across many games, not one? Then it isn’t the ~~Shader cache~~ / a single-game bug.

5 left

Reset overclock + clean DDU driver — no change, so cross off ~~Overclock~~ and ~~Driver~~.

3 left

Cool at idle in HWiNFO? Temps fine — it isn’t ~~Heat~~.

2 left

Re-seat power, fit an anti-sag bracket — still glitching, so it isn’t ~~Power / Sag~~.

1 left

LEFT STANDING · VRAM / GPU DIE

Confirm it with a −100–300 MHz memory underclock — if that stops the artifacts, the silicon can’t hold its rated speed. Then RMA (in warranty) or weigh a reflow / replacement, after proving the card is dead in a second PC.

Work top-down: every free check you pass shrinks the list, so you only reach for a screwdriver — or a credit card — once the cheap causes are gone. techfuelhq.com

The quick version

Screenshot or record the artifacts. In the capture → it’s the card (Steps 2–5). Clean capture → it’s the cable/monitor (Step 6).
Trails or afterimages? If it only happens with DLSS/TAA/Frame-Gen on and stops when you switch to DLAA/native or turn Frame Gen off, it’s a rendering feature, not a dying card.
Where does it show? One game = shader cache; every game = driver/heat/OC/VRAM; desktop or BIOS = hardware.
Do the free software pass: reset the overclock, clean-reinstall the driver with DDU, clear the shader cache.
Check heat (HWiNFO) — dust, fans, and a repaste fix thermal artifacts.
Confirm hardware: a −100–300 MHz memory underclock that stops the artifacts means degrading silicon; OCCT/FurMark and cross-testing on other games, monitors, and cables confirm a real fault.
Then, and only then, RMA (in warranty) or weigh a reflow/replacement — after proving the card is dead in a second machine.

Find out whether it’s software, the display path, or dying hardware first, and you stop reinstalling drivers on a card that never had a driver problem — and you stop throwing away cards a reset overclock would have fixed. For the driver side of this in depth, see Fix GPU Driver Crashes; if the card isn’t showing up at all rather than glitching, that’s a different branch covered in Graphics Card Not Detected.

GPU Fans Not Spinning? Check Idle vs Load Before You Panic (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

You glance at your open case, the GPU fans are dead still, and the internet immediately splits into two camps: your card is failing, RMA it — or it’s fine, that’s normal, ignore it. Both are sometimes right, and that’s exactly the problem. “GPU fans not spinning” describes three completely different situations, and the fix — or the relief — depends entirely on which one you actually have.

The good news is that for most people asking this question, nothing is wrong. Modern graphics cards stop their fans on purpose. The trick is knowing how to tell that normal, healthy silence apart from a genuinely dead fan, and to spot the one case where fans-not-spinning isn’t a fan issue at all.

Step 1: Idle or under load? This one check sorts everything

Before you touch a screwdriver, answer a single question: are the fans off because the card is cool, or off despite the card being hot?

Since about 2016, nearly every mid-range and higher graphics card ships with a zero-RPM idle feature. You’ll see it under a different brand name depending on who made your card:

Maker	Feature name
MSI	Zero Frozr
ASUS	0dB Fan
Gigabyte	Fan Stop
NVIDIA / AMD (reference)	Idle Fan Stop / Zero RPM mode

They all do the same thing: below roughly 50-60 °C, the aluminum heatsink alone sheds enough heat that the fans aren’t needed, so the card shuts them off to run completely silent. A GPU sitting on the Windows desktop, browsing, or playing video is usually well under that threshold — so fans-off at idle is the card working exactly as designed, not a failure.

To confirm it in 60 seconds, install HWiNFO (free) and watch the GPU temperature, then load something demanding — a game, or a quick FurMark or OCCT run:

Fans start once the temp crosses ~55-60 °C → everything is fine. You were looking at zero-RPM idle. You’re done.
Temp climbs past ~65-70 °C and the fans still haven’t moved → the auto curve isn’t triggering them. Now it’s a real fault — continue to Step 2.
No picture on screen at all, fans dead from the moment you power on → this usually isn’t a fan problem. Jump to Step 4.

That fork is the whole game. Most searches for this end right here at the first bullet.

Step 2: Fans stay off under load — the real fixes, in order

If the card is genuinely hot and the fans refuse to spin, work these from easiest to hardest. Roughly this is also their hit-rate order.

1. Override the fan curve in software. Open MSI Afterburner (it works on any brand), enable manual fan control, and set a fixed 60-70% speed. If the fans jump to life on command, the hardware is fine and the problem was a stuck auto curve, a disabled setting, or a software conflict — set a sensible custom curve with a low floor and you’re done. If they don’t respond to a direct manual command, the issue is physical; keep going.

2. Re-seat the fan power cable. On most cards the fan assembly connects to the PCB through a small internal header, and it can work loose — especially after shipping, a move, or a recent reinstall. Power down, pull the card, and check that little fan connector is fully clicked in. While the card is out, blow the dust out of the heatsink and fans with a can of compressed air; a packed heatsink can also trip thermal weirdness.

3. Re-seat the card and its PCIe power. Press the card firmly back into the x16 slot until the retention clip clicks, and unplug then firmly re-seat every PCIe power cable at both ends. A card that isn’t getting clean, sufficient power can behave erratically, fans included.

4. Clean-reinstall the driver. A corrupted driver or a bad VBIOS/software profile can leave the fan controller in a bad state. Download the latest driver from NVIDIA or AMD, run Display Driver Uninstaller (DDU) in Safe Mode to wipe the old one, reboot, and install clean. This is also the fix when the fans quit right after a driver update reset your curve.

If the fans still won’t move under load after all four, the fan or its motor is the problem — Step 3.

Step 3: Dead or dying fan — how to be sure, and what to do

A fan that’s mechanically failed gives itself away. With the PC fully powered off, gently flick each fan blade with a finger:

Spins freely and coasts → the fan is healthy; your problem was one of the Step-2 causes.
Stiff, grinding, or won’t turn → the bearing is worn or seized. This is the textbook cause when one of two or three fans is dead while the others spin — zero-RPM stops all of them together, so a single stationary fan is a hardware fault, not a setting.

A grinding, rattling, or clicking noise in the weeks before a fan stops is the classic worn-bearing warning. (Don’t confuse that mechanical grind with a high-pitched electronic zing that changes with your frame rate — that’s coil whine, a harmless electrical noise, not a dying fan.) For an older card, a worn sleeve bearing that’s lost its lubricant can sometimes be revived with one or two drops of light machine oil (sewing-machine oil is ideal) under the center sticker — never WD-40, which is a solvent that will make it worse over time. That’s a stopgap, not a repair.

The durable fix is a fresh fan. Replacement GPU fan kits for common cards are usually $10-25 and are a straightforward swap if you’re comfortable removing the shroud and matching the connector type and blade count. If the card is still under warranty, don’t open it — RMA it instead; opening the shroud can void coverage.

Step 4: Fans off and no display — this isn’t a fan problem

If the fans are dead from the second you hit the power button and you get no picture at all, stop troubleshooting the fans. Spinning fans only ever prove a card is getting some standby power; the reverse — dead fans with no display — almost always means the GPU isn’t initializing (POSTing) in the first place. The usual culprits are:

A PCIe power connector not fully seated — extremely common with the 12VHPWR / 16-pin plug on RTX 40- and 50-series cards, which needs to click all the way home.
The card not fully pressed into the slot.
The monitor plugged into the motherboard instead of the graphics card’s own ports.
A power supply that’s too weak or failing under load.

Re-seat the card until the clip clicks, re-seat every power cable firmly at both ends, and confirm the monitor cable is on the card, not the motherboard. Because this is a different branch entirely, it has its own full walk-through: Graphics Card Not Detected? Find Where It Disappears First.

When to worry — and when not to

Put simply: fans-off is only an emergency when the card is hot. A GPU that idles silent and spins up under load is one of the best-behaved things in your PC. A GPU that bakes past 80 °C while its fans sit dead will throttle, then crash, then eventually protect itself with a thermal shutdown — and running it that way repeatedly shortens its life. If you’ve confirmed a genuinely dead fan, don’t game on the card until it’s fixed; low-load desktop use is fine while you wait on a replacement. (The CPU cooler is the opposite case — it has no safe zero-RPM idle, so a still CPU fan is far more urgent: CPU fan not spinning covers that one.)

And if the fans turn out to be healthy but the card is still misbehaving — glitches, crashes, black screens — the fan was a red herring and the real fault is elsewhere. Overheating that survives working fans, or visual corruption, points at a different problem: see GPU Artifacts? Sort Software vs Dying VRAM and Fix GPU Driver Crashes.

The quick version

Check idle vs load first. Watch the temp in HWiNFO and load a game or stress test. Fans start by ~55-60 °C = normal zero-RPM mode, nothing’s wrong.
Fans off while hot (65 °C+)? That’s a real fault. Force them in MSI Afterburner; if they respond, it was the curve/software. If not, re-seat the fan cable, re-seat the card + PCIe power, and clean-reinstall the driver with DDU.
Spin each fan by hand (PC off). Stiff or grinding = worn bearing; a single dead fan among spinning ones is hardware, not a setting. Light oil is a stopgap; a $10-25 replacement fan is the fix (RMA instead if in warranty).
Fans dead and no display? Not a fan issue — the card isn’t POSTing. Re-seat card and power, check the 12VHPWR plug, move the monitor to the card’s port.

Sort which of those you actually have before you spend a cent, and you’ll stop RMAing cards that were working perfectly — and stop ignoring a genuinely cooked one because “that’s just zero-RPM mode.”

GPU Overheating? Confirm It Actually Is Before You Fix Anything (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

You saw a number — 80 °C, 90 °C, a scary-looking hotspot reading — and now you’re convinced your graphics card is cooking itself. Maybe it is. But here’s the thing almost every “fix GPU overheating” guide skips: most cards that get flagged as overheating are running exactly the way their engineers designed them to. A GPU is not a CPU, and the temperatures that would alarm you on a processor are routine on a graphics card.

So before you buy compressed air, tear off the shroud, or RMA anything, spend two minutes confirming the card is actually too hot — and, if it is, reading the one number that tells you whether it’s dust or dried-out paste. That single distinction decides whether this is a five-minute clean or a repaste job.

Step 1: Is it even overheating? Read core vs hotspot first

Install HWiNFO (free) or GPU-Z, load a game or a short FurMark run, and look at two numbers: GPU (core) temperature and GPU hotspot / junction temperature. Here’s what’s actually normal in 2026:

Reading	NVIDIA RTX 40/50	AMD RX 7000/9000
Idle (desktop)	~30-50 °C	~30-50 °C
Normal gaming (core)	65-85 °C	65-85 °C
Throttle point (core)	~83-85 °C	~90-95 °C
Hotspot above core (healthy)	10-15 °C	20-35 °C (by design)
Max spec	~90 °C core (hotspot throttles ~105 °C)	110 °C junction

Note for RTX 50-series owners: the hotspot column doesn’t apply to you — NVIDIA removed public hotspot access on Blackwell (see below), so your tools will only show core and memory.

Read that table before you do anything else, because it kills the most common false alarm outright:

Core in the 70s or low 80s under load? That’s a healthy card. Stop worrying. This is where the majority of “my GPU is overheating” searches actually end.
AMD hotspot showing 95-105 °C while the core sits around 70 °C? Also normal. AMD deliberately lets the junction run hot — a 100 °C hotspot next to a 70 °C core is the card working as designed, not a fault. The 110 °C number that looks terrifying if you’re used to NVIDIA is simply a different thermal philosophy.
Core pinned at 85 °C+ (NVIDIA) or 95 °C+ (AMD) and clocks dropping? Now it’s genuinely too hot and throttling. Continue to Step 2.

If you’ve got GDDR6X memory (RTX 3080/3090/4070 Ti/4080/4090 and similar), HWiNFO also reports a memory junction temperature. That’s rated to 110 °C but is happiest under about 95 °C — worth watching separately on those cards, since hot VRAM is a classic cause of visual artifacts even when the core looks fine.

If you own an RTX 50-series card, your hotspot went dark

Before you go hunting for a hotspot number, know this: on the RTX 50-series (Blackwell), NVIDIA removed public access to the hotspot sensor. GPU-Z, HWiNFO, and MSI Afterburner can no longer read it on a 5070/5080/5090 — the field is simply blank, or it briefly showed a bogus 255 °C before tools stopped reporting it. GPU-Z’s developer confirmed NVIDIA pulled hotspot out of the public API. The sensor still physically exists: Brazilian repair specialists read it with NVIDIA’s internal MODS diagnostic tool and caught an RTX 5070 Ti hitting 107 °C hotspot almost instantly under load while GPU-Z showed only 67-68 °C on the core — a bad factory paste job hiding entirely behind a calm-looking core temperature.

What that means for you if you’re on a 50-series card:

You can’t run the delta check below — there’s no hotspot number to subtract. Skip Step 2 and lean on behavior instead.
Trust throttling over the reading. If your card trims clocks or crashes under load while the core reads a comfortable 70-75 °C, a hidden-hot hotspot (poor paste or an uneven cooler mount) is a live suspect, exactly as on that 5070 Ti.
Watch the memory temperature, which is still reported, and treat repeated load crashes as a reason to check the cooler mount or RMA — not proof that “temps are fine.”

On RTX 50-series, the hotspot reads blank — but it’s still there

NVIDIA pulled the hotspot sensor from the public API on Blackwell. Your monitoring app shows a calm core while the real hottest point can be 40°C higher.

SENSOR STATUS · GPU-Z / HWiNFO on an RTX 5070 Ti

GPU Temperature (Core)
68°C

GPU Memory Junction
74°C

GPU Hot Spot
N/A — removed

Actual hotspot (NVIDIA MODS tool)
107°C

The delta check is out

No hotspot number to subtract. On a 50-series card, skip it.

Trust behavior instead

Throttling or crashes while the core looks cool → suspect a hidden-hot hotspot (paste / mount).

RTX 5070 Ti figures per Tom’s Hardware / VideoCardz coverage of the MODS-tool readings, 2026. techfuelhq.com

Step 2: The hotspot delta — the number nobody tells you to check

This is the diagnostic every “clean your dust” article omits, and it’s the one that saves you from guessing. Take your hotspot temperature minus your core temperature under load:

NVIDIA: delta under ~15 °C = healthy contact. Over ~20 °C = a problem.
AMD: delta under ~25 °C = healthy (AMD runs wider on purpose). Over ~30 °C = a problem.

A delta that’s wider than it should be means heat isn’t moving evenly from the die into the cooler. Dust doesn’t usually do that — dust raises both temperatures together. A wide, growing delta points at the thermal interface itself: thin, dried, or pumped-out thermal paste, or degraded thermal pads. Paste pump-out (the paste slowly getting squeezed out from the center by repeated heat cycling) is extremely common on RTX 30- and 40-series cards after about 18-24 months.

The tell is history: if your delta used to be 10 °C and it’s now 28 °C on the same NVIDIA card, the paste has aged out — and a repaste typically closes the gap by 5-15 °C. If the delta has always been in a healthy range and both temps are just high together, skip ahead — your problem is airflow or dust, not the paste.

The gap that matters: core vs hotspot

Dust raises both temperatures together. A widening gap between core and hotspot is the tell that it’s the paste, not dust — the one number that decides a five-minute clean from a repaste job.

core hotspot

Problem delta: NVIDIA over ~20° · AMD over ~30° (AMD runs wide on purpose). Both temps high together with a normal delta means dust or airflow — not paste. A delta that grew over the years on the same card is the pump-out tell.

Delta thresholds per NVIDIA/AMD sensor behavior; note the delta check needs a readable hotspot (not available on RTX 50-series). techfuelhq.com

Step 3: Fix the real cause, in order

Once you’ve confirmed the card is genuinely too hot, work these from easiest to hardest. This is also roughly their hit-rate order.

1. Clean the dust. A heatsink packed with dust is the single most common real cause of a hot GPU, and it raises core and hotspot together. Power down, open the case, and blow the fins and fans out with a can of compressed air — hold the fan blades still so they don’t spin and generate a charge. Don’t forget the case intake filters, which choke airflow to the whole system.

2. Fix case airflow. A cool GPU needs cool air reaching it. Make sure intake and exhaust fans are working and unobstructed, the PC isn’t buried in an enclosed desk cabinet, and cables aren’t blocking the front intake. Adding one or two case fans for a card that’s starved for airflow often drops temps several degrees for very little money. If a GPU fan has actually stopped, that’s its own problem — see GPU Fans Not Spinning.

3. Set an aggressive fan curve (and cap FPS). Open MSI Afterburner (works on any brand), enable manual fan control, and pull the curve up so the fans ramp earlier and harder. Capping your in-game frame rate — you rarely need 200 FPS — cuts the load the card has to cool. Both are free and instant.

4. Undervolt. The enthusiast favorite: in Afterburner, flatten the voltage/frequency curve so the card hits the same clocks at lower voltage. Done right it cuts load temps meaningfully — often 5-10 °C — with little to no performance loss. Worth learning if temps are borderline and you’d rather not open the card.

5. Repaste and replace pads. This is the fix when Step 2 flagged a wide hotspot delta on an aging card. Fresh thermal paste and correctly-sized replacement pads restore even contact and close the gap. It’s a genuine teardown — if the card is still under warranty, don’t open it; RMA it instead, because removing the shroud can void coverage. Not sure whether an older card is even due for it? A GPU doesn’t need a repaste on any fixed schedule — how often to replace thermal paste covers when a widening delta actually makes it worthwhile.

When it’s not really the temperature

Two traps to avoid. First, if your card throttles or crashes but the temperatures you’re reading are actually fine, the fan may have been a red herring — a thermal-looking crash can really be a driver fault or an unstable overclock. If games crash to desktop or you get black screens without high temps, see Fix GPU Driver Crashes. Second, if you’re seeing weird colors, flickering, or graphical glitches, hot VRAM can cause it — but so can a dying card, and those need a different diagnosis: GPU Artifacts vs Dying VRAM. Third, if the whole machine reboots or cuts off under load while the GPU temps read fine, the heat is likely coming from the CPU instead — confirm whether the CPU is actually overheating the same core-vs-hotspot way — or it’s a power fault rather than heat, which the PC keeps restarting guide works through in order.

And don’t over-correct. A GPU that lives at 60 °C because you’ve run the fans at 100% forever is loud for no reason — the card was fine in the 70s. The goal isn’t the lowest possible number; it’s staying comfortably under the throttle point with reasonable noise.

The quick version

Confirm it’s actually hot. Core in the 70s/low-80s under load = normal. AMD hotspot at 95-105 °C beside a ~70 °C core = normal by design. Only core at ~85 °C+ (NVIDIA) / ~95 °C+ (AMD) with dropping clocks is a real problem.
Check the hotspot delta. Hotspot minus core: over ~20 °C (NVIDIA) or ~30 °C (AMD) — especially if it grew over time — means the thermal paste has pumped out, not that you have dust. On RTX 50-series cards the hotspot isn’t readable, so judge by throttling behavior instead.
Fix by cause. Both temps high together → clean dust + improve airflow + fan curve. Wide/growing delta → repaste and replace pads (RMA instead if in warranty). Undervolt for an easy few degrees either way.
Rule out imposters. Crashes with normal temps = driver, not heat. Visual glitches = artifacts/VRAM, a separate diagnosis.

Read the two temperatures and the delta between them before you spend a cent, and you’ll stop repasting cards that just needed dusting — and stop dusting cards whose paste actually pumped out two years ago.

Sources

Normal GPU temperature ranges, throttle points, and the core-vs-hotspot delta thresholds (NVIDIA ~10-15 °C healthy, AMD 20-35 °C by design): NVIDIA and AMD published thermal specs, cross-checked against HWiNFO sensor behavior and TechPowerUp GPU-Z documentation.
AMD RX 7000/9000 (RDNA 3/4) 110 °C junction limit and deliberately wide hotspot design: AMD product specs and reviewer thermal testing (TechPowerUp, Tom’s Hardware).
NVIDIA removing public hotspot sensor access on the RTX 50-series (Blackwell), the invalid 255 °C readout, and the RTX 5070 Ti measured at 107 °C hotspot via NVIDIA’s internal MODS tool while public tools showed ~67-68 °C core: Tom’s Hardware and VideoCardz coverage of the GPU-Z developer’s confirmation.
Thermal-paste pump-out on RTX 30/40-series after ~18-24 months and GDDR6X memory happiest under ~95 °C: enthusiast repaste testing and HWiNFO memory-junction reporting.

General diagnostic guidance for desktop GPUs in 2026; check your specific card’s documentation for exact figures. Found an error? Email hello@techfuelhq.com with the article URL.

Lines on Your Monitor? Tell If It's the Cable, GPU, or a Dying Panel (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

A line appears on your screen and the internet immediately splits into two camps. One says your monitor is dead, buy a new one. The other says it’s your graphics card, RMA it. Both are guessing, and following the wrong guess costs you real money — a replaced monitor that was fine, or a card sent back when the actual problem was a bent $8 cable.

The truth is that “lines on the screen” is one symptom sitting on top of at least five completely different faults: a dying panel, a loose ribbon cable inside the monitor, a bad video cable or port, a refresh-rate or driver problem, or a failing GPU. You don’t need to know electronics to tell them apart. You need one button and about sixty seconds.

Step 1: The OSD test — is it the monitor or the PC?

Every standalone monitor has physical buttons (or a little joystick) on the bottom or back edge that pull up its on-screen display — the menu for brightness, contrast, and inputs. That menu is your diagnostic referee, because the monitor draws the OSD with its own internal board — nothing from your PC touches it.

Press the button and bring up the menu while the lines are visible, then look carefully at the menu overlay itself:

The lines cut through the OSD menu too → the fault is inside the monitor. The PC is sending a clean signal (or no signal at all, in the menu’s case) and the corruption is being added by the panel or the ribbon cable feeding it. Your graphics card is off the hook. Skip to Step 2.
The OSD menu is perfectly clean while the rest of the screen has lines → the monitor is fine. The corruption is arriving from upstream — the cable, the port, the refresh rate, the driver, or the GPU. Jump to Step 3.

If you want a second opinion, unplug the video cable entirely. Most monitors respond by floating a “No Signal” or “Check Cable” box on screen, generated internally. If that box still has a line through it, the panel is bad, full stop.

This one test throws out half the advice on the internet before you’ve changed a single setting.

Step 2: It’s the monitor — read the pattern

If the lines survived the OSD test, the problem is the display. Now the shape of the line tells you how bad it is.

A single thin line, one solid color (red, white, blue, orange) running top to bottom or side to side is the most common — and often the most fixable — version. Inside an LCD, every column of pixels is fed through a flat ribbon cable to a driver chip. When one of those connections loosens from years of heat cycling, that column gets stuck and you see a fixed colored line.

Here’s the field test that thousands of people have confirmed: press or gently flex the bezel right where the line begins. If the line changes color, dims, or vanishes while you hold pressure, you’ve found a loose internal ribbon cable. That’s a diagnosis, not a cure — the permanent fix is opening the monitor and reseating (or replacing) that ribbon connector, which is doable if you’re handy but voids the warranty and risks cracking the panel. On a monitor still under warranty, don’t pry — claim it.

A band of lines, blocks, or garbled color that covers part of the screen and grows over time usually means the panel’s own driver ICs or its glass are failing. There’s no reliable home fix for that; it’s a replace.

One more monitor-side check: do the lines appear before Windows loads — in the BIOS/UEFI screen or the motherboard splash? If corruption is present that early, no driver or operating-system setting can be the cause. It’s hardware, and combined with a failed OSD test, it’s the monitor.

Step 3: It’s upstream — work cheapest first

If the OSD menu was clean, the monitor is innocent and the fault is somewhere between the GPU and the panel. Work this list in order — it goes cheapest and most-likely to most-involved.

Reseat both ends of the video cable. Unplug the HDMI or DisplayPort cable at the monitor and the PC, and push both firmly back in. Loose connectors are a genuine cause of intermittent lines and sparkles.
Swap the cable. Video cables fail at the connector and from tight bends, and a marginal cable struggles most at high resolution and refresh rate — exactly when lines show up. A spare DisplayPort cable or HDMI cable is a few dollars and rules this out for good.
Change the connection type. If you’re on HDMI, try DisplayPort, or vice versa, and use a different physical port on the GPU. A repeatedly reported real fix: red lines on an HDMI connection that disappeared entirely once the monitor was moved to DisplayPort.
Drop the refresh rate. In Windows Settings → System → Display → Advanced display, set the refresh rate down from a high value (144 Hz or 165 Hz) to 60 Hz. If the lines stop, the cable or port couldn’t sustain the bandwidth the higher rate demanded — go back to step 2 with a better cable.
Clean-reinstall the graphics driver. A corrupted driver can throw display artifacts. Use DDU (Display Driver Uninstaller) in Safe Mode to strip the old driver completely, then install the current one from NVIDIA, AMD, or Intel.

If a different cable, a different port, and a clean driver all change nothing, you’ve isolated it to the graphics card itself.

Step 4: Is it the GPU?

The graphics card becomes the prime suspect when the lines follow the PC, not the monitor — they appear on a second monitor and a second cable too, they show up at the Windows desktop or even in the BIOS, and especially when they only erupt under load in a game while the desktop stays clean.

There’s a fast confirmation: take a screenshot while the corruption is on screen and open the file on your phone or another PC. Screen capture grabs the frame before it leaves the graphics card, so if the lines are baked into the saved image, the card rendered them wrong — that’s a render-side fault (GPU, VRAM, driver, or the game). If the capture is clean while the monitor still shows lines, the frame left the card fine and got mangled downstream, which sends you back to the cable and connection.

Once it’s pointing at the card, the real question is whether it’s a fixable software issue or dying silicon — an unstable overclock and a bad driver both fake the symptoms of failing VRAM. Our companion guide, GPU artifacts: sorting software from a dying card, walks that split in detail so you only RMA a card that’s genuinely failing.

Special case: laptops

On a laptop there’s no external cable to swap, but the same logic applies — the “cable” is just internal. The panel connects through a thin ribbon that winds through the hinge, and that ribbon is the single most common source of laptop screen lines because it flexes every time you open and close the lid. The tell is that opening, closing, or twisting the lid changes the line. An external monitor plugged into the laptop is your OSD test here: if the external screen is clean, the laptop’s GPU is fine and the fault is the panel or its hinge ribbon.

Quick reference

What you see	Most likely cause	The test that confirms it
Line crosses the monitor’s own OSD menu	Panel / internal ribbon	OSD test fails
Single thin colored line, changes when you press the bezel	Loose internal ribbon cable	Pressure on the bezel
Lines in BIOS / before Windows loads	Hardware (monitor or GPU), not driver	Appears pre-boot
Lines vanish with a different cable or HDMI↔DP	Bad cable or port	Swap fixes it
Lines only at high refresh rate	Cable bandwidth limit	Drop to 60 Hz
Lines only in games, clean desktop	GPU (heat / overclock / VRAM)	Screenshot captures them
Lines on a second monitor + second cable too	Graphics card	Follows the PC, not the screen
Laptop line changes when you move the lid	Hinge ribbon cable	Flex the lid

When to stop and replace

Replace the monitor when the OSD test fails and a bezel press does nothing (or only helps briefly and you don’t want to open it), when the lines are spreading, or when it’s an out-of-warranty panel with failing driver ICs. Replace or service the GPU only after the screenshot test, a second monitor, and a clean driver all still point at the card. Everything else on this page — cables, ports, refresh rate, drivers — is cheap, reversible, and worth doing first. The most expensive mistake with screen lines isn’t the repair; it’s replacing the wrong part before you’ve spent sixty seconds finding out which part is actually broken.

Motherboard Failure Symptoms: How to Tell It's Really the Board (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

Here is the uncomfortable truth every “10 signs of a bad motherboard” list skips: almost none of those signs actually point at the motherboard. No power, random blue screens, dead USB ports, spontaneous restarts, a PC that turns on but shows nothing — every one of those symptoms is produced just as easily by the power supply, the RAM, the CPU, or the graphics card. The motherboard touches everything, so when something else fails, the board is where the blame lands.

That’s why the r/buildapc community has a 200-plus-comment troubleshooting thread full of people who were about to buy a new board — and didn’t have to. The fix was a CMOS reset, a swapped power supply, a reseated stick of RAM, or, in more than one case, a dead front-panel power button. A motherboard is almost never diagnosed by a symptom. It’s diagnosed by exclusion — you rule the other parts out, one at a time, until the board is the only suspect left. This guide does exactly that, and then shows you the small set of tells that only a bad board produces.

Step 1: First, is the board even dead? Watch for POST

Before anything else, settle one question: does the board POST — does it run its Power-On Self-Test far enough to signal that the core hardware is alive? This one observation saves people the most money, because a board that POSTs is a board that works.

Three things count as “it POSTed”:

It beeps. If the motherboard has a speaker (or a header you can attach one to) and it sounds a beep pattern at power-on, the board is alive. As one experienced builder put it in that thread, the chip that drives POST is one of the most reliable parts on the board and will almost always output a beep or code even when something else is seriously wrong. A dead board, by contrast, fails to POST roughly 99% of the time. A beeping board is not your problem.
Its debug LEDs cycle. Boards with a CPU/DRAM/VGA/BOOT LED cluster (or a two-digit code display) that light in sequence are running POST — see Step 5 for reading them.
It reaches a screen — even just the BIOS logo or a “no boot device” message. That’s a fully working board with a problem further down the line, not a dead one.

Now the trap that catches everyone: lights and spinning fans are not POST. As long as the PSU is feeding its standby voltage, a board can light its RGB, its standby LED, and even its little onboard power button while being completely unable to boot. Fans can spin for the same reason. “It lights up” tells you the PSU’s standby rail works — nothing more. If the board powers on, fans spin, LEDs glow, but it never beeps, never advances a debug LED, and never shows a picture, that is the pattern worth suspecting — after you’ve excluded everything in Step 4.

Step 2: The symptoms that are traps (and what really causes them)

These are the classic “motherboard failure symptoms.” Each one is far more often something else. Before you touch the board, clear the cheaper suspect:

No power at all / dead when you hit the button. Suspect the power supply first, then the front-panel power button. A failed or unplugged PSU, or a dead case power switch, produces an identical “totally dead” PC. (One builder in the thread chased a “dead board” that turned out to be the power button — shorting the two power pins on the board with a screwdriver booted it fine.) Full PSU walk-through: PSU failure symptoms.
Fans spin but there’s no display. Suspect RAM and GPU before the board — reseat the memory (one stick, slot A2), and reseat or swap the graphics card. A no-POST-no-picture machine is usually a seating or component fault, and it has its own dedicated diagnostic: PC turns on but no display.
Graphics card not detected. Reseat the card and its power cables, and test it in another slot or PC before blaming the board’s PCIe. See graphics card not detected.
Random blue screens and crashes. Suspect RAM (run MemTest86) and drivers first; unstable memory and bad drivers cause far more BSODs than a failing board.
Random restarts or shutdowns. Suspect the PSU and thermals — an undersized or dying supply and an overheating CPU both cause spontaneous reboots that look exactly like a board fault.
A USB port stopped working. Suspect drivers and power before hardware — and even if it is physical, a single dead port is often just that one port, not a dead board.

The pattern is clear: the loud, scary symptoms are shared, so a symptom alone can’t convict the board. What can is the short list below.

Step 3: The tells that only a motherboard produces

A few symptoms don’t have a cheaper explanation. When you see one of these, the board itself is genuinely implicated:

Physical damage. Capacitors bulging on top or leaking brown crust, scorch marks or discoloration near the VRM or CPU socket, or a sharp burning/electrical smell coming from the board. This is the closest thing to a smoking gun — and it’s board-specific.
The CMOS won’t hold. A board that forgets the time, loses BIOS settings on every power-off, or repeatedly resets to defaults has a failing CMOS/RTC circuit (sometimes just a dead coin battery, sometimes the board). If a fresh CR2032 doesn’t fix it, that’s a board fault.
A specific rear-I/O port group is dead while others work. The rear USB/audio/LAN ports are soldered directly to the board. If one bank of ports is stone dead while the rest of the system is fine, that’s board-level, not driver-level.
A single DIMM or PCIe slot is dead — but the part works elsewhere. If a known-good RAM stick works in slot A2 but never in B2, or a known-good GPU works in a different PC but not in your top PCIe slot, you’ve localized the fault to that slot on the board.
A debug LED that stays stuck on one stage after everything else is swap-tested good. Covered next.

If none of these are present and the machine merely “won’t boot,” you are not yet looking at a confirmed bad board — you’re looking at a not-yet-excluded one. Go to Step 4.

Step 4: The exclusion ladder — confirm the board by ruling out the rest

This is the actual diagnosis. Work down the rungs; power off at the PSU switch before touching anything inside, and mind static. At each rung, note the real culprits people find there — because most “dead boards” get fixed on a rung above the board.

Look and smell. Blown caps, burn marks, or a burnt odor? If yes, jump to Step 6. If no, continue.
Reseat the power cables. Firmly re-seat the 24-pin ATX and — the one people forget — the 8-pin EPS/CPU power connector at the top of the board. A missing or loose EPS is a classic “I killed my board” scare: the board powers standby fine, fans may twitch, but the CPU never gets power and nothing POSTs. (One builder spent an hour debugging a “dead” build that was just an unplugged EPS.)
Clear the CMOS. This is the number-one fix in that entire 200-comment thread — comment after comment of “clearing CMOS saved me a new motherboard.” Use the Clear-CMOS jumper/button, or pull the coin battery for five to ten minutes and hold the power button 30 seconds to drain residual charge. Then try to boot.
Exclude the PSU. Test the supply (PSU tester or paperclip jumper test), and ideally swap in a known-good supply of adequate wattage. If another PSU boots the system, the board is innocent. Details: PSU failure symptoms.
Minimal boot. Strip to the essentials: motherboard, CPU, one stick of RAM in the recommended slot, and the PSU — no GPU (if the CPU has integrated graphics), no drives, no extra USB or expansion cards. If it POSTs now, add parts back one at a time until the culprit reveals itself. A single bad stick or a shorting add-in card is a common find here.
Swap RAM and reseat/relocate. Try a different stick and different slots. Bad RAM prevents boot and mimics a dead board.
Only now, the CPU. If it still won’t POST after all of the above, the remaining suspects are the CPU and the board. Reseat the CPU (check for bent socket pins — a frequent casualty of cleaning or handling), and if you can, test a known-good compatible CPU. If a good CPU on your board still won’t POST, and your board on a good PSU with good RAM still won’t POST, the motherboard is the answer — by exclusion.

Notice how far down the ladder the board is. Everything above it is cheaper, faster, and statistically more likely.

Step 5: Reading the debug LEDs and beep codes

If your board has the four-LED debug cluster (ASUS Q-LED, MSI EZ Debug, Gigabyte Status LEDs, ASRock Dr. Debug), it’s trying to tell you where POST stalled. During a normal boot each LED flashes briefly and goes out as that check passes; whichever one stays lit marks the stage that failed:

CPU — checked first. A stuck CPU LED is the most misread signal on the board. It rarely means “dead CPU.” Far more often it’s the 8-pin EPS not fully seated, a CPU cooler mounted too tight or uneven, bent socket pins, RAM not seated (yes, memory problems can light the CPU LED), or a newer CPU on a board that needs a BIOS update to recognize it. Exhaust those before condemning the CPU or board.
DRAM — a memory issue: reseat, try one stick, try another slot, check the QVL for your kit’s speed.
VGA — the board can’t initialize the graphics card: reseat the GPU and its power, try another slot or another card.
BOOT — POST passed but no bootable drive was found: a storage or BIOS-boot-order issue, not a board fault. If the drive is missing from BIOS entirely, work it as an SSD not showing up in BIOS or Windows problem first.

Beep codes work the same way, minus the display — a pattern of beeps maps to a failed stage in your board manual. And remember the headline from Step 1: if it beeps or cycles LEDs at all, the board is alive. The debug LEDs are a diagnostic feature working, not a death notice. Only a debug LED frozen on a stage whose component you’ve already swap-tested good points back at the board.

Step 6: If it really is the board — repair or replace

If you found a blown capacitor or burn mark, or the board failed the full exclusion ladder, it’s confirmed. Two paths:

Repair is occasionally worth it. A local board-level tech can resolder a single blown capacitor or reflow a connector — builders have reported a blown-cap fix for around $25 — and that can make sense for a recent, otherwise-healthy board. If it’s under warranty, RMA it instead of opening it up.
Replace is the usual answer. Most consumer board faults (a failed VRM, cracked traces, a damaged socket) aren’t economically repairable. Match the socket and chipset to your existing CPU and RAM if you want a drop-in swap; a fresh motherboard for your platform is the clean fix. If your CPU generation is old, price the whole platform, because a new board may pull a new CPU and RAM along with it.

One more thing the thread hammers home: if the cause was a surge or a failing PSU, the damage rarely stops at the board — test the CPU and drives before trusting the rebuild, and put the new board behind a real surge protector. And take care during install: a couple of builders killed a good board by letting a large, heavy graphics card scrape across it on the way in.

The bottom line

A motherboard is a diagnosis of exclusion, not a symptom. The symptoms everyone lists — no power, blue screens, dead ports, random restarts, no display — are shared with the PSU, RAM, CPU, and GPU, which is why so many people replace a board that was never broken. Start by checking whether the board even POSTs (a beep or a cycling debug LED means it’s alive), ignore the false comfort of a board that merely lights up, and then walk the exclusion ladder: reseat power, clear CMOS, swap the PSU, strip to a minimal boot. Only when a good PSU, good RAM, and a good CPU still won’t POST — or you find a blown cap or a burn mark — is it actually the motherboard. Most of the time, it’s the $0 CMOS reset, the cheaper part, or the loose cable, not the $200 board.

PC Turns On But No Display? Read the Motherboard Before You Buy Anything (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~8 min read · St. Louis County, MO

The fans spin. The RGB lights up. Maybe the graphics card fans turn too. But the monitor sits there black — “No Signal” — and you have no idea which of the dozen parts inside is the problem. So you start guessing, and guessing gets expensive fast.

(If pressing power gets you nothing at all — no fans, no lights, no sound — that’s a different problem: the PC isn’t powering on in the first place, which is a power-on-path fault. Start with Power Button Not Working on Your PC? and come back here once it’s spinning up.)

Here’s a true story that plays out in build-help forums every single day: someone with this exact symptom buys a whole new motherboard, installs it, gets the same black screen — and then realizes they’d never plugged both PCIe power cables into the graphics card. A five-second fix cost them a motherboard. The reason it happened is that they skipped the one step that would have told them where to look: the motherboard is already reporting which component failed. You just have to read it.

This guide is built around that step. Don’t reseat anything, don’t order parts, and definitely don’t RMA a working board until you’ve done the two-minute check and read the debug LED.

The whole troubleshoot fits on one page. Here it is as a map — the entire decision, start to fix, before you touch a screwdriver:

The no-display decision tree

Follow it top to bottom. Every path ends at a specific fix, not a guess — and the branch you land on is chosen by the motherboard, not by you. The most expensive mistake is skipping to the bottom before reading the board.

Black screen · fans & RGB running

↓

STEP 1 · THE 2-MINUTE CHECK

Monitor on the right input? Cable in the graphics card, not the motherboard? Both GPU power cables clicked in? Tried a spare cable and a second monitor?

FIXED ✓

About half of all “no display” cases end here. Zero dollars spent. Stop — you're done.

STILL BLACK ↓

The board isn't finishing POST. It already knows why. Go read it.

↓

STEP 2 · READ THE DEBUG LED

Which light stays lit for ~a minute?

ASUS Q-LED · MSI EZ Debug · Gigabyte Status LEDs · ASRock Dr. Debug

↘ ↓ ↙

DRAM

MOST COMMON

Reseat RAM → one stick in slot A2 → wait out DDR5 training → clear CMOS.

VGA

THE GRAPHICS CARD

Reseat GPU + both power cables → try the iGPU → CSM for old cards.

CPU

RARELY DEAD

Check the 8-pin EPS cable → reseat → BIOS update → swap-test last.

NO LED AT ALL

SHORT / POWER

Suspect a standoff short or PSU fault → bench-test outside the case.

The board spends one second at power-on naming the culprit. Reading it is the difference between a $0 reseat and a needless new part. techfuelhq.com

Step 1: The two-minute “is it even broken?” check

Roughly half of “no display” posts are not hardware failures at all. Clear these before you open the case, because they take seconds:

Monitor input. Press the monitor’s Source/Input button and cycle through its inputs. A monitor set to HDMI 1 will show “No Signal” all day while your PC happily outputs on HDMI 2 or DisplayPort.
Cable in the graphics card, not the motherboard. This is the single most common self-inflicted one. If your PC has a dedicated graphics card (a horizontal card lower on the back panel), the video cable must go into that, not the motherboard’s HDMI/DisplayPort ports up near the USB stack. On most desktops with a discrete GPU, the motherboard’s video outputs are disabled — plug into them and you get nothing.
Try the other everything. A different cable, a different monitor, a different port on the card. Cheap cables die, and a bad DisplayPort cable produces an identical black screen to a dead GPU.
Both GPU power cables fully seated. Modern cards use one or two PCIe power connectors (or a 12VHPWR/12V-2×6 plug). If even one isn’t clicked in, the card powers its fans and RGB but never outputs video — exactly the trap that costs people a new motherboard.

If the screen is still black after those, the machine genuinely isn’t completing POST (the power-on self-test that runs before Windows). Now the motherboard earns its keep.

One fork before you dig in: was it working yesterday?

The single most useful question — and the one most guides never ask — is whether this is a brand-new build that has never posted, or a machine that worked fine and then suddenly went black. Same symptom, different odds, so it’s worth naming which one you’re in:

New build, never displayed. The prime suspects are seating and compatibility: RAM not fully clicked in, a GPU not seated, an EPS or PCIe power cable never plugged, standoffs shorting the board against the case, or a BIOS too old for a brand-new CPU. Work the debug LED below — this is exactly what it’s for.
It was working, then suddenly nothing. Seating rarely un-does itself, so the odds shift toward things that drift or wear: a GPU power cable that worked loose (especially a 12VHPWR/12V-2×6 plug that was never fully latched), a power supply beginning to fail so voltages sag under load, an XMP/EXPO memory profile that was always marginal and finally tipped over, a dead CR2032 coin cell that lost your BIOS settings, or a graphics card that’s genuinely dying (often after a spell of visual artifacts first). The good news: the debug LED reads these out too, so the procedure is the same — you just start suspicious of cables and the PSU rather than seating.

If you moved, bumped, or cleaned the PC right before it went dark, treat it as the “suddenly” case with a loose cable at the very top of the list — reseat every power connector before anything else.

Step 2: Read the debug LED — the step almost every guide skips

Nearly every motherboard sold in the last several years has a small cluster of diagnostic LEDs labeled CPU, DRAM, VGA, BOOT (sometimes shown as a single two-digit code). When you power on, they light in that sequence as the board initializes each subsystem, then go out once POST completes. The one that stays lit is the stage that failed — that’s your answer. Manufacturers just brand them differently:

Brand	What it’s called	Where to look
ASUS	Q-LED	Near the 24-pin power / DIMM slots
MSI	EZ Debug LED	Right edge of the board, order CPU→DRAM→VGA→BOOT
Gigabyte	Status LEDs	Usually a 2×2 block under the 24-pin connector
ASRock	Dr. Debug	A two-digit code display; higher-end boards

One important detail: on boot it’s normal for the LEDs to flash through the sequence quickly. Only when one stays lit for roughly a minute (or a code stops changing) should you treat it as the failure point. On AM5 / DDR5 systems especially, the DRAM light can sit on for several minutes during memory training on a first boot or after a CMOS reset — that’s expected, so give it time before you panic.

No debug LEDs at all, and nothing on screen? That’s its own signal. If the board never lights any diagnostic LED, it may not be getting power correctly, or something is shorting it — jump to the bench test in Step 4.

About beep codes: the classic POST beeps (one long + two short for a GPU error, a repeating tone for RAM) only work if you have the small PC speaker installed — and most modern cases and boards don’t ship one. No beep usually means “no speaker,” not “no problem.” If you do have a speaker, treat the pattern as a hint (they vary between AMI, Award, and Phoenix BIOS versions) and trust the debug LED where you have one.

Step 3: Fix by whichever LED is stuck (in hit-rate order)

There’s a reason to work these in order rather than jumping to the scariest one. Across the thousands of “no display” build-help threads that all look identical, the causes are wildly lopsided: the top of the list is free and common, the bottom is expensive and rare. Reading the debug LED tells you which branch; this tells you how much to worry.

What's actually wrong — and what it costs

Ordered by how often it's the real culprit, from the pattern of build-help threads. Bar length is the qualitative tier (Most common → Rare), not a measured percentage. Notice the shape: nearly everything that's likely is also free to fix.

Wrong monitor input, or cable not in the GPU$0 · MOST COMMON

RAM needs a firm reseat (or one bad stick)$0 · MOST COMMON

GPU unseated, or a PCIe power cable loose$0 · COMMON

Unstable XMP/EXPO or a bad BIOS setting (clear CMOS)$0 · COMMON

BIOS too old for the CPU, or a failing PSU$ · OCCASIONAL

A genuinely dead CPU or motherboard$$ · RARE

Work top-down. The instinct to assume the worst (a dead CPU) targets the rarest, priciest cause first — exactly backwards. techfuelhq.com

DRAM light stuck — start here, it’s the most common

Memory that isn’t detected is the number-one reason a PC powers on but won’t POST. In order:

Reseat the RAM. Power off, unclip each stick, and press it firmly back in until both clips snap. A stick that looks seated but isn’t fully clicked is a classic culprit.
Test one stick, in the right slot. Pull all but one, and put that one in the slot your manual specifies for single-stick operation (usually the second slot from the CPU, labeled A2 or DIMM2). If it POSTs, add sticks back one at a time to find the bad one or the bad slot.
Wait out memory training. On DDR5, give a fresh configuration several minutes before concluding it’s dead.
Clear CMOS. A bad memory setting (an unstable XMP/EXPO profile) can hang POST; clearing CMOS resets it. Use the board’s Clear CMOS button/jumper, or pull the CR2032 CMOS battery for a minute with the power unplugged.

VGA light stuck — the graphics card

Reseat the GPU in its slot, and re-check both power cables (the mistake from the intro).
Try the integrated graphics if your CPU has them: pull the GPU, plug the monitor into the motherboard, and see if you get a picture. If you do, the problem is the card or its slot, not the rest of the PC.
Try a different PCIe slot if the board has one.
The older-card gotcha: genuinely old GPUs (GeForce GTX 600/700-era cards and older, before UEFI GOP video BIOSes became standard) can hang on the VGA light on a brand-new board until you enable CSM / Legacy boot mode in BIOS — which is a chicken-and-egg problem you may need a newer card or the iGPU to solve first. Worth knowing if you paired an old card with a new motherboard. If the card POSTs elsewhere but not here, that’s the pattern.

If it does eventually POST and boot but the card is missing inside Windows, that’s a different problem — see graphics card not detected.

CPU light stuck — usually not a dead CPU

Check the 8-pin EPS power at the top-left of the board. An unplugged CPU power cable produces a dead, no-POST board that looks exactly like a fried processor. This is far more common than an actual dead CPU.
Reseat the CPU and inspect the socket for bent pins under good light.
BIOS too old. If you just dropped a newer CPU into an older board, the BIOS may predate support for it. Use the board’s BIOS Flashback feature (often with an older, supported CPU) to update.
Only then suspect the CPU itself — confirmed by swapping in a known-good chip. A new CPU that never POSTs on a compatible, updated board can be DOA, but prove it with a swap before spending.

BOOT light stuck

By this point the board has POSTed and you likely have a display — this is a storage/boot-device issue, not a no-signal one, so it’s outside this guide’s scope.

No LED lights at all, or a red “power” light with nothing else

Suspect a short or a power problem. The most common short is an extra motherboard standoff under the board, or a case screw contacting the wrong spot — a genuinely frequent cause that forum veterans spot immediately. Also confirm the power supply is actually delivering; if the system won’t stay on or cycles power, work through PC keeps restarting. And if the board never POSTs even stripped to CPU, one RAM stick, and a known-good PSU, work through the exclusion ladder in motherboard failure symptoms.

Step 4: The barebones bench test (when the LED won’t localize it)

If the debug LED is ambiguous or absent, strip the build down to the absolute minimum and test it outside the case, on the motherboard box or a sheet of cardboard, to rule out a case short:

Power supply
Motherboard
CPU + cooler
One stick of RAM
Monitor plugged into the iGPU if available, otherwise the GPU

Nothing else — no extra drives, no case fans on the headers, no front-panel USB, no second GPU. Power it on by briefly bridging the two power-switch pins with a screwdriver. If it POSTs like this, add components back one at a time until the black screen returns; the part you just added is the fault. If it still won’t POST bare, with CMOS cleared and a known-good CPU and RAM, then you’ve genuinely narrowed it to a failed motherboard or CPU — and even that is a part swap, not a “bricked” machine.

A quick note on the word bricked: a PC that powers on but won’t display is almost never actually dead. Real bricking is rare. Nine times out of ten this is a reseat, a repower, a cleared CMOS, or a single loose cable — which is exactly why reading the board before buying parts saves the most money.

The quick version

Rule out the dumb stuff (2 min): monitor input, cable in the GPU not the motherboard, spare cable/monitor, both GPU power cables seated.
Read the debug LED (ASUS Q-LED / MSI EZ Debug / Gigabyte Status LEDs / ASRock Dr. Debug). The light that stays lit — CPU, DRAM, VGA, or BOOT — is the failed stage. Give DDR5 memory training a few minutes first.
Fix that stage: DRAM → reseat / single stick in slot 2 / clear CMOS. VGA → reseat GPU + both power cables / try iGPU / CSM for old cards. CPU → check 8-pin EPS / reseat / BIOS update / swap-test last.
No LEDs at all → suspect a standoff short or power fault; bench-test outside the case.
Barebones bench test to isolate the culprit, then add parts back one at a time.

Read the board before you reach for your wallet. The motherboard spent a full second at power-on telling you exactly which component didn’t wake up — and the difference between a $0 reseat and a needless new part is whether you looked.

Power Button Not Working on Your PC? Find the Real Fault First (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

You press the power button and nothing happens — no fans, no lights, no sound — and the obvious conclusion is that the button is broken. It usually isn’t. On a desktop, “power button not working” is one of the most mis-diagnosed faults there is, because the same dead-press symptom is produced by a loose wire, a flipped PSU switch, stuck residual power, or a failing power supply just as often as by an actually-broken button. Swap the button (or the whole case) on that assumption and half the time the machine is still dead.

So the real first move isn’t “how do I replace the power button” — it’s “is it even the button?” There’s a single test that answers that in about a minute, before you spend a dollar or order a part. Let’s get to it in the right order.

First: totally dead, or partly alive?

Look at the machine when you press power and sort it into one of three buckets — this decides everything that follows:

Nothing at all. No fans twitch, no LEDs, no motherboard debug light, no sound. This is a power-on-path problem — the button, its wire, the PSU switch/cable, flea power, or a dead PSU. That’s what this guide is for.
Fans spin or lights come on, but nothing else. The PC is powering on — the button is working. Your problem is downstream (no POST, no display), which is a different track: start with PC Turns On But No Display? Find Where the Boot Breaks.
The button physically sticks, feels mushy, or stays pressed in. That’s a mechanical button fault — jump to the “clean or replace the button” section below.

The rest of this walkthrough is about the first bucket: you press power and the PC is stone dead.

Step 1: the 60-second differential

Before touching anything, use the pattern of the symptom to rank the suspects. These are the tells that separate a button problem from everything it gets blamed for:

What you observe	Most likely culprit	Why
Totally dead, but it worked before you moved or cleaned the case	Loose front-panel wire	The thin PWR_SW lead pulls off the header pins easily
Totally dead, no PSU fan, no rear-switch glow	Power delivery (PSU switch off, dead outlet/cable, dead PSU)	Nothing is reaching the board at all
Dead now, but unplugging for a while sometimes revives it	Flea power (stuck residual charge)	Capacitors hold a state until drained
Button jumping the header pins boots the PC, button press doesn’t	The button or its wire	The board is fine; the switch path is broken
Nothing happens even when you short the header pins	PSU or motherboard	The fault is behind the button entirely
Button feels stuck, gritty, or stays in	The physical switch	Dust, wear, or spilled liquid in the contact

Notice how few of these rows are actually “the button.” That’s the whole point — and the next three steps walk the ladder from free-and-likely to conclusive.

Step 2: rule out power delivery (free, do this first)

Most “dead button” calls are solved here without opening anything meaningful:

Check the PSU’s rear switch. The rocker on the back of the power supply has a | (on) and O (off). It’s easy to knock to O while moving cables or the tower. Set it to |.
Test the wall outlet and cable. Plug a lamp or phone charger into the same outlet to confirm it’s live, and reseat the power cable firmly at both the wall and the PSU. Try a different cable if you have one.
Drain the flea power. Residual charge can leave the board in a stuck, unresponsive state. Turn off the PSU switch, unplug the power cable from the wall, then hold the case power button down for 30 seconds to bleed the remaining charge out of the capacitors. Plug back in, flip the PSU switch to |, and try again. This one step revives a surprising number of “dead” PCs. Intel lists the same flea-power drain as a first move when a computer won’t turn on.

If the machine springs back to life after any of these, the button was never broken — you had a power-delivery hiccup. If it’s still dead, it’s time for the test that actually settles the button question.

Step 3: the conclusive test — jump the header pins

This is the single most useful step, because it tells you definitively whether the button is at fault. The case’s power button does exactly one thing: it briefly connects two pins on the motherboard’s front-panel header. You can do that connection yourself.

Leave the PC plugged in and the PSU switch on (|).
Remove the side panel.
Find the front-panel header — a small cluster of pins, usually in the lower-right corner of the board. Two of them are labeled PWR_SW (or PWR / PW / Power SW). Your motherboard manual shows the exact layout; the two power-switch pins are what you want.
Briefly touch those two PWR_SW pins together with the tip of a flathead screwdriver — a quick tap, metal across both pins at once.

What the result tells you:

The PC powers up. The motherboard, PSU, and all power delivery are working. The fault is the physical button or the thin wire running from it to the header — the cheapest, easiest failure on the whole list. Go to Step 4.
Still nothing — no fans, no lights, no spin-up. The button is now ruled out. The problem is behind it: a PSU that’s failed, a dislodged 24-pin or 8-pin CPU power cable, or a motherboard fault. Skip to “when it isn’t the button.”

Intel documents this screwdriver method explicitly — lightly touching the two power-switch header pins turns the system on if everything behind them is connected correctly, doing the same job as the case button. It’s a standard bench move, not a hack.

Safety: tap the two PWR_SW pins only — briefly, and be careful not to slip onto neighboring pins. Do it with the PSU on but keep your hands clear of the CPU/GPU power connectors. If you’re uneasy identifying the pins, the manual’s front-panel diagram removes the guesswork.

Step 4: the free permanent fix — steal the reset switch

If the jump test booted the PC, you’ve confirmed the button/wire is dead — but you don’t necessarily need to buy anything. The reset switch is electrically identical to the power switch: both are momentary buttons that briefly short two header pins. So you can promote the reset button to power duty:

Power down and unplug.
At the front-panel header, disconnect the small two-pin RESET_SW cable and the PWR_SW cable.
Plug the Reset cable onto the pins the Power cable was using (the PWR_SW pins).
Reassemble. Now the case’s reset button turns the PC on.

You give up the reset function — rarely missed — and gain a working power control for free. Builders on r/buildapc and Tom’s Hardware point to this exact swap as the go-to when a case power button dies. If you’d rather have a proper button back, a replacement PC power/reset switch is a couple of dollars and plugs straight onto the same pins.

If the button feels stuck or gritty

When the button physically sticks — stays depressed, feels mushy, or needs a hard jab — the switch mechanism is fouled or worn, not electrically dead. With the PC off and unplugged, blast compressed air around the gap of the button to clear dust or debris, and work it a few times. If it still sticks, the spring or switch is done — swap to the reset button as above, or replace the switch.

When it isn’t the button

If shorting the PWR_SW pins produced nothing at all, the button is cleared and the fault is deeper in the power chain. Work these in order:

Reseat the main power cables. With the PC unplugged, firmly re-seat the 24-pin motherboard connector and the 8-pin (4+4) CPU power connector at the top of the board. A partially-seated CPU power cable is a classic “totally dead, no response” cause after a build or a component swap.
Suspect the power supply. A PSU that’s died — or whose rear switch/cable is bad — gives you exactly this no-response-at-all symptom. The clean way to confirm it is covered in PSU Failure Symptoms: Is It Really the Power Supply?, including why the paperclip test only proves a PSU can switch on, not that it’s healthy.
Then the motherboard. If power delivery checks out and jumping the pins still does nothing, board-level failure is what’s left. The signs and the how-do-I-be-sure steps live in Motherboard Failure Symptoms: How to Be Sure.

And if at any point the PC does start powering on — fans and lights — but won’t show anything or finish booting, you’ve moved past the power-button problem into a display/POST issue: PC Turns On But No Display? picks up there. If it powers on but then restarts or cuts out on its own, work PC Keeps Restarting? Through the Causes instead.

The quick version

Sort the symptom. Totally dead (this guide) vs powers-on-but-no-display (a different problem) vs button physically stuck (mechanical).
Rule out power delivery first, free: PSU rear switch to |, test the outlet/cable, and drain flea power (unplug, hold the button 30 seconds, plug back in).
Jump the header pins. Tap the two PWR_SW pins with a screwdriver. Boots = the button/wire is the fault. Nothing = the button is ruled out.
If it’s the button, fix it free: swap the reset switch wire onto the PWR_SW pins, or drop in a couple-dollar replacement button. Sticky button? Compressed air first.
If jumping the pins does nothing, it’s power delivery — reseat the 24-pin and CPU power cables, then check the PSU, then the motherboard.

The button is the cheapest thing that can cause a dead-press, and one of the least likely — so prove it with the screwdriver test before you replace anything. Five minutes of diagnosis here saves you from ordering a case, a PSU, or a board to fix a problem that turned out to be a wire that fell off a pin.

PSU Failure Symptoms: Is It Really the Power Supply? (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

The power supply is the hardest part in a PC to diagnose, because when it starts to fail it doesn’t announce itself — it frames another component. Random shutdowns look like an overheating GPU. Blue screens look like bad RAM. A machine that won’t POST looks like a dead motherboard. People swap out card after card, reinstall Windows, reseat the memory, and burn a weekend — and the culprit was quietly sagging under the whole time.

So before you spend anything, the real first question isn’t “what are the symptoms of a failing PSU” — it’s “is it actually the PSU, or something the PSU is being blamed for?” Get that right and the rest is easy.

The signs of a failing power supply

Here’s what a dying PSU actually does. None of these alone is proof — several of them overlap with other faults — but the pattern is the tell.

Random shutdowns or hard reboots, usually under load. The PC works fine browsing or on the desktop, then cuts out completely the moment you launch a game, start a render, or otherwise spike the power draw. No blue screen, no error — it just dies, sometimes rebooting on its own. (If that no-warning, no-BSOD shutdown is your main symptom, our computer randomly turns off guide walks the full heat-vs-PSU-vs-short diagnosis in order.)
It won’t turn on at all, or turns on for a second and stops. Press power and get nothing — no lights, no fans — or a brief twitch that immediately shuts back down. (A dead press has cheaper causes too — a loose front-panel wire or the button itself — so rule those out first with Power Button Not Working on Your PC? before you condemn the PSU.)
Blue screens and instability with no consistent cause. BSODs that point at different drivers each time, freezes, and USB devices dropping out can all trace back to unstable power delivery.
Coil whine or buzzing that rises with load, or grinding from the PSU fan as its bearing wears. (Occasional light coil whine is normal and harmless on its own — it’s new or worsening buzz paired with the crashes below that points at the PSU.)
A burning or electrical smell — the most serious sign. Unplug immediately (more on that below).
The “random” fingerprint. This is the big one: a failing PSU crashes inconsistently. It dies in a game today, a video export tomorrow, then behaves for days. Hardware that fails on a schedule usually isn’t the PSU; hardware that fails at random, under load, with no error, very often is.

If you recognize the load-dependent, no-error, random pattern, the power supply moves to the top of the suspect list. Now rule the impostors in or out.

Step 1: Is it the PSU, the GPU, or the motherboard?

These three produce nearly identical top-level symptoms — sudden shutdowns and crashes — so the diagnosis is about the secondary clues each one leaves.

Clue	Points at	Why
Dies under load, no error, timing is random	PSU	A sagging rail can’t hold voltage when draw spikes; nothing gets a chance to log an error
On-screen artifacts, driver resets, black screens	GPU	Visual and driver-level corruption is the graphics card’s signature, not the PSU’s
Crashes repeat in the same game or the same scene	GPU (or thermal)	A reproducible trigger points at the component doing that specific work
Shutdowns even at idle, or won’t POST with everything else swapped	Motherboard / VRM	Board power delivery can fail independently of the PSU
BSODs that name memory, fails a RAM test	RAM	Memory errors have their own diagnostic (MemTest86)

The reason PSU faults feel “random” is physics: a degrading unit still holds voltage fine when the system is sipping power at idle, and only drops out of spec when a modern GPU slams it with a sudden current spike. That’s why the same PC can be rock-solid for hours of light use and then die ninety seconds into a game. Power-supply maker Seasonic describes the same split — PSU trouble shows up as sudden shutdowns under load with no software error, while a failing GPU leaves visual or driver clues first.

If the crashes come with visual glitches or driver resets, work the GPU angle instead: GPU Artifacts? Sort Software From a Dying Card. If the PC won’t display or POST at all, start where the boot chain breaks: Graphics Card Not Detected? Find Where It Disappears. And if it’s restarting rather than dying dark, the broader checklist lives in PC Keeps Restarting? Work Through the Causes.

The gold-standard tie-breaker, if you can manage it: swap in a known-good power supply — borrowed, or a cheap-but-reputable spare. If the shutdowns vanish, you’re done, no guesswork. It’s the single most conclusive PSU test there is, which is why experienced builders reach for it before any meter.

Step 2: Why the paperclip test lies

Search “how to test a PSU” and the top answer is almost always the paperclip test (also called the jumper test): unplug everything, leave only the 24-pin cable, and short the green PS_ON pin to any black ground pin with a bent paperclip. Plug in, flip the switch, and if the fan spins, the internet declares your PSU “good.”

It isn’t wrong, exactly — it’s just answering a much smaller question than you think. All the paperclip test proves is that the PSU can switch on. It runs the unit with essentially no load, and a failing supply almost always passes at idle. The way these units die is by failing to hold voltage under load — precisely the condition the paperclip test never creates. A power supply that spins its fan on the bench and then crashes your PC the instant a game loads has “passed” a test that measured the wrong thing.

So treat a passed paperclip test as “not completely dead,” not “healthy.” For a real read you need to load it and watch.

Step 3: Actually measure it — under load

Here’s the testing ladder from easiest to most conclusive.

1. Watch the 12V rail under load (free, best first move). Install HWiNFO (free), open Sensors, find the 12V, 5V, and 3.3V readings, and run a stress test — OCCT has a dedicated power-supply test, or run a demanding game. The ATX spec allows each rail a ±5% tolerance, so the valid windows are:

Rail	Nominal	Valid range (±5%)
+12V	12.0 V	11.40 – 12.60 V
+5V	5.0 V	4.75 – 5.25 V
+3.3V	3.3 V	3.135 – 3.465 V

Watch the 12V rail especially — it feeds the CPU and GPU and is where trouble shows first. Steady readings inside the window are healthy; a 12V line that sags toward or below 11.4V when load hits, or swings around erratically, is a failing supply caught in the act. (Motherboard sensors aren’t lab-accurate, so read the trend and stability more than the third decimal — the newer ATX 3.0 spec even permits brief 12V dips to about 11.16V during transient spikes, so a momentary flicker isn’t damning; a sustained sag is.)

2. Use a PSU tester (~$20–30). A dedicated PSU tester plugs onto the PSU’s connectors and displays each rail’s voltage. It’s more convenient than a multimeter and catches a rail that’s dead or badly out of spec. Its limit is the same as the paperclip test’s — it reads at low load — so a clean result doesn’t fully clear a unit that only misbehaves under a real GPU spike. Good for catching gross faults, not subtle sag.

3. Multimeter on the rails. If you own a multimeter, you can back-probe the 24-pin against the ranges above. Same caveat: it’s a snapshot, and low-load.

4. The swap test (most conclusive). As in Step 1 — a known-good PSU in place of the suspect one settles it completely. Nothing beats it.

Notice the theme: every bench test is limited because it can’t recreate a real load, which is exactly when a dying PSU shows itself. That’s why watching the rails under an actual stress load and swapping in a known-good unit are the two tests that actually earn their conclusions.

Safety: the one part you never open

A power supply stores lethal energy. The large capacitors inside can hold a dangerous charge for a long time even after it’s unplugged — enough to seriously hurt you. There is nothing user-serviceable in there, so never open the PSU casing. All the testing above happens from outside the unit, at the cables and connectors. If a PSU is bad, you replace it; you don’t repair it.

And if you ever get a burning smell, smoke, a loud pop, or see sparks — power off at the switch and pull the plug from the wall right away, and don’t turn it back on. At that point diagnosis is over; the unit is done.

When to stop testing and just replace it

Power supplies are the one component where “just replace it” is often the smart move rather than a cop-out, for three reasons:

A quality unit is affordable relative to what it protects — a good 650–850W supply is a fraction of the cost of the GPU and board it feeds.
A failing PSU can take other parts with it. An out-of-spec unit can corrupt data or, in a real failure, push a spike into your motherboard, GPU, or drives. Continuing to run a PC you suspect is being fed bad power is a gamble with expensive stakes.
Diagnosis has real limits. Short of the swap test, you can’t fully prove a PSU is healthy — only that it isn’t obviously dead. If the symptoms fit (random shutdowns under load, no error, an older or cheap unit) and you can’t borrow a spare, buying a reputable replacement is often cheaper than the hours you’d spend chasing ghosts.

When you do replace, buy quality and leave headroom: a reputable unit with a solid warranty, an 80 PLUS efficiency rating, and enough wattage that you’re not running near the ceiling. If you’re not sure how much you need, size it to your actual parts plus a comfortable margin with the PSU calculator rather than guessing high or low. A good PSU is the least glamorous upgrade in the machine and the one most worth not cheaping out on — it’s the part every other part depends on.

The quick version

Recognize the fingerprint. Random shutdowns or reboots under load, with no error message, that come and go unpredictably — that’s the classic failing-PSU pattern.
Rule out the impostors first. Visual glitches or driver resets → suspect the GPU. Won’t POST → start at the boot chain. Idle shutdowns that survive a known-good PSU → possibly the motherboard. Memory-named BSODs → test the RAM.
Don’t trust the paperclip test. It only proves the PSU turns on, not that it holds voltage under load — which is how these units actually fail.
Measure under load. Watch the 12V rail in HWiNFO during a stress test (valid range 11.40–12.60V); a sag under load is the smoking gun. A PSU tester or multimeter catches gross faults; a known-good-PSU swap is the only conclusive test.
Never open a PSU — the capacitors hold a lethal charge. Burning smell or a pop → unplug from the wall immediately.
When it fits, just replace it. A quality PSU is cheap insurance against a failing one damaging everything it powers.

Sort out whether it’s actually the power supply before you swap a single other part, and you’ll skip the weekend of replacing healthy components one at a time — the exact trap a failing PSU is built to spring.

Why Is My CPU Overheating? Diagnose It by When It Happens (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

Almost every guide answers “how do I fix an overheating CPU” with the same list: clean the dust, reapply the paste, add fans. That list isn’t wrong - but handed out blindly it sends people repasting a chip whose pump died, or buying a bigger cooler when the fan simply wasn’t plugged in. The fix depends entirely on the cause, and the cause is written in when the overheating happens.

So before you touch anything, two questions decide everything: is the CPU actually overheating, or just reporting a high-but-normal number - and if it is overheating, when does it happen? Get those right and the correct fix is usually obvious.

First: is it actually overheating?

A big temperature number is not, by itself, a problem. Modern AMD and Intel CPUs are designed to boost right up to their thermal limit under load, so a Ryzen 7000/9000 touching 90-95C in a render, or an Intel Core chip in the high 90s during a stress test, is the chip working as intended - not damage. The one wrinkle worth knowing: the older 7000-series X3D chips like the 7800X3D top out lower at ~89C, but AMD raised the newer 9800X3D back to the full 95C. If a high-but-stable number is all you’re seeing, you may not have a problem at all; our safe CPU temperature guide has the real numbers by chip and workload.

The CPU thermal dial: a high number is not a fault

Modern CPUs are built to boost right up to their limit under load. 84°C, 90°C, even 95°C in a heavy render is the chip working as designed — not damage. What actually signals a problem is behavior, not the reading on the sensor.

The lime band is peak boost by design — the chip wants to live there under load.

WHERE EACH CHIP’S REDLINE (Tjmax) ACTUALLY SITS

Ryzen 7800X3D — 89°C Ryzen 7000/9000 & 9800X3D — 95°C Intel Core 12–14th gen — 100°C Intel Arrow Lake (Core Ultra 200S) — 105°C

The dial can’t diagnose you — only these three can. Real overheating is behavior:

Throttles under LIGHT load

clocks and frame-rates fall off a cliff while barely doing anything

Hot at IDLE

85°C+ sitting on the desktop doing nothing

Sudden SHUTDOWN

the PC cuts power or reboots with no blue screen

Redlines cross-checked against AMD & Intel published Tjmax specs, July 2026. techfuelhq.com

Overheating is a behavior, not a reading. You actually have a heat problem when you see one of these:

Thermal throttling - clock speeds drop under load and stay down, which you feel as sudden stutter or a frame-rate falling off a cliff from smooth to a slideshow. (Throttling is one cause of in-game stutter; if temps are fine but games still hitch, work through why your PC stutters in games instead. A throttling CPU can also read as low GPU usage - the card coasts while it waits on the slowed processor.)
Sudden shutdowns or reboots - the chip hits its emergency limit and the system cuts power instantly, with no blue screen. (If the whole PC restarts, work the PC keeps restarting fixes alongside this; if it locks up instead, see computer keeps freezing.)
Temperatures that don’t match the workload - 90C+ while only browsing or sitting idle. This is the real red flag, and it’s the one that means a genuine fault.

Grab a monitoring tool - HWiNFO64 is the standard, free choice - and watch two things: the actual core temperature, and whether the chip logs thermal throttling. A CPU that spikes to its limit only during a heavy all-core load and holds its clocks is fine. A CPU that throttles during light gaming, or sits hot at idle, is not. Now find out when.

Diagnose it by when it happens

This is the shortcut every generic guide skips. Match how your overheating behaves over time to a row below, and you’ve narrowed the cause before you pick up a screwdriver.

Read the timing: the temperature’s shape names the cause

Each little trace is temperature over time. Find the one that matches yours, and the likely fault — and the first thing to check — is already picked out for you.

Instant at boot (often a “CPU over temperature error”) → the cooler isn’t mounted, the fan isn’t in the CPU_FAN header, or the AIO pump isn’t running.

First check: CPU_FAN header, mounting pressure, pump power.

Only under heavy load (games, rendering) → the cooler can’t keep up: aged paste, a poor mount, weak airflow, or a cooler undersized for the chip.

First check: thermal paste age, cooler contact, fan curve.

Hot at idle and light use too (70–90°C doing nothing) → a hardware failure: a dead AIO pump, a stopped fan, or a heatsink choked with dust.

First check: feel the AIO tubes for flow, confirm every fan spins, inspect the heatsink.

Crept up gradually over months → dust building in the heatsink, or thermal paste slowly drying out or pumping out from between chip and cooler.

First check: clean the heatsink, then plan a repaste.

Suddenly, right after you touched the PC → a cooler knocked loose, or an AIO that lost its prime after being moved (an air bubble parked over the pump).

First check: reseat the cooler, look for an AIO air bubble.

The one question that beats all of it: did something change? A new build or fresh repaste that overheats is a mounting/contact problem. A rig that ran cool for a year and suddenly spikes has something that broke — a failure to find, not a setting to tune. techfuelhq.com

The single most useful clue is whether something changed. A brand-new build or a fresh repaste that overheats is a mounting or paste-contact problem nine times out of ten. A rig that ran cool for a year and suddenly spikes has something that broke - and that’s a failure to find, not a setting to tune.

The causes, and the fix for each

A dead or dying AIO pump (sudden, idle-and-load)

If you run an all-in-one liquid cooler and temps suddenly rocket toward 90-100C even at idle, suspect the pump first. When coolant stops circulating, the cold plate can’t move heat and the chip heats up in seconds regardless of load. Builders on Tom’s Hardware and VI-Control repeatedly trace exactly this “80-90C at idle out of nowhere” pattern to a failed pump. To check it: with the PC on, gently feel the two tubes leaving the pump - you should feel faint vibration and, over a few minutes, both tubes warming; a big temperature difference between the tubes or dead-still tubes points to a stopped pump or a blockage. Also confirm the pump header reports RPM in the BIOS. A dead pump means a new cooler.

Thermal paste that dried or pumped out (gradual, or after years)

Paste doesn’t last forever. Over years it can dry out, and on some mounts it slowly “pumps out” from between the chip and cooler through thermal cycling, leaving a poor contact patch. The result is a chip that used to run cool creeping hotter under load. A fresh repaste with a proven compound - a ~$7 tube of the Arctic MX-4 is plenty for years of applications - often drops load temps several degrees on a chip that was running hot. One counterintuitive trap: too much paste after a repaste can insulate rather than conduct, so use a modest pea-sized amount, not a thick layer. How often you actually need to do this is a temperature question, not a calendar one — how often to replace thermal paste explains why the popular “every 2-3 years” rule misleads more people than it helps.

The cooler isn’t seated right (instant, or after a repaste/move)

Uneven mounting pressure, a cooler tightened lopsidedly, or - embarrassingly common - the thin protective plastic film left on a new cooler’s cold plate all wreck contact and cause instant overheating. If it started right after you installed the cooler or moved the case, pull the cooler, confirm the film is gone, clean and repaste, and remount with even pressure across all screws. On an AIO, moving the PC can also introduce an air bubble into the pump; a common trick is to power the system on its side briefly to let the bubble migrate away from the pump.

A dead fan or dust (gradual, idle-and-load)

The dullest causes are still the most frequent. A CPU cooler fan or a case fan that has stopped spinning, or a heatsink packed with dust, chokes heat removal. Open the case, confirm every fan actually spins at boot, and clear dust from the heatsink fins and filters with compressed air. If the CPU cooler fan itself won’t turn, CPU fan not spinning walks through telling a dead fan apart from a wrong-header or fan-stop false alarm. Poor case airflow - the culprit Corsair names as the most common cause of CPU overheating - is the cheapest big win: make sure the case has real intake and exhaust and isn’t shoved against a wall or crammed in a cabinet.

The chip simply runs hot for its cooler (under load only)

If everything is healthy and it only hits the limit under genuine heavy load, the cooler may just be undersized for the chip. Two fixes, cheapest first: undervolt - a Curve Optimizer offset on AMD or a voltage offset on Intel lowers temperature with little or no performance loss, and it’s the single highest-return tuning step - and if that isn’t enough, move to a stronger air cooler or a 240/360mm AIO.

The “CPU over temperature error” at boot

This specific message - often paired with “CPU fan speed detection error! Please ensure your CPU cooler is properly connected to the CPU_FAN header” - trips up a lot of new builders, and it’s almost never a slightly-too-warm chip. The motherboard is reporting that the CPU crossed a temperature threshold or that it can’t see a fan on the CPU_FAN header. Check, in order: the cooler’s fan or the AIO pump cable is plugged into the CPU_FAN header (not a case-fan or CPU_OPT header), the cooler is mounted with even pressure and its plastic film removed, and - on an AIO - the pump is actually powered and running. Fix the mount or the header connection and the error clears.

What if it’s a laptop?

A laptop overheats for the same underlying reasons but the odds shift, because everything is smaller and packed tighter. Three things matter more than on a desktop:

Dust is even more often the culprit. A laptop pulls air through a single small blower and a thin fin stack that clogs fast, especially if it’s ever used on a bed, couch, or carpet that blocks the underside intakes. Clearing the intake grilles and the fan with short bursts of compressed air (hold the fan still so it doesn’t over-spin) is the highest-return fix and the first thing to try.
A high number under load is often normal here too. Thin chassis run hot by design - many gaming laptops touch 90-100C under a sustained load and thermal-throttle on purpose to stay there. As on the desktop, the tell isn’t the reading, it’s the behavior: throttling during light use, or heat while idle, is the real fault. Raising the back of the laptop an inch for airflow, or a cheap cooling pad, buys a few degrees for free.
Repaste and undervolt do more, but repaste is harder. Factory laptop paste dries out and is a frequent cause of a machine that used to run cool; a repaste (and fresh thermal pads on the VRM/memory) often drops load temps more than anything else - but it means disassembly, so weigh your comfort and warranty. The lower-risk win first is an undervolt: on Intel laptops ThrottleStop or the vendor’s tuning app, on AMD the vendor utility, both of which cut temperature with little performance loss. Also check the vendor’s power/thermal profile isn’t stuck on a silent “quiet” fan curve.

If the fan itself rattles, screeches, or won’t spin at all, that’s a failing fan rather than a heat-management problem - a common and usually inexpensive repair.

When it’s actually fine

Plenty of “my CPU is overheating for no reason” posts turn out to be a healthy chip doing exactly what it’s supposed to. A Ryzen 7 7800X3D idling around 45-50C, or a Ryzen 7000/9000 briefly touching 95C in a stress test, is normal. If the number only spikes under real load, the clocks hold, and the PC is perfectly stable, you don’t have an overheating problem - you have a modern CPU. The tell that something is genuinely wrong is always the same: heat that doesn’t fit the work, throttling under light load, or shutdowns. Anything else is worth confirming against the real safe-temperature ranges before you spend a dollar. And if the CPU checks out but games still stutter or the case still runs hot, the part actually overheating may be the graphics card — confirm the GPU’s temps with the same core-vs-hotspot check before you touch a cooler.

What to do right now

Confirm it’s real. Open HWiNFO64, watch the core temp and the throttling flag. High only under heavy load with stable clocks = normal. Hot at idle, or throttling under light use = a fault.
Read the timing. Instant-at-boot, load-only, idle-too, gradual, or right-after-a-change - use the table above to pick your suspect.
Check the free stuff first. Fans spinning, cooler seated, plastic film gone, AIO tubes warming, dust cleared, case airflow real.
Then the cheap fixes. Fresh thermal paste, a sane fan curve, an undervolt.
Hardware last. A dead pump means a new cooler; a chip that’s genuinely too much for its cooler means a bigger one. Don’t buy either until you’ve ruled the failures out.

Overheating feels alarming, but the CPU is one of the best-protected parts in the machine - it will throttle and shut down long before it hurts itself. Treat the temperature as a symptom, find when it happens, and the actual fix is almost always cheaper and simpler than the panic suggests.

Sources

Modern CPU thermal limits and throttle-then-shutdown behavior, verified against AMD/Intel published Tjmax specs (July 2026): Ryzen 7000/9000 to 95C; the 7000-series X3D like the 7800X3D lower at ~89C, but the restacked 9800X3D raised back to 95C; Intel 12th-14th-gen Core to 100C; Intel Arrow Lake (Core Ultra 200S) raised to 105C (confirmed via Tom’s Hardware and WCCFTech coverage of Intel’s spec change). Cross-checked against our first-party safe CPU temperature guide.
Laptop specifics (single-blower dust as the dominant cause, thin-chassis throttling being normal, repaste/undervolt as the high-yield fixes): manufacturer cooling guidance and r/laptops / r/techsupport troubleshooting consensus.
AIO pump-failure pattern (sudden 80-90C at idle; feel the tubes for coolant flow): builder troubleshooting threads on Tom’s Hardware and VI-Control, corroborated by NZXT’s Kraken failure-diagnosis guidance.
Poor case airflow as the most common CPU-overheating cause, and repaste guidance: Corsair DIY-builder resources; too-much-paste-after-repaste caution from repaste troubleshooting write-ups.
“CPU over temperature error / CPU_FAN header” boot message and the after-a-move mount/air-bubble pattern: real r/buildapc and r/pchelp troubleshooting threads (e.g. “CPU overheating for no reason, brand new AIO… started overheating on boot, all I did was move cases”).

General diagnostic guidance for desktop CPUs in 2026; check your specific CPU and cooler documentation for exact figures. Found an error? Email hello@techfuelhq.com with the article URL.

Why Is My PC Stuttering in Games? Frame Stutter vs Low FPS (2026)

LK Wood IV — Fri, 10 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-10 · ~9 min read · St. Louis County, MO

Search “PC stuttering in games” and every guide hands you the same 20-item checklist: update drivers, close background apps, turn off G-Sync, turn on G-Sync, reinstall Windows. People try all of it, in random order, and post the same thread a week later - “tried EVERYTHING, high-end rig, still stutters.” The reason the checklist fails is that “stuttering” is three different problems wearing the same word, and the fix for one does nothing for the others.

So before you change a single setting, do two things: figure out which of the three problems you actually have, then read the pattern that tells you the cause. Get that right and the correct fix is usually short and obvious.

Here is the whole problem in one picture. Two rigs, both averaging 120 FPS. One is butter-smooth, the other stutters badly - and the difference is invisible to the FPS counter because it lives in the distribution of frame times, not the average. This is where your frames actually land:

Where a 120 FPS rig's frames actually land

How often each frame time occurs. Both rigs share the same tall peak - the same 120 FPS average. Stutter is the red tail the average is too coarse to report.

Identical average. Identical peak. The stutter is the red tail.

The average sits on the fat peak and never moves; the worst-1-in-1000 frame (your 0.1% low) lives out in the tail. That gap is exactly what "my high-end rig still stutters at 120 FPS" means - and why chasing a higher average number fixes nothing.

techfuelhq.com · distribution, not average · 2026

First: is it actually stutter?

Three completely different things get called “stuttering,” and they need opposite fixes:

Low FPS - the whole game is just slow (a steady 35 FPS everywhere). The frames are evenly spaced, there’s just not enough of them. Fix: lower settings/resolution or get more GPU. This is not stutter.
Frame-pacing stutter / hitching - the average FPS looks fine or even high, but the game lurches: brief freezes, hitches when you move or enter a new area, or a constant micro-jitter. The frames are arriving unevenly. This is the real topic of this guide.
Network lag - only in online games: your character rubber-bands or warps while the local framerate is perfectly smooth. Fix lives in your connection, not your PC.

The tell that separates them is your 1% and 0.1% low FPS, not the big average in the corner. Average FPS hides the gaps between frames - a single 50ms frame buried in a stream of 8ms frames barely dents a 120 FPS average, but your eye catches it every time. The 0.1% low is exactly that worst frame, and it’s the number that tracks how smooth the game feels. A rig showing 300 FPS average with 0.1% lows of 15 FPS will stutter worse than a locked, even 90.

Measure your frametimes (the step everyone skips)

You cannot fix pacing by feel. Turn on a frametime graph and the problem becomes visible:

In-engine or launcher overlay - many games and the Steam overlay show a frametime line. Steam’s performance overlay (Shift+Tab → Performance) has a detailed mode with a frametime graph.
RTSS / MSI Afterburner - the enthusiast standard; add the “Frametime” graph, not just FPS.
Intel PresentMon - a free, vendor-neutral capture tool that logs frametimes and 1%/0.1% lows to a file you can actually read back.

A healthy game draws a nearly flat frametime line. Stutter shows up as spikes shooting up off that line - each spike is one frame that took too long, and that’s a hitch you felt. Watch the graph and your GPU usage together for a minute of real gameplay and note two things: are the spikes regular (every few seconds like clockwork) or event-driven (only when you move, load, or enter a new zone), and does GPU usage stay near 99% or drop when a spike happens. Those two observations narrow the cause more than any checklist.

Route by the pattern

This is the shortcut the 20-item lists skip. Match your frametime-graph behavior to a row and you’ve found the likely cause before you change anything.

When/how it stutters	GPU usage during it	Most likely cause	First fix
In new areas / first hour after a game or driver update	Usually high	Shader compilation	Let it pre-compile; enable Steam pre-cached shaders; clear DirectX shader cache
Crossing zones / moving through an open world	Mixed	Traversal / streaming stutter (common in UE5)	Faster SSD, more RAM, cap FPS; often engine-side
Regular hitch every few seconds, in every game	Drops briefly	Background task or DPC latency	Close RGB/monitor/overlay apps; run LatencyMon
Stutter with FPS dips, GPU usage falls to 50-70%	Drops	CPU or RAM bottleneck / power limit	Enable XMP/EXPO; check 1% lows, temps, CPU power
Jitter/tearing near your refresh rate	High	Frame pacing / VRR range	Cap FPS ~3 below refresh; enable G-Sync/FreeSync
Started right after a Windows feature update	Any	Known OS/driver regression	Clean driver install; toggle HAGS; check for the fix

The single most useful clue is whether the GPU is pinned or coasting while it stutters. Pinned at 99% and still hitching points at shaders, VRAM, or pacing; dropping to 50-70% points at the CPU, RAM, or a background thread stealing time.

The causes, and the fix for each

Shader compilation (new areas, right after an update)

Modern DirectX 12 and Unreal Engine games compile shader programs on your specific GPU the first time each effect appears. While a shader compiles, that frame stalls - so you get hitching in fresh areas or for the first hour after a new install or driver update, then it smooths out as the cache fills. The community fixes, cheapest first: let the game finish its up-front shader step instead of skipping it; on Steam, keep “pre-cached shaders” enabled in Settings → Downloads so Steam downloads shaders others already compiled; and after a graphics driver update, clear the DirectX Shader Cache (Windows Disk Cleanup → DirectX Shader Cache) so it rebuilds clean. NVIDIA’s driver and the NVIDIA App added background shader-compilation handling in 2026 that helps here; keep the driver current and its shader cache size set generously. If a game is notorious for shader stutter (many UE5 titles are), that’s the engine, and a community patch or the title’s own “compile shaders” option is the real fix.

Background tasks and DPC latency (regular hitch, every few seconds)

A hitch that arrives on a clock - every few seconds no matter the game - is almost always something outside the game waking up. The usual suspects: RGB and fan-control suites, hardware monitors polling sensors too fast, browser tabs with hardware acceleration, Discord/overlay capture, cloud sync (OneDrive/Dropbox), the Xbox Game Bar’s background recording, and antivirus scans. Close them one at a time and watch the frametime graph. If hitches persist with everything closed, run LatencyMon (free) - it points at the specific driver holding the CPU too long. The fix is usually updating or rolling back a network, audio, or chipset driver, since those are the classic DPC-latency offenders. Turning off Game Bar background capture and browser hardware acceleration clears a surprising number of these.

A CPU or RAM bottleneck (FPS dips, GPU coasting at 50-70%)

If GPU usage falls when you stutter, the graphics card is idling while it waits on the rest of the system - the full diagnosis for a coasting card lives in low GPU usage: real bottleneck vs fake. The most common free fix by far: your RAM is running at its slow default speed because XMP (Intel) or EXPO (AMD) was never enabled in the BIOS - flip it on and stutter and 1% lows often improve immediately. Beyond that, a genuine CPU bottleneck (frequent in simulation, strategy, and busy open-world scenes) shows as maxed CPU threads and coasting GPU; there’s no setting that fully fixes it, but closing background CPU load, capping FPS to a steady number, and making sure the CPU isn’t thermal-throttling all help. If your CPU is running hot, throttling itself reads as exactly this stutter - see CPU overheating to rule that out. Builders on r/pcmasterrace have chased “ghost” micro stutter on high-end 9800X3D/RTX 50-series rigs all the way down to the CPU being power-choked on a weaker board, GPU usage collapsing to 50% under transient load - a reminder that “coasting GPU” can mean power delivery, not just a slow CPU.

VRAM overflow (stutter that worsens over a session)

If a game runs smooth for ten minutes then degrades into stutter, or stutters hard only at high texture settings, you may be out of VRAM. When the card runs out of video memory it swaps textures across the PCIe bus, and every swap is a hitch. Drop texture quality one notch, turn off frame generation (it costs VRAM), and watch whether dedicated VRAM usage is sitting at the card’s limit. If it is, you’re asking for more than the card holds - our guide to how much VRAM you need has the real numbers by resolution.

Frame pacing and VRR (jitter/tearing near your refresh rate)

An uncapped game whose FPS swings wildly delivers frames at constantly changing intervals, which your eye reads as stutter even at high averages. Two moves smooth it. Cap your FPS to a rate your PC can hold steadily (a stable 90 beats a jumpy 90-200), using an in-engine limiter or RTSS. And if you have a G-Sync/FreeSync display, cap a few frames below your refresh - 141 on a 144Hz panel - to stay inside the VRR window where the monitor syncs to the GPU. That combination kills both tearing and range-exceed stutter. If tearing itself is the visible problem, fixing screen tearing covers the V-Sync/VRR interplay in full.

After a Windows update (started out of nowhere)

If smoothness vanished right after a Windows feature update, treat it as a regression, not a hardware fault. Do a clean graphics driver install (DDU then reinstall), and try toggling Hardware-Accelerated GPU Scheduling - it helps some systems and hurts others, so test both states; our HAGS on-or-off guide explains which way to jump. Check the GPU vendor’s forums for a known-issue driver, and roll back if a specific driver version introduced it.

The quick-win order

If you want a sequence rather than a diagnosis, do these free steps first, in order, checking the frametime graph after each:

Enable XMP/EXPO in the BIOS - the biggest single new-build win.
Close background apps - RGB suites, browsers, capture/overlays, sync, monitors.
Clean-install the current GPU driver (DDU), then let a couple of games build their shader caches.
Cap your FPS to a steady number and enable G-Sync/FreeSync a few frames below refresh.
Confirm the CPU isn’t throttling and the RAM profile is actually applied.

Only after those - if a frametime graph still shows spikes you can’t explain - do you start looking at DPC latency, VRAM limits, or hardware. Most stutter dies somewhere in the first four steps; the people who “tried everything” almost always tried them blind, in the wrong order, without ever looking at a frametime graph. If your system is freezing outright rather than hitching, that’s a different problem - computer keeps freezing covers hard locks - and if a specific game crashes to desktop instead of stuttering, start with the GPU driver crash fixes.

Graphics Card Not Detected? Find Where It Disappears First (2026)

LK Wood IV — Thu, 09 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-09 · ~9 min read · St. Louis County, MO

Search “graphics card not detected” and the answer at the top of the page tells almost everyone the same thing: reinstall your graphics drivers. Sometimes that’s the fix. Just as often it does nothing — because a GPU that “isn’t detected” is actually three completely different problems wearing the same symptom, and a driver reinstall only touches one of them.

The question that decides everything: where does the card disappear? A card that’s missing from the BIOS screen is a hardware problem. A card the BIOS sees but Windows doesn’t is a driver problem. A card that both see but games ignore is a configuration problem. Answer that first and you’ve already thrown out two-thirds of the advice on the internet.

Step 1: Find where the card disappears

Before you change a single setting, do two things: restart and open the BIOS/UEFI (tap Delete, F2, or F10 during boot — the key is on the splash screen), and note what you see there and in Windows. Then match your situation to the table. (This assumes you can actually see the screen — if the PC powers on but there’s no display at all and you can’t even reach the BIOS, that’s a no-POST problem first: work through PC turns on but no display before worrying about detection.)

What you see	Where the card disappears	Where the problem lives	Go to
No image at all, or the card isn’t listed in BIOS	BIOS/UEFI	Hardware — seating, power, slot, or PSU	Step 2
Card missing in BIOS but board has integrated graphics giving you a picture	BIOS/UEFI	Hardware or a BIOS setting forcing iGPU	Steps 2 & 4
BIOS lists the card, but Windows shows “Microsoft Basic Display Adapter” or a yellow Code 43	Windows / Device Manager	Driver	Step 3
Windows sees the card, but games/apps run on the integrated graphics	In use (in games)	Configuration — port or hybrid-GPU setting	Step 5

One quick triage that resolves a surprising number of desktop cases before you go further: make sure your monitor cable is plugged into the graphics card’s ports, not the motherboard’s. If it’s on the motherboard, you’re looking at the integrated graphics output, and a perfectly good card will look “not detected” for games and appear absent from the display. The card’s ports are the horizontal row lower on the back of the case; the motherboard’s are up in the I/O cluster with the USB ports.

Step 2: Not detected in BIOS — the hardware branch

If the motherboard itself can’t see the card, drivers are irrelevant. Power the PC fully off and unplug it, then work these in order. A classic case here is fans spinning (or RGB lit) but nothing detecting the card — spinning fans only prove standby power reached the board, not that the GPU core initialized. That symptom points straight at power and seating. (The mirror-image case — fans dead and no display — is the same power/seating branch seen from the other side; if that’s you, GPU Fans Not Spinning walks it through, but the re-seating steps below apply either way.)

1. Re-seat the card — until it clicks

Pull the card out and firmly press it back into the top PCIe x16 slot until the slot’s retention clip snaps closed. A card that looks seated but isn’t clipped in is one of the most common causes, especially in a new build or after moving the PC. Blow out the slot with compressed air if it’s dusty.

2. Re-seat every PCIe power cable

Modern cards need supplemental power from the PSU, and a loose or partially inserted connector will let the fans spin while the core stays dark.

Unplug and firmly re-seat every 8-pin (or 6+2) PCIe power cable at both ends — the card and the PSU.
On an RTX 40- or 50-series card, the single 12VHPWR / 12V-2×6 (16-pin) connector must be pushed in completely until it clicks flush. A connector seated even slightly proud is a well-documented cause of the card not powering up (and worse, of it overheating) — this is one of the most common failures on brand-new high-end cards.
Don’t use a single daisy-chained cable to feed a power-hungry card from two connectors; run separate cables from the PSU where the card asks for them.

3. Try the other PCIe slot

If the board has a second x16 slot, move the card there and boot. If it’s now detected, the first slot is faulty (or was disabled in BIOS). If nothing changes, the slot isn’t the problem.

4. Rule out the power supply

A PSU that’s too small, old, or failing can make a healthy GPU look dead the instant it draws load. Check the card maker’s recommended wattage against your PSU, and if you have a spare known-good unit, swap it in to test. A dying PSU is also a common cause of a machine that powers on, fans spin, and then nothing — the same signature as a PC that keeps restarting or won’t stay on. If the card is detected in a different PC with an adequate PSU, your supply is the suspect.

Step 3: In BIOS but not in Windows — the driver branch

If the BIOS lists the card but Windows shows “Microsoft Basic Display Adapter” in Device Manager, or the GPU appears with a yellow triangle and Code 43, the hardware is fine and the driver is the problem.

1. Do a clean driver reinstall with DDU

A half-installed, corrupted, or Windows-Update-stomped driver won’t fix itself with a plain reinstall. Use Display Driver Uninstaller (DDU) to wipe it cleanly first:

Download DDU and the latest driver from NVIDIA, AMD, or Intel before you start (you’ll have no proper display driver mid-process).
Boot into Safe Mode (Settings → System → Recovery → Advanced startup → Troubleshoot → Startup Settings → Safe Mode).
Run DDU, choose your GPU vendor, and select Clean and restart.
Back in normal Windows, install the driver you downloaded.

2. Stop Windows from reinstalling the wrong driver

If Windows keeps replacing your good driver with a generic one, the freshly installed driver can start misbehaving again. After a clean install, keep the vendor’s app (NVIDIA App / AMD Software) set to manage updates.

3. Quick sanity checks

A hung — not missing — driver can sometimes be revived instantly with Win + Ctrl + Shift + B, which restarts the graphics stack. If the screen blinks and the card comes back, you had a driver hang, not a detection failure (see our deeper walkthrough on GPU driver crashes).
In Device Manager, right-click the card → Enable device if it’s disabled, and check View → Show hidden devices for a ghosted duplicate to remove.

Step 4: BIOS settings that hide a working card

Sometimes the card is seated and healthy but a firmware setting keeps it from initializing. Enter BIOS/UEFI and check these:

Primary display / Initiate Graphic Adapter: set it to PCIe / PEG, not IGFX/Auto, so the board hands off to the discrete card.
Above 4G Decoding and Resizable BAR: these help modern cards, but a mismatched combination can block detection on some boards. Try enabling Above 4G Decoding (Resizable BAR needs it on and CSM off). If a card vanished right after you toggled these, set them back.
CSM (Compatibility Support Module): newer UEFI GPUs sometimes won’t post with CSM in the wrong mode. Try it disabled (full UEFI) for a modern card.
Update the BIOS. An older motherboard often needs a BIOS update to recognize a newer-generation GPU at all — check the board maker’s support page for your exact model. This is a frequent fix when a new card in an older build simply doesn’t appear.
If you’ve changed several things, Load Optimized Defaults to get back to a known state, then set only the primary display to PCIe.

Step 5: Detected, but games use the integrated graphics

If Windows does see the card but everything runs slow because it’s using the integrated GPU, nothing is broken — it’s a selection problem.

Desktop: the usual cause is the monitor plugged into the motherboard port. Move it to the graphics card. That single change routes the display through the discrete GPU.
Laptop (hybrid graphics): Windows runs the power-saving integrated GPU by default and only wakes the discrete card for apps you flag. Open Settings → System → Display → Graphics, add your game or app, and set it to High performance. You can also set the preferred graphics processor per-app in the NVIDIA Control Panel or AMD Software.
Confirm the discrete GPU isn’t disabled in Device Manager or switched off in the BIOS (some laptops expose a “Discrete/Hybrid/Auto” graphics mode).

When it’s actually a dead card

If you’ve re-seated the card and its power, given it enough wattage, tried both slots, and it still isn’t detected — test it in another PC. A card that isn’t seen in any system, with adequate power, is genuinely faulty. At that point:

If it’s under warranty, RMA it. That’s almost always the right call — home board-level repair costs more than most cards are worth.
If it’s out of warranty and you need a replacement, match it to your PSU and case first; a mid-range current-gen graphics card is often a better value than repairing an old one. If your testing pointed at the power supply rather than the GPU, a quality 80 Plus Gold ATX power supply sized above the card’s recommendation is the fix — and it protects the new card too.

Before you spend anything, though, be sure: a failing PSU can frame an innocent GPU, so confirm the card is dead in a second machine first.

The quick version

Open BIOS and find where the card disappears — BIOS, Windows, or only in games.
Missing in BIOS → re-seat the card until it clicks, re-seat every PCIe power cable (12VHPWR fully home on RTX 40/50), try the other x16 slot, and rule out the PSU. (Fans spinning but no detect = power/seating.)
In BIOS but not Windows → clean-reinstall the driver with DDU in Safe Mode; watch for Code 43 or “Basic Display Adapter.”
Still hidden → set BIOS primary display to PCIe, try Above 4G / Resizable BAR / CSM, and update the motherboard BIOS for a newer card.
Detected but games use the iGPU → move the monitor to the card’s port (desktop) or set the game to the high-performance GPU (laptop).

Find where it disappears first, and you stop reinstalling drivers for a card the motherboard was never seeing in the first place. The same layer-by-layer logic works for storage too — see SSD not showing up in BIOS or Windows when a drive goes missing instead of the card.

WiFi Keeps Disconnecting? Isolate It First, Then Fix It (2026)

LK Wood IV — Mon, 06 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-06 · ~9 min read · St. Louis County, MO

Search “WiFi keeps disconnecting” and the answer at the top of the page — and most of the ISP pages under it — tell you the same thing: restart your router, move it to the middle of the room, done. Sometimes that’s the fix. Often it does nothing, because a Wi-Fi drop has two completely different homes, and the fix for one is useless on the other.

The single question that decides everything: when the Wi-Fi drops, does it drop on every device, or just this one? Answer that first and you’ve already cut the problem in half.

Step 1: Isolate — one device, or the whole network?

Before you change a single setting, watch what happens the next time it drops. Look at your phone, another laptop, a smart TV — anything else on the same Wi-Fi.

What you see when it drops	Where the problem lives	Where to work
Only this PC drops; phone and other devices stay online	The device — its Wi-Fi adapter, driver, or power settings	Step 2 (the Windows fixes)
Every device drops at the same moment	The router, modem, or ISP	Step 4 (the router fixes)
Drops only in certain rooms / far from the router	Signal / range	Step 4, then the hardware section
Drops at predictable times (evenings, weekends)	Congestion / interference	Step 4 (channel + band)

This one observation is what almost every guide skips — and it’s why “restart your router” so often fails. Restarting the router cannot fix a laptop whose Wi-Fi adapter is being switched off to save battery. If only your PC drops, leave the router alone and go to Step 2.

Step 2: If it’s only this PC — the Windows fixes, in order

These are ordered by how often they actually solve it. Do them top to bottom and stop when the drops stop.

1. Turn off adapter power saving (the fix Windows hides)

This is the number-one cause of a single Windows machine dropping Wi-Fi, and it’s buried where nobody looks. Windows has a power-saving feature that quietly switches the Wi-Fi adapter off to save energy — and sometimes it doesn’t switch it back on cleanly.

Right-click Start → Device Manager.
Expand Network adapters, right-click your Wi-Fi adapter, choose Properties.
Open the Power Management tab.
Uncheck “Allow the computer to turn off this device to save power,” and click OK.

That’s it. For a lot of people the drops stop here, in under five minutes. (On a laptop, also open Settings → System → Power and make sure a battery-saver profile isn’t re-applying aggressive power limits.)

2. Update — or roll back — the Wi-Fi driver

A buggy or outdated Wi-Fi driver is the next most common cause, and Windows Update often installs a generic driver that behaves worse than the one from the hardware maker.

If the drops are long-running: get the latest Wi-Fi driver from your laptop maker’s support page (Dell, HP, Lenovo, ASUS…) or the adapter chipset maker (Intel, Realtek, MediaTek, Qualcomm). Install it over the top.
If the drops started right after a Windows or driver update: roll it back. Device Manager → your adapter → Properties → Driver → Roll Back Driver. A regression in a new driver is a classic trigger.

3. Check the WLAN AutoConfig service

Windows manages your Wi-Fi through a service called WLAN AutoConfig. If it’s stopped or set to Manual, connections get flaky.

Press Windows Key + R, type services.msc, Enter.
Find WLAN AutoConfig, double-click it, set Startup type: Automatic, and make sure it’s Running.

4. Tame roaming aggressiveness (only if you have more than one access point)

If you use a mesh system or more than one router/AP, your adapter constantly decides whether to jump to a “better” signal. Set too aggressive, it hops back and forth and drops mid-hop.

Device Manager → your Wi-Fi adapter → Properties → Advanced tab → Roaming Aggressiveness (some adapters call it Roaming Sensitivity).
The default is usually Medium (3). If you’re getting drops as you move around a multi-AP home, try Medium-Low or Low so the PC stays put longer.
On a single-router home this setting doesn’t matter — skip it.

5. Prefer 5 GHz over 2.4 GHz

The 2.4 GHz band reaches farther but is slower and crowded — it’s shared with neighbors, microwaves, Bluetooth, and smart-home gear. Where the signal is strong, 5 GHz is far more stable. In your adapter’s Advanced tab you can set Preferred Band to 5 GHz, or simply connect to the network’s 5 GHz name if the router broadcasts them separately.

6. Reset the network stack

If it still drops, flush Windows’ networking state. Open Command Prompt as administrator and run these one at a time, then reboot:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

7. Turn off Fast Startup

Fast Startup half-hibernates the PC instead of doing a clean shutdown, and it’s a frequent cause of Wi-Fi that won’t reconnect after a cold boot. Control Panel → Power Options → “Choose what the power buttons do” → “Change settings that are currently unavailable” → uncheck “Turn on fast startup.”

Step 3: Read the report Windows already keeps

Here’s the step that turns guessing into knowing — and, like reading Event Viewer for a freezing PC, it’s the part almost every guide leaves out. Windows can generate a full WLAN report: a timeline of every connect, disconnect, and the reason for each.

Open Command Prompt as administrator.
Run netsh wlan show wlanreport.
It creates an HTML report — the command prints the path (usually C:\ProgramData\Microsoft\Windows\WlanReport\wlan-report-latest.html). Open it in a browser.

The report shows a graph of your connection sessions with red markers on the disconnects, and for each one it lists a reason code — whether you roamed to another AP, whether the adapter dropped the link, or whether you simply lost the IP/DNS lease. That distinction tells you which of the fixes above to trust:

“Roamed” / lots of session switches → it’s the roaming/signal problem (Step 2.4 and 2.5, or a range issue).
Adapter reset / driver events → it’s power management or the driver (Step 2.1–2.2).
DHCP/DNS failures → it’s the router handing out addresses, not the PC (Step 4).

You can also run netsh wlan show interfaces right before and after a drop to watch the signal strength and state change in real time.

Step 4: If every device drops — work the router

When the whole house loses Wi-Fi at once, no amount of PC tweaking will help. Work the network equipment instead:

Power-cycle properly. Unplug the modem and router, wait 30 seconds, plug the modem back first, let it fully sync, then the router. This clears the most common transient faults.
Fix channel congestion. In a dense area, several neighbors on the same 2.4 GHz channel will cause mutual drops. Log into your router and set the 2.4 GHz channel to 1, 6, or 11 (the only non-overlapping ones), and enable 5 GHz for devices that support it.
Update the router firmware. Years-old firmware is a real source of instability; check the admin page for an update.
Check for overheating and placement. A router baking on top of a receiver, or crammed behind a TV, will drop connections when it gets hot. Give it air and a central, open spot away from thick walls, metal, and water (fish tanks, radiators).
Snug the cables. A slightly loose coax or WAN cable causes intermittent whole-network drops that look exactly like a Wi-Fi problem.

If every device still drops after all of that, the problem is likely upstream — the modem, the line, or the ISP. Note the times it happened and call your provider with specifics.

When the real fix is new hardware

Sometimes the adapter or router is simply old and struggling. A few honest upgrade paths once you’ve ruled out settings:

A dead or ancient laptop/desktop adapter: a plug-in USB Wi-Fi 6 adapter is the fastest way to bypass a flaky built-in card without opening anything. For a desktop with an open slot, a PCIe Wi-Fi 6E card with real antennas gives a far stronger, more stable link than a tiny dongle.
Drops that are really a range problem (only in far rooms): a single router can’t cover every home. A mesh system fixes dead zones properly — and if you’re weighing whether the newest standard is worth it, our Wi-Fi 7 for the home network guide breaks down when it actually helps and when Wi-Fi 6E is the smarter buy.

The quick version

Watch a drop. Only this PC, or every device?
Only this PC → turn off adapter power saving, update/roll back the driver, check WLAN AutoConfig, tame roaming, prefer 5 GHz, reset the network stack, disable Fast Startup.
Read netsh wlan show wlanreport to see why it dropped, and confirm which fix to trust.
Every device → power-cycle the modem+router, fix the channel, update firmware, cool and reposition the router, check cables — then call the ISP if it persists.

Isolate first, and you never waste an hour restarting a router for a problem that was living inside your PC the whole time.

Computer Keeps Freezing? Diagnose It by Freeze Type (2026)

LK Wood IV — Sun, 05 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-05 · ~9 min read · St. Louis County, MO

Most freezing guides — and the AI answer at the top of the results — hand you the same generic list: run sfc /scannow, clear the dust, update Windows. Sometimes that works. Often it doesn’t, because a computer freezes for very different reasons, and the fix for one type does nothing for another. The move that actually saves time is to sort the freeze first, then read what Windows already logged about it — and only then fix the specific thing.

Step 1: Sort the freeze type (this decides everything)

Before you change a single setting, figure out which of these you have. The type points straight at the likely cause:

What the freeze looks like	Usually means	Where to look
Hard freeze — total lock, mouse won’t move, sound loops, only a power-button hold recovers it	Hardware	RAM, overheating, failing drive, PSU
Soft hang — mouse still moves, apps go “Not responding,” recovers after several seconds	Software / resource	100% disk, low RAM, a driver
Only under load / while gaming	Heat or GPU	Temps, GPU driver, PSU
Only on idle, or right after waking from sleep	Power / driver states	Fast Startup, power plan, driver power management

If you’re not sure which you have, watch for one tell: does the mouse cursor still move during the freeze? A cursor that moves while everything else is stuck is a soft hang (software). A cursor frozen solid with everything else is a hard freeze (hardware). That single observation rules out half the causes.

Here’s the whole method on one grid. Find your freeze type on the left, and the bright cells are where to start — the dim ones are worth a look only if the bright ones come up clean. This is why sorting the type first saves hours: it crosses out most of the columns before you touch a screwdriver.

Which freeze points at which cause

A likelihood map, not a percentage chart — the shading is the diagnostic odds from the freeze pattern, read down from Steps 3–6. Start on the bright cells in your row.

FREEZE TYPE	RAM	HEAT	DRIVE	PSU	RESOURCE	GPU DRIVER	POWER STATE
Hard freeze mouse dead · Steps 2–3	START	likely	likely	likely	·	maybe	·
Soft hang cursor moves · Step 4	maybe	·	likely	·	START	·	·
Only under load / gaming Step 5	maybe	START	·	likely	·	START	·
Only idle / after sleep Step 6	·	·	·	maybe	·	maybe	START

start here likely, if the bright cell is clean possible, check last · unlikely for this pattern RESOURCE = disk pinned at 100% or low free RAM · techfuelhq.com

Step 2: Read what Windows logged (the step everyone skips)

Windows keeps a record of crashes and freezes. Reading it is faster than trying random fixes, and it’s the part almost every guide leaves out.

Start with the friendly view:

Press Windows Key + R, type perfmon /rel, and press Enter to open Reliability Monitor.
You’ll see a timeline with red X marks on the days things went wrong. Click the day of a freeze to read a plain-English summary of what failed.

Then get the detail:

Press Windows Key + R, type eventvwr.msc, and press Enter.
Go to Windows Logs → System, and look at the events stamped at the time of your freeze.

Three events tell you most of what you need:

Kernel-Power, Event ID 41 — Windows lost power or was hard-reset without a clean shutdown. This is the fingerprint a hard freeze leaves when you had to hold the power button. It’s a symptom, not the cause — but combined with “it only happens under load,” it points at power or heat.
WHEA-Logger (Event ID 17, 18, or 19) — the hardware itself reported an error. This is a strong signal of CPU, RAM, or memory-controller instability (often an unstable memory overclock/EXPO profile, or a genuinely failing part).
“Display driver stopped responding and has recovered” / LiveKernelEvent 141 — the graphics driver timed out and Windows reset it (a “TDR” event). Your fix lives in Step 5.

Match the event to the step below. If Event Viewer is empty at the freeze time, that itself is a clue: a freeze that logs nothing is usually a dead-hard hardware or power cut.

Here’s how to read the three fingerprints at a glance — the event name is the label Windows writes; the verdict is what it actually means; the arrow is where to go next.

Decode the log line

Three event signatures cover most freezes. Find the one stamped at your freeze time in System — each is a different culprit and a different fix.

Kernel-Power · Event ID 41

The PC lost power or was hard-reset without a clean shutdown — the fingerprint a hard freeze leaves after a power-button hold. A symptom, not the cause.

Paired with “only under load” → power or heat · Step 3

WHEA-Logger · Event ID 17 / 18 / 19

The hardware itself reported an error. A strong signal of CPU, RAM, or memory-controller instability — very often an unstable memory overclock (EXPO/XMP), not a dead part.

→ test RAM at JEDEC · Step 3

Display driver stopped responding · LiveKernelEvent 141

The graphics driver timed out and Windows reset it — a “TDR” event. The GPU driver, or heat/power showing up through it.

→ clean-reinstall the GPU driver · Step 5

Nothing logged at the freeze time? A freeze that leaves no trace is usually a dead-hard power cut or hardware fault — go straight to Step 3. techfuelhq.com

Step 3: Hard freezes → check the hardware, in order

If it’s a total lock (and especially if you saw Kernel-Power 41 or WHEA-Logger), work these in order:

RAM. Faulty or unstable memory is the classic cause of sudden hard freezes. Run the built-in Windows Memory Diagnostic (Windows Key + R → mdsched.exe → “Restart now and check for problems”), or MemTest86 from a USB stick for a thorough overnight pass. If you run an EXPO/XMP profile, set memory back to its default JEDEC speed and test — an overclock the kit or controller can’t hold freezes a system that’s otherwise healthy. The same bad or unstable memory often blue-screens instead of hanging, most often as PAGE_FAULT_IN_NONPAGED_AREA, which is worked in the same RAM-first order.
Heat. A CPU or GPU parked at its thermal limit can stall the whole system. Check load temps with HWiNFO; our safe CPU temperature guide covers what’s actually too hot (Ryzen to ~95 °C, X3D ~89 °C, Intel ~100 °C). Clear dust from fans and heatsinks with a can of compressed air, and if the paste is a few years old, a fresh tube of Arctic MX-4 often drops load temps several degrees.
Storage. A failing or nearly-full system drive causes hangs and hard freezes. Check the drive’s SMART health with CrystalDiskInfo (anything but “Good” is your answer), and make sure the system drive has at least 15–20 GB free — Windows freezes when it can’t page or write.
Power. If freezes are load-related and log nothing, suspect the PSU. Reseat every power cable (including all pins on a 12VHPWR/12V-2×6 GPU connector), and if a hungry GPU sits on an old supply, that’s a common cause. This overlaps heavily with reboots — if it sometimes restarts instead of freezing, work our PC keeps restarting guide alongside this one.

Step 4: Soft hangs → free the stuck resource

If the cursor still moves and apps go “Not responding,” you’re waiting on a resource. Open Task Manager (Ctrl+Shift+Esc) before the next hang, or right after, and watch the columns:

Disk pinned at 100%. The usual culprits are SysMain (SuperFetch) and Windows Search indexing thrashing the drive — common on systems with a hard drive or an aging SSD. Open services.msc, find SysMain, set Startup type to Disabled, and stop it; do the same for Windows Search as a test. If the hangs stop, that was it.
Memory near 100%. Too little free RAM for what’s open forces constant paging and stutter. Close heavy background apps and browser tabs; if it’s chronic, add memory. On a 8 GB machine in 2026, a browser plus a game will do this on its own. (If the game hitches rather than locking up the whole PC, that’s frame-pacing, not a freeze — see why your PC stutters in games.)
A specific process spiking. Sort by CPU or Disk to catch a misbehaving background app or a stuck update. A stuck Windows Update or a runaway antivirus scan freezes weak systems until it finishes.

A special case — brief freezes every few seconds, in a rhythm. If the machine hitches for a second or two on a repeating beat (the mouse catches up, then stalls again), that pattern points somewhere specific, not at general resource starvation. Check two things in order. First, the drive: a disk with failing or pending sectors stalls the whole system while it retries a read, and the stalls come in waves — run CrystalDiskInfo (look for a “Caution” SMART status or reallocated/pending sector counts) and, on a mechanical drive, listen for repeated clicking. Second, driver latency (DPC): a badly-behaved driver — most often network (Wi-Fi/Ethernet), audio, or a Bluetooth/USB device — can hog the CPU in short bursts and freeze the desktop periodically even when Task Manager looks idle. The free tool LatencyMon names the offending driver directly; a network or audio driver at the top of its list is your lead. Update or roll back that specific driver rather than reinstalling Windows.

Step 5: Load / gaming freezes → the graphics driver

If it only freezes under a game or GPU load — or Event Viewer showed a “display driver stopped responding” / TDR event — the graphics driver is the prime suspect:

Clean-reinstall the GPU driver. A plain reinstall often isn’t enough; do a full clean removal with DDU and a fresh driver. The complete process is in our GPU driver crash fix guide.
Confirm it’s not heat or power in disguise. Load freezes are also how a marginal PSU or an overheating GPU shows up — check GPU temps and hotspot in HWiNFO while you play. If temps are fine and a clean driver doesn’t fix it, treat it as power (Step 3).

Step 6: Idle or after-sleep freezes → power states

A PC that’s fine while you use it but freezes on idle, or locks up right after waking from sleep, is almost always a power-state or driver-power problem:

Turn off Fast Startup. Control Panel → Power Options → “Choose what the power buttons do” → “Change settings that are currently unavailable” → uncheck “Turn on fast startup.” Fast Startup half-hibernates the PC and is a frequent cause of post-wake freezes and cold-boot lockups.
Set the power plan to Balanced or High performance (not a third-party or aggressive custom plan), and in the plan’s advanced settings, turn PCI Express Link State Power Management to Off and disable USB selective suspend if a USB device wakes the system badly.
Update chipset and storage drivers from your motherboard maker — idle freezes often trace to a power-management bug in an old chipset or NVMe driver.

Step 7: The basics worth doing anyway

Regardless of type, these are cheap and occasionally the whole fix:

Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, to repair corrupt system files.
Install pending Windows updates (and optional driver/firmware updates), then reboot.
Scan for malware — a hidden miner or bad process freezes a system under its own load.
Keep 15–20 GB free on the system drive.

The fix order, in one list

Sort the freeze type — hard lock (hardware) vs soft hang (software) vs load vs idle. Cursor still moving = soft.
Read the logs — perfmon /rel then Event Viewer → System. Kernel-Power 41 (power/heat), WHEA-Logger (CPU/RAM), display-driver-stopped (GPU).
Hard freeze → RAM (mdsched/MemTest86, test at JEDEC), temps, drive SMART + free space, PSU cables.
Soft hang → Task Manager: 100% disk (disable SysMain/Search), low RAM (close/add), a spiking process.
Load/gaming → clean-reinstall the GPU driver (DDU), recheck GPU temps/power.
Idle/after sleep → turn off Fast Startup, fix the power plan, update chipset/NVMe drivers.
Basics → sfc/DISM, updates, malware scan, free space.

Work it in that order and the freeze type plus the logged event usually points you straight to the right step — no guessing, no parts-cannon.

Sources

The diagnostics and fixes use Microsoft’s built-in tools — Reliability Monitor (perfmon /rel), Event Viewer (eventvwr.msc), Windows Memory Diagnostic (mdsched.exe), services.msc, Power Options, and sfc /scannow + DISM /Online /Cleanup-Image /RestoreHealth — all standard and self-verifiable on any Windows 10/11 PC. The event signatures (Kernel-Power 41 = unclean shutdown/hard-reset; WHEA-Logger 17/18/19 = hardware-reported error; LiveKernelEvent 141 / “display driver stopped responding” = a graphics TDR event) are documented by Microsoft and cross-corroborated across community troubleshooting threads (Microsoft Q&A, Tom’s Hardware forums). A few widely used third-party diagnostics are named where the built-in tools don’t cover the job: CrystalDiskInfo and MemTest86 for drive-SMART and memory testing, HWiNFO for load temperatures, and LatencyMon for pinpointing the driver behind rhythmic, every-few-seconds micro-freezes (a DPC-latency pattern the generic “close some tabs” advice never catches).
Thermal limits and what “too hot” means: our safe CPU temperature guide (first-party). Graphics-driver clean reinstall: our GPU driver crash fix guide (first-party). When it reboots instead of freezing: our PC keeps restarting guide (first-party). When it’s the network dropping rather than the whole PC locking up: our WiFi keeps disconnecting guide (first-party). When a game closes to the desktop instead of the whole PC freezing: our games keep crashing on PC guide (first-party).

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

Keyboard Not Working? Fix It by What Actually Broke (2026)

LK Wood IV — Sun, 05 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-05 · ~7 min read · St. Louis County, MO

“Keyboard not working” is really three different problems that people lump together, and the reason so many fix-lists fail is that they jump straight to “reinstall the driver” no matter which one you have. Sort your problem into one of these first, then jump to that section:

Dead — nothing types at all.
Typing, but wrong or laggy — characters are swapped, doubled, missing quick taps, or letters come out as numbers.
Partly working — some keys respond, others don’t.

The good news: in every case the keyboard itself is usually fine. Most of these are a setting or a driver, not dead hardware — the Microsoft support page for mouse and keyboard problems confirms the same order (checks, then drivers). Work your section top to bottom and stop when it types.

First: which of the three is it?

Open Notepad and try to type. If nothing appears, you’re in the Dead section. If characters appear but they’re wrong, doubled, or laggy, you’re in the Typing-but-wrong section — and that’s good news, because it’s almost never hardware. If some keys work and others don’t, skip to Partly-working.

One 15-second test settles the biggest question: plug the keyboard into another computer (or, for a laptop, plug in any cheap USB keyboard). If it works elsewhere, the fault is your PC’s software or ports — not the keyboard. If it fails everywhere, the keyboard is the suspect.

If it’s dead: nothing types at all

Give yourself a way to type first. You can’t do most fixes without input, so open the on-screen keyboard: press Windows Key + Ctrl + O, or click Start, type osk, and open On-Screen Keyboard with your mouse. Now you can click keys and work through the menus below while you fix the physical one.

Try a different port and cable (wired). Plug the keyboard directly into a rear USB port on a desktop — not a front-panel port or a hub — and try another cable if it’s detachable. A different port also rules out a single dead port.

Fresh batteries and a re-pair (wireless). Swap batteries, re-seat the USB receiver in a different port, and for Bluetooth remove the keyboard under Settings > Bluetooth & devices and pair it again.

Reinstall the keyboard driver. This clears the single most common “dead after an update” cause. Open Device Manager (Windows Key + X > Device Manager), expand Keyboards, right-click your keyboard, choose Uninstall device, and restart. Windows reinstalls the driver automatically on boot.

Disable Fast Startup. If the keyboard is dead on a cold boot but works after a full restart, Fast Startup is leaving the input stack half-initialized. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable, then uncheck Turn on fast startup and save. (This is the same fix that resolves a lot of USB-device-not-recognized cases — a keyboard is just a USB device.)

Run the keyboard troubleshooter if your build has one. Settings > System > Troubleshoot > Other troubleshooters — if a Keyboard entry is listed, click Run. (Microsoft has removed several legacy troubleshooters in recent Windows 11 24H2 builds, so don’t be surprised if it isn’t there — the steps above cover what it did anyway.)

Broke right after a Windows Update? That’s the most-reported trigger. Use the on-screen keyboard to reinstall the driver as above; if it started with a specific update, you can also roll that update back under Settings > Windows Update > Update history > Uninstall updates.

If it’s typing but wrong or laggy

This is the section people miss, and it’s almost never hardware.

Filter Keys — the “it suddenly feels broken” cause. If quick taps get ignored and you have to hold keys down for them to register, Filter Keys is on. Holding the right Shift key for about eight seconds is a built-in Windows shortcut that enables it — easy to trigger by accident. Filter Keys tells Windows to ignore brief or repeated key presses, which makes normal typing feel laggy or dead. Fix: Settings > Accessibility > Keyboard, and turn Sticky keys, Filter keys, and Toggle keys all off. While you’re there, turn off the keyboard-shortcut option so you can’t re-trigger it by leaning on Shift.

Wrong symbols (@ and " swapped, £ where # should be) — it’s the layout. Your keyboard language got switched, usually by Windows Key + Space or a stray hotkey. Press Windows Key + Space to cycle back to your correct layout (for example US), then remove the extra one under Settings > Time & language > Language & region so it can’t come back.

Laptop typing numbers instead of letters (u=4, i=5, o=6, j=1…). On laptops without a separate number pad, Num Lock overlays a number pad onto part of the letter keys. Press Fn + Num Lock (sometimes labeled NumLk) to switch it off and the letters return.

If only some keys work

Isolated dead keys after the settings above are usually physical. Power off, tip the keyboard, and clean under and around the stuck keys with a can of compressed air — crumbs and dust under a keycap are a common cause. If a cluster of keys died after a spill, that’s liquid damage to the membrane or switches, and the board usually needs replacing.

When it really is the keyboard

If it failed the another-PC test, cleaning didn’t help, and the settings above are all clear, the keyboard (or its cable) is the fault. A dead laptop keyboard is also the one case where you need an external one to keep working — and a cheap wired backup is worth having regardless. An inexpensive wired USB keyboard plugs in with no drivers or pairing, which also makes it the perfect tool for doing the Device Manager fixes above when your main keyboard is dead.

The short version

Sort the problem first: dead, typing-wrong/laggy, or partly working — the fix depends on it.
Dead: on-screen keyboard (Win + Ctrl + O) → different port/cable → reinstall the driver in Device Manager → disable Fast Startup.
Typing but wrong: it’s Filter Keys (hold right Shift 8s turns it on) or the wrong layout (Win + Space), not broken hardware. Laptops typing numbers = Fn + Num Lock.
The another-PC test tells you in 15 seconds whether it’s your PC or the keyboard.

Still fighting Windows peripherals? See our fixes for USB devices not recognized, an Xbox controller that won’t connect, and GPU driver crashes.

Source: Mouse and keyboard problems in Windows — Microsoft Support. Filter Keys, Fast Startup, the on-screen keyboard, and Device Manager are all standard built-in Windows features; the steps above use their default locations in Windows 11 and 10.

NetBird vs Tailscale (2026): The Self-Hosted Mesh VPN Question

LK Wood IV — Sun, 05 Jul 2026 00:00:00 -0500

If you have already decided a WireGuard mesh is how you will reach your homelab from anywhere, the next fork in the road in 2026 is often NetBird vs Tailscale - and the way it usually gets framed (“which mesh VPN is faster/better?”) points you at the wrong thing. Both are mesh VPNs built on WireGuard. Under the hood, when the connection is direct, they are running the same encryption at the same speed. The real difference is not the tunnel. It is who owns the control plane.

This is the focused two-way version of that decision, aimed at homelabbers. If you are still one step earlier - deciding between a managed mesh and raw WireGuard at all - start with Tailscale vs WireGuard or WireGuard vs OpenVPN for the homelab. If you want the Layer 2 virtual-switch option in the mix, see ZeroTier vs Tailscale. If you have landed on a mesh and just want the two leading options compared honestly, keep reading.

The 20-second answer

You are one person, you want it working in 15 minutes, and you never want to run a server: Tailscale. Its free Personal plan and zero-maintenance SaaS control plane are the right default for most homelabs in 2026.
You want to self-host the entire stack - control plane included - as an officially supported path, not a community workaround: NetBird. It ships its own open-source coordination server as a first-class product.
You are scaling to a team and per-user cost matters: lean NetBird. Self-hosting is free, and its cloud Team plan undercuts Tailscale per user.

Neither choice is a mistake. What follows is where they actually diverge.

Same engine, different brain

Both products share the same data plane: WireGuard, the small, fast, modern tunnel that has been the standard for point-to-point encrypted links since it landed in the mainline Linux kernel. Both also add the same category of things WireGuard deliberately leaves out - automatic key distribution, NAT traversal, stable addressing, and access policy. That shared “coordination layer” is why people compare them at all.

Where they split is the control plane - the coordination server that brokers keys, tracks which device is where, and distributes your policy:

Tailscale runs that control plane as a proprietary, fully managed service. You never operate a server. The client is open source; the brain is not. If you want the brain on your own hardware, the community answer is Headscale, a separate open-source reimplementation of Tailscale’s control server.
NetBird ships its own coordination server as open source, as a supported part of the product. You can use NetBird’s hosted cloud or self-host the complete stack, and self-hosting is a documented first-class path rather than a reverse-engineered one.

So “NetBird vs Tailscale” really means: do you want a managed brain you never touch, or the option to own the brain yourself without leaving the supported path?

The one question that usually decides it: do you want to run the control plane?

This is the axis everything else hangs on.

If the honest answer is “no, I never want to run or secure another server,” Tailscale is built for you. You install clients, log in with an identity you already have, and the tailnet coordinates itself forever. There is no control server in your life. For a huge share of homelabbers - one person, a NAS, a couple of Pis, a laptop and a phone - that is exactly the right trade, and the free tier covers it completely.

If the answer is “yes, I want the coordination server on my own hardware,” the comparison tilts toward NetBird. You can get there with Tailscale by running Headscale, and many people happily do. But Headscale is a third-party project chasing a moving proprietary target: feature parity lags, and you are on your own for support. NetBird self-hosting is the vendor’s own supported stack. If owning the control plane is a hard requirement rather than a nice-to-have, that distinction matters.

What self-hosting NetBird actually asks of you

Self-hosting is easy to say and real to run, so be clear-eyed about it. A self-hosted NetBird deployment is three services:

Management service - holds network state, assigns peer IPs, and distributes configuration updates.
Signal service - brokers peer negotiation by relaying encrypted connection candidates so peers can find each other.
Relay service - provides fallback connectivity (a TURN-style relay) when two peers cannot establish a direct path.

You also wire in an identity provider for login. NetBird documents a Docker-based install that stands all of this up together, so it is well within reach for anyone already running self-hosted apps - but it is a service you now own, patch, back up, and keep reachable. The upside is total control and no external dependency in your remote-access path. The downside is that if your management server is down when you are away from home, you cannot bring new peers online until it is back (existing tunnels keep flowing).

Tailscale’s equivalent operational cost is simply zero - unless you choose Headscale, at which point you have taken on a very similar self-hosting burden as NetBird, just with a less-supported control server.

Policy and day-to-day: UI vs ACL file

For daily driving, the biggest felt difference is how you express access rules.

NetBird leans on a web UI with groups and policies - you build access rules with dropdowns and toggles, and assign peers to groups that automate routing and permissions. For people who do not want to think in config syntax, this is friendlier, and it scales cleanly as the number of peers grows.

Tailscale centers on the tailnet policy file, written in HuJSON (JSON with comments). It is powerful and version-controllable, and infrastructure-minded users often prefer having their whole access model as code in a file. But it does ask for comfort with ACL syntax, and a fat-fingered rule is edited in text, not clicked.

Neither is objectively better - it is a genuine UI-vs-config-file preference. If you like GitOps-style policy-as-code, Tailscale fits your hands. If you want to hand a teammate a console and dropdowns, NetBird does.

Performance: effectively a tie where it matters

When either product establishes a direct peer-to-peer connection - which both do the large majority of the time - you are running WireGuard in both cases, so throughput and latency are essentially the same. NetBird’s own engineering write-ups concede this: on a shared regional network path, direct P2P WireGuard performance is functionally identical across these tools.

The only honest performance caveats are at the edges:

NAT traversal reliability. Both use STUN/ICE-style hole punching plus a relay fallback. In a hard CGNAT environment, how often each achieves a direct path (versus relaying) is the thing that actually affects your speed, and it varies by network more than by product.
Relay fallback. When a direct path is impossible and traffic rides a relay, expect added latency and reduced throughput on that link until a direct route is found. This is true of both.

Bottom line: for SSH, web UIs, file transfers, and media streaming - the actual homelab workload - performance is not the deciding factor between these two. Do not pick on benchmarks; pick on control-plane ownership and cost.

Cost, especially at scale

For a single user, both are free and cost is a non-issue: Tailscale’s Personal plan is free for up to 6 users with a generous device allowance, and NetBird’s cloud free tier covers up to 5 users and 100 machines. Self-hosted NetBird is free at any size.

The gap opens when you grow a team on the hosted clouds. NetBird’s paid Team plan starts around $6 per user per month; Tailscale’s Standard plan is $8 per user per month, and its Premium tier (which is where some advanced identity features live) is $18 per user per month. NetBird also puts SSO and advanced policy on lower-cost tiers than Tailscale does. If you are outfitting a company rather than a homelab, that per-seat difference compounds - and self-hosting NetBird takes the per-seat cost to zero, trading it for the operational cost of running the stack.

The extras that can tip a close call

If control-plane philosophy and cost leave you undecided, two NetBird features can break the tie:

Post-quantum encryption via Rosenpass. NetBird can layer Rosenpass in front of WireGuard to defend against future quantum “harvest now, decrypt later” attacks. It is opt-in and off by default. Tailscale does not currently expose a comparable option. For almost every homelab this is theoretical, but if it is on your list, it is a real point for NetBird.
Built-in reverse proxy with automatic TLS. NetBird includes ingress that can expose an internal service over a custom domain with auto-issued Let’s Encrypt certificates. Tailscale’s nearest analog is Funnel, which exposes a node to the public internet more simply but with less of a full reverse-proxy story. If publishing a self-hosted app is part of your goal, NetBird bundles more of that in one place.

Side-by-side

	NetBird	Tailscale
Data plane	WireGuard	WireGuard
Control plane	Open source, self-host or cloud	Proprietary, managed (or Headscale to self-host)
Officially supported self-hosting	Yes (management + signal + relay)	No (Headscale is community)
License	BSD-3-Clause; server dirs AGPLv3	Client open source; control plane closed
Free tier	5 users, 100 machines (cloud); free self-hosted	6 users, generous device allowance
Paid entry price	~$6 / user / mo (Team)	$8 / user / mo (Standard)
Policy model	Web UI, groups + dropdowns	HuJSON ACL policy file
Post-quantum option	Yes (Rosenpass, opt-in)	Not currently
Built-in reverse proxy	Yes (auto-TLS ingress)	Funnel (simpler exposure)
Direct-connection performance	WireGuard (tie)	WireGuard (tie)
Best for	Owning the whole stack, cheaper team scaling	Zero-maintenance homelab, fastest time-to-working

So which should you run?

Pick Tailscale if you are one person or a small household, you want remote access working today with nothing to operate, and you value time-to-working over owning infrastructure. For most homelabbers in 2026, the free Personal plan is the correct default, and Headscale is there later if you ever want the brain on your own hardware.
Pick NetBird if self-hosting the control plane is a real requirement and you want it on a supported path rather than a community reimplementation, if you are scaling a team where per-user cost matters, or if features like its reverse proxy or Rosenpass post-quantum tip the balance.
Consider Tailscale plus Headscale if independence from a SaaS control plane is the only reason NetBird was appealing - it keeps the polished Tailscale clients while moving the brain to your hardware, at the cost of running a less-supported server.

Whichever you land on, the encryption underneath is the same WireGuard, and the raw speed is a tie. You are really choosing who runs the coordination server - a managed service, a community control plane, or you.

ZeroTier vs Tailscale (2026): Layer 2 Switch or Plug-and-Play Mesh?

LK Wood IV — Sun, 05 Jul 2026 00:00:00 -0500

If you want your devices to reach each other from anywhere in 2026 - your NAS from a coffee shop, your desktop from your phone, a friend’s server across the country - Tailscale and ZeroTier are the two mesh networks you keep running into. Both create a private overlay where every device gets a fixed address and can talk to every other device without port forwarding, even behind carrier-grade NAT.

They look interchangeable from the outside. They are not. The difference sits one layer down in the network stack, and it decides which one is right for you. This is the focused two-way version of that decision, written for homelabbers rather than enterprise network teams.

The 20-second answer

You want the simplest possible secure remote access across a pile of roaming devices, with as little setup as possible: Tailscale. It is the right default for most people in 2026, and its free tier now stretches further than ZeroTier’s.
You need a real flat LAN across the internet - broadcasts, multicast, Wake-on-LAN, legacy LAN apps, or bridging - or you run MikroTik gear: ZeroTier. Its Layer 2 design does things Tailscale structurally cannot.
You want to own the entire control plane on your own hardware: lean toward Headscale (self-hosted Tailscale control server) or NetBird rather than either default, because ZeroTier’s self-hosting story got more restrictive in 2026.

Neither is a mistake. What follows is where they actually diverge.

The one thing that explains every other difference: Layer 3 vs Layer 2

This is the root of the whole comparison, so it is worth getting right.

Tailscale is a Layer 3 (IP-level) VPN. It is built on the WireGuard protocol and adds a coordination layer on top: it distributes keys between your devices automatically, punches through NAT so they find each other, hands every device a stable 100.x.x.x address plus a MagicDNS name, and enforces access policy. It moves IP packets between devices that now know how to reach each other. It does not stretch your local network across the internet - each device is its own island that can route to the others.

ZeroTier is a Layer 2 (Ethernet-level) virtual switch. Instead of routing IP packets, it emulates a physical network switch in software: every device you join to a ZeroTier network behaves as if it were plugged into the same switch, on the same flat LAN, even when the machines are in different countries. Because it works at the Ethernet layer, it carries the things a real switch carries - broadcasts, multicast, ARP, and non-IP protocols - not just IP traffic.

That single architectural choice cascades into everything else:

Need broadcast or multicast (LAN game discovery, some IoT protocols, Wake-on-LAN across sites, legacy software that assumes one subnet)? That is Layer 2 - ZeroTier.
Just need “my devices can reach each other by IP or name, securely, from anywhere”? That is Layer 3, and it is simpler - Tailscale.

Everything below is a consequence of this.

Setup and day-to-day ease: Tailscale wins clearly

Every strand of community feedback lands the same way here. On the r/zerotier thread comparing the two, the recurring line from people who use both is that Tailscale “just works” and that non-networking users get it running in minutes.

Tailscale’s onboarding is: install the client, sign in with an existing identity provider (Google, Microsoft, GitHub, and others), and the device is on your tailnet. NAT traversal, key exchange, and DNS are handled for you. There is very little to misconfigure.

ZeroTier is more hands-on. You create a network, get a 16-digit network ID, join devices with that ID, and then manually authorize each device in the controller. Its power lives in a flow-rules engine and managed IP assignment that give you fine control - but that control is also more to learn and more to get wrong. As one longtime ZeroTier user put it, it is “more complicated, both the language and the stateless nature of the rules engine,” but that complexity buys flexibility.

If your priority is minimal friction, Tailscale is the easier tool by a wide margin. If you enjoy - or need - to shape the network by hand, ZeroTier gives you more surface to work with.

Speed: close enough that it rarely decides anything

Both establish direct peer-to-peer links when they can and fall back to relays when they cannot. Tailscale’s WireGuard data plane has marginally less overhead than ZeroTier’s custom protocol, and Tailscale’s own comparison notes throughput is “similar” in most environments with the theoretical edge to WireGuard rarely noticeable in practice.

The more real-world distinction from the community: Tailscale is generally a little better at finding a direct connection through difficult NAT rather than routing you through a relay, which makes it feel faster more often. ZeroTier, on the other hand, is reported to be less blocked in countries that filter VPNs and to offer connection aggregation - edges that matter for specific situations more than raw benchmarks.

Bottom line: on an established tunnel over a normal home connection, treat them as a tie. Do not pick on speed alone.

The free tier: this is where the story changed in 2026

This is the single fact most existing comparisons - and Google’s own AI summary - still get wrong, because both tools moved their free tiers.

Tailscale Personal (free): up to 6 users with an unlimited device allowance for non-commercial use, including peer-to-peer connections, subnet routers, exit nodes, and MagicDNS. For a solo homelab that keeps adding machines, this is effectively uncapped.
ZeroTier (free): 10 devices, 1 network, 1 administrator - down from the more generous caps of earlier years. Its paid Essential tier starts at 18 dollars per month (10 devices plus 2 dollars per extra device), and Scale jumps to 179 dollars per month for 100 devices.

For comparison, Tailscale’s paid plans are Standard at 8 dollars per user per month and Premium at 18 dollars per user per month - but most homelabbers never leave the free Personal plan.

The practical takeaway: if you are a single person adding your eleventh device, ZeroTier’s free tier now stops you and Tailscale’s does not. A ZeroTier user on r/zerotier summed up the direction bluntly - they wanted to move away because “their free tier is getting restrictive.” Verify the current numbers on each vendor’s pricing page before you commit, since this is exactly the kind of limit that changes.

Self-hosting and the 2026 licensing worry

If you like to own your infrastructure, read this section carefully, because the ground shifted under ZeroTier.

Historically, ZeroTier’s appeal for the self-hosting crowd was that you could run your own controller and even your own root nodes (moons) and depend on nobody. In recent 2026 releases that story tightened: the client remains open source, but running your own controller for organizational use has moved toward paid licensing, and moons have been curtailed. The r/zerotier discussion is full of longtime users who are, in their words, worried about the direction and actively looking at alternatives - NetBird and Netmaker come up repeatedly as the WireGuard-based landing spots.

Tailscale’s control plane is proprietary as a service, but the escape hatch is healthier: Headscale is a mature open-source implementation of the Tailscale coordination server, so you can keep the polished Tailscale clients and run the brains on your own box. If self-hosting the whole stack matters to you, that combination - or a fully open project like NetBird - is currently the more predictable bet than pinning your future to ZeroTier’s controller licensing.

Where ZeroTier still genuinely wins

Do not read the above as “just use Tailscale.” ZeroTier holds real, structural advantages that Tailscale cannot match by design:

True Layer 2 features: broadcast, multicast, and non-IP traffic ride the ZeroTier network as if every device were on one switch. Wake-on-LAN across sites, LAN-discovery-dependent apps, and bridging a remote device onto your home subnet are ZeroTier’s home turf.
MikroTik native support: ZeroTier runs natively on MikroTik routers, so the RouterOS crowd can run the controller and client directly on the router. This came up again and again from the “full MikroTik” homelabbers, and it is a real reason to choose ZeroTier if that is your gear.
No forced identity provider: you can sign up with any email. Several people specifically prefer ZeroTier because it does not require linking machines to a Google, Microsoft, or Apple account - a genuine privacy and independence angle that Tailscale’s SSO-first model does not offer out of the box.
Simultaneous multi-network membership: a device can belong to several ZeroTier networks at once natively; doing the equivalent on Tailscale takes more work.
CGNAT resilience: ZeroTier is reliable behind carrier-grade NAT and, per community reports, is sometimes less aggressively blocked in restrictive networks.

If any of those describe your situation - especially the Layer 2 requirements or MikroTik hardware - ZeroTier is not just viable, it is the correct answer.

Side-by-side

Factor	Tailscale	ZeroTier
Network layer	Layer 3 (IP VPN)	Layer 2 (virtual Ethernet switch)
Protocol	WireGuard	Custom ZeroTier protocol
Setup ease	Very easy, SSO, zero-config	More technical, manual authorization + rules
Free tier (2026)	6 users, unlimited devices	10 devices, 1 network
Paid entry	8 dollars/user/mo (Standard)	18 dollars/mo (Essential)
Broadcast / multicast / WoL	No (Layer 3)	Yes (Layer 2)
MikroTik native	No	Yes
Auth	Identity provider (SSO) required	Any email; machine keys
Self-host control plane	Headscale (open source)	Controller, now more restricted
Best at	Simplest secure remote access	Flexible flat-LAN emulation

Who should pick which

Choose Tailscale if you want secure remote access to your devices with the least possible effort, you are happy signing in through an identity provider, you keep adding devices (that free tier), or you want a clean self-hosting escape hatch via Headscale. For the majority of homelabbers whose goal is “reach my stuff from anywhere, securely, without fuss,” this is the default. Our Tailscale remote-access homelab guide walks the full setup.

Choose ZeroTier if you need Layer 2 behavior (broadcasts, multicast, Wake-on-LAN, legacy LAN apps, bridging), you run MikroTik gear, you want to avoid a forced identity provider, or you specifically want a flat LAN stretched across sites. Just go in aware of the smaller free tier and the tightening self-hosting story.

Choose neither, and look at Headscale or NetBird, if owning the complete control plane on your own hardware is non-negotiable - that is the cleanest path in 2026.

Still weighing the underlying options rather than these two managed meshes? Start with Tailscale vs WireGuard for the raw-protocol-versus-coordination-layer decision, or the broader homelab firewall and router stack if you are planning the whole edge.

1440p vs 4K Gaming in 2026: Is 4K Worth It?

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-04 · St. Louis County, MO

The short answer: 1440p is the sweet spot for most gamers in 2026, and 4K is worth it only if you have both a flagship GPU and a big screen. 1440p at 27 inches gives you sharp image quality that a mainstream card can actually drive at high frame rates; 4K rewards a 32-inch-plus panel and an RTX 5080-class GPU. This guide gives the real pixel math behind the gap, the GPU you need for each resolution, and exactly when 4K earns its cost.

Why 4K is so much harder to run

Start with the numbers, because they explain everything downstream:

1080p = 1920 x 1080 = 2.07 million pixels
1440p = 2560 x 1440 = 3.69 million pixels (1.78x of 1080p)
4K = 3840 x 2160 = 8.29 million pixels (2.25x of 1440p, 4x of 1080p)

Your GPU has to shade every one of those pixels every frame, so 4K asks for roughly 2.25 times the graphics work of 1440p for the same frame rate. That’s not a small tax - it’s the difference between a card cruising and a card struggling. In practice a demanding ray-traced game that a flagship like the RTX 5080 runs at well over 100 fps at 1440p can fall to roughly half that at native 4K on the very same card. The resolution alone - not a slower GPU - is what moved the frame rate.

The GPU you need for each resolution

This is where most “which resolution” advice goes wrong: it treats the monitor as the decision when the GPU is the real gate. Here’s the 2026 mapping:

Resolution	GPU class you want
1440p high-refresh	RTX 5070 / RX 9070 XT (the sweet spot)
4K upscaled (DLSS 4 / FSR 4)	RTX 4080 / RTX 5070 and up
4K native, high frame rate	RTX 5080 or better

Cards like the RTX 4070 and RX 7800 XT are fundamentally 1440p GPUs - they can output a 4K signal, they just can’t hold the settings and frame rates most players want there. Pair a mid-range card with a 4K monitor and you’ll end up either dropping settings hard or leaning entirely on upscaling. To see where a specific card lands, the GPU Comparison Tool and the best GPUs for 4K gaming guide put the raw performance next to the resolution it’s meant for.

When 4K is worth it - and when 1440p wins

Choose 4K if you:

Own a flagship GPU (RTX 5080 or better).
Use a 32-inch or larger screen, where the extra sharpness is clearly visible.
Prioritize visual fidelity, HDR impact, and single-player immersion over maximum frame rate.

Choose 1440p if you:

Have a mid-range GPU (RTX 5060-5070 class).
Use a 27-inch monitor - the size where 1440p already looks sharp.
Value high refresh rates and competitive frame rates, or want your GPU to last longer before it feels slow.

Screen size is the quiet deciding factor. On a 27-inch panel at a normal desk distance, 1440p’s pixels are already small enough that 4K’s upgrade is subtle; on a 32-inch-plus screen, 4K’s extra density is obvious. You can check the exact pixel density for any size and resolution with the PPI Calculator before you buy.

Upscaling changes the math (a bit)

DLSS 4 and FSR 4 render the game at a lower internal resolution and reconstruct it up to 4K, which cuts the GPU cost meaningfully and is what makes 4K practical on an RTX 4080/5070 rather than only a flagship. It’s genuinely good in 2026 - but it doesn’t erase the gap, and native 4K still asks for a top-tier card. If you’re counting on upscaling to make 4K work on a mid-range GPU, treat it as a helpful boost, not a magic fix; the DLSS vs FSR breakdown covers what each does well.

Don’t forget VRAM and the monitor cost

Two costs beyond the GPU core:

VRAM. 4K’s high-resolution frame buffer and textures eat graphics memory - 16GB is the sensible minimum for 4K, where 1440p is comfortable on 12GB. A fast card starved of VRAM stutters at 4K; the how much VRAM you need guide has the full breakdown.
The monitor. 4K panels cost more than equivalent 1440p ones, and a high-refresh 4K monitor plus the GPU to feed it is a serious combined spend. 1440p high-refresh is the value sweet spot on the display side too.

The verdict

Most gamers: 1440p at 27 inches with an RTX 5070 / RX 9070 XT-class card. Best balance of sharpness, frame rate, and cost.
Visual-fidelity-first, big screen: 4K at 32 inches-plus with an RTX 5080 or better (16GB+ VRAM). Worth it when the hardware matches.
Competitive / budget: 1080p is still fine for 240Hz+ esports or a tight budget.
The rule: pick the resolution your GPU is built for, not the biggest number. A 1440p card on a 4K screen is a worse experience than the same card on the 1440p screen it was made for.

4K is more attainable than ever in 2026, but “attainable” still means a flagship GPU and a big screen. For the money most people spend, 1440p delivers the better all-round result - which is exactly why it’s the resolution to beat.

Sources

2026 resolution/GPU-class guidance (1440p sweet spot, 4K GPU tiers, upscaling break-even) synthesized from current testing roundups. The ~2.25x 4K-over-1440p GPU cost is exact pixel-count arithmetic (8.29M vs 3.69M pixels); the real-world frame-rate hit scales roughly with it.
First-party tools and guides: GPU Comparison, best GPUs for 4K gaming, how much VRAM you need, and the PPI Calculator.

Guidance is for mid-2026; GPU classes and monitor prices shift, so confirm current benchmarks for the specific card and games you play. Found an error? Email hello@techfuelhq.com with the article URL.

Forgejo vs Gitea 2026: Which Self-Hosted Git to Pick

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

If you’re standing up a self-hosted Git server in 2026, the two names you’ll weigh are Forgejo and Gitea — and they’re no longer the same thing wearing different logos. Forgejo began as a friendly fork of Gitea, became a hard fork in early 2024, and has been diverging ever since. So the real question isn’t “which logo do I like,” it’s “which project do I want to run for the next five years.” Here’s how they actually compare in 2026 on the things that decide it — governance, licensing, federation, and migration — verified against each project’s own documentation.

The two at a glance

	Forgejo	Gitea
Governance	Codeberg e.V. (non-profit, community-led)	For-profit company (Gitea Ltd), Open Core
License	GPLv3+ (since v9.0; MIT before)	MIT + commercial edition
Fork status	Hard fork since early 2024	Original project
Federation (ActivityPub)	In active development	None (as of Dec 2024)
CI/CD	Forgejo Actions	Gitea Actions
Upgrade / accessibility tests	Yes (e2e + browser a11y)	Not as of mid-2025
Migration	Drop-in from Gitea ≤ v1.22 → Forgejo v10	—
Best for	Community governance, federation, homelab	MIT license, Gitea Enterprise features

Both are lightweight, single-binary Git forges that run happily on a mini PC or a small VM, both do issues/PRs/wiki/releases/CI, and both are far lighter than GitLab. The differences below are about who controls the project and where it’s going, not about whether it can host your repos — either one can.

Why Forgejo exists: the governance split

This is the part that started everything. In 2022, the Gitea project’s domain name and trademark were transferred to a newly-formed for-profit company (Gitea Ltd) — by the community’s account, without prior knowledge or approval. A group of maintainers and contributors who wanted the project to stay community-governed responded by creating Forgejo in December 2022, hosted under Codeberg e.V., a registered German non-profit. Forgejo’s stated priority is “the interest of the general public”; its criticism of Gitea is that a for-profit owner makes decisions “to maximize profit rather than favor the interest of the general public.”

In 2026, Forgejo governance is a formal, documented structure — community elections, transparent roadmap, public decision-making. Gitea, by contrast, runs an “Open Core” model: the core is MIT-licensed, but the company also develops non-free components and (per Forgejo’s comparison) requires copyright assignment even for MIT-licensed contributions. Neither model is inherently wrong — a company-backed project can ship features and support that a volunteer non-profit can’t always match — but they pull in different directions, which is exactly why the fork became a hard fork.

Licensing: MIT vs GPLv3+ (and why it probably doesn’t affect you)

Gitea is MIT-licensed — maximally permissive, meaning anyone (including a company) can take the code, modify it, and ship it in a closed product. Forgejo was MIT too, up to and including its v8 series. Starting with its v9.0 release (2024), Forgejo relicensed to GPLv3-or-later — a copyleft license. Every version up to and including the v8 series was MIT.

The stated reason: to keep Forgejo’s code from being pulled back into a commercially-controlled Gitea. So the license divergence is really the governance dispute expressed in legal terms.

For a homelab user, this is invisible. GPLv3 only creates obligations when you distribute a modified version of the software — running Forgejo for yourself, your family, or your team triggers none of them. The license matters if you’re a business planning to build and sell a closed product on top of the code (MIT lets you; GPLv3 doesn’t), or if you have a philosophical preference for copyleft over permissive. Otherwise, both are genuinely Free/Open-Source and you can ignore this section.

Where they actually differ now

Since the hard fork, the codebases have drifted. The concrete, verifiable differences in 2026:

Forge federation (Forgejo’s flagship bet). Forgejo is actively implementing ActivityPub-based forge federation — the ability for issues, pull requests, and stars to work across independent instances, the way Mastodon federates social posts. Progress is public with monthly reports. Gitea has no federation effort. If a “self-hosted but not isolated” future appeals to you, this is Forgejo’s single biggest differentiator.
CI/CD. Both ship a GitHub-Actions-compatible runner — Forgejo Actions and Gitea Actions — so your .github/.forgejo workflows and existing actions largely just run. Forgejo notably develops and releases itself using Forgejo Actions (dogfooding); Gitea develops on GitHub.
Testing and accessibility. Per Forgejo’s own comparison, Forgejo maintains end-to-end tests, upgrade tests, and browser tests that include accessibility checks; Gitea, as of mid-2025, did not have end-to-end or upgrade tests and only an example browser test. For an app you’ll upgrade for years, upgrade-test coverage is a quiet but real reliability signal.
Development stack. Forgejo is developed on Codeberg (itself Forgejo) with localization via Weblate; Gitea is developed on GitHub with localization via Crowdin. A values signal more than a feature, but it’s real.

What has not meaningfully diverged: the core self-hosting experience. Repo hosting, the web UI, issues, PRs, wiki, packages, and releases are still very similar, because they share the same origin. This is why the choice is about trajectory, not day-one features.

Compatibility and migration — the practical part

Here’s the reassuring news for anyone already on Gitea: Forgejo is still designed to be a drop-in replacement. The projects remain compatible at the database and API level, and Forgejo publishes an official Gitea-migration guide. The supported path is:

Upgrade from any Gitea version up to and including v1.22.x to Forgejo v10.0.x — done in two steps.

In practice that means: back up your Gitea database and data directory, then run the matching Forgejo release pointed at the same data — no re-cloning repositories, no re-creating users. If you’re on a newer Gitea than v1.22, upgrade within Gitea to a compatible point first, then cross over.

The honest caveat: this is effectively a one-way door now. Because Forgejo has diverged (and relicensed) since the hard fork, there’s no supported route to migrate a modern Forgejo instance back to Gitea. That’s not a reason to avoid the move — it’s a reason to make the decision deliberately and keep a backup of your pre-migration state. If you’re running Gitea as part of a Docker Compose homelab stack, the swap is mostly a change of image and a data backup.

Which should you run?

New homelab or small-team forge, no existing instance → Forgejo. You get the same lightweight experience plus non-profit governance, copyleft licensing, upgrade/accessibility testing, and the federation roadmap. It’s the lower-risk long-term bet for a project you don’t want a company to be able to close.
You specifically need Gitea’s commercial “Enterprise” features, or you’re building a product on top and want the permissive MIT license → Gitea.
You already run a stable Gitea and nothing hurts → there’s no urgency. Gitea is still open and maintained. Migrate when you next do a major upgrade, or when a Forgejo feature (federation, an Actions improvement) actually pulls you.

Self-hosted Git is one of the highest-value things you can pull off SaaS — it’s a core piece of the self-hosted stack that replaces rented tools, and it runs fine in a container next to everything else. Whichever you pick, you’re keeping your code on infrastructure you control, and deciding whether to run it in a container or a VM is the next call.

The honest verdict

In 2026 this is a good-vs-good decision, not a rescue. Both Forgejo and Gitea are excellent, lightweight, genuinely open self-hosted Git forges, and either will serve a homelab well. The tiebreakers are about governance and direction: Forgejo is the pick if you want a community-controlled, non-profit-governed project with copyleft protection and a federated future, and it’s my default recommendation for anyone starting fresh. Gitea remains the right call if you need its commercial features or the permissive MIT license, or if you’re simply happy where you are.

One thing I won’t fake: resource footprint. Because Forgejo and Gitea share a common Go codebase, their memory and CPU use are effectively identical — both idle in the low hundreds of megabytes and scale with your repo count and CI usage, not with the logo. Anyone quoting a dramatic footprint gap between the two is guessing; run whichever you choose and watch it on your own box.

Sources

Forgejo — official comparison with Gitea (governance, license, federation, testing): https://forgejo.org/compare-to-gitea/
Forgejo — Gitea migration guide (supported Gitea ≤ v1.22 → Forgejo v10 path): https://forgejo.org/docs/v10.0/admin/gitea-migration/
Forgejo relicenses to GPLv3+ (v9.0; rationale): LWN.net · https://forgejo.org/2024-02-forking-forward/
Forgejo becomes a hard fork of Gitea (governance record): https://codeberg.org/forgejo/governance/issues/58
Forgejo — Wikipedia (origin December 2022, Codeberg e.V.): https://en.wikipedia.org/wiki/Forgejo

How Much RAM Do You Need in 2026? Gaming, Work, and the Shortage

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-04 · St. Louis County, MO

The short answer for a new PC in 2026: 32GB is the baseline, 16GB is the budget floor, and 64GB is for specific heavy workloads - VMs, serious content creation, or local AI. That is the same conclusion Microsoft, PC Gamer, and most of the build community landed on this year. The honest complication is that a DRAM shortage has tripled RAM prices, so the real question is no longer “how much can I afford” - it is “how much do I actually need, so I do not overpay for capacity I will never use.”

This guide answers that by use case, with the reasoning behind each number, so you can size RAM for your build instead of guessing. Here is the whole decision as a ladder — find the rung that matches what you actually do.

The 2026 RAM ladder

Buy for the rung you live on — not the one above it.

16GB

Floor

Office, web, streaming video, light use

Still playable for esports and older games with a clean background. The budget-shortage choice, not the comfortable one.

32GB

Baseline ★

Gaming builds · gaming + streaming · heavy multitasking

The 2026 default. Absorbs the OS, background apps, and modern engines without swapping — and smooths the 1% lows you actually feel. The tier worth paying for even in the shortage.

64GB+

Specialist

VMs · 4K video / big photo catalogs · local AI in system RAM

Bought for a workload that genuinely pins >32GB — never for gaming, where it sits idle. Priciest and scarcest tier in the shortage.

Gaming alone tops out its usefulness at 32GB. Everything above is a non-gaming workload decision.

techfuelhq.com · 2026

The 2026 baseline, and why it moved

For years the answer to “how much RAM do I need” was 16GB, and it was a comfortable answer. It stopped being comfortable in 2026 for three reasons that have nothing to do with raw frame rate:

Windows got hungrier. A clean Windows 11 install idles at roughly 3 to 4GB with nothing open, and in normal use - a browser, Discord, a few tray apps - the OS and background overhead commonly sit around 4 to 6GB before you launch a game.
Game engines got hungrier. Modern titles across every big engine now reserve well over 16GB at high settings. Testing outlets through 2026 have measured demanding releases such as Indiana Jones and the Great Circle (id Tech 7) and Dragon Age: The Veilguard (Frostbite) using comfortably past 16GB of system RAM at high settings and 1440p — and Unreal Engine 5 titles trend the same way.
The messaging caught up. In 2026 Microsoft published a Windows gaming support doc calling 16GB the “practical starting point” and 32GB the “no-worries” upgrade for anyone running Discord, a browser, or a stream alongside their games - then removed it within days after backlash that pushing 32GB during a price spike was tone-deaf (Windows Latest). The recommendation was sound; the timing collided with the shortage.

So the baseline moved to 32GB not because games suddenly need double the frame-rate memory, but because the headroom math changed: subtract 4-6GB for the OS and 12-20GB for a modern game, and a 16GB machine is out of room while a 32GB machine still has slack. It is easier to see than to describe.

Where your RAM actually goes

Same load: Windows 11 + a modern game + Discord, a browser, and a stream (~21GB).

32GB

Modern game

Free · 11GB

16GB

Game

SSD
swap

▲ over capacity → stutter

The workload is identical. A 32GB machine still has ~11GB of slack; a 16GB machine runs out and spills the overflow to the SSD — which you feel as micro-stutter and pop-in, not as a lower average FPS.

techfuelhq.com · OS ~5GB, modern game ~16GB (figures from this guide)

How much RAM by use case

Use case	Buy	Why
Office, web, streaming video, light use	16GB	Comfortable for everyday tasks and the OS overhead.
Gaming (new build, 2026)	32GB	The baseline. Absorbs the OS, background apps, and modern engines without swapping.
Gaming + streaming / heavy multitasking	32GB	Streaming, a browser, and a game at once is exactly what fills 16GB.
Content creation (video, large photo catalogs)	32-64GB	Editors and large projects benefit past 32GB; 64GB for 4K timelines and big catalogs.
Virtual machines / homelab workstation	64GB+	Each VM reserves real RAM; a homelab box fills fast.
Local AI models in system RAM	64-128GB	Model weights live in RAM when they do not fit in VRAM.

The pattern: gaming alone tops out its usefulness around 32GB, and everything above that is bought for a specific non-gaming workload, not for frames.

The 32GB kit to buy

For a gaming or all-round build, a 32GB (2 × 16GB) DDR5-6000 CL30 kit is the pick — the AM5 sweet spot that's also fine on Intel. Proven options on the AMD QVL:

G.Skill Flare X5 32GB DDR5-6000 CL30 EXPO — the AM5 default pick. Check price on Amazon →
Corsair Vengeance 32GB DDR5-6000 — broad compatibility, RGB option. Check price →

Prices move week to week in the 2026 RAM shortage, so check current pricing before buying. For 64GB, Intel-tuned kits, or the full breakdown, see the DDR5 RAM buying guide.

Is 32GB of RAM enough?

For almost everyone building or upgrading in 2026, yes. Gaming, everyday work, and heavy multitasking all sit comfortably inside 32GB, and it is the tier worth paying for even with the shortage inflating prices. The reason is headroom, not raw speed: after Windows 11 and background apps take their 4-6GB and a modern game reserves 12-20GB, a 32GB machine still has slack for Discord, a browser, and a stream at the same time - the exact load that pushes 16GB into swapping.

It also holds up over time. Because 16GB became the floor game developers design around, system-RAM demand from new titles has crept up slowly rather than doubling, so 32GB should stay comfortable for gaming for years. What actually pushes people past 32GB is not newer games - it is a change in workload: running several virtual machines, editing 4K video or large photo catalogs, or loading local AI models into system RAM. Those are the cases where 32GB stops being enough and 64GB earns its price (covered in the next section). If none of them describe you, 32GB is the ceiling worth buying - and the money above it is better spent on the GPU or a faster CPU.

Is 16GB enough for gaming in 2026?

It depends on what else is running. For pure gaming at 1080p in esports titles and older games, with a clean background, 16GB still plays fine. Two things break it:

Modern AAA, especially Unreal Engine 5. These engines reserve more system RAM than older ones. On 16GB the system fills up and starts swapping to the SSD, which shows up as texture pop-in, micro-stutter, and “alt-tab lag” - not as a lower average FPS.
Multitasking. Discord, a browser with tabs, a second monitor with a YouTube video, or a stream - each takes a bite, and on 16GB the game is competing for what is left.

This is the key nuance the benchmark headlines miss: 16GB and 32GB post similar average FPS in most games, but 32GB has clearly better 1% and 0.1% lows - the frame-time consistency you actually feel. If you want to see how your specific CPU and GPU balance out at your resolution, the PC Bottleneck Calculator shows which part limits you first; RAM headroom is the quiet third factor underneath it.

Bottom line: 16GB is enough to start, and it is a defensible budget choice in the shortage. It is not the comfortable choice for a new 2026 build.

32GB vs 64GB: where more stops helping

For gaming, 64GB shows essentially no benefit over 32GB - the extra capacity sits idle. 64GB earns its price only for workloads that genuinely reserve more than 32GB:

Running several virtual machines at once (a Proxmox or homelab workstation).
Video editing 4K timelines, or large Lightroom / photo catalogs.
Compiling large codebases.
Loading local AI models into system RAM when they do not fit in GPU VRAM.

If none of those describe you, 32GB is the ceiling worth paying for. And in 2026 specifically, 64GB kits carry a disproportionate shortage premium and are frequently out of stock, so “buy 64GB to be safe” is the expensive mistake this year - buy it for a real workload, not a hunch.

The part nobody wants to talk about: the price

Sizing RAM in 2026 is really a budgeting decision, because a DRAM shortage - the same one raising hard-drive and SSD prices - has pushed memory to roughly three to four times its 2024-2025 lows. A 32GB DDR5-6000 kit that ran around $95-130 in early 2026 now sits closer to $420-480, and 64GB kits are scarcer and pricier still (verified pricing and specific kit picks are in the DDR5 RAM buying guide).

That changes the advice in two practical ways:

Do not over-buy. The old “just get 64GB for future-proofing” logic doesn’t hold when 64GB costs what a GPU used to. Buy the tier your workload actually uses.
A staged 16-to-32 plan is legitimate. On a tight budget, a single 16GB stick now and a matching second stick later is a reasonable way to spread the cost - as long as you buy a board with a free slot and a kit you can match. (One caveat on AMD: four DIMMs can drop your stable memory speed, so prefer a 2x16GB kit over 4x8GB when you get to 32GB.)

If you are speccing a whole system around your RAM budget, the 2026 gaming PC build guide and the PC Builder balance the memory decision against the CPU and GPU so you don’t starve the parts that move frame rates most.

The verdict

Everyday / office use: 16GB is comfortable.
New gaming build in 2026: 32GB. It is the baseline for a reason - headroom for the OS, background apps, and modern engines, with far smoother 1% lows than 16GB.
Tight budget: 16GB now is defensible in the shortage; plan a matching second kit later and leave a slot open.
VMs, heavy content creation, local AI: 64GB, and only 96-128GB if a real workload pins it.
Gaming and nothing else: 64GB is overkill - the money is better spent on the GPU or a faster CPU.

The 2026 twist is cost, not capability. RAM is expensive right now, so the win is buying exactly what your use case needs - which for most people building to game is 32GB, and for most people upgrading on a budget is a smart 16GB-to-32GB path - and putting the savings where you will actually feel them.

Sources

Microsoft Windows gaming guidance (the 2026 “Gaming Features” support doc, later removed after backlash), as reported by Tom’s Hardware, Windows Latest (recommendation), and Windows Latest (removal).
PC Gamer and TechSpot 2026 RAM testing (16GB vs 32GB average FPS vs 1% lows; UE5 memory use).
First-party pricing and kit selection: the TechFuelHQ DDR5 RAM buying guide and 2026 RAM & SSD price crisis.

Guidance is for a US audience in mid-2026; RAM prices move week to week during the shortage - check current retailer pricing before buying. Found an error? Email hello@techfuelhq.com with the article URL.

How Much VRAM Do You Need in 2026? Is 8GB Still Enough?

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-04 · St. Louis County, MO

The short answer, by resolution: 8GB of VRAM for 1080p, 12GB for 1440p, 16GB for 4K. The endless “is 8GB enough” argument only makes sense once you attach a resolution to it - 8GB is genuinely fine at 1080p and genuinely a wall at 1440p Ultra. This guide gives the honest amount for your resolution, shows what actually breaks an 8GB card, and explains why running low on VRAM feels worse than the benchmark averages suggest.

VRAM is not the same as system RAM

Quick clarification, because the two get confused: VRAM is the memory on your graphics card, used for textures, frame buffers, and shaders. System RAM is separate - that’s the how much RAM you need question. A GPU can be plenty fast and still stutter if it runs out of VRAM specifically, because it then has to shuffle texture data over the slow PCIe bus to system memory. That’s the failure mode this whole debate is about.

How much VRAM by resolution (2026)

Resolution	Buy	Notes
1080p	8GB (10-12GB for Ultra/RT)	Fine for the large majority of games; a wall only in a few unoptimized titles + RT at Ultra.
1440p	12GB minimum, 16GB comfortable	The 2026 baseline. 8GB cards fill up at Ultra and stutter.
4K	16GB minimum (24GB future-proof)	High-res textures + frame buffer eat memory; RT open-world can approach/exceed 16GB.

That ladder - 8/12/16 by resolution - is the consensus across 2026 testing outlets, and it maps to how memory use actually scales: the processor-side work is fixed, but every step up in resolution and texture detail costs VRAM.

What actually breaks an 8GB card

8GB doesn’t fail everywhere - it fails in specific, predictable places. Multiple 2026 benchmark rundowns put several current AAA titles - Cyberpunk 2077, Monster Hunter Wilds, and Hogwarts Legacy among them - at or past 12GB of VRAM use at 1440p Ultra, and turning on full ray tracing on an 8GB card at 1440p tends to blow past the limit immediately (wccftech). At 4K, AAA open-world games with ray tracing can approach or exceed 16GB.

The pattern: it’s textures and ray tracing that eat VRAM, not raw resolution alone. You can often keep an 8GB card happy at 1440p by dropping texture quality one notch and skipping ray tracing - but that’s exactly the compromise a 12GB or 16GB card lets you avoid.

Why running out of VRAM feels worse than the numbers

This is the part benchmark headlines miss. When a card runs out of VRAM, it usually does not just post a lower average FPS. Instead it swaps texture data over the slow PCIe bus, and you get:

Texture pop-in - surfaces load in blurry, then sharpen a beat later.
Stutter and frame-time spikes - sudden hitches even when the average looks fine.
Collapsing 1% lows - the smoothness metric craters while the average barely moves.

That’s why PC Gamer’s 2026 real-world testing found 8GB cards “still enough” on averages yet the 16GB versions “surprisingly faster” in practice (PC Gamer) - the gap shows up in frame-time consistency, not the average. If you only read the average-FPS bar chart, you’ll underestimate how much VRAM matters. The PC Bottleneck Calculator helps you see where the GPU sits relative to your CPU; VRAM is the quiet third factor that a pure FPS number won’t show.

8GB vs 16GB: bigger gap than the debate suggests

The “8GB is fine” and “8GB is dead” camps are both half right, and the honest read is in the middle: 8GB is fine for 1080p and a liability above it. Where people go wrong is treating it as a 1440p amount. In 2026, current 8GB cards like the RTX 5060 Ti 8GB and RX 9060 XT 8GB are strong 1080p performers but are the early casualties at 1440p with ray tracing or maxed textures. If you’re spending real money on a 1440p or 4K card, the VRAM number is not where to save - a fast GPU starved of VRAM spends its life stuttering. Size the whole card to your resolution; the GPU Comparison Tool and the best GPUs for 4K gaming guide put the raw performance next to the memory.

Upscaling and frame generation change the picture slightly but don’t erase it - DLSS and FSR render at a lower internal resolution, which trims VRAM use, while frame generation actually adds a little memory overhead. Neither turns an 8GB card into a 1440p-Ultra card.

The verdict

1080p gaming: 8GB is enough for most games in 2026; 10-12GB if you want Ultra textures and ray tracing headroom.
1440p gaming: 12GB is the floor, 16GB is the target - do not buy an 8GB card for 1440p Ultra.
4K gaming: 16GB minimum, 24GB if you want future-proofing or heavy ray tracing.
The rule: match VRAM to resolution. A fast GPU with too little VRAM doesn’t run slower on average - it stutters, and that’s the worse experience.

VRAM is one of the few GPU specs where the marketing number genuinely matters, because the failure mode is invisible on an average-FPS chart and obvious the moment you play. Buy the amount your resolution needs, and put any savings toward a faster GPU core rather than shaving VRAM you’ll feel the lack of.

Sources

8GB VRAM benchmarks and the 1440p ceiling: wccftech (Sapphire Pulse 9060 XT 8GB testing; Hardware Unboxed podcast comments), PC Gamer real-world 8GB vs 16GB testing.
VRAM-by-resolution consensus (8/12/16): 2026 testing roundups including Tech4Gamers on 12GB as the 1440p minimum.
Related first-party guides: how much RAM you need, best GPUs for 4K gaming, and the GPU Comparison Tool.

Guidance is for mid-2026; game VRAM demands keep rising, so treat these as floors, not ceilings. Found an error? Email hello@techfuelhq.com with the article URL.

How to Fix Monitor Ghosting (2026): Overdrive Done Right

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-04 · ~8 min read · St. Louis County, MO

The most common advice for monitor ghosting — “buy a new cable” — is usually wrong. Ghosting is not a cable problem. It’s a pixel response-time problem happening inside the panel, and the real fix is one setting most people either never touch or turn up too far. This guide explains what ghosting actually is, how to find your monitor’s overdrive sweet spot without creating the worse problem (inverse ghosting), and which kinds of ghosting genuinely can’t be fixed.

What monitor ghosting actually is

Ghosting is a faint trail or duplicate that follows moving objects across the screen. It happens because the monitor’s pixels change color too slowly: the next frame arrives before the previous pixel transition has finished, so you briefly see the old image fading behind the new one.

The spec that governs this is gray-to-gray (GtG) response time — how long a pixel takes to change from one shade to another, measured in milliseconds. Lower is better. Ghosting shows up whenever GtG is slower than the time between frames. And here’s the part that trips people up: refresh rate and response time are different things. A 144Hz monitor refreshes every 6.9ms and a 240Hz one every 4.2ms, but if the panel’s pixels take longer than that to switch, you’ll still get trails. A high refresh rate does not guarantee fast pixels.

The quickest way to confirm you actually have ghosting is the Blur Busters UFO test — the same free tool monitor reviewers use. A UFO slides across the screen; a faint UFO trailing behind it is ghosting.

Fix #1: Set overdrive correctly (the sweet spot, not the max)

This is the fix that solves most ghosting, and it’s already built into your monitor. Overdrive applies extra voltage to force pixels to switch faster, shrinking the response time so transitions fit inside the frame window. Depending on the brand, it’s in your monitor’s on-screen display (OSD) menu under one of these names:

Overdrive (generic)
Response Time (Samsung, many others)
OD (short form)
Trace Free (ASUS)
Overshoot / AMA (some BenQ/Acer)

The mistake almost everyone makes is setting it to maximum. Too much overdrive causes inverse ghosting (overshoot): instead of lagging behind the target shade, the pixel overshoots it and settles back, leaving a bright halo, a dark outline, or a purple “corona” around moving objects. That looks worse than the ghosting you started with.

How to find your sweet spot:

Open the testufo.com UFO test in your browser at your monitor’s native refresh rate.
Open your monitor’s OSD and find the overdrive setting.
Cycle through the levels one at a time — Off → Low/Normal → Medium → High — watching the UFO after each change.
Pick the highest level that still has clean trails with no bright/dark overshoot halo leading or following the UFO.

On most monitors the correct answer is the middle setting, not the top one. The maximum is there for marketing, not for you.

Fix #2: Run your native refresh rate

If your monitor isn’t actually running at its advertised refresh rate, motion looks worse and ghosting is more noticeable. Windows often defaults a new display to 60Hz.

Go to Settings → System → Display → Advanced display, and set Choose a refresh rate to the highest value your monitor supports. If your top refresh rate isn’t listed, you’re likely bandwidth-limited by your cable or port (more on that below). Running at native refresh gives the panel the shortest frame window and lets a correct overdrive setting do its job. This is also the foundation for fixing screen tearing, which is a related but separate motion problem.

Fix #3: Rule out in-game motion blur (it’s not really ghosting)

If you only see “ghosting” inside games and not on your desktop, it may not be your monitor at all. Many games ship with a Motion Blur effect enabled on purpose, and it’s easy to mistake for panel ghosting. Open the game’s video/graphics settings and turn Motion Blur off (and Film Grain while you’re there). If the trailing disappears, it was a software effect, not your hardware — no monitor tweaking needed.

Fix #4: Know your panel type (VA “black smear” can’t be fully fixed)

Not all ghosting is fixable, and it’s important to be honest about that. If you have a VA (Vertical Alignment) panel, you’ll likely see black smearing — a dark trailing smear behind objects moving over dark backgrounds. This is an inherent characteristic of how VA pixels transition in dark scenes, and overdrive only partly helps. You can lessen it by nudging brightness and gamma up slightly in the OSD, but you can’t eliminate it the way you can on an IPS or OLED panel.

If dark-scene smearing genuinely bothers you and you game in a dark room, the fix isn’t a setting — it’s a different panel technology. IPS ghosts far less, and OLED effectively has none. If you’re weighing an upgrade, our guide on using an OLED as a PC monitor covers the motion-clarity trade-offs, and the 1440p vs 4K gaming breakdown helps you match the panel to the GPU you actually have.

The cable question — answered honestly

You’ll see “replace your cable” as the top fix everywhere. For true ghosting, a cable won’t help — ghosting is a response-time problem inside the panel, full stop.

Where a cable does matter is a different symptom that gets confused with ghosting: signal artifacts. A failing, damaged, or under-spec cable can cause random sparkles, brief black flashes, or your monitor silently dropping to a lower refresh rate — and a monitor stuck at 60Hz when it should run 144Hz will look far worse in motion. If the artifact is instead steady vertical or horizontal lines on the screen, the monitor’s own OSD menu settles the cable-versus-panel question in one press. If you see those symptoms, or your native refresh rate won’t appear in Windows, then ruling out the cable is worthwhile: a properly rated VESA-certified DisplayPort cable or an Ultra High Speed HDMI 2.1 cable guarantees the bandwidth for high-refresh signals. But do this to fix signal artifacts or a capped refresh rate, not trailing-behind-motion ghosting — for that, go back to overdrive.

The fix ladder

In order, this is how to kill monitor ghosting:

Confirm it’s ghosting with the testufo.com UFO test (trailing = ghosting; leading halo = too much overdrive).
Set overdrive to the sweet spot — the highest level with no overshoot halo, usually the middle option.
Run your native refresh rate in Windows display settings.
Turn off in-game Motion Blur if you only see it in games.
Accept VA black smear as inherent, or move to IPS/OLED if it bothers you.
Only then consider the cable, and only if you also have signal artifacts or a capped refresh rate.

Most people fix ghosting entirely at step 2. It’s a five-minute setting, not a hardware purchase — which is exactly why “buy a new cable” is such bad first advice.

Sources

Pixel overdrive, response time, and inverse ghosting/overshoot mechanics: KTC — Pixel Overdrive & Inverse Ghosting and How-To Geek — What Is Inverse Ghosting
Gray-to-gray (GtG) response time vs. refresh rate, and ghosting causes: How-To Geek — What Is Monitor Ghosting and Corsair — What is monitor ghosting and how to fix it
Motion/ghosting test tool: Blur Busters UFO Test (testufo.com)

Figures and behavior described are general to LCD (IPS/VA/TN) monitors in 2026; your exact overdrive labels and levels vary by brand. Found an error? Email hello@techfuelhq.com with the article URL.

Monitor Keeps Going Black? Fix the Random Blackouts (2026)

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-04 · ~9 min read · St. Louis County, MO

A monitor that keeps cutting to black - usually for a second or two, then recovering - is one of the most common and most misdiagnosed PC problems. People assume the monitor is dying and start shopping for a new one, when the actual cause is almost always a cable, a driver, or a power setting. The good news is that you already have the single most useful clue and probably haven’t used it: the rhythm of the blackout - how it drops and how it comes back - tells you which of five very different faults you’re looking at. Read the rhythm first, and you fix it at the cheapest step instead of replacing hardware that’s fine.

Read the blackout's rhythm

Think of the video signal as a trace on a scope: up is a live picture, the dotted floor is black. How it drops and whether it climbs back names the fault - before you touch a cable.

Flickers, then recovers

A signal dropout: a cable that can't hold your res/refresh, a driver crash-and-recover (TDR), or PCIe link power. Steps 1-3.

Drops and stays black

A hard fault that needs a reboot or power-cycle to clear: heat, a loose GPU, or power delivery. Step 4.

Fine at idle, drops under load

Not the cable - it's heat, power stability, or VRR flicker that only shows when games push the GPU. Step 4 + the VRR check.

A fourth rhythm - only black coming back from sleep - isn't on the scope because it's not random: that's DisplayPort's hot-plug behavior. Jump to it. time → techfuelhq.com

First, read the symptom

The scope trace above, in words - the exact behavior tells you where to look:

Goes black and recovers on its own (a flicker to black, then the picture returns) → a signal or driver dropout. Cable, driver, or power settings. Start at step 1.
Goes black and stays black until you reboot or power-cycle → a harder fault. More likely overheating, an unstable overclock, a loose GPU, or power delivery. Jump to step 4.
Only goes black in games / under load → heat, power stability, or VRR flicker, not the cable. Go to step 4, and check the VRR section.
Only goes black waking from sleep → DisplayPort hot-plug behavior, not a dying monitor. See the after-sleep section.
Never displayed at all (black from the moment you power on, and it never showed a picture this session) → that’s not an intermittent-blackout problem, it’s a no-POST one. See PC turns on but no display instead.

Step 1: The cable (the #1 cause of intermittent blackouts)

Most “keeps going black” cases are a video cable that can’t reliably carry your signal - and it gets worse the higher your resolution and refresh rate. There’s a real physics reason for that, and it’s worth seeing, because it explains why a cable that “works” can still cut to black at 144Hz or 4K.

Why a cable drops to black at 1440p or 4K

The more resolution and refresh you ask for, the more raw bandwidth the signal needs. A cable rated below it - or a marginal, damaged, or uncertified one - passes a basic picture but cuts to black exactly at the top. Bars are approximate uncompressed 8-bit data rates; the dashed lines are what each connector standard can carry.

HDMI 2.0
DP 1.4
HDMI 2.1
DP 2.1

1080p @ 60Hz

~3 Gbps

1440p @ 144Hz

~14 Gbps

4K @ 120Hz

~26 Gbps

4K @ 240Hz

~52 Gbps

Read it like this: 1440p144 sits right on HDMI 2.0's ceiling and 4K120 right on DisplayPort 1.4's — the [DisplayPort/HDMI bandwidth calculator](/tools/displayport-hdmi-bandwidth-calculator/) shows whether your resolution and refresh actually fit your cable and port — so a slightly-too-weak or damaged cable that's fine on the desktop drops out the instant you hit those. (DSC - Display Stream Compression - squeezes these down roughly 3:1, which is how a DP 1.4 cable does 4K144 at all; a marginal cable is exactly what fails to hold it.) The fix is almost never a new monitor - it's a properly rated cable.

A marginal cable will pass a basic signal fine but drop out at 144Hz or 4K, cutting the screen to black while it re-syncs.

Reseat both ends of the HDMI or DisplayPort cable until they click. DisplayPort especially seats loosely and works its way out.
Swap the cable. This is the single highest-yield fix. Use a properly rated VESA-certified DisplayPort cable or an Ultra High Speed HDMI 2.1 cable that’s rated for your resolution and refresh - a cheap or damaged cable is the most common reason a screen blacks out intermittently, and the meter above is why.
Try a different port on your graphics card, and make sure the cable is in the graphics card, not the motherboard. If you’re troubleshooting a display Windows doesn’t even list, see second monitor not detected.

Step 2: Recover it instantly, then fix the driver

When the screen is black but the PC is clearly still running, press Windows Key + Ctrl + Shift + B. This restarts the graphics driver on the spot - a brief black screen and a beep, then the picture returns. If that reliably brings it back, your problem is driver- or link-related, not a dead cable.

A blackout-and-recover is often a driver crash-and-recover (Windows calls this a TDR - the display driver stops responding, Windows resets it, and the screen returns after a second). It’s the exact behavior the Tom’s Hardware forums describe for this symptom, and the fix is a clean driver install:

Download the latest driver from NVIDIA, AMD, or Intel.
Remove the current driver cleanly with DDU (Display Driver Uninstaller) in Safe Mode, then install the fresh one.
If it started right after an update, roll the driver back (Device Manager → your GPU → Properties → Driver → Roll Back Driver).

If the blackouts come with a “display driver stopped responding” message, work the full GPU driver crash fix guide - it’s the same underlying TDR problem.

Step 3: Turn off the power settings that cause blackouts

Two Windows power options blank the screen and are easy to miss:

Display sleep: Search Edit power plan, and set Turn off the display to a longer time or Never.
PCI Express Link State Power Management: in the same Change advanced power settings window, expand PCI Express → Link State Power Management and set it to Off. This setting throttles the link to your graphics card to save power and is a genuine, under-known cause of brief random blackouts on desktops.

The after-sleep case: it's DisplayPort, not the monitor

If the only time it goes black is coming back from sleep - the monitor won’t wake, shows “No Signal,” or your windows have all jumped to another screen - stop suspecting the panel. This is a well-documented quirk of DisplayPort called hot-plug detect: when a DisplayPort monitor sleeps, it drops all signal on the link, so Windows treats it as if you physically unplugged it. On wake, the PC sometimes fails to re-establish the link or reshuffles everything to whatever display it still sees.

Work it in this order - cheapest first:

Swap the DisplayPort cable for a known-good, DisplayPort-certified one. A borderline cable makes the re-detect far less reliable, and this alone fixes a surprising number of cases.
Check the monitor’s on-screen menu for a setting named DisplayPort deep sleep, DP 1.2/1.4 power, or DDC/CI - toggling that option (off, or to the alternate DP version) changes how the monitor drops the link and often stops the wake blackout. Some Dell and LG panels expose exactly this.
Move to HDMI, or use a good active DisplayPort-to-HDMI adapter - HDMI doesn’t kill hot-plug detect the same way, so it sidesteps the whole behavior. It’s the surest workaround if the setting isn’t in your OSD.
Blank instead of sleep: set your display to turn off via a blank screensaver with a timeout, rather than the power plan’s “turn off the display,” so the monitor never fully drops the link.

Microsoft has shipped a Windows-side fix for the window-rearranging half of this, but the black-on-wake itself is still best solved at the cable/OSD level above.

Step 4: Heat, power, and a loose GPU (for stay-black and under-load cases)

If the screen stays black until you reboot, or only blacks out under gaming load, it’s usually not the display path:

Overheating: a GPU or CPU hitting its thermal limit can trigger a protective blackout. Confirm all fans spin and clear dust from the case and GPU. If temps are high, our safe CPU temperature guide covers what’s normal and when heat is actually the problem.
Unstable overclock/undervolt: revert any GPU or CPU tuning (MSI Afterburner, Adrenalin, Ryzen Master) to stock and test. An overclock that’s slightly unstable - or an undervolt that’s too aggressive - produces exactly this black-screen behavior under load.
Reseat the GPU: power down, and firmly reseat the graphics card in its PCIe slot and its power connectors. A card that’s crept loose in its slot drops signal intermittently.
Power delivery: a failing or underpowered PSU, or a loose PCIe power cable, causes blackouts under load. Make sure the GPU’s power cables are fully seated (including all pins on a 12VHPWR/12V-2x6 connector).

Only in games? Check VRR before you blame the hardware

Here’s a load-related cause almost every other guide misses. If your monitor flashes black or flickers specifically in games and you have G-Sync or FreeSync (VRR) turned on, the odds are it’s the variable-refresh feature itself, not a dying cable or panel.

VRR works by constantly changing the monitor’s refresh interval to match your frame rate. When the frame rate swings hard - and especially when it dips below the monitor’s VRR floor (the low end of its adaptive range, often around 48Hz) - the panel keeps re-timing itself, and OLED and some VA panels show each transition as a brief black flash or brightness flicker. It’s worst in poorly optimized games with uneven frame times, and it looks alarming even though nothing is failing.

Confirm and fix it without buying anything:

Cap your frame rate a few fps below the monitor’s maximum, using RTSS (RivaTuner Statistics Server) or the in-game limiter. Staying inside the smooth part of the VRR range is the single most effective fix.
Toggle G-Sync/FreeSync off as a test. If the black flashes vanish with VRR disabled, you’ve found it - now you’re tuning, not replacing.
Narrow the VRR range with CRU (Custom Resolution Utility) - raising the floor (say, 48-144Hz to 90-144Hz) leaves less brightness gap between refresh steps and cuts the flicker.
Update the monitor firmware and GPU driver - panel makers have shipped firmware specifically to reduce VRR flicker.

This is a tuning problem, not a fault. Treat a game-only black flash with VRR on as VRR-first, and you’ll skip a lot of pointless cable-swapping.

The fix order, in one list

Read the rhythm - flicker-and-recover vs stay-black vs under-load vs after-sleep. It tells you which step to start on.
Cable - reseat, then swap for a properly rated cable; confirm it’s in the graphics card. (The #1 cause; see the bandwidth meter.)
Driver - Win+Ctrl+Shift+B to recover, then a DDU clean reinstall (or roll back if a recent update broke it).
Power settings - Turn off display → Never, and PCI Express Link State Power Management → Off.
After-sleep only - it’s DisplayPort hot-plug: certified DP cable, the OSD DP/DDC setting, or move to HDMI.
Heat / power / seating - for stay-black or under-load blackouts: check temps, revert overclocks, reseat the GPU and its power cables.
Games only - if it’s a black flash with VRR on, cap your frame rate and tune the VRR range before suspecting hardware.

Work it in the order your rhythm points to, and you’ll fix the vast majority of random blackouts at step 2 or 3 - a cable swap or a clean driver install - long before “buy a new monitor” is on the table.

Sources

Cause overview (cable/power/driver) and cable-swap first: Mobile Pixels - Why does my monitor keep going black and Dell - Multi-Monitor Displays: Black Screen or Not Detected. The driver crash-and-recover behavior is described directly in the Tom’s Hardware forums thread on this exact symptom.
PCI Express Link State Power Management fix (a real, under-known blackout cause): Microsoft Q&A - Screen blacking out. The “Turn off the display” timeout is a standard built-in Windows power-plan option.
DisplayPort hot-plug / after-sleep blackout: Microsoft’s fix for DisplayPort window-rearrangement on wake (gHacks) and community workarounds (PowerToys issue #3217).
VRR (G-Sync/FreeSync) black-flash flicker and the frame-rate-cap fix: Display Ninja - What is VRR brightness flickering and Blur Busters Forums - flickering with G-Sync.
Approximate uncompressed bandwidth figures compared against the published data rates of HDMI 2.0/2.1 and DisplayPort 1.4/2.1 (UHBR20); DSC reduces the required rate roughly 3:1.
Clean GPU driver reinstall tool: Display Driver Uninstaller (DDU), Wagnardsoft

Steps are for Windows 10 and 11 desktops and laptops in 2026; menu names vary slightly by version and GPU vendor. Found an error? Email hello@techfuelhq.com with the article URL.

PC Keeps Restarting? Fix the Random Reboots (2026)

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-04 · ~10 min read · St. Louis County, MO

A PC that keeps restarting on its own is one of the most stressful problems to diagnose, because the reboot wipes the evidence before you can read it. The fix starts with a setting most guides skip: turn off Windows’ automatic restart so the next crash actually shows you the error. From there it’s a short, ordered checklist — heat, power, RAM, drivers — and the pattern of when it restarts tells you where to look.

Step 1: Make Windows show you the error (do this first)

By default, Windows instantly reboots on a system crash, so you never see the blue screen. Turn that off so the next crash leaves a stop code on screen:

Press Windows Key + R, type sysdm.cpl, and press Enter.
Go to the Advanced tab → under Startup and Recovery, click Settings.
Under System failure, uncheck “Automatically restart”, and click OK.

Now, the next time it crashes, you’ll get a blue screen with a stop code instead of an instant reboot. Write it down — a code like WHEA_UNCORRECTABLE_ERROR points at hardware or power, while a named driver file (nvlddmkm.sys, for example) points at the GPU driver. That one clue turns guesswork into a targeted fix.

If the PC restarts with no blue screen at all — an instant, total cut like someone pulled the plug — that’s a strong sign of a power problem (PSU or a loose cable), because a true power loss happens faster than Windows can even draw a BSOD. And if it doesn’t come back on its own at all — it powers off and stays off until you press the button — that’s a sudden shutdown rather than a restart, with its own checklist: work our computer randomly turns off guide.

If instead of rebooting the system locks up and freezes — the screen stays frozen, the mouse won’t move, and it never restarts on its own — that’s a different failure with a different checklist; work our computer keeps freezing guide instead.

Read the blue screen: the stop code names the cause

With automatic restart off, the next crash leaves this screen up instead of vanishing. One line does the work — the stop code. It won’t always name the exact part, but it points you at the right step instead of the parts cannon.

Your PC ran into a problem and needs to restart. We’re just collecting some error info, then we’ll restart for you.

For more info, search online later for this stop code:

WHEA_UNCORRECTABLE_ERROR

↑ write this line down — it is the whole clue

WHEA_UNCORRECTABLE_ERROR Fatal hardware error: heat, an unstable overclock/undervolt, or a failing part (CPU, RAM, board, power). Steps 2, 3, 6.

CLOCK_WATCHDOG_TIMEOUT A CPU core stopped responding — usually an unstable CPU overclock or too-aggressive undervolt, else the CPU itself. Step 5, then RAM.

VIDEO_TDR_FAILURE + a .sys name (nvlddmkm.sys) The graphics driver crashed and took the system with it. Clean-reinstall it. Step 5.

MEMORY_MANAGEMENT / IRQL_NOT_LESS_OR_EQUAL RAM or a driver. Test memory first, then drivers. Steps 4–5.

NO blue screen — instant black cut Power, not software: a true power loss beats Windows to the BSOD. Check Event Viewer for Kernel-Power 41 (the “didn’t shut down cleanly” marker — a symptom, not the cause). Step 3.

A named driver file (like nvlddmkm.sys) points straight at that driver. Hardware codes (WHEA, CLOCK_WATCHDOG) point at power, heat, or an unstable overclock — not one exact part — so you still work the steps below to isolate which. techfuelhq.com

Five of the most-searched stop codes have their own step-by-step deep dives: DPC_WATCHDOG_VIOLATION (a driver stalling the CPU — usually storage), KERNEL_SECURITY_CHECK_FAILURE (memory corruption — test RAM first), CLOCK_WATCHDOG_TIMEOUT (a CPU core that stopped responding — revert the overclock first), PAGE_FAULT_IN_NONPAGED_AREA (missing memory — test RAM, then storage), and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (a bad driver, usually named right on the blue screen). If your blue screen shows any of them, start there.

Read the pattern

When it restarts narrows it down fast:

Only under load / while gaming → heat or power (jump to Overheating and PSU).
Random, including at idle or light use → RAM, driver, PSU, or an unstable overclock. When it’s truly random and the stop code keeps changing, use the isolation build below.
In a loop before Windows loads → software (bad update, corrupt files) or a hardware failure (see the boot-loop FAQ above).
Only when you shut down — it reboots instead of powering off, or won’t stay off → that’s usually not a crash at all; see restarts right after shutdown.

Step 2: Overheating

A CPU or GPU that hits its thermal limit reboots the system to protect itself, and this is the #1 cause of load-triggered restarts. If the CPU is the culprit, the why is my CPU overheating guide sorts the cause by when it happens - a dead pump, dried paste, or a loose cooler each fix differently. If the restarts hit hardest in games, suspect the graphics card and confirm the GPU is really overheating with the core-vs-hotspot check before you touch anything - a card that only looks hot needs a different fix.

Check temperatures under load with HWiNFO or HWMonitor. Our safe CPU temperature guide covers what’s normal (Ryzen to ~95°C, X3D ~89°C, Intel ~100°C) and when heat is actually the problem — a chip parking at its limit and rebooting means cooling can’t keep up.
Clear dust from fans, heatsinks, and vents with a can of compressed air, and confirm every fan spins (a failed AIO pump or CPU fan causes fast thermal shutdowns).
Reapply thermal paste if it’s a few years old — dried paste is a common cause of a system that used to run cool and now overheats. An inexpensive tube of Arctic MX-4 is enough for several repastes and often drops load temps several degrees.

Step 3: Power supply

The PSU is the most under-suspected hardware cause of restarts, especially the load-related and no-BSOD kind. A supply that’s failing, undersized for your GPU, or connected with a loose cable can’t hold the load and drops the system.

Reseat every power cable — the 24-pin, the CPU (EPS) connector, and every GPU power cable, including all pins on a 12VHPWR/12V-2x6 connector, which is notorious for partial seating.
Rule out undersizing: a new, power-hungry GPU on an old PSU is a classic restart cause. Run your parts through the PSU wattage calculator to see whether your supply has the headroom — if you’re near or over its rating under load, that’s your answer.
If temps are healthy and it still restarts under load, a known-good, adequately-rated PSU is the next test. Size it first, then buy — don’t guess on wattage.

If power looks like the culprit and you want to confirm the PSU is failing rather than just undersized, our deep dive covers the tell-tale symptoms, why the paperclip test can give a false all-clear, and how to read the 12V rail under load: PSU Failure Symptoms: Is It Really the Power Supply?

Step 4: RAM

Faulty or unstable memory causes random restarts and blue screens.

Test it: run the built-in Windows Memory Diagnostic (Windows Key + R → mdsched.exe), or MemTest86 from a USB stick for a thorough overnight pass.
Reseat and isolate: reseat both sticks, then test one stick at a time to find a bad module.
Check your memory speed: an unstable EXPO/XMP profile can restart a system that’s otherwise fine. Set memory to its default JEDEC speed to test; if the restarts stop, the kit or memory controller isn’t holding the rated speed.

Step 5: Drivers and overclocks

Graphics driver: a crashing GPU driver can take the whole system down. If your blue-screen names a driver like nvlddmkm.sys, do a clean reinstall — the full process is in the GPU driver crash fix guide.
Revert overclocks/undervolts: set any CPU or GPU tuning (MSI Afterburner, Ryzen Master, BIOS PBO/curve) back to stock. An overclock that’s slightly unstable, or an undervolt that’s too aggressive, restarts the system under load exactly like a hardware fault.

Step 6: Software (for boot loops and post-update restarts)

If the trouble is a reboot loop or started right after an update:

Windows Recovery: force-power-off during boot three times to trigger Automatic Repair, then try Startup Repair, System Restore, or Uninstall latest updates.
Safe Mode to roll back a bad driver or uninstall recently installed software.
Scan for malware, and run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth to repair corrupt system files.

When it's random: the isolation build

When a restart only happens under load, or the blue screen names a part, you follow the step it points to. But some restarts are genuinely random — different stop codes each time, no pattern, or no blue screen at all — and chasing those by swapping parts wastes money. The reliable move is the opposite of adding parts: strip the machine to a configuration you know is stable, then add each variable back one at a time until the restart returns. Whatever you re-enabled last is the cause.

The isolation build: strip to stable, add one thing back

Stop swapping parts on a hunch. Drop the machine to a known-stable floor, then re-introduce one variable at a time and run it. The first change that brings the restart back is your culprit.

THE STABLE FLOOR — stock clocks (no PBO/OC/undervolt), RAM at default JEDEC speed (XMP/EXPO off), one stick, light desktop use. Rock-solid here? Add back, one at a time ↓

Still restarts stripped this bare? It isn’t tuning — look at the PSU, heat, or a driver (Steps 2, 3, 5).

STEP 1 · ADD

EXPO / XMP

BASE EXPO

Restart returns now → the kit or memory controller can’t hold the rated speed. Run a milder EXPO, nudge SoC/DRAM voltage, or stay at JEDEC. (Step 4.)

STEP 2 · ADD

OC / PBO / undervolt

BASE EXPO OC

Returns only after this → the overclock or undervolt isn’t stable. Loosen the curve or go stock. (Step 5.)

STEP 3 · ADD

the 2nd RAM stick

BASE EXPO OC 2×RAM

Returns only with both sticks in → a bad module or a 2-DIMM stability limit. Test each stick alone. (Step 4.)

STEP 4 · ADD

a full gaming load

BASE EXPO OC 2×RAM LOAD

Returns only under real load, everything else stable → heat or PSU headroom. Check temps and wattage. (Steps 2–3.)

Change one thing per step and run it long enough to catch the crash — hours, or a full session of your usual game. Two changes at once is exactly why a ‘random’ restart stays random. more variables → techfuelhq.com

The two variables that cause the most “random” restarts are the ones people forget they turned on: the memory’s EXPO/XMP profile and any CPU or GPU overclock, PBO, or undervolt. Both run the hardware past its guaranteed-stable defaults, and both can behave for weeks and then drop the system under the wrong workload. Turning them off costs nothing and clears them in one test — which is why the isolation build starts there, not at the parts store.

Restarts right after you shut down (or won't stay off)

There’s one “restart” that isn’t a crash at all: you click Shut down, the PC powers off for a second, then boots straight back up — or it never fully powers off. That’s a shutdown problem, not a stability one, and it has its own short list.

Turn off Fast Startup first. Fast Startup (Windows’ hybrid shutdown) saves the kernel to disk instead of powering all the way down, and on a lot of systems it’s the direct cause of a reboot-instead-of-shutdown. Open Control Panel → Power Options → “Choose what the power buttons do” → “Change settings that are currently unavailable”, then uncheck “Turn on fast startup” and save. Forcing a full cold shutdown every time fixes the majority of these cases.
Stop a device from waking it. A network adapter or mouse allowed to wake the machine can pull it back on the instant it powers off. In Device Manager, open the network adapter (and the mouse) → Power Management tab → uncheck “Allow this device to wake the computer.” From a terminal you can list armed wake sources with powercfg /waketimers and see what last woke it with powercfg /lastwake.
Rule out a pending update. A Windows Update mid-install reboots rather than shuts down once — let it finish, then try again.
A dirty previous shutdown (a hard power-off or a crash) can make the next shutdown behave oddly a single time; if it happened only once, it’s likely nothing.

If it still reboots on shutdown after all of that, treat it like a random restart and work the stability steps above — a marginal PSU can occasionally show up this way too.

The fix order, in one list

Uncheck “Automatically restart” (sysdm.cpl → Advanced → Startup and Recovery) so you can read the stop code.
Read the pattern — under-load = heat/power; random = RAM/driver/PSU/overclock; boot-loop = software/hardware failure.
Overheating — temps, dust, fans, thermal paste.
PSU — reseat cables, check wattage headroom, then swap if load-related.
RAM — mdsched/MemTest86, reseat, one stick at a time, test at JEDEC speed.
Drivers/overclocks — clean-reinstall the GPU driver, revert all tuning to stock. Still random? Run the isolation build — strip to a stable floor, add one variable back at a time.
Software — Automatic Repair, Safe Mode, malware scan, sfc/DISM for boot loops.

Work it in order and the stop code from step 1 usually points you straight to the right step — no parts-cannon required. Two cases sit outside this flow: a genuinely random restart is fastest to pin with the isolation build, and a reboot that only happens when you try to shut down is a Fast Startup problem, not a crash.

Sources

The diagnostic and fixes use Microsoft’s built-in Windows tools — disable automatic restart (sysdm.cpl → Advanced → Startup and Recovery), the Windows Memory Diagnostic (mdsched.exe), Automatic Repair / Safe Mode, and sfc /scannow + DISM /Online /Cleanup-Image /RestoreHealth — all standard and self-verifiable on any Windows 10/11 PC. The ordered hardware causes (overheating, PSU, RAM, driver, overclock) are cross-corroborated across community and vendor troubleshooting guides.
Thermal limits and what “too hot” actually is: our safe CPU temperature guide (first-party). Driver-crash clean reinstall: our GPU driver crash fix guide (first-party).
Blue-screen stop codes map to Microsoft’s Bug Check Code Reference (WHEA_UNCORRECTABLE_ERROR = fatal hardware error; CLOCK_WATCHDOG_TIMEOUT = an unresponsive CPU core; VIDEO_TDR_FAILURE = a display-driver timeout). Kernel-Power event ID 41 is Microsoft’s marker that the PC rebooted without a clean shutdown — a symptom of a power loss or hard crash, not a cause (Microsoft Q&A, corroborated on Tom’s Hardware and Linus Tech Tips forums).
The restart-instead-of-shutdown fix (disable Fast Startup, then check device wake permissions) is the standard, widely-corroborated remedy — see ASUS official support and The Windows Club.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version. Found an error? Email hello@techfuelhq.com with the article URL.

Proxmox vs Hyper-V (2026): Free and Open vs Windows-Licensed

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-04 · St. Louis County, MO

The short version: Proxmox VE is free and open-source; Hyper-V is not free anymore. The free, standalone Hyper-V Server that homelabbers used to grab was discontinued after its 2019 edition, so in 2026 Hyper-V means enabling a role inside a licensed copy of Windows. That single fact reshapes the whole comparison, especially now that the Broadcom-era VMware price hikes have people hunting for an escape hatch - and finding that Microsoft’s “free” one quietly closed.

This guide compares the two honestly: what each really costs, how they differ in features and management, and which one fits a home lab or a small business.

The cost and licensing reality (the part that changed)

This is the difference that matters most in 2026, so it goes first.

Proxmox VE is free and open-source. You download it, install it, and run unlimited VMs and containers with no license key, no node limit, and no time limit. An optional paid subscription (per CPU socket, per year) gets you the enterprise software repository and vendor support, but the features are identical to the free community version.
Hyper-V is no longer free as a standalone product. Microsoft discontinued the standalone Hyper-V Server line after Hyper-V Server 2019 - the last free, standalone edition - and its mainstream support ended in January 2024 (Microsoft Lifecycle). In 2026 you get Hyper-V by enabling the role on a licensed Windows: either Windows Server (licensed per physical core, with a 16-core-per-server and 8-core-per-processor minimum, per Microsoft’s Windows Server licensing) or Windows 10/11 Pro/Enterprise for desktop-class virtualization. Enabling the role is free; the Windows underneath it is not, and you license your Windows VMs on top.

So the “free Microsoft hypervisor” many people still assume exists mostly doesn’t. Hyper-V the technology is alive and well - it’s a supported role in Windows Server 2022 (mainstream support through October 2026, extended support through October 2031) and 2025 - but there is no free, bare-metal Hyper-V host in 2026. If free is the requirement, Proxmox is the answer.

Proxmox VE vs Hyper-V at a glance

	Proxmox VE	Hyper-V
Cost	Free, open-source (optional paid support)	Needs a licensed Windows (Server per-core, or Win 10/11 Pro)
Base OS	Debian Linux	Windows Server / Windows 10-11 Pro
Hypervisor	KVM (type-1) + LXC containers	Hyper-V (type-1)
Management	Built-in web UI (per-node + cluster)	Windows Admin Center / Hyper-V Manager / Failover Cluster Manager
Clustering + HA	Built in, free	Failover clustering (Windows Server; more setup)
Live migration	Built in, free	Live Migration (Windows Server)
Backup	Built in (+ Proxmox Backup Server)	Windows Server Backup / third-party
Containers	LXC (system containers) natively	Windows containers (Windows-centric)
Best for	Home labs, budget builds, open-source flexibility	Microsoft-ecosystem shops, Windows-heavy workloads

Architecture and ease of use

Both are true type-1 hypervisors, so raw VM performance is close; the practical differences are the platform and the tooling around them.

Proxmox VE runs on Debian Linux and manages everything through a single built-in web interface - VMs, LXC containers, storage, networking, clustering, and backups - with no extra server to install. That web UI is the reason Proxmox punches above its weight for a home lab: you get enterprise-style features from one browser tab. The trade-off is a steeper start if you are not comfortable with Linux concepts like ZFS, bridges, and the shell when something goes sideways.

Hyper-V lives inside Windows, so if you already administer Windows it feels familiar fast - creating a Windows VM is a wizard, and it integrates cleanly with Active Directory, Group Policy, and System Center in a business setting. Multiple 2026 hands-on comparisons put Hyper-V as the easier one to pick up for Windows admins, while noting it carries the overhead of the Windows OS underneath and leans on paid infrastructure for its more advanced features (XDA Developers, WunderTech).

Containers: Proxmox’s quiet advantage

If you want to run containers next to your VMs - which most self-hosters do - Proxmox has the edge. It supports LXC system containers natively from the same web UI, so you can spin up a lightweight Linux container in seconds instead of a full VM, and run Docker inside an LXC or a small VM. Hyper-V’s container story is tied to Windows containers and the Windows ecosystem, which is a fit if that’s your world but not the flexible, low-overhead path a homelab usually wants. For the VM-vs-container decision itself, see LXC vs VMs on Proxmox and Proxmox vs Docker.

Hardware and resource use

Proxmox is lean. It runs happily on a mini PC or an older desktop, which is exactly why it is the popular home-lab pick on the kind of low-power hardware covered in the best mini PCs for a home lab guide; check the Proxmox hardware requirements before you buy. Hyper-V needs enough headroom to run its Windows host comfortably on top of your VMs, so on the same modest box Proxmox generally feels more responsive because it isn’t carrying a full desktop OS. On strong, Windows-centric server hardware the gap narrows and Hyper-V is perfectly capable.

The VMware-exodus context

A lot of people arrive at this comparison because the Broadcom acquisition reshaped VMware’s licensing and pricing, and they’re looking for somewhere to land. Both Proxmox and Hyper-V are legitimate off-ramps from VMware - but the twist is that Microsoft’s free standalone option is gone too, so the “free escape” is Proxmox, not Hyper-V. If VMware/ESXi specifically is what you’re leaving, the Proxmox vs ESXi comparison covers that migration in depth; this page is the Microsoft side of the same decision.

Who should run which

Run Proxmox VE if:

You want a genuinely free, open-source platform with no license to manage.
It’s a home lab, or a budget-conscious business, especially on mini PCs or older hardware.
You want VMs and lightweight containers from one web interface.
You’re leaving VMware and “free” is a hard requirement.

Run Hyper-V if:

You’re already deep in the Microsoft ecosystem (Active Directory, System Center, Windows Server) and value that integration.
Your workloads are Windows-heavy and you’re comfortable licensing Windows Server per core.
You specifically want to learn or standardize on Microsoft’s virtualization stack.
You just need desktop-class VMs on a machine that already runs Windows 11 Pro.

The verdict

For a home lab or a cost-sensitive setup in 2026, Proxmox VE is the default recommendation - free, open-source, light on hardware, and complete out of the box with clustering, HA, live migration, and backups. Hyper-V earns its place in Microsoft-centric environments, where its integration and familiar tooling are worth running on a licensed Windows host. The old tie-breaker - “Hyper-V is free too” - no longer applies: the free standalone Hyper-V Server is gone, so if budget and openness lead your decision, Proxmox wins it cleanly. Ready to try it? The how to install Proxmox VE guide gets you from download to first VM.

Sources

Hyper-V licensing and lifecycle: StarWind on the end of free standalone Hyper-V, plus Microsoft Lifecycle for Hyper-V Server 2019 (mainstream support ended 2024-01-09) and Windows Server 2022, and Microsoft’s Windows Server licensing (per-core minimums).
Proxmox vs Hyper-V hands-on comparisons: XDA Developers, WunderTech, HorizonIQ.
Proxmox VE features and licensing: our own Proxmox vs ESXi and how to install Proxmox VE guides.

Comparison current as of mid-2026. Licensing terms and Windows Server core pricing can change - confirm current Microsoft licensing before a business purchase. Found an error? Email hello@techfuelhq.com with the article URL.

Safe CPU Temperatures in 2026: What's Normal, What's Too Hot

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-04 · Updated 2026-07-13 · St. Louis County, MO

The short answer: 30-50C at idle and 60-85C while gaming is healthy, and hitting your chip’s rated limit (95C on a Ryzen including the 9800X3D, ~89C on Zen 4 X3D parts like the 7800X3D, 100-105C on Intel) under a heavy load is usually normal, not damage. The single most important thing to understand about CPU temps in 2026 is that modern processors are designed to run hot - they boost right up to their thermal limit on purpose. This guide gives the real numbers by chip and workload, the X3D exception that trips people up, and how to tell a normal temperature from an actual problem.

Rather than hand you one more “65-85C is safe” range, the whole guide runs on a single idea you can apply to any reading: a temperature is only meaningful next to the workload that produced it. Start with where your number actually falls on the scale.

The whole scale, from idle to redline

Find your number on the bar. The green-to-lime band is where a healthy chip lives under load; the red ticks below are each family’s hard limit (TjMax), where it starts protecting itself. Touching a redline in a stress test is by design — not damage.

89° Zen 4 X3D (7800X3D, 5800X3D) 95° most Ryzen 7000/9000, incl. 9800X3D & 9950X3D 100° Intel Core 12–14th gen 105° Intel Arrow Lake (Core Ultra 200S)

TjMax figures from AMD & Intel published specifications, verified July 2026. techfuelhq.com

Modern CPUs are built to run hot

The instinct that “hot equals damage” is out of date. Both AMD and Intel now use aggressive boost algorithms that push clock speed until the chip hits either its power limit or its temperature limit - whichever comes first. That means a healthy modern CPU under a heavy all-core load will often sit right at a temperature that would have terrified you a decade ago, and that’s the chip doing exactly what it was engineered to do.

So a Ryzen 7000/9000 at 90-95C in a render, or an Intel Core chip in the 90s during a stress test, is not a red flag by itself. What matters is whether the temperature matches the workload - which is the lens this whole guide uses.

Safe CPU temperatures by chip and workload

Workload	Healthy	Normal ceiling (TjMax)
Idle / desktop	30-50C	-
Gaming	60-85C	-
Heavy all-core (render, stress)	75-90C	at the chip’s limit below
AMD Ryzen 7000/9000 (non-X3D)	-	95C (by design)
AMD Zen 4 X3D (5800X3D/7800X3D)	-	~89C (lower - see below)
AMD Zen 5 X3D (9800X3D/9950X3D)	-	95C (limit restored)
Intel Core 12th-14th gen	-	~100C
Intel Arrow Lake (Core Ultra 200S)	-	105C

High-end chips idle warmer than you’d expect - a Ryzen 7 7800X3D commonly idles around 45-50C, which is normal, not a fault. The healthy targets above are where you want your sustained temps; brief spikes to TjMax during a stress test or a heavy load burst are fine.

The X3D exception (7800X3D / 9800X3D)

This is the detail most temperature guides miss - and it’s genuinely a story about physics, not a spec typo. AMD’s X3D chips bolt a slab of extra L3 cache (the 3D V-Cache) onto the compute die. On Zen 4 parts (5800X3D, 7800X3D) that cache sits on top of the cores - so every watt of heat the cores make has to travel up through the cache before it reaches the heatspreader and your cooler. Cache silicon is a worse thermal conductor than the cores, so AMD holds those chips to a lower ceiling (~89C) to protect the stack. On Zen 5 (9800X3D, 9950X3D) AMD flipped the sandwich: the cache moved underneath the cores, the cores now touch the heatspreader directly, and the full 95C limit came back. Same trick, literally turned upside down.

Why 89° became 95°: AMD flipped the sandwich

Both chips stack cache and cores under one heatspreader. What changed between generations is the order of the layers — and that order is the whole reason the ceiling moved 6 degrees.

Zen 4 X3D — cache on top

5800X3D, 7800X3D

HEATSPREADER (to cooler)

3D V-CACHE (heat must cross this)

CORES ↑ hot

~89°C

ceiling — the cache blanket runs hotter

Zen 5 X3D — cache underneath

9800X3D, 9950X3D

HEATSPREADER (to cooler)

CORES ↑ hot, touching the lid

3D V-CACHE (out of the heat path)

95°C

ceiling — full limit restored

Practical upshot: on a 7800X3D, treat ~85°C as your comfortable load target and ~89°C as the ceiling. On a 9800X3D or 9950X3D, judge it like any other Ryzen — 95°C under load is fine.

The upside is the same for both: X3D chips draw less power than their raw performance suggests, so they run cool for what they deliver. A good air cooler or a 240/360mm AIO keeps them well in range, and a small Curve Optimizer undervolt (the AMD equivalent of the undervolting principle covered in our RTX 5080 guide) shaves several degrees with no performance cost - often the single best thing you can do for an X3D chip’s temperatures.

Laptops play by different rules

Everything above assumes a desktop. Laptops run hotter on purpose, because they cram the same class of chip into a fraction of the cooling. 75-90C on the CPU while gaming is normal for a laptop, and a thin machine touching 90-95C under a sustained load - with the chip deliberately thermal-throttling to stay there - is usually the design working, not a fault. That is the trade-off for the form factor.

The warning signs are the same as anywhere: hot at idle, or throttling during light use. Because a laptop pulls air through one small blower that clogs fast (especially on a bed, couch, or carpet that blocks the underside vents), the first fix is almost always cleaning the intake and fan with compressed air, then raising the back for airflow or using a cooling pad. An undervolt via ThrottleStop (Intel) or the vendor tuning app cuts temps with little performance loss, and a repaste helps on an older machine - though on a laptop that means disassembly.

When a temperature actually means trouble

The rule is simple: worry when the temperature doesn’t fit the work. 95C in a full render is fine; 95C while opening a browser is not. Signs of a real cooling problem:

High temps at idle or light load - sitting at 90C+ while browsing points to a failed or unplugged AIO pump, dried-out or badly applied thermal paste, or a cooler that isn’t seated properly.
Sudden shutdowns under load - the chip is hitting its emergency limit (if it reboots the whole PC, work the PC keeps restarting fixes).
Sustained throttling during normal gaming - clocks dropping and staying down means the cooler can’t keep up.
A sharp jump after reseating the cooler - usually a paste or mounting-pressure issue.

Those are faults to fix, not numbers to live with - if your chip is genuinely overheating (throttling or shutting down), the why is my CPU overheating guide diagnoses the cause by when it happens. A quick temperature sanity check is also worth doing before you blame the CPU for stutter - the PC Bottleneck Calculator helps you separate a thermal problem from a genuine CPU/GPU mismatch, and the CPU Comparison Tool shows where your chip should land when it’s cooled properly.

How to bring temperatures down

If your temps are higher than the healthy ranges above, the fixes in rough order of impact:

Improve case airflow - intake and exhaust fans, and make sure the case isn’t starved. This is the cheapest, biggest win on many builds.
Reapply thermal paste if it’s a few years old or was applied badly - a dried pea of old paste is a common culprit for a chip that used to run cooler. A ~$5 tube of a proven paste like the Arctic MX-4 (or the higher-performance MX-6) is enough for years of repastes and often drops load temps several degrees on a chip that was running hot.
Undervolt - a Curve Optimizer offset (AMD) or a voltage offset (Intel) lowers temperature with little or no performance loss. It’s the tuning step that pays off most for the least effort.
Set a sane fan curve - many boards ship conservative curves; a slightly more aggressive one trades a little noise for a lot of headroom.
Upgrade the cooler if the chip is genuinely too much for it - a quality air cooler or a 240/360mm AIO like the NZXT Kraken 360 handles any current desktop chip.

The verdict

Idle: 30-50C is normal (high-end chips run at the top of that).
Gaming: 60-85C is the healthy zone; under 80C keeps boost clocks high.
Heavy load: up to TjMax is within spec - 95C for Ryzen 7000/9000 (incl. Zen 5 X3D), ~89C for Zen 4 X3D, 100C for Intel Core 12-14th gen, 105C for Arrow Lake.
Laptops: add ~5-10C - 75-90C gaming is normal by design.
The rule: judge the temperature against the workload. Hitting the limit in a render is normal; hitting it at idle is a cooling fault.

Modern CPUs are supposed to run warm, so don’t panic at a big number in a stress test. Watch instead for temperatures that don’t match what you’re doing - that’s the real signal that something needs fixing.

Sources

AMD Ryzen 7000/9000 TjMax (95C by design): AMD’s stated Zen 4/5 thermal threshold, confirmed across 2026 reviews and AMD’s own product pages (e.g. AMD Ryzen 9 9950X3D specs, corroborated by TechPowerUp’s 9950X3D temperature testing).
Zen 4 X3D ceiling (~89C, lower than 95C because the stacked 3D V-Cache sits on top of the cores and is more thermally sensitive) and the Zen 5 X3D restack to 95C: AMD’s X3D specifications, reported consistently across 2026 hardware outlets. Corroborated first-party by our own Ryzen 7 7800X3D review.
Intel Arrow Lake TjMax (105C, raised from the traditional 100C): Intel Core Ultra 9 285K product specifications and Tom’s Hardware’s Arrow Lake review.
First-party context: our Ryzen 7 7800X3D review (real X3D thermals and Curve Optimizer setup) and NZXT Kraken 360 review.

Figures are general guidance for desktop chips in 2026 (laptops run warmer); check your specific CPU’s spec page for its exact TjMax. Found an error? Email hello@techfuelhq.com with the article URL.

Second Monitor Not Detected? The Fix Order That Works (2026)

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-04 · ~7 min read · St. Louis County, MO

A second monitor that won’t show up in Windows is almost never a broken monitor. It’s usually a setting Windows didn’t apply, a cable in the wrong port, or a display plugged into the motherboard instead of the graphics card. This guide works the fixes in the right order — fastest and most common first — so you’re not reinstalling drivers to solve what a keyboard shortcut would have fixed. Most people are done by step 3.

First: is it “not detected” or “no signal”?

These look the same but point in different directions, so check which you have:

Not detected — the monitor is on but Windows doesn’t list it in Display Settings. This is usually a Windows/driver issue. Start at step 1.
No signal (the monitor shows its own “No Signal” message) — the panel is powered but getting no video feed. This is a connection/port issue. Jump to step 3.

Step 1: Force Windows to detect it

Windows sometimes just fails to register a display that’s physically fine. Make it look again:

Right-click the desktop → Display Settings. Scroll to Multiple displays and click Detect.
Set the projection mode. Press Windows Key + P and choose Extend (not “PC screen only,” which ignores the second display, and not “Duplicate” unless you want mirrored screens).
Restart the graphics driver without rebooting: press Windows Key + Ctrl + Shift + B. The screen goes black and beeps for about a second, then comes back — Windows has reset the display stack and re-scanned for monitors. This one shortcut fixes a surprising number of “suddenly gone” second monitors, and most people have never heard of it.

If the display appears now, you’re done. If not, it’s hardware — keep going.

Step 2: Plug both monitors into the graphics card (the #1 hardware mistake)

On a desktop with a dedicated graphics card, this is the most common cause and the easiest to miss. Your PC has two sets of video outputs: the ones on the graphics card (lower down on the back of the tower, oriented horizontally) and the ones on the motherboard (up near the USB ports).

When a dedicated GPU is installed, the motherboard’s video outputs are usually inactive — they only drive a display if your CPU has integrated graphics and the iGPU is enabled in the BIOS, which it often isn’t by default. So if you plugged your first monitor into the graphics card and your second into the motherboard, the second one typically gets no signal and never appears in Windows. Move both cables to the graphics card’s ports. This alone fixes a huge share of “second monitor not detected” cases on desktops.

Step 3: Check the input source, cable, and port

If it’s still missing (or showing “No Signal”), rule out the physical connection:

Input source: Use the monitor’s own physical buttons to open its menu and set the input to the exact port your cable is in — HDMI 1, DisplayPort, USB-C, etc. A monitor sitting on the wrong input shows nothing even with a perfect cable.
Reseat the cable: Unplug both ends, wait five seconds, and push them back in until they click. DisplayPort and some HDMI connectors seat loosely.
Swap the cable: A marginal or damaged cable is one of the most common culprits, especially if you’re pushing high resolution or refresh rate. Test with a known-good, properly rated certified DisplayPort cable or Ultra High Speed HDMI 2.1 cable — a cable that can’t carry your resolution/refresh will silently fail to link.
Try a different port on the graphics card to rule out a single dead output.
Adapters: If you’re going DisplayPort-to-HDMI or using a splitter, a passive adapter often can’t handle high-refresh or multi-monitor signals — you need an active DisplayPort-to-HDMI adapter. On a laptop or USB-C setup, a USB-C docking station (or its cable) is a frequent point of failure — test the monitor plugged directly into the machine first to isolate it.

Step 4: Update, roll back, or clean-reinstall the GPU driver

If the hardware checks out, the driver is next. Outdated or corrupted display drivers routinely stop Windows from seeing a second monitor — and this is the usual cause when a monitor stopped being detected right after a Windows or driver update.

Press Windows Key + X → Device Manager → Display adapters.
Right-click your graphics card → Update driver → Search automatically.
If it’s already current, roll it back (right-click → Properties → Driver → Roll Back Driver) — this is the fix when a recent update broke detection.
For a stubborn case, do a clean reinstall: use DDU (Display Driver Uninstaller) or the AMD Cleanup Utility to fully remove the driver, then install the latest from NVIDIA, AMD, or Intel directly. A clean reinstall clears the corrupted display configuration that a simple update leaves behind — the same approach that resolves a lot of GPU driver crashes.

The fix order, in one list

Force-detect: Display Settings → Detect, then Win+P → Extend, then Win+Ctrl+Shift+B.
Both monitors into the graphics card, not the motherboard.
Input source, cable, port — set the right input, reseat/swap the cable, try another port, check adapters/docks.
Driver — update, then roll back, then clean-reinstall with DDU.

Work it in that order and you fix the problem at the cheapest, fastest step instead of jumping straight to a reinstall. Once both screens are up, the next things worth dialing in are screen tearing and monitor ghosting, which are the two motion issues that show up once a display is actually working — and if a screen instead cuts to black intermittently, see monitor keeps going black.

Sources

Force-detect, Win+P Extend, and driver steps: Windows Central — How to fix a second monitor not detected and Microsoft support — multiple displays
Cable/connection and GPU-vs-motherboard port causes: Dell — Multi-Monitor Displays: Black Screen or Not Detected
Clean driver reinstall tool: Display Driver Uninstaller (DDU)

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version and GPU vendor. Found an error? Email hello@techfuelhq.com with the article URL.

USB Device Not Recognized? The Fix Order That Works (2026)

LK Wood IV — Sat, 04 Jul 2026 00:00:00 -0500

By LK Wood IV · 2026-07-04 · ~7 min read · St. Louis County, MO

“USB device not recognized” is one of Windows’ most common and most fixable errors. The good news: the device is usually fine — the fault is almost always the PC’s ports, a power setting, or a driver in a bad state. This guide works the fixes in order, from the ten-second checks to the driver-level fixes, so you solve it without buying anything you don’t need. Start at the top and stop when it works.

The 30-second isolation test

Before changing any settings, find out whether the problem is the device or the PC:

Plug the device into a different computer. If it works there, your PC is the problem — go to the software fixes below. If it fails on every PC and every cable, the device or its cable is the fault.
Try a different port and cable on your own PC. On a desktop, use a rear port (directly on the motherboard’s I/O, not a front-panel or hub port) — rear ports are wired straight to the controller and are the most reliable.

Most of the time the device works elsewhere, which means the fix is in Windows.

Fix #1: Disable USB selective suspend (the #1 silent cause)

Windows has a power-saving feature that suspends USB ports to save energy, and it frequently fails to wake a device back up — so the device “isn’t recognized” until you unplug and replug it. Turning it off fixes a large share of cases, especially on laptops:

Open Edit power plan (search for it), then Change advanced power settings.
Expand USB settings → USB selective suspend setting.
Set it to Disabled (both On battery and Plugged in), and apply.

While you’re in Device Manager (next fix), also stop individual hubs from powering down: for each USB Root Hub, open Properties → Power Management and uncheck “Allow the computer to turn off this device to save power.”

Fix #2: Reinstall the USB controllers in Device Manager

A corrupted USB controller driver blocks detection, and reinstalling it is a clean fix:

Windows Key + X → Device Manager.
Look for a device with a yellow warning triangle — often “Unknown USB Device (Device Descriptor Request Failed).” Right-click it → Uninstall device.
Expand Universal Serial Bus controllers and, if the specific device is still missing, uninstall each USB Root Hub entry too.
Click Action → Scan for hardware changes, or reboot. Windows reinstalls the controllers from scratch, which clears the bad state.

This is also the answer to “how do I force Windows to detect it” — uninstall the stuck entry and rescan.

Fix #3: Disable Fast Startup

Fast Startup (Windows’ hybrid shutdown) doesn’t fully shut down the system, and it routinely leaves the USB stack half-initialized — so devices that worked yesterday aren’t recognized after a “shutdown.” Turn it off:

Control Panel → Power Options → Choose what the power buttons do.
Click Change settings that are currently unavailable.
Uncheck Turn on fast startup, and save.

Then do a full shutdown (not restart) and power back on. This alone resolves a lot of intermittent “not recognized” and “device descriptor request failed” cases.

Fix #4: Update chipset and USB drivers

Outdated motherboard chipset drivers are a genuine cause on desktops, because the chipset provides the USB controllers. Get the latest chipset drivers from your motherboard maker (ASUS, MSI, Gigabyte, ASRock) or, on a laptop, from the laptop maker’s support page for your exact model. Run Windows Update too, which delivers many USB and controller driver updates. If the trouble started right after a driver change, this is where the fix usually is — the same driver-state logic behind GPU driver crashes applies to USB controllers.

Fix #5: Power — the cause people miss on drives and hubs

High-draw devices — external hard drives, some SSDs, and busy hubs — can pull more power than a single port or an unpowered hub supplies, and an under-powered device simply won’t enumerate. (If the device that won’t appear is specifically an external drive — powered and detected, but missing from File Explorer or Disk Management — the drive-by-drive detection ladder in external hard drive not showing up pins that case exactly, including the two data-safety landmines you should not touch.) Two moves:

Plug power-hungry devices straight into a rear port, not through an unpowered hub or a front-panel header.
If you’re out of ports or running several devices, use a powered USB hub (one with its own power adapter) so each device gets full power instead of splitting one port’s budget. And if the fault followed a specific cable, a known-good USB 3.0 cable rules it out — a marginal cable is a common, cheap cause.

The fix order, in one list

Isolate: test the device on another PC; try a rear port and a different cable.
USB selective suspend → Disabled, and uncheck USB Root Hub power-saving.
Reinstall USB controllers in Device Manager (uninstall the flagged/Unknown device + USB Root Hubs, then Scan for hardware changes).
Disable Fast Startup, then do a full shutdown.
Update chipset/USB drivers from your board or laptop maker + Windows Update.
Power: rear port for high-draw devices, or a powered hub; swap a suspect cable.

Work it top to bottom and the vast majority of “USB device not recognized” errors clear at the power-setting or Device Manager step — no new hardware required. This is the same connect-it-and-it-just-works troubleshooting mindset behind fixing a keyboard that won’t type, a game controller that won’t connect, or a second monitor Windows won’t detect.

Sources

USB-C, ports, cables, and reinstall-driver guidance (including plugging power-hungry drives directly in rather than through a hub): Microsoft — Fix USB-C problems in Windows
Device Manager error codes, including Code 43 (“Windows has stopped this device… device descriptor request failed”): Microsoft — Error codes in Device Manager in Windows

The USB selective suspend, USB Root Hub power-management, Fast Startup, and Device Manager reinstall/rescan steps above are standard built-in Windows 10/11 settings and procedures.

Steps are for Windows 10 and 11 in 2026; menu names vary slightly by version and manufacturer. Found an error? Email hello@techfuelhq.com with the article URL.

Best NAS Hard Drives 2026: Picks by Use Case + Real $/TB Math

LK Wood IV — Fri, 03 Jul 2026 00:00:00 -0500

By LK Wood IV · Published 2026-07-03 · Updated 2026-07-03 · ~12 min read · St. Louis County, MO

TL;DR · What to actually buy in 2026

Top pick / 24-7 heavier duty: Seagate IronWolf Pro or WD Red Pro. All-CMR, 550TB/year workload, 5-year warranty. IronWolf Pro adds 3 years of Rescue data recovery.
Best for a 4-bay home NAS: WD Red Plus (2-12TB, all CMR, 180TB/year, 3-year warranty) — built for up-to-8-bay RAID and quieter/cheaper than the Pro tier.
Best for Plex / media bulk: whichever CMR drive gives the lowest $/TB at 8-16TB — capacity for the library, and a single drive already outruns your home network.
Best budget / value: a recertified big-capacity CMR drive. A recertified 16TB IronWolf Pro was $31.25/TB — the cheapest per-TB in our July 3 pull — but check the warranty terms.
The one rule: buy CMR, never SMR, for any NAS. Avoid the legacy WD Red "EFAX" SMR drives.

Spec numbers are from the manufacturers' current data sheets. All prices are a live Amazon snapshot dated 2026-07-03 and move week to week — check the retailer link before buying.

The short version

Buying a NAS drive in 2026 comes down to three decisions, in this order: CMR not SMR (non-negotiable for RAID), the right tier for your workload (a home 4-bay NAS does not need an enterprise-grade drive), and the right capacity at the right price-per-terabyte (which, as you’ll see below, does not automatically favor the biggest drive). Get those three right and brand is almost a coin flip — Western Digital, Seagate, and Toshiba all make solid current-generation CMR NAS drives.

This guide leans on two things most competing listicles skip: real dollar-per-terabyte math from a dated live price pull, and the recertified-drive economics that a growing number of homelabbers use to beat the 2026 hard-drive price crunch. We have not benchmarked these drives ourselves — every reliability and workload number here comes straight from the manufacturer spec sheets, cited inline. For the box these drives go into, see our companion budget NAS build guide — or, if you’re building a media server, the best NAS for Plex and Jellyfin, where hardware transcoding rather than capacity drives the pick. This page is about the disks.

Picks by use case

Best for a 4-bay home NAS: WD Red Plus

The WD Red Plus line is purpose-built for exactly this: WD’s own product brief positions it “for RAID-optimized NAS systems with up to 8 bays.” It spans 2TB to 12TB and is all-CMR at every capacity per the WD Red Plus data sheet (Sep 2025). The core spec across the line: 180TB/year workload rate, 1,000,000-hour MTBF, and a 3-year limited warranty. RPM varies by model — the current 12TB and 10TB SKUs are 7200 RPM, while the 8TB and below run 5400/5640 RPM, which keeps the smaller drives quieter and cooler for a home shelf or closet. (Note: the specific 12TB row we priced below is the older WD120EFAX, which is the 5400-RPM variant — the current 7200-RPM 12TB is the newer WD120EFBX. Both are CMR.)

Why it wins the home slot: you get genuine NAS-rated CMR reliability without paying the Pro-tier premium, and the 180TB/year workload is plenty for a household that isn’t hammering the array around the clock. A new 8TB WD Red Plus (WD80EFZZ) ran $339.99 — $42.50/TB in our July 3 pull (Amazon).

Best for 24-7 heavier duty: Seagate IronWolf Pro or WD Red Pro

If your NAS runs constantly, hosts many users, or lives in an 8+ bay chassis, step up to the Pro tier — and note that both leaders roughly triple the workload rating of the home drives.

Seagate IronWolf Pro is an all-CMR portfolio; Seagate states plainly that “all IronWolf Pro drives utilize conventional magnetic recording (CMR) technology.” The current top capacities reach 30TB and 28TB, rated for a 550TB/year workload, 2,500,000-hour MTBF, 7200 RPM, and a 5-year limited warranty, per the IronWolf Pro data sheet. Its signature extra is 3 years of complimentary Rescue Data Recovery Services bundled in — a real safety net if a drive dies with data you never backed up (though you should back up anyway).

WD Red Pro matches the mission: all-CMR from 2TB up to 26TB, 550TB/year workload, 7200 RPM across the whole line, and a 5-year limited warranty, per the WD Red Pro data sheet (Jan 2025). MTBF is 2,500,000 hours on the 14TB-26TB models and 2,000,000 hours on the 2TB-12TB models. The largest capacities (22-26TB) use OptiNAND; the big models are helium-sealed for lower power and heat.

Between the two, the tie-breakers are price at your target capacity and whether the IronWolf Pro’s bundled Rescue service matters to you. Both are correct answers for a heavy 24-7 array. And if you’re deciding specifically between IronWolf, IronWolf Pro, and an enterprise Exos, our Seagate NAS drive breakdown settles which of the three fits your bays and budget.

Best for Plex / media bulk: the lowest-$/TB CMR drive at 8-16TB

For a media server, you are buying capacity per dollar, not raw speed — a single spinning NAS drive already saturates a typical home network, so IOPS is rarely the constraint for streaming. That flips the decision into a straight $/TB shopping exercise across the CMR families, in the 8-16TB band where value tends to concentrate.

Two honest caveats from our own price pull, both covered in the table below: (1) among new drives, bigger did not mean cheaper per-TB — the new 12TB WD Red Plus ($48.53/TB) was pricier per terabyte than the new 8TB ($42.50/TB); and (2) the outright value champion was a recertified 16TB IronWolf Pro at $31.25/TB. So for media bulk, shop the live $/TB at 8-16TB rather than assuming the biggest new drive is the best deal, and seriously consider recertified for the bulk tier. For the transcoding side of a media box, our best GPU for Plex/Jellyfin guide covers the compute half.

Best budget: a recertified big-capacity CMR drive (with eyes open)

The cheapest way to fill bays in 2026 is a recertified enterprise-class or NAS-Pro CMR drive. In our July 3 pull the recertified 16TB IronWolf Pro (ST16000NE000) was $499.99 = $31.25/TB, versus $640 = $40.00/TB for the same model listed as new — a ~22% discount and the lowest cost-per-terabyte in the entire comparison (recertified Amazon listing). (The $640 “new” anchor came from a third-party marketplace listing rather than a first-party pristine-new sale, so treat it as the same-model reference price, not a guaranteed factory-new quote.) The trade-offs are real and covered in the recertified section below: thinner warranty and thinner review counts. This is a value play for someone running redundancy and backups, not a set-and-forget pick.

For budget on a new drive, the standard-tier lines (base Seagate IronWolf, standard Toshiba N300) exist, but note Toshiba’s N300 8TB was actually the most expensive per-TB new drive in our pull at $55.59/TB — so “budget brand” does not always mean budget price at a given capacity. Shop the number, not the label.

CMR vs SMR — and the WD Red history you should know

This is the single most important technical distinction for a NAS drive, and it has a real cautionary tale attached.

CMR (conventional magnetic recording) writes data tracks side by side. SMR (shingled magnetic recording) overlaps tracks like roof shingles to pack in more areal density. Seagate frames it cleanly on its official CMR/SMR list: CMR is the plug-and-play choice for standard NAS deployments that prioritize reliability, while SMR is best only for sequential, write-once workloads (archives, backup tiers) and generally wants SMR-aware file systems. The practical NAS problem is that SMR’s device-managed garbage collection and band-rewrite behavior can drastically slow random writes and RAID rebuilds — the worst possible time for a drive to crawl is while your array is rebuilding after a failure.

The reason NAS buyers learned to check this the hard way: around 2020, plain WD Red (non-Plus) “EFAX” drives were quietly SMR. Western Digital’s own WD Red product brief lists the WD60EFAX (6TB), WD40EFAX (4TB), WD30EFAX (3TB), and WD20EFAX (2TB) as SMR, and WD’s own blog statement names the same capacities directly — “our current device-managed shingled magnetic recording (DMSMR) (2TB, 3TB, 4TB, and 6TB) WD Red series.” Those are the drives at the center of the SMR-in-NAS backlash, and they are why the “Plus” and “Pro” branding exists. WD’s official CMR/SMR determination page advises checking each drive’s data sheet to confirm whether it uses CMR or SMR — which we’ve done for you here.

The good news for 2026: every current dedicated NAS-Pro family is 100% CMR. The WD Red Plus, WD Red Pro, Seagate IronWolf and IronWolf Pro, and Toshiba N300 and N300 Pro data sheets all read CMR across every capacity, and Seagate flags zero IronWolf-family drives as SMR on its product list. So the practical rule is simple: buy a current NAS-Pro CMR drive and steer clear of the legacy EFAX SKUs on the used market.

Live $/TB table — dated 2026-07-03

Below is a live US Amazon price snapshot captured 2026-07-03. Every price is from that pull; drives our source did not return with a verified new price are noted rather than guessed. $/TB uses the drive’s marketed (decimal) capacity. Prices move week to week — treat this as a method, not a promise, and check the retailer link before buying.

Drive (model)	Condition	Capacity	Price	$/TB	Recording	Link
Seagate IronWolf Pro (ST16000NE000)	Recertified	16TB	$499.99	$31.25	CMR	Amazon
Seagate IronWolf Pro (ST16000NE000)	New	16TB	$640.00	$40.00	CMR	Amazon
WD Red Plus (WD80EFZZ)	New	8TB	$339.99	$42.50	CMR	Amazon
WD Red Plus (WD80EFZZ)	Renewed	8TB	$275.00	$34.38	CMR	Amazon
WD Red Plus (WD120EFAX)	New	12TB	$582.35	$48.53	CMR	Amazon
Toshiba N300 (HDWG780EZSTA)	New	8TB	$444.70	$55.59	CMR	Amazon

Two takeaways jump out of this table. First, recertified big-capacity is the $/TB champion — the recertified 16TB IronWolf Pro at $31.25/TB beat every new drive here. Second, higher capacity did not automatically lower $/TB among new drives — the new 12TB Red Plus ($48.53/TB) cost more per terabyte than the new 8TB ($42.50/TB), and the new Toshiba N300 8TB ($55.59/TB) was the priciest per-TB of the lot. The lesson: run the per-TB number for your specific target capacity on the day you buy, rather than assuming bigger or a “value brand” is automatically cheaper. (One gap: our pull returned no verified new price for the non-Pro Seagate IronWolf 8TB, so it is omitted rather than invented.)

Recertified drives — what the seller pages actually say

Recertified and renewed drives are the biggest under-covered angle in NAS-drive buying, and the price crunch of 2026 has made them mainstream. Here is what’s real, stated straight from seller documentation rather than forum lore.

The discount is real: across two clean same-model comparisons in our July 3 pull, recertified/renewed ran ~19-22% below new — the 8TB WD Red Plus at $275 renewed vs $339.99 new (~19%), and the 16TB IronWolf Pro at $499.99 recertified vs $640 new (~22%). Renewed/recertified listings showed up in every search we ran.

The warranty catch is also real. ServerPartDeals — a common recertified-drive seller — defines a “Manufacturer Recertified” drive in its FAQ as an item “tested, recertified, and approved by the original manufacturer… without a manufacturer warranty.” In other words, the original manufacturer warranty does not carry over. The coverage you actually get is the seller’s own, stated per product — one live recertified Exos listing shows a “2 Year Limited Period Warranty” plus a 30-day satisfaction return window. Warranty length is set per product, not by a single site-wide number, so read the specific listing.

Second signal to watch: review depth. The renewed 8TB WD Red Plus in our pull carried only 3 ratings versus 1,100 on the new version of the same model — a thin trust signal worth weighing.

Net: recertified is a smart value move if you run redundancy (RAID/RAIDZ so a single failure doesn’t lose data), keep a real 3-2-1 backup, and accept a seller warranty in place of the manufacturer’s. It is not the pick for someone running a single drive with no backup.

What the competition skips (our angle)

We read the current top-ranking guides before writing this. Most of them cover the CMR-vs-SMR basics well — that part is table stakes now. What they consistently don’t give you:

Real $/TB math. The mainstream listicles tell you to “buy the largest drive that makes sense” without ever computing cost per terabyte — which, as our table shows, is exactly where the counterintuitive results hide (bigger isn’t always cheaper per-TB).
Recertified/refurbished economics. Even though cheap-drive shopping is one of the most common questions homelabbers ask, the standard listicles say nothing about the ~19-22% recertified discount (measured in our dated table above) or the warranty trade-off. That’s the single biggest money lever for a homelabber right now.
Honest homelab-vs-enterprise separation. Guides tend to jump from “home” straight to “small business,” glossing over the fact that a 4-bay household NAS is genuinely better served by the cheaper, quieter Red Plus tier than by an enterprise drive.

That’s the gap this guide fills: cited specs for reliability, a dated $/TB table for price, and the recertified math laid out honestly.

Best budget NAS builds 2026 — the chassis and platform these drives go into.
DAS vs NAS in 2026 — whether you even need a networked box, or a simpler direct-attached enclosure.
TrueNAS vs Unraid vs Proxmox storage backend — the OS/filesystem layer that turns these disks into a pool.
NAS storage calculator — work out real usable capacity after RAID redundancy before you buy.
Transfer time calculator — estimate how long it takes to fill or migrate an array.
Best NVMe SSDs for a homelab 2026 — the cache/fast-pool half of a hybrid NAS.

Self-Hosted Discord Alternatives (2026): The Honest Hardware-Grounded Comparison

LK Wood IV — Fri, 03 Jul 2026 00:00:00 -0500

The one-paragraph version: There is no drop-in self-hosted replacement for Discord in 2026, and any guide that hands you a single “winner” is skipping the hard part. The honest answer is a match to what you use Discord for. Want the closest-looking clone? Stoat (the platform formerly called Revolt) - but it is pre-1.0 and self-hosting its voice/video is still immature. Want a federated text community with real native group calling? Matrix + Element, at the cost of the most complex setup. Running a team or workplace? Mattermost or Rocket.Chat. Threaded text only? Zulip, with the cleanest license. Just voice for a gaming group? A tiny Mumble server. The realistic outcome most communities land on is a combination - text on one tool, voice on another - plus accepting real onboarding drop-off. This guide gives you the piece the copy-paste roundups leave out: current versions, license caveats, the honest voice/video reality, and the resource footprints that are actually documented.

Most competing roundups converge on the same six-to-eight tools and produce near-identical pros/cons lists, but they share three universal blind spots: no real hardware requirements, no honest voice/video assessment, and no actual migration path. That trio is exactly where a PC-hardware-first site should be useful, so that is where this article spends its words.

The quick verdict, by use case

Your priority	Best pick	The honest caveat
Closest Discord clone (look and feel)	Stoat (formerly Revolt)	Pre-1.0; self-hosting voice/video is transitional and undocumented
Federated text community, many spaces one login	Matrix + Element	Hardest setup; no native voice channels without extra services
Team / workplace (Slack-style)	Mattermost or Rocket.Chat	Group voice and video sit behind paid tiers or external add-ons
Threaded, organized text	Zulip	No native voice or video at all
Low-latency voice for a gaming group	Mumble	Voice only; dated interface; no async text chat

The recurring pattern in real community threads is that no single self-hosted product covers Discord’s full text-plus-voice-plus-video-plus-forum-plus-roles-plus-bots bundle, so people deploy a stack: Matrix or Zulip for text alongside Mumble or Jitsi for voice. Keep that in mind before you expect one install to do everything.

Stoat (formerly Revolt): the closest clone, still under construction

First, the naming, because half the guides online are stale on it. Revolt was renamed to Stoat. The GitHub organization migrated from revoltchat to stoatchat and now describes itself as “Open source, user-first chat platform. (formerly Revolt).” The self-hosted repository documents a breaking change dated October 5, 2025 that renamed the Docker Compose project from revolt to stoat, and revolt.chat now redirects to stoat.chat. If you find a 2022-era “Revolt review,” it is describing this same software under its old name.

Stoat is the pick when you want the interface that looks and feels most like Discord. The backend, written in Rust, is at v0.13.9, published July 2, 2026 - meaning it is still pre-1.0 software. It self-hosts via Docker Compose from the stoatchat/self-hosted repo, whose README recommends a minimum footprint of at least 2 vCPUs and 2 GB of memory - notably the only candidate here that publishes a clear minimum.

The honesty gap the ranking list-posts gloss over is voice and video. Stoat is migrating its voice stack to LiveKit (replacing the older “Vortex” voice server), and self-hosting voice/video is transitional: documentation is essentially non-existent, community front-end patches have been needed to enable features, and the video implementation is incomplete - the self-hosted README even warns the server will kick any user who tries to stream video larger than a configured maximum. Voice also requires opening RTC ports (7881/tcp plus a 50000-50100/udp range). Community self-host reports back this up, describing a buggy interface, missing features, channel-creation quirks, and no built-in way to stop random users spinning up servers on your instance. Verdict: best UX match, weakest maturity. Use it for experimentation; do not bet a large community on it yet.

Matrix + Element: the most-deployed, most-federated, hardest to master

Matrix is a protocol, not one app. You run a homeserver and users connect with a client - usually Element. The recommended homeserver is Synapse, currently v1.155.0 (June 16, 2026). An important caveat for anyone following old links: the original matrix-org/synapse repository is archived and read-only; active development moved to the element-hq/synapse fork. Synapse is dual-licensed - free under AGPLv3, or under a paid Element Commercial License - an open-core arrangement that followed the 2024 relicensing.

There is a second-generation Go homeserver, Dendrite (v0.15.2, August 15, 2025), but its README states it is in maintenance mode, meaning only security fixes are applied, and the project positions it for small deployments (tens to hundreds of users) and in-browser or mobile peer-to-peer nodes rather than large community hosting. For a Discord replacement you want Synapse.

Matrix’s genuine, unique draw is federation: it is the one option that mirrors Discord’s multi-server model by letting you join many communities from a single login. That is why power users stay on it. The recurring first-hand complaint is voice: Matrix has no always-on, Discord-style voice channels by default. Native group voice and video come from Element Call (v0.20.3, June 29, 2026), which Element’s own writeup describes as built on MatrixRTC using LiveKit as its backend. Self-hosting it means deploying a LiveKit SFU plus a MatrixRTC authorization service alongside the homeserver. Once running, it supports 1:1 calls, ad-hoc in-room calls, and standalone conferences; Element’s own performance testing states that a single standard VPS machine can host up to 500 participants. The second recurring complaint is the client model itself - the Space-and-room structure is widely described as unintuitive, and setup documentation as scattered. Difficulty reports are split (some call basic server standup easy; Matrix-plus-voice is where people get stuck), and the community matrix-docker-ansible-deploy playbook is the usual recommendation to ease the base install. Verdict: best for a federated text community that will invest the setup time; the strongest native group-call story here, but not the easiest.

Mattermost and Rocket.Chat: team chat, not gaming communities

These two are consistently classed by their own users as Slack/Teams replacements rather than community or gaming Discord replacements - more corporate, with per-user considerations even when self-hosted.

Mattermost is at v11.8.2 (June 26, 2026), which includes a medium-severity security fix, so keep it patched. Two free self-host paths exist: Team Edition is free and open source under the MIT license (a single Linux binary with PostgreSQL), and Mattermost Entry is a free, feature-capped tier of the Enterprise Edition (see editions and offerings). The Enterprise binary itself is commercial (open-core). On voice: the Calls plugin is bundled by default and does WebRTC voice and screen sharing - but the free Team/Entry editions get only 1:1 calling and screen sharing (up to 40 minutes); group calling with no time limit requires a paid Professional tier or above, and scaling past roughly 50 concurrent callers needs a separate RTCD service to offload media. (Third-party pages cite Professional at around $10/user/month billed annually, but that figure was not confirmed on Mattermost’s own pricing page - treat the dollar amount as unverified; the tier structure is from official docs.)

Rocket.Chat is at v8.5.1 (June 15, 2026), MIT-licensed but with an open-core split (an ee enterprise folder and paid premium features). It self-hosts via official Docker Compose (Rocket.Chat plus MongoDB). Its video story is the weakest-by-default of the team tools: video conferencing is not native WebRTC out of the box - the documented standard path integrates an external Jitsi provider you point at your own Jitsi Meet domain. Verdict: reach for these if you are replacing Slack or standing up a workplace; they are a poor fit for a casual gaming friend-group where free, low-friction group voice is the whole point.

Zulip: excellent threaded text, no native calling

Zulip Server 12.1 (June 26, 2026) is the cleanest license of the bunch - fully open source under Apache 2.0, with no open-core caveat on the server. Its threaded model is genuinely good for organized, high-volume text discussion. But for a Discord replacement it has the weakest voice story of all the candidates: Zulip has no native built-in voice or video calling. It only inserts call links via a configured external provider - Jitsi Meet (default), Zoom, BigBlueButton, or Nextcloud Talk. There are no persistent voice channels and no built-in media server. Verdict: a strong pick if your community lives in text and you are content bolting voice on externally; a poor standalone Discord swap if voice matters.

The voice/video reality (the part other guides skip)

This is the single sharpest differentiator, and almost no competing roundup benchmarks it. Here is how native, self-hosted voice and video actually stand today:

Tool	Native group voice/video?	How it works	The real cost
Matrix + Element	Yes	Element Call on MatrixRTC + LiveKit SFU	Must deploy LiveKit + auth service; scales to ~500/call
Mattermost	Yes (bundled)	Calls plugin, WebRTC	Free tiers = 1:1 up to 40 min; group needs paid tier; 50+ callers need RTCD
Stoat	In transition	Migrating to LiveKit voice	Undocumented self-host; community patches needed; video incomplete
Rocket.Chat	Not by default	External Jitsi integration	You run a separate Jitsi instance
Zulip	No	External call links only	No persistent voice channels
Mumble	Voice only	Opus codec (which itself scales up to 510 kbps)	No text/video; low latency; tiny footprint

Two practical takeaways. First, screen sharing - an under-served sub-intent that appears in the related searches for this topic - is best served today by Mattermost’s bundled Calls plugin, then by Matrix via Element Call; Rocket.Chat routes it through Jitsi, and Zulip cannot do it natively. Second, if all you need is voice for a gaming group, a self-hosted Mumble server remains the community favorite: it is praised for low latency and near-zero resource use, it uses the Opus codec (which itself scales up to 510 kbps), and its main limitation is that it is voice-only with a dated interface and no async chat.

Resource footprint: what is actually documented

A word of caution, because this is where roundups invent numbers. Of these projects, only Stoat publishes a clear minimum in the sources checked: at least 2 vCPUs and 2 GB of memory. Synapse, Mattermost, Rocket.Chat, and Zulip did not surface hard minimums on the pages reviewed, so anyone quoting exact RAM figures for those is usually guessing.

Tool	Documented minimum	Notes
Stoat	2 vCPUs, 2 GB RAM	From the self-hosted README
Matrix (Synapse)	Not published on pages checked	Plan by workload; voice adds a LiveKit SFU
Mattermost	Not published on pages checked	Single binary + PostgreSQL; RTCD for scale
Rocket.Chat	Not published on pages checked	Runs with MongoDB
Zulip	Not published on pages checked	Install script or Docker

The honest planning rule: a small, text-only community is light on any of these, but the moment you add native voice/video the picture changes - a LiveKit SFU for Matrix or an RTCD service for Mattermost adds both CPU load and real bandwidth. If you want to size a chat server against the rest of your homelab, our Docker RAM planner helps you budget memory across a multi-service stack, and chat servers are firmly in the “give them headroom” category.

Migration reality: expect friction, plan to dual-run

The 2026 wave of interest is driven by Discord’s age-assurance rollout, which introduced age-verification methods (an on-device facial age estimate or an ID/selfie check) and pushed communities to look for exits. But wanting to leave and actually moving your people are different problems, and the community consensus is blunt about the gap.

None of these tools ship a real Discord-community migration path or import tooling - that is the third universal gap across every competing guide. And the single biggest reason people give up and stay on, or return to, Discord is onboarding friction for non-technical members. Discord’s “open this link and you are in the voice call” flow has no self-hosted equal; even a few-dollars-a-year hosted alternative adds enough friction to stall adoption among casual users. Churn runs both ways, too - screen-sharing quality is a documented reason some groups moved to Discord in the first place.

So the realistic plan is not a clean cutover. It is:

Match the tool to your primary need using the verdict table above - text-first vs voice-first is the fork that matters most.
Accept a combination stack if you need both - text on Matrix or Zulip, voice on Mumble or Jitsi - because no single product covers the whole bundle.
Dual-run the self-hosted space alongside Discord for a while, and expect meaningful drop-off from members who will not install a second app.

If self-hosted chat is your first serious service, our self-hosting essentials priority guide covers what to stand up first and why, the broader self-hosted apps to replace SaaS roundup sets the context, and since Matrix and Rocket.Chat both ship Compose files, the Docker Compose starter-stack tutorial is the fastest way to get a test instance running.

Bottom line

Do not chase a single “best” self-hosted Discord alternative - it does not exist in 2026. Decide whether your community is fundamentally about text or voice, pick the tool that owns that axis (Matrix or Zulip for text, Mumble for voice, Stoat if you truly need the Discord look and can tolerate pre-1.0 rough edges, Mattermost or Rocket.Chat for teams), and plan for the migration friction that sinks most attempts. Get the voice/video architecture and the onboarding right and the tool choice mostly takes care of itself.

Grafana vs Prometheus: What Each Actually Does (And Do You Need Both?)

LK Wood IV — Thu, 02 Jul 2026 00:00:00 -0500

Search “grafana vs prometheus” and the top results all open with the same correct sentence — they’re complementary, not competitors — and then spend two thousand words on Kubernetes federation and enterprise observability platforms. Correct framing, wrong audience. If you’re a self-hoster deciding what to actually deploy on your Docker host this weekend, the questions that matter are different: what does each piece really do, which alerting system should you use (there are two, and that’s the real “vs”), and what does the whole stack cost in RAM? Those are the questions this guide answers, with numbers from the stack we actually run.

The one-paragraph version: Prometheus collects and stores metrics — it scrapes exporters on your machines every 15 seconds into its own time-series database and evaluates alert rules. Grafana visualizes them — it queries Prometheus (or ~50 other data sources) and turns the numbers into dashboards. You deploy both, they fit in well under a gigabyte of RAM, and the only genuine either/or decision inside the stack is Alertmanager vs Grafana Alerting. Everything below unpacks that.

What Prometheus actually does

Prometheus (currently 3.x LTS, Apache 2.0, an independent CNCF project) is the data layer:

Pull-based scraping. Prometheus polls HTTP endpoints called exporters on an interval (15s is the common default). Nothing pushes to it; it fetches.
A built-in time-series database (TSDB). Metrics land on local disk with configurable retention (15 days by default). Per the official storage docs, Prometheus “stores an average of only 1-2 bytes per sample” — the documented capacity formula is retention_seconds × samples_per_second × bytes_per_sample. In practice, our 5-node stack at 15-day retention sits in the low single-digit gigabytes.
PromQL. The query language for rates, aggregations, and alert conditions — the same expressions power both dashboards and alerts.
The exporter ecosystem. This is why Prometheus owns homelab monitoring: node_exporter for Linux hosts (~15MB RAM each), windows_exporter, pve-exporter for Proxmox, cAdvisor for Docker containers, blackbox_exporter for HTTP/ping probes.

What Prometheus deliberately does not do: dashboards. Its built-in expression browser is a debugging tool, not a UI you’d live in. And it doesn’t handle logs — metrics only.

What Grafana actually does

Grafana (currently 13.x; OSS core AGPLv3 since v8.0, plugins Apache 2.0) is the presentation layer:

Dashboards. Drag-and-drop panels — time series, gauges, heatmaps, stat panels, tables. The community dashboard library means a full Linux-host dashboard is an import-by-ID away.
Data-source agnostic. Prometheus is one of dozens of native sources alongside Loki, InfluxDB, MySQL, Elasticsearch, CloudWatch, and more. Grafana is the one pane of glass over all of them.
Grafana Alerting. Since Grafana 9, a unified alerting system that creates alert rules against any data source through the GUI, with notification “contact points” configured in the UI.

What Grafana cannot do: collect or store anything. No scraping, no database. Without a backend it’s an empty shell — which is precisely why the “vs” framing fails.

The real comparison: Prometheus Alertmanager vs Grafana Alerting

Here’s the genuine either/or decision inside the stack, and the one the usual comparisons skip entirely. Both tools can fire alerts; they do it very differently.

Prometheus Alertmanager is a separate small binary. Prometheus evaluates alert rules you write in YAML (PromQL expressions with thresholds and durations) and fires them to Alertmanager, which handles deduplication, grouping, silencing, inhibition, and routing to Slack, Discord, email, PagerDuty, Telegram, or webhooks. Its strengths: alerts live in version-controllable YAML files (alerts-as-code), and its routing trees handle genuinely complex logic. Its cost: you’re writing YAML and PromQL, not clicking a UI.

Grafana Alerting builds rules through the GUI against any data source, not just Prometheus. Contact points and notification policies are configured visually, and it can even import Prometheus-compatible rules. Its strengths: much gentler learning curve, and it’s your only option if your data source isn’t Prometheus. Its cost: complex routing is weaker than Alertmanager’s trees, and click-configured alerts are harder to version-control.

The homelab recommendation: if you run the full stack, define your core infrastructure alerts (disk filling, host down, RAM pressure) in Prometheus + Alertmanager — they’re code, they’re in Git, they survive a Grafana reinstall — and use Grafana Alerting for ad-hoc or dashboard-adjacent alerts. The two coexist without conflict. If you only have Grafana over a non-Prometheus source, Grafana Alerting is the answer by default.

Comparison table

	Prometheus	Grafana
Primary role	Metrics collection + time-series storage	Visualization + dashboards
Data model	Pull-based scrape → labeled time series	Source-agnostic queries to backends
Alerting	Alertmanager (YAML rules, routing trees)	Grafana Alerting (GUI, any data source)
Dashboards	Minimal expression browser	Full dashboard builder + community library
Storage	Built-in TSDB, ~1-2 bytes/sample	None — queries external sources
Homelab RAM (5 nodes)	200–400MB (15-day retention)	100–200MB
License	Apache 2.0 (CNCF)	AGPLv3 core (since v8.0), Apache 2.0 plugins
Can you skip it?	Only if your metrics live elsewhere	Only if you never want dashboards

The homelab stack: what you actually deploy, and what it costs

The standard self-hosted composition — the one our full setup guide walks through end to end — is four pieces:

Component	Count (5-node homelab)	RAM
Node Exporter	one per monitored machine	~15MB each (~75MB)
pve-exporter (Proxmox)	1	~30MB
Prometheus (15-day retention)	1	200–400MB
Grafana	1	100–200MB
Alertmanager	1	~50MB
Total		~450–750MB — budget 600–800MB

Those are our first-party tested numbers, not vendor specs. CPU is a non-issue on anything with two modern cores; disk lands at a few gigabytes with default retention (compute your own with the official formula above). A Raspberry Pi 4 with 4GB runs the full stack — put the Prometheus TSDB on an SSD, not an SD card, because the write pattern will eat cheap flash. If you’re budgeting the whole Docker host, our Docker RAM planner accounts for the monitoring stack alongside your other services.

Can you skip one? Prometheus without Grafana works — your alerts still fire — but you lose the visibility that’s half the point. Grafana without Prometheus only makes sense when your metrics already live in another backend. For 95% of homelabs, the answer is both, and at ~600MB total the economics don’t justify agonizing over it.

When the full stack is overkill

Honest caveat: if all you want is “is my server up and roughly how busy is it,” Prometheus + Grafana is more machinery than you need. Lighter single-binary tools — Beszel, Netdata, Glances — give you instant per-host visibility with near-zero setup; we compare them in our lightweight monitoring roundup. The Prometheus stack earns its place when you want history (“what was the CPU doing three hours before the crash?”), cross-host dashboards, and real alerting. And if you’d rather not host it at all, Grafana Cloud’s free tier (10K series, 14-day retention, 3 users) exists — at the philosophical cost of shipping your homelab’s metrics to someone else’s cloud.

Bottom line

Prometheus is the data layer; Grafana is the glass. Deploy both — via our step-by-step stack guide or as an addition to your Docker Compose stack — put your load-bearing alerts in Alertmanager where they’re version-controlled, use Grafana’s alerting for everything visual, and the whole thing costs you well under a gigabyte of RAM. The “vs” was never real; the layering is.

Proxmox vs Docker: They're Not Rivals — What to Actually Run Where (2026)

LK Wood IV — Thu, 02 Jul 2026 00:00:00 -0500

Type “proxmox vs docker” into any search engine and you’ll find a decade of forum threads arguing about the wrong question. Proxmox VE and Docker are not competitors. Proxmox VE 9 is a Type-1 hypervisor — it owns your physical hardware and carves it into virtual machines and LXC containers. Docker is an application runtime — it packages a single app and its dependencies into a portable image and runs it. One is the foundation of your homelab; the other is something you run on that foundation. The real 2026 decision is not which to pick — it’s how to layer them: Docker inside a Proxmox VM, Docker inside an LXC, Proxmox-native LXC per service with no Docker at all, or (new this cycle) Proxmox’s own OCI container support.

This guide gives you the layered answer with the details the usual comparisons skip: what Proxmox’s documentation actually recommends (with the real quote, not the folklore), the ZFS storage-driver conflict that silently breaks Docker-in-LXC on most Proxmox hosts, where GPU passthrough really stands for each option, and a decision tree you can run your own setup through. If you’re still deciding between containers and VMs at the Proxmox layer itself, start with our LXC vs VM breakdown — this article picks up where that one ends.

What Proxmox VE actually is (2026)

Proxmox VE is a free, open-source (AGPLv3) Type-1 hypervisor, currently at version 9.2. In Proxmox’s own words, it “tightly integrates the KVM hypervisor and Linux Containers (LXC), software-defined storage and networking functionality, on a single platform.” In practice that means:

Full KVM virtual machines — Windows, pfSense/OPNsense, Home Assistant OS, anything with its own kernel.
LXC system containers — lightweight full-Linux-OS containers sharing the host kernel, each with its own IP and filesystem.
A web UI, clustering, and snapshots — plus first-class Proxmox Backup Server integration for deduplicated, incremental backups of every VM and container.

The no-subscription repository makes it fully usable for homelab without paying anything.

What Docker actually is

Docker Engine is an application container runtime. It pulls OCI-format images (from Docker Hub or anywhere else), layers them onto a shared host kernel, and starts them in under a second. Its real superpower for self-hosters is the ecosystem: nearly every project you’d want to self-host publishes a docker-compose.yml, and Docker Compose turns a whole multi-service stack into one file and one command. What Docker is not: a hypervisor. It can’t run Windows, can’t give a workload its own kernel, and doesn’t manage your physical host. It also isn’t the only engine that runs OCI images — Podman does the same thing daemonlessly and rootless by default, which is a separate decision from the layering question here.

Why the question is framed wrong

Because the two tools sit at different layers, “Proxmox vs Docker” really decomposes into two separate questions:

Should my bare metal run Proxmox? For almost any homelab beyond a single-purpose box: yes. Even if you only ever run Docker, putting Proxmox underneath costs you a few percent overhead and buys you snapshots, easy reinstalls, backups, and the freedom to add a VM later. (If you are weighing that hypervisor choice against VMware, the Proxmox vs ESXi breakdown covers why the free tier lands on Proxmox after Broadcom.)
How should Docker run on that host? This is the decision with real trade-offs — and it’s the rest of this article.

The four ways to run containers on Proxmox

	Proxmox LXC (native)	Docker in a VM	Docker in an LXC	Proxmox OCI (PVE 9.1+, preview)
Shares host kernel	Yes	No (own kernel)	Yes	Yes
Isolation	Medium	High	Low–medium	Medium
RAM overhead	Minimal	~0.5–1 GB per VM	Minimal	Minimal
Boot time	<1 s	15–45 s	<1 s	<1 s
PBS backup story	Full container backup	Full VM backup, volumes included	Full container backup	Container backup
Docker Compose	No	Yes, native	Yes (nesting=1)	No
GPU access	Device bind mount	Full VFIO passthrough	Device bind mount	Not documented
ZFS host compatibility	Native	Native	Native since OpenZFS 2.2 (PVE 8.1+)	Native
Official Proxmox guidance	First-class	Recommended for Docker	VM recommended instead	Technology preview
Best for	Single Linux services	Compose stacks, anything important	RAM-starved hosts, trusted services	Experiments

The Docker-in-LXC debate: what Proxmox actually says

The claim you’ll see everywhere is “Proxmox officially discourages Docker in LXC.” The reality is more precise. There is no wiki page banning it (the oft-cited Docker_on_LXC page simply doesn’t exist), but the official Proxmox documentation does take a position — quoted in Proxmox’s own forum best-practices thread:

“…it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and the ability to live-migrate.”

So: a recommendation toward VMs, not a prohibition of LXC. In homelab practice, Docker inside an LXC with features: nesting=1 (add keyctl=1 for some workloads) runs reliably for trusted, internal services — that’s the long-standing consensus across the Proxmox forums and communities like LearnLinuxTV.

The famous ZFS gotcha — now mostly historical. For years, Docker’s default overlay2 storage driver didn’t support ZFS backing filesystems, so Docker inside an LXC on a ZFS-backed Proxmox host fell back badly out of the box, and the community fix was switching to fuse-overlayfs. OpenZFS 2.2 changed this: it added native overlayfs support, so on Proxmox VE 8.1+ (and PVE 9, which ships OpenZFS 2.3) overlay2 simply works in an LXC on ZFS. If you’re on an older pool or you see overlay errors, fuse-overlayfs remains the fallback — or skip the whole question and run Docker in a VM, where the guest’s ext4 makes it a non-issue.

Backup reality: where each option wins

This is the most under-weighted factor in every comparison we read, and it’s where the layered setup pays off:

Docker in a VM + PBS — Proxmox Backup Server snapshots the entire VM: Docker Engine, every container, every named volume, all application data. Restoring your whole stack after a bad upgrade is one operation. This is the best backup story in self-hosting.
LXC (native or with Docker) + PBS — also good: PBS backs up the full container.
Docker on bare metal — you own the problem: volume-by-volume backups with tar jobs or Restic, plus the compose files, plus remembering how it all fit together. It works, but it’s the reason bare-metal Docker hosts tend to be rebuilt rather than restored.

GPU passthrough: which setup actually works

VM + VFIO — the reliable path. Pass the full GPU to a VM (our step-by-step guide), then install Docker plus the NVIDIA Container Toolkit inside it. This is the standard setup for Ollama, Stable Diffusion, Jellyfin/Plex hardware transcode.
LXC + device bind mount — contrary to what some comparison pages claim, LXC GPU access does exist: you bind-mount the /dev/nvidia* devices and match driver versions between host and container. It works for CUDA workloads and it’s lighter than a VM — but it’s a different mechanism from VFIO, it couples the container to host driver versions, and it’s more fragile across upgrades.
Docker bare metal — works, but again forfeits the hypervisor’s snapshot/backup layer around it.

What about Proxmox 9’s native OCI support?

New since PVE 9.1: you can create LXC containers directly from OCI images — the same image format Docker uses. Per the official release notes, creating system containers from suitable OCI images is supported, while application containers from OCI images are explicitly a technology preview. There is no Compose equivalent, no orchestration, and no ecosystem around it yet. It’s a genuinely interesting direction — one image standard across your whole stack — but in mid-2026 it is not a Docker replacement for a real homelab. Watch it; don’t build on it.

The honest decision tree

Run your setup through this, top to bottom:

Need Windows, pfSense, Home Assistant OS, or any non-Linux workload? You need Proxmox VMs regardless. Docker slots in as one more VM.
GPU-accelerated containers (LLMs, Stable Diffusion, transcoding)? Docker in a VM with VFIO passthrough.
Want one-step restore of your whole stack, data included? Docker in a VM, backed up by PBS.
Proxmox host on ZFS and set on Docker-in-LXC? On PVE 8.1+ (OpenZFS 2.2+) overlay2 works natively; on an older pool, use fuse-overlayfs inside the container — and know why.
Under 16 GB of RAM and every megabyte counts? Docker in an LXC with nesting=1 for trusted, internal-only services is a legitimate choice — size it with our Docker RAM planner.
Just running a handful of single Linux services (DNS, reverse proxy, monitoring)? Proxmox-native LXC per service, no Docker needed — lowest overhead, per-service IPs, clean PBS backups.

Most homelabs end up hybrid: a couple of native LXCs for infrastructure services, one Docker VM for the Compose stacks, and headroom for the odd full VM. If that’s where you land, our Docker Compose starter stack fills the Docker VM in about half an hour, and the Proxmox capacity planner tells you how much host you actually need.

Bottom line

Proxmox and Docker answer different questions. Proxmox decides how your hardware is divided; Docker decides how applications are packaged. Put Proxmox on the metal, put Docker in a VM on top of it (or in an LXC if you know the trade-offs and your storage driver), and you get the ecosystem of Docker with the snapshots, backups, and flexibility of a real hypervisor underneath. That layered setup — not a winner-take-all choice — is why the “vs” framing never quite made sense.

WireGuard vs OpenVPN for the Homelab (2026): A Self-Hoster's Decision Guide

LK Wood IV — Thu, 02 Jul 2026 00:00:00 -0500

If you’re comparing WireGuard and OpenVPN, most of what you’ll find is written for commercial VPN shoppers — which provider’s app is faster, which unblocks more streaming. This is the other version of the question: you’re a self-hoster putting a VPN server on your own router, Raspberry Pi, or Proxmox container so you can reach your homelab from anywhere (and maybe link two sites). For that job, the 2026 answer is direct: WireGuard is the default, and OpenVPN survives for exactly one scenario — networks where UDP is blocked and only TCP on port 443 gets out. The rest of this guide is the evidence, the benchmarks from our own hardware, and the configurations where each one earns its place.

(If your actual question is “WireGuard or Tailscale,” that’s a different comparison — Tailscale is WireGuard plus a coordination layer. This article is about the raw protocols you host yourself.)

Protocol architecture: what you’re actually running

WireGuard lives in the Linux kernel (mainlined in 5.6, 2020) and is famously small — about 4,000 lines of code in the original kernel implementation, per its NDSS 2017 academic paper. Its cryptography is fixed, not negotiated: ChaCha20-Poly1305 for authenticated encryption, Curve25519 for key exchange, BLAKE2s for hashing, HKDF for key derivation, in a Noise IKpsk2 handshake — all specified on the official protocol page. Identity is just a key pair, like SSH. It is UDP-only by design (the project explicitly avoids TCP tunneling because TCP-over-TCP degrades badly), and it roams beautifully: when your phone hops from WiFi to LTE, the server just starts replying to the new address — no re-key, no reconnect dance.

OpenVPN is the two-decade veteran: a userspace daemon built on TLS via OpenSSL, with negotiated ciphers (AES-256-GCM is typical; ChaCha20-Poly1305 is available in modern builds), a full PKI — CA certificate, server certificate, client certificates — and both UDP and TCP modes. The codebase is roughly 70,000 lines, an order of magnitude larger than WireGuard. That heft buys flexibility: cipher policy compliance, user/password auth options, and the single killer feature WireGuard deliberately lacks — TCP on port 443, where VPN traffic is effectively indistinguishable from ordinary HTTPS at the packet-inspection layer.

Performance: the honest picture on homelab hardware

Test	WireGuard	OpenVPN	Source
Netgate 4100, single tunnel	941 Mbps	not benched	our own firewall stack bench
GL.iNet Flint 2 (OpenWrt)	~900 Mbps	not benched	independent reviews, per our gear guide
PIA vendor test (US)	~180 Mbps	~120 Mbps	vendor-conducted, conditions undisclosed
ExpressVPN latency (UK, same server)	40 ms	113 ms (TCP)	vendor-conducted

The honest framing: the “3–4x faster” claim that circulates comes from vendor tests and old benchmarks — WireGuard’s own performance page openly calls its published numbers “old, crusty, and not super well conducted,” and critics have noted the original whitepaper benchmarks used 64KB jumbo frames rather than real ~1500-byte internet packets. The defensible version: on Linux, WireGuard’s kernel-space path gives it a real CPU-efficiency edge (roughly 1.3–1.5x in comparable tests, and much lower latency than OpenVPN-over-TCP), while on Windows and macOS it runs in userspace (wireguard-go) and the gap narrows. For a homelab, both protocols are faster than your WAN link. A modest firewall appliance pushes WireGuard at wire speed — 941 Mbps on our Netgate 4100 at 14W. The protocol is not your bottleneck; pick on traversal, config complexity, and use case instead.

The comparison table

	WireGuard	OpenVPN
Transport	UDP only	UDP or TCP (incl. port 443)
Blocked-network traversal	Fails if UDP filtered (needs a wrapper)	TCP/443 passes almost everything
Crypto	Fixed modern suite (ChaCha20-Poly1305, Curve25519)	Negotiated via OpenSSL (agile, misconfigurable)
Codebase	~4,000 lines (kernel implementation)	~70,000 lines
Security review	Formal verifications (Tamarin, eCK/ACCE, ProVerif, verified Curve25519)	Two decades of production use + independent audits
Setup	Key pair + a dozen config lines per peer	Full PKI: CA, server cert, client certs, config
Roaming (WiFi ↔ LTE)	Automatic, no reconnect	Reconnect required
Site-to-site	Symmetric peer config	Server/client model, more moving parts
Kernel-space (Linux)	Yes	No (userspace + tun driver)
DPI visibility	Identifiable as WireGuard	TCP/443 mode blends with HTTPS

Road-warrior: reaching your homelab from anywhere

This is the case most self-hosters actually have — laptop or phone out in the world, homelab at home.

WireGuard wins every normal network: home WiFi, coffee shops, cellular. Sub-second connections, silent roaming, a battery-friendly protocol, and clients on every platform. Our WireGuard-on-Proxmox guide gets a road-warrior server running in an afternoon.
OpenVPN wins the hostile networks: corporate offices that block outbound UDP, hotel and airport captive portals, ISPs that filter VPN traffic. OpenVPN in TCP mode on port 443 looks like HTTPS and gets through.
The simple test: from the restrictive network, check whether you can reach your home IP on UDP 51820. Reachable → WireGuard. Blocked → OpenVPN TCP/443 (or a TCP wrapper like wstunnel around WireGuard, if you’d rather carry the complexity than run a second server).

Our own setup, documented in the firewall stack article, is the honest real-world answer: WireGuard for road-warrior duty, with a small OpenVPN TCP-443 instance kept alive as the fallback for the two situations a year where UDP dies. On OPNsense or pfSense, running both side by side is a couple of tabs in the same UI (OPNsense VPN docs cover both first-class).

Site-to-site: linking two networks

Connecting your home network to a VPS, a parent’s house, or a second site changes the calculus slightly:

WireGuard does site-to-site with a pleasingly symmetric config — each side lists the other as a peer, AllowedIPs carries the remote subnet, IP forwarding on, done (worked reference config). The catch: at least one side needs a reachable endpoint (public IP or port forward); WireGuard has no built-in relay for two-sides-behind-CGNAT (that’s the problem Tailscale exists to solve).
OpenVPN uses a server/client model for site-to-site, with the extra PKI ceremony that entails — but inherits its TCP fallback, which matters if one site sits behind a UDP-hostile ISP.

Default to WireGuard here too; reach for OpenVPN when one end’s network conditions demand TCP.

What about the criticisms of WireGuard?

Two are worth taking seriously. No cipher agility: if ChaCha20 or Curve25519 is ever weakened, every WireGuard endpoint must upgrade in lockstep — a legitimate enterprise objection that is mostly moot in a homelab where you control all five endpoints. No obfuscation and UDP-only: covered above; that’s precisely OpenVPN’s remaining lane. The security fundamentals, meanwhile, are unusually strong — WireGuard’s protocol carries multiple published formal verifications (symbolic and computational proofs plus formally verified crypto implementations), a level of analysis very few network protocols get. OpenVPN counters with something different but real: twenty years of production hardening and independent audit history.

Bottom line

Run WireGuard. It’s in the kernel, it’s a dozen lines of config, it roams silently, it’s formally verified, and it moves at wire speed on a $60 router — while you’ll hit your WAN cap long before you hit the protocol’s. Keep OpenVPN in your toolkit for the one thing it still does better than anything: escaping UDP-hostile networks over TCP 443, either as a standing fallback server (our setup) or spun up when a work trip demands it. And if what you actually want is WireGuard without thinking about keys and endpoints, that’s Tailscale’s job — a different trade, covered in a different comparison.

CPU Mining in 2026: Is It Worth It, and Which Coins?

LK Wood IV — Wed, 01 Jul 2026 00:00:00 -0500

If you have a decent desktop or a homelab box sitting idle, “can I just mine some crypto on it” is a fair question. The honest answer in 2026 is: yes, on exactly one coin worth taking seriously, for a few dimes to a couple of dollars a day, and only if your electricity is cheap. This guide is the math and the method, from the hardware side, with none of the “passive income” fantasy.

The bottom line, up front

The coin is Monero (XMR). Its RandomX algorithm is the one major mining algorithm deliberately designed to run best on ordinary CPUs. Almost everything else worth mining now needs ASICs or GPUs.
The money is small. A high-end Ryzen earns roughly $0.60–$0.80/day in XMR at a ~$200 price, before power. Net profit is measured in cents unless your electricity is very cheap.
The electricity rate decides everything. Below ~$0.08/kWh it is worth running; above ~$0.17/kWh you are paying to mine.
Never buy hardware to do this. The payback on a bought rig runs past five years. Mine on a machine you already own and would keep anyway.
The real risk is malware, not money. Mining software is one of the most abused categories on the internet. Getting the download wrong is how people lose far more than they ever mine.

If that is enough for you, great — that restraint is the whole point. If you want to actually do it well, here is the rest.

What CPU mining is (and why it still exists)

Most crypto mining abandoned CPUs over a decade ago. Bitcoin moved to purpose-built ASICs, and GPU mining dominated everything else until Ethereum — the coin that made graphics cards worth buying by the pallet — switched to proof-of-stake and stopped being mined at all. That should have been the end of the CPU miner.

It was not, because of one deliberate design choice. Monero uses an algorithm called RandomX, built specifically to be ASIC-resistant and CPU-friendly. It works by generating random program code and forcing miners through large, unpredictable memory-access patterns — exactly the workload a general-purpose CPU with a big cache is built for, and exactly what a fixed-function ASIC circuit is bad at. Per reputable 2026 mining coverage, no dedicated Monero ASIC meaningfully beats a well-tuned CPU, and GPUs generally lose to CPUs on a hash-per-watt basis for RandomX.

That single design decision is why CPU mining is a real, if niche, thing in 2026 — and why the chips that win are the same big-cache processors that win at gaming.

Is CPU mining profitable? The actual math

Here is the whole calculation. There is no magic in it, which is the point.

Daily profit = (your XMR per day × XMR price) − (watts ÷ 1000 × 24 × your $/kWh)

Work a real example — a Ryzen 9 7950X, one of the strongest home mining CPUs, tuned to about 27 KH/s, which earns roughly 0.0035 XMR/day. At an illustrative $200 XMR price that is about $0.70/day of revenue, and the chip draws about 170W while doing it (≈ 4.08 kWh/day):

Your electricity rate	Daily power cost	Daily net profit
$0.05 / kWh	$0.20	$0.50
$0.10 / kWh	$0.41	$0.29
$0.15 / kWh	$0.61	$0.09
$0.17 / kWh	$0.69	$0.01 (break-even)
$0.20 / kWh	$0.82	−$0.12 (loss)

Two things fall out of that table. First, the electricity rate is the entire game — the same machine is a modest earner or a money-loser depending only on what you pay per kilowatt-hour. The break-even here is about $0.17/kWh; the U.S. residential average is near that line, which is why “it depends where you live” is the real answer.

Second, buying hardware to mine is a bad trade. At $0.29/day net, a $600 machine takes over 2,000 days — more than five years — to pay for itself, and that is before the XMR price or network difficulty moves against you. Mining only makes sense on a capable CPU you already own and would keep running anyway. On this site we are big fans of turning an old gaming PC into a homelab server; letting spare cycles on that box mine a little XMR is a reasonable use of hardware you already paid for. Buying a box for it is not.

These numbers are illustrative and move constantly. XMR price and network difficulty change daily, so plug your own CPU, wattage, and power rate into a live Monero mining calculator (CoinWarz and MoneroOcean both publish one) before you commit. Treat any single day’s figure as a snapshot, not a promise.

Which CPUs actually mine well

RandomX rewards three things: cores, L3 cache, and memory bandwidth. That is an unusual profile — it means the chips built for high-end gaming and workstation loads are also the best miners, and that cache can matter as much as core count.

Enthusiast (≈25–31 KH/s): AMD Ryzen 9 7950X / 7950X3D / 9950X. The top of the home range.
Mid-range (≈10–15 KH/s): six-to-eight-core Ryzen and recent Intel Core chips — this is where most people’s existing desktop lands.
Budget / SBC (≈1–5 KH/s): older CPUs and Raspberry-Pi-class boards. Real, but the earnings are rounding error.

Because RandomX leans on cache and RAM, fast dual-channel memory genuinely helps — this is one of the few consumer workloads where your DDR5 kit choice shows up in the result — and AMD’s stacked-cache X3D chips punch above their core count. The same Ryzen 7 7800X3D that tops gaming charts for its cache is, for the same reason, an efficient little RandomX miner. If you want exact per-model numbers, the XMRig benchmark page and the community Monero Benchmarks site list tuned hashrates by CPU.

How to mine Monero, safely

Four pieces, in order. Do them in this order and you avoid every common beginner mistake.

A Monero wallet. Get an address to be paid into first. The official GUI/CLI wallet from getmonero.org is the reference; a reputable hardware or mobile wallet also works. You only need the receiving address to start.
A pool (or P2Pool). Solo mining a single CPU will realistically never find a block, so you join a pool and earn a steady share. SupportXMR and MoneroOcean are the common centralized pools; P2Pool is the decentralized option that keeps mining trustless and is the community’s preferred choice for network health. You point your miner at the pool and paste your wallet address.
The miner: XMRig. This is the standard RandomX miner. Download it only from the official XMRig GitHub releases page, and read the safety section below before you run anything.
Tune and monitor. Enable large/huge pages and set thread count for your chip (XMRig’s docs and its --randomx guidance cover this), then watch temperatures and the pool dashboard for your accepted shares. A CPU pinned at 100% for days runs hot — make sure cooling and your power supply are actually up to a sustained 24/7 load, which is a different thing from a gaming spike.

The part that actually matters: don’t get owned

This is where CPU mining hurts people, and it has nothing to do with profit.

Mining software is a top malware category. XMRig is legitimate and open-source, but it is also the miner attackers bundle into cracked games, “free” tools, and drive-by installs to quietly mine on other people’s machines. That reputation is earned.
Only use official sources. Download XMRig from its official GitHub releases and verify the published checksum. Never run a build from a random forum post, a YouTube description, or anything advertising “double hashrate,” “AV-bypass,” or “no-fee unlocked” — those are the exact lures used to ship wallet-stealers.
Expect an antivirus flag on the real binary. Because the genuine miner is so widely abused, Windows Defender and most AV tools flag even the legitimate XMRig as riskware or a “coin miner.” That is expected. Whitelist it only after you have verified you downloaded the real thing yourself — do not blindly disable protection because a “guide” told you to.
Watch the thermals and the bill. Sustained all-core load is a real stress test. Confirm your cooling holds and that mining a few dimes a day is not quietly adding dollars to your power bill.

The honest verdict: who should, and who shouldn’t

Do it if: you already own a capable CPU, your electricity is cheap (roughly $0.10/kWh or less), and you see it as slowly accumulating a bit of a genuinely private coin and supporting a network you like — not as income. Running it on a homelab box you keep on anyway, especially in winter when the heat is not wasted, is the sweet spot.

Skip it if: you would need to buy hardware, your power is expensive, or you are expecting meaningful money. The five-year payback and cents-per-day margins are real, and no amount of tuning changes the arithmetic. There is no shame in concluding the honest answer is “not worth it for me” — for a lot of people it is, and knowing that before you install anything is the win.

Either way, mine the math first. That is the one step that never depends on the price.

OPNsense vs pfSense (2026): Which Firewall Should You Actually Run?

LK Wood IV — Wed, 01 Jul 2026 00:00:00 -0500

If you are standing up a real firewall for a home network or a homelab in 2026, the choice almost always comes down to two FreeBSD-based, open-source platforms: OPNsense and pfSense. They look similar on a feature checklist, they share a common ancestor, and both will happily route, filter, VPN, and inspect traffic for a small network. The interesting differences are not on the spec sheet - they are in licensing direction, interface philosophy, update cadence, and the plugin you happen to depend on.

This is the focused two-way version of that decision. If you are trying to pick the hardware to run either of these on - Netgate boxes, Protectli, MikroTik, or UniFi - that is a different question, and we cover it with real throughput numbers in the homelab firewall and router stack comparison.

The 20-second answer

New build, commodity hardware, want a modern UI and fast updates: OPNsense. It is the better default for most people starting fresh in 2026.
You already run pfSense and it works, or you depend on pfBlockerNG / a pfSense-specific package: stay on pfSense CE. It is stable and there is no urgency to move.
You want a paid, vendor-backed appliance with US support and legendary uptime: pfSense Plus on Netgate hardware.

Both are genuinely good. Nobody picking either one is making a mistake. What follows is where they actually diverge.

Common roots, a decade apart

OPNsense began as a fork of pfSense and the older m0n0wall project in 2014, with its first official release in January 2015 (OPNsense project history). That shared lineage is why the two feel familiar - the same FreeBSD packet-filtering core (pf), the same broad feature set, similar concepts for rules, NAT, and VPN.

But a decade of separate development has pulled them apart. OPNsense is maintained by Deciso, a Netherlands-based company, and follows a calendar-versioned release train - the current 2026 series is 26.1 (“Witty Woodpecker”), with two major releases a year (January and July) and non-breaking updates roughly every two weeks (OPNsense releases). pfSense is developed by Netgate in the US and ships as two editions: pfSense CE (Community Edition, free and open source, currently on the 2.8.x line built on FreeBSD 14 - pfSense download) and pfSense Plus, the commercial edition that runs on Netgate appliances or registered installations.

Licensing: the quiet reason a lot of people moved

This is the single biggest non-technical driver of the 2026 conversation, and it is worth being clear-eyed about.

OPNsense is fully open source under a 2-clause BSD license, with no paid tier gating firewall features. pfSense CE is also open source and free - but Netgate’s development attention and newest features flow to pfSense Plus, the paid edition, and CE has at times lagged behind it. Community discussion since roughly 2020 has centered on unease about that CE-versus-Plus direction and Netgate’s stewardship, and that unease is a real part of why some long-time pfSense users switched. You will find this sentiment stated plainly across r/homelab and r/selfhosted threads on the topic.

None of that makes pfSense CE a bad firewall - it is still free, capable, and widely run. But if “will the free edition keep getting first-class attention” is a question you care about, OPNsense’s answer is simpler.

Interface and daily use

The most commonly cited difference, and the one you feel every time something breaks at 2 a.m., is the web UI.

OPNsense uses a collapsible left-side menu with a built-in search bar. Menus are grouped logically, inline help is current, and finding a setting you rarely touch is fast. It also ships built-in two-factor authentication for the web UI and a built-in REST API, which is a real advantage if you automate anything.
pfSense uses the traditional top-drop menu layout. It is dense, it is what a lot of people learned on, and once you know where things live it is perfectly efficient - but there is no built-in search, and the learning curve is steeper for a newcomer.

If you are new to firewalls, OPNsense’s interface is the friendlier place to start. If you have muscle memory for pfSense’s menus, that familiarity is worth something real.

Plugins and packages

pfSense’s package library is larger and older, and its headline package is pfBlockerNG for DNS and IP blocklisting - a genuinely excellent tool that many pfSense users consider load-bearing. Mature packages like HAProxy, ntopng, and ACME are well established.

OPNsense takes a more curated approach: a tighter, quality-controlled plugin set, with several things built in that pfSense treats as add-ons (reporting/NetFlow insight, for example). It does not have pfBlockerNG, but it covers the same ground with built-in Unbound DNS blocklists, native alias/GeoIP features, and optional plugins like Zenarmor for next-gen filtering.

The practical read: if a specific pfSense package - especially pfBlockerNG - is central to your setup, that is a legitimate reason to stay on pfSense. If you want a clean, curated set that mostly works out of the box, OPNsense’s model is less likely to leave you running an abandoned package.

Security cadence - with an honest caveat

OPNsense’s frequent, roughly biweekly release train means new features and fixes generally land faster, and the project publishes security updates on a fast cycle. That cadence is a real advantage.

The honest caveat: a faster release cadence is not automatically a faster patch-for-a-specific-CVE cadence. There have been documented community discussions arguing pfSense has at times shipped certain upstream security fixes sooner, despite its slower release rhythm. Both projects take security seriously; neither is negligent. Do not pick a firewall on a blanket “one patches faster” claim - the reality is more nuanced than either camp’s marketing.

Performance: effectively a tie where it counts

Raw throughput is a function of your CPU and NIC, not which firewall you install. Both OPNsense and pfSense now use kernel-mode WireGuard, which closed the old user-space VPN ceiling.

On our own bench, at a 1 Gbps WAN:

Firewall / hardware	NAT throughput	WireGuard (1 tunnel)	Idle power
pfSense Plus, Netgate 4100	~938 Mbps	~941 Mbps	14 W
OPNsense, Protectli VP2420 (i3-N305)	~941 Mbps	~938 Mbps	11 W
OPNsense, N100 mini-PC	~939 Mbps	~692 Mbps	7 W

They are, for practical purposes, tied at line rate. The one place a gap opens is Suricata IDS on underpowered hardware: a single-threaded N100 starts to bottleneck with IDS enabled, while a multi-core box (i3-N305 class or better) keeps up. That is a CPU story, not an OPNsense-versus-pfSense story. Full methodology and the four-way hardware bench are in the homelab firewall and router stack piece.

How to actually decide

Skip the feature-checklist paralysis. Answer these instead:

Do you already run pfSense and is it working? Stay. There is no prize for switching.
Do you depend on pfBlockerNG or another pfSense-specific package? Stay on pfSense.
Starting fresh, on your own commodity hardware, want the nicer UI and faster updates? OPNsense.
Want a paid appliance with vendor support and set-and-forget uptime? pfSense Plus on a Netgate box.
Uneasy about the pfSense CE/Plus licensing direction? OPNsense removes that question entirely.

Once you have picked, the next step is hardware and setup. For a clean, quiet, low-power box to run either one, see the best mini PCs for a homelab, and for a step-by-step OPNsense install on a mini PC, our OPNsense mini-PC setup guide walks the whole thing. If you are also planning VLANs behind the firewall, start with the homelab VLAN guide.

Bottom line

In 2026, OPNsense is the better default for a new homelab firewall - modern UI, fast updates, commodity-hardware friendly, and free of the licensing question hanging over pfSense CE. pfSense remains an excellent choice if you already run it, value its maturity and stability, or depend on a pfSense-specific package. Both are FreeBSD-grade, both will serve a home network for years, and the “wrong” choice here is still a very good firewall.

Podman vs Docker (2026): Which Container Engine Should You Actually Run?

LK Wood IV — Wed, 01 Jul 2026 00:00:00 -0500

If you are running containers on a home server or a developer laptop in 2026, the choice has quietly narrowed to two engines: Docker, the incumbent that made containers mainstream, and Podman, Red Hat’s daemonless, rootless-by-default challenger. They run the same images, read the same Dockerfiles, and share almost the same command line - so on a feature checklist they look nearly identical. The differences that matter are architectural: whether there is a background daemon, whether containers run as root, and how much ecosystem friction you are willing to trade for a smaller attack surface.

This is the focused two-way version of that decision. If you are just trying to get containers running for the first time, our install Docker on Ubuntu guide and Docker Compose starter stack get you moving fast - everything below applies whichever engine you land on. And if you are also weighing the host layer itself, Proxmox vs Docker explains why that is a layering question, not a rivalry.

The 20-second answer

New to containers, want the smoothest on-ramp and the biggest pile of tutorials: Docker. It is still the better place to learn.
Security-conscious, run on Linux, or manage containers as systemd services: Podman. Rootless-by-default and Quadlet make it the cleaner production-style choice.
You are a larger company worried about Docker Desktop licensing: Podman removes that question entirely - it is fully open source with no company-size restriction.
You just want your existing images and Compose files to work: either one. They share the OCI image format and Podman speaks the Docker API.

Both are excellent. Nobody picking either is making a mistake. Here is where they actually diverge.

The daemon: the one architectural difference everything traces back to

Docker uses a client-server model. The docker command you type is a thin client that talks to dockerd, a background daemon that, by default, runs as root and owns every container on the host. That daemon is convenient - it manages lifecycle, networking, and the API in one place - but it is also a single, always-running, privileged process. If a container escapes its boundary, the daemon it targets is running as root (Docker rootless docs).

Podman is daemonless. There is no background service; podman run forks the container directly as a child of your shell, and when the container exits, nothing lingers. Combined with rootless-by-default operation, a container escape lands in your unprivileged user account, not root (Podman documentation). Docker can run rootless too - it has been an opt-in mode since Docker 19.03 - but it is not the default and takes deliberate setup. Podman’s default is the safer posture.

That is the whole story in one paragraph. Nearly every other Podman-vs-Docker talking point - security, systemd integration, resource usage at idle - flows from “there is no root daemon.”

Compatibility: Podman speaks Docker

The reason a switch is even feasible is that Podman went out of its way to be Docker-compatible:

Same images. Both use the OCI image format, so any image from Docker Hub, GHCR, or your own registry runs unchanged under either engine.
Same CLI. Podman’s commands mirror Docker’s closely enough that many people literally run alias docker=podman and never think about it again.
Same Dockerfiles. podman build reads your existing Dockerfile and produces an identical image.
Docker API socket. Podman exposes a Docker-compatible REST socket, so tools that expect the Docker API - including the official Docker Compose v2 CLI - can point at Podman instead (Podman Desktop: managing Docker compatibility).

Where compatibility frays: some Compose files that lean on Docker-specific extensions need small edits, podman-compose (the native tool) occasionally lags the official Compose spec, and any tooling hard-wired to assume a running Docker daemon needs the compatibility socket enabled. For a typical homelab Compose stack, migration is usually “enable the socket, re-run docker compose up, fix one or two warnings.”

Pods, Kubernetes, and systemd: where Podman pulls ahead

Podman was built with Kubernetes in mind, and it shows in two features Docker has no direct answer for:

Pods. Podman can group containers into a pod - the same shared-namespace concept Kubernetes uses - and podman kube generate will emit Kubernetes-compatible YAML from your running containers or pods, easing the jump from a single host to a cluster (Red Hat: Podman and Kubernetes YAML).
Quadlet + systemd. On a Linux host, Podman’s Quadlet lets you declare a container as a native systemd unit, so it starts on boot, restarts on failure, and shows up in systemctl like any other service. This is now the recommended approach - the older podman generate systemd is deprecated (Red Hat: Quadlet). For running self-hosted apps as first-class services, this is genuinely nicer than Docker’s restart policies.

Docker’s counterweight is Docker Swarm and, more importantly, the enormous ecosystem of tooling, tutorials, and Compose files that assume Docker. If your endgame is Kubernetes, Podman’s pod model is a smoother stepping stone; if your endgame is “a Compose file that a thousand blog posts already documented,” Docker is the path of least resistance.

Licensing: the business reason, not the technical one

This is the single biggest non-technical driver of the 2026 conversation, so it is worth stating precisely.

Podman is fully open source (Apache 2.0), with no company-size restriction. Free, forever, for anyone.

Docker Desktop is free for personal use, education, non-commercial open source, and small businesses - defined as fewer than 250 employees AND less than $10 million in annual revenue. Above that threshold, Docker Desktop requires a paid subscription: roughly Pro $9, Team $15, and Business $24 per user per month (billed annually) as of 2026 (Docker Desktop license, Docker pricing). Note this applies to Docker Desktop, the GUI/VM bundle - Docker Engine (the CLI on Linux) remains free.

For a solo homelabber, the licensing point rarely bites - you are under the threshold and often on Linux without Docker Desktop anyway. But for a larger organization it is a real line item, and it is a big part of why some teams evaluated Podman in the first place.

Performance: close enough that it is rarely the deciding factor

Independent benchmarks vary and depend heavily on workload and configuration, so be skeptical of any blanket “X is faster” claim. The consistent themes across published 2025-2026 comparisons:

Idle/memory: Podman tends to use less memory at rest, because there is no always-running daemon - some tests put the difference around 15-20% (Xurrent comparison).
Per-operation speed: Docker is often slightly faster for individual operations like container startup and image pulls - some tests cite 10-15% (Uptrace comparison).

At homelab scale - a handful of containers on a mini PC - you will not feel either difference. Performance is dominated by your CPU, disk, and the apps themselves, not the container engine. If you are sizing a box, our Docker RAM planner estimates memory for a stack regardless of which engine runs it. Treat performance as a tie and decide on architecture and ecosystem instead.

The honest disadvantages of Podman

To keep this from reading like a Podman ad, the real friction, straight from practitioners on r/podman and r/selfhosted:

Documentation and community answers are thinner. When something breaks at 1 a.m., there are far more Docker Stack Overflow threads to search. This is the most common complaint.
Rootless has edge cases. Privileged ports (below 1024), some container-to-container networking, and a few volume-permission scenarios need extra steps that rootful Docker handles transparently.
Some tooling assumes Docker. Anything that talks directly to the Docker daemon needs the compatibility socket, and a minority of tools simply do not support Podman yet.

None are dealbreakers, but together they are exactly why Docker is still the easier first container engine to learn - and why “just use Docker” remains reasonable advice for a beginner.

How to actually decide

Skip the feature-checklist paralysis and answer these:

Are you brand new to containers? Start with Docker. Learn the concepts where the tutorials are thickest, then re-evaluate.
Do you care about rootless-by-default security, or run containers as systemd services on Linux? Podman. Quadlet alone is worth it for a service-style homelab.
Are you a company over 250 employees / $10M revenue using Docker Desktop? Podman removes the licensing question.
Is your endgame Kubernetes? Podman’s pods and kube generate are a smoother on-ramp.
Do you just need your existing images and Compose files to keep working? Either - they share the OCI format, and Podman speaks the Docker API.

Bottom line

In 2026, Docker remains the best place to start and the safest default for compatibility - the largest ecosystem, the smoothest onboarding, and the tooling everything assumes. Podman is the better choice when architecture matters: daemonless, rootless by default, excellent systemd integration, a clean path toward Kubernetes, and no licensing asterisk. They run the same images and share almost the same command line, so this is a low-stakes decision - and plenty of people run both. Pick Docker to learn and to match the world’s tutorials; reach for Podman when you want a smaller attack surface and a more Linux-native way to run your containers as real services. Once you have picked, the self-hosting essentials guide covers what to actually run on top.

Tailscale vs WireGuard (2026): Which One Should You Actually Run?

LK Wood IV — Wed, 01 Jul 2026 00:00:00 -0500

If you want to reach your homelab from anywhere in 2026, the two names you keep hearing are Tailscale and WireGuard - and the way they are usually pitched (“which VPN is better?”) frames the choice wrong. They are not really rivals. Tailscale is built on WireGuard. The honest question is not which protocol wins; it is whether you want raw WireGuard or WireGuard wrapped in a coordination layer that handles the tedious parts.

This is the focused two-way version of that decision, aimed at homelabbers. If you want the step-by-step builds instead, we have full guides for both: Tailscale remote access for the homelab and a self-hosted WireGuard VPN on Proxmox. Still deciding between the two bare protocols before adding a coordination layer? Start with WireGuard vs OpenVPN for the homelab.

The 20-second answer

Behind CGNAT, or you just want it to work in 15 minutes across many roaming devices: Tailscale. It traverses NAT with no port forwarding and manages keys for you. This is the right default for most people in 2026.
You can port-forward (or have a static-ish IP/DDNS), run a couple of devices, and want zero third-party dependency: self-hosted WireGuard. It is minimal, in-kernel, fast, and answers to nobody but you.
You want Tailscale’s convenience without the SaaS: run Headscale (self-hosted Tailscale control plane) or plain WireGuard.

Neither choice is a mistake. What follows is where they actually diverge.

They are not actually competitors

WireGuard is a VPN protocol - a small, fast, modern tunnel that landed in the mainline Linux kernel in version 5.6 (2020) and is now the standard for point-to-point encrypted links. It does exactly one thing: move encrypted packets between peers that already know each other’s public keys and network addresses. It does not distribute keys, discover peers, punch through NAT, or provide names. Those are your job.

Tailscale is a coordination layer that uses WireGuard underneath. It keeps the fast WireGuard data plane and adds everything WireGuard deliberately leaves out:

Automatic key distribution - devices exchange public keys through Tailscale’s control server, so you never hand-copy a key again.
NAT traversal - it establishes direct peer-to-peer links through firewalls and NAT, and falls back to an encrypted relay when a direct path is impossible.
Stable addressing + MagicDNS - every device gets a fixed 100.x.x.x address and a friendly name (nas.your-tailnet.ts.net) that works the same on home Wi-Fi or LTE.
Access control - a policy file decides which devices can reach which, instead of hand-written iptables.

So “Tailscale vs WireGuard” really means: do you want to run the coordination yourself, or let a managed service do it?

The one question that usually decides it: can you port-forward?

This is the single most important factor, and it is the reason the r/homelab threads on this topic keep landing on Tailscale.

A self-hosted WireGuard server has to be reachable from the internet. That means an inbound UDP port forwarded on your router to a public-facing IP (a static IP, or a dynamic-DNS hostname that tracks your changing residential IP). If you can do that, WireGuard is wonderful.

If you cannot - and increasingly you cannot - Tailscale wins by default. Carrier-grade NAT (CGNAT) is now common on Starlink, 5G home internet, and plenty of fiber and apartment ISPs. Behind CGNAT you share a public IP with other customers and there is no port to forward. Self-hosted WireGuard simply cannot accept inbound connections in that situation without renting a VPS with a public IP to act as a relay - at which point you have rebuilt a piece of Tailscale by hand.

Tailscale is engineered precisely for this world: it brokers a direct connection through the NAT when it can (the majority of the time), and relays encrypted traffic through its DERP servers when it cannot. You open zero ports. For anyone on CGNAT, that is close to a decision-ender.

Setup and day-to-day

Tailscale is genuinely a 15-minute experience: install the client, log in with an existing identity provider, and the device joins your tailnet. Adding the tenth device is as easy as the first. MagicDNS means you stop memorizing IPs. Subnet routing (to reach non-Tailscale LAN devices) and exit nodes (to route all traffic through one node) are a checkbox and a command.

WireGuard takes longer up front and scales by hand. You generate a key pair per peer, write each peer into the server config and the server into each client config, and manage the address plan yourself. For two or three devices this is a pleasant afternoon. For twenty roaming devices with rotating keys it becomes real operational work, which is exactly the gap tools like Tailscale, Headscale, NetBird, and ZeroTier exist to fill.

One honest Tailscale-side wrinkle from the community: the mobile client can be a battery draw, and on Linux the daemon occasionally tangles with the local networking stack. These are minor and usually fixable, but they are real, and pure WireGuard - being a thin kernel module - has none of that surface.

Performance: effectively a tie where it matters

When Tailscale establishes a direct peer-to-peer connection - which it does the large majority of the time - you are running WireGuard, so throughput and latency are essentially the same as raw WireGuard.

Two honest caveats:

Kernel vs userspace. Raw WireGuard on Linux runs as a kernel module and is extremely efficient (multi-gigabit with low CPU). Tailscale ships a userspace WireGuard engine, which is modestly slower in raw throughput on very fast links. At the WAN speeds almost every homelab actually runs (well under 1 Gbps to the internet), you will not notice.
Relay fallback. If Tailscale cannot punch a direct path and falls back to a DERP relay, expect added latency and reduced throughput on that link until a direct route is found. Raw WireGuard, being direct by definition, never has this failure mode - but it also cannot connect at all in the scenarios where Tailscale is relaying.

Bottom line: for SSH, web UIs, file transfers, and media streaming - the actual homelab workload - performance is not the deciding factor.

Control, privacy, and independence

This is where self-hosted WireGuard pulls ahead for a specific kind of user.

With WireGuard, no third party exists. Your keys never leave your machines; there is no account, no coordination server, no company that could go down, change pricing, or get breached. That independence is the entire point for many homelabbers - the recurring “I want to be completely independent” motivation you see stated plainly in r/homelab.

With Tailscale, your traffic is still end-to-end encrypted and flows peer-to-peer (Tailscale cannot read it), but a proprietary coordination server brokers your keys and holds device metadata and your access policy. You are trusting that control plane and your account security. If Tailscale’s coordination service is unavailable, existing connections generally keep working but establishing new ones can be affected.

The middle path is Headscale: an open-source, self-hostable reimplementation of Tailscale’s control server. You keep the excellent Tailscale clients and the mesh/MagicDNS experience while running the brain yourself - no external dependency, at the cost of operating that server. For identity-aware access on top of any of these, a self-hosted SSO layer like Authentik is a common companion.

Side-by-side

	WireGuard (self-hosted)	Tailscale
What it is	VPN protocol (kernel module)	Coordination layer over WireGuard
Setup time	30-60 min	~15 min
Works behind CGNAT / no port-forward	No (needs a VPS relay)	Yes, automatic
Key management	Manual, per peer	Automatic
Naming	Manual / your own DNS	MagicDNS built in
Access control	Hand-written iptables	Policy file
Third-party dependency	None	Tailscale control plane (or self-host Headscale)
Peak throughput on fast links	Highest (kernel)	Very high; slightly lower (userspace)
Users on free tier	N/A (no accounts)	6 users, generous device allowance
Best for	Independence, simple static setups	CGNAT, many roaming devices, speed of setup

So which should you run?

Pick Tailscale if you are behind CGNAT, you have a lot of roaming devices, you value time-to-working over ideology, or you are new to VPNs. For most homelabbers in 2026, this is the correct default.
Pick self-hosted WireGuard if you can accept an inbound connection (port forward or static-ish IP/DDNS), you run a small, mostly-static set of devices, and you want zero external dependency - your keys, your server, nobody else in the loop.
Run both. A very common homelab pattern is self-hosted WireGuard on the router for a fast, dependency-free link from your main devices, plus Tailscale on a NAS or Pi as a subnet router for zero-config access from anywhere. Convenience when you want it, independence when you need it - there is no rule that says you must choose only one.

Whichever you land on, the underlying encryption is the same WireGuard either way. You are really choosing who runs the coordination - a service, or you.

Data Usage Calculator: Estimate Your Monthly Internet GB

LK Wood IV — Tue, 30 Jun 2026 00:00:00 -0500

This tool estimates your monthly internet data usage in gigabytes from how you actually use the connection - streaming, YouTube, music, video calls, gaming, general browsing, and downloads - then tells you whether you’re likely to bump into a data cap. Enter your typical hours per day for each activity and your monthly download volume, set how many people share the connection, and you get a monthly GB total, a daily average, and how that compares to the common 1.2 TB US cap.

The honest framing: streaming dominates, and resolution is the dial that matters most. SD video is about 1 GB/hour, HD about 3, and 4K about 7 - so the difference between a 1080p and a 4K habit can be hundreds of gigabytes a month per person (Netflix’s published data-usage figures). Gameplay itself is light (~0.1 GB/hour); it’s the 50-150 GB game downloads that move the needle, which is why downloads are a separate line. Every rate here is a provider-published approximation - your real usage varies with app settings, codecs, and content - so treat the result as a well-grounded estimate, not a billing meter.

To turn a download size into a time estimate at your connection speed, use the Transfer Time Calculator; if you’re sizing a home network to carry all this, see the 10GbE home networking guide.

Disclosure

Tue, 30 Jun 2026 00:00:00 -0500

Retailer links and sourcing

The retailer links in articles (Newegg, B&H, and others) are plain reference links to help a reader find a part. TechFuel HQ earns no commission on them — they are editorial references, nothing more. No retailer relationship influences which products get recommended. If a product is not worth recommending, it does not get recommended.

Affiliate links (Amazon Associates)

TechFuel HQ participates in the Amazon Associates Program and may earn a commission from qualifying purchases at no extra cost to the reader. As an Amazon Associate, TechFuel HQ earns from qualifying purchases. Some Amazon links in articles are affiliate links; links to other retailers (Newegg, B&H, eBay, manufacturer stores, and others) are plain reference links that earn nothing. Every article that contains an affiliate link carries a clear disclosure line near the top, so you always know when a link can earn a commission before you click it. A commission never changes which product gets recommended — if a product is not worth recommending, it does not get recommended, affiliate link or not.

Advertising

TechFuel HQ is funded by display advertising. Google AdSense (when enabled) serves ads on the site; Google and its advertising partners use cookies to serve ads based on a visitor’s prior visits to this site and other sites. Third-party vendors, including Google, use the DoubleClick DART cookie to serve ads based on those visits. You can opt out of personalized advertising at Google’s Ads Settings, and review Google’s advertising and DART cookie policy. When advertising is active, visitors in supported regions (the EEA, UK, and Switzerland) are shown a cookie consent banner for managing advertising and personalization cookies. Full detail is in the Privacy Policy.

Source standards

Vendor specs are cited with links to the vendor’s official documentation page
Benchmarks are cited with links to the original test source (publication, repository, or vendor)
News and licensing changes are cited with links to the originating announcement

If a claim cannot be cited to a real, resolvable source, it is omitted.

Real-artifact policy

Where a 2024–2025 article references a physical measurement, photo, or receipt — a Kill A Watt reading, an iperf3 result, or a parts receipt — that artifact was captured on the author’s own gear during the 2024–2025 testing period. Most of that gear was sold or retired in early 2026 (see Colophon).

Articles published from June 2026 onward source benchmarks from named third-party publications, cited inline at each claim, with one exception: hands-on observations and original first-party measurements from the gear the author still owns and uses daily. That current rig is a Ryzen 7 7800X3D / ASUS ROG STRIX B650-A / 64GB DDR5-6000 / ASUS ROG Astral RTX 5080 OC / NZXT Kraken 360 / EVGA SuperNOVA 1000 GT / Samsung 970 EVO Plus / Gigabyte AORUS FO48U — the published ASUS ROG Astral RTX 5080 OC bench dataset (captured 2026-06-08–2026-06-09) is the most data-heavy example. Where a hardware claim cannot be backed by either a real third-party citation or first-hand use of gear the author owns, it is omitted; figures that are vendor-spec or third-party are labeled as such, separately from anything measured first-hand.

Updates

Articles are revised when the underlying facts change (a new release, a price shift, a vendor policy change). The “Last updated” date in the article reflects the most recent revision.

Errors and corrections

Spotted an error or want to challenge a recommendation? Email hello@techfuelhq.com with the article URL and the specific section. Material corrections are made in-place with an updated “Last updated” date.

Contact

Publisher: Lowell K. Wood IV Email: hello@techfuelhq.com Location: St. Louis County, Missouri, United States

How to Install Docker on Ubuntu (2026): Step-by-Step

LK Wood IV — Tue, 30 Jun 2026 00:00:00 -0500

By LK Wood IV · Published 2026-06-30 · ~8 min read · St. Louis County, MO

Docker is the foundation of almost every self-hosted stack — Jellyfin, Nextcloud, Home Assistant, Pi-hole, the lot. (Weighing it against the daemonless, rootless alternative first? See our Podman vs Docker comparison.) This guide installs Docker Engine on Ubuntu the official way: from Docker’s own apt repository, so you get the current release, the Buildx plugin, and Compose v2 together, with updates straight from Docker. It works on Ubuntu 24.04 LTS, 22.04 LTS, and current interim releases, and the repository line auto-detects your version so you never edit it by hand.

Skip Ubuntu’s built-in docker.io package and the Snap version — both lag upstream and ship without the bundled Compose v2 plugin, which is the usual reason docker compose “is not a docker command.” The steps below come straight from Docker’s official Ubuntu install documentation; I have reproduced the current commands verbatim and added the post-install and error-fixing steps that the quick-start glosses over.

Prerequisites

A 64-bit Ubuntu 24.04, 22.04, or current release (desktop or server)
A user with sudo privileges
Internet access to reach download.docker.com

Step 1: Remove conflicting packages

Older or distro-packaged Docker bits collide with the official packages. Clear them first:

sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-compose-v2 docker-doc podman-docker containerd runc | cut -f1)

It is fine if apt reports some of these were not installed. Your images and volumes in /var/lib/docker are left untouched.

Step 2: Add Docker’s official apt repository

First add Docker’s GPG key so apt trusts the packages:

# Add Docker's official GPG key:
sudo apt update
sudo apt install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

Then add the repository itself. This block writes the modern deb822-format source file and fills in your Ubuntu codename and CPU architecture automatically:

# Add the repository to Apt sources:
sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF

sudo apt update

Step 3: Install Docker Engine

sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

That single command installs the Engine, the CLI, containerd, Buildx, and Compose v2 — everything a homelab needs.

Step 4: Verify the install

sudo docker run hello-world

If you see “Hello from Docker!”, the Engine is running. Confirm Compose v2 too:

docker compose version

A v2.x number means docker compose up -d will work for your stacks.

Step 5: Run Docker as a non-root user

By default docker needs sudo. Add your user to the docker group so you can drop it:

sudo usermod -aG docker $USER

Then log out and back in (or run newgrp docker in the current shell) so the new group membership takes effect. After that, docker run hello-world works without sudo.

Security note: the docker group grants root-equivalent access to the host — a member can mount the host filesystem into a container. Only add users you trust as administrators.

Docker is enabled to start on boot automatically after this install (via systemd). You can confirm with systemctl is-enabled docker.

Common install errors and fixes

permission denied while trying to connect to the Docker daemon socket — your user is not in the docker group yet, or you have not logged out and back in since Step 5. Re-run the usermod line, then log out/in.
docker: 'compose' is not a docker command — you installed the old docker.io or Snap package instead of docker-ce. Remove it (Step 1) and install from the official repo (Steps 2–3), which includes the Compose plugin.
NO_PUBKEY / GPG error on apt update — the GPG key step did not complete. Re-run the four key commands in Step 2 and check the key exists with ls -l /etc/apt/keyrings/docker.asc.
Unable to locate package docker-ce — the repository was not added or apt update was not run after adding it. Re-check /etc/apt/sources.list.d/docker.sources exists and re-run sudo apt update.
Behind a proxy or on a fresh server, curl fails — install curl first (sudo apt install curl) and confirm the box can reach download.docker.com.

Where to go next

With the Engine running, the natural next step is a Compose stack. Start with the Docker Compose starter stack for a homelab, size your host RAM with the Docker homelab RAM planner, or jump straight to a real service like Jellyfin in Docker. For the bigger picture of what to self-host, see the best self-hosted apps to replace SaaS.

Commands reproduced from Docker’s official Ubuntu installation guide and verified 2026-06-30. Docker Engine, Buildx, and Compose are trademarks of Docker, Inc.; this is an independent guide.

Monitor Size Calculator: Screen Width, Height & Desk Fit

LK Wood IV — Tue, 30 Jun 2026 00:00:00 -0500

This tool turns a monitor’s diagonal size and aspect ratio into its real physical dimensions - width and height in both inches and centimeters - plus the screen area and a plain-English desk-fit verdict. Enter a diagonal and pick an aspect ratio, or tap a preset for a common screen. It is the answer to “how wide is a 34-inch ultrawide, actually?” and “will this thing fit on my desk?”

The key insight the diagonal alone hides: width, not the diagonal, decides whether a screen fits your space, and two monitors with the same diagonal can be very different shapes. A 34-inch 21:9 ultrawide is 3.5 inches wider than a 32-inch 16:9, yet it is also shorter and has slightly less total screen area - because ultrawides trade height for width. A 49-inch 32:9 is nearly four feet (120 cm) across. The calculator makes those trade-offs concrete before you buy. One knock-on effect worth knowing if you are moving to an ultrawide: the wider field of view changes how a given in-game sensitivity feels, so it is worth re-checking your cm/360 in the mouse sensitivity converter after the swap.

To turn the same numbers into pixel sharpness, use the PPI Calculator; to nail down a screen’s exact aspect ratio from its resolution, use the Aspect Ratio Calculator; and to convert a game’s field of view between a 16:9 and an ultrawide screen, see the FOV Calculator.

Aspect Ratio Calculator: Resolutions, Ultrawide & 16:9 (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This calculator works two ways. Enter a pixel resolution and it reduces to the exact aspect ratio (with the decimal and the common name). Or set a ratio - type it or tap a preset like 16:9 or 21:9 - and enter one dimension to solve the other. It is built for monitors and gaming resolutions, so the presets and names match real displays.

The detail most aspect-ratio tools skip: advertised ratios are often rounded. A “21:9” 3440x1440 monitor is exactly 43:18, and a 2560x1080 one is 64:27. Neither is truly 21:9. This tool shows the precise reduced ratio, which is the real geometry of the panel - useful when you are matching wallpapers, video, or a game’s render target to the actual screen.

To size a graphics card for the resolution you land on, see the GPU Comparison Tool and the PC Bottleneck Calculator.

Common resolutions and their real ratios

Most PC resolutions reduce to a short list. 1920x1080, 2560x1440, and 3840x2160 are all 16:9, the standard. 1920x1200 and 2560x1600 are 16:10, common on laptops and productivity panels. The ultrawides are where the marketing labels drift from the geometry: 2560x1080 is exactly 64:27, 3440x1440 is 43:18, and both wear a “21:9” sticker. Super-ultrawide 5120x1440 is 32:9. Going back, 1280x1024 is 5:4 and the classic 1024x768 is 4:3. Enter any native resolution above and the tool reduces it with the greatest common divisor, so you get the exact ratio rather than the rounded one.

Why “21:9” is a rounding

True 21:9 works out to 2.333 wide for every 1 tall. A 3440x1440 monitor divides to about 2.389, which reduces exactly to 43:18; a 2560x1080 one divides to about 2.370, which is exactly 64:27. Neither is really 21:9; the label is just cleaner to advertise. It rarely matters for buying, but it matters when you are matching a wallpaper, a video, or a game’s render target to the panel, because using the true ratio avoids the slight stretch or letterbox that a rounded “21:9” would introduce.

How aspect ratio touches gaming performance

The ratio itself does not change performance; the pixel count does. A 3440x1440 ultrawide has about 4.95 million pixels, roughly 34 percent more than 2560x1440 but well short of 4K’s 8.29 million, so its frame rates usually land between 1440p and 4K. Budget a graphics card accordingly with the GPU Comparison Tool. A wider screen also changes what you see: ultrawides widen your in-game field of view, which you can convert precisely with the FOV Calculator.

CPU Comparison Tool: Compare Any Two Gaming Processors (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This tool compares any two processors for gaming and shows which is faster, by how much. Pick two CPUs. The result is a relative gaming margin based on aggregated 1080p benchmarks, which is the standard way to rank processors against each other because it removes the graphics card as a bottleneck.

The honest framing: this is a 1080p gaming ranking, not a productivity score, and not the gap you will feel at every resolution. At 1080p and high refresh rates you may see most of the difference; at 1440p and 4K the graphics card usually becomes the limiter and the gap between two capable chips shrinks. For multi-core work like rendering or compiling, core count changes the order, so check those benchmarks separately.

Scores come from the Tom’s Hardware CPU benchmarks hierarchy (1080p gaming), current through June 2026. To see whether a given CPU actually bottlenecks a specific graphics card at your resolution, pair this with the PC Bottleneck Calculator; to compare two graphics cards, use the GPU Comparison Tool.

How to read the result

The number is a 1080p gaming margin, not a general speed score. Testing at 1080p on a fast graphics card removes the card as a limit, so the gap you see is the processor’s true gaming ceiling, which is the honest way to rank chips against each other. But it is a ceiling, not the gap you will feel at every resolution. At 1080p and high refresh rates you may see most of it; at 1440p and 4K the graphics card usually becomes the limiter and the difference between two capable chips shrinks, sometimes to nothing. Read the percentage as the maximum gaming gap, then expect less of it the higher you play.

Why X3D chips win games

If a lower-clocked, cheaper AMD chip is beating a pricier one in this ranking, the reason is almost always cache. AMD’s X3D processors stack extra L3 cache onto the die. Games constantly request small pieces of data, and a bigger cache serves more of those requests instantly instead of waiting on slower system memory. The payoff shows up most in simulation, strategy, and esports titles that live and die on memory latency. That is how a Ryzen 7 7800X3D or 9800X3D beats higher-clocked, more expensive chips in games while drawing less power, even when those same chips pull ahead in raw multi-core work.

Gaming and productivity do not rank the same

This tool ranks gaming, and gaming only. A chip that wins games can lose at rendering, compiling, or video encoding, where core and thread count matter more than the cache and latency that win games. The clean example is the X3D line again: it leads in gaming on cache, but a same-price non-X3D or Intel chip with more cores can finish a render faster. If your machine does real productivity work, treat this as the gaming half of the decision and check multi-core benchmarks for the other half before you buy.

The free frames most people leave on the table

Two builds with the same processor can differ several percent on memory alone, because gaming is sensitive to memory latency and bandwidth. The index here assumes your memory is running at its rated speed, which means the EXPO profile on AMD or XMP on Intel is switched on in the BIOS. Out of the box it often is not. Enabling it is one of the cheapest ways to close a gaming gap, and a slow-rated kit can quietly cost you frames on even a strong chip.

When a gap is small, spend the difference elsewhere. An 8 percent gaming lead at 1080p that mostly vanishes at your real resolution is rarely worth paying up for, and the money is usually better spent on a faster graphics card. The 7800X3D vs 9800X3D upgrade guide works through exactly that math, the 7800X3D review covers the value pick most gamers land on, and the PC Builder balances a whole system to a budget.

CPU Hierarchy 2026: Gaming Processor Tier List

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This is a 2026 CPU hierarchy: a tier list of 28 modern processors ranked by gaming performance, not by price or core count. Each chip carries a relative gaming score, normalized so the fastest gaming processor equals 100, and a tier label. Scores come from 1080p gaming benchmarks — testing at 1080p on a top-tier graphics card removes the GPU as a limiter, so the numbers reflect each chip’s true gaming ceiling rather than your monitor’s.

Two ideas run through this whole list, and the chart above shows both. First, gaming CPUs barely spread out. Where graphics cards run from about 25 to 100, every processor here scores 60 or better — the entire race happens in the top 40% of the scale. The slowest modern chip is still a perfectly good gaming CPU, and the gap between a mid-tier and a top-tier part is often a handful of percent that shrinks to nothing once you leave 1080p behind. Second, the very top is a clean sweep of cache. The seven fastest gaming chips of 2026 are all AMD 3D V-Cache parts, and it is worth understanding why before you read a single tier.

Why the top is all cache

Games are latency-bound in a way that most productivity work is not. They fire off enormous numbers of small, unpredictable memory requests, and every one that misses the cache means a long wait on system RAM. AMD’s 3D V-Cache stacks a slab of extra L3 cache directly on top of the chip — 96MB on an X3D part versus roughly a third of that on a normal one — so far more of those requests are answered instantly. The payoff is largest in exactly the games that hammer the CPU: simulation, strategy, MMOs, and esports at high refresh.

The surprising part is what it does to the usual “more cores, more money, more performance” instinct. For gaming, it inverts it. A cache-heavy chip with fewer cores routinely beats a higher-clocked, higher-core, more-expensive processor — while drawing less power.

The 3D V-Cache effect

In games, cache beats cores. Relative 1080p gaming index (55 = short bar, 100 = full).

Ryzen 5 7600X3D
6 cores · cache

80.6

Core i9-14900K
24 cores · no cache

78.2

Ryzen 7 7800X3D
8 cores · cache

85.6

Ryzen 9 9950X
16 cores · no cache

76.9

A 6-core cache chip out-games Intel's 24-core flagship. An 8-core X3D beats a 16-core Ryzen 9. For gaming, stop counting cores.

techfuelhq.com · 1080p gaming index, from the Tom's Hardware CPU hierarchy

The catch — and it is a real one — is that this is a gaming ranking. Those extra cores on a 9950X or a 14900K are not wasted; they win decisively in rendering, compiling, streaming, and anything that scales with threads. If you do serious multi-core work as well as game, read the Strong tier below with that in mind. But if the machine exists to play games, the list starts and ends with cache.

The 2026 CPU gaming hierarchy

#	Processor	Gaming index	Tier
1	Ryzen 7 9850X3D	100.0	Elite
2	Ryzen 7 9800X3D	97.0	Elite
3	Ryzen 9 9950X3D	95.7	Elite
4	Ryzen 9 9900X3D	86.9	Excellent
5	Ryzen 7 7800X3D	85.6	Excellent
6	Ryzen 9 7950X3D	83.9	Excellent
7	Ryzen 5 7600X3D	80.6	Excellent
8	Core i9-14900K	78.2	Strong
9	Core Ultra 7 270K Plus	77.5	Strong
10	Ryzen 9 7900X3D	77.1	Strong
11	Ryzen 9 9950X	76.9	Strong
12	Core i9-13900K	76.8	Strong
13	Core i7-14700K	76.4	Strong
14	Core i7-13700K	75.8	Strong
15	Ryzen 9 9900X	73.9	Strong
16	Core Ultra 5 250K Plus	73.3	Strong
17	Core i5-14600K	72.8	Solid
18	Ryzen 5 9600X	72.6	Solid
19	Core Ultra 9 285K	71.8	Solid
20	Ryzen 9 7950X	71.0	Solid
21	Core i5-13600K	70.9	Solid
22	Ryzen 7 7700X	70.6	Solid
23	Core Ultra 7 265K	70.3	Solid
24	Ryzen 9 7900X	69.2	Solid
25	Ryzen 5 7600X	67.3	Solid
26	Core Ultra 5 245K	67.1	Solid
27	Core i7-12700K	65.8	Entry
28	Core i5-12600K	60.8	Entry

Scores are relative 1080p gaming performance (fastest gaming chip = 100) from the Tom’s Hardware CPU benchmark hierarchy, current through June 2026.

How to use the tiers

Elite (3 chips). The fastest gaming processors, all AMD X3D. Worth it for high-refresh 1080p and 1440p competitive play, or if you simply want the best and will keep the platform a long time. For 4K-focused gaming the premium is hard to feel.

Excellent (4 chips). Near the top in games at a more reasonable price, again led by X3D cache. For most gaming builds this tier is the smart ceiling.

Strong (9 chips). High-end Intel Core and non-X3D Ryzen chips. They game very well and pull ahead in multi-core productivity, so this tier suits people who do real work outside games as well as play them. This is also where Intel’s Arrow Lake Refresh lands — the Core Ultra 7 270K Plus and Ultra 5 250K Plus (launched March 2026) added more cores, higher clocks, and a new Binary Optimization tool worth roughly 15% more gaming performance on average, which genuinely pulled Intel back into the conversation. It closes the gap to AMD; it does not erase it. For a pure gaming build the X3D chips above still lead, but a 270K Plus is a legitimate all-rounder if you value multi-core work too.

Solid (10 chips). The value middle. These run any game well and pair naturally with a mid-range graphics card; at 1440p and 4K you would struggle to tell them from the tiers above.

Entry (2 chips). Older or lower-core chips that still game capably at 1080p. Fine for a budget build, especially paired with a card that is the real limiter at your resolution.

Pick the right CPU for your build

A hierarchy shows gaming speed, but the right chip depends on your resolution, your graphics card, and whether you do multi-core work. To compare any two processors head-to-head, use the CPU Comparison Tool. To check whether a CPU will bottleneck a specific graphics card at your resolution, use the PC Bottleneck Calculator. And for where graphics cards land, see the GPU Hierarchy 2026. For specific X3D matchups, weigh the budget Ryzen 5 7600X3D vs 7800X3D and the flagship Ryzen 9 9950X3D vs 9800X3D. For hands-on takes, our Ryzen 7 7800X3D review covers the Excellent-tier value benchmark, and the 9800X3D undervolt guide shows how to run the Elite-tier chip cooler and more efficiently with Curve Optimizer.

DisplayPort & HDMI Bandwidth Calculator (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This calculator tells you whether a given display mode fits over a specific cable standard. Pick your resolution, refresh rate, color depth, and chroma subsampling, and it shows the bandwidth that mode needs and which interfaces can carry it: HDMI 2.0, HDMI 2.1, DisplayPort 1.4, and DisplayPort 2.1 UHBR, both uncompressed and with DSC.

The figures it compares against are the effective bandwidths after encoding overhead, not the marketing raw numbers. HDMI 2.0 and DisplayPort 1.4 both lose 20% to 8b/10b encoding, landing at 14.4 and 25.92 Gbps. HDMI 2.1 uses a more efficient scheme for 42.6 Gbps, and DisplayPort 2.1 UHBR is the most efficient of all, up to 77.4 Gbps. That is why a mode can clear the raw headline number but still not fit.

The honest caveat: this is a close uncompressed estimate using a standard reduced-blanking timing allowance, and real numbers shift slightly with the exact timing your GPU and monitor negotiate. When a mode only fits with DSC, that is normal and visually lossless on modern hardware. If you are pushing the edge of what a link can do, the monitor overclocking guide covers how to test a custom mode safely, and the aspect ratio calculator helps confirm your exact pixel dimensions first.

DLSS vs FSR 2026: Which Upscaler Wins, and on What GPU

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

If you are trying to decide between DLSS and FSR in 2026, the comparison most articles set up is the wrong one. There is no single winner, because the two are not freely interchangeable. DLSS 4 and 4.5 are still the image-quality and frame-generation leader, but they are hard-locked to NVIDIA RTX hardware, and the headline feature only runs on the newest cards. AMD’s FSR 4 closed most of the visual gap with a real machine-learning model and just broke its own hardware exclusivity. The real story is the tension between a locked, best-in-class option and an open, good-enough one, and which side of that line your GPU sits on decides everything.

So the useful question is not “DLSS or FSR.” It is “which one can my card run, and how good is that one.” This guide answers that directly.

The short answer by GPU

Three buckets cover almost everyone.

If you own an NVIDIA RTX card, DLSS is the clear pick, and it is the upscaler you already have. The best version of frame generation needs an RTX 50-series card, but the upscaling itself runs on every RTX generation.

If you own a current AMD card, meaning a Radeon RX 9000 (RDNA 4) or now an RX 7000 (RDNA 3), FSR 4 is genuinely competitive and good enough for most players, though still a touch softer than DLSS in side-by-side comparison.

If you own anything older or non-AMD, such as an RX 6000, a GTX card, or you simply want one upscaler that works on every machine you touch, you fall back to the open, cross-vendor FSR 3.1 or Intel XeSS. Both look clearly worse than the modern ML upscalers, but they run almost anywhere.

The rest of this article unpacks why, with the hardware-support details that actually change which option you can use.

What DLSS 4 and 4.5 actually are

DLSS 4 introduced a transformer-based AI model for Super Resolution, Ray Reconstruction, and DLAA, which NVIDIA describes as the graphics industry’s first real-time application of transformers, replacing the older convolutional neural network. The practical result is better temporal stability, less ghosting, and more retained detail in motion than the previous generation.

Here is the part the marketing tends to bury. That transformer Super Resolution model runs on all RTX generations, including RTX 20, 30, 40, and 50 series. It is not an RTX 50 exclusive. So if you bought an RTX 3070 years ago, you can still run the newest DLSS upscaling today.

What is RTX 50 exclusive is Multi-Frame Generation. MFG generates up to three additional AI frames per rendered frame, the 4X mode, and NVIDIA markets up to 8X performance over traditional rendering. It launched in 75-plus games and apps. It is locked to Blackwell because the RTX 50 architecture adds hardware flip metering needed for smooth multi-frame pacing, and NVIDIA removed the dedicated Optical Flow Accelerator that RTX 40’s older Frame Generation relied on, moving the work onto the RTX 50 Tensor Cores.

Single Frame Generation, the older DLSS 3 style 2X output of one generated frame per rendered frame, works on both RTX 40 and RTX 50, and DLSS 4 gave RTX 40 an upgraded model that uses less VRAM. Frame Generation in any form does not work on RTX 30 or RTX 20. If the difference between upscaling and frame generation is fuzzy, our frame generation explainer walks through exactly what each one does and where it helps.

DLSS 4.5, rolling out through 2026, pushes the quality side further. It adds a second-generation transformer model for Super Resolution that uses five times the compute of the original DLSS 4 transformer and was trained on an expanded high-fidelity dataset. That Super Resolution upgrade is available across all RTX GPUs in 400-plus games and apps. On the frame-gen side, 4.5 adds a 6X Multi-Frame Generation mode and a Dynamic MFG mode that auto-shifts the multiplier to balance frame rate, image quality, and latency, both RTX 50 exclusive. Going from 4X to 6X raises 4K path-traced frame rates by up to 35 percent.

What FSR 4 actually is, and the big 2026 change

AMD’s FSR 4, rebranded as FSR Upscaling and part of the FSR Redstone suite, is AMD’s first ML-accelerated upscaler, delivering image-quality gains over the older FSR 3.1. The full Redstone suite covers FSR Upscaling, FSR Frame Generation, FSR Ray Regeneration, and FSR Radiance Caching.

The most important update of 2026 is that AMD broke RDNA 4 exclusivity. FSR Upscaling 4.1.1, delivered through FSR SDK 2.3 posted on June 24, 2026, now runs on RDNA 3 Radeon RX 7000-series discrete GPUs. AMD states it is optimized to deliver image quality that closely matches the RX 9000 RDNA 4 result. This matters because a huge number of older articles, and AMD’s own launch messaging, still describe FSR 4 as RDNA 4 only. That is now outdated for upscaling.

The exclusivity did not fully dissolve, though. FSR Frame Generation (4.0.1) and FSR Ray Regeneration (1.2.0) remain RDNA 4 only, meaning RX 9000 and above. Only the upscaling component crossed over to RX 7000. And RDNA 2, the Radeon RX 6000 series, is not supported by the ML upscaler at all. Those cards, and non-AMD GPUs, fall back to the analytical, non-ML modes.

The open fallback: FSR 3.1 and XeSS

This is where the open-versus-locked theme pays off for everyone else. FSR 3.1 is open-source under the MIT license on GPUOpen and runs cross-vendor on AMD, NVIDIA, and Intel GPUs. It also decoupled frame generation from upscaling, so FSR 3.1 frame-gen can pair with DLSS or XeSS upscaling. Its hardware compatibility spans Radeon RX 6000, 7000, and 9000, GeForce RTX 20 through 50, and Intel Arc, which makes it the catch-all for any card too old for the ML upscalers.

Intel XeSS is the third option. It runs best on Intel Arc through dedicated XMX matrix cores but ships a cross-vendor DP4a fallback that runs on most modern NVIDIA and AMD GPUs. The DP4a path is a clear step down in sharpness and stability compared to the native XMX path, but it widens compatibility considerably.

Both of these open paths look noticeably worse than DLSS 4 or FSR 4. They are the compatibility layer, not the quality target.

Image quality: who actually wins

On pure picture quality with the latest models, the tech-press consensus is consistent. DLSS 4 and 4.5 with the transformer model remain the quality leader, holding up sharper with better detail retention on fine elements such as fences, foliage, and text while in motion. FSR 4 closed most of the gap against FSR 3 but produces a softer image than DLSS, though it is less prone to grain and pixelation. Digital Foundry’s framing, cited in that comparison, is that FSR 4 is far better than FSR 3, yet DLSS 4 still shows higher detail in dynamic scenes.

How close is close? In one ComputerBase blind test, nearly half of voters preferred DLSS 4.5 to native rendering, which says modern AI upscaling can now exceed native image quality in many scenes. That is a real shift in what these technologies are for. On the AMD side, the practical buyer framing reported in press is that on an RX 9070 XT, FSR 4 delivers roughly 90 percent of the DLSS experience, with the visual gap mainly visible in deliberate side-by-side comparison. That last figure is a softer, less rigorously verified claim than the lab tests above, so treat the exact number as a directional read rather than a measured result.

The honest summary: DLSS still wins on detail, FSR 4 is good enough that most players will not notice in normal play, and the older open upscalers trail both.

Game availability

Availability still favors NVIDIA, though the numbers move constantly. DLSS appears in 650-plus titles in total, with DLSS 4 specifically in 250-plus games, while FSR spans 400-plus titles. FSR 4 game counts vary by source and date and are harder to pin down. AMD reported 85-plus FSR 4 games via Adrenalin 25.9.1 on September 8, 2025, which is a launch-era floor, not a current total. Mid-2026 estimates range from the mid-60s into the low hundreds as adoption and driver-level overrides grow. Treat any exact FSR 4 count you see as approximate and moving.

How to decide

Strip away the brand loyalty and it comes down to the card in your slot.

Own an RTX 50 card and you get the whole stack, transformer upscaling plus up to 6X Multi-Frame Generation. Own an RTX 40 card and you get the best DLSS upscaling plus Single Frame Generation. Own an RTX 20 or 30 card and you get the transformer upscaling, no frame generation. Own an RX 9000 and you get all of FSR 4 including frame generation. Own an RX 7000 and you get FSR 4 upscaling but not the newest frame gen. Own an RX 6000, a GTX card, or an Intel GPU, and you are on FSR 3.1 or XeSS.

If you are still choosing the hardware rather than the software, that is the more consequential decision, and it is worth grounding in real performance tiers. Our GPU hierarchy for 2026 ranks current cards so you can see where each one lands, and if 4K is the goal specifically, the best GPUs for 4K gaming breakdown narrows the field. You can also line two cards up directly with the GPU comparison tool to see the spec deltas side by side.

Where to go next

The upscaler question is really a hardware question wearing a software costume. Sort out which GPU you are buying or already own, and the DLSS-versus-FSR answer falls out of it. To go deeper, read the frame generation explainer to understand the latency tradeoff behind the impressive frame-rate multipliers, check the GPU hierarchy and best 4K GPU guide to place your card in context, and run any two candidates through the GPU comparison tool before you spend a dollar.

Fix GPU Driver Crashes (2026): NVIDIA & AMD Timeout Errors

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

If your screen flickered, went black for a second, and Windows told you the “display driver stopped responding and has recovered,” it is tempting to blame the driver and rage at NVIDIA or AMD. Here is the honest truth most guides skip: the driver is usually not the real culprit. The large majority of so-called GPU driver crashes trace back to an unstable overclock or undervolt (including aggressive factory tuning), unstable memory from an XMP or EXPO profile, marginal power delivery, or a corrupt leftover driver install. The driver is often just the component that happened to stall and report the problem.

Once you understand the actual Windows mechanism behind the crash, the fix order stops being a random list of tweaks and becomes a logical process. This guide explains what is really happening, then walks you through an ordered, verified fix path that matches what Microsoft, NVIDIA, and AMD themselves recommend. It also debunks the most popular bad advice on the internet: raising a registry timeout value to make the error “go away.”

What is actually happening: TDR explained

Windows has a built-in safety feature called Timeout Detection and Recovery, or TDR. According to Microsoft’s documentation, TDR detects when the GPU takes longer than expected to complete an operation, then resets the graphics card so the entire system does not hang. The GPU scheduler inside the DirectX graphics kernel (Dxgkrnl.sys) notices the stall and tries to preempt the stuck task. The wait time on that preempt operation is the TDR timeout.

That timeout is short. The default TDR timeout period in Windows is two seconds. If the GPU cannot finish or preempt the current task within that window, the OS decides the GPU is frozen and resets it.

When the reset succeeds, the only visible artifact is a brief screen flicker as the OS redraws the desktop, plus the informational message “Display driver stopped responding and has recovered,” which Windows also logs in Event Viewer. That recovery is a good outcome. The bad outcome is bug check 0x116, VIDEO_TDR_FAILURE, which Microsoft defines as an attempt to reset the display driver and recover that failed. Windows also bug-checks the whole machine by default on the sixth GPU hang inside one minute, controlled by TdrLimitCount (default 5) and TdrLimitTime (default 60 seconds).

There is one useful nuance. A modern engine reset (bug check 0x141 with the app-blocked code 0x142) can block GPU access for only the offending process instead of the whole adapter, which is why sometimes a single game crashes while the rest of your desktop keeps running, versus the entire screen flickering at once. If your games close to the desktop with no driver-timeout message at all - no black screen, no “display driver stopped responding” flicker - the cause is usually somewhere other than the driver; our games keep crashing on PC guide sorts those crashes by their signature.

Why most “driver crashes” are not the driver

This is where Microsoft’s own primary source does the heavy lifting. The official listed causes of VIDEO_TDR_FAILURE are: an outdated display driver; hardware issues including over-clocked components such as the motherboard; incorrect compatibility or settings, especially memory configuration and timings; insufficient cooling; insufficient power; defective parts like memory modules and motherboards; and too many background programs or visual effects slowing the PC.

Read that list again. Most of those are not “the GPU driver is buggy.” They are the system around the GPU being unstable. In a crash dump, the faulting kernel module is nvlddmkm.sys for NVIDIA and amdkmdag or atikmdag for AMD, which is why the error often reads “Display driver amdwddmg stopped responding.” That module name is what makes people blame the driver, but the module is simply where the stall surfaced. It is the same name Windows prints in parentheses on a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED blue screen - the stop code to work when the machine halts outright instead of recovering.

So the most productive mindset is: a TDR crash is a stability symptom. Treat it like one.

The ordered fix path that actually works

The community-reported fix order that lines up with vendor guidance, documented at MakeUseOf, runs from highest-yield to last resort. Work through it in order and test after each step.

1. Do a DDU clean reinstall in Safe Mode

This single step resolves the largest share of crashes, especially the kind where a new Game Ready or Adrenalin driver broke something that worked fine before. Standard Windows rollback or an over-install leaves enough leftover state behind to keep the bug alive, which is why a clean wipe is the real fix.

Display Driver Uninstaller (DDU) from Wagnardsoft is the standard tool. Its official guidance is to run it in Safe Mode (strongly recommended), use the “Clean and restart” option, and disconnect the internet or block Windows Update until your new driver is installed, so Windows does not silently reinstall an old driver behind your back. Download the latest driver straight from NVIDIA or AMD first, then run DDU, then install the fresh driver. As one community write-up puts it, the leftover registry and driver-store entries that survive an over-install are exactly what keep regression bugs alive. The same clean reinstall also resolves cases where a driver update makes Windows stop seeing a display — see second monitor not detected.

2. Revert every overclock and undervolt to stock

If you run MSI Afterburner, the tuning sliders in Adrenalin, or Ryzen Master, set everything back to default and test. This includes factory-overclocked “OC edition” cards, whose aggressive boost behavior is a leading cause of timeouts. It also includes undervolts: an undervolt that is too aggressive starves the card under load and produces black screens and timeouts just like an unstable overclock. AMD’s own stability guidance explicitly says to restore default settings if Radeon Software or Ryzen Master were used for overclocking, and to disable third-party performance-monitoring and overclocking utilities entirely while you diagnose.

3. Clear overlays and shader caches

Disable in-game and app overlays from Discord, Steam, and Adrenalin, and clear the shader cache. Overlays inject themselves into the render path, and a stale shader cache can replay a corrupt state every launch. This is also a common fix for game-specific crashes, which overlap with anti-cheat conflicts; if a single protected game is the one crashing, our Easy Anti-Cheat fix guide covers that adjacent failure mode in depth.

4. Update Windows and BIOS, then test with XMP/EXPO off

Update Windows and your motherboard chipset and BIOS, set the BIOS to optimized defaults, and test with your memory profile (XMP, EXPO, or DOCP) turned off. Memory instability is one of Microsoft’s named causes, and a too-tight or marginal memory profile is a classic source of TDR. AMD’s guidance also recommends verifying the BIOS is on optimized factory defaults, setting “Power Supply Idle Control” to Typical, and running Windows Memory Diagnostic to rule out RAM. Running the system at stock memory for a day is a fast way to confirm or clear that suspect.

5. Check power delivery and reseat the GPU

If crashes persist, inspect the physical layer. Check that PSU cables are fully seated, pay special attention to a 12VHPWR connector if your card uses one, and reseat the GPU in its PCIe slot. A borderline or failing PSU is a common and badly underdiagnosed cause of timeouts under load.

6. Disable MPO with NVIDIA’s official registry file

NVIDIA officially documented that after Game Ready Driver 461.09 and newer, some desktop apps could flicker or stutter, for example when resizing windows, on some configurations because of Windows 11 Multi-Plane Overlay. NVIDIA provides a downloadable mpo_disable.reg file (and a restore file) as the workaround, which requires a reboot. The common third-party method, a DWORD named OverlayTestMode set to 5 under the DWM key, may no longer reliably disable MPO on Windows 11 24H2 and later, so NVIDIA’s own file is the authoritative route.

The TdrDelay myth: do not do this

Search “fix driver stopped responding” and you will find dozens of pages telling you to raise the TdrDelay value in the registry. The exact keys live under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers, and Microsoft documents the defaults: TdrLevel is 3, TdrDelay is 2 seconds, TdrDdiDelay is 5 seconds, TdrLimitCount is 5, and TdrLimitTime is 60 seconds.

Here is the part those guides leave out. Microsoft explicitly warns that these keys are for driver developers and that “End users shouldn’t manipulate these registry keys.” Raising TdrDelay only gives a hung GPU more time before Windows resets or bug-checks it. You get fewer recovery popups and a delayed blue screen, but the unstable overclock, faulty memory, weak power, or broken driver that caused the stall is still there. It is the equivalent of taping over a check-engine light. Fix the cause from the ordered list above instead.

When it really is the driver (and when it is hardware)

Sometimes a specific driver build genuinely is broken, and a fresh update is the fix. This is a real, current phenomenon. AMD’s own known-issues notes for Adrenalin 26.6.x list intermittent application crashes or driver timeouts on specific hardware while playing specific games. On the NVIDIA side, the RTX 50-series (5080 and 5090) had widespread black-screen and crash issues through early-to-mid 2025, some tied to Multi-Frame Generation and to overclocked cards running at reduced clocks after a reboot. NVIDIA addressed these through successive Game Ready drivers, a hotfix, and a vBIOS update. So updating to a fixed build, or rolling back to a known-good one when a new release regressed, is sometimes exactly right.

But if crashes continue after a DDU clean install, after reverting to stock clocks, and after updating Windows and BIOS, the cause is almost always hardware. At that point you are looking at thermals and throttling, a failing GPU, or a borderline or failing PSU. If the card is throwing visual corruption — colored lines, snow, or garbled textures — rather than clean crashes, that’s a related but distinct symptom; our guide to GPU artifacts shows how to tell a dying card from a bad cable or an unstable overclock. And if the card has stopped being detected altogether — gone from Device Manager, or absent from the BIOS screen — that’s a separate diagnostic path; see graphics card not detected to find where it disappears before assuming the card is dead. If you suspect the card itself is on the way out and you are weighing a replacement, our 2026 GPU hierarchy ranks current cards by real performance tier, and the GPU comparison tool lets you put two specific cards side by side so you can size an upgrade sensibly rather than guessing.

GPU driver crashes are a stability puzzle, not a verdict on your hardware. Start with the DDU clean install, revert your clocks to stock, and only move down the list if the flicker keeps coming back. Skip the TdrDelay registry “fix” entirely; Microsoft says it is not for you, and it solves nothing.

If a single anti-cheat-protected game is what crashes rather than your whole desktop, read the Easy Anti-Cheat fix guide next. If your testing points at a dying card and you need an upgrade, the 2026 GPU hierarchy and the GPU comparison tool will help you pick the right replacement without overspending.

FOV Calculator: Convert Field of View Between Aspect Ratios (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This calculator converts a game’s field of view between aspect ratios and between horizontal and vertical FOV. Enter your current FOV, say whether it is horizontal or vertical, pick your current aspect ratio, and choose a target - for example converting a 16:9 setting to a 21:9 or 32:9 ultrawide. It uses Hor+ scaling, holding the vertical view constant and widening the horizontal view, which is how most modern PC games behave.

The honest caveat: games define FOV differently. Some sliders are horizontal, some vertical, and a few old engines use a 4:3 base. The math here is exact geometry, so if a converted number does not match in-game, the usual reason is that your source game uses a different axis than you assumed - switch the horizontal/vertical type and re-check.

To work out a screen’s exact aspect ratio first, use the Aspect Ratio Calculator; a wider screen also renders more pixels, so size your GPU with the PC Bottleneck Calculator.

Horizontal versus vertical FOV

A single FOV number is ambiguous unless you know its axis. Horizontal FOV measures the angle across the screen’s width, vertical FOV across its height, and for the same scene they are linked by the aspect ratio: the wider the screen, the larger the horizontal figure is relative to the vertical. Many shooters expose horizontal FOV; a lot of newer and console-first engines expose vertical, sometimes labeled just “FOV.” That mismatch is the single most common reason a converted number does not match in-game, so if it looks off, switch the type and compare again.

Hor+ scaling and ultrawide

Most modern PC games use Hor+ (horizontal-plus) scaling: they hold the vertical field of view fixed and extend the horizontal to fill a wider screen. That is why a well-behaved game on an ultrawide shows more of the world at the sides rather than a stretched or zoomed image. The opposite, Vert- scaling, crops the top and bottom instead, which is what you get in games that do not properly support ultrawide. This tool uses Hor+, so converting a 16:9 setting to 21:9 holds the vertical view steady and widens the horizontal, matching how a correct game behaves.

What FOV to actually use

There is no single right value, but some anchors help. On 16:9, many players land between 90 and 105 degrees horizontal: higher feels more aware and is popular in competitive shooters, lower feels more cinematic. If you get motion sickness, a higher FOV usually helps by reducing the zoomed-in, swimming feel. Sitting closer to a bigger screen also argues for more FOV. On ultrawide, keep your vertical comfort level and let the horizontal number rise, which this tool does for you. Try a value, play a session, adjust. To confirm your screen’s exact ratio first, use the Aspect Ratio Calculator.

Frame Generation Explained: DLSS 4, FSR & AFMF (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

Frame generation is a smoothness multiplier, not a performance fix. That single sentence solves most of the confusion around DLSS 4, FSR, and AMD’s Fluid Motion Frames. The technology shines only when you already have a healthy base framerate, roughly 50 to 60 fps native before you switch it on, paired with a high-refresh display to actually show the extra frames. Below that floor it makes games look worse because artifacts get magnified, and feel worse because latency stays tied to your low base rate even as the fps counter balloons. That is exactly the situation struggling players are tempted to “fix” with it, which is the worst possible time to use it.

The honest framing most guides skip: the fps number frame generation reports is a fluency metric, not a responsiveness metric. Once you separate those two ideas, every other decision gets easier.

How Frame Generation Actually Works

Frame generation creates entirely new, AI-built frames and inserts them between traditionally rendered frames to raise the displayed frame rate, rather than rendering those extra frames in the game engine. Every consumer implementation today, NVIDIA DLSS, AMD FSR, and AMD AFMF, is interpolation-based: the system sits between two real frames and generates the in-between frame, as NVIDIA describes in its DLSS documentation.

That word, interpolation, is the whole story. To insert a frame between frame A and frame B, the system needs both A and B in hand first. So it holds back frame A, waits for frame B to finish rendering, builds the middle frame, then releases all of them in order. That buffering is why interpolation inherently adds latency. The generated frame is built from past data, so it physically cannot reduce input-to-display responsiveness. The only real lever to shrink that latency cost is a higher base framerate, because shorter frame times mean less waiting.

If you want to understand whether your own system is even GPU-limited enough to benefit, run your build through our PC bottleneck calculator first. A CPU-bound game gets little from frame generation no matter what the marketing slides promise, and Star Citizen is the extreme case: it is limited by the CPU and the server, and as of Alpha 4.5 it does not support frame generation at all.

DLSS 3 vs DLSS 4: One Extra Frame vs Three

Treating all frame generation as the same thing is the most common mistake, so here is the lineup.

DLSS 3 Frame Generation launched in 2022. It generates one additional frame per rendered frame for up to a 2X frame-rate multiplier, and NVIDIA marketed up to 4X “performance” when stacked with DLSS upscaling. It is exclusive to RTX 40 series and newer because it leans on the Ada Lovelace Optical Flow Accelerator and 4th-gen Tensor Cores, per NVIDIA’s own launch material. Note that the DLSS upscaling portion of those games still runs on RTX 20 and 30 cards; only the frame-generation component is locked out on older hardware.

DLSS 4 Multi Frame Generation arrived in January 2025 and generates up to three additional frames per rendered frame in 4X mode, which NVIDIA frames as up to an 8X multiplier with the full DLSS suite. It is exclusive to RTX 50 series Blackwell GPUs, as detailed in NVIDIA’s DLSS 4 announcement. Under the hood, DLSS 4 swapped the older CNN for a transformer-based model that NVIDIA says is 40% faster and uses 30% less VRAM, running once per rendered frame to produce multiple frames. Blackwell also adds hardware Flip Metering, which moves frame-pacing logic onto the display engine for steadier pacing.

DLSS 4.5, announced for Spring 2026 and RTX 50 only, adds a second-generation transformer model and pushes the ceiling to a 6X multiplier, five generated frames per rendered frame. It also introduces Dynamic Multi Frame Generation, which varies the multiplier in real time to target your display’s refresh rate instead of locking to a fixed 2X, 3X, or 4X setting.

For a deeper image-quality and hardware breakdown of how all of this stacks up against AMD, see our DLSS vs FSR comparison.

AMD’s Two Answers: FSR Frame Gen and AFMF

AMD splits the job into two separate tools, and the distinction matters.

FSR Frame Generation is the integrated path. It generates one interpolated frame between two consecutive rendered frames, effectively doubling the displayed frame rate, but it needs render-resolution motion vectors, depth, and camera data from the game itself, so a developer has to build it in. The original FSR 3 Frame Generation from 2023 was cross-vendor and ran on a wide range of GPUs, while the newer ML-based FSR “Redstone” frame generation requires Radeon RX 9000 RDNA 4 and above, according to AMD’s GPUOpen documentation. The cross-vendor reach of FSR 3 is real and worth repeating: it runs on NVIDIA RTX 20, 30, and 40 series and Intel Arc, unlike DLSS Frame Generation, which is locked to NVIDIA’s own RTX 40 and 50 cards.

AMD Fluid Motion Frames (AFMF) is the driver-level path. It lives in Adrenalin software and works in DirectX 11 and 12 games with no developer integration at all, on Radeon RX 6000 and 7000 and newer, as AMD describes it. The tradeoff is built into how it operates. Because it runs at the driver level, it has no in-game motion vectors, so generated frames can include UI and HUD artifacts. AFMF 2 improved latency and added Borderless Fullscreen plus Vulkan and OpenGL support, and the 2.1 revision reduced ghosting and overlay-text problems. AFMF also disables itself during fast camera motion to avoid heavy artifacting, which is why panning quickly can produce an on-off “judder” feel.

The Latency Tradeoff Nobody Puts on the Box

Enabling frame generation does not reduce input lag. On its own it raises latency. NVIDIA Reflex and Reflex 2, and AMD Anti-Lag and Anti-Lag 2, exist to claw that penalty back toward, not below, your native baseline. They make the penalty less severe; they do not make generated frames as responsive as real ones. Pairing frame generation with Reflex or Anti-Lag is not optional polish. It is the thing that keeps the whole feature usable.

The newer end of this is meaningful. Reflex 2 with Frame Warp reduces PC latency by up to 75% by reprojecting the final rendered frame to your most recent input right before display. NVIDIA’s cited example in THE FINALS at 4K max on an RTX 5070 goes from 56ms unoptimized to 27ms with Reflex to 14ms with Reflex 2 Frame Warp. That is a real responsiveness gain, but notice it is a separate technology layered on top of frame generation, not a property of frame generation itself.

Where the Base-Framerate Floor Comes From

This is the line the rest of the internet keeps blurring. Vendor guidance is surprisingly consistent: AMD recommends roughly 60 fps before enabling FSR 3 Frame Generation and says sub-30 fps should be absolutely avoided, Intel recommends a 40 fps minimum with 60 ideal for XeSS, and NVIDIA recommends targeting at least roughly 120 fps output with a high-refresh monitor to display the extra frames.

Independent testing backs this up. Digital Foundry found that with a 40 to 60 fps base before frame gen, games felt responsive, and that most of the added latency comes from buffering that first extra frame, with additional intermediate frames adding relatively little on top. At a 30 to 40 fps base, the experience is poor and artifacts become much more noticeable. The community widely reports the same thing across r/nvidia, ResetEra, and Steam discussions, landing on roughly a 50 to 60 fps native base as the practical feel-good floor and disliking it for competitive play.

Why does a low base make it worse on both axes? Because at a low base the gap between real frames is larger, so there is more to interpolate and each frame sits on screen longer, which makes any error more visible. Generated frames can show ghosting, shimmer, and distortion on fast-moving elements and especially on UI and text, and those artifacts get worse the lower your base goes. The DLSS 4 transformer model reduces ghosting versus the old CNN, but it does not repeal the math.

The “Fake Frames” Debate, Fairly

The criticism is not just noise. GamersNexus and Hardware Unboxed argue that generated frames are not a like-for-like substitute for rendered ones because they are interpolated from past frames, carry no new game state, and do not improve responsiveness, so reporting a Multi Frame Generation fps number next to a native fps number is misleading. GamersNexus specifically flags NVIDIA’s headline 8X figure as combining 4X Multi Frame Generation with DLSS upscaling set to Performance, which is a quarter-resolution render. The fps tripled or quadrupled; the underlying simulation did not.

The constructive version of this critique, echoed across tech press, is that frame generation does not fix bad performance. It should not be used to compensate for poor optimization or to drag a low base up to a “playable” 60. There is real concern that some developers lean on it as a crutch, occasionally shipping games where frame gen is effectively required to hit advertised framerates. Frame generation multiplies a good base. It does not create one.

When to Use It, and When to Turn It Off

Put simply, this is a single-player, cinematic-game feature. Turn frame generation off for competitive and fast-paced multiplayer, because the added latency directly hurts aim and reaction time and the smoothness gain does not pay for that cost in an esports title. If you bounce between several of those titles, holding one physical cm/360 across them is the other half of consistent aim — that is what the mouse sensitivity converter does. It belongs in visually demanding games where you already hold a solid base framerate and want the motion to look smoother.

A few practical rules that fall out of the facts above:

Never use it to escape a sub-40 fps base. That is the one place it hurts on both image and feel.
Always pair it with Reflex or Anti-Lag. The latency penalty is real and these are how you partly offset it.
It needs a high-refresh display to matter. On a plain 60Hz panel, generating frames above 60 gives little benefit and can introduce tearing without variable refresh rate.
Match the tech to your card. DLSS Frame Generation needs RTX 40 or 50; FSR 3 Frame Generation runs cross-vendor; the newest ML FSR frame gen needs RDNA 4.

Looking ahead, extrapolation, predicting a future frame from your latest input instead of interpolating between two past frames, is positioned as the path to cut the latency cost, but as of mid-2026 every mainstream consumer implementation is still interpolation-based.

Where to Go Next

If you are deciding which upscaling and frame-generation ecosystem to buy into, our DLSS vs FSR comparison breaks down image quality and hardware support side by side. Shopping for a card that actually has a high enough base framerate to make frame generation worthwhile at 4K? Start with our best GPU for 4K gaming guide and put two specific cards head to head in the GPU comparison tool. And before you blame your GPU for low frames at all, run the PC bottleneck calculator to confirm you are GPU-limited rather than CPU-limited, because frame generation only earns its keep when the GPU is the part holding you back.

GPU Comparison Tool: Compare Any Two Graphics Cards (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This tool compares any two graphics cards head-to-head and shows which is faster, by how much, at the resolution you actually play. Pick two cards and a resolution. The result is a relative performance margin, plus a breakdown at 1080p, 1440p, and 4K so you can see where the gap widens or narrows.

One honest caveat up front: these are rasterized gaming scores, not absolute frame rates, and they exclude ray tracing and DLSS/FSR upscaling. They are the fairest like-for-like baseline, but a card’s standing can shift in ray-traced titles or with frame generation. The most useful thing the tool surfaces is where the winner changes with resolution — a card that is a hair ahead at 1080p can fall behind at 4K once its VRAM runs short, and that is exactly the kind of buying mistake worth catching early.

Scores come from the Tom’s Hardware GPU benchmarks hierarchy (rasterized gaming, native resolution), current through June 2026. To check whether your processor can keep up with a given card, pair this with the PC Bottleneck Calculator.

How to read the result

The number this tool gives you is a relative margin, not a frame rate. If it says one card is 18 percent faster at 1440p, that card’s aggregate raster score is 18 percent higher across the benchmark set. In a GPU-bound game that lands close to 18 percent more frames, but it is not a promise for any single title, and it says nothing about the absolute FPS either card hits in the game you actually play. Treat it as the size of the gap. If you have a specific frame-rate target in mind, look up benchmarks for that exact game and settings to turn the gap into real numbers.

The scores are rasterized, native-resolution results with no upscaling and no ray tracing. That is the fairest like-for-like baseline, but it is a baseline, not the whole story. Turn on heavy ray tracing and NVIDIA cards usually gain ground. Turn on DLSS or FSR with frame generation and either card can jump well past its native result. If those features are central to how you play, add a mental adjustment on top of what you see here.

Where VRAM flips the winner

The most useful thing this comparison surfaces is the resolution breakdown, because the winner can change between 1080p and 4K. Two cards that trade blows at 1080p can separate hard at 4K, and the usual culprit is video memory. Higher resolutions load bigger textures and frame buffers into VRAM; an 8GB card that was fine at 1080p can run short at 4K and stutter, while a 12GB or 16GB card keeps scaling. Memory bandwidth and cache size matter too, but capacity is the one that produces the obvious, ugly stutters.

That is why the tool shows the margin at all three resolutions and flags when the faster card actually changes. If you play at 4K, or plan to within the life of the card, weight the 4K column and the VRAM figure more heavily than a 1080p average that will not reflect your reality.

Price per frame beats raw speed

Raw performance is the wrong number to shop on by itself. The one that matters is price per frame: what you pay for each unit of performance. A card that is 10 percent slower but 25 percent cheaper is usually the better buy, because that 10 percent gap is rarely visible in normal play while the money saved is very real. Run the performance margin here against the actual price gap before you decide.

There are three cases where paying up for the faster card is worth it: you are chasing a specific frame-rate target the cheaper card cannot reach, the faster card also carries more VRAM that will extend its useful life, or its efficiency and feature set genuinely matter to you. Absent one of those, the cheaper card with the better price per frame is the smarter pick.

Matchups worth running

If you are cross-shopping this generation, the comparisons people run most are the ones where the value line is close. A few worth putting head to head, with full written reviews if you want the detail:

RTX 5070 Ti vs RX 9070 XT - the 1440p value fight of the generation.
RTX 5060 Ti vs RX 9060 XT - where the 8GB-versus-16GB question bites hardest.
RTX 4080 vs RTX 4090 - the classic “is the halo card worth it” call.

Once you have picked a card, check your processor can keep up with the PC Bottleneck Calculator, or price a full system around it with the PC Builder.

GPU Hierarchy 2026: Graphics Card Tier List by Performance

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This is a 2026 GPU hierarchy: a tier list of 41 modern graphics cards ranked by how they actually perform in games, not by price or marketing. Each card carries a relative performance score at 1080p, 1440p, and 4K, its video memory, and a tier label. The ranking is sorted by 1440p performance — 1080p still leads the Steam Hardware Survey, but 1440p is where most current GPU buying decisions concentrate — and the scores are normalized so the fastest card equals 100.

There is one idea to hold onto before you read a single row. A GPU hierarchy is not a shopping list; it is a speed map. It tells you how fast each card is relative to every other card, and nothing else. Price, availability, power draw, and driver quirks all sit on top of that map, and in mid-2026 — with a memory shortage pushing street prices well past MSRP (see the RAM and SSD price crisis for why GDDR is caught in the same squeeze) — the price layer moves faster than the performance layer ever will. So read the ranking for where a card lands, then check the current street price before you buy.

A note on how to read the numbers: these are rasterized gaming scores at native resolution, the fairest like-for-like baseline across NVIDIA, AMD, and Intel. They exclude ray tracing (which favors NVIDIA in heavy-RT titles) and upscaling like DLSS and FSR (which can lift any card well past its native result). And the single most useful thing this table does that a spec sheet cannot is show you how a card holds up as the resolution climbs. That is where the 8GB cards quietly fall apart — which is worth its own picture.

The 8GB problem, in one chart

Every card here scores lower at 4K than at 1080p; that is just physics. But some cards fall much further than others, and the reason is almost always video memory. When a card runs out of VRAM at 4K, it does not slow down gracefully — it stutters, swaps textures, and collapses well below where its raw speed says it should be.

The cleanest way to see it is to ask how much of a card’s relative pace it keeps at 4K. Below, “retention” is each card’s 4K score as a share of its own 1080p score. The pairing that removes all doubt is the RTX 4060 Ti: the exact same GPU, sold in 8GB and 16GB versions, retains dramatically less on the 8GB model. Same silicon, same clocks — only the memory differs.

4K performance retention

Each card's 4K score as a share of its own 1080p score. Higher = holds its pace at 4K.

8GB cards — fall off a cliff

RTX 4060

45%

RTX 5060

45%

RTX 3060 Ti

48%

RTX 4060 Ti 8GB

50%

12–16GB cards — hold their ground

RTX 4060 Ti 16GB

64%

RX 9060 XT 16GB

66%

RTX 5060 Ti 16GB

70%

The RTX 4060 Ti keeps 64% of its pace at 4K with 16GB but only 50% with 8GB. Same chip. That 14-point gap is pure VRAM.

techfuelhq.com · retention = 4K score / 1080p score, from the Tom's Hardware hierarchy

The takeaway is not “never buy an 8GB card.” It is that an 8GB card is a 1080p card in 2026, full stop — and if you are shopping at 1440p or 4K, a slightly slower card with more memory will usually age better than a faster one that runs out of it. Keep that in mind as you read the tiers.

The 2026 GPU hierarchy

#	Graphics card	1080p	1440p	4K	VRAM	Tier
1	GeForce RTX 5090	100.0	100.0	100.0	32GB	Flagship
2	GeForce RTX 4090	90.1	85.7	80.4	24GB	Flagship
3	GeForce RTX 5080	81.9	76.7	69.8	16GB	Flagship
4	Radeon RX 7900 XTX	79.3	73.1	63.7	24GB	Flagship
5	GeForce RTX 4080 Super	78.0	70.9	62.6	16GB	Flagship
6	GeForce RTX 4080	77.2	70.3	60.9	16GB	Flagship
7	GeForce RTX 5070 Ti	76.2	69.8	61.9	16GB	Flagship
8	Radeon RX 9070 XT	76.9	69.7	59.4	16GB	Flagship
9	Radeon RX 7900 XT	71.3	64.6	54.0	20GB	High-end
10	GeForce RTX 4070 Ti Super	69.3	62.1	52.8	16GB	High-end
11	Radeon RX 9070	69.1	62.1	52.1	16GB	High-end
12	GeForce RTX 3090 Ti	64.7	59.7	53.5	24GB	High-end
13	GeForce RTX 4070 Ti	66.3	58.6	48.6	12GB	High-end
14	GeForce RTX 5070	65.1	57.6	49.0	12GB	High-end
15	GeForce RTX 3090	60.3	54.7	47.9	24GB	High-end
16	GeForce RTX 4070 Super	62.2	54.5	44.4	12GB	High-end
17	Radeon RX 6950 XT	60.5	53.5	43.6	16GB	High-end
18	GeForce RTX 3080 Ti	58.7	53.3	46.0	12GB	High-end
19	Radeon RX 9070 GRE	59.2	51.8	41.8	12GB	Mid-range
20	Radeon RX 7800 XT	58.1	50.7	40.7	16GB	Mid-range
21	Radeon RX 6900 XT	57.4	50.2	40.5	16GB	Mid-range
22	GeForce RTX 3080 (10GB)	54.8	49.0	39.6	10GB	Mid-range
23	Radeon RX 6800 XT	54.9	47.6	38.1	16GB	Mid-range
24	GeForce RTX 4070	54.7	46.5	37.2	12GB	Mid-range
25	GeForce RTX 5060 Ti 16GB	51.6	43.9	36.3	16GB	Mid-range
26	Radeon RX 7700 XT	50.5	43.4	34.3	12GB	Mid-range
27	Radeon RX 9060 XT 16GB	48.2	40.2	31.7	16GB	Mid-range
28	GeForce RTX 3070 Ti	46.4	40.0	23.5	8GB	Mid-range
29	Radeon RX 9060 XT 8GB	45.7	37.3	26.8	8GB	Budget
30	GeForce RTX 4060 Ti 16GB	43.8	36.2	28.2	16GB	Budget
31	GeForce RTX 5060	43.4	35.8	19.6	8GB	Budget
32	GeForce RTX 4060 Ti 8GB	43.2	35.2	21.5	8GB	Budget
33	GeForce RTX 3070	42.8	34.8	23.6	8GB	Budget
34	Radeon RX 6750 XT	40.8	34.4	26.7	12GB	Budget
35	Radeon RX 6700 XT	38.9	32.5	25.3	12GB	Budget
36	GeForce RTX 3060 Ti	36.4	30.5	17.5	8GB	Budget
37	Intel Arc B580	35.1	30.3	24.9	12GB	Budget
38	GeForce RTX 4060	35.1	28.4	15.7	8GB	Entry
39	Radeon RX 7600	34.3	27.2	16.6	8GB	Entry
40	Intel Arc B570	31.1	26.5	17.7	10GB	Entry
41	GeForce RTX 3060 12GB	30.2	25.0	20.0	12GB	Entry

Scores are relative (fastest card = 100) from the Tom’s Hardware GPU benchmark hierarchy, rasterized gaming at native resolution, current through June 2026.

How to use the tiers

Flagship (8 cards). The fastest cards available, built for 4K gaming and high-refresh 1440p. This is where you pay the steepest price-per-frame premium, so buy here only if you genuinely game at 4K or chase very high frame rates; the value is worse than the tiers below by design.

High-end (10 cards). Comfortable 1440p at high refresh and capable 4K with some settings management. For most enthusiasts this tier is the sensible ceiling: most of the performance of a flagship at a meaningfully lower price.

Mid-range (10 cards). The volume sweet spot. These cards run 1440p well and 1080p at high refresh, and they tend to offer the best performance per dollar. Most gamers are best served here, especially paired with a 1440p monitor.

Budget (9 cards). Built for 1080p high-refresh and entry 1440p. Watch the VRAM: 8GB at this tier is increasingly tight in new 2026 titles, so a slightly slower card with more memory can age better.

Entry (4 cards). The floor for modern gaming at 1080p with adjusted settings. Fine for esports and lighter titles; plan to lower settings in the most demanding games. Below this tier sits NVIDIA’s RTX 5050 — a $249, 8GB, 130W card that lands roughly a step under the RTX 4060 and is built strictly for 1080p. It is the cheapest current-generation new card, and its whole pitch rests on DLSS 4 and frame generation rather than raw silicon, so treat its native raster standing as entry-tier and lean on upscaling to stretch it.

Reading the brands

Sort the ranking by tier and a pattern falls out. At the very top, NVIDIA owns the halo: the RTX 5090 and 4090 have no AMD answer, and if you want the single fastest card, that is the conversation. Drop into High-end and Mid-range and AMD gets far more interesting — the RX 9070 XT, 9070, and 7800 XT deliver flagship-adjacent raster for meaningfully less, and AMD has been more generous with VRAM at every price, which the retention chart above rewards. Intel’s Arc B580 and B570 are the wildcards: they punch above their raster score in value terms and carry a healthy 12GB and 10GB of memory, but they lean on newer drivers and are best for a fresh 1080p build rather than a drop-in upgrade.

Two caveats this raster ranking deliberately hides. Turn on heavy ray tracing and the order tilts toward NVIDIA, sometimes by a lot. Turn on upscaling and frame generation and any card can leap well past its native line — DLSS 4 Multi-Frame Generation in particular flatters the RTX 50-series. The hierarchy is the honest native-raster baseline; those two levers are yours to add back based on the games you actually play.

Pick the right card for your build

A hierarchy tells you raw speed, but the right card depends on your resolution, your CPU, and your budget. To compare any two cards head-to-head at your resolution, use the GPU Comparison Tool. To check whether your processor can keep up with a given card (or whether you are about to create a bottleneck), use the PC Bottleneck Calculator. For a worked 1440p build around a mid-range card, see the $1,500 RTX 5060 Ti 1440p build. For hands-on takes on where specific cards land, our head-to-head reviews go deeper — the RTX 5060 Ti vs RX 9060 XT 1440p showdown and the ROG Astral RTX 5080 review among them. And once you have picked a card, the complete GPU undervolting guide shows how to run it cooler, quieter, and often a little faster — with real per-card settings in the undervolt results database.

How to Fix Screen Tearing (2026): VRR, V-Sync & FPS Caps

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-29 · ~8 min read · St. Louis County, MO

The old advice was simple: see a tear, turn on V-Sync. In 2026 that advice is mostly wrong. Screen tearing is not something you fix by toggling one checkbox anymore. The real fix is variable refresh rate, which means G-Sync, FreeSync, or the open VESA Adaptive-Sync standard, paired with a frame-rate cap set a few frames below your monitor’s maximum refresh. V-Sync still exists, and it still kills tearing, but it has become the fallback for people without a VRR monitor, not the default. This guide ranks the fixes from best to last resort and gives you exact, copy-pasteable numbers and click paths.

What screen tearing actually is

Tearing comes from a timing mismatch. Your GPU writes a new frame to the framebuffer while the monitor is partway through drawing the previous one, so a single screen scan ends up showing parts of two or more frames at once. That produces the familiar horizontal split or line across the image, usually most visible during fast horizontal camera pans — a line that exists only while the picture is moving, unlike the persistent lines on a monitor that point at a cable, a port, or a dying panel. The key technical detail, explained well by DisplayNinja, is that the GPU and the monitor are simply not synchronized.

There is a common misconception worth clearing up early. Tearing is not only a too-many-frames problem. It can occur both when your frame rate is higher than your refresh rate, which is the most obvious case, and when it is lower than your refresh rate. So capping your frame rate alone does not make tearing go away. The cap has a job, but eliminating tearing is not it. (If your problem is a faint trail following moving objects rather than a clean horizontal split, that’s a different artifact entirely — see how to fix monitor ghosting.)

The best fix: VRR plus an FPS cap

Variable refresh rate flips the relationship between GPU and monitor. Instead of forcing the GPU to wait on a fixed refresh, VRR makes the monitor dynamically change its refresh rate to match the GPU’s frame rate in real time, as long as that frame rate stays within the monitor’s supported VRR range. DisplayNinja gives a clean example: if your game is running at 65 FPS, the panel shifts to 65Hz to match, which eliminates both tearing and stutter with only about a 1ms input-lag penalty. That is a fraction of what V-Sync costs.

There are three flavors. VESA Adaptive-Sync is the open standard, introduced by VESA in 2014 under DisplayPort 1.2a. AMD FreeSync is built on top of Adaptive-Sync, which is why it is open, royalty-free, and needs no proprietary monitor hardware, per AMD’s FreeSync page. NVIDIA’s original G-Sync uses a proprietary scaler module embedded in the monitor and typically supports VRR from 1Hz all the way to the panel’s max refresh.

You do not need matching brands. NVIDIA GPUs can drive FreeSync and Adaptive-Sync monitors through the G-Sync Compatible program — supported since the January 2019 driver on GTX 10-series cards and everything newer — so VRR is no longer locked to one vendor. As RTINGS notes, true G-Sync module monitors historically cost roughly $100 to $200 more than comparable FreeSync panels because of the proprietary chip and licensing. For most people, a certified Adaptive-Sync monitor is the better value.

Enabling G-Sync (NVIDIA)

Per NVIDIA’s own control panel documentation, the steps are:

Open the NVIDIA Control Panel.
Go to Display, then “Set up G-SYNC.”
Check “Enable G-SYNC / G-SYNC Compatible.”
Choose “Enable for full screen mode” or “Enable for windowed and full screen mode.”

The prerequisite is a G-Sync-capable or G-Sync Compatible display connected, enabled, and set as your primary display. To confirm it is actually working, turn on “Show indicator for G-SYNC” in the Display menu, which puts an on-screen overlay up in-game when VRR is active.

Enabling FreeSync (AMD)

The AMD path is shorter because, per AMD’s support FAQ, FreeSync is enabled globally by default on systems with a compatible AMD GPU and a FreeSync-certified display. To check or toggle it:

Open AMD Software: Adrenalin Edition.
Go to Settings (the gear icon), then Display.
Confirm or toggle “AMD FreeSync.”

Per game, you can set FreeSync to “AMD Optimized,” which is the default, or “On,” or “Off” in the application profile.

The critical step: cap your FPS below refresh

This is where most people go wrong. Enabling VRR is only half the fix. You also need a frame-rate cap a few frames below your monitor’s maximum refresh so you stay inside the variable-refresh window. Per Blur Busters’ G-SYNC 101 testing, the tested safe target is about 3 FPS below your max refresh:

Refresh rate	Cap to
60Hz	57 FPS
100Hz	97 FPS
120Hz	117 FPS
144Hz	141 FPS
165Hz	156 FPS
240Hz	233 FPS

The minus-3 figure is the tested minimum; some setups need a slightly larger margin depending on the limiter or the game. Whatever you do, do not cap exactly at your refresh rate. Capping 144 on a 144Hz panel pushes you up against the ceiling, which kicks you out of the VRR range and brings tearing or V-Sync lag right back.

The enthusiast combo: G-Sync + V-Sync + cap

Here is the counterintuitive part. Blur Busters’ G-SYNC 101 testing found that the lowest tear-free latency comes from running G-Sync ON, V-Sync ON in the NVIDIA Control Panel (not in-game), keeping your frame rate inside the refresh range, and keeping GPU usage below about 99 percent. The reason this works is subtle but important. When V-Sync is on, G-Sync reverts to V-Sync behavior above its range, so there is no tearing at the ceiling. When V-Sync is off, G-Sync disables above its range and tearing returns display-wide.

So the combination of G-Sync + V-Sync On + an FPS cap gives you tear-free output across the entire range. The cap, not V-Sync, is what keeps latency low, because the cap keeps you out of the V-Sync region in normal play. V-Sync only ever activates at the very top edge as a safety net. One more detail from the Blur Busters forums: turn in-game V-Sync off while leaving driver V-Sync on, and disable every in-game “Vertical Sync” or “Triple Buffering” option so the game does not quietly enable its own higher-latency sync path. The game should think it is running with V-Sync off.

Add NVIDIA Reflex when the game supports it

NVIDIA Reflex reduces system latency by aligning game engine work to finish just in time for rendering, which eliminates the GPU render queue and reduces CPU back-pressure in GPU-bound scenes. Per NVIDIA, it cites up to about a 33 percent responsiveness improvement on a GTX 1660 Super, and it works best when you are GPU-bound. Importantly, when you enable Reflex alongside G-Sync and V-Sync, Reflex automatically caps your frame rate just below the refresh rate, so you do not need a manual cap in Reflex-supported games.

The community-recommended modern setup follows from this: if a game supports Reflex, enable G-Sync, V-Sync (driver), and Reflex, then run uncapped in-game and let Reflex’s built-in limiter handle the cap. For games without Reflex, set the cap yourself at about 3 FPS below refresh, preferring the in-game limiter when one exists.

The non-VRR options: Fast Sync, Enhanced Sync, and plain V-Sync

If you are stuck on a fixed-refresh monitor with no VRR, you still have choices. NVIDIA Fast Sync and AMD Enhanced Sync are a different class of fix. Per DisplayNinja, they let the GPU render uncapped above the refresh rate while still showing only the most recently completed full frame, which eliminates tearing without V-Sync’s hard wait. The catch is that they work best when your FPS is well above refresh, ideally around twice your refresh or more, so there are spare frames to drop. Below refresh they do not help and can stutter. That makes them a fit for very-high-FPS esports titles on a non-VRR display, and a poor fit for everything else.

Plain V-Sync is the last resort. It stops tearing by forcing the GPU to hold each finished frame until the monitor’s next refresh, but per TechSpot, double-buffered V-Sync at 60Hz adds roughly up to 33ms of input lag, about one to two frames. Worse, with plain double-buffered V-Sync, if your frame rate drops below your refresh rate the GPU misses the refresh window and V-Sync drops you to the next divisor. As DisplayNinja describes, that essentially halves you from 60 to 30 FPS at 60Hz, producing stutter that can feel worse than the tearing you were trying to fix. Triple buffering softens this by giving the GPU a second back buffer so it does not have to stall.

Common mistakes to avoid

Capping AT your refresh rate instead of below it. Cap below, around minus 3, to stay inside the VRR window.
Turning V-Sync off with G-Sync. Backwards. Driver V-Sync on plus an FPS cap below refresh is the low-latency, tear-free setup.
Doubling up in-game and driver V-Sync. Use driver V-Sync on and in-game V-Sync off.
Expecting a frame-rate cap alone to fix tearing. Per a community guide, a cap with no VRR or sync mode only reduces how often and how severely tearing shows up, because the GPU and monitor are still unsynchronized. The cap’s real job is to keep you inside the VRR range.
Thinking frame generation fixes tearing. It does not. Frame generation and upscaling raise smoothness, not synchronization.

A quick note on frame generation, since people conflate it with sync. DLSS 4 on the RTX 50 series and AMD’s FSR 4 line are performance and smoothness features, not tearing fixes. AMD itself ships them alongside, not instead of, VRR, and as PC Gamer reports, FSR 4.1 reached the RX 7000 series on June 22, 2026 as an FPS feature. If you want to understand how that interpolation works and why it still needs VRR underneath it, read our breakdown of frame generation explained.

Where to go from here

Screen tearing is one of the few PC problems with a clean answer in 2026: turn on VRR, cap a few frames below your refresh, and leave driver V-Sync on as a ceiling. If you are still figuring out whether your GPU and CPU are well matched for the frame rates you are targeting, run the numbers through our PC bottleneck calculator so your cap targets are realistic for your hardware. And if your tearing only shows up in certain games, your render path may be part of the story, which is why it is worth reading how DX12 and DX11 differ for FPS before you blame the monitor.

Mouse Sensitivity Converter & eDPI Calculator (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This converter keeps your aim consistent when you switch games. Enter your mouse DPI, your current game, and its in-game sensitivity, then choose the game you want to play. The tool returns the sensitivity that preserves your cm/360 - the physical distance you move the mouse to turn a full circle - so your muscle memory transfers intact. It also shows your eDPI and your exact 360 distance in centimeters and inches.

The method is the one every serious sensitivity converter uses. Each game has a documented yaw, the degrees your view rotates per mouse count at sensitivity 1. Source-engine games like CS2 and Apex share a yaw of 0.022, so they convert one to one; Valorant uses 0.07; the Overwatch 2 and Call of Duty family uses 0.0066. To match your feel in a new game, the target sensitivity is your sensitivity times your game’s yaw divided by the target game’s yaw, which holds your cm/360 constant at the same DPI.

The honest caveat: a handful of games (Fortnite, some battle royales) use a percentage or per-scope slider rather than a clean linear scale, so their conversion is a close approximation marked with an asterisk - confirm it with an in-game 360 test. Field of view also changes how a given sensitivity feels, so if you are also moving between aspect ratios, set your view with the FOV Calculator, and size the GPU that drives your frame rate with the PC Bottleneck Calculator.

PC Bottleneck Calculator: CPU vs GPU by Resolution (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

A bottleneck is when one part of your PC, the CPU or the GPU, cannot keep up with the other, so the faster part sits partly idle and your frame rate is capped below its potential. This calculator estimates which part limits you at the resolution you actually play, using aggregated gaming benchmarks. Pick your processor, your graphics card, and a resolution.

The honest part first: this is a directional estimate, not a benchmark. A real bottleneck depends on the specific game and engine, your settings, your memory speed, your refresh rate, and whether you use upscaling. What the tool is good for is a sanity check before you buy, spotting an obvious mismatch and understanding why the same pair behaves so differently at 1080p versus 4K. Being GPU-bound at 1440p or 4K is not a fault; it is the efficient, intended state.

The processor scores come from the Tom’s Hardware CPU benchmarks hierarchy (1080p gaming) and the graphics-card scores from the Tom’s Hardware GPU benchmarks hierarchy (rasterized gaming), both current through June 2026. The resolution-shifts-the-limiter principle is well established by reviewers and by Intel’s own developer guidance.

How to read the result

The tool gives you a limiter, CPU or GPU, and an imbalance percentage. Read it as a direction and a rough size, not a precise measurement. The processor and graphics-card scores come from two different game suites, so the exact number is an approximation; a result within a few points either way is effectively balanced hardware. What it reliably tells you is which part is likely holding you back at the resolution you chose, and how that flips as the resolution changes. Use it to catch an obvious mismatch before you spend money, then confirm with benchmarks for the specific games you play.

Why resolution decides the limiter

The processor does the same work every frame no matter the resolution: game logic, physics, AI, and setting up draw calls do not care how many pixels the screen has. The graphics card does far more work as resolution climbs, because there are far more pixels to shade. 1440p has roughly 1.78 times the pixels of 1080p, and 4K has four times as many. Raising the resolution loads up the graphics card while the processor’s job stays flat.

That is the whole reason the same CPU-and-GPU pair can be CPU-limited at 1080p and clearly GPU-limited at 4K. It is also why reviewers test processors at 1080p, to expose the gaps between chips, and treat 4K as mostly a graphics-card test. If you play at 4K, a mid-range processor paired with a strong card is usually fine; the same processor can hold that card back at 1080p.

Fixing a CPU bottleneck

If the tool flags your processor as the limiter, there are a few real levers. The most direct is a faster gaming chip, and the ones with extra cache (AMD’s X3D parts) lead in most games because gaming leans hard on cache. Faster memory with its profile enabled (EXPO on AMD, XMP on Intel) helps too, since game performance is sensitive to memory latency. The free option is to raise the resolution or settings, which shifts work onto the graphics card and often hides a mild CPU limit entirely. Before blaming the hardware, rule out the cheap causes: background apps, a stale chipset driver, or a power plan that parks cores can all make a CPU limit look worse than it is.

The mismatches that waste money

Two pairings burn money. The first is a top-tier graphics card behind a weak processor at 1080p: the card spends its life waiting on the CPU and you paid for frames you never see. The second is over-buying the processor for a 4K build, where the graphics card is the limiter anyway and the extra CPU headroom does almost nothing. The goal is not zero bottleneck, which is impossible since one part always leads, but a pair that is balanced for your resolution.

If you are planning a build rather than diagnosing one, the PC Builder picks balanced parts to a budget, and the 7800X3D vs 9800X3D upgrade guide shows how much a cache-heavy gaming chip actually moves the needle. For a worked 1440p example, the $1,500 RTX 5060 Ti build is balanced by design.

PPI & Pixel Density Calculator: Monitor Sharpness (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

This tool calculates the pixel density (PPI, pixels per inch) of any display from its resolution and diagonal size, then tells you what that density means in practice. Enter a width, height, and screen size, or tap a preset for a common monitor. You get the PPI, the pixel pitch in millimeters, the total megapixels, an approximate “retina” distance, and a plain-English sharpness verdict.

The honest framing: PPI does not decide sharpness on its own - viewing distance does. A phone needs far higher density than a monitor because you hold it close. For a desktop screen at arm’s length, anything above roughly 90 PPI looks clean and 140-plus is very sharp, so you do not need phone-class numbers on a monitor you sit back from. The “retina distance” figure is the point beyond which individual pixels get hard to resolve for normal vision.

Pixel density also drives GPU load: more pixels means more work per frame. To size a graphics card for a given resolution, see the GPU Comparison Tool; to work out a screen’s exact aspect ratio, use the Aspect Ratio Calculator.

How this pixels-per-inch calculator works

This screen PPI calculator uses the standard pixel density formula: the diagonal resolution in pixels divided by the diagonal size in inches. It takes the square root of the width squared plus the height squared to get the diagonal in pixels, then divides by the screen’s diagonal in inches. That single number, pixels per inch, is what makes a 27-inch 1440p monitor (about 109 PPI) look crisper than a 32-inch 1440p one (about 92 PPI) even though both have the same resolution. The result also reports pixel pitch in millimetres for the datasheets that list density that way, plus total megapixels and an approximate retina distance, so you can judge sharpness for your actual viewing distance rather than from resolution alone. One disambiguation, since plenty of people land here searching for a “DPI calculator”: a mouse’s DPI is a pointer-sensitivity setting rather than a screen measurement, and that belongs in the mouse sensitivity converter instead.

What PPI to aim for at your distance

Density only matters relative to how far you sit. For a desktop monitor at arm’s length, the useful band is roughly 90 to 160 PPI. Around 90 (a 24-inch 1080p, or a 27-inch 1440p on the larger side) is usable but not crisp. About 109, the density of a 27-inch 1440p panel, is the desktop sweet spot: sharp text with no need for display scaling. Around 140 and up (32-inch 4K and denser) is very sharp but usually wants some operating-system scaling so menus are not tiny. Below about 80 PPI, individual pixels and jagged edges start to show at a desk. Phones and tablets run far higher numbers only because you hold them close.

27-inch 1440p versus 4K, and scaling

At 27 inches, 1440p is about 109 PPI and 4K is about 163 PPI, so 4K is visibly sharper, especially on text and fine detail. The trade-offs: 4K is about 2.25 times the pixels, so it needs a stronger graphics card for the same frame rate, and at 27 inches it usually wants around 150 percent display scaling to keep the interface readable. If you mostly game and chase frames, 1440p is the easier target; if you read, code, or design a lot and have the GPU for 4K, 27-inch 4K is a real step up in clarity. To check a panel’s exact ratio alongside its density, use the Aspect Ratio Calculator.

Star Citizen Best Settings for FPS (2026)

LK Wood IV — Mon, 29 Jun 2026 00:00:00 -0500

If you came here expecting a list of sliders to drop for big FPS gains, here is the honest truth most guides skip: in Star Citizen, graphics settings are the weakest lever you have. In a normal game, lowering settings is the FPS fix. Here it barely moves the needle, because the bottleneck is somewhere your monitor settings cannot reach. The game is limited by CPU single-thread performance, system RAM, NVMe streaming, and above all the server-side simulation. That is not a fault in your PC. It is how this engine works in 2026, and understanding it will save you hours of slider-tweaking that goes nowhere.

So this guide ranks the real levers in order: your hardware floor first, then your renderer and upscaling choice, then the short list of settings that actually help, and finally the part nobody can tune away, the server. Set your expectations there and everything else makes sense.

Why Star Citizen Ignores Your Graphics Card

Star Citizen is primarily CPU-bound, not GPU-bound. The engine spends most of its time processing server state, physics, and NPC AI on the processor, and that work lands hardest on a single core. As one performance tuning guide puts it bluntly, “the CPU is in current state more important than the GPU,” and “even with the fastest GPU on the planet, you won’t achieve high results because, most likely, your CPU will max out before” (citizen-history.com). The official guidance agrees that high single-core performance matters more than core count (starcitizenhelp.com).

The practical consequence is that even an RTX 4090 will not always peg 120 FPS in this game. Cities and stations, packed with NPCs and physics objects, tank your frame rate far more than open space does, and that drop comes from the CPU, not the GPU. If you want to know whether your processor is the part holding you back versus your graphics card, run your parts through the PC Bottleneck Calculator before you buy anything new. In Star Citizen specifically, a faster single-thread CPU usually beats a bigger GPU.

The Hardware Floor That Actually Sets Your Ceiling

Before any in-game setting matters, three hardware pieces decide your experience.

RAM: 32GB is the sweet spot. The official recommended spec is 32GB of DDR4 or DDR5, with a 16GB minimum. A test on a 96GB system showed Star Citizen only using 20 to 30GB, confirming that 32GB is plenty and that more does little (citizen-history.com). 16GB can run the game, but 32GB is the comfort zone most players want.

NVMe SSD: effectively mandatory. Star Citizen streams world data in real time, so a fast NVMe SSD is treated as a hard requirement for a glitch-free experience, not just a nice-to-have. The official guidance is explicit: do not install Star Citizen on a spinning hard drive. Aim for a PCIe Gen 3 or Gen 4 NVMe drive with 3,000 MB/s or higher read speeds, with around 100GB free plus roughly 10GB for the pagefile (starcitizenhelp.com). On a slow drive you get object loading failures and texture pop-in that no graphics setting can fix.

Do not disable your pagefile. This catches a lot of people who have 32GB or 64GB of RAM and assume they no longer need swap. In Star Citizen, “disabling it, even with ample physical memory, invites unnecessary strife.” Set it to System Managed or a minimum of about 16GB, and keep it on the SSD (citizen-history.com). For the full breakdown of recommended parts and why they matter, see the Star Citizen system requirements guide.

Renderer and Upscaling: Your Second-Biggest Lever

Once your hardware floor is set, the renderer is the next decision. Vulkan, the Gen12 renderer, is the default as of Alpha 4.5 and it addresses “common stuttering issues and enhancing game stability” compared to the older DirectX 11 path. It precompiles shaders instead of generating them just in time, spreads rendering across multiple CPU cores, and raises minimum frame rates while cutting stutter in contested areas (citizen-history.com). The fallback advice is simple: Vulkan is better on most modern hardware, but if performance is worse for no clear reason, switch to DirectX 11 and test (GagandeepMalhotra gist).

One gotcha worth flagging: some auto-installed copies of vulkan-1.dll have been flagged by Easy Anti-Cheat, which can cause launch or error problems with the Vulkan renderer. If Vulkan refuses to start, RSI maintains a Vulkan troubleshooting article for exactly this. This sits close to the broader anti-cheat launch issues covered in the Star Citizen error 5007 fix guide, so check there if your launch failure looks anti-cheat related.

On upscaling, Star Citizen Alpha 4.5 added support for the DLSS 4 transformer model alongside the Vulkan improvements, and the game supports NVIDIA DLSS, AMD FSR on all GPUs, and Intel XeSS (mmopixel.com). Star Citizen originally gained DLSS and Vulkan support through an NVIDIA Game Ready driver back in 2024, the same cycle that added F1 24 and Hellblade II (tomshardware.com). Quality or Balanced upscaling is one of the most effective FPS boosts on GPU-limited mid-range hardware, but it provides little benefit when you are CPU-bound, which is most of the time in busy areas.

A clear warning on Frame Generation: it is not supported in Star Citizen as of 4.5. Only upscaling, the super resolution part, works; multi-frame generation does not (starcitizen.tools). Do not go hunting for a Frame Gen toggle expecting it to double your FPS. It is not there, and even if it were, it would not help a CPU or server bottleneck.

The Short List of Settings That Actually Move FPS

Most of the graphics menu is noise in this game. These few entries are the ones worth your attention.

Planet Volumetric Clouds: Low. This is one of the biggest FPS killers in the game and can cause a 20-plus FPS difference on mid-range hardware (GagandeepMalhotra gist). Drop it first.
Object / Object Container View Distance: Medium or High. Ultra “causes significant frame jitter with minimal visual benefit.” Medium or High is the smart trade; some guides go as low as Low for the biggest gain.
Gas Clouds: Low. Shading: Medium. Post Effects: Low. Small but real gains.
Object Detail: High minimum. Setting it Low “causes surface rendering issues on planets,” so do not push this one below High.
Textures: set by VRAM, not by taste. Under 8GB of VRAM, keep textures at Medium to avoid stuttering; 12GB or more can go by preference. The redline matters here: staying under your VRAM cap is smooth, but hitting it, for example 11.2 of 11.2 GB on a 12GB card, creates stutter (GagandeepMalhotra gist).
Shadows, Fog, Water Caustics, Video Comms: negligible FPS impact. These are player preference. Tune them for looks, not frames.

A few NVIDIA Control Panel tweaks help too, though only a few matter: set Shader Cache Size to about 10GB to help in streaming-heavy areas, and removing motion blur and film grain cleans up the image without taxing the CPU (citizen-history.com). On Intel 12th-gen and newer CPUs, micro-stuttering tied to efficiency cores is a known issue; disabling E-cores for the game or pinning Star Citizen to P-cores with a tool like Process Lasso can smooth it out.

The Diagnostic That Separates a Bad PC From a Bad Server

This is the differentiator. Before you blame your hardware, open the console with the tilde key, type r_displayInfo 1, and press Enter. You get an FPS, RAM, and latency overlay in the upper-right corner. Higher values, r_displayInfo 2 through 4, show progressively more detail, and r_displayInfo 0 turns it off (guided.news).

Read it like this. If lowering your resolution barely changes FPS, and cities tank far more than space, you are CPU-bound. If FPS jumps when you lower resolution or switch upscaling modes, and GPU usage is consistently high, you are GPU-bound (citizen-history.com). And the overlay also shows the server. A normal server should run at roughly 4 to 8 FPS; values below about 2 FPS mean a degraded server, and the fix is to switch servers, not to touch a single graphics setting (citizen-history.com). No client setting changes the server tick. That is the ceiling on your experience, and it is invisible until you measure it.

One more expectation to set: Star Citizen compiles shaders on startup, so very low frame rates for roughly the first 10 minutes after logging in, or after a patch, are normal and not a settings problem (boostroom.com). Clear the shader cache after major updates only. Constant clearing just forces expensive rebuilds.

Where to Go Next

Settings help less in Star Citizen than almost anywhere else, and now you know why and what to actually do about it. If you are still deciding whether your CPU or GPU is the real limiter, run your build through the PC Bottleneck Calculator, since in this game a stronger single-thread CPU beats a bigger graphics card. To plan a build that meets the real hardware floor of 32GB RAM and a fast NVMe drive, start with the Star Citizen system requirements guide. And if your trouble is the game refusing to launch rather than running slowly, the Star Citizen error 5007 fix covers the anti-cheat and Vulkan launch failures that often get mistaken for performance problems.

DX12 vs DX11: Which Gives More FPS (and When to Switch)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~9 min read · St. Louis County, MO

TL;DR · DX12 vs DX11

DX12 wins when your CPU is the limit on a modern multi-core PC and the game's DX12 path is well made -- typically 10-20% more FPS because it spreads render work across cores.
DX11 can win when DX12 is poorly implemented -- steadier frame pacing, fewer hitches, better on older or thermally limited machines.
DX12's weakness is shader-compilation stutter when a studio doesn't pre-compile shaders properly.
Ray tracing requires DX12. If you want it, you're on DX12.
The rule: try both, keep whichever gives better 1% lows -- not the higher average FPS counter.

“DX12 vs DX11, which gives more FPS?” has a frustrating but honest answer: it depends on what is bottlenecking your frame rate, and on how well the studio built the game’s DX12 mode. The good news is that once you understand the one real difference between them, you can predict which will help – and test it yourself in two minutes. This guide gives you both.

The one real difference: how they use your CPU

Everything else follows from this. DirectX is the layer that turns “draw this scene” into instructions for your GPU, and the two versions hand that work to your CPU very differently.

DX11 routes most of its render commands through a single main CPU thread. If that one thread maxes out, your frame rate sags – even if the rest of your CPU cores are sitting nearly idle. The driver does a lot of the heavy lifting for you, which keeps things simple and stable, but it is a one-lane road.
DX12 spreads those render commands across multiple CPU cores at once. On a modern six-core-or-more processor, that removes the single-thread choke point, which is exactly why it helps when your CPU is the limit. The trade-off: it moves responsibility from the driver to the game, so a lazy or rushed DX12 implementation can perform worse than DX11.

One lane vs many: how each uses your CPU

Relative render load per CPU core (illustrative)

So which is faster?

The honest rule, in one line: DX12 has the upside when your CPU is the bottleneck and the game’s DX12 path is well built; otherwise the two are close, and a bad DX12 port can lose to DX11.

CPU-bound + modern multi-core CPU + good DX12 port -> DX12 typically gives 10-20% more FPS. This is the scenario DX12 was built for.
GPU-bound (you are at high resolution/settings and the graphics card is the limit) -> the API barely matters; both feed the same GPU. Pick on stability.
Poorly optimized DX12 mode -> DX11 can be faster and smoother. A messy DX12 implementation can create the very CPU bottleneck DX12 is supposed to remove.

That last point is why you cannot just declare “DX12 is newer, so use DX12.” Newer is only better when the studio did the work. And since the whole question turns on whether your CPU is the limiter, it helps to know that first: the PC Bottleneck Calculator estimates whether your CPU or GPU is the bottleneck at your resolution.

DX12’s real weakness: shader-compilation stutter

If you have heard people complain about “DX12 stutter,” this is it. Because DX12 gives developers direct control of the graphics pipeline, the game is responsible for compiling shaders ahead of time. When a studio does not pre-compile them well, shaders get compiled on the fly during gameplay – and each one is a brief hitch. DX11’s driver handled more of this automatically behind the scenes, which is why some DX11 games feel smoother even when the average FPS is the same.

This is the single biggest reason to actually test both rather than trust the average frame rate: DX12 can show a higher average FPS while feeling worse, because the stutters live in the 1% lows, not the average.

When to use which

Situation	Pick
Modern 6+ core CPU, CPU-limited, good DX12 port	DX12
You want ray tracing / mesh shaders	DX12 (required)
The game’s DX12 mode stutters or crashes	DX11
Older CPU, or a thermally limited laptop	DX11 (often steadier)
GPU-bound at high resolution	Either – pick the steadier one

How to test it yourself (two minutes)

Do not trust a forum verdict for your hardware and your game. Test it:

In the game’s graphics/display settings, find the Graphics API / Renderer / DirectX version dropdown (some games use a -dx11 / -dx12 launch option instead). Switching usually needs a game restart.
Pick a demanding, repeatable scene – a busy area, not an empty menu.
Turn on a frame-time overlay (your GPU software’s overlay, or a tool that shows 1% lows and frame-time, not just average FPS).
Run the same scene on each API and compare the 1% lows and frame-time consistency. Keep whichever is steadier, even if its average FPS is a touch lower. Smooth beats a higher number that hitches.

A note on the CPU that drives this

Because DX12’s whole advantage is spreading work across cores, the API conversation is really a CPU conversation. A strong modern gaming CPU – lots of fast cores and large cache – is what lets DX12 pull ahead, and it is also what carries you in the CPU-bound games where the API matters most. That is a big part of why the $2,500 4K build is built around a Ryzen 7 7800X3D, and why the GPU reviews pair cards with CPUs that can keep them fed. If a specific game stutters under DX12, that is also worth checking against the anti-cheat and launch fixes before blaming the API – sometimes the “DX12 problem” is something else entirely.

The bottom line

DX12 is not automatically better than DX11 – it is better at one job: getting more frames out of a modern multi-core CPU when that CPU is the limit and the game was built properly. DX11 is the steadier, simpler path that still wins in messy DX12 ports and on older hardware. Ray tracing forces DX12. For everything else, switch between them in the settings, watch your 1% lows, and keep the one that feels smooth. The right API is the one your specific game and PC actually run best – and now you can prove which that is.

Sources

Hardware Times – difference between DirectX 11 and DirectX 12: https://hardwaretimes.com/what-is-the-difference-between-directx-11-and-directx-12/
Overclock.net – DX11 vs DX12 multi-thread performance (Ashes of the Singularity): https://www.overclock.net/threads/directx-11-vs-directx-12-multi-thread-performance-ashes-of-the-singularity.1584528/
Community analysis on DX12 CPU overhead and shader-compilation stutter (AnandTech, Beyond3D forums): https://forums.anandtech.com/threads/how-does-a-directx-11-game-has-a-lower-overhead-cpu-limited-scenario-than-dx12.2568366/

Easy Anti-Cheat Errors: The Complete Fix Guide (2026)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~11 min read · St. Louis County, MO

TL;DR · Fix Easy Anti-Cheat

Start here: run the game's own EasyAntiCheat_Setup.exe as administrator and click Repair Service. This fixes most "not installed" errors.
If it still fails: reinstall EAC with that same tool, verify game files, and run the game as administrator.
Windows 11 "untrusted system file" / won't launch: enable Secure Boot + TPM 2.0 (EAC now requires them), and check Memory Integrity.
The cause almost no guide mentions: Windows 11 Smart App Control can silently block an unsigned launcher or anti-cheat module. Confirm it first (Event Viewer), then disable it as a last resort -- it lowers security for your whole PC.
Never download a third-party "EAC fixer." Every real fix is a Windows setting or the official tool already inside your game.

Easy Anti-Cheat (EAC) runs underneath a huge share of online PC games – Star Citizen, Apex Legends, Fortnite, Lords of the Fallen, Elden Ring, and dozens more – and when it breaks, the game simply will not start. The errors come in a few flavors (“Easy Anti-Cheat is not installed,” “Easy Anti-Cheat failed to start,” “untrusted system file,” or a launcher that just bounces back to desktop), but they share a small set of real causes. This guide ranks the fixes by how often they actually work, and it covers one cause – Windows 11 Smart App Control – that I ran into on my own machine and that nearly every other guide misses.

The one rule before you start: fix the cause, not the symptom. Reinstalling a 100 GB game because a service failed to register is the slow, wrong move. Work down this list in order and stop at the one that applies to you.

What Easy Anti-Cheat actually is (and why it fails)

EAC is a kernel-level anti-cheat service that each game installs alongside itself. Because it runs at a low level and has to trust the code around it, it is unusually sensitive to four things: whether its own service is registered correctly, whether it has permission to run, whether Windows’ platform-security features (Secure Boot, TPM) are on, and whether anything on the system is blocking it from loading. Almost every EAC error traces back to one of those four. Knowing which one is the whole game.

The fixes, ranked by what actually works

1. Repair the Easy Anti-Cheat service (fixes most “not installed” errors)

EAC ships a small installer inside every game that uses it, and it has a one-click repair. This is the first thing to try and it resolves the majority of “not installed” / “failed to start” errors.

Open the game’s install folder. For Steam that is usually C:\Program Files (x86)\Steam\steamapps\common\[Game Name]; other launchers have their own path.
Find the EasyAntiCheat (or EasyAntiCheat_EOS) subfolder and open it.
Right-click EasyAntiCheat_Setup.exe and choose Run as administrator (accept the UAC prompt).
Pick your game from the dropdown, then click Repair Service.
Restart your PC and launch the game again.

If repair does not do it, run the same tool, choose Uninstall, let it finish, then run it again and choose Install. This rebuilds the service from scratch. (Driver Easy, Appuals)

2. Run the game (and the repair tool) as administrator

EAC needs to register and start a Windows service, which requires elevated rights. If it lacks them, you get a “not installed” or “failed to start” error even when the files are fine. Right-click the game’s launcher (or the EAC setup) and Run as administrator. To make it permanent, open the launcher’s Properties, go to Compatibility, and tick Run this program as an administrator.

3. Verify the game files

A single corrupted EAC file will break the service. Use your launcher’s repair: on Steam, right-click the game, Properties, Installed Files, Verify integrity of game files; other launchers have an equivalent “verify” or “scan.” This re-downloads only what is broken, not the whole game.

4. Turn on Secure Boot and TPM (the “untrusted system file” / Windows 11 cause)

Modern Easy Anti-Cheat enforces Secure Boot and TPM 2.0 as part of its “additional security requirements.” If Secure Boot is disabled, newer EAC titles can refuse to start or report an untrusted system file. (Easy Anti-Cheat additional security requirements)

Reboot into your BIOS/UEFI (usually Del or F2 at boot).
Under Boot or Security, set Secure Boot to Enabled, and confirm TPM (often labeled PTT on Intel or fTPM on AMD) is on.
Save and reboot.
If a game still complains, open Windows Security > Device security > Core isolation and try enabling Memory Integrity (note it can cost a little performance on some systems). (Microsoft Q&A)

A caution worth stating: enabling Secure Boot on a PC that was installed in Legacy/CSM mode can stop Windows from booting. If your install is older, confirm it is using UEFI/GPT before flipping Secure Boot on.

5. Update Windows, GPU drivers, and the Visual C++ runtimes

EAC leans on current platform components. Install pending Windows Updates, update your GPU driver, and install the latest Microsoft Visual C++ Redistributables (x64 and x86). Outdated runtimes are a quiet cause of “failed to start.”

6. Whitelist EAC in your antivirus

Because EAC injects at a low level, third-party antivirus sometimes quarantines or locks its files mid-launch. Add the game’s folder and EasyAntiCheat_Setup.exe to your antivirus exclusions (preferred), or pause real-time protection only long enough to test. Whitelisting beats fully disabling your antivirus.

7. The cause almost no guide covers: Windows 11 Smart App Control

This is the one I hit personally, on a clean Windows 11 install on my own 7800X3D / RTX 5080 build: the game would not launch, no fix above changed anything, and there was no useful error – because the thing blocking it was a Windows security feature, not the game.

Smart App Control (SAC) is a Windows 11 (22H2 and newer) feature that blocks apps it does not recognize or that are unsigned – system-wide, with no per-app allowlist. It is separate from Microsoft Defender. When SAC is enforced, it can silently block an unsigned game launcher or an anti-cheat component from loading, and the result looks exactly like a generic EAC or launch failure with no message pointing at the real cause.

It is a real but uncommon cause, which is why it belongs near the bottom of this list – but if every other fix has failed and you are on Windows 11, check it.

Confirm SAC is actually the cause first. Do not disable a security feature on a guess:

Look for a notification that reads “Smart App Control blocked an app,” or
Open Event Viewer > Applications and Services Logs > Microsoft > Windows, and check the CodeIntegrity / AppLocker logs around the time the game failed for a block on the launcher or EAC executable.

If, and only if, SAC is confirmed as the cause, you can turn it off:

Open Windows Security > App & browser control > Smart App Control settings.
If it reads On or Evaluation, set it to Off.
Restart and launch the game.

Two honest caveats you should know before you do this:

It lowers security for your whole PC, not just the game. SAC blocks unsigned and unknown software across the system, so turning it off removes that layer everywhere.
Historically, turning SAC off was a one-way door – re-enabling it required reinstalling Windows. An April 2026 Windows 11 update is changing this so you can re-enable SAC from Windows Security without a reinstall, but it is rolling out gradually and your PC may not have it yet. Treat disabling SAC as a deliberate choice, and re-enable it once your game’s anti-cheat is trusted.

Work the fixes in order -- stop at yours

Most common at the top; the security-lowering step is deliberately last

What not to do

Do not download a third-party “EAC fixer” or “anti-cheat repair” tool. Every real fix is either a Windows setting or the official EasyAntiCheat_Setup.exe already inside your game. A downloaded program that changes system or security settings is exactly the kind of unsigned software Windows SmartScreen and Smart App Control exist to block – and ironically, running one can trigger the very problem you are trying to fix.
Do not reinstall the whole game first. It is the slowest fix and rarely the right one; it only helps if file verification (step 3) finds damage it cannot repair.
Do not disable Smart App Control or your antivirus “just to see.” Confirm the cause first. Lowering a security layer should be a decision, not a shot in the dark.

Game-specific notes

EAC behaves the same across titles, but a few have their own quirks. Star Citizen is the one I see trip people up most, because its launcher is unsigned and its errors (like the generic “5007”) hide the real cause – it has its own ranked, log-first walkthrough here: Star Citizen Error 5007: read your log first. If you are building or upgrading a rig for EAC-heavy games, Secure Boot and TPM are now effectively mandatory, which is one more reason the modern AM5 build ships them on by default, and the GPU reviews cover the cards that actually carry these games.

The bottom line

Easy Anti-Cheat errors look scary but come from a short list of causes. Repair the service, give it admin rights, verify your files, and – on Windows 11 – make sure Secure Boot and TPM are on. If you have exhausted those and you are still stuck, check whether Smart App Control is silently blocking the launcher before you reach for anything drastic, and disable it only with eyes open. Fix the cause that applies to you, in order, and you will spend ten minutes on this instead of an evening.

Sources

Easy Anti-Cheat – additional security requirements (Secure Boot, TPM): https://www.easy.ac/support/articles/additional-security-requirements
Roberts Space Industries – Easy Anti-Cheat troubleshooting: https://support.robertsspaceindustries.com/hc/en-us/articles/4412276152343-Easy-Anti-Cheat-Troubleshooting
Microsoft Q&A – can’t play games that use anti-cheat (Secure Boot / Memory Integrity): https://learn.microsoft.com/en-us/answers/questions/3929849/i-cant-play-any-game-that-uses-anti-cheat
Driver Easy – “Easy Anti-Cheat is not installed” repair steps: https://www.drivereasy.com/knowledge/easy-anti-cheat-not-installed/
Appuals – Easy Anti-Cheat is not installed: https://appuals.com/easy-anti-cheat-is-not-installed/
Microsoft – Smart App Control overview: https://support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003

Karakeep vs Linkwarden: Which Self-Hosted Bookmark Manager (2026)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~10 min read · St. Louis County, MO

TL;DR · The one-line call

Karakeep (formerly Hoarder) = keep + organize + AI. Bookmark links, notes, images, PDFs, and videos; automatic AI tagging (OpenAI or local Ollama). Pick it to build an organized, searchable knowledge base.
Linkwarden = archive + preserve. Auto-saves a PDF and a screenshot of every page, so your bookmarks survive link rot. Pick it to keep a permanent, self-owned copy of what you save.
Both are AGPL-3.0, self-hostable with Docker, search via Meilisearch, and ship browser extensions + iOS/Android apps. You can't really go wrong; you're choosing a philosophy, not a winner.

Self-hosted bookmark managers all promise the same thing – “own your bookmarks” – but the two that homelabbers actually shortlist in 2026 are Karakeep and Linkwarden, and they answer a different question underneath. One wants to help you organize what you save. The other wants to guarantee it still exists in five years. That difference should drive your choice more than any feature checklist.

This is a researched comparison drawn from both projects’ documentation, GitHub repositories, and community write-ups, current as of June 2026 – not a paid review and not a claim of a months-long side-by-side deployment. Where a number matters (stars, RAM, services), it’s pulled from the source.

What each one actually is

Karakeep (github.com/karakeep-app/karakeep) is a “bookmark-everything” app: links, notes, images, PDFs, and videos, with AI-based automatic tagging and full-text search as the headline features. It was previously called Hoarder and rebranded to Karakeep. It’s an active, popular project – roughly 26.3k GitHub stars at the time of writing, about two years into development, released under AGPL-3.0.

Linkwarden is a self-hosted bookmark manager whose defining feature is archival: it automatically captures a PDF and a screenshot of every page you save, so the content survives even if the original URL dies. It’s the older of the two – around four years of development versus Karakeep’s two, roughly 18.8k stars, also AGPL-3.0. That ~1.9-year head start shows up as a polished, mature archive view and PWA.

So both are genuinely free, self-hostable, and well-supported. The fork in the road is what they optimize for.

The core difference: organizing vs archiving

This is the whole comparison in one sentence: Karakeep focuses on the keeping and organizing part; Linkwarden focuses heavily on the archiving part. Everything else follows from that.

If your problem is “I save hundreds of links and can never find anything,” Karakeep’s AI tagging and broad content support (notes, images, PDFs, video) are aimed straight at you. It behaves more like a personal, searchable knowledge base than a bookmark list.
If your problem is “the article I bookmarked last year is now a 404,” Linkwarden’s automatic per-page PDF + screenshot archive is the answer. You’re trading some organizational flash for a durable, self-owned copy of everything.

Plenty of people want both, and either tool will technically do both. But each is clearly better at its half, so match the tool to the problem that actually bothers you.

Which one fits your actual problem

Pick by the pain you have, not the feature list

Feature comparison

Dimension	Karakeep (formerly Hoarder)	Linkwarden
Primary focus	Keep + organize (knowledge base)	Archive + preserve (link rot)
Content types	Links, notes, images, PDFs, videos	Links (with full-page PDF + screenshot archive)
AI auto-tagging	Yes – OpenAI or local Ollama	Limited / not the focus
Full-page archival	Yes (headless Chrome)	Yes – the core feature, polished archive view
Search	Meilisearch (local, full-text)	Meilisearch (local, full-text)
Apps / extensions	Chrome, Firefox, iOS, Android	Browser extensions, mobile, polished PWA
License	AGPL-3.0	AGPL-3.0
Maturity	~2 years, ~26.3k stars	~4 years, ~18.8k stars (more mature)
Managed cloud option	Yes (optional)	Yes (optional)

The single most important row is AI auto-tagging with a local-LLM option. If you want hands-off organization without shipping your reading habits to OpenAI, Karakeep’s Ollama support is a real differentiator – you can run the entire tagging pipeline on your own hardware. Linkwarden’s standout row is full-page archival, which it does more maturely than anything else in the category.

Self-hosting footprint (the homelab part)

Neither is a one-container drop-in, so size your box accordingly.

Karakeep runs three services: the main web app, a headless Chrome instance (for archival and screenshots), and Meilisearch for search. In practice the core app sits around ~200MB RAM, Meilisearch ~100MB, and the Chromium crawler can spike to ~500MB while it processes a page – so a typical deployment is comfortable on a 2GB-RAM box, with at least ~1GB free recommended so Meilisearch has breathing room (Karakeep Docker docs).

Linkwarden’s standard Docker Compose brings up the app with PostgreSQL plus Meilisearch. Same ballpark – plan on a couple of gigabytes of RAM and a Docker host you already run.

Either fits fine on a mini PC or a small Proxmox LXC/VM. If you don’t already have a Docker host, our Docker Compose starter stack gets you to a clean base in an afternoon, and the best mini PCs for a homelab covers the hardware to run it on.

Which should you pick?

Choose Karakeep if:

You save a mix of things – links, notes, screenshots, PDFs – and want them organized, not just listed.
You want automatic tagging and are happy to point it at a local Ollama model to keep everything private.
You value faster, nicer first-party apps for day-to-day capture.

Choose Linkwarden if:

Your top priority is permanence – a self-owned PDF/screenshot of every page that survives link rot.
You want the more mature, battle-tested project with the most polished archive view.
You mostly save links (articles, references) rather than mixed media, and “find it later” matters less than “still have it later.”

If you genuinely can’t decide, default to Linkwarden for an archive you’ll trust in five years, or Karakeep for a living, AI-organized knowledge base you’ll actually browse. Both are AGPL-3.0 and Docker-native, so trying one and migrating later is a weekend, not a commitment.

Where these fit in a self-hosted stack

A bookmark manager is one of the highest-value, lowest-effort self-hosted apps you can run – it replaces a SaaS you’d otherwise rent, and your data never leaves your network. For the broader picture of which SaaS tools are genuinely worth self-hosting (and which aren’t), see self-hosted apps that replace SaaS, and if you’re weighing other head-to-head homelab choices, the Komodo vs Portainer vs Dockge breakdown uses the same “match the tool to your actual problem” approach.

One category note before you commit to either: both of these are bookmark managers, built to organize and preserve links at scale. If your real goal is reading — a clean reader view for articles you save on your phone and finish on the couch, the job Pocket did until it shut down — that is a neighbouring category with different tools, compared in self-hosted read-it-later apps.

The honest bottom line: in 2026 these are the two best self-hosted bookmark managers, they share a license and a search engine, and they barely compete on quality – they compete on intent. Decide whether you’re organizing or archiving, and the choice makes itself.

Star Citizen Error 5007: Read Your Log First (2026)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~10 min read · St. Louis County, MO

TL;DR · Stop guessing at 5007

5007 is not one problem. It is the RSI Launcher's generic "Datapatcher - Unknown error." The real cause is written in your log.log.
Read the log first (60 seconds): RSI logo → Settings → Application → Get Log → search for "Could not resolve host", "permission", or "verify".
Most common on a fresh install: an NVMe sector-size mismatch -- fixed with one reversible registry command (or install to a SATA drive).
Most common while updating: DNS ("could not resolve host") or low virtual memory.
Don't reinstall 100GB or disable Windows security on a guess. Use the tool below to find your fix.

If you have hit error 5007 in Star Citizen, the internet has probably already told you to “verify your files” or “reinstall the game.” Most of the time that is wrong, and it costs you an evening and a 100 GB re-download. Here is the honest version: 5007 is the RSI Launcher’s catch-all for a patch step that failed, the actual reason is sitting in a log file, and once you read that line, the fix is usually small and specific.

This guide does three things the 60-second fix videos do not: it tells you what 5007 really is, it shows you the one-minute log check that reveals your cause, and it ranks the real fixes – with a small tool to point you straight at yours.

What error 5007 actually is

In the RSI Launcher, the Datapatcher is the engine that downloads and applies game patches. When it fails for a reason it cannot classify, it reports 5007 – “Datapatcher - Unknown error.” That is the key word: unknown. It is an umbrella code, not a diagnosis.

You can see this in the codes around it, which RSI’s launcher does name:

5001 – Datapatcher: Fix Permissions (the launcher cannot write to the game folder)
5006 – Failed to verify a file (corrupted or incomplete data)
5015 – Network: could not resolve host builds.robertsspaceindustries.com (DNS/network)

So 5007 is “something in the patch pipeline broke and I cannot tell you what.” The same code can mean a storage problem on one PC, a DNS problem on another, and a low-memory problem on a third. That is exactly why a one-size fix does not exist – and why the first move is to read the log, not to start deleting things.

Step 0: the 60-second log check (do this first)

This is read-only, it cannot hurt anything, and it is the single most useful thing you can do.

Open the RSI Launcher.
Click the RSI logo in the top-left, then Settings.
Go to Application and click Get Log – it opens the folder containing log.log.
Open log.log in Notepad and press Ctrl+F to search for:
- “Could not resolve host” → a DNS / network problem (see fix B)
- “permission” or “access” → a permissions / install-path problem (fix D)
- “verify” → corrupted files (fix E)
While you are at it, open status.robertsspaceindustries.com – if RSI’s servers are down, 5007 is on their end and waiting is the fix.

Whatever phrase you find points you at the right fix below. If you are not sure, the tool here will walk you through it.

Find your 5007 fix

Pick what matches your situation. This tool only shows you the exact command or setting to run yourself -- it never changes anything on your PC.

The fixes, ranked

The tool above gives you the short version; here is the full detail for each, in rough order of how often they actually resolve 5007.

A. NVMe sector-size mismatch (top cause on fresh installs). Advanced-format NVMe drives present 4096-byte sectors that the Datapatcher can choke on. If the install fails on your NVMe but works on a SATA drive, force the OS to present 512-byte sectors with the registry command in the tool, restart, delete the failed partial install, and retry. It is reversible by deleting that value. If you would rather not touch the registry, install to a SATA SSD or hard drive instead.

B. DNS / “could not resolve host.” If log.log shows it cannot resolve builds.robertsspaceindustries.com, change your DNS to 1.1.1.1 (or 8.8.8.8), run ipconfig /flushdns in an admin prompt, and retry. A VPN set to a different country sometimes clears stubborn CDN-routing cases. This is the most common cause of update (not first-install) failures.

C. Virtual memory (pagefile). The patch needs large transient space; RAM-limited PCs run out. Raise the pagefile (a known-good value on 16 GB of RAM is 24576 MB initial / 49152 MB max) and keep well over 60 GB free, then retry. It is a standard, reversible Windows setting.

D. Install path, leftover files, and permissions. Confirm your library path, delete stale partial installs on other drives, run the launcher as administrator, and create the target folder manually if it is missing (this covers the 5001 “fix permissions” case too).

E. Verify files / clear cache (not a full reinstall). If the log says “verify,” use the launcher’s VERIFY, clear the launcher cache, or delete the USER folder. Avoid a full 100+ GB reinstall unless everything else has failed – it usually does not fix DNS- or storage-rooted 5007 anyway.

F. Antivirus and clock. Whitelist the launcher and game folder in third-party antivirus (or pause it briefly to test), disable VPN “web protection” features during the patch, and make sure your system clock is set automatically – a wrong clock breaks the secure connection to RSI’s servers.

G. Smart App Control (Windows 11, last resort). Only if you are on Windows 11, every fix above failed, and you have confirmed in Event Viewer that Smart App Control blocked the launcher or anti-cheat. Disabling it lowers security for your whole PC, so re-enable it afterward. This is the same Windows feature covered in depth in the Easy Anti-Cheat fix guide, because it blocks EAC the same way it blocks the RSI launcher.

My own 5007, and why this guide exists

I hit 5007 on a clean Windows 11 install on my own 7800X3D / RTX 5080 build. I did the obvious things first – verified, cleared cache, ran as admin – and none of it changed anything, because the launcher’s unsigned executable was being blocked by Smart App Control, and nothing in the 5007 message said so. The fix took thirty seconds once I knew the cause; finding the cause took the log. That is the whole lesson here: 5007 hides its reason, the reason is in the log, and the right fix is small once you read it. Most guides skip that and send you straight to a reinstall.

What not to do

Do not reinstall the whole game first. It is the slowest “fix” and rarely the right one for 5007.
Do not disable Windows security on a guess. Smart App Control is a real but uncommon cause; confirm it before you touch it.
Do not run a downloaded “Star Citizen fixer” tool. Everything you need is a Windows setting or a command you can read – nothing to install.

Where to go next

If your launch problem turns out to be the anti-cheat rather than the patcher, the cross-game Easy Anti-Cheat fix guide ranks those fixes the same way. For everything else Star Citizen – specs, settings, and performance – see the Star Citizen troubleshooting hub, and if the game launches fine but runs badly, the best settings for FPS guide covers which dials actually move the frame rate. And if your 5007 traced back to an undersized drive or too little RAM, that is no accident: the Star Citizen system requirements guide explains why RAM and a fast NVMe matter more than your GPU, and the 2026 RAM and SSD price reality covers how to buy them.

Sources

Roberts Space Industries – Error 2000 or 50XX (Datapatcher codes): https://support.robertsspaceindustries.com/hc/en-us/articles/22514899089431-Error-2000-or-50XX
Roberts Space Industries – Troubleshoot the RSI Launcher: https://support.robertsspaceindustries.com/hc/en-us/articles/360000161747-Troubleshoot-the-RSI-Launcher
RSI status (server-side outages): https://status.robertsspaceindustries.com
Microsoft – What is Smart App Control: https://support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003

Star Citizen System Requirements & Recommended Specs (2026)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~10 min read · St. Louis County, MO

TL;DR · What Star Citizen really needs

The official minimum lets it launch, not run well. 16GB RAM and a GTX 1060 will start the game; they will not give you a smooth one.
RAM is the #1 thing. The game uses 18-24GB in busy areas, so 32GB is the real 2026 minimum. With 16GB you swap to disk and stutter.
An NVMe SSD is the #2 thing. Star Citizen streams constantly; a slow drive causes missing textures and clipping, not just long loads.
It's more CPU/RAM/IO-bound than GPU-bound. A mid-range 8GB+ GPU with 32GB and an NVMe beats a top GPU with 16GB and a slow disk.
Target by resolution: 1080p = 8GB GPU; 1440p = 12GB; 4K = 16GB. Plus 32GB RAM and NVMe at every tier.

Most “Star Citizen system requirements” pages just copy the official spec sheet and move on. The problem is that the official sheet is misleading – not wrong, but it lists what gets the game to a menu, not what gets you a stable session in a hundred-player city. This guide gives you both: the real official numbers, and the honest 2026 reality of what actually decides whether Star Citizen runs well, which is mostly your RAM and your SSD – not your graphics card.

The official minimum requirements

These are the current, officially published minimums. Treat them as “the game will start,” not “the game will be smooth.”

Component	Official minimum
OS	Windows 10 64-bit (latest update)
CPU	Quad-core with AVX, AVX2 & FMA3 – Intel i7 Haswell (4th gen) or later, AMD Ryzen 5 1600 / Excavator or later
GPU	DirectX 11.1 / Vulkan 1.2 capable, 4GB VRAM (GTX 1060 / RX 580 class)
RAM	16GB
Storage	100GB+ free on an SSD (NTFS), plus room for the pagefile

The thing to understand: Star Citizen is in active development, its build keeps growing, and its real memory and storage behavior outpaces that 16GB / 100GB line. The official sheet even pairs with a “recommended” tier of Windows 11, an 8-core CPU, an 8GB+ DirectX 12 GPU, and 32GB of RAM – which is much closer to the truth.

Why the minimum lies: RAM is the real bottleneck

Here is the single most useful fact in this whole guide. In a busy landing zone or a populated server, the Star Citizen process alone commonly uses 18 to 24GB of RAM. If you only have 16GB installed, the game needs more memory than you have, so Windows pushes the overflow into the pagefile on your SSD – and that swapping is what produces the stutter and frame hitches people blame on their GPU. No graphics card fixes a memory problem.

Why 16GB isn't enough for Star Citizen

The game's real memory use vs what each kit gives you

Real-world memory use reported across Star Citizen community testing; 1 GB = the chart's horizontal unit.

Going from 16GB to 32GB is the highest-impact, best-value upgrade you can make for this game – and with the 2026 memory price spike, it is also the upgrade to plan for deliberately rather than overspend on. If you are buying RAM, our DDR5 buying guide covers what actually matters (speed, timings, two sticks vs four).

The #2 bottleneck: your SSD has to be fast

Star Citizen streams an enormous amount of data continuously as you fly between locations. A slow drive does not just make loads longer – it makes assets fail to arrive on time, which shows up as invisible terrain you fall through, missing or low-detail textures, doors that will not open, and general clipping. People often read those as “bugs” when they are really a storage-speed problem.

SSD is mandatory. The game will not behave on a mechanical hard drive.
NVMe is strongly recommended. A good NVMe drive roughly halves load times versus a SATA SSD and smooths the transitions between locations.
Budget 150GB+ free, and double that if you also run the PTU test universe alongside the live build. The install keeps growing.

If your drive is the weak link, that is also the most common root cause behind launch and patch failures – see the log-first Error 5007 guide, where an advanced-format NVMe is the top fix.

What you actually need in 2026, by resolution

This is the practical target. RAM and storage are constant across every tier because they are the real bottlenecks; the GPU is what scales with resolution.

Tier	CPU	GPU (VRAM)	RAM	Storage
1080p	Ryzen 5 7600 / Core i5-13400	RTX 4060 / RX 7600 (8GB)	32GB	1TB NVMe
1440p	Ryzen 7 7700X / Core i5-14600K	RTX 4070 / RX 7800 XT (12GB)	32GB	1-2TB NVMe
4K	Ryzen 7 7800X3D / Core i7-14700K	RTX 5080 / RX 9070 XT (16GB)	32GB (64GB optional)	2TB NVMe

A few honest notes on this table:

CPU: Star Citizen loves per-core speed and benefits from AMD’s 3D V-Cache. The Ryzen 7 7800X3D is the standout value chip for it – big cache, low power, excellent gaming performance. You do not need to jump to a 9800X3D for this game.
GPU: because the game is so often CPU/RAM/IO-limited, do not buy the most expensive card and pair it with weak memory and storage. VRAM is the spec to watch – 8GB at 1080p, 12GB at 1440p, 16GB at 4K. The GPU reviews cover the specific cards.
RAM: 32GB everywhere. 64GB only helps if you multitask heavily (streaming, lots of browser tabs) while playing.

Is your PC GPU-bound or something else?

The most common mistake is upgrading the graphics card to fix stutter that a memory or storage upgrade would actually cure. A quick way to think about it:

Stutter, hitching, long “loading” hangs, assets popping in late -> almost always RAM (you are swapping) or your SSD (too slow). Fix those first.
Low but steady frame rate that drops as you raise resolution/settings -> that is the GPU. See the Star Citizen best settings for FPS guide for the specific dials that move it. Lower settings or step up a card tier.
Poor performance only in crowded cities/servers -> partly the game’s server-side performance, and partly your CPU’s per-core speed. This is the one you cannot fully buy your way out of yet. If a game gives you the choice, the API matters here too – see DX12 vs DX11 for which one helps when the CPU is the limit.

For a worked example of a machine that handles 4K Star Citizen with real headroom – 7800X3D, RTX 5080, 32GB, NVMe – see the $2,500 4K build, which was specced around exactly these priorities.

My own setup, and what mattered

I run Star Citizen on a 7800X3D / RTX 5080 build with 32GB of RAM on an NVMe drive. The honest lesson from living with it: the GPU is the part I think about least. The things that decided whether a session was smooth were having enough RAM to never touch the pagefile and a fast enough SSD that assets streamed in before I reached them. If you only change one thing on an older machine, make it 32GB of RAM; if you can change two, make the second an NVMe SSD. The graphics card is where you spend what is left, sized to the resolution you actually play at.

Where to go next

It launches but errors out? Star Citizen Error 5007: read your log first.
It is the anti-cheat, not the patcher? Easy Anti-Cheat fix guide.
Buying the RAM and SSD now? Why RAM and SSD prices tripled in 2026 explains the timing.
Building the whole rig? The $2,500 7800X3D + RTX 5080 4K build.

Sources

Roberts Space Industries – Star Citizen Minimum System Requirements: https://support.robertsspaceindustries.com/hc/en-us/articles/360042417374-Star-Citizen-Minimum-System-Requirements
Star Citizen Logbook – system requirements (minimum + recommended tiers): https://citizen-logbook.com/en/requirements
Community testing on real-world RAM use and NVMe streaming behavior (StarCitizen.au, Doctor Memory): https://starcitizen.au/system-requirements/

Why RAM and SSD Prices Tripled in 2026 (and What to Do)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-28 · ~11 min read · St. Louis County, MO

TL;DR · The 2026 memory crunch

What happened: consumer DDR5 RAM and NVMe SSDs roughly tripled to quadrupled in price through 2026. A 32GB DDR5 kit that was ~$90 is now ~$375; a 2TB NVMe that was ~$130 is now $300-480.
Why: memory makers shifted wafer capacity to high-margin AI data-center memory (HBM + high-capacity modules). It's a deliberate reallocation, not a factory failure.
When it ends: prices peak Q3-Q4 2026; meaningful relief not before late 2026, and 2024 levels unlikely for 12-18 months. New capacity lands ~2027-2028.
What to do: if you need RAM/SSD, buy now (prices are still climbing). Right-size (32GB + a 1-2TB SSD for most), reuse what you own, and budget extra for those two parts. GPUs and CPUs are comparatively stable.

If you priced a PC build in 2024 and went back to your cart in 2026, the shock isn’t the graphics card. It’s the two parts nobody used to think about: the RAM and the SSD. They quietly became the most expensive surprise in a modern build, and the reason has almost nothing to do with PCs.

This is the explainer: the real numbers (cited, not vibes), the actual cause, the honest timeline, and a practical plan for building or upgrading during the crunch.

The numbers: how bad it actually got

RAM. On June 3, 2026, Tom’s Hardware’s daily RAM price tracker recorded the cheapest in-stock 32GB DDR5 kit in the US at $374.97 — a kit class that routinely sold for $80-120 a year earlier. High-capacity 64GB kits that sat near $150-200 for most of 2025 now commonly list at $600 or more. Across the board, consumer DRAM rose roughly 300-600% off its 2024-2025 lows, and DRAM contract prices jumped 55-60% in Q1 2026 alone.

SSDs. Storage followed, with a lag and then a vengeance. NAND flash pricing more than doubled in roughly six months, and by mid-2026 NAND had risen close to 4x off its lows. A 2TB NVMe drive that could be found for $120-150 a year ago now lists at $300-480; Samsung’s 990 Pro 2TB bottomed near $189 in 2025, while the newer 9100 Pro 2TB was listed around $478 in April 2026. Consumer SSDs broadly climbed 100-200% in a matter of months.

To put it plainly: in a typical mainstream build, the memory and the boot drive went from “rounding error” to the two parts that can cost more than the CPU.

Same parts, one year apart: 2025 vs mid-2026

Typical US street prices for identical components

Source: Tom's Hardware RAM and SSD price trackers, June 2026. 2025 figures are typical pre-shortage street prices.

Why is RAM so expensive? Your DIMM lost a bidding war to a server

The shortage is not a manufacturing breakdown. It’s a capacity reallocation, and the buyer who outbid you is an AI data center.

Memory makers have a finite amount of wafer capacity, and in 2026 they pointed it at the most profitable product they make: high-bandwidth memory (HBM) and high-capacity modules for AI accelerators. IDC and other analysts describe a deliberate shift of production away from consumer electronics toward AI memory, with AI workloads projected to absorb about 20% of global DRAM wafer capacity in 2026.

The economics are brutal and they explain everything:

A single HBM3E stack sells for roughly $60-100, versus about $5-10 for a comparable amount of conventional DDR5.
One gigabyte of HBM consumes roughly the wafer area of four gigabytes of standard DRAM.

So a wafer turned into HBM earns several times more than the same wafer turned into the DIMMs you buy — while also producing less total memory. Every gigabyte of AI memory is effectively several gigabytes of consumer memory that never gets made, at many times the margin. Faced with that math, no manufacturer rationally prioritizes a $90 desktop kit. NAND tells the same story for storage: AI data centers need vast, fast storage, and one major SSD-controller maker (Phison) confirmed NAND prices had more than doubled and that all of 2026’s production was already sold out.

That’s the uncomfortable part: this isn’t a glitch that gets patched next quarter. It’s the market working exactly as designed, against you.

One wafer, two products: why yours lost the bid

A memory maker's wafer capacity is fixed, so it goes to the more profitable product

Figures per IDC market analysis and industry reporting cited in this article.

When does it end?

Honestly: not soon, and not on a schedule anyone can promise. But the cited consensus is consistent enough to plan around.

Through 2026: prices stay elevated and keep climbing, with the peak expected in Q3-Q4 2026. TrendForce projected client SSD contract prices rising at least 40% quarter-over-quarter in Q1 2026, with tight supply persisting all year.
Relief: the earliest meaningful softening is late 2026, and a return toward 2024 price levels is widely called unlikely within the next 12-18 months.
Real capacity: new fabrication capacity is generally expected to come online around 2027-2028 — and even that only helps if AI memory demand moderates, which few analysts expect.

The blunt takeaway from the timeline: in 2026, “wait for prices to drop” is bad advice. Prices are far more likely to be higher in three months than lower.

The 2026 memory price timeline

Cited consensus across industry trackers

What to actually do (a builder’s plan)

Here’s the practical part, and it’s where most of the value is.

1. If you need RAM or an SSD, buy it now. This is the rare case where “buy the dip” is wrong — there is no dip coming in 2026. If a build or upgrade is already on your list, the memory and storage are the two parts to lock in first, before the Q3-Q4 peak.

2. Right-size, don’t over-buy. The instinct to “future-proof” with 64GB or a 4TB SSD is exactly the wrong move at these prices. For most people:

RAM: 32GB DDR5-6000 is the sweet spot for gaming and general use; 16GB is the floor if the budget is brutal (and even 16GB now runs ~$240). Going to 64GB roughly doubles an already-painful cost for capacity most desktops never touch. (How much RAM do you actually need in 2026? breaks it down by use case.)
SSD: a single 1-2TB NVMe covers the vast majority of builds. Buy the capacity you’ll use in the next year, not the next five.

3. Reuse what you already own. DDR5 and NVMe carry forward cleanly. If you’re upgrading a platform, pull the RAM and the boot drive from the old machine before you price new ones — a perfectly good DDR5 kit or 1TB NVMe you already paid 2024 prices for is the cheapest memory you will buy in 2026.

4. Spend the budget where the spike isn’t. GPUs, CPUs, and motherboards have been comparatively stable through the memory crunch. That means the RAM and SSD are the line items distorting your build budget — so cut elsewhere only if you must, and treat memory/storage as the fixed cost they’ve become. Our $1,000-class budget AM5 build was priced around this shortage and shows how much the memory line alone moves the total.

5. Model the running cost, not just the sticker. If you’re building a homelab or always-on box, the parts you keep for years cost more than their purchase price. Size the rest of the system honestly and run the numbers with the Power & Cost Calculator so the shortage doesn’t push you into an oversized, power-hungry box you’ll pay for monthly.

For the deeper RAM-specific breakdown — speeds, timings, and what actually matters when you do buy — see the DDR5 RAM buying guide, which now carries a dated note reflecting these 2026 prices.

The bottom line

The 2026 memory crunch is real, it’s cited, and it’s structural: your DDR5 kit and your NVMe drive lost a bidding war to AI data centers that pay several times more for the same silicon. Prices were still climbing through mid-2026 and are expected to peak before the year is out, with no return to 2024 levels on the near horizon.

So the move isn’t to panic and it isn’t to wait. It’s to buy what you need now, buy exactly as much as you’ll use, reuse what you own, and put the rest of the budget where the spike isn’t. Do that, and the most expensive surprise in a 2026 build becomes a line item you planned for instead of one that blows up your cart.

Xbox Controller Not Connecting to PC? The Fix Ladder (2026)

LK Wood IV — Sun, 28 Jun 2026 00:00:00 -0500

TL;DR · Fix an Xbox controller on PC

Start wired. Plug in a known-good USB-C cable. If it works wired, the controller and the game are fine and the problem is your wireless path.
Check if your controller even has Bluetooth. Only newer models do -- the giveaway is whether the plastic around the Xbox button is part of the faceplate (has Bluetooth) or the top by the bumpers (no Bluetooth).
One Bluetooth controller at a time. Windows only allows a single Bluetooth game controller. For more, use USB or the Xbox Wireless Adapter for Windows.
Update firmware in the Xbox Accessories app (over USB or the adapter -- it will not see a Bluetooth-connected pad), then reinstall the driver in Device Manager.
Then the basics: fresh batteries, move off other 2.4 GHz gear, get closer to the PC.

An Xbox controller is the default gamepad for Windows – Steam, the Xbox app, and almost every controller-friendly game expect it – so when it will not connect, it stops play cold. The frustrating part is that “not connecting” covers several very different problems: a controller that has no Bluetooth radio at all, a Windows limit you have never heard of, dead batteries, stale firmware, or a driver that needs rebuilding. This guide ranks the fixes by what actually clears the most cases, and it is honest about the one thing most guides skip: a lot of Xbox controllers simply cannot do Bluetooth, and Windows only lets you run one Bluetooth pad at a time anyway.

The rule before you start is the same one I use for every connection problem: confirm what works before you change what does not. A USB cable rules out half the possible causes in thirty seconds, so that is rung one. (If Windows does not recognize the controller over USB at all – or throws a generic “USB device not recognized” – that is a separate host-side problem; work the USB device not recognized fixes first.)

How an Xbox controller talks to a PC

There are exactly three supported ways to connect an Xbox controller to a Windows device: a USB cable, the Xbox Wireless Adapter for Windows, or Bluetooth on controllers that support it. (Xbox Support – connect to PC) Each path has different requirements, and most “won’t connect” problems are really “I picked a path my controller or my PC can’t do.” Knowing which of the three you are on tells you which fixes even apply.

The fixes, ranked by what actually works

1. Connect with a USB-C cable first (rules out everything wireless)

A wired connection skips radio entirely, so it is both the fastest fix and the best diagnostic. Plug a known-good USB-C cable (data-capable, not a charge-only cable) into the back of the controller and into your PC. (Xbox Support) Windows installs the controller driver automatically and it should work in seconds.

What this tells you: if the controller works wired, the controller, the cable port, the game, and Windows are all fine – your problem is specifically the wireless path, and you can jump to the wireless rungs below. If it does not work even wired, suspect the cable first (swap it), then the USB port, then move on to the driver reinstall in rung 5.

2. Bluetooth: know your model and the one-controller limit

Bluetooth is where most people get stuck, for two reasons almost no guide states plainly.

First: only newer Xbox controllers have Bluetooth. You can identify yours by looking at the plastic around the Xbox (guide) button. On Bluetooth-capable controllers, that plastic is part of the faceplate of the controller. On older controllers without Bluetooth, the plastic around the Xbox button is part of the top of the controller, where the bumpers are. (Xbox Support – set up Bluetooth) If yours is the older style, no amount of pairing will work – skip to rung 3 (the wireless adapter) or stay wired.

Second: Windows only allows one Bluetooth game controller at a time. (Microsoft Q&A) If you already have one Bluetooth pad bound and try to add a second, it appears to pair but never registers in-game. This is a Windows limitation, not a broken controller. For more than one wireless controller, you need USB cables or the Xbox Wireless Adapter.

If your controller does have Bluetooth and you are within the limit, pair it like any Bluetooth device:

Hold the Xbox button to turn the controller on, then press and hold the small Pair button on the top until the Xbox button flashes quickly.
On the PC, open Settings > Bluetooth & devices > Add device > Bluetooth.
Select Xbox Wireless Controller from the list and let it connect. (Xbox Support)

If the controller is also paired to an Xbox console, it can fight over which device it joins – turn the console off, or unpair the controller there, while you set up the PC.

3. Use the Xbox Wireless Adapter for older controllers (or multiple pads)

If your controller has no Bluetooth, or you want several controllers connected wirelessly, the Xbox Wireless Adapter for Windows is the answer. It is a small USB dongle that uses Xbox’s own wireless protocol instead of Bluetooth, works on Windows 10 and 11, and supports up to eight controllers at once. (Xbox Support – adapter setup)

Plug the adapter into a USB port (front-panel or a short extension can help line-of-sight).
Press the button on the adapter until its light flashes.
Turn the controller on, hold its Pair button until the Xbox button flashes, and the two will bind. (Xbox Support)

This path sidesteps the Bluetooth single-controller limit entirely, which is why it is the right call for couch co-op.

4. Update the controller firmware (fixes flaky wireless)

Stale controller firmware is a genuine cause of dropped and refused wireless connections. Update it in the Xbox Accessories app (free in the Microsoft Store): open the app, connect the controller with a USB-C cable or the Xbox Wireless Adapter, and apply any update it offers. (Xbox Support – update controller)

One honest catch that trips people up: the Xbox Accessories app will not detect a controller connected over Bluetooth. (Xbox Support) So even though your goal is to fix Bluetooth, you have to connect by cable to do the update. Plug in, update, unplug, then try pairing again.

5. Reinstall the controller driver in Device Manager

If Windows recognizes the controller but it behaves badly – shows up with an error, or refuses to register inputs – rebuilding its driver often clears it. Microsoft’s own guidance is to unplug the device first, because Windows will rediscover it and reinstall the driver automatically. (Microsoft Learn – uninstall via Device Manager)

Open Device Manager (search for it from the Start menu).
Expand the node for the controller (look under Xbox Peripherals, Human Interface Devices, or Bluetooth), right-click it, and choose Uninstall device.
If offered, you can tick Delete the driver software for this device to remove the package too. (Microsoft Learn)
Unplug and replug the controller (or reboot). Windows reinstalls a clean driver. (Microsoft Learn)

6. Battery and interference basics (do not skip these)

These are last on the list only because the rungs above fix more cases – but a dead battery or a noisy 2.4 GHz environment will defeat every other step.

Fresh power. Replace the AA batteries or fully charge the rechargeable pack. A controller low on power often pairs and then drops.
Reduce 2.4 GHz interference. Bluetooth and the Xbox wireless adapter share the crowded 2.4 GHz band with Wi-Fi, USB 3.0 devices, and wireless mice. If your Wi-Fi keeps dropping at the same times, that band is congested network-wide and worth fixing at the router – moving other devices to 5 GHz frees up airtime for the controller too. Move the controller and adapter away from those, and get closer to the PC.
Mind the range and line of sight. A metal case or a desk between you and the PC weakens the signal. A short USB extension that brings the adapter (or a Bluetooth dongle) onto the desk often fixes “connects then disconnects.”

Work the fixes in order -- stop at yours

Wired first (it diagnoses everything); the basics are last because the rungs above fix more cases

What not to do

Do not assume your controller has Bluetooth. Plenty of perfectly good Xbox One pads never had it. Check the plastic around the Xbox button before you spend an hour fighting a pairing that was never possible. (Xbox Support)
Do not try to run two Bluetooth controllers. Windows allows one. (Microsoft Q&A) The second one will look connected and do nothing in-game – use USB or the wireless adapter for the others.
Do not download a third-party “controller driver” or “fixer.” The driver Windows installs on its own is the correct one, and a downloaded driver utility is exactly the kind of unsigned software that causes more problems than it solves. Reinstall the in-box driver through Device Manager instead.
Do not skip the firmware update because pairing “should” work. Outdated firmware is a quiet cause of wireless drops, and the fix is two minutes over a cable. (Xbox Support)

Where this fits

A controller that will not connect is a peripheral problem, but the same habits carry over to the rest of PC gaming troubleshooting on this site: confirm what works, identify your exact cause, then apply the one fix that matches. If the peripheral acting up is a keyboard rather than a pad, the keyboard-not-working walkthrough sorts the dead-vs-wrong-input symptoms the same way. If your issue is a game that will not launch rather than a controller that will not pair, the Easy Anti-Cheat fix guide uses the same ranked approach for launcher and anti-cheat errors, and the rest of the gaming section covers driver crashes, DX12 stutter, and game-specific fixes. If you are putting a new rig together, every machine in our build guides has the USB-C ports and Bluetooth that make all three connection paths available out of the box.

The bottom line

“Xbox controller not connecting to PC” almost always comes down to picking the wrong connection path for your specific controller. Go wired first to prove the controller works, then sort the wireless side: confirm your model actually has Bluetooth, respect the one-Bluetooth-controller limit, and reach for the Xbox Wireless Adapter when Bluetooth is not an option. Update the firmware, rebuild the driver if Windows is confused, and rule out dead batteries and 2.4 GHz noise. Work the list in order and you will have the pad in your hands in a few minutes instead of an evening.

Sources

Xbox Support – How do I connect my Xbox controller to PC? (USB, adapter, Bluetooth): https://support.xbox.com/en-US/help/hardware-network/controller/connect-xbox-wireless-controller-to-pc
Xbox Support – Set up Bluetooth on your Xbox Wireless Controller (model identification): https://support.xbox.com/en-US/help/hardware-network/accessories/connect-and-troubleshoot-xbox-one-bluetooth-issues
Microsoft Q&A – Windows multi-controller Bluetooth support (one controller at a time): https://learn.microsoft.com/en-us/answers/questions/4301395/windows-multi-controller-support-bluetooth
Xbox Support – Set up the Xbox Wireless Adapter for Windows (up to 8 controllers): https://support.xbox.com/en-US/help/hardware-network/accessories/xbox-wireless-adapter-for-windows-setup
Xbox Support – Update your Xbox Wireless Controller (Xbox Accessories app, no Bluetooth detection): https://support.xbox.com/en-US/help/hardware-network/controller/update-xbox-wireless-controller
Microsoft Learn – Using Device Manager to uninstall devices and driver packages: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages

How to Overclock Your Monitor (More Hz Safely, 2026)

LK Wood IV — Sat, 27 Jun 2026 00:00:00 -0500

TL;DR · Overclock your monitor safely

Pick one tool: NVIDIA Control Panel (Create Custom Resolution), AMD Adrenalin (Custom Resolution), or CRU for any GPU including Intel.
Go up in small steps -- a 60Hz panel often reaches 70-75Hz, but it is panel-dependent and no one can promise a number.
The mandatory step: run the TestUFO frame-skipping test. A monitor will happily report a higher Hz while silently dropping frames -- which is worse than stock.
You cannot beat physics: your panel and your cable/port bandwidth set a hard ceiling. DisplayPort 1.4 carries ~25.92 Gbps; HDMI 2.0 ~18 Gbps.
It is reversible. The worst common failure is a black screen, fixed by reverting the setting or booting into safe mode.

Overclocking a monitor means asking it to refresh faster than its rated number – pushing a 60Hz panel to 75Hz, or a 144Hz panel to 165Hz. It works because manufacturers rate panels conservatively, so there is often a little unlabeled headroom on top. The catch is that “often” is not “always,” and a monitor that accepts a higher rate is not the same as a monitor that delivers it. This guide gives you the three ways to do it and the one test that separates a real overclock from a fake one.

First, the ceiling you cannot move

Before you change anything, understand what you are working against, because it explains every failure you will hit. Your maximum refresh rate is capped by the lower of two limits.

The first is the panel itself – the physical electronics that drive the pixels. This is the limit you are probing when you overclock, and it varies unit to unit.

The second is bandwidth: how much data your cable and port can carry. A refresh rate is just frames per second, and every frame is a fixed pile of data (pixels x color depth). Push more frames per second through the same pipe and you need more bandwidth. The pipe has a published ceiling:

DisplayPort 1.4 (HBR3) runs at 32.4 Gbps of raw link rate, which delivers about 25.92 Gbps of usable video data after encoding overhead, per the DisplayPort specification.
DisplayPort 2.1 raises that sharply with its UHBR modes – UHBR 10 at 40 Gbps, UHBR 13.5 at 54 Gbps, and UHBR 20 at 80 Gbps of raw link rate, again per the spec.
HDMI 2.0 carries up to 18 Gbps, and HDMI 2.1 raises the ceiling to 48 Gbps, a spec set by the HDMI Forum.

Why this matters in practice: if you hit a flat wall where the monitor simply rejects anything above a certain rate no matter how gently you climb, you are probably bandwidth-limited, not panel-limited. NVIDIA’s own documentation notes the refresh rate is bounded by the display’s scan capability at the current resolution. No software trick beats a hardware pipe. The fix is a better cable or a higher-spec port – not a registry edit.

Path 1: NVIDIA Control Panel

If you have a GeForce card, the built-in tool is the easiest starting point and it has its own validation step built in.

Right-click the desktop and open the NVIDIA Control Panel.
Under Display, click Change resolution.
Click the Customize button, then check Enable resolutions not exposed by the display, then click Create Custom Resolution.
Leave the resolution at your native value and raise only the Refresh rate (Hz) field by a small amount – say from 60 to 65.
Click Test. NVIDIA documents that the panel will test the new mode and, if the display accepts it, ask you to confirm before saving.

If the screen goes black, do nothing – the test reverts automatically after a few seconds. If it holds and looks clean, confirm to save, then climb again in small steps until a rate fails. Then drop back to the last good one. Do not trust it yet; you still have to run the frame-skip test below.

Path 2: AMD Software (Adrenalin Edition)

The Radeon equivalent lives inside AMD’s driver suite and follows the same logic.

Open AMD Software: Adrenalin Edition and type Custom into the search box, then open the Custom Resolution result.
Click Create New. The profile opens pre-filled with your current settings.
Raise the refresh-rate field by a small increment, leaving resolution and color depth alone, then click Create.
AMD checks the new mode for compatibility, and the support article notes the screen may go momentarily blank during this step – that is normal.

As with NVIDIA, if the display refuses the mode you will see a blank screen that recovers on its own. Keep the highest rate that applies cleanly, then go verify it.

Path 3: CRU (Custom Resolution Utility) – any GPU

Custom Resolution Utility, written by ToastyX, is the tool to reach for when the vendor utility refuses a mode, when you want finer control over timing parameters, or when you are on Intel graphics. It is more capable because it works at a lower level: rather than asking the driver for a custom mode, CRU writes a software EDID override into the registry – effectively rewriting the table of resolutions your monitor advertises to Windows. It changes no hardware.

That power is also why CRU demands more respect. Because it overrides what the system believes the monitor can do, a bad entry can leave you with no usable picture until you undo it. So do two things before you start, both straight from the tool’s own documentation:

Know how to boot into safe mode (via a Windows recovery drive, or by holding the power button during boot to reach Troubleshoot > Advanced options > Startup Settings).
Know that reset-all.exe (shipped with CRU) wipes every override and restores defaults, and it can be run from safe mode if the screen is unusable.

The workflow itself:

Run CRU.exe (accept the UAC prompt – it needs registry access).
Pick your display from the dropdown.
Under Detailed resolutions, click Add, set your native resolution, and enter the higher refresh rate.
Click OK, then run the included restart.exe to restart the graphics driver and apply the change. CRU requires this restart step to take effect.

If the screen comes back at the new rate, good. If it does not, restart.exe usually recovers on its own after a few seconds; if not, safe mode plus reset-all.exe is your reset button.

The mandatory step everyone skips: TestUFO frame-skip check

Here is the trap that makes most “I overclocked to 75Hz” claims meaningless. A monitor will frequently accept a higher refresh rate, report it proudly in Windows display settings, and then quietly skip frames – displaying, say, only 60 unique frames inside a 75Hz cycle. You get the higher number with none of the smoothness, and in some cases worse pacing than stock. The reported Hz is a promise the panel did not keep.

The only way to catch this is to look at actual frames, and the standard tool is the free TestUFO Frame Skipping Checker from Blur Busters. It scrolls a row of numbered squares across the screen at your refresh rate. You photograph that motion with a phone camera set to a long exposure – around 1/10 second or longer – and inspect the result:

A clean run shows an unbroken sequence of squares with no gaps. Per the Blur Busters method, a ~200ms exposure on a 144Hz display should capture roughly 28 successive squares.
Gaps in the sequence mean frame skipping. Any gap, even one, means the overclock is fake at that rate.

Close other apps and browser tabs before testing, and dim screen brightness so the camera can use a longer exposure. If your overclock skips, step the rate back down and retest until you find the highest rate that captures zero gaps. That rate – not the highest one the monitor accepted – is your real overclock.

This is the entire point of the exercise. An overclock that drops frames is worse than useless; a verified, gap-free overclock is free smoothness. The test is what tells them apart.

Realistic expectations

Numbers vary so much that anyone quoting you a guaranteed figure is guessing. A 60Hz panel commonly lands somewhere in the 70-75Hz range, and many go no higher; a handful reach further. Two of the same model can disagree because of normal manufacturing tolerances. So the honest framing is a method, not a number: climb in small steps, run the frame-skip test at each one, and keep the best rate that passes clean. Whatever you get is a bonus.

A few practical notes worth keeping in mind. Higher-refresh OLEDs and TVs-as-monitors behave differently from cheap LCD panels – if you are running something like the Aorus FO48U or a desktop LCD covered in our 27-to-32-inch monitor guide, the same step-and-test method applies, but the bandwidth ceiling bites sooner at 4K because each frame is far larger. And remember that more frames only help if your PC can produce them – a smooth overclock pairs naturally with the frame-rate fundamentals we cover in DX12 vs DX11.

Overclock in small steps, verify with TestUFO every single time, and never trust the number the monitor reports over the frames your camera sees.

Resizable BAR / Smart Access Memory: On or Off? (2026)

LK Wood IV — Fri, 26 Jun 2026 00:00:00 -0500

Verdict · Resizable BAR / SAM

Turn it ON on any modern build: GeForce RTX 30-series or newer, Radeon RX 6000-series or newer, on a UEFI install.
What it does: lets the CPU map your GPU's entire VRAM at once instead of through a small 256 MB window.
Honest payoff: a few percent in some games, no change in most, a small number of older titles regress. NVIDIA and AMD both default it on.
How: in BIOS enable Above 4G Decoding + Re-Size BAR Support, with CSM disabled (UEFI/GPT required). Update BIOS and driver first.
One real risk: disabling CSM on an old Legacy/MBR Windows install can stop it booting. Confirm you are on UEFI/GPT before you touch it.

Resizable BAR (ReBAR), which AMD markets as Smart Access Memory (SAM), is one of those BIOS toggles that gets talked about like a secret performance cheat. It is not. It is a small, legitimate, mostly-free improvement that you should enable on a modern system and then stop thinking about. This guide explains what it actually changes at the hardware level, gives you the honest performance picture from primary sources, and walks the exact BIOS steps to turn it on without breaking your boot.

What Resizable BAR actually is

A “BAR” is a Base Address Register, the PCI Express mechanism that maps a slice of a device’s memory into the CPU’s address space so the processor can read and write it. Historically, a graphics card only exposed a small portion of its memory this way. As Microsoft’s own driver documentation puts it, “discrete GPUs usually claim a 256 MB I/O region for their frame buffers” for “compatibility with 32-bit operating systems.” (Microsoft Learn)

That 256 MB window is the whole story. Your card might have 12 or 16 GB of VRAM, but the CPU could only “see” a 256 MB slice of it at any instant. To touch a different region, the system had to keep re-pointing that little window around the framebuffer while the GPU worked. It is a holdover from the 32-bit era that survived long into 64-bit computing.

Resizable BAR removes the limit. It is a capability defined in the PCI Express specification by PCI-SIG, and on a card that supports it, Microsoft says “Windows renegotiates the size of a GPU’s BAR after firmware initialization,” after which “the GPU BAR is resized to its maximum size to expose the entire VRAM of the discrete GPU.” The driver then presents “a single CPUVisible memory segment” the CPU can address directly. (Microsoft Learn)

In plain terms: the CPU can now reach all of the GPU’s memory in one continuous mapping instead of peeking through a 256 MB porthole. When a game streams large assets, that can mean fewer round trips and better-fed transfers, which is where the occasional frame-rate gain comes from.

Resizable BAR and Smart Access Memory are the same feature. ReBAR is the vendor-neutral PCI-SIG name; SAM is AMD’s brand for its version. NVIDIA and Intel use the generic term. The BIOS settings are identical regardless of whose GPU you run.

The honest performance picture

Here is the part the “free FPS” headlines skip. The gains are real but small, and they are not universal.

NVIDIA is refreshingly direct about this in its own announcement. The company states: “In our testing, we’ve found some titles benefit from a few percent, up to 12%. However, there are also titles that see a decrease in performance.” (NVIDIA) That is the whole shape of it from the vendor itself: some up, most flat, a few down.

This is exactly why NVIDIA does not just switch it on for everything. It “pre-tests titles and uses game profiles to enable Resizable BAR only when it has a positive performance impact,” so that “you won’t have to worry about bugs or performance decreases.” (NVIDIA) The feature is enabled per-game on the driver side, not blindly across your whole library.

AMD set higher expectations at launch, claiming SAM with RDNA 2 cards could deliver roughly 5 to 15 percent depending on the game. Independent testing landed lower. PCWorld’s explainer, written by Whitson Gordon, notes that while “AMD promises up to 16 percent” and “NVIDIA claims up to 12 percent,” their own testing showed “uplifts between 2 and 8 percent,” and warns plainly that “results can vary by game, resolution, and the hardware you’re using” and that “in some cases, Resizable BAR can actually decrease performance.” That piece also points to Hardware Unboxed finding measurable performance penalties in a few of NVIDIA’s own supported titles. (PCWorld)

So the verified verdict is consistent across vendor and independent sources: enable it, expect a few percent in the games that respond, expect nothing in most, and accept that a small number of older or lighter titles tick slightly down. Both NVIDIA and AMD ship it on by default on supported cards, which is the clearest signal of where the trade-off settles.

256 MB window vs. full-VRAM mapping

Resizable BAR lets the CPU address all of the GPU's memory at once

How to enable Resizable BAR / Smart Access Memory

Do the prep first, because most “ReBAR won’t turn on” problems are stale firmware.

Update your motherboard BIOS to the latest version from your board vendor, and update your GPU driver. ASUS notes that working Resize BAR needs “motherboard BIOS, graphics card VBIOS and driver support” all current. (ASUS Support) Older RTX 30 cards may also need a one-time VBIOS update via NVIDIA’s firmware tool.
Confirm you are on UEFI/GPT. Press Win+R, type msinfo32, and check that BIOS Mode reads UEFI. If it says Legacy, your install is MBR and the next step can stop it booting. Convert to GPT first (or do not proceed).
Enter BIOS (usually Del or F2 at boot).
Disable CSM. ASUS states outright that the “Launch CSM option must set to Disabled to support Resize BAR.” (ASUS Support) It typically lives under a CSM (Compatibility Support Module) submenu.
Enable the two PCI settings. Under PCI Subsystem Settings (the wording varies by board), set Above 4G Decoding to Enabled and Re-Size BAR Support to Enabled or Auto. ASUS’s own walkthrough places both there and calls for Above 4G Decoding enabled with Re-Size BAR Support set accordingly. (ASUS Edge Up)
Save (F10) and reboot.
Verify. On NVIDIA, open the NVIDIA Control Panel, go to System Information, and look for Resizable BAR: Yes. On AMD, open AMD Software and check that Smart Access Memory reads enabled.

If the Above 4G Decoding option is greyed out or Re-Size BAR refuses to enable, the cause is almost always one of the prep items: CSM still on, a Legacy/MBR install, or an out-of-date BIOS/VBIOS.

Who should leave it off

The honest exceptions are narrow. If you are on an older system that NVIDIA, AMD, or Intel never qualified for Resizable BAR, leave it alone; forcing it on unsupported hardware is a community-mod path, not a supported one. And if your Windows install is Legacy/MBR and you are not ready to convert it to GPT, do not disable CSM just to chase a couple of percent. The downside risk (an install that will not boot) badly outweighs the upside.

For everyone on a current GPU and a UEFI install, there is no good reason to keep it off. If your real question is whether your CPU and GPU are well matched in the first place, that is a different and more impactful tuning question. Our PC bottleneck calculator shows where the actual limiter sits at your resolution, which matters far more than a BAR toggle.

Where this fits with your other settings

Resizable BAR is one of a small cluster of platform-level toggles worth getting right once. Hardware-Accelerated GPU Scheduling (HAGS) is the other big one, and like ReBAR it helps in some scenarios and is neutral in most, so the same “enable it, verify, move on” mindset applies. If you are also chasing down launch or anti-cheat failures while you are in BIOS, our Easy Anti-Cheat fix guide covers the Secure Boot and TPM settings that newer games now require. A modern build like our 7800X3D / RTX 5080 reference rig ships with Resizable BAR available out of the box, and our GPU reviews cover the cards that support it.

The bottom line

Resizable BAR and Smart Access Memory do exactly one thing: they let your CPU map the GPU’s full memory at once instead of through a 256 MB porthole. The verified payoff is a few percent in some games, nothing in most, and a slight dip in a small handful. That is a good trade, which is why both major GPU vendors enable it by default. Update your BIOS and driver, confirm you are on UEFI/GPT, switch on Above 4G Decoding and Re-Size BAR Support with CSM off, verify it in your control panel, and leave it on. Then spend your tuning energy on the things that actually move frame rates more.

Sources

Microsoft Learn – System and Driver Support for Resizable BAR (256 MB region, full-VRAM CPUVisible segment): https://learn.microsoft.com/en-us/windows-hardware/drivers/display/resizable-bar-support
NVIDIA – GeForce RTX 30 Series Performance Accelerates With Resizable BAR Support (per-game profiles; few percent up to 12%, some titles decrease): https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/
ASUS Support – How to Enable Resize BAR (CSM must be disabled; BIOS/VBIOS/driver all current): https://www.asus.com/us/support/faq/1046107/
ASUS Edge Up – Guide: How to enable Resizable BAR on your ASUS-powered gaming PC (Above 4G Decoding + Re-Size BAR Support, UEFI/GPT): https://edgeup.asus.com/2021/guide-how-to-enable-resizable-bar-on-your-asus-powered-gaming-pc/
PCWorld (Whitson Gordon) – Resizable BAR explained (2-8% measured uplift, game-dependent, can decrease performance; cites Hardware Unboxed penalties): https://www.pcworld.com/article/394720/faster-gaming-frame-rates-for-free-resizable-bar-explained.html

Hardware-Accelerated GPU Scheduling: On or Off? (2026)

LK Wood IV — Thu, 25 Jun 2026 00:00:00 -0500

TL;DR · HAGS on or off

Modern GPU (RTX 30/40/50, RX 6000+): turn it ON. Current drivers assume it, and it is the default on Windows 11.
It is required for frame generation. NVIDIA DLSS Frame Generation will not activate with HAGS off, and AMD's frame-gen path expects it on supported hardware.
FPS impact is usually neutral to slightly positive -- the real win is less CPU scheduling overhead and lower latency in some titles, not a big frame-rate jump.
Turn it OFF only if you see a regression: documented cases include micro-stutter, high DPC latency, and some VR hitching that clear up when it is disabled.
The toggle: Settings > System > Display > Graphics > Change default graphics settings. Restart after.

The short answer for almost everyone reading this: if you are on a modern graphics card, turn hardware-accelerated GPU scheduling on and leave it on. It is the default on Windows 11 for a reason, and it is a hard requirement for the frame generation features people most want from RTX 40/50 and recent Radeon cards. The longer answer – why it exists, what it changes, and the handful of real cases where off still wins – is what decides whether you ever need to touch the switch.

What hardware-accelerated GPU scheduling actually changes

“HAGS” sounds like a performance toggle, but it is really a change to who schedules work onto your GPU. Microsoft introduced it as part of the Windows graphics driver model, and the mechanism is specific.

Before HAGS, Windows scheduled GPU work using a high-priority thread running on your CPU. That thread collected render commands, batched them, and fed them to the GPU. With hardware-accelerated GPU scheduling enabled, Windows “can now offload most of GPU scheduling to a dedicated GPU-based scheduling processor,” as Microsoft’s DirectX team describes it. The GPU’s own scheduling processor takes over the high-frequency work – quanta management and context switching between GPU engines – using its own memory (VRAM) to manage those queues in batches. Windows still decides which application gets priority; only the moment-to-moment scheduling moves down onto the silicon.

Microsoft is blunt that this is “a significant and fundamental change to the driver model,” which is exactly why it shipped as an opt-in feature that was disabled by default, and why it needs a WDDM 2.7 or newer driver plus a GPU built to support it. It is not a tweak layered on top of the old path; it is a different path.

The practical consequence: with the CPU no longer running that scheduling thread, you free up some CPU overhead and can shave latency in the games where that overhead was a factor. That is the upside. It is also why the gains are modest and uneven rather than a universal FPS boost – more on that below.

The honest FPS expectation: neutral-to-positive, not a magic button

This is where a lot of guides oversell it. Hardware-accelerated GPU scheduling does not reliably hand you a big frame-rate increase. The realistic expectation is neutral to slightly positive on average FPS, with the meaningful benefit being reduced CPU scheduling overhead.

That framing tells you where it helps most: CPU-bound situations. If your processor is the limiter, trimming the scheduling work it has to do is more likely to matter. If you are GPU-bound – pushing high resolution and settings where the graphics card is pegged – moving the scheduler off the CPU changes very little, because the CPU was not the bottleneck to begin with. If you are not sure which side you are on, the PC Bottleneck Calculator estimates whether your CPU or GPU is the limiter at your resolution, and that is the variable that decides whether HAGS does anything you can feel.

So the case for turning it on is not “more frames.” It is “modern drivers are built around it, it costs you nothing on average, and it unlocks the feature below.”

The real reason it is non-negotiable: frame generation

Here is the part that turns “probably leave it on” into “leave it on.” NVIDIA’s DLSS Frame Generation requires hardware-accelerated GPU scheduling to be enabled at the operating-system level. This is not a community rumor – it is stated in official game-vendor documentation. CD PROJEKT RED’s support page for DLSS Frame Generation says plainly that “DLSS Frame Generation requires a GeForce RTX 40 Series graphics card and Hardware-Accelerated GPU Scheduling being enabled in operating system,” and walks players through enabling it (CD PROJEKT RED support).

The reason is the mechanism from the first section: frame generation needs the GPU to have direct control over its own scheduling and memory to insert generated frames into the pipeline. If Windows is still running the old CPU-side scheduler, that control is not there, and the feature simply stays unavailable. On Windows 11 this is usually a non-issue because the setting is on by default; on Windows 10 you may have to enable it yourself before Frame Generation appears.

AMD’s frame generation works differently under the hood – its FSR 3 / driver-level Fluid Motion Frames path runs on the GPU’s shaders via asynchronous compute rather than a dedicated optical-flow hardware block like NVIDIA’s RTX 40 cards use, per AMD’s GPUOpen documentation. The takeaway is the same in practice: on a supported modern Radeon, you want HAGS on and your driver current. If you want the full picture of how interpolated frames, latency, and the base-framerate floor interact, that is the subject of frame generation explained – this article is just the OS switch that lets any of it run.

When OFF can actually win

A blanket “always on” would be dishonest, because a minority of setups regress with it enabled. These are real, documented cases – not invented numbers – and they share a pattern: the issue appears with HAGS on and clears when you turn it off.

Micro-stutter. Some players report frame-pacing micro-stutter that disappears the moment they disable HAGS, with the game running smooth afterward (ASUS ROG forum thread).
High DPC latency. On some Windows 11 systems, high DPC latency tied to the NVIDIA display driver (nvlddmkm.sys) drops sharply after turning HAGS off (NVIDIA GeForce forums). High DPC latency is a classic source of audio crackle and stutter, so this one is worth checking if you have those symptoms.
VR. Disabling HAGS is a recommended troubleshooting step for SteamVR stutter on some configurations (Steam community). VR is latency- and pacing-sensitive in a way flat gaming is not, which is why it shows up disproportionately here.
Older or weaker GPUs, and some Unreal Engine titles. If your card barely meets the support bar, or a specific game’s engine paces worse with it on, the simpler CPU-scheduled path can feel steadier.

The common thread: none of these are reasons to default to off. They are reasons to test off if you are seeing a specific problem – and if you do not use frame generation, you have nothing to lose by trying it.

A simple decision

Your situation	Setting
Modern GPU (RTX 30/40/50, RX 6000+), no issues	On (it is the default)
You want DLSS / AMD frame generation	On (required)
Micro-stutter, audio crackle, or high DPC latency	Test Off – keep whichever is smoother
VR stutter you cannot otherwise fix	Test Off
Older / barely-supported GPU that feels hitchy	Test Off

How to change it (and verify)

The toggle lives at Settings > System > Display > Graphics > Change default graphics settings, where you flip the Hardware-accelerated GPU scheduling switch (Microsoft Learn). If you do not see the option at all, your GPU either does not support it or your driver is older than WDDM 2.7 – install the latest driver straight from NVIDIA, AMD, or Intel and check again. Restart after changing it so the display driver reloads cleanly.

To judge whether it helped or hurt your machine, do not trust the average FPS counter. Run a demanding, repeatable scene with a frame-time overlay and compare your 1% lows and frame-time consistency on and off. As with the DX12 vs DX11 question, smoothness lives in the lows, not the average – and if a single game stutters under HAGS, rule out the boring causes first, like a launcher or anti-cheat fault, before blaming the scheduler.

The bottom line

Hardware-accelerated GPU scheduling is best understood as plumbing, not a performance cheat – the same way Resizable BAR / Smart Access Memory is a small, legitimate gain rather than the free-FPS switch it gets sold as. On a modern GPU it belongs on: it is the Windows 11 default, it moves scheduling overhead off your CPU for a neutral-to-small FPS effect, and – the deciding factor – it is a hard requirement for NVIDIA DLSS Frame Generation and the AMD frame-gen path most people on current cards actually want. Turn it off only when you have a concrete regression in front of you: stutter, DPC latency, or VR hitching that demonstrably clears when you disable it. Otherwise, leave the switch where Windows put it and spend your tuning time somewhere it pays off more.

Sources

Microsoft DirectX Developer Blog – Hardware Accelerated GPU Scheduling (mechanism, WDDM 2.7 requirement, opt-in): https://devblogs.microsoft.com/directx/hardware-accelerated-gpu-scheduling/
Microsoft Learn – how to open the Hardware-accelerated GPU scheduling toggle (Settings path): https://learn.microsoft.com/en-us/answers/questions/3857947/how-to-open-hardware-accelerated-gpu-scheduling-on
CD PROJEKT RED Support – DLSS Frame Generation requires Hardware-Accelerated GPU Scheduling: https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/2369/dlss-frame-generation-how-to-enable-hardware-accelerated-gpu-scheduling-1
AMD GPUOpen – FidelityFX Super Resolution 3 frame generation (shader / async-compute mechanism): https://gpuopen.com/fidelityfx-super-resolution-3/
ASUS ROG Forum – HAGS micro-stutter regression report: https://rog-forum.asus.com/t5/rog-strix-series/quot-if-i-enable-hags-i-get-micro-stutters/td-p/1019715
NVIDIA GeForce Forums – high DPC latency on Windows 11 resolved by disabling HAGS: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/506279/high-dpc-latency-nvidia-win-11/3341675/
Steam Community – SteamVR stutter troubleshooting (disable HAGS): https://steamcommunity.com/app/250820/discussions/3/4036976796097585542/

Ryzen 5 7600X3D vs Ryzen 7 7800X3D: Value Pick (2026)

LK Wood IV — Wed, 24 Jun 2026 00:00:00 -0500

For a pure gaming build, the Ryzen 5 7600X3D captures most of the X3D magic for less money: it carries the same 96MB of 3D V-Cache as the 7800X3D and trails it by only about 6% in gaming. The 7800X3D earns that 6% with two more cores and slightly higher clocks, which also buy you streaming headroom, multitasking, and a longevity buffer. The honest split: a single-task 1080p or 1440p gamer who lives near a Micro Center should look hard at the 7600X3D; everyone who streams, multitasks, or cannot get the exclusive should pay up for the 7800X3D.

Why both chips game so well: 3D V-Cache

The reason these two processors punch above their core counts is the stacked cache. AMD’s 3D V-Cache stacks an extra 64MB of L3 onto the die, bringing both the Ryzen 5 7600X3D and the Ryzen 7 7800X3D to 96MB of total L3.

Games make many small, scattered memory requests. A larger cache serves more of them on-chip instead of waiting on slower system RAM, which is why X3D chips beat higher-clocked, pricier CPUs in games while drawing less power. That mechanism is identical on both parts here. The 7600X3D is not a watered-down cache design; it has the full 96MB working set. This is the core of the value argument: you are not paying the 7800X3D premium to get the feature that makes X3D special in games. You already have it on the cheaper chip.

The spec gap: 6 cores vs 8, and clocks

The difference between these two is cores and clocks, not cache.

Spec	Ryzen 5 7600X3D	Ryzen 7 7800X3D
Architecture	Zen 4 (5nm)	Zen 4 (5nm)
Cores / Threads	6 / 12	8 / 16
Base clock	4.1 GHz	4.2 GHz
Boost clock	4.7 GHz	5.0 GHz
L3 cache	96MB	96MB
Default TDP	65W	120W
Socket	AM5	AM5

The 7600X3D’s official specs (6 cores, 12 threads, 4.1 GHz base, 4.7 GHz boost, 65W) come from AMD’s product page; the 7800X3D’s 8-core, 16-thread, 5.0 GHz boost, 120W rating comes from AMD’s 7800X3D page. Two things stand out. The 7800X3D has a 300 MHz higher boost clock, and it carries a meaningfully higher 120W TDP versus the 7600X3D’s 65W, reflecting the extra cores it has to feed. Both are Zen 4 on the same AM5 platform, so a motherboard or RAM kit that works with one works with the other.

The gaming gap: about 6 percent

On our relative gaming index, the 7800X3D scores 85.6 and the 7600X3D scores 80.6 (see the 2026 CPU gaming hierarchy). That is roughly a 6% gaming lead for the 8-core chip. Our index is a relative gaming score where the fastest chip in the set anchors at 100, not an absolute frame-rate figure, so read it as tier position rather than a literal FPS delta.

That 6% is corroborated by the most thorough public test of these two parts. Gamers Nexus, reviewing the 7600X3D against the 7800X3D, measured a spread that mostly lands in the single digits:

Stellaris: 7800X3D ahead by 5.4%
F1 24: 7800X3D ahead by 7.2%
Baldur’s Gate 3: about 9% (126 vs 116 FPS average)
Final Fantasy XIV Dawntrail: roughly tied
Rainbow Six Siege: a 1.4% lead Gamers Nexus called “basically error”

A handful of CPU-bound titles stretch the gap wider. Gamers Nexus saw Starfield run about 19% faster on the 7800X3D (145 vs 122 FPS) and Dragon’s Dogma 2 around 15%. Those are the exception, not the rule, and they tend to be the games where extra cores and clocks help most. Across a broad suite the picture is consistent with our 6% index figure: the 7800X3D is faster, but in most games you would struggle to feel it. To line the two up yourself, the CPU Comparison Tool puts their index scores side by side.

When the 6-core 7600X3D is enough

The 7600X3D is the right call when your machine does one demanding thing at a time. If you play at 1080p or 1440p chasing high refresh, and you are not also encoding a stream, transcoding video, or running a wall of background apps, six X3D cores keep modern games fed. The cache does the heavy lifting, and that cache is identical to the 7800X3D’s.

This is also the resolution caveat that matters. The higher you push resolution, the more the graphics card sets your frame rate, which shrinks any CPU gap further. At 1440p with a mid-to-high-end GPU, the already-small 6% lead compresses toward nothing because the GPU hits its ceiling first. The PC Bottleneck Calculator estimates whether your CPU or GPU is the limiting part at a given resolution, which is the real question behind “do I need the 8-core chip.”

When to pay up for the 8-core 7800X3D

Two extra cores and four extra threads stop being a rounding error the moment the game is not the only workload running.

Pay up for the 7800X3D if you:

Stream or record while you play. Game capture and encoding want cores the 6-core chip is also using for the game.
Run simulation, 4X, or strategy titles with heavy background tasks, where late-game CPU load piles up.
Do any real productivity work: video editing, compiling, local AI inference, dozens of browser tabs.
Run a sustained all-core load like CPU mining. Monero’s RandomX rewards both cores and cache, so the 8-core 7800X3D out-hashes the 6-core 7600X3D — though, as that guide’s math shows, neither one pays for itself.
Want a longevity buffer. As games trend toward using more threads, the 8-core part has more runway before it feels tight.

That last point is the quiet argument for the 7800X3D even on a gaming-only build. You are buying two cores of future-proofing for the years the chip will live in your system. If you later want to know whether to jump again, the 7800X3D vs 9800X3D upgrade analysis covers the next rung.

The availability catch you cannot ignore

There is a practical reason this is not a clean “buy the cheaper chip” call: the 7600X3D is a Micro Center exclusive. AMD launched it quietly in September 2024, sold only through Micro Center’s roughly 28 U.S. stores at a $299 list price, often as in-store stock or in-store pickup with a discounted CPU-plus-board-plus-RAM bundle. It shipped with no review samples, which is why coverage was thin at launch.

For anyone near a Micro Center, that exclusivity is a feature, because the bundle pricing makes the value gap wider than the chips alone. Gamers Nexus’s own verdict was blunt: the 7800X3D’s roughly $180 premium “doesn’t seem worth it if you have a Micro Center near you.” If you do not, the equation flips. The 7800X3D sells through every normal retailer, and chasing a store-exclusive part you cannot reliably buy is not worth losing weeks over to save a single-digit performance gap you may never notice.

The verdict on price-per-frame

For a value gamer, the call comes down to access and use case. If you can buy the 7600X3D at Micro Center and you game one task at a time, it is the better price-per-frame chip: you surrender about 6% of gaming performance, most of it invisible at 1440p, to keep real money in your pocket. If you cannot get the exclusive, or you stream, multitask, or want the two-core longevity cushion, the 7800X3D is the safer pick and the one I would point most buyers to simply because you can actually purchase it. Both are excellent X3D gaming chips. The cheaper one just asks you to live near the right store.

Want the full picture? The 2026 CPU gaming hierarchy ranks both chips against the rest of the X3D lineup, and the CPU Comparison Tool lets you stack any two processors head-to-head.

Ryzen 9 9950X3D vs 9800X3D: Which X3D for Gaming

LK Wood IV — Mon, 22 Jun 2026 00:00:00 -0500

For a pure gaming PC, buy the Ryzen 7 9800X3D, not the Ryzen 9 9950X3D. The 9950X3D is the better all-rounder if you also render, compile, or stream on the CPU, but in games it lands at parity with the cheaper chip - and sometimes a hair behind it. This guide explains why a 16-core flagship ties an 8-core part in games, what the dual-CCD design actually does under the hood, and which buyer each chip is for.

The one-line verdict

In our CPU gaming hierarchy, from Tom’s Hardware data where the Ryzen 7 9850X3D is the 100.0 reference, the 9800X3D scores 97.0 and the 9950X3D scores 95.7. That puts the 8-core 9800X3D about 1 to 2 percent ahead of the 16-core 9950X3D in relative gaming - a small gap, but a real one, and it points the wrong way for anyone expecting the pricier chip to win.

Independent testing agrees. In a 16-game average at 1080p High/Ultra, the 9800X3D edged the 9950X3D 195.5 FPS to 194.8 FPS, a 0.4% difference that is within measurement noise per TechSpot’s testing summary. GamersNexus found the same pattern title by title: Final Fantasy XIV “functionally equal,” Stellaris simulation 5% faster on the 9800X3D, Dragon’s Dogma 2 a “measurable but irrelevant 3.2%” lead for the 9950X3D. The chips trade places depending on the game. Neither is decisively faster for play.

Why 16 cores does not beat 8 cores in games

Two facts about PC games explain the whole result. First, games rarely scale past eight threads, so a second 8-core die mostly sits idle during play. Second, games are latency-sensitive: they fire many small, scattered memory requests, and what wins is keeping data close. That is exactly what 3D V-Cache does - AMD stacks extra L3 cache on the die so more of those requests hit cache instead of waiting on system memory.

Here is the catch. On the 9950X3D, 3D V-Cache sits on only one of its two core dies. The chip carries 128 MB of L3 and 16 cores, but the cache-rich gaming cores are only eight of them. If a game’s threads were to spill onto the second, cache-light die, every cross-die hop would add latency and erase the V-Cache advantage. The 9800X3D never has that problem: it is a single 8-core die with all 96 MB of L3 cache on the cores the game is already using. One die, one cache pool, no hops. That structural simplicity is the entire reason an 8-core part can match or beat a 16-core one in gaming.

The dual-CCD parking mechanism, explained

AMD’s fix for the 9950X3D is software that steers games onto the cache die. When you launch a game, the system parks the cores on the second die that lacks 3D V-Cache, making them temporarily unavailable to the OS, so the scheduler is forced to keep the game on the fast cache cores. The brain behind this is AMD’s 3D V-Cache Performance Optimizer, which dynamically picks the favored cores per application - prioritizing the cache-connected cores during gaming and the highest-frequency cores for non-gaming work.

How does the system know it is a game? AMD ships an Application Compatibility Database - a whitelist - that detects specific titles and adjusts the thread pool accordingly, delivered through chipset driver updates AMD confirmed for the 9950X3D and 9900X3D. Xbox Game Bar assists with detection, but parking does not depend on it being enabled.

When it works, it works well - GamersNexus confirmed “parking is functioning properly and the CPU is not hamstrung.” But notice what you are signing up for: a driver, a whitelist, and a scheduling layer that all have to fire correctly every session. A brand-new game the database has not learned yet can land on the wrong cores until a driver update catches up. The 9800X3D has none of this machinery to go wrong, because it has nothing to schedule around. For a gaming-only box, that is one fewer thing that can break - and the practical reason the single-die chip is the safer pick.

Where the 9950X3D actually wins: productivity

None of this means the 9950X3D is a bad chip. It is a superb one - for a different job. With twice the cores, it is about 73% faster than the 9800X3D in multi-threaded work — a 635 vs 367 geometric-mean gap in GamersNexus testing (put the other way: the 9800X3D scores ~42% lower). That is the difference between a chip that games and a chip that games and renders, compiles, runs VMs, or encodes a stream on the CPU while you play.

So the dividing line is clean. If your PC only plays games, those 16 cores are dead weight you paid extra for. If your PC also earns money or finishes creative work, the 9950X3D gives you 9800X3D-class gaming with workstation-class throughput in one socket - and that is a genuinely compelling package. GamersNexus reached the same split verdict: for a build that is purely about games, scale down to the 9800X3D because the difference is not big enough to justify it.

Price, power, and thermals

Price is the loudest argument for the 9800X3D in a gaming build. The 9950X3D launched at a $699 MSRP on March 12, 2025, while the 9800X3D carries a $479 MSRP. That is roughly $220 you can redirect to a faster GPU - which, in a gaming PC, buys far more frames than the second CPU die ever will.

Power follows the same logic. The 9800X3D is rated at a 120W TDP; the 9950X3D carries a 170W TDP. In games the gap narrows because only the cache die is active - GamersNexus measured the 9950X3D pulling 98.8W in Starfield versus 168W for the non-X3D 9950X. Still, the 8-core part is the cooler, simpler chip to feed and quiet, which matters in a compact or low-noise build.

How to choose

Match the chip to the workload, not the marketing tier:

You only game. Buy the 9800X3D. Equal-or-better frame rates, single-die simplicity with no parking to babysit, lower power, and about $220 saved that belongs in your graphics card. The relative-tier data, the independent benchmarks, and GamersNexus all converge here.
You game and do heavy CPU work - video editing, compiling, 3D, VMs, or CPU-side streaming. Buy the 9950X3D. You give up nothing meaningful in games and gain roughly 42% in multi-core throughput.
You are unsure how CPU-bound you even are. Resolution decides how much any of this matters. At 4K the GPU dominates and both chips converge; at high-refresh 1080p and 1440p the CPU gap is most visible. Run your exact GPU and resolution through our PC bottleneck calculator before buying CPU headroom you cannot use, and put the two chips side by side in the CPU comparison tool.

The headline rarely matches the receipt: the cheaper 8-core chip is the better gaming CPU here, and the 16-core flagship is the better computer only if you do more than play. For more head-to-heads and the latest tested hardware, see our reviews.

How to Build a NAS From an Old PC (2026 Guide)

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · Published 2026-06-19 · St. Louis County, MO · ~13 min read

TL;DR · Old PC into a NAS

Does it qualify? 64-bit CPU, 4GB+ RAM (8GB comfortable), enough SATA ports for your drives plus a boot SSD, and bay space. Almost any desktop from the last ~10 years passes.
Pick the OS by RAM: low-RAM or genuinely old box gets OpenMediaVault (Debian, runs on 2-4GB). 8GB+ and you want checksumming gets TrueNAS Community Edition (ZFS). Want to mix drive sizes and will pay gets Unraid.
Boot device: a small separate SSD (64-128GB). Never install the OS on a data drive.
Out of SATA ports? Add an LSI HBA flashed to IT mode, not a cheap RAID card or port multiplier.
The honest catch: no ECC on consumer boards (fine, keep backups), and an old tower can idle at 40-70W versus under 20W for a purpose-built box. If power matters, do the three-year math first.
This guide is the zero-purchase path. Buying new parts instead? See the budget NAS build guide. Want a hypervisor, not just storage? See the old gaming PC to Proxmox guide.

The real question: is your old PC worth it versus a $200 mini PC?

You have a desktop in a closet. An old office Optiplex, a retired family PC, a gaming rig you upgraded out of. The pitch is obvious: it already has a case, a power supply, RAM, and probably some empty drive bays, so turning it into network storage costs nothing but a weekend. That is true, and it is the single best reason to do this.

But “free” only counts the up-front cost. A network-attached storage box runs around the clock, so the number that actually matters over its life is idle power draw. A 2018-era tower with a 65W-class CPU and a couple of spinning drives commonly idles somewhere in the 40-70W range, while a purpose-built 4-bay mini NAS like the ones in the budget NAS build guide idles under 20W. At a typical US electricity rate, that gap is real money over three years. We track the actual draws for common homelab hardware in the 24/7 idle power cost breakdown so you can plug in your own rate.

Here is the honest decision rule. If the old PC has a 65W-class or smaller CPU and you can get it idling under ~40W, repurposing it is the clear winner — you save the entire cost of a new box and you get a far bigger RAM ceiling and more PCIe slots than any mini PC. If it is a 105W+ enthusiast chip, or it idles north of ~75W even after tuning, the power bill will quietly out-cost a new mini NAS inside a year or two. In that case, sell the old platform and buy purpose-built.

This guide is specifically the reuse the hardware you already own path. If your goal is a virtualization host that also does storage rather than a dedicated storage appliance, you want the old gaming PC to Proxmox guide instead — same hardware, different job. And if you are still deciding whether you even need a NAS versus simpler direct-attached storage, start with DAS vs NAS in 2026.

Does my old PC qualify? The five-minute checklist

Before you download anything, confirm the machine clears these bars. None of this requires opening a terminal yet, just knowing your specs.

1. 64-bit CPU

Every NAS OS worth running is 64-bit only. Any Intel Core 2-era-or-newer or AMD chip from roughly 2010 onward is 64-bit, so this rules out only genuinely ancient hardware. Practically, if the PC ran a 64-bit copy of Windows, it qualifies. Unlike a Proxmox hypervisor build, you do not need VT-x/VT-d virtualization flags for a plain NAS, so even chips with virtualization disabled or absent are fine.

2. RAM: 4GB floor, 8GB comfortable

This is the spec that steers your OS choice more than any other. The Google AI Overview and the r/HomeServer consensus both land on the same numbers: 4GB is the absolute minimum, 8GB or more is recommended for stability. OpenMediaVault will genuinely run on 2-4GB because it is just Debian with a web UI. TrueNAS wants 8GB as a practical floor because ZFS uses spare RAM as read cache. Whatever you have, there is an OS that fits it — the trick is matching them, which the next section does.

3. SATA ports (and bay space)

Count two things: how many SATA ports the motherboard has, and how many drives the case can physically hold. You need one SATA port per data drive plus one for the boot device. Most consumer boards ship 4-6 ports, which comfortably covers a 2-4 drive home NAS. Bay space is the other half: a slim office desktop might only fit one or two 3.5-inch drives even if the board has six ports, so check the chassis, not just the spec sheet. XDA’s “things to check when building a NAS with old PC parts” walks through exactly this trap.

4. The HBA escape hatch (when you run out of ports)

If you want more drives than the board has ports, the community-standard answer is an LSI HBA card flashed to “IT mode.” IT mode turns the card into a plain pass-through controller, handing each disk directly to the OS — which is exactly what ZFS and OMV want. Cards like the LSI 9211-8i (and its OEM rebadges from Dell and others) are cheap on the used market and are a homelab staple precisely for this. Avoid two tempting shortcuts: a cheap hardware RAID card (it hides the disks from ZFS) and a SATA port multiplier (flaky under load). The flashing process is well-documented across the TrueNAS forums and r/homelab; budget an evening for it the first time.

5. A separate boot drive

Do not install the NAS OS onto one of your storage drives. Use a small, dedicated boot device — a cheap 64-128GB SATA or NVMe SSD is ideal. If you are genuinely out of SATA ports, a quality USB SSD works (the official TrueNAS forum advice is a real USB SSD like a Samsung T7, not a flimsy thumb drive, which wears out fast). Keeping the OS off the data pool means the storage stays clean and portable: you can reinstall or swap the OS without ever touching your files.

Does your old PC qualify?

Five checks before you flash a USB stick

Check	You need	Fix if short
CPU	64-bit (any ~2010+ desktop)	None practical — replace the box
RAM	4GB min / 8GB comfortable	Cheap DDR3/DDR4 used, or run OMV
SATA ports	1 per drive + 1 boot	LSI HBA in IT mode
Bay space	Room for your 3.5in drives	Bigger case, or fewer/larger drives
Boot device	Separate 64-128GB SSD	USB SSD (not a thumb drive)

techfuelhq.com · June 2026

Choosing the OS: OpenMediaVault vs TrueNAS vs Unraid

This is where people stall, and the wrong pick means a rebuild. For an old consumer PC specifically, the decision is simpler than the general “best NAS OS” debate, because two things narrow it: your RAM, and the fact that your board almost certainly has no ECC.

OpenMediaVault — the default for old, low-RAM hardware

OpenMediaVault (OMV) is Debian Linux with a NAS-focused web UI bolted on. That is its whole strength: it is the lightest option by a wide margin, runs comfortably on 2-4GB of RAM, and does not force a particular filesystem on you (ext4, XFS, or Btrfs, with ZFS available via plugin). It does SMB/CIFS shares, NFS, rsync, and basic Docker, and nothing it does not need to. For a genuinely old desktop, a low-RAM machine, or anyone who wants a pure file server without ZFS’s appetite, OMV is the right call and the one the SERP’s own AI Overview singles out as “designed specifically to run well on minimal, older hardware.”

TrueNAS Community Edition — when you have 8GB+ and want ZFS

TrueNAS Community Edition is built around ZFS, and that is both its appeal and its cost. ZFS gives you end-to-end checksumming, silent scrubs that catch bit rot, snapshots, and clean recovery from a failed drive — the most trustworthy storage layer you can run on consumer hardware. The price is RAM: TrueNAS lists 8GB as its practical floor, and ZFS will use whatever spare memory you give it as read cache (ARC). The widely repeated “1GB of RAM per TB” rule is a rough rule of thumb, not a requirement, and has been walked back for years. If your old PC has 8GB or more and the data matters, TrueNAS is the pick. Just go in knowing the ECC caveat below.

Unraid — the paid pick for mismatched drives

Unraid is the odd one out: it is paid (perpetual licenses from roughly $49 to $249), and instead of pooling identical disks it treats each drive as its own filesystem with parity calculated across them. The killer feature is mixing drive sizes — exactly the situation you land in when you reuse an old PC and a junk-drawer pile of mismatched HDDs (a 4TB, a 6TB, an 8TB all in one array). It also has the friendliest Docker and VM interface of the three. The tradeoffs: it costs money, and its parity approach does not checksum data the way ZFS does. If you are reusing whatever drives you already own and do not want to buy a matched set, Unraid’s flexibility is worth the license. If you do go the other way and buy a matched set of NAS drives for a ZFS pool, the best NAS hard drives guide walks through the CMR picks and the recertified $/TB math — and if you’re set on Seagate, IronWolf vs IronWolf Pro vs Exos sorts out which of the three tiers fits your pool and budget.

The decision rule

Under 8GB RAM, or you just want a simple file server: OpenMediaVault.
8GB+ and the data is irreplaceable: TrueNAS Community Edition (ZFS), accepting no-ECC.
A pile of mismatched drives you want to use as-is, and you will pay: Unraid.

For a deeper look at how the ZFS, Btrfs, and parity backends actually differ on rebuilds, IOPS, and redundancy, see the full Proxmox vs TrueNAS vs Unraid storage backend comparison. And before you commit to a drive layout, run your disk count and sizes through the NAS and RAID storage calculator to see usable-versus-raw capacity across RAID and RAIDZ levels.

NAS OS for an old PC, compared

Picked for reused consumer hardware, not enterprise builds

	OpenMediaVault	TrueNAS CE	Unraid
Price	Free	Free	$49-$249
Min RAM	2-4GB	8GB	4GB (8GB+ ideal)
Filesystem	ext4 / XFS / Btrfs	ZFS	XFS + parity
Bit-rot protection	Depends on FS	Yes (self-heal)	Parity only
Mix drive sizes	With plugin	No	Yes (killer feature)
Best for old PC when	Low RAM, simple file server	8GB+, data integrity	Mismatched junk-drawer drives

techfuelhq.com · June 2026

The build path: from old PC to working shares

Once the machine qualifies and you have picked an OS, the actual conversion is short. This is the path the TrueNAS docs, OMV docs, and every beginner walkthrough converge on.

Step 1 — Back up anything on the drives first

Installing a NAS OS and creating a storage pool erases the drives. If the old PC or any of the disks still hold files you care about, copy them off now, to another machine or an external drive. There is no undo once you build the pool.

Step 2 — Pick your OS and download the installer

Grab the ISO for your choice: OpenMediaVault from the official site, TrueNAS Community Edition from truenas.com, or Unraid from unraid.net. Match it to your RAM per the decision rule above — this is the call that is hardest to reverse later.

Step 3 — Flash a USB installer

Write the ISO to a spare USB stick with Rufus (Windows), balenaEtcher (cross-platform), or Ventoy if you want to keep several installers on one stick. This USB is the installer and can be reused afterward — it is not where the OS will live.

Step 4 — Boot the old PC from USB and install

Plug in the installer USB and your separate boot SSD. Power on and tap the boot-menu key (commonly F11, F12, or Delete) to boot from the USB. Run the installer and, when it asks for a target, select your small boot SSD — not a data drive. A few minutes later it reboots to a console showing an IP address, for example 192.168.1.150.

Step 5 — Open the web UI and set a static IP

Type that IP into a browser on your main computer to reach the NAS dashboard. First housekeeping job: give the NAS a static IP, either in the OS network settings or as a DHCP reservation in your router, so the address never moves out from under you.

Step 6 — Create the storage pool

In the OS dashboard, group your data drives into a pool. The redundancy choice matters: a two-drive mirror (ZFS mirror or RAID 1) gives you one-drive fault tolerance and is the simplest safe default; larger arrays use RAIDZ (TrueNAS) or parity (Unraid). Sanity-check raw-versus-usable space for your layout with the NAS and RAID storage calculator before you commit, since redundancy always costs capacity.

Step 7 — Create shares and connect

Enable SMB (Server Message Block) for Windows/Mac/Linux access, create a shared folder on your pool, add a user, and point your other devices at it. The share now mounts like any network drive. Add a scheduled scrub (ZFS) or parity check (Unraid) so the array verifies itself on a cadence, and you have a working NAS.

The honest caveats

A repurposed old PC is a genuinely good NAS, but it is not free of tradeoffs, and pretending otherwise would not help you. Here are the four worth knowing before you commit.

Power draw. This is the big one, covered up top: an old tower idles far higher than a purpose-built mini NAS, and over years that gap can exceed the cost of just buying the new box. Measure your idle wattage with a smart plug or a Kill-A-Watt and run it against your electricity rate using the 24/7 idle power cost breakdown. If you are over ~75W and cannot bring it down, the repurpose math may not win.

No ECC RAM. Consumer desktop boards do not support error-correcting memory, and ZFS is happiest with ECC. But the long-standing scare that “ZFS without ECC will destroy your data” has been overstated for years — non-ECC ZFS is no more dangerous than any other non-ECC filesystem, and it is what the overwhelming majority of home TrueNAS users run. The real protection is not ECC; it is keeping actual backups, because a NAS (RAID or not) is never a backup by itself.

Drive and SATA limits. A consumer board and a small case cap how far you can expand. You can push past the port count with an HBA, but bay space, power-supply SATA connectors, and airflow all become real constraints as you add disks. If you find yourself buying an HBA, a bigger PSU, and a new case, you have effectively built a new machine and should price it against a purpose-built one.

Noise and footprint. A tower with case and CPU fans is louder and far larger than a silent shelf-top mini NAS. If the box lives in an office or bedroom, that matters. It is a fine reason to choose differently even when the power math says “keep it.”

None of these are dealbreakers for the common case — a reasonably efficient desktop with a few drives, living somewhere you will not hear it. They are the signals that tell you when reusing the old PC stops making sense and buying purpose-built starts. If you land on “buy,” the budget NAS build guide covers the cheapest paths in the current drive-price climate.

Bottom line

If you already own a desktop with a 64-bit CPU, 4GB or more of RAM, and a couple of free SATA ports, you can turn it into a real NAS this weekend for the cost of a small boot SSD and a free OS. Match the OS to the RAM — OpenMediaVault for the lean, low-RAM box; TrueNAS Community Edition when you have 8GB-plus and want ZFS’s data integrity; Unraid when you are pooling mismatched drives and will pay for the convenience. Put the OS on a separate boot drive, add an LSI HBA in IT mode if you run short on ports, and keep backups regardless of redundancy.

The one number that decides whether this is a smart move or a slow money leak is idle power. Measure it, do the three-year math, and if your old tower drinks too much, there is no shame in selling it and building a purpose-built box instead. For most people with a 65W-class machine gathering dust, though, the answer is simple: do not throw it out — give it a second life as storage.

Sources

XDA — How to turn an old PC into a NAS and 6 things to check when building a NAS with old PC parts — hardware checklist, SATA/bay constraints, boot-drive guidance
How-To Geek — Don’t throw away your old PC, it makes a better NAS — boot SSD, RAM, Rufus-flashed TrueNAS USB walkthrough
TrueNAS documentation and community forums — Community Edition system requirements, ZFS RAM guidance, USB-SSD boot advice, no-ECC reality
OpenMediaVault documentation — Debian base and minimal-hardware system requirements
Unraid documentation — licensing tiers and mixed-drive parity array
r/HomeServer — “Complete beginner: can I build a NAS with an old PC” and r/DataHoarder — “Use an old PC, or build a NAS?” — community consensus on RAM floor, OS choice, and the HBA IT-mode staple
Rufus and balenaEtcher — USB installer tools

Email corrections to hello@techfuelhq.com.

Lowell K. Wood IV (LK Wood IV) runs TechFuel HQ from St. Louis County, Missouri — a homelab and budget-PC infrastructure site for self-hosters who refuse to pay cloud rent. Contact: hello@techfuelhq.com

How to Install Proxmox VE (2026): Install + Update Reference

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~12 min read · St. Louis County, MO

Installing Proxmox VE is genuinely easy. The graphical installer is a few screens, and it writes itself to disk in a couple of minutes. What trips people up is not the install itself: it is the first fifteen minutes afterward, where a default install points at a repository you cannot use without paying, and the longer-term question of how you keep the thing updated once it is running.

This page is the generic reference for both. It is hardware-agnostic on purpose: the steps below apply to a mini PC, a used office desktop, an old gaming rig, or a rack server. If you want a hands-on, click-by-click walkthrough on a specific small box, the Proxmox mini PC setup guide is the hardware-specific companion to this one. If you are still choosing hardware, start with the Proxmox hardware requirements. And if you already run VE 8 and want to jump to VE 9, that is a different, planned operation covered in the 8-to-9 upgrade gotchas.

Everything below is cited to the official Proxmox documentation. The current release as of this writing is Proxmox VE 9.2-1 (released May 21, 2026), built on Debian 13 “Trixie.” If a command or file path is here, it is real and current for VE 9.

Part 1: The clean install (any hardware)

Step 1: Download and verify the ISO

Grab the latest Proxmox VE ISO from the official downloads page. As of June 2026 that is the VE 9.2-1 installer, about 1.7 GB.

Do not skip the checksum. The download page publishes a SHA256 value next to the ISO. After downloading, compute the hash and compare it to that published value:

# Linux / macOS
sha256sum proxmox-ve_9.2-1.iso
# Windows (PowerShell)
Get-FileHash proxmox-ve_9.2-1.iso -Algorithm SHA256

If the two strings do not match, the download is corrupt or tampered with. Delete it and re-download. This takes ten seconds and it is the one verification step that matters before you write installation media.

Step 2: Write the USB installer

A USB stick is the standard install medium. The tool depends on your OS, and the official guidance is specific about which ones work:

Linux: use dd. Identify the USB device first with lsblk (run it before and after plugging the stick in so you are certain which device is the USB), then write:
```
dd bs=1M conv=fdatasync if=./proxmox-ve_9.2-1.iso of=/dev/XYZ
```
Replace /dev/XYZ with your actual USB device. Getting this wrong overwrites the wrong disk, so confirm the device name carefully.
Windows: Etcher works with no configuration. Rufus also works, but you must select DD mode when it prompts, not ISO mode.
macOS: convert the ISO to a raw image, then write it (see the official media-prep page for the exact hdiutil and dd sequence).

One specific warning from the docs: do not use UNetbootin. It is incompatible with the Proxmox installer.

Step 3: Boot the installer and pick your filesystem

Plug the USB into the target machine, power on, and bring up the boot menu (the key varies by vendor, commonly F11, F12, or Del). Select the USB device, then choose Install Proxmox VE from the boot menu.

The installer is a graphical wizard. Most screens are self-explanatory, but two decisions matter:

Target disk and filesystem. Select the SSD or NVMe you want Proxmox installed on, and be careful not to pick the USB installer drive by accident. The filesystem choices:

Filesystem	When to choose it
ext4 (default)	Single-disk machine. Simple, fast, reliable, uses an LVM-thin pool Proxmox manages natively. The right first-install answer.
ZFS	Two or more drives and you want a mirror or RAID-Z, plus snapshots, checksums, and self-healing. Wants meaningful RAM for its cache.
XFS	Offered with LVM, but far less common in Proxmox setups than ext4.
Btrfs	A technology preview. Not recommended for a production-style install yet.

The official installer note is blunt that ZFS on top of any hardware RAID is unsupported and can cause data loss, so if you run ZFS, give it the raw disks. For a first build on one drive, choose ext4 and move on.

Network and password. Set a hostname, then set a static IP outside your DHCP range so the web UI always lives at the same address. Set a strong root password and a notification email (real if you want system alerts, a dummy if you do not). The installer builds a Linux bridge called vmbr0 on your first NIC so VMs and containers can reach the network.

Click install. It writes to disk in a few minutes and reboots. The console then shows a URL.

Step 4: Reach the web interface

Point a browser on another machine at the IP given during install, on port 8006:

https://your-ip:8006

Note the https and the :8006 — plain http or a missing port is the single most common “it didn’t work” mistake, and the install is almost certainly fine. You will get a certificate warning because Proxmox uses a self-signed cert; accept it and log in as root with the password you set.

Part 2: The first fifteen minutes (the repository fix)

This is the part generic install guides skip, and it is the one step every Proxmox install needs. A fresh install points apt at the enterprise repository, which requires a paid subscription. Without a key, every apt update ends in 401 Unauthorized and your package lists never refresh.

Proxmox VE 9 also changed the repository file format. It moved to the deb822 .sources format, so the files look nothing like the one-line sources.list entries from VE 8 and earlier. Here is the current, correct configuration.

Disable the enterprise repository

Open the node shell (web UI → your node → Shell) and edit the enterprise sources file:

nano /etc/apt/sources.list.d/pve-enterprise.sources

Add a single line to that entry so it reads Enabled: no. That suppresses the enterprise repo without deleting it.

Enable the no-subscription repository

Create the no-subscription sources file with the exact deb822 contents the docs publish for VE 9:

# /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

You can do all of this from the web UI instead, with no text editing: node → Updates → Repositories → Add, pick No-Subscription from the dropdown, then highlight the enterprise row and click Disable. The GUI writes the same files for you.

The no-subscription repo ships the same packages as enterprise without a key. Proxmox is explicit that these packages are “not always as heavily tested and validated,” so it is fine for a home lab or test cluster but is not their recommendation for production. For most homelabbers that is an acceptable trade, and the no-subscription repo is what the vast majority run.

Run the first update

Now that apt points at a repo you can actually use, pull updates:

apt update
apt full-upgrade

Use full-upgrade, not plain upgrade — more on why in Part 3. Reboot if a new kernel was installed, and you are on the latest VE 9 point release.

The login popup reminding you to buy a subscription is cosmetic. It does not affect anything. Click OK and move on; the only repository change that matters is the one you just made.

Part 3: How to update Proxmox over time

Once Proxmox is running, “update” means two very different things, and conflating them is where homelabs get into trouble.

Routine updates (within a major version)

This is normal maintenance: keeping VE 9 current as point releases ship (9.1 to 9.2 and so on). Two equivalent ways:

From the shell:

apt update
apt full-upgrade

From the web UI: select the node, open Updates, click Refresh to pull the package lists, then Upgrade to apply them.

Why full-upgrade and not apt upgrade? Plain upgrade refuses to install anything that requires a new dependency, and on Proxmox that means the kernel and the pve-manager stack get held back — exactly the packages you want updated. full-upgrade (the apt equivalent of dist-upgrade) installs them. A reboot is only needed when a new kernel arrives. There is no rush to apply every point release the day it lands; updating on a comfortable cadence is fine.

Major upgrades (across major versions)

Moving from VE 8 to VE 9 is a different animal. It crosses to a new major version, which also moves the underlying Debian base and kernel, and it carries real breaking changes: LVM autoactivation defaults change, network interfaces can be renamed by the newer kernel, and PCI passthrough can need attention. That is a planned event with its own pre-flight checklist — back up first, run the pve8to9 --full checker, pin your NIC names, and have console access that is not the web GUI.

Do not run a major upgrade as part of routine maintenance. The full procedure, the gotchas, and the order of operations for clusters are in the dedicated Proxmox VE 8 to 9 upgrade guide. Proxmox VE 8.4 continues to receive security and bug-fix updates until August 2026, so there is no pressure to rush the jump.

The short version of the distinction: routine updates are low-risk and you do them often; major upgrades are higher-risk and you do them deliberately.

Common install gotchas

A handful of issues account for most “fresh install” frustration:

apt update returns 401 Unauthorized. You are still on the enterprise repository. Disable it and enable pve-no-subscription (Part 2). This is the number-one new-user issue.
The web UI will not load. You used http instead of https, or forgot :8006. The correct URL is https://your-ip:8006. The install is fine.
VMs will not start (“KVM not available”). Hardware virtualization (Intel VT-x or AMD-V) is disabled in the BIOS/UEFI. Reboot into firmware and enable it. If you also plan GPU or NIC passthrough, enable IOMMU (VT-d / AMD-Vi) while you are in there.
You picked ZFS and the host feels short on RAM. ZFS reserves RAM for its cache. Size it deliberately; the hardware requirements page covers the ZFS RAM rule.
You accidentally installed onto the USB stick. Always confirm the target disk in the installer is your internal SSD/NVMe, not the installer drive.

After the install: what to build

With Proxmox installed, updated, and pointed at the right repository, you have a working hypervisor. The next decisions are about what to run on it:

For a guided, screen-by-screen walkthrough on a specific small machine — including BIOS keys, the first VM, and the first container — follow the Proxmox mini PC setup guide.
For each service, decide between a container and a full VM. The LXC vs VM in Proxmox guide has the decision tree; containers are lighter and start in seconds, VMs give full isolation.
To size your box — how many VMs and containers your RAM and cores can actually support, with ZFS overhead included — the Proxmox capacity planner does the math.

The install is the easy part. The repository fix is the part that makes updates work, and knowing the difference between a routine update and a major upgrade is what keeps the box healthy for years.

Sources

Proxmox VE Package Repositories — the deb822 .sources format for VE 9, the exact proxmox.sources no-subscription entry, the enterprise repo and Enabled: no disable, the “not as heavily tested” note, and the GUI Repositories panel.
Proxmox VE Installation — installer filesystem options (ext4/XFS/ZFS/Btrfs preview), the ZFS-on-hardware-RAID warning, and the https://youripaddress:8006 web interface URL.
Proxmox VE: Prepare Installation Media — the dd command for Linux, Etcher/Rufus-DD-mode for Windows, the macOS sequence, and the UNetbootin incompatibility warning.
Proxmox VE downloads (ISO) — current VE 9.2-1 ISO and the published SHA256 checksum.
Proxmox VE 9.0 release announcement — VE 9 on Debian 13 “Trixie,” and the VE 8.4 support window to August 2026.
Proxmox VE Upgrade from 8 to 9 — the major-version upgrade process and breaking changes, distinct from routine full-upgrade maintenance.

Already have the hardware on your desk? The Proxmox mini PC setup walkthrough is the hands-on companion to this reference. Still picking parts? See the Proxmox hardware requirements. Running VE 8 today? The 8-to-9 upgrade guide is the planned-upgrade path.

NZXT Kraken 360 Review: Long-Term on a Ryzen 7 7800X3D (2026)

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~10 min read · St. Louis County, MO

Rating: 4.0 / 5

I ran the NZXT Kraken 360 on a Ryzen 7 7800X3D inside a ROG STRIX B650-A build for an extended period before moving on to a different configuration. This isn’t a first-day review — it’s what happens after the novelty of the LCD display wears off and you start noticing the software.

The short answer: the Kraken 360 is a well-built, genuinely quiet 360mm AIO with a smooth installation and good thermals. NZXT CAM is the only meaningful problem, and it’s a real one if you care about background processes.

What NZXT ships

The exact unit: this review covers the classic Kraken 360 with the 2.36-inch LCD pump display (the RL-KR360-W1 generation). Worth knowing before you shop: NZXT has since relaunched the Kraken line under a Core / Plus / Elite naming scheme, so a 2026 search for “Kraken 360” returns the newer SKUs rather than the exact unit reviewed here. The pump platform (Asetek 7th-gen) and radiator carry over, but confirm the current product page matches the model you’re buying — the LCD-vs-static-ring split is the thing that changes between tiers.

Hardware (per NZXT product page, accessed 2026-06):

Radiator: 394 × 120 × 27 mm (360mm), aluminum
Pump head: 2.36-inch color LCD display (1080×1080 resolution on the Elite model)
Fans: 3× NZXT F120 RGB Core (120mm, 500–2400 RPM, 30.4 dBA max)
Pump: Asetek 7th-generation, 800–2800 RPM
TDP claim: NZXT rates the Kraken 360 for “up to 500W+TDP” (internal testing methodology — treat as relative, not absolute)
Included socket brackets: AM5, AM4, LGA1700, LGA1851

Price (at time of purchase): $179 USD for the base Kraken 360 / $199 USD for the Kraken Elite 360.

Installation on AM5

Straightforward, but the stock AMD bracket must come out first — that’s the only extra step over an older platform install.

Remove the stock AMD cooler bracket: four screws, retained from behind by a plastic backplate
Install the NZXT backplate from the rear of the motherboard
Thread in the four AM5 standoffs finger-tight, then snug with a small wrench
Apply thermal paste (I use a pea-sized dot of MX-6; NZXT includes their own TIM which is adequate)
Press the Kraken head onto the CPU, align the spring-loaded screws with the standoffs, and tighten cross-pattern

Radiator orientation: front intake (pulling cool air from outside the case through the radiator and pushing warm air into the case) or top exhaust (radiator exhausts hot air out the top of the case). For a build with a strong GPU producing heat inside the case, top exhaust is the better choice — it removes the heat without recirculating it past the radiator. The ROG STRIX B650-A’s layout (standard ATX) accommodates top-mount 360mm without clearance issues.

Total time: 10 minutes with the motherboard out of the case. If you’re doing a full build, it’s the first cooler part to install (backplate goes on before the board goes into the case).

Thermals on a 7800X3D

The Ryzen 7 7800X3D is a different thermal challenge than a high-TDP chip like the Ryzen 9 7950X or Intel i9-14900KS. Its 3D V-Cache stacks SRAM on top of the CPU die, which creates a thermal constraint: AMD’s own thermal throttle limit is 89°C on the 3D V-Cache tier. Above that, the chip reduces clock speeds to protect the cache.

The practical consequence: the 7800X3D benefits from a cooler that keeps it below 89°C under gaming load, but it doesn’t produce the kind of sustained 250–300W loads that stress-test premium AIOs. At its rated 162W PPT (max socket power), a 240mm AIO can keep it under the throttle threshold. A 360mm AIO gives more temperature headroom.

In my build — ROG STRIX B650-A, B650 chipset power delivery, Fractal case with airflow configuration — the 7800X3D stayed under 80°C during sustained gaming sessions with the fans at a curve that maxed at 1700 RPM. Under Cinebench R23 multi-core sustained for 10 minutes, it peaked at 84°C and maintained stable clocks. I did not observe thermal throttling during normal gaming workloads.

For independent sustained thermal measurements on the Kraken 360 across multiple CPU platforms, GamersNexus publishes AIO cooler reviews with controlled methodology — their data on Asetek 7th-gen performance is the benchmark I compare against.

NZXT CAM: the weak link

CAM is NZXT’s proprietary software for controlling the pump, fans, and LCD. The functionality is solid — you can create custom fan curves, set up display pages showing CPU/GPU temp and usage, customize the ARGB ring, and monitor system stats.

The problem: CAM needs to run in the background for any of the display and RGB functionality to work. It’s an Electron-based application, which means on startup it uses more RAM and CPU than feels appropriate for a peripheral-control utility.

What CAM requires:

Background process (~150 MB RAM, periodic CPU spikes on startup)
Login to an NZXT account for full feature access (offline mode limits some display options)
Windows only with full functionality; Linux has no native support

What works without CAM: basic pump and fan operation at defaults. The LCD shows the NZXT logo or a built-in temperature readout based on the pump head’s internal thermistor. Fans run at a built-in speed curve.

For a Windows gaming machine where CAM runs at startup and stays resident, this is a non-issue — you set it up once and forget it. For a build dual-booting Linux, or for someone who doesn’t want background software, the CAM dependency is a genuine negative.

ASUS Armory Crate and Corsair iCUE have the same pattern. NZXT CAM is not worse than the competition in this category — it’s just that all of them have this problem.

Pump and fan noise

The pump: inaudible with the side panel on at any point during normal operation. I could not isolate it from case fan noise. This matches the behavior of Asetek 7th-gen units generally — the pump is not the noise concern with this cooler.

The fans: at default NZXT curves, the F120 RGB Core fans are quiet at light loads (under 1200 RPM) and audible under load when they spin up toward 2000+ RPM. The 30.4 dBA spec at max RPM is accurate in a controlled environment — in a room with normal ambient noise, the fans become noticeable above about 1800 RPM.

Custom curve I settled on: 800 RPM at 40°C, 1200 RPM at 60°C, 1600 RPM at 70°C, 1800 RPM max. At these speeds the fans are inaudible from 1 meter away with the case side on, and thermal performance on the 7800X3D was unchanged — a 360mm radiator at 1800 RPM is more than adequate for 162W.

Build quality

Physical build quality is high. The radiator finish, pump head housing, and fan blade consistency are noticeably better than budget AIOs. The braided tubing has a solid feel and didn’t kink or stiffen over time. The LCD display glass is flush and scratch-resistant. The F120 fans have a consistent spin-up behavior and no blade wobble or grinding.

The only quality concern: the thermal paste pad that ships pre-applied on the Asetek head. I remove it and apply my own paste. The included pad performs adequately but unevenly — depending on how the head seats, coverage can be inconsistent. This is an Asetek packaging issue, not specific to NZXT.

Price and alternatives

At $179 for the base Kraken 360, the value proposition is reasonable for the build quality and thermals. Comparable options:

Cooler	Size	Key differentiator	Street price
NZXT Kraken 360	360mm	LCD display, premium finish	~$179
Corsair iCUE H150i Elite LCD XT	360mm	Infinity mirror LCD	~$200
DeepCool LT720	360mm	No LCD, lower price	~$110
be quiet! Pure Loop 360	360mm	Near-silent fans, no RGB	~$130
Thermalright Frozen Prism 360	360mm	Best price-to-thermal	~$65

The Thermalright Frozen Prism 360 (no LCD, basic ARGB ring) competes on thermals at less than half the Kraken’s price. If the LCD display is not important to you, the Thermalright is a harder value to ignore. GamersNexus measured the Frozen Prism 360 as a top-tier thermal performer for its price class.

The Kraken 360 is worth the premium over the Thermalright if:

You want the display for at-a-glance CPU/GPU monitoring without opening software
Build aesthetics matter and the NZXT industrial design fits the case
CAM running in the background is not a concern

Verdict

The Kraken 360 does what an AIO cooler is supposed to do: it keeps a demanding CPU cool, does it quietly, and doesn’t require setup beyond the initial configuration. On the 7800X3D, it’s more cooler than needed — the chip doesn’t push the AIO anywhere near its limits — which means there’s headroom for future platform upgrades if you build around it.

The LCD display is genuinely useful, not a gimmick. Having CPU temp and GPU temp visible on the pump head without opening a monitoring app is the kind of ambient information that actually gets used. The display implementation is good; the CAM software that drives it is adequate.

If you’re pricing AIOs for a 7800X3D specifically: a 240mm AIO is sufficient for that chip at any normal fan curve. The 360mm gives more headroom and flexibility. If you’re building around a higher-TDP chip like the Ryzen 9 7950X or Intel i9 series, the 360mm starts being necessary rather than optional.

Rating: 4.0/5 — Excellent hardware, middling software. The LCD earns the premium if you want it. The base Kraken 360 at its price is solid but has stiff competition from non-LCD alternatives at half the cost.

For the full build this cooler shipped in, the ROG STRIX B650-A review covers the motherboard. The PC Builder tool checks socket and clearance compatibility for coolers against any AM5/LGA1700 board in the database.

Proxmox Hardware Requirements (2026): Real Homelab Specs

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · Published 2026-06-19 · Updated 2026-07-03 · ~11 min read · St. Louis County, MO

There are really two Proxmox hardware conversations, and they give wildly different answers. The spec-sheet one is settled in a single sentence — the official minimum is trivial, and the table below is the whole story. The conversation that actually matters is the second one: how those requirements scale the moment you start stacking real services onto the box. That is where people either underbuy and regret it a month later, or overbuy a 128 GB server to run a Pi-hole. So that is where this page spends its time.

Everything here is cited to Proxmox’s own documentation or, where I give workload numbers, to the community sources I trust. If a spec isn’t sourced, it isn’t here.

The official minimum vs recommended requirements

Proxmox publishes two tiers on its hardware requirements page: a bare minimum for evaluation and testing, and a recommended set for production. Here is exactly what they list, plus the ZFS guidance from the Proxmox wiki:

Component	Official minimum (eval/test)	Recommended (production)	Practical homelab target
CPU	64-bit Intel 64 / AMD64 with Intel VT-x / AMD-V	Intel 64 / AMD64 with VT-x / AMD-V flag	Any modern x86; N100/N150 mini-PC chip is fine
RAM	Minimum 1 GB	2 GB for OS + services, plus RAM for each guest	16-32 GB to start
ZFS / Ceph RAM	n/a	Approx. 1 GB extra per TB of used storage	+1 GB per TB on top of guest RAM
System disk	A hard drive	Fast, redundant storage; SSDs preferred	SSD/NVMe for OS + VM storage
Network	One NIC	Redundant Gbit NICs; 10 GbE+ supported	1x Gbit is fine for most homelabs
Passthrough	n/a	CPU with VT-d / AMD-Vi (IOMMU) flag	Needed only for GPU/NIC passthrough

Source: Proxmox VE Hardware Requirements and the Proxmox ZFS on Linux wiki.

The key takeaway from the official page: there are no exotic requirements. As one long-standing Proxmox forum answer puts it, “Proxmox doesn’t have any major hardware requirements — the cpu and bios should support Intel VT or AMD-V but that’s pretty standard these days.” The minimum column is real but misleading — 1 GB boots the host and leaves nothing for guests. The recommended column is where you should start planning.

CPU: what “VT-x / AMD-V” actually means

Proxmox needs a 64-bit x86 processor with hardware-assisted virtualization. On Intel that flag is VT-x; on AMD it is AMD-V. This is standard on every desktop, server, and mini-PC CPU made in roughly the last ten years — including the budget Intel N100 and N150 chips that dominate cheap homelab mini PCs. The one thing to check is that virtualization is enabled in the BIOS/UEFI, because some vendors ship it off.

If you intend to pass a whole GPU or NIC into a VM, you need a second flag: IOMMU, which Intel calls VT-d and AMD calls AMD-Vi. This is a board-and-CPU feature, not just a CPU one, so verify both support it before buying for a passthrough build.

RAM: the formula that actually matters

Proxmox’s own rule is simple: about 2 GB for the OS and services, then add the memory you assign to each VM and container on top. The host overhead is small; your guests dominate the total.

The exception is ZFS, which is covered below — it wants meaningful RAM of its own. If you are not using ZFS, you can size RAM as “2 GB for Proxmox + the sum of your guest allocations + a small buffer.”

Storage: SSD over capacity, every time

The official minimum is one hard drive. The recommendation is fast and redundant storage, with SSDs explicitly called out for best results. For data integrity Proxmox recommends either hardware RAID with a battery-backed write cache (BBU) or non-RAID disks managed by ZFS.

For a homelab, the pattern that works: a small SSD or NVMe for the Proxmox OS, and a separate SSD/NVMe drive or ZFS pool for your VM and container disks. If that pool is ZFS, size endurance as well as capacity — copy-on-write write amplification consumes a drive’s rated TBW faster than the host write numbers suggest, which the SSD endurance calculator lets you model. Spinning hard drives are fine for bulk media storage on a NAS, but running VM root disks off a single HDD makes every guest feel sluggish.

The ZFS RAM rule, verified

ZFS is where homelab RAM folklore goes wrong, so here is the real current guidance from the Proxmox ZFS on Linux wiki:

ZFS “depends heavily on memory, so you need at least 8 GB to start.”
The sizing rule is 2 GiB base + 1 GiB per TiB of storage. So an 8 TiB pool wants about 10 GiB reserved for the ARC.
Since Proxmox VE 8.1, the ZFS ARC default is 10% of host RAM, capped at 16 GiB — much lower than the old “use half your RAM” behavior, which is why ZFS feels less RAM-hungry on recent installs than its reputation suggests.
You can hard-cap the ARC by setting zfs_arc_max in /etc/modprobe.d/zfs.conf (for example options zfs zfs_arc_max=8589934592 for an 8 GiB cap), then rebooting.

The old “1 GB per TB” number you see everywhere is a reasonable rule of thumb and matches the headline figure Proxmox uses for ZFS/Ceph on its requirements page. The wiki’s “2 GiB base + 1 GiB/TiB” is the more precise version. Either way: ZFS RAM is on top of your guest RAM, not shared with it. If you are deciding between ZFS, TrueNAS, and Unraid as your storage backend, the storage backend comparison walks through the tradeoffs.

The practical rule homelabbers repeat on the Proxmox and r/homelab forums follows straight from that math: if a box has less than 8 GB of RAM, skip ZFS and use ext4 or LVM-thin for the system disk instead. ZFS on a memory-starved host spends RAM you needed for guests and still cannot cache the pool well, so you get the complexity without the speed. Reserve ZFS for boxes with 16 GB or more, and always size the ARC on top of your guest allocations, never carved out of them.

ECC RAM is recommended for ZFS but not strictly required — for a learning homelab, non-ECC is fine; for anything holding data you care about, ECC is the safer call.

What you actually need, by workload

Specs in a vacuum don’t help. Here is how the requirements scale with what you are actually running. These are homelab-oriented targets, not enterprise sizing.

The RAM math is where the “scales with workload” idea stops being abstract. Both builds below start with the same ~2 GB Proxmox base at the bottom of the tank. What separates a box that is happy on 32 GB from one that wants 64 GB is almost entirely one segment — the ZFS ARC cache — plus a couple of heavier VMs stacked on top.

The RAM budget, stacked

Two real homelab builds, filled from the bottom up on the same scale (5 px = 1 GB). Same Proxmox base in both. The thing that doubles the box is the ZFS ARC cache plus heavier VMs — not the hypervisor.

Typical first homelab

uses ~12 of 32 GB

VM 4

12 GB

ZFS NAS + a stack of VMs

uses ~30 of 64 GB

ZFS ARC
10

3 app VMs · 9

Win/NVR VM 6

30 GB

Proxmox host (~2 GB base) LXC containers (light) Virtual machines Media / NAS services ZFS ARC — the swing factor

Drop ZFS and the second build loses ~10 GB instantly and fits a 32 GB box. Keep ZFS on a big pool and the ARC alone can outweigh every container you run. That is why "how much RAM for Proxmox?" has no single answer — the base is fixed, your guests and your storage engine decide the rest.

techfuelhq.com · illustrative allocations; ZFS ARC sized by the 2 GiB + 1 GiB/TiB rule for an 8 TB pool

A file server / NAS (a few shares, light use)

A single mini PC with an Intel N100/N150, 8-16 GB RAM, and one or two drives handles a basic file server easily. If you run that NAS on ZFS, push RAM toward 16 GB and follow the ZFS rule above for the pool size. CPU load for plain file serving is trivial; RAM for ZFS ARC is the thing to size, not cores.

A handful of VMs and containers (the typical first homelab)

This is where most people land: Pi-hole or AdGuard, a reverse proxy, Home Assistant, a few Docker stacks, maybe one or two small VMs. 16 GB of RAM is a comfortable floor and 32 GB gives real breathing room. A 4-core mini PC is plenty because most of these services idle. Lean on LXC containers rather than full VMs wherever you can — a bare Debian container uses roughly 30-60 MB of RAM versus 200-400 MB for the equivalent VM, so an LXC-heavy lab fits far more services into the same box. The LXC vs VM decision guide covers exactly when to use each. To size this precisely for your specific RAM and core count, the Proxmox capacity planner does the math for you.

Plex / Jellyfin with hardware transcoding

Media transcoding is the one workload where the GPU question matters, and the answer is an Intel integrated GPU, not a discrete card. Jellyfin’s official Intel hardware-acceleration docs state that Intel Quick Sync Video (QSV) is the preferred method on mainstream Intel GPUs for better performance, supported on Broadwell (5th-gen Core) and newer.

In practice, the Intel N100 iGPU with Quick Sync handles roughly 3-4 simultaneous 4K-to-1080p transcodes, or about 8 streams at 1080p, which is more than enough for a household and even a few remote users. That is why the N100/N150 mini PC has become the default budget media-server platform — you get hardware transcoding without buying or passing through a GPU. RAM-wise, the transcode itself is light; size RAM for everything else you run alongside it.

A ZFS NAS plus VMs on one box

Combining a ZFS storage pool with a stack of VMs is the most RAM-hungry homelab pattern, because you pay for both. Add up: ~2 GB for Proxmox, your ZFS ARC (2 GiB + 1 GiB per TiB of pool), and the RAM for every guest. A 4 TB ZFS pool running half a dozen VMs realistically wants 32 GB and is happier at 64 GB. This is the build where stepping up to a used enterprise box or a higher-RAM mini PC pays off.

Do you need a GPU? (Almost never)

For Proxmox itself: no. The hypervisor is headless and managed through a web UI from your laptop, so the host needs no graphics card and is happy with integrated graphics or no display output at all. Adding a discrete GPU to a Proxmox host does nothing for the host.

You add a GPU only for a guest:

Hardware transcoding for Plex/Jellyfin — and even then, an Intel iGPU with Quick Sync is the right tool, not a discrete card.
GPU passthrough to a VM for gaming, video editing, or local AI inference — this needs the IOMMU (VT-d/AMD-Vi) flag and a VM, not a container.

If neither of those is on your roadmap, skip the GPU entirely and spend the money on RAM and SSD instead.

What Proxmox VE 9 changes (and what it doesn’t)

Proxmox VE 9.0 was released on August 5, 2025 on Debian 13 “Trixie” with the Linux 6.14 kernel. The current stable release is VE 9.2 (May 21, 2026), which moves to the Linux 7.0 kernel on Debian 13.5 — VE 9.1 (November 2025, kernel 6.17) sat in between. VE 8.4 was the final 8.x release, and its maintenance window closes around August 2026. If you are building fresh in 2026, there is no reason to start on 8.x — install 9.2 directly.

The hardware requirements themselves did not change — VE 9 still wants a 64-bit VT-x/AMD-V CPU, the same RAM and disk minimums, and a NIC. What changed is underneath: a newer kernel for better hardware support, plus a handful of breaking changes (LVM autoactivation defaults, possible network-interface renames, PCI-passthrough quirks on the new kernel). If you are upgrading an existing box rather than installing fresh, read the Proxmox VE 8 to 9 upgrade gotchas first — the “requirement” for a clean VE 9 upgrade is doing the pre-flight checks, not new hardware.

Putting it together: a sane 2026 homelab baseline

If you want a single recommendation that covers most first homelabs without overbuying:

CPU: an Intel N100/N150 mini PC (VT-x, Quick Sync for transcoding) or a used small-form-factor desktop.
RAM: 16 GB minimum, 32 GB if you can — and more if you run ZFS or many VMs.
Storage: an SSD or NVMe for the OS and VM disks; add bulk drives only for media/NAS storage.
Network: one Gigabit NIC is fine; 10 GbE only matters if you are moving large files between machines constantly.
GPU: none, unless you are passing one through or want discrete transcoding muscle.

For the full hands-on walkthrough from USB installer to first VM on exactly this kind of box, see the Proxmox mini PC setup guide, and for picking the actual hardware, the best mini PCs for a homelab in 2026 breaks down the current options. If you would rather hit these specs cheaply with used enterprise gear, the $800 Proxmox server from refurbished parts walks three builds that meet the recommended targets above.

Sources

Proxmox VE Hardware Requirements — official minimum and recommended CPU, RAM, storage, network, and the ZFS/Ceph “1 GB per TB” note.
Proxmox VE System Requirements wiki — the wiki mirror of the same requirements.
Proxmox ZFS on Linux wiki — ZFS “at least 8 GB” guidance, the “2 GiB base + 1 GiB/TiB” rule, the 10%-capped-at-16-GiB ARC default since VE 8.1, and zfs_arc_max.
Proxmox Virtual Environment 9.0 release (Aug 5, 2025) — VE 9 on Debian 13 Trixie, kernel 6.14, and the VE 8.4 support window to August 2026.
Jellyfin Intel hardware acceleration docs — Intel Quick Sync (QSV) as the preferred transcoding path, Broadwell and newer.

Sizing a specific box? The Proxmox capacity planner tells you how many VMs and containers your RAM, cores, and ZFS ARC allocation can actually support. Deciding between containers and full VMs for each service? The LXC vs VM guide has the decision tree. Ready to build? Start with the best mini PCs for a homelab and the Proxmox mini PC setup walkthrough.

ROG STRIX B650-A Gaming WiFi Review: AM5 ATX for the Homelab

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~11 min read · St. Louis County, MO

Rating: 4.2 / 5

The ROG STRIX B650-A was the board I ran under a Ryzen 7 7800X3D in my primary build for an extended period. It’s an ATX AM5 board at a price point ($279–319 at time of purchase) that competes against X670 non-E boards rather than budget B650M options. This review reflects real-world use rather than a synthetic first-look.

Specs from ASUS product page

(Per ASUS ROG STRIX B650-A product page, accessed 2026-06.)

Socket: AM5 (LGA1718)
Chipset: AMD B650
Form factor: ATX (305 × 244 mm)
Memory: 4× DDR5 DIMM, dual-channel, up to 192GB (unofficial Samsung B-die boards go higher), up to DDR5-8000+ OC
Power delivery: 12+2 teamed power stages
PCIe slots: PCIE_x16_1 (PCIe 5.0 x16), PCIE_x16_2 (PCIe 4.0 x4, keyed as x16), PCIE_x1_1 (PCIe 4.0 x1)
M.2 slots: 4× (1× PCIe 5.0 x4, 2× PCIe 4.0 x4, 1× PCIe 4.0 x2/SATA)
USB (rear I/O): 2× USB 3.2 Gen 2x2 (20 Gbps), 2× USB 3.2 Gen 2 (10 Gbps), 2× USB 3.2 Gen 1 (5 Gbps), 2× USB 2.0; 1× USB 3.2 Gen 2 Type-C
LAN: Intel I226-V (2.5 GbE)
WiFi: Intel AX210 (WiFi 6E, Bluetooth 5.3)
Audio: SupremeFX ALC4082, SABRE9018Q2C DAC
Display output: HDMI 2.1, DisplayPort 1.4 (for integrated graphics / APU use)

Power delivery for the 7800X3D

The B650-A’s 12+2 teamed power delivery is more than the 7800X3D requires. The chip’s max socket power (PPT) is 162W — AMD rates the TDP at 120W — with typical gaming loads running closer to 100–130W. The 12+2 configuration means the 7800X3D’s power draw is split across enough phases that no single phase runs hot.

Under sustained Cinebench R23 multi-core loads (which push the 7800X3D to its sustained limits), the VRM heatsink on the B650-A stayed below the concerning threshold. Under normal gaming loads — which is what the 7800X3D is built for — the power delivery was a non-event. For an X3D chip, B650 power delivery is sufficient by a wide margin.

If you’re considering this board for a 7950X or 7900X (AMD’s higher-TDP flagship chips), the 12+2 teamed stages are adequate but the thermal situation gets tighter under sustained AVX workloads. The B650-A is not the wrong choice for those chips, but the premium X670E boards have more headroom.

DDR5 tuning with EXPO

EXPO (AMD’s equivalent to Intel’s XMP for DDR5) posted first-time with my own DDR5-6000 kit, and the board’s QVL covers the common DDR5-6000/6400 CL30–32 families from Corsair, G.Skill, and Kingston. Enable EXPO in BIOS → Ai Tweaker → Ai Overclock Tuner.

ASUS’s Ai Tweaker UI is the best RAM timing interface on any AM5 board. Subtimings are individually accessible with descriptions, the memory training log is readable, and the BIOS saves manual overrides reliably across reboots. X670E Extreme boards have more advanced Curve Optimizer tools, but for DDR5 tuning at the EXPO profile level, the B650-A is equivalent.

One note: DDR5-6000 is the sweet spot for Ryzen 7000/9000 series. AMD’s memory controller in AM5 chips runs best with EXPO profiles at DDR5-6000 (1:1 fabric ratio). DDR5-6400 and above often requires loosening subtimings to maintain stability, and the bandwidth gain over 6000 is minimal. The B650-A’s memory training handles 6000 EXPO kits first-boot; 6400+ EXPO kits sometimes need a training cycle.

PCIe layout for homelab and multi-device builds

The slot layout matters more than it sounds. Most ATX AM5 boards have:

Slot 1: PCIe 5.0 x16 (GPU)
Slot 2: PCIe 4.0 x4 (second card, labeled as x16)
Slot 3: PCIe 4.0 x1

For a build pairing a primary GPU with a 10GbE NIC (Mellanox ConnectX-3, Intel X550, etc.), the B650-A’s PCIE_x16_2 at PCIe 4.0 x4 is sufficient — a 10GbE NIC saturates at under 10 Gbps bidirectional, which is well within the ~32 Gbps ceiling of PCIe 4.0 x4. No bandwidth limitation exists in practice.

For a build running a GPU plus a PCIe 4.0 x4 NVMe expansion card (adding SSD slots for a NAS-style build), same logic applies.

One limitation: PCIE_x16_2 shares bandwidth with M.2 slot 3. When a card is installed in PCIE_x16_2, M.2 slot 3 may disable depending on the configuration. Check the ASUS manual for the sharing rules before planning a build that uses both simultaneously.

BIOS quality

BIOS quality is where ASUS earns its premium over competing B650 boards. The ROG STRIX B650-A shipped with BIOS 1404 and received updates through the 2400-series by 2026. Key positives:

EXPO implementation: reliable first-boot memory training, no repeated failed boots
Fan control: per-header curves, temperature source selectable per header (CPU package, CPU socket, VRM, etc.)
POST time: about 25–30 seconds cold boot with DDR5-6000 EXPO kit — slightly longer than B550 era but normal for DDR5 training
Secure Boot: fully compatible with Windows 11 and easy to configure for Linux dual-boot

Negatives:

AI Overclocking (AiO, ASUS’s automated OC): marketing feature. The AI overclock profiles apply preset PBO values that you can configure manually in 10 minutes. It’s not generating novel configurations; it’s selecting from a table.
BIOS interface at 4K: the ASUS BIOS does not scale to 4K monitors cleanly when connected during POST. It renders at a fixed resolution that looks blurry on large displays. This is an industry-wide problem, not B650-A-specific, but it’s annoying on a 4K setup.

Build quality and I/O

The rear I/O shield is integrated into the board — no separate I/O plate to install, which is now standard on premium boards. The included 2× USB 3.2 Gen 2×2 (20 Gbps) ports are useful for fast external SSDs; not something every B650 board includes.

The M.2 Shield (thermal covers for all four M.2 slots) are well-designed — tool-less removal for slots 2 and 3, single-screw removal for slot 1. Drive installation is easier than any previous AM4 board I’ve used with non-standard M.2 retention mechanisms.

Audio (SupremeFX ALC4082 + ESS SABRE DAC): noticeably better than the typical Realtek implementation. Negligible noise floor for the headphone amplifier out of the rear audio jack. If you’re running a DAC externally (USB or optical), this doesn’t matter — but for a build where you occasionally plug headphones directly into the PC, the B650-A’s onboard audio is better than you’d expect from a gaming board.

What ASUS got wrong

Aura Sync RGB: the addressable RGB headers (2× ARGB) and standard RGB header work fine, but Aura Sync — ASUS’s software for coordinating RGB across components — is another background-process-heavy utility like NZXT CAM. If you’re not invested in RGB coordination across an ASUS ecosystem, the Aura Sync software is usable only at startup and then killed.

Fan header placement: the CPU fan header and CPU OPT header are both at the top of the board near the CPU socket. Three of the chassis fan headers are at the bottom of the board. Routing cables from bottom case fans to bottom-board headers is fine, but routing the AIO pump (which goes to CPU OPT) down from a top-mounted radiator means cable management gets complicated in some cases.

Quantity of bundled connectors: the B650-A ships with ARGB splitter cables and fan extension cables but no M.2 drive screws. Screw count is 4 per slot, 16 total — barely enough if you populate all four M.2 slots with 2280 drives.

Versus the competition

At the B650 ATX tier ($200–320):

Board	Key differentiator	Street
ASUS ROG STRIX B650-A	12+2 teamed VRM, best BIOS UI, WiFi 6E	~$280
MSI MAG B650 TOMAHAWK	16+2+1 VRM, more fan headers, no WiFi	~$210
Gigabyte B650 AORUS Elite AX	Solid VRM, onboard WiFi, slightly lower build quality	~$220
ASRock B650E Taichi	Premium build, 24+2+1 VRM, Thunderbolt 4	~$340

The MSI TOMAHAWK is the strongest value competition — its 16+2+1 VRM has higher total thermal capacity than the B650-A’s 12+2 teamed configuration (though both handle the 7800X3D without strain), and its fan header count is higher. The TOMAHAWK trades the B650-A’s BIOS quality and WiFi inclusion for lower cost.

For a homelab builder where BIOS stability and RAM tuning reliability matter, the B650-A justifies its premium over the TOMAHAWK. For a dedicated gaming build where BIOS tinkering is minimal, the TOMAHAWK at $60 less is harder to argue against.

Verdict

The ROG STRIX B650-A is the right board if you’re building an AM5 ATX system with a Ryzen 7 7800X3D and want reliable EXPO memory training, good power delivery, and ASUS’s BIOS — which remains the best DDR5 tuning interface on any AM5 platform. The WiFi 6E inclusion and premium I/O (20 Gbps USB) add value without requiring you to buy a more expensive X670 board.

It’s not perfect — Aura Sync is unavoidable if you use ARGB headers, the fan header placement requires cable routing decisions, and the AI overclocking marketing overstates what the feature actually does. But the fundamentals are strong, and a board you can trust to boot reliably with a loaded DDR5 kit is worth something.

Rating: 4.2/5. Recommended for AM5 ATX builds pairing a 7000/9000-series CPU with a 360mm AIO and DDR5-6000 memory. The BIOS alone is worth the premium over budget B650 boards.

The NZXT Kraken 360 review covers the cooler this board ran under. For a full system build around the 7800X3D platform, the PC Builder tool checks socket, RAM slot, and PCIe slot compatibility. For repurposing this class of hardware as a Proxmox server when upgrading, the repurpose gaming PC guide covers the full Proxmox setup from an existing desktop.

Self-Hosted AI in 2026: The Stack and How to Start

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~13 min read · St. Louis County, MO

Self-hosted AI is the simple idea that you run the model on your own box instead of renting someone else’s. The prompt you type and the answer you get back never touch a third-party server. There is no API key, no monthly token bill, no rate limit, and the thing keeps working when your internet is down. In 2026 that is no longer a research project — it is a weekend install on hardware you may already own.

This page is the map, not the deep dive. Local AI now spans four practical categories — chat and text (local LLMs), image generation, speech (transcription and synthesis), and coding assistants — plus the one question that decides everything: how much GPU you need. I’ll lay out the real, current tools in each lane, who each is for, and where to start. Where there’s a number to get exactly right — which model fits which card, tokens per second, the cost math — I link down to the deep dives on this site rather than re-deriving it here.

A note on honesty up front, because the field is loud with hype: self-hosted models are not as good as the best hosted models for the hardest tasks, and pretending otherwise wastes your weekend. The trade you are actually making is covered next.

Why self-host AI — and the honest tradeoffs

Three real reasons people self-host, and three real costs.

The reasons:

Privacy. Financial questions, draft emails about coworkers, proprietary code, half-formed business ideas — none of that has to sit in a third-party log file. For sensitive workloads, local isn’t just cheaper past a break-even point, it’s the only option that keeps data off external servers.
Cost and no rate limits. Once the hardware is paid for, inference is free at the margin. Heavy users running summarization pipelines, coding assistants, or batch jobs stop watching a token meter.
Control. You pick the model, the quantization, the system prompt, and the version. Nothing gets deprecated out from under you, and the model runs offline.

The tradeoffs:

Capability ceiling. As the r/LocalLLaMA and r/selfhosted crowd will tell you plainly, a single consumer GPU won’t match a frontier hosted model on the hardest reasoning and agentic tasks. An 8B–32B open-weight model is excellent for everyday work and noticeably weaker at the top end.
Upfront hardware. The privacy and cost wins are real, but they sit behind a GPU purchase. The break-even math depends entirely on how much you actually use it.
You are the ops team. Drivers, model downloads, container updates, and the occasional out-of-memory error are now your problem. That is a feature if you enjoy a homelab and a cost if you don’t.

The pattern most people settle into: local for volume and anything sensitive, cloud for the occasional genuinely hard problem. With that framing set, here are the four categories.

Category 1 — Local LLMs (chat, text, RAG)

This is the heart of self-hosted AI and where almost everyone starts. You run an open-weight large language model through a runner, and optionally point a chat UI at it.

The runners, by friction tolerance — all built on, or alongside, the same llama.cpp foundation:

Ollama — a daemon wrapping llama.cpp with a clean CLI and model registry. ollama pull qwen3 and you’re chatting in under a minute. It exposes an OpenAI-compatible API on port 11434, so existing tools point at it without code changes. This is the default starting point for one-developer use on any OS. (daily.dev)
LM Studio — a desktop GUI over llama.cpp (and MLX on Mac), with one-click model downloads and a built-in OpenAI-compatible server. Best for a GUI-first experience on Windows or Mac. (codersera)
llama.cpp — Gerganov’s original C/C++ inference engine. The most control over quantization, batch size, and GPU layers; the most setup. Drop down to it for embedded or unusual-hardware deployments. (codersera)
vLLM — a high-throughput serving system using PagedAttention and continuous batching. In benchmark testing it reached roughly 16–20x Ollama’s concurrent throughput, but it’s API-only and aimed at multi-user production on NVIDIA or AMD GPUs — overkill for a single-user box. (InsiderLLM)
Open WebUI — not a runner but the front end most people pair with Ollama: a self-hosted, ChatGPT-style browser interface. The Ollama + Open WebUI combination is the single most popular local AI stack in 2026. (Google AI Overview / VirtualizationHowto)

Who it’s for: anyone who wants a private chat assistant, RAG over personal documents, or an OpenAI-API drop-in for their own scripts. Start with Ollama plus Open WebUI; reach for vLLM only when you’re serving several people at once.

On models: the dependable open-weight families in 2026 are Alibaba’s Qwen3 / Qwen3.5 (Apache 2.0), OpenAI’s GPT-OSS (20B designed for 16GB cards; 120B for data-center GPUs), Meta’s Llama, DeepSeek, Mistral Small, and Google’s Gemma 3. (Hugging Face) The roster of “newest and best” shifts month to month, so the durable advice is to match the model family to your VRAM rather than chase releases — which is exactly the question the next section answers, and which our local-LLM-by-GPU-VRAM guide maps out tier by tier with real GGUF file sizes.

Category 2 — Image generation

The self-hosted image stack has consolidated around the Stable Diffusion family and Flux, driven through one of two interfaces:

ComfyUI — a node-based interface that exposes the full generation pipeline. The pick when you need complex workflows, custom nodes, or to serve generation in a repeatable way. Steeper to learn, far more powerful. (SingularityByte)
AUTOMATIC1111 (and the Forge fork) — a Gradio-based web UI. Install it, load a model, start generating in minutes. The beginner-friendly path. (offlinecreator)

On models, the community split in 2026 is roughly: Flux (from Black Forest Labs) for the best current photorealism if your card has 12GB+ of VRAM, and SDXL or Stable Diffusion 3.5 checkpoints — often fine-tuned versions pulled from Civitai — for stylized, illustrated, or anime output with the broadest community support. (BentoML, Awesome Agents)

Who it’s for: anyone generating images who wants no per-image cost, no content filter they didn’t choose, and full control over models and LoRAs. Image generation is VRAM-hungry — the better Flux models want 12–16GB+ — so it leans on the same hardware question as LLMs.

Category 3 — Speech (transcription and synthesis)

Two halves: speech-to-text (STT) and text-to-speech (TTS).

Whisper (OpenAI’s open-source model, released 2022) remains the best general-purpose self-hosted transcription system three-plus years on. You run it through the original Python package, whisper.cpp (a C/C++ port from the team behind llama.cpp), or faster-whisper, which delivers transcription several times faster than the reference implementation. (Northflank)
TTS — for synthesis, Piper and Kokoro are the common lightweight open-source choices, covering 20+ languages. Integrated servers like Speaches bundle faster-whisper for STT and Piper/Kokoro for TTS behind an OpenAI-compatible API — “like Ollama, but for audio.” (Northflank)

Who it’s for: anyone transcribing meetings, podcasts, or voice notes who doesn’t want audio leaving the machine, plus voice-assistant and dictation builders. Whisper’s smaller models run fine on CPU; the large model benefits from a GPU.

Category 4 — Coding assistants

A self-hosted coding assistant gives you Copilot-style completion and chat with the model running on your own hardware:

Tabby — an open-source, self-hosted assistant explicitly built as a Copilot alternative. It ships an admin dashboard and SSO, runs models locally by default (it can use Ollama as a backend), and plugs into VS Code and JetBrains. The clearest pick for a team that needs an air-gapped or fully self-hosted setup. (TabbyML on GitHub)
Continue — a VS Code and JetBrains extension that points at your local Ollama model from a single shared config. The best-supported individual-developer option. (Second Talent)
Aider / Cline — terminal-and-editor agentic tools that also run against a local Ollama endpoint.

On models, Codestral (Mistral) and DeepSeek Coder lineages are the strongest local coding picks, and Qwen3-Coder is a capable agentic option. (Second Talent) Be realistic: as that same comparison notes, self-hosted coding tools in 2026 are genuinely usable but still trail the best cloud assistants on the hardest tasks. They shine when you can’t send code to the cloud, or when per-seat pricing gets expensive.

Who it’s for: privacy-bound or air-gapped teams (Tabby), and individual developers who want free, local completion (Continue + Ollama).

The hardware question: what GPU and VRAM you need

Every category above is gated by the same thing: GPU VRAM, because the model has to fit in the card’s memory for full-speed inference. I’m not going to re-derive the numbers here — this site already has the authoritative breakdowns, and duplicating them would just risk drift. The short version:

8GB (RTX 3060, 4060) — comfortable for 7–8B chat and coding models. The entry tier.
16GB (RTX 4060 Ti 16GB, 5060 Ti, 5080) — 14B models plus a 20B mixture-of-experts like GPT-OSS-20B, and enough for the better Flux image models.
24GB (RTX 3090, 4090) — the single-card sweet spot, running ~32B models with room for context.

For the full tier-by-tier map with real GGUF file sizes and the math behind them, see which local LLM fits your GPU by VRAM, and to check a specific model-and-card combination before you download anything, run it through the LLM VRAM calculator. If you’re picking hardware, the $1,000 local AI workstation build lays out a real parts list and the cloud-vs-local cost math at the 16GB tier. CPU and system RAM matter far less than the GPU — any modern 6-core CPU with 32GB of RAM is plenty for a pure inference box.

How to start in an afternoon

You don’t need the workstation to begin. The fastest honest path, on a homelab box or spare PC with an NVIDIA GPU:

Install Ollama. On Linux: curl -fsSL https://ollama.com/install.sh | sh. It registers a service listening on localhost:11434. (On Windows, the LM Studio one-installer path is friendlier — the single-RTX-5060 walkthrough covers both end to end, including the Blackwell-driver gotcha that silently drops you to CPU.)
Pull a model that fits your card. ollama pull qwen3 for a general 8B, or a smaller model if you’re on 8GB. Check fit first with the VRAM calculator.
Test it. ollama run qwen3 "Summarize the tradeoffs of self-hosting an LLM." First token in about a second on a modern GPU.
Add a UI. Run Open WebUI in Docker and point it at Ollama for a ChatGPT-style interface on your LAN. The official n8n self-hosted AI starter kit bundles Ollama, Open WebUI, and a workflow engine in one Docker Compose file if you’d rather start from a template. (n8n on GitHub)

That’s a working private chat assistant in an afternoon. From there, the natural progression is to run it as a proper always-on service. A small hypervisor host is the clean way to do that — our Proxmox-on-a-mini-PC setup guide gets you from a USB installer to a first VM in under an hour, and once you’re comfortable hosting one service you’ll want the rest of the self-hosted toolbox: the self-hosted apps that replace SaaS covers the photo, notes, and password managers that pair naturally with a local AI box.

Where to go next

New to all of this and unsure what fits your card? Start with which local LLM fits your GPU by VRAM.
Ready to actually install on a specific GPU? The self-host a local LLM on an RTX 5060 tutorial is the hands-on path.
Picking hardware? The $1,000 local AI workstation build guide has the parts list and the break-even math.
Want the host to run it on? Set up Proxmox on a mini PC, then fill it with self-hosted apps that replace SaaS.

Self-hosted AI in 2026 isn’t one tool — it’s a small stack of mature, mostly free, mostly open-weight pieces, gated by how much GPU you’re willing to buy. Pick the category you actually need, match the model to your VRAM, and start with Ollama on a box you already own.

Working out of St. Louis County. Running a different self-hosted AI stack — a model, runner, or hardware combo worth comparing notes on? Send your config to hello@techfuelhq.com.

Sources

Google AI Overview for “self-hosted AI” (Ollama + Open WebUI as the easiest stack; VRAM guidance; n8n): cited inline.
daily.dev, “Running LLMs Locally in 2026: Ollama, llama.cpp, and Self-Hosted AI for Developers”: https://daily.dev/blog/running-llms-locally-ollama-llama-cpp-self-hosted-ai-developers/
Codersera, “Ollama vs LM Studio vs vLLM vs llama.cpp vs MLX 2026”: https://codersera.com/blog/ollama-vs-lm-studio-vs-vllm-vs-llama-cpp-vs-mlx-2026/
InsiderLLM, “llama.cpp vs Ollama vs vLLM: One User vs Many (2026)”: https://insiderllm.com/guides/llamacpp-vs-ollama-vs-vllm/
Hugging Face, “The Best Open Source and Open-Weight LLM Models to Run Locally in 2026”: https://huggingface.co/blog/daya-shankar/open-source-llm-models-to-run-locally
SingularityByte, “AI Image Generator Showdown 2026: Stable Diffusion, Flux, and ComfyUI”: https://singularitybyte.com/tutorials/ai-image-generator-stable-diffusion-vs-flux-vs-comfyui-2026.html
BentoML, “The Best Open-Source Image Generation Models in 2026”: https://www.bentoml.com/blog/a-guide-to-open-source-image-generation-models
Northflank, “Best open source speech-to-text (STT) model in 2026 (with benchmarks)”: https://northflank.com/blog/best-open-source-speech-to-text-stt-model-in-2026-benchmarks
TabbyML, “Self-hosted AI coding assistant” (GitHub): https://github.com/TabbyML/tabby
Second Talent, “Top 7 Open-Source AI Coding Assistants in 2026”: https://www.secondtalent.com/resources/open-source-ai-coding-assistants/
n8n, “Self-hosted AI Starter Kit” (GitHub): https://github.com/n8n-io/self-hosted-ai-starter-kit

Servers for a Homelab (2026): Which One to Buy

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~12 min read · St. Louis County, MO

Search “homelab server” and you fall straight into a Reddit thread, a “what is a homelab” explainer, or one person’s build log. None of them answer the question you actually have: out of all the things people call a homelab server, which one should you buy? This page is the routing map. It frames the five real classes of server, tells you in a paragraph who each one is for, gives you a decision rule you can apply in two minutes, and then points you down to the detailed guide for whichever class fits.

This is a chooser, not a spec sheet. Where a class deserves a full breakdown, the deep-dive lives on its own page and is linked inline.

Start here: what kind of server do you actually need?

A “homelab server” is just a computer you run at home to host services and to learn on. The hardware can take five broadly different shapes, and the right one is decided almost entirely by three questions:

Where does it live? A living room, office, or bedroom rules out anything loud. A basement, closet, or garage with a door opens up the noisy options.
What does it run? A handful of containers and a couple of VMs needs very little. Many VMs, big storage, or local AI changes the answer.
What do you care about — quiet and cheap-to-run, or capacity and expandability? You usually cannot max out both at once.

Hold those three answers in your head as you read the classes below. If you are not sure how much hardware your workload actually needs, the Proxmox hardware requirements guide translates “I want to run X” into real CPU, RAM, and storage numbers — read that first if you are starting from zero.

The five classes of homelab server

1. New mini PC — the default first server for most people

A modern mini PC (an Intel N150 box, a Beelink, an ASUS NUC, or a Minisforum MS-01) is a full x86 computer the size of a paperback. It runs Proxmox, idles in the single-to-low-double-digit watts, and is effectively silent. You buy it, add RAM and an NVMe drive, and you are done — no parts list, no assembly.

Who it’s for: Anyone whose server lives in a living space, anyone who wants a clean “it just works” box, and anyone running a normal homelab of a dozen-or-so containers and a few VMs. The MS-01 in particular adds dual 10GbE for people who want real network virtualization. The main ceiling is RAM (typically 64–96 GB) and a single small chassis.

For specific models, idle-power figures, and which tier to buy, see Best Mini PC for a Homelab 2026.

2. Used small-form-factor (SFF) desktop — the cheapest legitimate way in

A used Dell OptiPlex Micro, HP EliteDesk Mini, or Lenovo ThinkCentre Tiny is the value entry point. These are ex-corporate machines with 8th-gen-or-newer Intel chips, built to run reliably on an office desk for years, and they sell for well under $200 on eBay. Add a stick of RAM and an SSD and you have a real Proxmox host for the price of a video game console.

Who it’s for: Budget-first builders, anyone who wants to learn what Proxmox feels like before spending real money, and cluster-curious people who want three nodes for high-availability practice without a $1,500 bill. The trade-offs are older platforms, usually a single gigabit NIC, and a lower RAM ceiling (often 32 GB) — fine for a single node, limiting once you cluster.

These used SFF picks are covered alongside the new mini PCs in the mini PC homelab guide (the value tier), since they compete in the same quiet, low-power category.

3. Used enterprise tower or rack server — capacity, at a cost

This is the romanticized option: a 2013-era Dell PowerEdge or HP ProLiant with 128 GB of RAM and eight drive bays for a couple hundred dollars. It is genuinely unbeatable on RAM-per-dollar, drive density, and out-of-band management (iDRAC / iLO lets you manage the box remotely as if you were standing at it). What the sticker price hides is the running reality: a rack server idles far louder and far hungrier than a mini PC, and that gap compounds every hour of every day it runs.

Who it’s for: People who genuinely need a high RAM ceiling cheaply (many simultaneous VMs, large databases, lab environments), 8+ drive bays in one chassis, or remote management — and who have a basement, closet, or dedicated room where noise does not matter. A tower server (HP ML-series, Dell T-series) is the quieter, more home-friendly subset of this class; a 1U/2U rack is the loudest.

Before you buy on the cheap-RAM pitch alone, read the honest head-to-head: Used Enterprise Server vs Mini PC for Homelab. It runs the full noise, power, RAM, and three-year ownership math so you can see exactly when the enterprise box wins and when it does not.

4. DIY build — Mini-ITX or a used-parts server

If no off-the-shelf box fits, you build one. There are two flavors. A Mini-ITX build gives you a full desktop CPU, a real PCIe x16 slot for a GPU (AI inference, hardware transcode, a gaming VM), standard DIMMs, and more storage slots than a mini PC — in a shelf-sized case. A used-parts build chases maximum capability per dollar by mixing second-hand enterprise or consumer components into a tower.

Who it’s for: Builders who want a discrete GPU, more than ~64 GB of RAM, or expansion cards, and who are comfortable picking parts and assembling. The cost is money (ITX motherboards and cases carry a premium) and effort (you are the integrator and the warranty). It is the next step up from a mini PC, not the starting point.

Two routes, two guides: the Mini-ITX homelab build guide for a small, quiet, GPU-capable box, and the $800 used-parts Proxmox server for the maximum-capability-per-dollar path.

5. Off-the-shelf or DIY NAS — when storage is the point

Sometimes the “server” you want is really a storage appliance: a place to keep files, media, and backups with drive redundancy, running quietly and independently of whatever else you tinker with. That is a NAS. You can buy a turnkey unit (Synology, QNAP, UGREEN) for the least-fuss path, or build one running TrueNAS, Unraid, or OpenMediaVault for more capacity and control per dollar.

Who it’s for: Anyone whose primary need is bulk storage with redundancy rather than compute, anyone who wants their storage layer to stay up even while they break and rebuild their compute node, and households centralizing photos, media, and backups. Many mature homelabs run both — a quiet compute node plus a separate NAS.

For the build side of this class, including the 2026 hard-drive-shortage angle, see Best Budget NAS Build 2026.

The honesty section: why a used rack server is usually the wrong first homelab

The internet loves the cheap-rack-server flex, so it is worth being blunt about why it bites most newcomers.

Noise. A used Dell R720-class rack server at idle measures roughly 50–55 dBA at one meter — about the volume of a conversation happening next to you, constantly. Under load it climbs to 70–80 dBA. A mini PC at idle is effectively silent. Unless your server lives behind a closed door away from where you live, the rack server is unlivable, and “I’ll just put it in the closet” underestimates how far that whine carries.

Power. A rack server commonly idles at 80–120 W; a mini PC idles at 10–18 W. On a machine that runs 24/7 that is not a rounding error — it is the difference between a few dollars a month and a noticeable line on your power bill, and it persists for the entire life of the server. The full region-by-region math, including what each class costs annually, is in 24/7 Homelab Idle Power Costs.

Space and heat. Rack gear is deep, heavy, and dumps real heat into the room. It assumes a rack, rails, and airflow most homes do not have.

The community consensus that shows up over and over in r/homelab “if I started over” threads is consistent: begin with a quiet, low-power box — a mini PC or a used SFF desktop — learn the software, and only move to enterprise gear once you have hit a real wall (RAM, drive bays, or remote management) that the small box genuinely cannot clear. The cheap rack server is a great second or specialized server, not a great first one.

The decision rule

Walk it top to bottom and stop at the first match:

If your server lives in a room you sit in → quiet class only. Start with a new mini PC (cleanest) or a used SFF desktop (cheapest). Do not buy a rack server.
If your main goal is bulk storage with redundancy → a NAS (buy off-the-shelf for least fuss, build it for capacity per dollar).
If you want the cheapest possible way to learn Proxmox → a used SFF desktop under $200, and add a second one later to learn clustering.
If you need a GPU, big DIMMs, or expansion cards and you can live in a room with the box, or you want it shelf-sized → a DIY Mini-ITX build.
If you genuinely need 128 GB+ RAM cheap, 8+ drive bays, or iDRAC/iLO, AND you have a basement/closet/dedicated room → a used enterprise server (a tower if you want it quieter, a rack if noise truly does not matter).
If you are not sure how much hardware you need → settle that first with the Proxmox hardware requirements guide, then come back and re-run this rule.

A large share of homelabs that have been running for a year or two converge on the same shape: one quiet, low-power compute node (mini PC or SFF) doing the day-to-day work, plus a separate NAS for storage, with enterprise gear added only for a specific job it is uniquely good at. If you build toward that from the start, you rarely buy the wrong thing twice.

Sources

Search volume, keyword difficulty, and search intent for “homelab server” / “servers for homelab” / “home lab server”: DataForSEO Labs and Google Ads keyword data, accessed 2026-06-19 (head term ~1,600/mo, KD 12, navigational + commercial intent).
Live SERP and People Also Ask for “homelab server”: DataForSEO Google organic results, accessed 2026-06-19 (Reddit r/homelab, joekarlsson.com “How to get started building a Homelab server in 2026”, stormagic.com, dev.to build logs).
Noise, idle power, RAM, and three-year ownership figures by server class: TechFuel HQ first-party analysis in Used Enterprise Server vs Mini PC for Homelab and 24/7 Homelab Idle Power Costs, with mini PC idle figures measured at the wall in Best Mini PC for a Homelab 2026.
“Start with a mini PC or used SFF, not a loud rack” newcomer consensus: r/homelab “if you could start your homelab over” discussion threads (top of the live SERP for the head term), accessed 2026-06-19.

The $2,500 RTX 5080 + 7800X3D 4K Build for 2026

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~15 min read · St. Louis County, MO

Some links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate we earn from qualifying purchases. Commissions never influence which products get recommended — see our disclosure.

This is the rig I actually run, priced as a build you can put together today. A Ryzen 7 7800X3D paired with an RTX 5080, on AM5, with the memory, storage, cooling, and power supply that make a 4K card behave like one. The headline parts (CPU and GPU) come to about $1,570 in June 2026; the full build lands in the $2,500 to $2,900 range depending on the RTX 5080 model you choose and where the 2026 memory and storage shortage has prices parked the week you buy.

I am writing this one differently from a spec-sheet build. The GPU benchmarks below are not lifted off a launch slide or paraphrased from a YouTube video. They are first-party numbers I measured on my own ASUS ROG Astral RTX 5080 OC, on this exact 7800X3D platform, and published in full in the open bench dataset. Where I lean on someone else’s testing for broader context, I name the source. That is the whole point of this site.

If you want the framework behind every choice here rather than the receipt, the how to choose a PC build guide walks the decision in order. This article is the high-end worked example.

Who this build is for (and who it isn’t)

This is a 4K build. If you game on a 1440p monitor, you are overpaying for a card you cannot fully use, and the $1,500 RTX 5060 Ti 1440p build is the better receipt for you. The 5080 earns its price on a 4K panel — a 4K 144Hz monitor or a 4K OLED — where its raw output and DLSS 4 Multi-Frame Generation have somewhere to go.

It is also a build for people who want one machine that does more than game. The 16GB of GDDR7 and 32-64GB of system RAM mean this same box runs local AI models, handles 4K video work, and doubles as a serious workstation. If pure gaming is the only goal and budget is tight, you do not need to be here — the 5080 is a want, not a need, above 1440p.

The one-line verdict: for 4K high-to-ultra gaming with real headroom for ray tracing and AI work, a 7800X3D + RTX 5080 is the build that makes sense in 2026 — provided you buy the 7800X3D and not the pricier 9800X3D, because at 4K you will not feel the difference.

The parts list with June 2026 prices

Every price below is a real US price I confirmed in June 2026, with a source. Two line items — RAM and storage — are caught in a genuine 2026 price spike driven by AI demand draining the DRAM and NAND supply, so I have given those as ranges and told you where to check live pricing. Tax is not included. The “as tested” column is the exact part on my bench; the recommended column is the sensible buy if you are building fresh.

Part	Recommended (build fresh)	As tested (my rig)	Price (June 2026)
CPU	AMD Ryzen 7 7800X3D (8C/16T, AM5)	Ryzen 7 7800X3D	~$320
GPU	RTX 5080 16GB (standard AIB)	ASUS ROG Astral RTX 5080 OC	$1,250+
Motherboard	B650E ATX (PCIe 5.0, Wi-Fi)	ASUS ROG STRIX B650-A Gaming WiFi	~$180-200
RAM	32GB DDR5-6000 CL30 (2×16GB)	64GB DDR5-6000 (2×32GB)	$120-400
Storage	2TB PCIe Gen4 NVMe	Samsung 970 EVO Plus 1TB (PCIe 3.0, owned)	$200-285
Cooler	360mm AIO, or a good air tower	NZXT Kraken 360	$110-200
PSU	850W ATX 3.1, 80+ Gold	EVGA SuperNOVA 1000 GT (1000W)	$110-130
Case	Dual-chamber or mesh mid-tower	HYTE Y60	$150
OS	Windows 11 Home	Windows 11 Home	~$40
Total (recommended)			~$2,500-2,900

A few notes on the line items that matter.

CPU — Ryzen 7 7800X3D (~$320). This is the value gaming chip, and the reason this build does not waste money (Ryzen 7 7800X3D on Amazon). Tom’s Hardware tracked it dropping to $319, an all-time low and $20 below its previous low, and VideoCardz logged it at $324.99 around the same time. Call it $320-340 depending on the day. The longer case for it over the 9800X3D is in the 7800X3D vs 9800X3D upgrade guide and the 7800X3D long-term review; the short version is in the benchmark section below.

GPU — RTX 5080 16GB ($1,250 and up). MSRP is $999 for the Founders Edition, but in June 2026 the cheapest in-stock new card on Best Value GPU’s tracker was $1,249, with standard models clustering in the $1,300-$1,450 band and premium variants like my ASUS ROG Astral OC running up toward $1,900. Buy a standard dual- or triple-fan card in the $1,250-$1,350 range; the premium models buy you a quieter cooler and a small factory overclock, not a different tier of performance. My own ROG Astral RTX 5080 review measures exactly how much that factory OC is worth (about 2-3% for free), and the answer is: not enough to pay a $500 premium for.

Motherboard — B650E, ~$180-200. My bench runs an ASUS ROG STRIX B650-A. For a fresh build I would spec a B650E board for the PCIe 5.0 x16 slot, which lets a future GPU run at full Gen5 bandwidth. Current ASUS B650E listings sit around $180-190 on Best Buy and Micro Center. B650E is the no-regret choice: it takes the 7800X3D today and any AM5 chip through Zen 6 with a BIOS update.

RAM — 32GB DDR5-6000 CL30, $120-400. This is the line that hurts in 2026. A memory shortage tied to AI infrastructure demand has sent DDR5 prices up several-fold (the full breakdown of why): Tom’s Hardware’s RAM price tracker and TweakTown’s reporting that 64GB of DDR5-6000 now costs more than a PlayStation 5 tell the story. A solid value 32GB kit can still be found near $120-150; name-brand CL30 kits run $300-540. Buy 32GB (2×16GB) at DDR5-6000 CL30 for the AM5 sweet spot — I run 64GB only because I keep VMs and local models resident, which is the one case where more RAM actually earns its price. Check PCPartPicker for the live number the week you buy; this is the single most volatile part in the build.

Storage — 2TB PCIe Gen4 NVMe, $200-285. Same crisis, different chips. NAND prices are climbing for the same AI-demand reason, and Tom’s Hardware’s SSD price tracker shows drives that were $150 now sitting near $285. Get a 2TB Gen4 drive with DRAM and a five-year warranty — Gen5 runs hotter and costs more for gains you will not feel in games. My bench drive is an older 1TB; on a 4K rig where modern installs run 150GB each, 2TB is the floor.

Cooler — 360mm AIO or a good air tower, $110-200. The 7800X3D is a cool 65W-class gaming chip — a quality dual-tower air cooler handles it silently and is the cheaper, no-pump-to-fail choice. I run an NZXT Kraken 360 because the LCD looks right behind glass and I had it on the bench; the NZXT Kraken Core 360 sits near $110-130. Match the cooler to the chip, not to the GPU — the 5080 cools itself.

PSU — 850W ATX 3.1, $110-130. Fully modular, ATX 3.1, with the native 12V-2x6 connector so the 5080 plugs in without an adapter daisy-chain. The NZXT C850 Gold and Cooler Master MWE Gold 850 V3 both land near $90-120. I run a 1000W EVGA SuperNOVA because I have had a supply die mid-game and now overbuy, but the measured draw (below) says 850W is correct.

Case — dual-chamber or mesh mid-tower, ~$150. I run a HYTE Y60 at $149.99. It is a beautiful case with one real warning: the panoramic glass design makes GPU clearance tight, and a thick triple-fan 5080 needs checking against the spec before you buy. A simpler high-airflow mesh tower is the safer pick if you do not want to fuss with clearance.

4K gaming benchmarks: first-party numbers on this exact rig

Here is where this build article earns its keep. The numbers in this table were measured by me, on my own ASUS ROG Astral RTX 5080 OC running on this 7800X3D platform, captured with HWiNFO64 logging and published in full — with 1% lows, methodology, and the raw dataset files — in the open bench dataset. These are demanding, ray-tracing-forward titles, run at native 4K, because that is where a 5080 either holds up or doesn’t.

Game (4K)	Avg FPS	1% Low	Settings
Cyberpunk 2077	58	49	Ultra, raster, no upscaling
Cyberpunk 2077	50	41	RT-Ultra + DLSS 4 Quality
Cyberpunk 2077	19	15	Path Tracing, native, no DLSS
Alan Wake 2	49	38	RT + DLSS 4 Quality
Black Myth: Wukong	34	27	Cinematic preset

The 1% lows run about 80-85% of the average across the rasterized and DLSS-Quality passes, which is a healthy frame-time consistency profile — no stutter, just a steady floor. The exception is native path tracing (19/15), where the card is bottlenecked so hard that the average frame and the slowest frame are basically the same. That is what 4K path tracing without upscaling looks like on any card short of a 5090, and it is exactly the problem DLSS 4 exists to solve.

DLSS 4 Multi-Frame Generation: what makes 4K path tracing playable

The single most important chart for a Blackwell card is what happens to that unplayable 19 FPS path-traced run when you turn on DLSS 4. These are my measured numbers on Cyberpunk 2077 at 4K with RT Overdrive (path tracing), including the PC latency at each step, because frame generation is worthless if it adds the input lag back:

Mode	FPS	PC Latency
Native path tracing (no DLSS, no FG)	19	95 ms
DLSS 4 Quality (no frame gen)	40	45 ms
+ Multi-Frame Gen 2×	90	55 ms
+ Multi-Frame Gen 4×	135	62 ms

The story holds up under measurement. DLSS Quality alone more than doubles the frame rate and halves the latency, because Reflex is scheduling a smaller render workload. Stacking MFG 2× doubles the frame rate again for a 10ms latency cost, and MFG 4× lands at a smooth 135 FPS while latency stays well below the native baseline. Across the full ladder, frame rate climbs about 7× and the input lag never gets worse than where it started. That is the actual experience of path-traced 4K on a 5080: native is a slideshow, DLSS 4 turns it into a smooth, responsive game.

How the 5080 sits in the broader 4K picture

My dataset is deliberately RT-heavy. For breadth across a wider raster suite, published testing fills in the rest. KitGuru’s review found that “at 4K the gains over the 4080 Super do get slightly wider, with the 5080 now 13% faster on average,” while it “still lags behind the RTX 4090 by 15%.” That third-party +13%-over-the-4080-Super figure is a near-exact match for my own first-party generational index, which put the 5080 Founders Edition at 114 against a 4080 Super baseline of 100 (+14%) — two independent measurements landing in the same place. The takeaway: the 5080 is comfortably a 4K card in raster, mid-100s FPS in most mainstream titles, a notch behind the much pricier 4090, and the DLSS 4 ladder above is what extends that to the heaviest ray-traced games.

Do you actually need the 9800X3D? (The question the SERP skips)

Search “RTX 5080 build” and most results pair it with a Ryzen 7 9800X3D. That is the default, and for a 4K build it is the wrong default for most people.

At 4K, the GPU is the bottleneck in nearly every game. The CPU sets up frames and then waits on the 5080 to draw them. Published reviews from Digital Foundry, Gamers Nexus, and Hardware Unboxed consistently place the 9800X3D about 10-20% ahead of the 7800X3D in CPU-limited 1080p testing — but as I cover in the full 7800X3D vs 9800X3D breakdown, that gap shrinks to roughly 2-5% at 4K, because both chips spend their time GPU-bound. You are paying a $150-180 premium for the 9800X3D to recover a few frames you will not see on a 4K panel.

The 9800X3D is the right call in two cases: you also game at 1080p competitively at very high refresh, or you run heavy production workloads (the Zen 5 chip is meaningfully faster in Blender and compilation). If production is the larger half of that job, the comparison to read is 9950X3D vs 9800X3D, where the 16-core chip buys a large multi-core lead without costing meaningful gaming performance. For a build whose entire reason to exist is 4K gaming, the 7800X3D is the chip, and the money saved goes further as a 2TB-to-4TB storage bump or a better monitor.

Power: what this build actually pulls

This is the part people guess at. Here is what I measured, not what a box claims. On my own card, board power ran 266-340W in games and topped out near 360W under a sustained stress load, with brief transient spikes into the 500-600W range — the spikes are why a quality ATX 3.1 supply matters more than a big wattage number. The 7800X3D adds well under 100W under a gaming load. That puts real sustained system draw around 450-500W.

An 850W ATX 3.1 unit covers that with clean headroom for the transient spikes and a future GPU upgrade, which is why it is the recommended part even though I personally run 1000W. Do not eyeball it — run your exact components through the PSU wattage calculator for a sized recommendation, and if you want to know what the rig costs to run, the power cost calculator turns that wattage into a monthly electric bill. For the record, the 5080 is also strikingly efficient for its performance: KitGuru measured it averaging about 306W at 4K, just 6W above the 4080 Super it comfortably outruns.

Build notes from my own bench

A few specifics from running this platform that the spec sheet will not tell you.

Memory speed on AM5. My kit is rated DDR5-6000 but I run it at 5800. Getting DDR5 fully stable at its rated speed on AM5 can be a fight, and after a weekend of BIOS tuning I dropped to 5800 and stopped. In actual gaming the difference is 1-2 FPS. Set EXPO, confirm it boots stable, and do not lose a weekend chasing the last 200 MHz.

GPU clearance in a glass case. The HYTE Y60’s panoramic glass makes for a gorgeous build and a tight fit. When I had a thick RTX 4080 in here previously, the front glass panel would not seat. Measure your specific 5080 model’s length and thickness against the case spec before you order — a triple-fan OC card is a real clearance risk in dual-chamber cases. The PC builder tool checks case-clearance and PSU compatibility as you pick parts.

The 12V-2x6 connector. Seat the power cable into the 5080 fully before you slot the card, and confirm the click. The connector is short and stiff, and given the 500-600W transient spikes this card produces, a partially-seated connector is the one failure you do not want. Use the native ATX 3.1 cable, not a third-party adapter.

Undervolt the GPU. The 5080 responds well to a light undervolt — you can shave board power and temperature with no measurable FPS loss. I cover the exact curve in the RTX 5080 undervolt guide; it is the single best 20 minutes you can spend after the build is done.

Cheaper and pricier alternatives

This build is one point on a line, not the only answer.

Step down to 1440p (~$1,500): if you are not on a 4K panel, the $1,500 RTX 5060 Ti 1440p build is the honest recommendation — same no-regret philosophy, a card sized correctly for 1440p, and a much smaller bill.
The same platform, a smaller GPU: the 7800X3D + B650 + DDR5-6000 base here is the right foundation at several price points. Drop to an RTX 5070 Ti and you have a strong entry-4K build for a few hundred less; the GPU is the only part that changes.
Build it yourself, priced live: the budget builder sorts parts by what you can actually spend, and the PC builder checks compatibility as you swap. Component pricing in 2026 moves weekly — use the tools rather than trusting any static total, including this one.

Verdict

For 4K gaming in 2026, a 7800X3D + RTX 5080 is the build that makes sense — fast enough to drive a 4K panel at high-to-ultra, efficient enough to live in a quiet case, and flexible enough to run local AI and creative work as a second job. The two decisions that keep it honest are buying the 7800X3D instead of the 9800X3D (you will not feel the difference at 4K) and buying a standard RTX 5080 instead of a $1,900 premium variant (you are paying for a cooler, not a tier).

The only thing working against it in 2026 is the memory and storage shortage, which has turned RAM and NVMe into the line items most likely to move your total. Everything else is stable, the GPU is a genuine 4K card, and the numbers above are real — measured on the rig in front of me, with the full dataset published so you can check my work.

How to Choose Your PC Build: CPU, GPU, PSU, RAM (2026)
The $1,500 RTX 5060 Ti 1440p Build
Ryzen 7 7800X3D vs 9800X3D: Should You Upgrade?
ASUS ROG Astral RTX 5080 OC Review · First-Party Bench Dataset
The $1,000 Local AI Workstation on an RTX 5080
A rig like this runs the most demanding games, but they need their anti-cheat happy: Easy Anti-Cheat fix guide and Star Citizen performance & troubleshooting.
PC Builder · PSU Wattage Calculator · Power Cost Calculator

Sources

TechFuelHQ first-party bench dataset — ASUS ROG Astral RTX 5080 OC (4K benchmarks, 1% lows, power, DLSS 4 MFG) — https://techfuelhq.com/data/gpu/rog-astral-rtx-5080-oc-2026-06-09/
Tom’s Hardware Ryzen 7 7800X3D all-time-low price — https://www.tomshardware.com/pc-components/one-of-amds-best-gaming-cpus-hits-an-all-time-low-price-ryzen-7-7800x3d-on-sale-for-less-than-usd320
VideoCardz Ryzen 7 7800X3D price — https://videocardz.com/newz/amd-ryzen-7-7800x3d-drops-to-324-99-ryzen-7-9850x3d-now-25-cheaper
Best Value GPU RTX 5080 price tracker — https://bestvaluegpu.com/history/new-and-used-rtx-5080-price-history-and-specs/
KitGuru RTX 5080 review (4K performance + power) — https://www.kitguru.net/components/graphic-cards/dominic-moass/nvidia-rtx-5080-review-efficiency-gains-but-a-performance-letdown/all/1/
Tom’s Hardware RAM price tracker 2026 — https://www.tomshardware.com/pc-components/ram/ram-price-index-2026-lowest-price-on-ddr5-and-ddr4-memory-of-all-capacities
Tom’s Hardware SSD price tracker 2026 — https://www.tomshardware.com/pc-components/ssds/ssd-price-tracking-2026-lowest-price-on-every-m-2-ssd
TweakTown 64GB DDR5 price reporting — https://www.tweaktown.com/news/109033/its-official-64gb-of-ddr5-6000-ram-now-costs-way-more-than-a-playstation-5-console/index.html
Newegg 80+ Gold PSU roundup 2026 — https://www.newegg.com/insider/best-80-plus-gold-power-supplies-for-high-end-pc-builds-in-2026/
HYTE Y60 store listing — https://hyte.com/store/y60

The Cheapest AM5 1080p Gaming PC You Can Build (2026)

LK Wood IV — Fri, 19 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-19 · ~11 min read · St. Louis County, MO

Some links below are Amazon affiliate links; if you buy through them TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate we earn from qualifying purchases. Commissions never influence which products get recommended — see our disclosure.

Here is the honest headline first: the $800 gaming PC does not exist in mid-2026. It did in 2025. A 2026 memory and storage shortage erased it, and the real entry price for a sensible new AM5 1080p build is now around $1,150 to $1,250 — up to roughly $1,350 if every part lands at the top of its price range. This article is that build — the cheapest machine I would actually tell someone to buy in mid-2026, the parts that make it, the prices with sources, and a clear explanation of where the extra money went so you are not blindsided at checkout.

If you came here expecting $800, I am not going to pad a parts list with prices from last year to hit a number that no longer holds. The framework behind every choice below is in the how to choose a PC build guide; this is the budget worked example, priced for the month you are reading it.

Why $800 isn’t enough anymore

The budget build did not get worse. Two of its parts got expensive.

Through 2026, an AI-infrastructure buildout drained the supply of DRAM and NAND flash, and the prices of RAM and SSDs climbed hard as a result. Tom’s Hardware’s RAM price tracker documents DDR5 kits that sold for $80-100 in late 2025 now starting in the hundreds, and a Team Group executive warned that DRAM and NAND contract prices rose 80-100% month-on-month and would keep climbing. SSDs followed: Tom’s Hardware’s SSD tracker shows 1TB drives that were sub-$100 now sitting around $150-250, with popular models routinely out of stock.

What that does to a budget build is specific. A 16GB DDR5-6000 kit that was a $90 afterthought now runs around $240, and a 1TB Gen4 SSD that was $70 is now around $150. That is roughly $250-300 of new cost dropped onto two parts that used to be cheap — and it lands hardest on a budget build, where every dollar already counted. The CPU, motherboard, power supply, cooler, and case are all about what they were. RAM and storage are the whole story. The deeper cause — AI and HBM demand pulling memory wafers off the consumer market — and when prices might ease are covered in why RAM and SSD prices tripled in 2026.

The parts list with mid-2026 prices

Every price below is a real US price with a source — CPU, RAM, and SSD as of June 2026, and the GPU re-checked live on July 10, 2026. RAM, SSD, and the GPU are the volatile ones — they move daily right now and sell out fast, so treat them as a snapshot and check live pricing before you buy. Tax is not included.

Part	Pick	Price (mid-2026)
CPU	AMD Ryzen 5 7600 (6C/12T, AM5, includes Wraith Stealth cooler)	~$160-210
GPU	AMD Radeon RX 9060 XT 8GB	~$380-420
Motherboard	B650M micro-ATX (Gigabyte B650M Gaming Plus / ASRock B650M Pro RS)	~$110
RAM	16GB DDR5-6000 (2×8GB)	~$240
Storage	1TB PCIe Gen4 NVMe (Silicon Power UD90, or a name-brand drive)	~$150-200
PSU	650W ATX 3.1, 80+ Bronze (Montech Beta 2 / MSI MAG A650BN)	~$50-60
Cooler	Included with the 7600 (Wraith Stealth)	$0
Case	Budget mesh-front (Fractal Core 1000 / Phanteks G370A)	~$50-70
OS	Windows 11 Home	~$0-40
Total		~$1,140-1,350

Notes on the line items that matter:

CPU — Ryzen 5 7600 (~$160-210). The cheapest sensible AM5 gaming chip, and it ships with a Wraith Stealth cooler, which saves you a cooler purchase on a budget build (Ryzen 5 7600 on Amazon). Micro Center had it at $159.99 in-store (pickup only, includes the cooler); online it runs closer to $210. If a Micro Center is already in reach, its exclusive Ryzen 5 7600X3D is the 3D V-Cache version of this same six-core class — the 7600X3D vs 7800X3D value comparison covers what the stacked cache costs and what it returns. The Ryzen 5 7500F is about $30-40 cheaper if you can find it (it is an OEM chip sold mostly by marketplace sellers) and gaming performance is within ~2% — Tech4Gamers measured the 7600 just 2.3% ahead — but the 7500F has no included cooler, which erases most of the savings on a budget build.

GPU — Radeon RX 9060 XT 8GB (~$380-420). The raster value leader at 1080p (RX 9060 XT 8GB on Amazon). Best Value GPU’s tracker listed it at $359 new on June 18, 2026, but by July 10, 2026 live Amazon listings had climbed to roughly $380 at the floor and $415-420 for a typical in-stock 8GB model, with 16GB versions starting around $450 — the memory shortage has spread to graphics-card GDDR, so budget another $20-60 over the June figure. Launch MSRP was $299; everything in this class sells well above MSRP right now. Published testing from XDA put it about 6% ahead of the RTX 5060 at 1080p, with a 5-10% lead depending on the game, at the same MSRP. More on the GPU choice below.

RAM — 16GB DDR5-6000 (~$240). This is the part that hurts, and there is no way around it in 2026. 16GB (2×8GB) at DDR5-6000 is the right amount and speed for an AM5 budget build, and a real dual-channel kit runs around $240 right now per the Tom’s Hardware tracker. Watch for a trap: several “16GB DDR5-6000” listings near $195 are single 16GB sticks, not 2×8GB kits — single-channel memory measurably hurts gaming on Ryzen, so buy a matched two-stick kit. The DDR5 buying guide covers speed and timings.

Storage — 1TB Gen4 NVMe (~$150-200). The other crisis line. A 1TB Gen4 drive runs from about $150 for a value model (Silicon Power UD90) up to around $200 for a name-brand drive per the SSD tracker; popular WD and Samsung models are frequently out of stock. 1TB is a tight but workable floor for a budget machine — add a second drive later when prices ease rather than overbuying capacity at peak.

Motherboard — B650M (~$110). A micro-ATX B650 board (Gigabyte B650M Gaming Plus WiFi, ASRock B650M Pro RS) gives you AM5, DDR5, PCIe, and a clean upgrade path to a future Ryzen chip with a BIOS update. No need for B650E or X670 on a budget 1080p build.

PSU — 650W ATX 3.1 (~$50-60). A quality 650W 80+ Bronze ATX 3.1 unit (Montech Beta 2, MSI MAG A650BN) is plenty for a sub-200W system and leaves headroom. Do not cheap out below a known brand here — run your exact parts through the PSU wattage calculator to confirm.

Case — budget mesh (~$50-70). Prioritize front-mesh airflow over looks at this price. The Fractal Core 1000, Phanteks G370A, and similar mesh towers land around $50-60 and keep the parts cool, which matters more than RGB.

The GPU choice: RX 9060 XT, RTX 5060, RX 7600, or Arc B580

At roughly $290-420 there are four real options, and the build above picks the RX 9060 XT 8GB for a reason — but the right answer depends on what you value.

RX 9060 XT 8GB (~$380-420) — the raster value pick. Fastest of the group at 1080p raster, with XDA measuring a 5-10% lead over the RTX 5060. This is the default for pure 1080p gaming, though the shortage has pushed it up enough that the cheaper cards below are worth a hard look if the budget is tight.
RTX 5060 8GB (~$339) — the ray tracing / DLSS pick. Slightly slower in raster but stronger in ray tracing and with DLSS 4 Multi-Frame Generation. Worth it if RT and upscaling features matter to you.
RX 7600 8GB (~$279) — the cheapest entry. Last-gen but the lowest price in, and a fine 1080p card if the budget is truly tight.
Intel Arc B580 12GB (~$303) — the VRAM value pick. More VRAM than any of the 8GB cards for less money, which buys headroom; drivers have matured but are worth checking against the titles you play.

For the full head-to-head with benchmarks, the RTX 5060 vs RX 9060 XT review is the detailed comparison; this build defaults to the 9060 XT and treats the others as informed swaps.

Is 8GB of VRAM enough at 1080p in 2026?

Short answer: yes at 1080p, with a ray-tracing caveat. Reviewer consensus is that 8GB still handles 1080p gaming in 2026 — PC Gamer’s real-world testing concluded 8GB GPUs are still enough for gaming at that resolution, and XDA’s testing found 1080p users face far fewer VRAM compromises than 1440p or 4K players do.

The honest caveat: the heaviest ray-traced titles and the highest texture presets can push past 8GB even at 1080p, and that is where you turn a setting down. If you want to avoid that entirely, the 16GB RX 9060 XT (~~$450) or the 12GB Arc B580 (~~$300) buys the margin. For most people playing at 1080p high, 8GB is fine in 2026 — just not generous.

What to expect from this build

This is a 1080p high-to-ultra machine, not a 1440p or 4K one. The RX 9060 XT comfortably drives modern AAA titles at 1080p with high settings and runs lighter and esports titles far above any monitor’s refresh you are likely to own at this budget. Pair it with a good 1080p 144Hz+ panel and the GPU has somewhere to put the frames. If you want 1440p instead, that is a different build — the $1,500 RTX 5060 Ti 1440p build is the next tier up, and the $2,500 RTX 5080 4K build is the 4K flagship.

Where to cut, and where not to

If ~$1,150 is still over budget, the honest places to trim:

GPU down to the RX 7600 (~$279) saves ~$80 and is still a capable 1080p card.
Skip the Windows license cost — you can install Windows 11 unactivated and add a key later, which is legal to run with minor cosmetic limits.
Reuse parts — a case, drive, or PSU from an old build is the cleanest saving, and the budget builder helps you price a partial build.

Where not to cut: do not buy a single-stick 16GB module to save $40 (single-channel memory hurts Ryzen gaming), do not buy a no-name PSU, and do not drop below 16GB of RAM in 2026. Those are the false economies that make a budget build feel cheap instead of just affordable. Use the PC builder to check compatibility as you swap parts.

Verdict

The cheapest gaming PC worth building in mid-2026 is an AM5 1080p machine around $1,150-1,250 as specced — up to roughly $1,350 at the top of every price range — a Ryzen 5 7600, an RX 9060 XT, 16GB of DDR5-6000, and a 1TB Gen4 drive. It is more than the $800 it would have cost a year ago, and most of the difference is the RAM and storage shortage — now with graphics cards selling above MSRP on top of it — not a worse build. If you need a machine now, this is the honest floor; if you can wait, there is no confirmed near-term price relief to wait for. Either way, the parts above are the right ones, and the prices are real as of mid-2026 (GPU re-checked July 10).

Sources

Best Value GPU RX 9060 XT price tracker — https://bestvaluegpu.com/history/new-and-used-rx-9060-xt-price-history-and-specs/
XDA RTX 5060 vs RX 9060 XT (1080p positioning) — https://www.xda-developers.com/nvidia-rtx-5060-vs-amd-rx-9060-xt/
Tom’s Hardware RAM price tracker 2026 — https://www.tomshardware.com/pc-components/ram/ram-price-index-2026-lowest-price-on-ddr5-and-ddr4-memory-of-all-capacities
Tom’s Hardware DRAM/NAND crisis (Team Group GM) — https://www.tomshardware.com/pc-components/dram/the-ram-pricing-crisis-has-only-just-started-team-group-gm-warns-says-problem-will-get-worse-in-2026-as-dram-and-nand-prices-double-in-one-month
Tom’s Hardware SSD price tracker 2026 — https://www.tomshardware.com/pc-components/ssds/ssd-price-tracking-2026-lowest-price-on-every-m-2-ssd
Micro Center Ryzen 5 7600 listing — https://www.microcenter.com/product/674517/amd-ryzen-5-7600-raphael-am5-38ghz-6-core-boxed-processor-wraith-stealth-cooler-included
Tech4Gamers Ryzen 5 7500F vs 7600 — https://tech4gamers.com/ryzen-5-7500f-vs-ryzen-5-7600/
PC Gamer 8GB VRAM real-world testing 2026 — https://www.pcgamer.com/hardware/graphics-cards/my-real-world-testing-shows-8-gb-gpus-are-still-enough-for-gaming-in-2026-but-im-surprised-at-just-how-much-faster-the-16-gb-versions-are/
XDA 8GB VRAM in 2026 — https://www.xda-developers.com/gamers-were-wrong-8-gb-of-vram-is-still-good-enough-in-2026/

Colophon — How TechFuel HQ Is Built

Thu, 18 Jun 2026 00:00:00 -0500

What this page is

A public record of how this site gets built — the publishing stack, the sourcing approach, and the editorial rules every article has to clear before it ships. The short version is on the About page. This is the long version with names, versions, and rules written out.

Publishing stack

TechFuel HQ is a static site built with Hugo extended (v0.145.0) and deployed to GitHub Pages from the main branch via GitHub Actions.

Hosting: GitHub Pages
Build: Hugo extended (v0.145.0), --gc --minify on every deploy
Source control: GitHub, every change goes through a pull request
CDN / DNS: Cloudflare in front of GitHub Pages (migrated 2026-06-20)
Analytics: Google Analytics 4 (GA4)
Search: Google Search Console for indexing state
Domain: techfuelhq.com, registered to the site author

Layouts and styles are written from scratch. No third-party theme.

How hardware figures are sourced

Hardware recommendations published in 2024–2025 were tested on a bench in St. Louis County, Missouri, using a P3 P4400 Kill A Watt for at-the-wall power, iperf3 for network throughput, fio for storage IOPS, and PresentMon for GPU frame-time capture. GPUs benchmarked on that bench — and used as the first-party baselines in the RTX 5080 dataset — included the RTX 4080, RTX 4080 Super, and an RTX 5080 Founders Edition. That homelab gear was largely sold or retired in early 2026; the ASUS ROG Astral RTX 5080 OC remains on the current bench.

Content published or updated from June 2026 onward sources its benchmarks from named third-party publications and primary documentation rather than a current personal bench:

Power and homelab hardware: ServeTheHome reviews and power testing, plus manufacturer spec sheets
Linux and storage benchmarks: Phoronix and the OpenZFS documentation
General hardware and GPUs: Tom’s Hardware and the AnandTech archive
First-party specs and standards: manufacturer product pages, Intel ATX design guides, JEDEC, PCI-SIG, and IEEE documents

Every figure is attributed to its source inline. Vendor spec-sheet numbers are labeled separately from independent third-party measurements.

AI in the workflow

AI tools assist with research aggregation, outlining, and first drafts — gathering sources to read, structuring an outline, and producing a rough draft to edit down. They do not decide what gets recommended, and they do not generate the measured figures: every benchmark, price, and spec still traces to a cited source or labeled first-party data under the standards below. Editorial judgment, verification, and the final wording are the author’s, and the byline is human and accountable.

Editorial standards

Every article on this site has to clear all of these before it ships:

No sponsored articles, no vendor samples, no paid placement. A recommendation is never shaped by anything other than the merits of the product.
Methodology and sources block on every article. Every benchmark-based article includes a “Methodology and sources” section naming the third-party publications and primary documentation the figures are drawn from.
Last-verified date on every article. When the underlying facts change, the article gets updated and the last-verified date moves. When they don’t, it doesn’t.
Cited benchmarks or no benchmarks. Vendor spec-sheet numbers are labeled separately from independent third-party measurements. Made-up benchmarks are worse than no benchmarks; any figure that cannot be attributed to a named source is removed rather than estimated.
No paid placement, ever. No product appears because a vendor paid, gifted, or sponsored it; placement is editorial only.
Cite primary sources inline. Vendor docs, official changelogs, and reputable trade press get linked. Reddit and forum threads get linked when they are the primary signal but get labeled as community-reported, not as vendor-confirmed.
No fabricated first-party claims. Present-tense first-person measurement claims (“I measured…”, “on my own bench…”) are used only when backed by a real, current artifact. Where no such artifact exists, figures are sourced to named third parties and the prose says so. Past-tense references to gear genuinely owned in 2024–2025 are allowed and labeled as past.

Source standards

Every factual claim that is not first-person traces to one of these:

Vendor documentation — release notes, specification sheets, official pricing pages, official product matrices
Vendor announcements — release blogs, press notes, official forums
Reputable third-party publications — ServeTheHome, Tom’s Hardware, the AnandTech archive, Phoronix, LWN, and vendor-independent benchmark labs. Forum posts and community wikis are used only for facts that have a clear authoritative provenance (release notes, license docs, official FAQs)
Standards bodies — JEDEC, PCI-SIG, IEEE, RFC documents

Sources are linked inline at the point of claim.

Monetization

The site is funded by display advertising via Google AdSense. The retailer links to Newegg, B&H, and other stores that appear in articles are plain reference links and earn no commission.

Some Amazon links are affiliate links through the Amazon Associates Program, which may earn a commission on a qualifying purchase at no extra cost to the reader; as an Amazon Associate, TechFuel HQ earns from qualifying purchases. Every article that contains an affiliate link carries a clear disclosure near the top, and a commission never changes which product gets recommended. Full detail is on the disclosure page.

Updates and corrections

Readers who spot an error are encouraged to email hello@techfuelhq.com with the article URL and the specific section in question. Confirmed corrections are made in-place in the affected article with an updated “Last verified” date.

Contact

Spot something wrong, want to challenge a recommendation, or have a question about how a specific article was produced? Email hello@techfuelhq.com.

Last updated: 2026-06-18.

Editorial Methodology

Thu, 18 Jun 2026 00:00:00 -0500

TechFuel HQ publishes hardware guides for homelabbers and budget-PC builders. This page describes — in plain language — who produces the content, how it is produced, what is and is not verified first-hand, and how readers can challenge any claim. The intent is to make every article auditable. See the full colophon for the publishing stack and bench methodology.

Who produces the content

The site is owned and edited by Lowell K. Wood IV (byline LK Wood IV), based in St. Louis County, Missouri. Lowell is the publisher of record. Author identity and contact information are exposed in the JSON-LD schema on every article and in the About page.

Email: hello@techfuelhq.com

There is no other staff. The site is a single-operator publication.

Real-artifact policy

A small number of claims on the site rely on first-person evidence rather than vendor specs — for example, a Kill A Watt idle-wattage reading, an iperf3 throughput run between two specific NICs, a photo of a parts receipt, or a screenshot of a BIOS configuration. The site has a strict policy for these:

Default tense is past. Most of the 2024–2025 testing gear was sold or retired in early 2026 (full timeline on the Colophon). First-person measurement language in older articles refers to that period and is phrased in the past tense.
Present-tense first-person claims (“I measured…”, “on my bench…”) are allowed only when the article either (a) shows the underlying artifact inline — a photo, a receipt, a measurement screenshot, captured terminal output — or (b) links to a published TechFuelHQ-canonical dataset that contains the artifact. The current canonical first-party dataset is the ASUS ROG Astral RTX 5080 OC bench dataset, captured 2026-06-08–2026-06-09.
No artifact, no first-person claim. Articles that would need a first-person claim but lack the artifact use cited third-party measurements instead, attributed to the named publication (ServeTheHome, Phoronix, Tom’s Hardware, TechPowerUp).
Fabricating an artifact — staged screenshots, made-up wattage numbers, invented dmesg or journalctl output, fake receipts — is forbidden under site policy.

If an article’s evidence shifts from “vendor spec citation” to “first-person measurement” or vice versa, the article’s update log records the date and direction of the shift.

Source standards

Every factual claim that is not first-person traces to one of these:

Vendor documentation — release notes, specification sheets, official pricing pages, official product matrices.
Vendor announcements — release blogs, press notes, official forums.
Reputable third-party publications — ServeTheHome, Tom’s Hardware, AnandTech archive, Phoronix, LWN, vendor-independent benchmark labs. Forum posts and community wikis are used only for facts that have a clear authoritative provenance (release notes, license docs, official FAQs).
Standards bodies — JEDEC, PCI-SIG, IEEE, RFC documents, where relevant.

Sources are linked inline at the point of claim and aggregated in the Sources block within each article.

A claim that cannot be cited to a resolvable, real source is removed before publish. Articles do not carry uncited “rumor” or “in my experience” lines that lack an artifact.

AI in the workflow

AI tools assist with research aggregation, outlining, and first drafts. The editorial judgment — what to recommend, what to cut, what to verify, and the final wording — is the author’s, and every measured claim still passes the source standards and real-artifact policy above before it ships. The byline is human and accountable; the fuller toolchain is described in the colophon.

Monetization disclosure

The site is funded by display advertising via Google AdSense. The retailer links to Newegg, B&H, and other stores that appear in articles are plain reference links and earn no commission.

Some Amazon links are affiliate links through the Amazon Associates Program, which may earn a commission on a qualifying purchase at no extra cost to the reader; as an Amazon Associate, TechFuel HQ earns from qualifying purchases. Every article that contains an affiliate link carries a clear disclosure near the top. A commission never changes which product gets recommended — if a product is not the right pick for the use case, it does not get recommended, affiliate link or not. Full detail is on the disclosure page.

The site participates in Google AdSense for display advertising. Advertising never appears inside the body of an article in a way that disrupts reading flow, and editorial recommendations are made independently of advertiser identity.

Update cadence

Articles are revised when the underlying facts change — a new product release, a vendor price shift, a license-policy change, a new firmware or kernel that affects compatibility. Each article carries a “Last updated” date that reflects the most recent material revision. Cosmetic edits (typos, layout fixes) do not bump that date.

Corrections

Readers who spot an error are encouraged to email hello@techfuelhq.com with the article URL and the specific section in question. Confirmed corrections are:

Made in-place in the affected article.
Logged in the article’s update log with the date and a one-line summary.
Acknowledged by reply email.

Material errors discovered after the fact are not silently overwritten. The site’s intent is to be auditable.

What this site does not do

To set explicit expectations:

The site does not publish vendor-paid placements disguised as editorial.
The site does not publish “review” content for products the author has not handled and for which no first-person artifact is shown — vendor-spec comparisons are framed as such, not as hands-on reviews.
The site does not chase hype cycles. If a product is unproven, the article says so.

Contact

Publisher: Lowell K. Wood IV Email: hello@techfuelhq.com Location: St. Louis County, Missouri, United States

Site policies referenced from this page: About, Disclosure, Privacy, Terms, Contact.

EVGA SuperNOVA 1000 GT Review: Gold PSU After the GPU Exit

LK Wood IV — Thu, 18 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-18 · ~9 min read · St. Louis County, MO

Rating: 4.3 / 5

The EVGA SuperNOVA 1000 GT is one of the better PSUs I’ve used. It’s also made by a company that exited the GPU market in 2022 and has wound down sharply since. These two facts both matter, and the degree to which the second should affect your purchasing decision depends on how much warranty coverage is worth to you.

I ran the SuperNOVA 1000 GT in my primary build — Ryzen 7 7800X3D, ROG Astral RTX 5080 OC, ROG STRIX B650-A, 64GB DDR5 — for an extended period. This is the review that follows real use.

What EVGA shipped

Published specifications (per EVGA’s published product specifications):

Capacity: 1000W
Efficiency rating: 80 Plus Gold
Modular: fully modular
Fan: 135mm FDB bearing, zero-RPM mode up to 40% load
ATX connector: 1× 24-pin
EPS/CPU connectors: 2× 8-pin (4+4)
PCIe connectors: 4× 6+2 pin (plus the SuperNOVA 1000 GT shipped with a 12VHPWR adapter for NVIDIA RTX 40-series and later GPUs)
Warranty: 10 years (verify current EVGA warranty support before relying on it)
Dimensions: 160mm depth (ATX standard)
Platform: Seasonic Focus GX-derived

The fully modular design is meaningful in practice. Unused cables stay in the bag, cable routing in the case is cleaner, and if a cable fails, you replace the cable rather than the PSU. The SuperNOVA GT series was consistently recommended over the GQ (semi-modular) line for this reason.

Efficiency in practice

80 Plus Gold means at least 87% efficiency at 20% load, 90% at 50% load, and 87% at 100% load (at 115V AC per 80 Plus specification). The Seasonic Focus GX platform consistently measures at or slightly above rated efficiency in third-party testing.

At my typical gaming load (~450W combined system draw), the 1000 GT runs at 45% utilization — squarely in its efficiency sweet spot. A Seasonic Focus GX-1000 measured at Cybenetics labs shows roughly 91–92% efficiency at the 50% load point. I use this as a proxy for the SuperNOVA GT given the shared platform, not as a direct measured spec for the EVGA unit.

At the Power & Cost Calculator: a 450W gaming PC running 4 hours per day at $0.13/kWh and 91% PSU efficiency costs approximately $10.50/month in electricity. The efficiency difference between an 80 Plus Gold and 80 Plus Bronze PSU at this load saves roughly $1.50–2.00/month — meaningful over years, not months.

Zero-RPM mode

The SuperNOVA 1000 GT runs its fan in zero-RPM mode below approximately 400W (40% load). At typical gaming loads with a 7800X3D and RTX 5080, the fan spins but spins slowly — it’s one of the quieter components in the build. At idle or light workloads, the PSU is completely silent.

Zero-RPM mode does mean the PSU runs hotter at low load than a fan-always-on unit, but PSU temperature at idle load is well within the operating spec. It’s a design tradeoff that optimizes for acoustics at the cost of slightly elevated idle temperatures. For a desktop build with reasonable case airflow, it’s the right tradeoff.

Cabling: PCIe and 12VHPWR

The SuperNOVA 1000 GT ships with four 6+2 PCIe cables and a 12VHPWR adapter (the 16-pin connector introduced with NVIDIA RTX 40-series and used on RTX 50-series). The 12VHPWR adapter is a passive cable that converts two 8-pin PCIe connectors to a single 12VHPWR.

On an RTX 5080, which uses the 16-pin 12VHPWR connector directly: the adapter works, but a native 12VHPWR cable is preferable. The adapter creates an extra connection point, and NVIDIA’s own adapter guidance recommends native 12VHPWR cables where available. This is a solved problem on any PSU purchased after 2023 — new units ship with native 12VHPWR cables. The SuperNOVA 1000 GT predates this connector and uses the adapter approach.

If you run an RTX 50-series card with a SuperNOVA GT, the adapter is fine. Just route it cleanly so the cable doesn’t stress the connector. JonnyGURU’s documentation of the 12VHPWR cable fires (now archived) traced failures to bent connectors and poor cable routing, not the adapter design itself.

EPS / CPU power

The 1000 GT includes two 4+4 EPS connectors for CPU power. The Ryzen 7 7800X3D at 162W PPT (max socket power) uses one 8-pin connector at well under 10A on the 12V rail. The second EPS cable stays unused for an AM5 build. For high-TDP Intel builds (i9-14900KS, i9-13900KS) that can draw 250–300W through the CPU power connectors, both EPS cables are used and the 1000W capacity is still appropriate.

The EVGA situation: what it means for buyers

EVGA announced in September 2022 that it would stop producing NVIDIA graphics cards, citing frustration with NVIDIA’s business practices. That announcement was about the GPU line specifically; EVGA kept selling power supplies and other products afterward. The company has wound down steadily since, and its current warranty service for hardware is limited and hard to confirm in 2026 — so the practical advice is to verify coverage before you count on it.

For units bought before September 2022: EVGA honored warranty claims for a period after the exit announcement. Whether that coverage is still serviced today is uncertain — confirm with EVGA before treating the 10-year warranty as a guaranteed benefit.

For units bought new-in-box after September 2022 (from retail stock): treat warranty support as unverified. The box says 10 years; check with EVGA whether that coverage is still honored before you rely on it.

For used units: no transferable warranty, obviously. Price accordingly.

The hardware itself doesn’t change based on EVGA’s corporate situation. A well-made PSU in the 1000 GT class will run for 8–12 years without failure in a desktop build that doesn’t have cooling issues. The risk you’re absorbing without a warranty is that if it fails inside what would have been the warranty window, you buy a replacement.

What to buy instead (if warranty matters)

Current alternatives at the 1000W Gold tier with active warranties:

PSU	Efficiency	Warranty	Approximate street
Corsair RM1000x (2024 rev)	80+ Gold	10 years	~$150
Seasonic Focus GX-1000	80+ Gold	12 years	~$170
be quiet! Straight Power 12 1000W	80+ Gold	10 years	~$160
Fractal Design Ion+ 1000W	80+ Platinum	10 years	~$180
Cooler Master V1000 Gold	80+ Gold	10 years	~$130

The Corsair RM1000x (2024 revision) is the most direct comparable — fully modular, 80 Plus Gold, 10-year warranty, available from active stock. It’s slightly more expensive than a SuperNOVA 1000 GT found new-in-box but comes with warranty coverage that actually exists.

Verdict

The SuperNOVA 1000 GT hardware is excellent and I’d use it again in a build where warranty coverage isn’t the deciding factor. Fully modular, quiet, efficient, right-sized for an RTX 5080 + Ryzen 7 7800X3D build, and well-built enough to outlast most of the components it powers.

The warranty situation is the only reason to hesitate. If you find a SuperNOVA 1000 GT new-in-box for $100 or less, or used in verifiably good condition for $70–80, the hardware justifies the purchase. If price parity exists with a RM1000x or Seasonic Focus GX, buy the warranted unit.

Rating: 4.3/5 — top-tier hardware from a company whose ongoing support is uncertain. Buy at a discount and verify warranty coverage; buy a warranted competitor at parity.

For the full build this PSU shipped in, the ROG STRIX B650-A review covers the platform. To size a PSU for your specific build, the PSU Wattage Calculator gives you peak draw, minimum recommended size, and the efficiency sweet-spot size. To calculate how a 1000W unit affects your electricity bill vs. a 750W, the Power & Cost Calculator models PSU efficiency at real load points.

How to Choose Your PC Build: CPU, GPU, PSU, RAM (2026)

LK Wood IV — Thu, 18 Jun 2026 00:00:00 -0500

Picking PC parts is less about memorizing models and more about making the right decisions in the right order. Get the order wrong and you over-spend on one part while bottlenecking another. This guide walks the decision the way I actually make it — what to choose first, how each component constrains the others, and where to let a calculator do the math instead of guessing. It’s framework, not a fixed parts list; for a concrete example, the $1,500 RTX 5060 Ti build puts every choice here into one real receipt.

Start with the part that defines your use case

Every build has one component that sets the ceiling, and you choose it first:

Gaming → start with the GPU. It decides your resolution and frame rate and usually eats the largest share of the budget. Everything else supports it.
Productivity / creation / homelab → start with the CPU and platform. Core count, PCIe lanes, and memory capacity drive those workloads more than the GPU does.

Pick that anchor part to fit your real target — the resolution you play at, the software you run — then build outward so nothing else holds it back.

GPU: match VRAM and tier to your resolution

The GPU question is really two questions: how much raw performance, and how much VRAM.

1080p: an entry card is fine; 8 GB still works but is getting tight in new titles at high textures.
1440p: the mainstream target in 2026. 16 GB is the comfortable amount — enough that VRAM stops being the bottleneck and the GPU itself becomes the limit.
4K / local AI: 16 GB is the floor; 24 GB+ buys real headroom for textures and models.

When two cards sit at a similar price, the one with more VRAM usually ages better — texture and model sizes only grow. For a worked comparison at the mid-range, see the RTX 5060 Ti vs RX 9060 XT 1440p showdown.

CPU and platform: enough, not excessive

Match the CPU to the GPU and resolution rather than buying the biggest chip on the shelf. At 1440p and 4K the GPU is almost always the limit, so a solid current-gen 8-core is plenty; chasing a flagship CPU there is wasted money that belongs in the GPU. A faster or 3D V-Cache CPU earns its keep at 1080p and in CPU-bound esports titles.

On platform: in 2026, prefer a current-gen socket (AMD’s AM5 or the current Intel socket) over a dead-end one, so a CPU upgrade later doesn’t mean a new board. A mid-range board that takes a future higher-end chip with a BIOS update is the no-regret choice.

RAM: speed, timing, and capacity

For AM5, the established sweet spot is DDR5-6000 CL30 at a 1:1 memory-to-fabric clock — push the speed higher and the controller often drops to a 2:1 ratio that gives the gain back. Capacity in 2026:

32 GB (2×16): the default for gaming and light creative work.
64 GB: heavy multitasking, VMs, or running local LLMs alongside everything else.

Populate two slots with a matched kit, not four, for the cleanest high-speed stability. If you are still deciding between those tiers, how much RAM you actually need in 2026 walks through 16 vs 32 vs 64 GB by use case, and the DDR5 buying guide covers speeds and timings in depth.

Storage: NVMe first, capacity by need

A PCIe Gen4 NVMe with real DRAM is the right boot/game drive in 2026 — Gen5 runs hotter and costs more for gains you won’t feel in games. Size by what you actually store: 1 TB is a tight minimum, 2 TB is the comfortable default, and you can add a second drive later. Note that NAND prices have been volatile, so buy the capacity you need now rather than over-buying on a spike.

PSU: size with headroom, get the right connector

This is the part people guess at and shouldn’t. Add up your components’ real draw (the GPU and CPU dominate), then add ~30% headroom for spikes, efficiency, and a future upgrade. A typical mid-range build pulls 350–450 W under load, which puts a quality 650–750 W unit in the right range — the extra isn’t for today, it’s so a future GPU doesn’t force a PSU swap.

In 2026, buy an ATX 3.1 / PCIe 5.1 supply with the native 12V-2x6 connector so modern cards plug in without adapters. Rather than eyeball it, run your exact parts through the PSU wattage calculator for a sized recommendation with headroom built in.

Cooling and case: match the heat, fit the parts

For most CPUs in the 65–105 W class, a good dual-tower air cooler is quiet, cheap, and has no pump to fail. Step up to a 240–360 mm AIO only for a high-TDP chip run hard, a case with poor air clearance, or the aesthetic. The case itself is a real decision, not an afterthought: prioritize front mesh airflow, GPU and cooler clearance, and enough room for cable management. A pretty case that cooks the parts is the wrong case.

Let the tools do the math

Three calculators on the site exist so you don’t have to guess the numbers:

PC Builder — pick parts and it checks socket, PSU, and case-clearance compatibility as you go.
PSU Wattage Calculator — enter your components, get a sized supply with headroom.
Budget Builder — sort gear by what you can actually spend and balance the build to your budget.

The decision in one line

Choose the part that defines your use case first, match everything else to it, give the GPU the VRAM it needs for your resolution, size the PSU with headroom and the right connector, and let the calculators catch the mistakes before you buy. When you want to see it all assembled into a real receipt, the $1,500 RTX 5060 Ti 1440p build is the worked example. For the high-end version of the same framework at 4K, the $2,500 RTX 5080 + 7800X3D 4K build is the worked example one tier up.

Sources

AMD AM5 platform / EXPO memory guidance — https://www.amd.com/en/products/processors/desktops/ryzen.html
Intel ATX / power-supply design guides — https://www.intel.com/content/www/us/en/products/docs/power-supplies/atx-design-guide.html
JEDEC DDR5 standard (JESD79-5) — https://www.jedec.org/standards-documents/docs/jesd79-5b
PCI-SIG (PCIe / 12V-2x6 connector standards) — https://pcisig.com/

Samsung 970 EVO Plus 1TB Review (2026): A PCIe 3.0 Keeper

LK Wood IV — Thu, 18 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-18 · ~8 min read · St. Louis County, MO

The Samsung 970 EVO Plus came out in 2019. It runs in my daily machine in 2026 alongside a Ryzen 7 7800X3D and an RTX 5080. At some point, most people with older NVMe drives wonder whether they’re leaving performance on the table by not upgrading. Here’s the honest answer from running this drive for years: probably not.

The hardware, briefly

Samsung’s 970 EVO Plus uses 92-layer V-NAND TLC NAND with Samsung’s in-house Phoenix controller and LPDDR4 DRAM cache. The 1TB variant is rated at:

Spec	Value
Interface	PCIe 3.0 × 4, NVMe 1.3
Sequential read	3,500 MB/s
Sequential write	3,300 MB/s
Random read (4KB)	600,000 IOPS
Random write (4KB)	550,000 IOPS
DRAM cache	Yes (LPDDR4)
Endurance	600 TBW
Warranty	5 years
Form factor	M.2 2280

Source: Samsung official 970 EVO Plus specifications

The random IOPS numbers matter more than the sequential numbers for everything except file transfers and large data workloads. Game load times, application launches, OS responsiveness — these are IOPS workloads, not sequential workloads. The 970 EVO Plus’s 600K/550K IOPS puts it in a range where it is not the bottleneck in any typical gaming or desktop workflow.

Real-world use as a boot drive

This drive holds Windows and my game library in a Ryzen 7 7800X3D build with a ROG STRIX B650-A motherboard. The B650-A has a PCIe 5.0 M.2 slot I haven’t used for anything yet and two PCIe 4.0 M.2 slots. The 970 EVO Plus runs in one of the PCIe 4.0 slots at native PCIe 3.0 speeds — that’s the correct behavior, backward compatible with no performance penalty beyond the Gen3 ceiling.

In day-to-day use: fast. There is no situation where I’m waiting on storage in typical workflows. Game loads in Baldur’s Gate 3 take about 12 seconds from click to playable. Cyberpunk 2077 initial load is around 15 seconds. Those numbers on a Gen4 drive at 7,000 MB/s would be roughly 11 and 14 seconds. Half a second to a second faster per load. That’s the real-world gap.

For game load times specifically, the IOPS throughput matters more than sequential throughput, and the gap between a quality PCIe 3.0 drive and a quality PCIe 4.0 drive in IOPS is narrower than the sequential bandwidth gap implies.

Thermals

This is the 970 EVO Plus’s weakest point. Under sustained sequential writes — large game installs, moving large video files, system image backups — the drive runs warm. Surface temperatures in the 55–65°C range under heavy write workloads are normal and within spec, but noticeably warmer than modern Gen4 drives that run cooler due to smaller process nodes.

In a slot without a heatsink, it’s worth monitoring via CrystalDiskInfo or HWiNFO64 the first few times you run heavy workloads. The B650-A’s M.2 slots come with thermal pads and shields; the 970 EVO Plus runs comfortably in those slots with the included heatsink assembly.

Throttling doesn’t occur in typical desktop use — only under sustained sequential writes that would also challenge most people’s SATA connectivity. For a gaming boot drive, thermal throttling is a non-issue.

The Gen4 comparison question

Current Gen4 drives at comparable price points:

Samsung 990 Pro: 7,450/6,900 MB/s sequential, ~$80-90 for 1TB
WD Black SN850X: 7,300/6,600 MB/s sequential, ~$85-95 for 1TB
Crucial T500: 7,300/6,800 MB/s sequential, ~$70-80 for 1TB

In 2026, Gen4 drives are essentially price-equivalent to where the 970 EVO Plus was when new. The sequential bandwidth ceiling is double. In sustained sequential transfer workloads — large file copies, video editing timelines, VM disk images with heavy I/O — the Gen4 drives are meaningfully faster.

For everything else — OS boot, game load, application launch, daily file access — the gap is measured in fractions of seconds.

If I were buying new today, I would not buy the 970 EVO Plus. Gen4 drives are available at the same price, run cooler, offer double the sequential bandwidth, and have matching or better IOPS. The 970 EVO Plus was the right buy in 2019–2021. It is not the right buy in 2026.

If I already own one, I would not replace it. The performance I lose to not having a Gen4 boot drive is less than the time it takes to clone drives and reinstall.

Endurance and reliability

600 TBW on the 1TB is a strong endurance rating. At typical desktop write loads — 30–50 GB/day — you’d reach 600 TBW in 32–55 years, and the SSD endurance calculator runs the same arithmetic for your own daily writes and write amplification. Endurance is not a practical concern for this drive in any normal use case. The NAND will survive longer than the rest of the system.

Samsung’s V-NAND reliability track record is excellent. For a boot drive in a long-running machine, the 970 EVO Plus is among the most reliable options available regardless of generation.

The 5-year warranty is a real warranty from a manufacturer still in business and still supporting the product line. This is a relevant contrast to the EVGA SuperNOVA situation where the brand exited hardware production.

DRAM cache: why it matters

The 970 EVO Plus includes LPDDR4 DRAM. Drives without DRAM (DRAM-less drives, common in budget segments) use host memory buffer (HMB) — borrowing system RAM — which introduces latency. Under sustained write loads, DRAM-less drives hit a write cliff where performance drops dramatically as the SLC cache fills and the controller falls back to writing directly to the NAND.

The 970 EVO Plus’s DRAM cache prevents this cliff for typical workloads. Under heavy sustained write (200+ GB transfers), it will eventually exhaust the SLC layer and fall back to raw TLC write speeds (~1,200 MB/s), but this only matters for transfer workloads larger than most users ever encounter.

Verdict

The 970 EVO Plus is a well-built, reliable, properly-performing PCIe 3.0 NVMe that has aged gracefully. It is no longer a competitive purchase at 2026 prices, but it remains a fully capable daily drive for any workload that isn’t specifically bottlenecked by sequential throughput. If it’s in your system, keep it. If you need more storage, add a Gen4 drive rather than replacing it. If you’re building new, buy Gen4.

Related hardware in this build: ROG STRIX B650-A review covers the motherboard this drive runs in, including M.2 slot configuration and thermal performance. The Gaming PC Build 2026 article lists the full build context.

Are Proxmox Helper Scripts Safe? What Runs as Root (2026)

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

If you run a Proxmox homelab, you have seen the one-liners. A forum post or a YouTube comment says “just paste this,” you copy a bash -c "$(curl ...)" command into your Proxmox shell, and ninety seconds later you have a fully configured LXC container running Jellyfin, AdGuard, or Home Assistant. They are the community-scripts ProxmoxVE helper scripts — the project formerly known as tteck’s Proxmox scripts — and they are some of the most-used tools in the entire homelab ecosystem.

The question people quietly type into a search bar before pasting that command is the right one: is this actually safe?

The honest answer is “mostly, with conditions” — and the conditions matter more than most write-ups admit. I read the current source to write this, and the part that changes the calculus is that the script you paste is not the only code that runs. Here is what these scripts actually do as root, where the real risk lives, and a practical way to use them without gambling your node.

The short answer

These are legitimate, reputable, community-maintained scripts under the MIT license, built on tteck’s original work. They are not malware.
They run as root on your Proxmox host, and they download more code from GitHub while they run — so reviewing the one file the command points at does not show you everything.
The trust model changed when tteck passed away and the project moved to community maintainers. That is a reason to re-examine your assumptions, not to panic.
For a test node, the risk is low. For a host you cannot afford to lose, read the script and snapshot or back up first.

What the helper scripts actually are

The project lives at community-scripts/ProxmoxVE and powers a catalog of hundreds of one-command installers for self-hosted services — media servers, home automation, databases, networking tools, monitoring. You browse the catalog at community-scripts.org, find your service, copy the install command from its page, and paste it into the Proxmox host’s root shell. The repo’s own requirements line says it plainly: you need “root shell access on the Proxmox host.”

The provenance matters. The scripts began as tteck’s personal project (tteck/Proxmox). After tteck passed away, the work was carried forward by a community team as community-scripts/ProxmoxVE, licensed MIT and footnoted “In memory of tteck.” That is a genuinely good outcome for an orphaned project — but it is also the crux of the safety question, which is really a trust question.

What actually runs as root (the part most guides skip)

When you paste a helper-script one-liner, it fetches a script from GitHub and executes it as root. That much is obvious. What is less obvious is what that script does next.

Reading the shared framework that nearly every container script relies on — misc/build.func — the very first thing it does is pull more code from the internet and execute it in the running shell:

source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func)
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func)
source <(wget -qO- https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/error_handler.func)

That source <(curl ...) pattern — process substitution — runs the downloaded file’s contents directly, as root, the moment it lands. The framework falls back to wget if curl is missing. So a single “review the script” step is misleading: the file you read is a loader that, at runtime, pulls in several more files (api.func, core.func, error_handler.func, and others) from the main branch. You are trusting the current state of the repository at the moment you run it, not the static text you skimmed.

From there, build.func does exactly what you would expect a capable installer to do — and it is a lot:

Creates an LXC container with the CPU, RAM, and disk you choose.
Configures networking — DHCP or static IP, IPv6, VLAN tags, MTU, bridge selection.
Selects storage for the container rootfs and templates.
Sets security-relevant options — SSH keys, the root password, GPU passthrough, container nesting, FUSE/TUN.
Applies host/system settings — timezone, hostname, DNS, APT caching, tags, protection flags.

It walks you through all of this with a whiptail wizard (roughly 29 configuration steps in the current code). None of that is malicious. But every one of those actions happens with full root authority on your hypervisor, driven partly by code fetched live from the internet.

So where is the real risk?

It is not “the maintainers are bad actors.” The repo is public, popular, MIT-licensed, and reviewable. The risk is structural, and it is the same risk as any curl-to-bash-as-root workflow:

You are trusting a moving target. The one-liner pulls from main. Code that was clean last week is not guaranteed to be the code you run today. There is no review step between “a commit lands” and “it executes as root on your box.”
The trust handover is real. As one homelabber put it bluntly after the maintainer change: “Ever since tteck passed away, I stopped using them. He was the guy who wrote those scripts and I trusted him.” That is not an accusation against the new maintainers — it is an honest acknowledgment that “I trust this project” is a decision you should make consciously, not inherit.
Supply-chain compromise is a documented pattern. The 2024 xz-utils backdoor showed that even long-trusted open-source tooling can be subverted by the people maintaining it. A widely-used script repo that runs as root on tens of thousands of hypervisors is exactly the kind of high-value target that history says to treat carefully.
The blast radius is your whole node. Running as root, a bad or buggy script can wipe data, misconfigure the host, or install something unintended. As the community guides say without sugar-coating: you could end up with “malware, a wiped drive, or a compromised Proxmox node.”

To be clear about proportion: there is no known incident of these scripts shipping malware, and millions of installs have gone fine. The point is that “it has been fine so far” and “it is safe to run blind on my production host” are two different statements.

How to vet a helper script (the workflow I’d use)

You do not have to choose between “paste blindly” and “never use them.” A few habits move you from gambling to a calculated, reversible decision:

Read it before you run it. Open the raw GitHub URL the one-liner points at and actually read it. Remember the framework pulls in more files at runtime — so also skim build.func once to understand what the shared engine does. You are not auditing every line forever; you are confirming it does what it claims and noting that it sources remote code.
Back up the host first. Snapshot or back up the Proxmox node with Proxmox Backup Server before running anything new. This single step converts “a bad script bricked my node” into “I restored in ten minutes.”
Test on a non-critical node. If you run more than one box, try new scripts on the one you would not cry over. If you run one node, that is even more reason to do steps 1 and 2.
Download, review, then run a saved copy instead of piping straight to bash. curl -fsSL <url> -o app.sh, read app.sh, then bash app.sh. Now you are running a fixed, reviewed file — not whatever main happens to contain at execution time.
Pin to a commit if you re-run it. If a script is part of your routine, reference a specific commit hash rather than main so you get a reproducible, reviewed version each time.
Keep the service in an unprivileged LXC where the app supports it, and do not flip on nesting, FUSE, or passthrough unless the workload actually needs them. Least privilege limits what a future problem can reach.

If that sounds like more friction than “paste this,” that is the trade. The scripts buy you speed; these habits buy back the safety you skipped. On a test node, steps 1–2 are plenty. On a host running things you care about, do all six.

When to use them — and when not to

Situation	Verdict
Spinning up a throwaway service on a test node	Fine — read it, run it, move on
Learning Proxmox and what a clean LXC setup looks like	Great — but read the script so you learn what it did
Installing on your main node with data you care about	Only after a host backup + a read-through
Production / anything you cannot restore quickly	Prefer doing the install yourself, or run from a reviewed, pinned copy
You cannot or will not read a bash script at all	Reconsider — that is the user these workflows are riskiest for

There is also a long-term argument worth taking seriously: the scripts are a fantastic accelerator and a poor teacher. As one user put it, “they are good for learning short term, but when you find yourself getting serious on a project, you’re better off learning to do it without the scripts.” Knowing how to create and configure an LXC container yourself — or set up a node from scratch — means you are never dependent on a third party’s root access to your hypervisor.

The honest verdict

The Proxmox helper scripts are not a scam, not malware, and not a mistake to use. They are a well-run, MIT-licensed, community-maintained project doing a genuinely useful thing. But “is it safe?” is the wrong shape of question. The accurate version is: “am I comfortable letting code fetched live from GitHub run as root on this specific host, and could I recover if it went wrong?”

On a test node, the answer is almost always yes — use them, and read them to learn. On a host you cannot afford to lose, make it a yes on purpose: read the script, understand that it pulls more code at runtime, back the node up first, and keep your containers least-privileged. Do that, and you get the ninety-second install without betting the homelab on it.

Sources

community-scripts/ProxmoxVE repository and README (MIT license, “In memory of tteck,” root requirement): https://github.com/community-scripts/ProxmoxVE
misc/build.func shared installer framework (runtime remote sourcing of api.func / core.func / error_handler.func): https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func
“Helper Scripts or Hidden Risks? The Ongoing Debate in the Proxmox Community” (trust, handover, vetting): https://www.mrplanb.com/blog/helper-scripts-hidden-risks-proxmox-community
Proxmox forum: “How safe are the Updatable PVE Helper-Scripts”: https://forum.proxmox.com/threads/how-safe-are-the-updatable-pve-helper-scripts.174400/

Authentik Self-Hosted SSO for the Homelab (2026)

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-17 · ~15 min read · St. Louis County, MO

Once you have ten self-hosted services running, the per-app account problem becomes real. Nextcloud has one username/password. BookStack has another. Portainer has a third. Grafana has a fourth. If you add family members or collaborators, you’re creating accounts across every app separately.

Authentik solves this with a single login that every other app delegates to. It runs in Docker, supports every authentication protocol your apps need, and the free tier covers everything a homelab will ever use. (Still deciding between Authentik and the lighter Authelia? Authelia vs Authentik compares footprint, protocol coverage, and which one actually does single logout — then come back here to build Authentik.)

What Authentik gives you

Single sign-on (SSO): one login for Nextcloud, BookStack, Grafana, Portainer, Gitea, Immich, and any other OIDC/SAML/LDAP-capable app
LDAP provider: apps that can’t do OIDC (or are easier to configure with LDAP) connect via Authentik’s built-in LDAP server
MFA: TOTP, WebAuthn/passkeys, Duo — configurable per application and per user group
User self-enrollment: users can reset their own passwords, enroll MFA devices, and manage sessions through the Authentik user portal
Outpost proxy: protect apps that have no built-in auth at all (add authentication in front of any web UI)

The Authentik model

Before deploying, understand three concepts:

Providers: define the protocol connection — OIDC/OAuth2, SAML, LDAP, or Proxy. Each external app needs a Provider with the right protocol for how it authenticates.

Applications: tie a Provider to an entry in the Authentik portal (name, icon, launch URL). Users see a list of Applications in their portal; clicking an Application authenticates them to that service.

Flows: sequences of stages (authentication prompts, MFA, consent, enrollment) that run when a user logs in, enrolls, or resets their password. Authentik ships with sensible default flows.

Stack requirements

Authentik has more dependencies than most self-hosted apps:

Container	Role
`authentik-server`	Main web UI, API, authentication flows
`authentik-worker`	Background tasks (email, cleanup, LDAP outpost)
`authentik-db`	PostgreSQL — user accounts, sessions, configuration
`authentik-redis`	Task queue and cache

Total idle RAM: approximately 500–700 MB combined. Authentik is heavier than BookStack or Paperless-ngx at idle, which reflects the complexity of the task it handles.

Directory layout

mkdir -p /opt/authentik/media /opt/authentik/certs /opt/authentik/custom-templates

Docker Compose

services:
 authentik-db:
 image: postgres:16
 container_name: authentik-db
 restart: unless-stopped
 environment:
 POSTGRES_DB: authentik
 POSTGRES_USER: authentik
 POSTGRES_PASSWORD: CHANGE_THIS_DB_PASSWORD
 volumes:
 - /opt/authentik/db:/var/lib/postgresql/data
 healthcheck:
 test: ["CMD-SHELL", "pg_isready -U authentik"]
 interval: 10s
 timeout: 5s
 retries: 5

 authentik-redis:
 image: redis:7-alpine
 container_name: authentik-redis
 restart: unless-stopped
 command: --save 60 1 --loglevel warning

 authentik-server:
 image: ghcr.io/goauthentik/server:2024.12
 container_name: authentik-server
 restart: unless-stopped
 command: server
 depends_on:
 authentik-db:
 condition: service_healthy
 authentik-redis:
 condition: service_started
 environment:
 AUTHENTIK_REDIS__HOST: authentik-redis
 AUTHENTIK_POSTGRESQL__HOST: authentik-db
 AUTHENTIK_POSTGRESQL__USER: authentik
 AUTHENTIK_POSTGRESQL__PASSWORD: CHANGE_THIS_DB_PASSWORD
 AUTHENTIK_POSTGRESQL__NAME: authentik
 AUTHENTIK_SECRET_KEY: CHANGE_THIS_SECRET_KEY
 AUTHENTIK_EMAIL__HOST: smtp.yourdomain.com
 AUTHENTIK_EMAIL__PORT: 587
 AUTHENTIK_EMAIL__USE_TLS: "true"
 AUTHENTIK_EMAIL__USERNAME: authentik@yourdomain.com
 AUTHENTIK_EMAIL__PASSWORD: your-smtp-password
 AUTHENTIK_EMAIL__FROM: authentik@yourdomain.com
 volumes:
 - /opt/authentik/media:/media
 - /opt/authentik/custom-templates:/templates
 ports:
 - "9000:9000"
 - "9443:9443"

 authentik-worker:
 image: ghcr.io/goauthentik/server:2024.12
 container_name: authentik-worker
 restart: unless-stopped
 command: worker
 depends_on:
 authentik-db:
 condition: service_healthy
 authentik-redis:
 condition: service_started
 environment:
 AUTHENTIK_REDIS__HOST: authentik-redis
 AUTHENTIK_POSTGRESQL__HOST: authentik-db
 AUTHENTIK_POSTGRESQL__USER: authentik
 AUTHENTIK_POSTGRESQL__PASSWORD: CHANGE_THIS_DB_PASSWORD
 AUTHENTIK_POSTGRESQL__NAME: authentik
 AUTHENTIK_SECRET_KEY: CHANGE_THIS_SECRET_KEY
 volumes:
 - /opt/authentik/media:/media
 - /opt/authentik/custom-templates:/templates
 - /var/run/docker.sock:/var/run/docker.sock

Three values to set before starting:

AUTHENTIK_SECRET_KEY: generate with openssl rand -hex 32
AUTHENTIK_POSTGRESQL__PASSWORD and POSTGRES_PASSWORD: must match
SMTP settings: required for password reset and email verification flows; without SMTP, those flows fail silently

Pinning the version: use a specific version tag (2024.12) rather than latest. Authentik uses a YEAR.MONTH release format; major updates can change configuration and database schema. Check release notes before updating.

First start

cd /opt/authentik
docker compose up -d

# Watch the server start (takes 60-90 seconds first run for database migration)
docker compose logs -f authentik-server

Wait for the log line Starting web server before navigating to the UI.

Initial admin setup: navigate to https://your-host-ip:9443/if/flow/initial-setup/ — this URL only works on the first run. Create the admin account here. After setup, the initial-setup flow is disabled.

Reverse proxy with NPM

Add Authentik to Nginx Proxy Manager:

Domain: auth.yourdomain.com
Forward to: authentik-server:9000
SSL: Let’s Encrypt

In NPM Advanced tab:

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
client_max_body_size 10M;

Update AUTHENTIK_URL in your compose environment to https://auth.yourdomain.com after setting up the proxy. Authentik uses this URL in redirect URIs for OAuth2 flows.

Configure your first OIDC application: Nextcloud

Nextcloud is one of the best test applications for Authentik because it has mature OIDC support. This also fills in your user accounts with a real test.

Step 1: Create an OIDC Provider in Authentik

Authentik Admin → Applications → Providers → Create
Select: OAuth2/OpenID Connect Provider
Name: Nextcloud
Client ID: auto-generated (copy for later)
Client Secret: auto-generated (copy for later)
Redirect URIs: https://nextcloud.yourdomain.com/apps/oidc_login/oidc (exact URL for the Nextcloud OIDC app)
Sub Mode: Based on username (default is fine)
Save

Step 2: Create an Application

Admin → Applications → Applications → Create
Name: Nextcloud
Provider: select Nextcloud (from step 1)
Launch URL: https://nextcloud.yourdomain.com
Icon: upload a Nextcloud logo (optional)
Save

Step 3: Configure Nextcloud

In Nextcloud:

Install the oidc_login app via Nextcloud → Apps → search “OpenID Connect Login”
Add to config/config.php:

'oidc_login_provider_url' => 'https://auth.yourdomain.com/application/o/nextcloud/',
'oidc_login_client_id' => 'CLIENT_ID_FROM_AUTHENTIK',
'oidc_login_client_secret' => 'CLIENT_SECRET_FROM_AUTHENTIK',
'oidc_login_auto_redirect' => false,
'oidc_login_button_text' => 'Log in with Authentik',
'oidc_login_scope' => 'openid email profile',
'oidc_login_end_session_redirect' => false,

After adding the config, Nextcloud shows an “Authentik” button on the login page. Clicking it redirects to Authentik, authenticates, and returns to Nextcloud with the user session.

Configure BookStack with LDAP

BookStack’s SAML2 and LDAP support are both good. LDAP is simpler to configure and doesn’t require understanding SAML assertion mapping. Authentik’s built-in LDAP provider serves BookStack accounts directly.

Step 1: Create an LDAP Provider in Authentik

Admin → Applications → Providers → Create → LDAP Provider
Name: LDAP
Bind Flow: default
Search Group: create a group called homelab-ldap — all users in this group are visible over LDAP
Save

Step 2: Create an Application for the LDAP Provider

Admin → Applications → Applications → Create
Name: LDAP
Provider: select LDAP
No Launch URL needed — LDAP isn’t a browser flow
Save

Step 3: Create an LDAP Outpost

Admin → Applications → Outposts → Create
Name: LDAP Outpost
Type: LDAP
Select the LDAP Application
Save

The LDAP Outpost binds to port 3389 on the Authentik worker container (or a dedicated outpost container for more advanced setups). For a simple homelab setup, the embedded outpost (running inside the worker) is sufficient.

Step 4: Configure BookStack

In your BookStack Docker Compose environment:

AUTH_METHOD: ldap
LDAP_SERVER: authentik-worker
LDAP_PORT: 3389
LDAP_BASE_DN: "DC=ldap,DC=goauthentik,DC=io"
LDAP_DN: "cn=ldapservice,DC=ldap,DC=goauthentik,DC=io"
LDAP_PASS: your-authentik-service-account-password
LDAP_USER_FILTER: "(&(objectClass=person)(uid={user}))"
LDAP_FOLLOW_REFERRALS: "false"

The LDAP_BASE_DN format is Authentik’s internal LDAP tree. The LDAP_DN is a bind user — create a service account in Authentik for this purpose (a user with a known password that BookStack uses to search the LDAP directory).

Add MFA for specific applications

Authentik’s MFA is configured per-flow, not per-user. To require TOTP for all logins:

Admin → Flows & Stages → Stages → Create → Authenticator TOTP Stage
Add a Stage Binding in the default authentication flow after the password stage

To require MFA only for specific applications (e.g., Proxmox access but not BookStack):

Create a new authentication flow specifically for high-security apps
Include the MFA stage in that flow
Configure the Proxmox Application to use this high-security flow instead of the default

This is where Authentik’s model shows its depth — granular security policies without per-app code.

User management

Create users: Admin → Directory → Users → Create

Or enable self-enrollment: Admin → Flows → create an enrollment flow and bind it to your Authentik tenant.

User groups: Admin → Directory → Groups → Create

Groups control which Applications users can access. Create groups per tier of access (e.g., homelab-admin, homelab-read, family) and configure Application policy to allow specific groups.

Password reset: Authentik ships with a recovery flow by default. Users navigate to the Authentik login page, click “Forgot password,” and receive an email with a reset link. This requires SMTP configuration.

Backup

Authentik’s data lives in PostgreSQL. Back up with:

docker compose exec authentik-db pg_dump -U authentik authentik \
 > /opt/authentik/backup/authentik-$(date +%Y%m%d).sql

Also back up /opt/authentik/media/ — this contains uploaded files (icons, certificates).

For encrypted LDAP connections or custom TLS certificates, back up /opt/authentik/certs/ as well.

Resource usage

Container	Idle RAM
authentik-server	~200 MB
authentik-worker	~150 MB
authentik-db	~60 MB
authentik-redis	~10 MB
Total	~420 MB

Peak RAM during login storms or during MFA enrollment flows can reach 600–700 MB combined. For a homelab with 16+ GB RAM, this is negligible.

Updating Authentik

Authentik updates can include database migrations. Always check the release notes before updating a major version (e.g., 2024.10 → 2024.12).

# Update the version in your compose file first
# Then:
docker compose pull
docker compose up -d
docker compose logs -f authentik-server

Watch for any migration errors in the server log on startup. Authentik handles migrations automatically on startup; no manual migration command needed for minor updates.

Authentik connects to the other services in the self-hosted stack. The Nextcloud AIO setup guide covers the Nextcloud side of OIDC integration. The BookStack Docker guide covers LDAP configuration for BookStack users. The Vaultwarden guide covers the password manager you’ll want for managing all your service credentials before SSO replaces per-service logins. The Nginx Proxy Manager guide covers the HTTPS reverse proxy that Authentik requires. For external access via Tailscale, the Tailscale guide covers connecting all services over the same WireGuard mesh.

Sources

Authentik documentation – official reference for the Applications, Providers, Flows, and Policies model
Authentik LDAP provider – official details for the built-in LDAP provider that BookStack binds to
BookStack documentation – official admin reference for BookStack’s LDAP and SAML authentication options
Docker Compose documentation – official reference for the multi-container Compose file used to run the Authentik stack

Best NVMe SSDs for Homelab and PC Builds 2026

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-17 · ~10 min read · St. Louis County, MO

NVMe SSD choice is simpler than the market noise suggests. The right drive depends on what you’re using it for — a boot drive for a gaming PC has different requirements than a Proxmox VM storage pool, which has different requirements than NAS cache or a ZFS log device.

The categories that matter

Gaming/desktop OS drive: Sequential speed is largely irrelevant beyond Gen4. The bottleneck is random IOPS for game asset loading, not raw sequential throughput. Any quality Gen4 drive with DRAM cache covers this completely.

Proxmox OS drive (boot): Same as gaming/desktop. The OS disk in a Proxmox server boots once and then runs from RAM. A budget Gen4 with DRAM is perfectly adequate.

Proxmox VM storage (active VMs): Random IOPS matters most. Look for drives with high 4K random read/write ratings and DRAM cache. Avoid DRAM-less drives in this role.

NAS cache (ZFS L2ARC or metadata device): Endurance (TBW) matters here because the cache device is written heavily (the SSD endurance calculator turns a TBW rating and your daily writes into a lifespan in years). Optane (discontinued) was ideal; for current NVMe, look at drives with high TBW ratings.

ZFS ZIL/SLOG device: Ultra-low write latency. High endurance. Small capacity (16–64GB is enough for most homelab ZFS pools). Enterprise-grade or high-endurance NVMe is appropriate here.

Gen3 vs Gen4 vs Gen5: the real-world difference

Generation	Sequential read (peak)	Price per TB	Heat	Best use
PCIe 3.0 (Gen3)	~3,500 MB/s	~$60–80	Low	Secondary storage, existing builds
PCIe 4.0 (Gen4)	~7,000 MB/s	~$70–100	Moderate	OS drives, VM storage — primary recommendation
PCIe 5.0 (Gen5)	~12,000–14,000 MB/s	~$120–160	High (needs heatsink)	Specific high-throughput workloads

For nearly every homelab and gaming use case, Gen4 is the right choice in 2026. Gen5 costs 50–80% more per GB for throughput gains that don’t materialize in typical workloads.

Drive picks by use case

Gaming PC OS drive (1TB)

Primary pick: Samsung 990 Pro 1TB

Sequential: 7,450/6,900 MB/s (PCIe 4.0 × 4)
Random IOPS: 1,400K read / 1,550K write (rated)
DRAM: Yes (LPDDR4)
TBW: 600 TBW
Warranty: 5 years
Approx. street: ~$85–100

The 990 Pro remains the benchmark for consumer Gen4 performance. Consistent random IOPS across queue depths, proven Samsung reliability track record, and the 600 TBW rating puts it beyond any realistic consumer endurance concern. It runs warm under sustained write but within spec.

Value pick: WD Black SN850X 1TB

Sequential: 7,300/6,600 MB/s
DRAM: Yes
TBW: 600 TBW
Approx. street: ~$80–95

Comparable performance to the 990 Pro, competitive pricing, good thermal management. WD’s Western Digital NVMe controller is mature and reliable. Either the 990 Pro or SN850X is a correct choice.

Budget pick for secondary games drive: Crucial P3 Plus 2TB

Sequential: 5,000/4,200 MB/s (PCIe 4.0 but with QLC NAND)
DRAM: No (DRAM-less — acceptable for a secondary games drive, not for VM storage)
TBW: 440 TBW
Approx. street: ~$70–90 for 2TB

DRAM-less drives are acceptable for a secondary drive that stores games and you read more than write. The write cliff under sustained writes isn’t a problem for a drive that mostly does game loading (reads).

Proxmox server: OS drive + VM storage

Boot drive: any reliable mid-range Gen4 — the one server role where DRAM-less is fine

The Proxmox OS disk loads once at boot and then mostly idles, so the DRAM rule below doesn’t apply to it. A 256–500GB drive is plenty for the OS and some log storage. The WD Blue SN580 500GB (~~$45) or Crucial P3 Plus 500GB (~~$40) — both DRAM-less — are fine here; save the DRAM budget for the VM pool, where it actually matters.

VM storage pool: Samsung 990 Pro or WD Black SN850X (same as gaming picks)

The same high-IOPS Gen4 drives that make excellent gaming OS drives make excellent VM storage. For a homelab running 5–10 VMs, a single 2TB drive covers most storage needs. For a pool with multiple drives, consider ZFS mirror (2× drive) for redundancy.

High-endurance option for write-heavy workloads: Samsung 990 Pro at high capacity

If you’re running databases, logs aggregation, or anything writing continuously, the 990 Pro’s 1,200 TBW (2TB) or 600 TBW (1TB) covers years of heavy writes.

NAS build: L2ARC and data drives

For TrueNAS or a Proxmox ZFS pool serving storage:

L2ARC cache device: A small (512GB–1TB) Gen4 drive with high endurance. The L2ARC is written heavily as it caches reads from slower HDDs. High TBW matters; raw sequential speed matters less because L2ARC access patterns are mixed. The Samsung 990 Pro is appropriate; avoid DRAM-less or QLC drives in this role.

ZIL/SLOG device: The ZFS intent log is written every sync write. If you have sync writes (NFS shares to VMs that use sync writes), a dedicated ZIL/SLOG device dramatically reduces write latency. Use a small, high-endurance NVMe. 32–64GB is plenty for most homelab pools. Some homelab operators use used Optane P1600X (older enterprise drives available cheaply used) for this purpose.

Primary storage: HDDs are still the most cost-effective bulk storage. For a NAS, the Seagate IronWolf or WD Red Pro are the relevant NAS-specific drives (helium-filled, vibration compensation, NAS firmware). NVMe is used for cache; HDDs hold the actual data. Because those spinning drives are the moving parts in your homelab, learn their failure signs — a new clicking or grinding noise is the classic early warning, and SMART monitoring plus a real backup is what turns a dying drive into a non-event.

What I run

My daily rig uses a Samsung 970 EVO Plus 1TB — Gen3, from before Gen4 was the norm. It works fine as a gaming boot drive in 2026 because game load time bottlenecks are rarely sequential throughput. If I were buying new today, I’d buy a Gen4 drive. If I’m upgrading: the 970 EVO Plus stays until it fails.

The DRAM cache decision

Never skip DRAM for a primary drive in a server or VM storage role. The difference:

With DRAM	Without DRAM (DRAM-less)
Consistent 4K IOPS across all queue depths	IOPS drop at high queue depths
Gentler post-cache slowdown — the DRAM-held mapping table keeps I/O consistent when the SLC cache fills	Harder write cliff when SLC cache fills; falls to raw NAND speeds with variable latency
Lower latency for small random writes	Higher and variable latency under sustained load
10–30% higher cost	15–25% cheaper

For a gaming boot drive: DRAM-less is acceptable. For anything in a server role: DRAM cache is not optional.

Gen5 NVMe: when it makes sense

PCIe 5.0 NVMe drives (Samsung 9100 Pro, Crucial T705, WD_BLACK SN8100) deliver 12,000–14,000 MB/s sequential reads. They require:

A PCIe 5.0 M.2 slot (AM5 boards, 13th/14th gen and newer Intel)
A heatsink — they generate substantial heat under load
$120–160+ for 1TB

The use cases where Gen5 matters:

Database servers with sustained random write I/O
Video editing with multiple simultaneous 4K/8K streams from the SSD
Large AI model loading where GB-level transfers are common

For gaming, Gen5 saves approximately 0.1–0.3 seconds on a long game load vs Gen4. Not worth the cost premium for that use case.

For the homelab server foundation, the ZFS on Proxmox guide covers pool configuration and ARC tuning that matters more than drive generation in most storage scenarios. For NVMe in a gaming build context, the Gaming PC Build 2026 lists storage picks alongside the full component selection.

Beszel vs Netdata vs Glances: Homelab Monitoring

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

Once you run more than a couple of services, you want to see your homelab — what’s hot, what’s full, what’s down. The lightweight monitoring conversation in 2026 centers on three resource monitors — Beszel, Netdata, and Glances — plus Uptime Kuma, which does a related-but-different job. They’re easy to confuse, so here’s what each actually is, verified against their repos and docs, and how to pick.

One key distinction up front: Beszel, Netdata, and Glances monitor resources (CPU, RAM, disk). Uptime Kuma monitors uptime (is a service reachable?). They’re complementary, not alternatives — most homelabs run one of each.

At a glance

	Beszel	Netdata	Glances	Uptime Kuma
Job	Resource dashboard	Deep real-time metrics	Single-box glance	Uptime / status pages
License	MIT	GPL-3.0 (agent)	LGPL-3.0	MIT
Architecture	Hub + agents	Per-node agent	One process/host	Single app
Multi-server dashboard	Yes	Yes (Cloud/Parent)	Per-host	Yes (checks)
Historical data	Yes	Yes (tiered)	No (export)	Yes (checks)
Footprint	Very light	Heavier (tunable)	Light (Python)	Light
Stars (approx)	~23k	~80k	~33k	~89k
Latest (Jul 2026)	v0.18.7 (pre-1.0)	v2.10	v4.5	2.4.0 (stable)

Star counts rounded; GitHub stars and release versions verified July 2026.

The monitoring map: depth vs weight

Every resource monitor trades how much it shows you against how much it costs to run. Plot the three that way and the choice gets obvious — there is a homelab sweet spot, and Beszel sits right in it.

the homelab sweet spot

Netdata

deep, heavier

Beszel

light + enough

Glances

one box, live

heavier to run ▲

featherweight

deep forensics ▶

a quick glance

Not on this map: Uptime Kuma. It asks a different question entirely — is my service reachable?, not how is the box doing? — so it lives off the depth-and-weight axes. Run it alongside whichever you pick.

Beszel: the simple multi-server dashboard

Beszel (MIT, by henrygd) is the easy default for “show me all my boxes on one screen.” It’s a hub-and-agent design: the hub is a web dashboard built on PocketBase, and a tiny Go-binary agent runs on each host reporting CPU, memory, disk usage and I/O, network, load, temperature, GPU, Docker container stats, and S.M.A.R.T. disk health. It keeps historical data, sends configurable alerts (CPU, memory, disk, bandwidth, temperature, load), and supports multi-user, OIDC, and automatic backups to disk or S3.

It launched in 2024 and grew fast (~23k stars) because it nails the homelab sweet spot: low overhead, dead-simple setup, one clean pane of glass. Be clear about scope, though — it’s deliberately not a full observability platform. No per-second high-resolution metrics, no log aggregation, no APM/tracing, no PromQL. It’s a resource dashboard, and a very good one. (It’s still pre-1.0 (v0.18.7 as of mid-2026), so expect some churn, and verify current first-party Windows-agent support if you need it — that’s historically been community/fork territory.)

Pick Beszel if you want a low-overhead dashboard and alerts across several servers without running a heavier stack.

Netdata: depth and real-time diagnostics

Netdata is the opposite end: maximum depth out of the box. Its agent collects per-second metrics, auto-discovers thousands of metrics with little config, and runs unsupervised ML anomaly detection right on the agent. When you need to understand why a box is misbehaving in real time, nothing here competes. Licensing nuance worth knowing: the agent core is GPL-3.0 (open source), but the UI is closed-source-but-free and Netdata Cloud is closed-source (free and paid tiers) — the self-hosted agent works fully without Cloud.

On the perennial “is Netdata heavy?” debate, be fair: it does far more per node than the lightweights, so it uses more — but it’s tunable. Netdata’s own docs cite roughly 150 MiB RAM and ~5% CPU by default, dropping to ~100 MiB and under 1% CPU with ML and alerts off and ephemeral storage. (You’ll see third-party “200–500 MB/node” claims; those aren’t Netdata’s stated default and depend heavily on config — treat them as unverified.) Its free Cloud tier caps at 5 nodes; a non-commercial Homelab plan is $90/year, and Business is $4.50/node/month.

Pick Netdata if you want deep, real-time metrics and anomaly detection and don’t mind a heavier (but adjustable) footprint.

Glances: the quick single-box look

Glances (LGPL-3.0, by nicolargo) is a Python-based top/htop alternative for a single machine, runnable as a terminal UI, a web UI, or a REST API. It shows live CPU, memory, disk, network, sensors, processes, and containers (Docker/Podman/LXC, even Kubernetes pods) at a glance. The key caveat: it’s not historical by default — you get a live snapshot with only short in-memory history. For real retention you export to InfluxDB, Prometheus, PostgreSQL, and others, then chart it in Grafana (see how Grafana and Prometheus divide that work). Alerting is basic threshold coloring, not a full notification engine.

Pick Glances if you want an instant rich overview of one box for ad-hoc diagnostics, or a lightweight metrics source to feed a bigger stack — not a standalone multi-server dashboard.

Uptime Kuma: a different job

Uptime Kuma (MIT, by Louis Lam, the Dockge creator) is uptime/status-page monitoring, not resource monitoring. It runs HTTP, TCP-port, ping, DNS, and keyword checks to tell you whether a service is up, down, or slow, with 90+ notification channels and public status pages. Its 2.x line is now stable (v2.4, released mid-2026, added MariaDB support and a UI refresh — older “2.x is beta” advice is outdated). Run it alongside a resource monitor: Kuma answers “is it reachable?”, the others answer “why is the host struggling?”

Which question are you actually asking?

The confusion clears the moment you name the question. These tools split into two jobs first, and only then by how deep you want to look.

What do you need to know about your homelab?

“Is a service reachable?”

Up, down, or slow — HTTP, TCP port, ping, DNS.

Uptime Kuma

Checks + status page + 90+ notification channels. Not a resource monitor.

“How are my resources?”

Why is a box struggling — CPU, RAM, disk, temperature. Now pick by depth:

Beszelstart here

One clean dashboard across all your hosts, with alerts. Featherweight.

Glances

A quick, rich look at ONE box right now — terminal, web, or API.

Netdata

Per-second metrics and on-agent ML anomaly detection when you need to dig deep. Heavier.

Which should you run?

Simple resource dashboard + alerts across all hosts → Beszel. The homelab default.
Deep real-time metrics + anomaly detection on a box → Netdata. Heaviest but most powerful.
Quick single-box glance or a metrics source → Glances.
Service uptime + status page + notifications → Uptime Kuma (run it alongside the above).

A sane, common stack is Beszel + Uptime Kuma — resource overview plus uptime/status — reaching for Netdata when you need to deep-dive a specific host and Glances for one-off terminal inspections. If you’re deploying these in containers, the Docker Compose starter stack guide pairs well, and you’ll likely front the web UIs with a reverse proxy.

A note on footprint numbers

The whole appeal of “lightweight” monitoring is low overhead — but precise RAM/CPU figures are the most-fabricated numbers in this space. Beszel is genuinely tiny (a single small Go agent), Glances is light (a Python process), and Netdata is heavier-but-tunable per its own docs. Beyond Netdata’s published defaults, exact figures vary by version, host, and what you’re collecting — so measure on your own hardware with docker stats rather than trusting a blog’s number, including this one.

Sources

Beszel repo & docs: https://github.com/henrygd/beszel · https://beszel.dev/guide/what-is-beszel
Netdata repo & resource-utilization docs: https://github.com/netdata/netdata · https://learn.netdata.cloud/docs/netdata-agent/resource-utilization
Netdata Cloud pricing: https://www.netdata.cloud/pricing/
Glances repo & docs: https://github.com/nicolargo/glances · https://glances.readthedocs.io/
Uptime Kuma repo: https://github.com/louislam/uptime-kuma

Caddy vs Nginx Proxy Manager vs Traefik in 2026

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

By LK Wood IV · Published 2026-06-17 · Updated 2026-07-13 · ~9 min read · St. Louis County, MO

A reverse proxy is the front door to a homelab. It puts clean hostnames and automatic HTTPS in front of all your services, so jellyfin.home.lab just works instead of everyone memorizing 192.168.1.14:8096. Three names dominate the choice in 2026: Caddy, Nginx Proxy Manager (NPM), and Traefik. They’re all free, all open source, and all solve the same problem, but they have genuinely different personalities, and picking well is mostly about matching one to how you like to work. Everything below is verified against each project’s own repos and docs, with the community’s real-world consensus folded in.

The choice in one screen

Skip to the section that fits you, or read the whole thing. Here is the shape of the decision before the details.

	Caddy	Nginx Proxy Manager	Traefik
License	Apache 2.0	MIT	MIT (open-core add-ons)
Interface	Caddyfile (config-as-code)	Web GUI	Config + Docker labels
Auto HTTPS	Most automatic (LE + ZeroSSL)	Per-host, via UI	Cert resolvers (config)
Docker auto-discovery	Plugin only	No	Yes (native)
Learning curve	Moderate	Lowest	Steepest
Written in	Go (single binary)	nginx + OpenResty + Node UI + DB	Go (single binary)
GitHub stars (approx)	~74k	~33.5k	~64k
Latest stable (mid-2026)	2.11.x	2.15.x	3.7.x
Best for	Config-as-code, easiest TLS	Beginners, GUI lovers	Docker/K8s dynamic labs

Star counts and versions are current as of July 2026 and drift over time; check each repo for today’s numbers.

The single most useful way to feel the difference is to watch each one do the exact same job. Here is what it takes to put HTTPS in front of one service in all three:

The same service, three ways

One job — reverse-proxy app.example.com to a container at 192.168.1.10:8080 with automatic HTTPS. Three completely different surfaces. This contrast, not benchmarks, is the actual choice.

Nginx Proxy Manager

point & click

Domainapp.example.com

Forward host192.168.1.10

Forward port8080

✓SSL tab → Request new certificate

~6 clicks · no file · no restart

Caddy

config as code

app.example.com {
reverse_proxy 192.168.1.10:8080
}

3 lines · 1 file · HTTPS is automatic

Traefik

label discovery

labels:
- traefik.enable=true
- traefik.http.routers.app.rule=
Host(`app.example.com`)
- ...tls.certresolver=le

plus a one-time static config (entrypoints, cert resolver) that every service then reuses.

3+ labels per service · auto-routes on deploy

All three arrive at the identical HTTPS front door. NPM asks you to fill a form, Caddy asks you to write two lines, Traefik asks you to label a container. Pick the surface that matches how you already like to work — that, far more than speed, is what makes a proxy feel right six months later.

techfuelhq.com · minimal working config per tool, verified against each project's docs

Caddy: the simplest automatic HTTPS

Caddy is a Go-based web server and reverse proxy under Apache 2.0, fully open source with no paid tier, shipped as a single static binary (~74k GitHub stars, latest 2.11.x). Its headline feature is automatic HTTPS: the moment Caddy knows a hostname, it obtains and renews certificates in the background, using Let’s Encrypt and ZeroSSL with automatic failover, redirects HTTP to HTTPS, and even issues self-signed certs from an internal CA for local names. A working HTTPS reverse proxy is about three lines of Caddyfile, which is exactly why so many people who “just wanted it to work” ended up here. As one r/selfhosted user put it, it’s “brain dead easy… a reverse proxy in as little as 4 lines and 2 of them are the curly brackets.”

The trade-offs: there’s no built-in GUI (config is a text file), and Caddy core doesn’t natively auto-discover Docker containers. The third-party caddy-docker-proxy plugin adds that if you want it, and notably a Caddy maintainer confirms it’s “supported and a recommendation of the Caddy maintainers.” One bit of history worth knowing: Caddy briefly sold commercial licenses in 2017-2019, but permanently moved everything to open source under Apache 2.0 in October 2019, so today it’s unambiguously free. It’s the most-starred of the three and actively maintained.

Pick Caddy if you like config-as-code, want the least-fuss automatic HTTPS on the market, and don’t need a GUI.

Nginx Proxy Manager: the beginner’s favorite

NPM is a web GUI wrapped around nginx + OpenResty + Certbot, distributed as a Docker image, under the MIT license (verified against its raw LICENSE file; despite some secondhand claims that it’s GPL, it is not). You add proxy hosts in a browser, click to request a Let’s Encrypt cert, and it generates the nginx config for you. It has the lowest learning curve of the three by universal consensus, which is why it’s the standard “start here” recommendation, and it currently sits around 33.5k stars on the 2.15.x line. If you go this route, our Nginx Proxy Manager homelab setup guide walks the full install and wildcard-SSL flow.

Two honest caveats. First, its state lives in a database and generated config rather than portable code, so it isn’t naturally version-controlled; keep your own backups. Second, because NPM bundles its own stack (nginx/OpenResty, Certbot, a Node.js UI, and a database), that bundle can lag upstream security fixes, and there have been notable CVEs. The most-cited is CVE-2025-50579 (CVSS 5.3), a CORS-misconfiguration flaw reported against v2.12.3 that lets a malicious website steal an admin’s JWT token and take over the panel; it was still open on the project tracker into the 2.15.x line. The fix is discipline: keep it updated and never expose the admin UI publicly. Recent releases added TOTP two-factor auth and more DNS challenge plugins, which help.

Pick NPM if you want a point-and-click workflow for a handful of services and would rather not touch config files.

Traefik: dynamic discovery for Docker labs

Traefik (MIT, ~64k stars, latest 3.7.x) is a modern, dynamic reverse proxy built for containers, shipped as a single Go binary. Its defining trait: it auto-discovers services and builds routes at runtime by reading provider APIs. Add a few Docker labels to a container and Traefik creates the route instantly, no restart, and it does the same for Kubernetes (including the Gateway API), Consul, Nomad, and more. This is the capability NPM lacks entirely and Caddy needs a plugin for.

The cost is complexity, and the community is split on how much. Traefik divides configuration into static (startup: entrypoints, providers, certificate resolvers) and dynamic (hot-reloaded routers, services, middlewares), and you need to understand that model plus “label discipline.” Some homelabbers find it “ridiculously convoluted… six labels on every container,” while others counter that with a good base config you can get down to “just traefik.enable=true” plus a single router rule. Either way it’s the steepest learning curve here. On licensing, Traefik runs open-core: the proxy is fully free, including its OWASP Coraza WAF integration added in v3, while Traefik Labs sells optional Hub/Enterprise API-management tiers you’ll never need at home. Traefik v3 (GA 2024) also brought HTTP/3, WebAssembly middleware plugins, OpenTelemetry, and a newer experimental FastProxy engine aimed at closing its throughput gap.

Pick Traefik if your lab is Docker- or Kubernetes-heavy, you want services to register themselves as you deploy them, and you’re comfortable with the configuration model.

Which should you run?

The most useful framing from the 2026 community: people rarely pick the wrong proxy; they pick one whose operating style doesn’t match their skill level or their stack. So match it to yourself:

Beginner, few services, wants a GUI → Nginx Proxy Manager. Start here.
Wants config-as-code and the easiest automatic HTTPS, no GUI → Caddy.
Docker/Kubernetes-heavy, wants dynamic auto-registration → Traefik.

A common growth path is to learn on NPM, then migrate to Caddy (for config-as-code) or Traefik (for Docker discovery) as the lab matures, and that migration is easy because you can always read the generated config and copy it out. If you’re building out that Docker layer, the Docker Compose starter stack guide pairs naturally, and if you’re also choosing how to manage those containers, see Komodo vs Portainer vs Dockge.

On performance: the question everyone asks and no one needs

“Which is fastest?” is the first thing people ask and the last thing that should decide it. Real, reproducible 2026 community benchmarks do exist now, and they’re consistent about the order: nginx (the engine under NPM) leads, Caddy is a close second, and Traefik trails on raw requests-per-second and P95 latency. But look at the actual magnitudes against what a homelab does:

The performance question, settled

Roughly what each handles on a small box, from representative 2026 community benchmarks (order is consistent across tests; exact numbers vary by hardware). The bar that matters is the one at the bottom.

nginx / NPM engine~80,000 req/s

Caddy~60,000 req/s

Traefik~45,000 req/s

What a busy homelab actually needs~5-50 req/s

Yes — that sliver. Every option here clears your real load by three to four orders of magnitude.

So "which is fastest" has a real answer — nginx, then Caddy, then Traefik — and it does not matter to you. At homelab scale the proxy is never the bottleneck; your disk, your network, or the backend service is. As the top-voted reply on the big 2026 benchmark thread put it: you won't notice the difference "unless you're running websites with 50k visitors a minute."

techfuelhq.com · magnitudes representative, not a lab-grade benchmark; choose on config style, not throughput

You’ll sometimes see idle-RAM figures too (rough ballparks like ~40-50 MB for the single-binary Caddy and Traefik, more for NPM once you count its bundled nginx, Node UI, and database). Treat those as directional, not gospel, since methodology and versions aren’t standardized. The bottleneck in your lab will be your services, not the proxy in front of them.

Sources

Caddy repository & license (Apache 2.0): https://github.com/caddyserver/caddy · Automatic HTTPS docs: https://caddyserver.com/docs/automatic-https
Caddy open-source move (issue #2786, Oct 2019): https://github.com/caddyserver/caddy/issues/2786 · caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy
Nginx Proxy Manager repository & license (MIT): https://github.com/NginxProxyManager/nginx-proxy-manager
Traefik repository (MIT) & configuration overview: https://github.com/traefik/traefik · https://doc.traefik.io/traefik/getting-started/configuration-overview/
NPM CORS CVE-2025-50579 (CVSS 5.3, NVD): https://nvd.nist.gov/vuln/detail/CVE-2025-50579 · issue thread: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4509
Community benchmark & consensus (r/selfhosted, Oct 2025): https://www.reddit.com/r/selfhosted/comments/1odh46j/nginx_vs_caddy_vs_traefik_benchmark_results/

Frigate NVR Storage Calculator

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

How to use this calculator

Enter how many cameras you run, pick the resolution, frame rate, and codec, choose continuous or motion-only recording, and set how many days of footage you want to keep. The calculator instantly estimates total storage, daily write volume, a recommended drive size, and the /dev/shm value Frigate needs.

If you already know your camera’s bitrate (check its web UI or app), type it into the optional bitrate field — that is the single most accurate input, because Frigate records the stream your camera sends without re-encoding it.

What actually drives Frigate storage

Two numbers decide almost everything:

Bitrate — the data rate of the recorded stream, in Mbps. Continuous recording at 1 Mbps uses about 10.8 GB/day. Everything else (resolution, FPS, codec) matters only because it changes the bitrate.
Retention — how many days you keep. Storage is linear: double the days, double the disk.

Because Frigate copies the camera’s stream rather than transcoding it, the codec choice here estimates what your camera would produce on H.264 vs H.265. H.265 (HEVC) is roughly half the bitrate of H.264 at the same quality — the easiest way to halve your storage is to set the camera to H.265, if its hardware and your decoding setup support it.

Continuous vs motion-only

Continuous 24/7 recording is the safe default for security footage — no gaps, nothing missed. Motion/detect-only recording stores far less, proportional to how active the scene is, but a missed detection means missed footage. The comparison table above shows both modes side by side for your exact setup so you can see the trade in real gigabytes before you commit.

Don’t forget /dev/shm

A storage plan that ignores shared memory is how Frigate setups fail on day one. Frigate buffers decoded frames in /dev/shm, and the default container allocation is small. The calculator outputs a recommended shm-size from Frigate’s own per-camera formula — set it on your container (for an LXC or Docker run) so Frigate has room to work. For the host underneath it, an LXC vs VM decision and a solid storage backend round out a reliable NVR build.

A note on the estimates

When you don’t supply a bitrate, the figures come from typical mainstream-IP-camera bitrates by resolution and codec, scaled by frame rate — good enough to size a drive, but not a substitute for your camera’s real number. Storage uses decimal GB/TB (1 TB = 1,000 GB), matching how drives are sold. Always size up: retention you never use is cheap; running out of space mid-incident is not.

Komodo vs Portainer vs Dockge: Best Docker Manager (2026)

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

For years the answer to “what should I use to manage Docker in my homelab” was just “Portainer.” That changed once Portainer moved a set of previously-free, team-oriented features behind its paid Business Edition — and a wave of self-hosters went looking for alternatives. The two names that keep coming up are Komodo and Dockge. Here’s how all three actually compare in 2026 on the things that matter: licensing, what you get free, and which fits which homelab — verified against each project’s own docs and repositories.

The three at a glance

	Portainer	Komodo	Dockge
License	CE open-source; BE paid	GPL-3.0 (fully open)	MIT (fully open)
Scope	Docker, Swarm, Kubernetes, Podman, edge	Docker + stacks, multi-host, GitOps	Compose only
Multi-host	Yes (governance in BE)	Yes, uncapped	Yes (v1.4+)
RBAC / SSO	Business Edition only	Included	None (by design)
Architecture	Server + agents	Core + Periphery + database	Single Node service
GitHub stars	~38k	~11.6k	~23.7k
Latest (Jul 2026)	CE 2.39 LTS	v2.2 (May)	v1.5 (Mar ‘25)
Best for	Breadth / K8s / teams	Multi-host fleets	Single/dual-host Compose

What you actually run

Uncapped and free has a price, and it is paid in processes, not dollars. Every box below is a separate service you install and keep alive. This footprint, more than any feature list, is the real split between the three.

Dockge1 service

Dockge

One Node container. Your compose files stay on disk. Add one small agent per extra host (v1.5+).

Portainer1 service

Portainer Server+ edge agent · optional

One server container. It stores its own database internally, so nothing extra to run. Edge agents only for remote hosts.

Komodo3+ services, grows per host

Komodo Core+Database (MongoDB)+Periphery agent × each host

A Rust Core, a separate database, and one agent per managed server. This is the "bloat" and "why MongoDB?" you see in every migration thread — the honest cost of no license meter.

Portainer: still capable, now partly paywalled

Portainer is the broadest of the three — it manages Docker, Swarm, Kubernetes, Podman, and edge devices — and its Community Edition is genuinely free and open-source. The friction is what moved to Business Edition (BE):

RBAC is BE-only. BE has a full seven-role hierarchy (Administrator, Environment Administrator, Operator, Namespace Operator, Helpdesk, Standard User, Read-Only); CE has only basic single-tier user management.
SSO/OIDC with provider templates (Microsoft, Google, GitHub; Azure AD, Okta, Ping) and automatic group-to-team mapping is BE-only. In CE, “Custom” is the only OAuth option and automatic group membership can’t be configured.
Audit logging, advanced GitOps, registry management, and S3 backups are BE features too.

The licensing math: BE is free for up to 3 nodes, renewed yearly at no cost, with the full feature set (one license per company domain). Beyond that, Starter is $99/month ($995/year) and Scale is $199/month ($1,995/year); there’s a non-commercial Home & Student plan at $149/year. For a small homelab the 3-node free BE tier is actually generous — the catch is the per-company-domain limit and that the moment you outgrow 3 nodes commercially, you’re into real money.

A recurring CE complaint worth knowing: Compose stacks created in Portainer’s editor become tied to Portainer, and editing the underlying YAML outside the UI is awkward. That single behavior is why many people prefer the other two.

For currency: Portainer is still by far the most-installed of the three (~38k GitHub stars, more than Komodo and Dockge combined) and the most actively released. It ships on a dual track — pick the LTS line (2.39, released Feb 2026, supported into November 2026) for a homelab you don’t want to babysit, not the short-term STS builds (2.43). None of this is the problem. The paywall line is.

The line Portainer drew

Community Edition is genuinely free, but the team-oriented features moved to paid Business Edition. This is the exact line that started the exodus — and the reason Komodo and Dockge draw no line at all.

Portainer

Free · Community Edition

Container & stack management Compose & K8s / Swarm Basic single-tier users One "Custom" OAuth option

Paid · Business Edition

RBAC · 7-role hierarchy SSO / OIDC + group mapping Audit logging · S3 backups Advanced GitOps · registries

Free up to 3 nodes, then $99–$199/mo

Komodo

No edition split. RBAC, uncapped multi-host, GitOps — all in the free GPL-3.0 build.

Dockge

No line to draw. It omits RBAC and SSO by design, not by paywall — everything it does is free.

Komodo: open-source, uncapped, more to run

Komodo is the project most directly positioned against Portainer’s licensing. It’s GPL-3.0, written mostly in Rust, and its docs are blunt about it: “There is no limit to the number of servers you can connect… There is no limit to what API you can use for automation… No ‘business edition’ here.”

Architecturally it’s a Core + Periphery model: Komodo Core is the central service (and talks to a database — MongoDB recommended, with FerretDB/Postgres as an alternative), and a lightweight, stateless Periphery agent runs on every managed host, IP-whitelisted, reporting container status, logs, and system usage back to Core. You deploy it with Docker Compose. The payoff is real multi-host fleet management with Git-backed (GitOps) deployments, all free. The cost is operational: you’re now running a Rust service plus a database plus an agent per server — more moving parts than a single container. That footprint is the one honest knock on Komodo in 2026: browse any migration thread and you’ll see “bloat” and “why does it need MongoDB?” alongside the praise. It’s a fair trade for uncapped fleet management, but go in expecting to run a database. At ~11.6k GitHub stars and a steady release cadence (v2.2 landed May 2026) it’s younger than Portainer but has strong momentum and an actively responsive maintainer.

One practical gotcha to know before you commit: Komodo substitutes secrets and variables into compose files using its own bracket syntax, not standard Compose interpolation. If you lean on .env files or portable ${VAR} references, check that your workflow survives the move — it’s the single most-cited friction point from people coming off Portainer.

Dockge: the lightweight Compose manager

Dockge comes from Louis Lam, the creator of Uptime Kuma, who built it after being frustrated with Portainer’s stack management (spinning loaders, unclear errors). It’s MIT-licensed and deliberately narrow: it manages Docker Compose and nothing fancier. The defining feature is that it keeps your compose.yaml editable on disk — it “won’t kidnap your compose files,” so they stay usable with normal docker compose commands outside the UI. You get a reactive web editor, an interactive terminal, a docker run → Compose converter, and multi-agent support since v1.4.

What it deliberately lacks: RBAC, OIDC, vulnerability scanning, and a REST API. That’s the point — it’s a clean UI over Compose, not a platform. At ~23.7k stars it’s the most popular of the three by a wide margin, reflecting how many self-hosters just want exactly this.

The one caveat to weigh honestly in 2026: Dockge’s development has gone quiet. The last tagged release, v1.5, shipped in March 2025 — well over a year ago — and the subreddit now has recurring “Dockge alternatives?” threads from people whose small gripes have piled up with no fixes landing. It still works, it’s simple, and MIT means it can’t be pulled out from under you, but if you want a tool under active iteration, that’s a real point for Komodo or the newer Arcane. If Dockge does exactly what you need today, its stability is a feature; if you were hoping the rough edges would get sanded down, temper that expectation.

Portainer vs Dockge vs Komodo: head-to-head

The profiles above cover each tool on its own. Here are the direct pairwise matchups people actually search for.

Portainer vs Dockge

Portainer is a full platform (Docker, Swarm, Kubernetes, Podman, edge) with a heavier UI; Dockge is a focused Compose-only manager with a lighter one. The deciding factor is usually file ownership: Portainer’s editor tends to tie a stack to Portainer, while Dockge leaves your compose.yaml on disk and editable with plain docker compose. If you run one or two hosts and live in Compose, Dockge wins on simplicity; if you need Kubernetes or Business Edition team features, Portainer wins on breadth.

Portainer vs Komodo

Both do multi-host, but the split is licensing. Portainer gates RBAC, SSO/OIDC, and audit logging behind Business Edition (free only up to 3 nodes); Komodo is fully GPL-3.0 with no business edition, no server cap, and no API cap. Choose Komodo if you want uncapped fleet management and GitOps without a license meter, and accept running a database plus a per-host agent. Choose Portainer if you need its breadth (Kubernetes/Swarm/Podman) or fit inside the free 3-node BE tier.

Komodo vs Dockge

Same open-source spirit — both are fully free — but very different scope. Dockge is a single Node service for Compose on one or two hosts; Komodo is a Rust Core plus a database plus a per-host Periphery agent, built for a fleet with Git-backed deployments. Pick Dockge for a tidy single-host UI, and Komodo when you’ve outgrown one host and want real multi-server automation.

Which should you run?

One or two hosts, you like Compose, you want it to stay portable → Dockge. Lightest, simplest, your files stay yours.
A fleet of hosts, you want GitOps and uncapped management, and Portainer’s licensing annoyed you → Komodo. Free and uncapped; accept running a database and per-host agents.
You genuinely need Kubernetes/Swarm/Podman breadth, or BE team features, and fit the 3-node free tier (or can pay) → Portainer.

Community sentiment in 2026 trends Komodo > Dockge > Portainer for self-hosters, but that ranking is use-case-dependent, not absolute. If you’re just standing up your first stacks, the Docker Compose starter stack guide pairs well with Dockge; if you’re managing Docker across multiple Proxmox nodes, Komodo’s fleet model is the natural fit.

Moving off Portainer without breaking anything

The single most common follow-up question — and one of the top searches on this exact topic — is how to actually switch. The reassuring part: Portainer never owned your containers. It only ever held its own view of the Docker engine, so migrating is additive, not a risky teardown. You install the new tool alongside Portainer and move stacks over one at a time.

The cleanest path, whichever tool you land on, is to get your compose files into Git first (or at least onto disk in a tidy folder tree). Once your stacks are plain compose.yaml files you control, both alternatives adopt them directly and Portainer’s lock-in stops mattering.

To Dockge is almost trivial: point Dockge at the directory holding your compose files and it picks them up as stacks — the files were already yours. This is why the “Portainer → Dockge → Komodo” path shows up so often in the community: Dockge is the low-friction first step off Portainer.
To Komodo takes more setup (stand up Core, a database, and a Periphery agent per host), but then you add each stack pointing at its compose file, ideally from your Git repo, and redeploy. Do it one stack at a time, confirm health, then move the next. Leave Portainer running until the last stack is across, then remove it.

The one gotcha that bites people: secrets you injected through Portainer’s UI don’t come along. Portainer stores stack environment overrides in its own database, so those values live nowhere in your compose files. Before you decommission Portainer, export or re-note every override and re-add it as a Komodo variable (remember its bracket syntax) or a mounted .env. Miss one and a stack redeploys with a blank password. Plan the secrets, and the rest of the move is genuinely low-drama.

Other Portainer alternatives: Arcane, Dockhand, Coolify, and Yacht

Komodo and Dockge are the two names that come up most, but the “Portainer alternatives” conversation in 2026 is wider. Four more are worth knowing, along with where each actually fits:

Arcane — a modern, mobile-friendly Docker UI written in Go, so it ships as a single lean container. It’s BSD-3-Clause licensed with real-time metric graphs and GitOps, and it’s the newest name gaining serious momentum (~5k+ GitHub stars and active development). If you like Dockge but want container-level management and a nicer dashboard, Arcane is the one to try — it’s the tool behind the Dockge vs Arcane searches.
Dockhand — a security-focused manager (BSL 1.1) built around image vulnerability scanning and safe-pull protection, which scans a new image before it swaps a running container. It’s newer and rougher than Arcane, but it’s the pick if update safety is your priority.
Coolify — worth calling out because it’s a different category. Coolify is a self-hosted PaaS (a Heroku/Vercel-style, Git-driven deploy platform with 280+ one-click services), not a container-management UI. If your goal is “push to Git and get a running app with SSL and a domain,” reach for Coolify; if it’s “see and control the containers I already run,” that’s Portainer/Dockge/Komodo territory. That category gap is the honest answer to Portainer vs Coolify.
Yacht — a lightweight, template-driven Docker UI (Docker and Podman) built around simplicity. It’s fine for a single host, but it can’t match Portainer on multi-host management, team access, or Kubernetes — so Portainer vs Yacht really comes down to “simple templates” vs “full platform.”

One more, for completeness: if you’re actually running Kubernetes, Rancher — not Portainer — is the enterprise-grade tool for that, and it’s overkill for a plain-Docker homelab.

The honest verdict

There’s no single winner — there’s a right tool per situation. Dockge is the easy recommendation for most single-host homelabs: light, open, and it respects your files. Komodo is the answer when you’ve outgrown one host and don’t want a license meter on your own infrastructure. Portainer remains the most capable platform and is fine if the free 3-node BE tier covers you or you need Kubernetes — just go in knowing which features are CE and which require paying.

One thing I won’t fake: resource footprint. There’s no reliable, current head-to-head RAM/CPU benchmark across all three, and it varies by version and how many stacks and agents you run. Dockge is lightest by design; Komodo has the largest baseline (Core + database + agents); Portainer is in between. If footprint decides it for you, run each for a day and watch docker stats on your own hardware — and use our Docker RAM planner to size the host before you commit. That’s the only number that’s actually yours.

Sources

Portainer CE vs BE comparison (RBAC, SSO/OIDC split): https://www.portainer.io/blog/portainer-community-edition-ce-vs-portainer-business-edition-be-which-should-you-install
Portainer Business Edition pricing: https://docs.portainer.io/faqs/licensing/what-is-the-pricing-for-business-edition
Portainer 3-nodes-free Business Edition license: https://www.portainer.io/take-3
Portainer release lifecycle (LTS 2.39 / STS 2.43): https://docs.portainer.io/start/lifecycle
Komodo project + docs: https://komo.do/docs/setup · https://github.com/moghtech/komodo (GPL-3.0, ~11.6k stars, v2.2, verified July 2026)
Dockge repository: https://github.com/louislam/dockge (MIT, ~23.7k stars, latest release v1.5 dated March 2025, verified July 2026)
Portainer CE repository (stars/version): https://github.com/portainer/portainer
Arcane (Go Docker UI): https://github.com/ofkm/arcane
Coolify (self-hosted PaaS): https://coolify.io/
Portainer alternatives roundup (Arcane, Dockhand, Dockge, Komodo): https://www.bitdoze.com/portainer-alternatives/
Community migration sentiment (r/selfhosted, 2026): “Does it make sense to move from Portainer to Komodo?”, “Switched from Portainer to Dockge, and today to Komodo”, “Dockge alternatives?” threads

Local LLM Speed Calculator: Estimate Tokens per Second

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

How to use this calculator

Enter the model’s size in billions of parameters, pick the quantization you’ll run, and choose your GPU (or enter a custom memory bandwidth). The calculator estimates the generation speed in tokens per second — the speed you feel while the model is typing its reply — plus the weights size and a rough VRAM figure. The table compares common quant levels so you can see the speed-vs-quality trade for your exact hardware.

If you’ve measured your real tokens/sec on a known model, nudge the efficiency slider until the estimate matches — then its predictions for other models and quants on your rig get more accurate.

Why bandwidth, not TFLOPS, decides speed

Local LLM generation is memory-bandwidth-bound. To produce each token, the GPU streams the model’s weights out of VRAM once and does comparatively little arithmetic per byte. So the limiting factor is how fast the card can read memory — its GB/s — not its raw compute. That’s why a memory-bandwidth number predicts token speed far better than a TFLOPS rating, and why the formula is simply:

tokens/sec ≈ (memory bandwidth ÷ weights size) × efficiency

A 70B model at Q4_K_M is ~39 GB of weights; divide a card’s bandwidth by that and you’re in the right ballpark. Halve the weights (a lighter quant) and you roughly double the speed.

Speed vs. fit: two different questions

“How fast will it run?” and “will it even fit?” are separate problems. This tool answers the first. A model can fit comfortably in VRAM and still be slow (big model, modest bandwidth), or be fast in theory but not fit at all (not enough VRAM, forcing slow CPU offload). For the fit side — VRAM for weights plus the KV cache at your context length — use the LLM VRAM Calculator. Run both before you buy a card or pick a model.

Picking a model for your card

If the estimated speed is comfortable (say 15+ tok/s for chat) and the model fits, you’re set. If it’s too slow, your levers are: a lighter quant (faster and smaller, slight quality cost), a smaller model, or a card with more bandwidth. For which models actually fit each card in the first place, the VRAM-tier guide to local LLMs by GPU maps it tier by tier; for build-level guidance, see the single-RTX-5060 local-LLM walkthrough and the $1,000 local-AI workstation for a tuned setup.

A note on accuracy

These are estimates from the bandwidth-bound model, most reliable for larger models and short-to-medium contexts. Real numbers vary with context length (the KV cache grows and gets re-read), the inference backend, and whether the whole model fits in VRAM. Use the figure to compare GPUs and quants and to size expectations — not as a guaranteed benchmark.

Move a Proxmox VM to a New Host Without a Cluster (2026)

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

Most homelabs aren’t clusters — they’re one Proxmox box, maybe two, running independently. (If you’d rather build an actual cluster with live migration and high availability instead, Proxmox clustering and HA is the guide for that path.) So when you buy new hardware and need to move your VMs and containers over, the cluster-only qm migrate command doesn’t apply. The good news: you don’t need a cluster. There are three supported ways to move a guest between standalone Proxmox hosts, and this guide covers the exact commands and the pitfalls for each — drawn from the official qm/pct manpages and Proxmox’s backup documentation.

Keep the source until the destination is verified. Whichever method you use, don’t delete the original guest until the new one boots, networks, and works. Every method below leaves you a fallback if you don’t rush the cleanup.

The three methods at a glance

Method	Downtime	Crosses storage types?	Needs	Best for
`qm/pct remote-migrate`	Near-zero (with `--online`)	Only when online	API token	Minimal-downtime moves
`vzdump` + `qmrestore`	Some (mode-dependent)	Yes	File copy (scp/rsync)	Most moves; mismatched storage
Proxmox Backup Server	Some (or `--live-restore`)	Yes	Shared PBS	If you already run PBS

Method 1: `qm remote-migrate` (direct, supports live)

This transfers a guest straight from one host to another, authenticated by an API token. It’s the only no-cluster method that supports live (online) migration, but Proxmox still labels it an EXPERIMENTAL feature (it landed in PVE 7.3, November 2022). Treat it as CLI-only and test before trusting it with something critical.

Syntax (VM):

qm remote-migrate <vmid> [<target-vmid>] <target-endpoint> \
--target-bridge <bridge> --target-storage <storage> [OPTIONS]

The <target-endpoint> is:

apitoken=PVEAPIToken=user@realm!token=SECRET,host=ADDRESS[,fingerprint=FP][,port=PORT]

A real example (move VM 134 to become VM 205 on pve-dest, live):

qm remote-migrate 134 205 \
'apitoken=PVEAPIToken=root@pam!migrate_token=abc123,host=pve-dest,fingerprint=D4:9A:3F:...:CD' \
--target-bridge vmbr0 --target-storage local-lvm --online

Useful options: --online (live-migrate a running VM), --delete (remove the source after success), --bwlimit. For containers, use pct remote-migrate with the same form plus --restart (it restarts the CT on the destination). Passing the special value 1 to --target-bridge/--target-storage maps each source item to a same-named target (identity mapping).

Set up the API token on the target host: Datacenter → API Tokens → Add, user root@pam. Either turn off Privilege Separation (full account access) or keep it on and grant the token the Administrator role on path / (Datacenter → Permissions → Add → API Token Permission). Get the fingerprint with:

openssl x509 -fingerprint -sha256 -noout -in /etc/pve/nodes/$(hostname)/pve-ssl.pem

The two big limitations: remote-migrate can’t move a guest that has snapshots (delete them first, or use backup/restore), and offline migration can’t cross storage types — you’ll hit cannot migrate from storage type lvmthin to zfspool. The workaround is to migrate while the VM is running (online storage migration can change storage type), or use Method 2.

Method 2: `vzdump` + `qmrestore` / `pct restore` (most reliable)

This is the storage-agnostic workhorse: back the guest up, copy the file, restore it on the new host. It works across mismatched storage types where remote-migrate refuses.

On the source:

vzdump 777 --mode snapshot --compress zstd --dumpdir /var/lib/vz/dump

--mode snapshot is the default and avoids downtime; use --mode stop for maximum consistency (more downtime). zstd is the fast modern compressor. You get a vzdump-qemu-777-….vma.zst (VM) or vzdump-lxc-777-….tar.zst (container).

Copy it to the new host:

rsync -avP /var/lib/vz/dump/vzdump-qemu-777-*.vma.zst root@pve-dest:/var/lib/vz/dump/

On the new host — restore (VM, then container):

qmrestore /var/lib/vz/dump/vzdump-qemu-777-*.vma.zst 500 --storage local-lvm --unique
pct restore 600 /var/lib/vz/dump/vzdump-lxc-777-*.tar.zst --storage local-lvm

Pick a free target VMID (or pass --force to overwrite an existing one), set --storage to a pool that exists on the new host, and use --unique to assign a fresh MAC so two copies don’t fight on the network.

Method 3: Proxmox Backup Server (if you already run it)

If you run PBS for 3-2-1 backups, it doubles as a migration path. Add the same PBS as storage on the new host (Datacenter → Storage → Add → Proxmox Backup Server), then select the guest’s backup in the storage tree and Restore, or use qmrestore/pct restore against the PBS-backed storage. PBS deduplicates and only transfers changed chunks, so it’s efficient for repeated moves, and --live-restore (PBS only) boots the VM immediately while the data restores in the background. One catch: for encrypted backups you must supply the same encryption key on the new host or the restore fails.

The pitfalls that bite

Storage-type mismatch. Offline remote-migrate can’t cross types (lvmthin → zfspool). Use online migration or vzdump+restore with the right --storage.
Bridge naming. The new host must have the bridge the guest expects (vmbr0), or you map it with --target-bridge. A guest that boots onto a non-existent bridge comes up with no network.
VMID conflicts. If the target ID is taken, pick a new target VMID, or use --force (overwrite) / --unique (fresh MAC) deliberately.
Snapshots block remote-migrate. Delete them first or take the backup/restore route.

Which should you use?

For a one-off move to new hardware, use vzdump + restore — it’s the most reliable, crosses storage types, and leaves the original safe. For minimal downtime on a running service, use remote-migrate --online, accepting its experimental status and testing first. If you already run PBS, restoring from it is the least extra work. Whatever you choose, keep the source guest until the destination is verified — and if you’re moving because you’re rebuilding a host, read the PVE 8→9 upgrade gotchas before you reinstall.

Sources

Proxmox qm manual (remote-migrate syntax): https://pve.proxmox.com/pve-docs/qm.1.html
Proxmox pct manual (container migration/restore): https://pve.proxmox.com/pve-docs/pct.1.html
Proxmox vzdump documentation: https://pve.proxmox.com/pve-docs/chapter-vzdump.html
Proxmox Backup and Restore wiki: https://pve.proxmox.com/wiki/Backup_and_Restore

PoE Power Budget Calculator: Will Your Switch Power It All?

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

How to use this calculator

Enter how many of each PoE device you have — access points, fixed cameras, PTZ cameras, VoIP phones, and anything else — with the wattage each draws. Set the average cable run length and a headroom percentage, and the calculator returns the total switch PoE budget you should buy. Enter your switch’s actual budget too, and it tells you whether it fits with watts to spare or falls short.

The defaults are typical values; for an accurate result, set each device’s real rated draw (it’s on the spec sheet or the device itself).

Switch budget vs. device draw

A PoE switch advertises a total PoE budget — say 60 W or 250 W — which is the combined wattage it can deliver across all ports at once, measured at the switch (the PSE, power-sourcing equipment). Your devices (PDs, powered devices) are rated by what they consume, and the difference between the two is lost in the cable. So the budget you need isn’t just the sum of device labels: it’s that sum, plus cable losses, plus headroom. Size for the switch side, not the device side.

The headroom rule

Always leave room. Power-on inrush, an AP that ramps up under a full client load, a camera switching on night-vision IR, and underestimated cable loss all push real draw above the nameplate sum. About 20% headroom keeps ports reliable and leaves space to add a device later. A switch run at 100% of budget will start dropping power to ports the moment something spikes — usually as a confusing, intermittent outage rather than a clean failure.

What this pairs with

Once you know the budget, the budget homelab networking gear guide covers switches that hit common budget tiers, and the MikroTik CRS305 review is worth a look if you’re combining PoE with a 10GbE uplink. If your APs are the big draw, the Wi-Fi 7 guide covers which APs need PoE+/bt versus plain PoE.

Proxmox VE 8 to 9 Upgrade: The Gotchas to Know First (2026)

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

By LK Wood IV · Published 2026-06-17 · Updated 2026-07-13 · ~8 min read · St. Louis County, MO

Proxmox VE 9 has been out since August 2025, and the current release — 9.2, built on Debian 13.5 “Trixie” with Linux kernel 7.0 — is what a fresh in-place upgrade from 8 lands you on today. The 8-to-9 in-place upgrade is officially supported. It is also a real version jump, not a point release, and it ships a handful of breaking changes that can leave a node off the network or refusing to boot if you walk in unprepared.

There’s a clock on it now, too: Proxmox VE 8 reaches end of standard support in August 2026, which is why upgrade searches are climbing through the summer. This is the pre-flight guide: what to check before you start, the gotchas that actually bite, and the upgrade steps themselves — built from Proxmox’s official Upgrade_from_8_to_9 documentation and the issues the community has reported hitting. The mechanism is not scary. The preparation is the whole job.

Back up first, always. Proxmox’s own guidance is blunt: “A valid and tested backup is always required before starting the upgrade process.” If you take one thing from this page, take that.

Proxmox VE 8's support clock

The 8→9 upgrade isn't urgent because 9 is shiny — it's urgent because 8 runs out of official support. A homelab box keeps booting afterward, but with no more security or bug fixes.

End of standard support

August 2026

Jul 2026 — you are here ▼

Supported · since Jun 2023

Unsupported

● Jun 2023 — PVE 8 released Aug 2026 — EOL →

PVE 9 has been available since August 2025, so there's a mature 9.x line (now 9.2) to land on — you're not an early adopter. Waiting for a point release you trust is still fine; just remember that wait now has a hard deadline a few weeks out.

techfuelhq.com · dates per Proxmox's official support-lifecycle table

The short version

Get every node to PVE 8.4.1 or later first.
Run pve8to9 --full and clear every warning before touching repositories.
Back up all VMs/containers (ideally a tested 3-2-1 backup) and make sure you have IPMI or physical console access.
Switch repos from bookworm to trixie, apt update && apt dist-upgrade, reboot into the new kernel (7.0 on the current 9.2).
On a cluster: one node at a time, keep quorum, Ceph to Squid first.
Expect possible NIC renames and LVM autoactivation changes — handle them before you reboot.

What you’re actually upgrading to

When you point your repositories at Trixie and run apt dist-upgrade, APT installs the current Proxmox VE 9 packages — you don’t get to choose 9.0. As of mid-2026 that means you land directly on Proxmox VE 9.2 (released May 21, 2026), not the original 9.0 from August 2025. The stack underneath you becomes:

Debian 13.5 “Trixie” and Linux kernel 7.0 (up from the 6.14 that shipped with 9.0)
QEMU 11.0, LXC 7.0, ZFS 2.4
Ceph Tentacle 20.2 as the new default for hyperconverged clusters, with Squid 19.2 still available (you still upgrade existing Ceph to Squid before the PVE jump — see the cluster section)

The headline 9.2 additions over 9.0 are a dynamic load balancer that migrates guests across a cluster from live CPU/RAM utilization while respecting your HA rules, native WireGuard and BGP in the SDN stack, and custom CPU model management in the web UI. None of this changes the upgrade procedure — but it’s worth knowing you jump straight to the current release, and that the newer kernel is what drives the NIC-rename and PCI-passthrough gotchas further down.

Before you touch anything

The prerequisites from the official guide:

Be on PVE 8.4.1+ on every node. The pve8to9 checklist ships in the latest 8.4 packages.
Tested backups of every guest. Test a restore in a lab if you can.
At least 5 GB free on the root filesystem (10+ GB recommended) for the package transition.
Console access that isn’t the web GUI. Use IPMI/iKVM or a physical console, or SSH inside tmux/screen — never the GUI’s noVNC console, which dies with the services mid-upgrade.
Ceph users: upgrade Ceph to 19.2 Squid before upgrading Proxmox.
Co-installed Proxmox Backup Server: upgrade PBS to version 4 first.

Run the checklist: `pve8to9 --full`

Before changing a single repository line, run:

pve8to9 --full

It flags common incompatibilities — repository state, LVM, boot configuration, known package conflicts — but it does not fix anything for you. Work through every warning, then run it again until it’s clean. This one command prevents the majority of failed upgrades.

The gotchas that actually bite

These are the changes most likely to cause a bad day. Most are easy to handle if you handle them before the reboot.

LVM autoactivation is now off by default

On Proxmox 9, LVM autoactivation is disabled by default for new logical volumes in shared-LVM setups. Existing volumes keep their old behavior, but this trips people on shared storage. There’s a migration helper at /usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation, and some LVM thin pools need a manual repair afterward:

lvconvert --repair pve/data

Network interfaces can get renamed

The newer kernel can recognize additional NIC hardware features, which changes the predictable interface name. If your vmbr0 bridge points at the old name, the host boots with no network. Proxmox ships pve-network-interface-pinning to lock your current names in place — run it before the upgrade, and keep console access handy just in case.

If you run a Ceph Full Mesh with post-up /usr/bin/systemctl restart frr.service, that line will deadlock on 9 — switch it to a conditional restart.

Boot and systemd changes

Remove the systemd-boot meta-package where proxmox-boot-tool manages booting (the upgrade notes call this out).
GRUB on LVM in UEFI mode can fail to install; the fix is [ -d /sys/firmware/efi ] && apt install grub-efi-amd64.
/etc/sysctl.conf is no longer honored by systemd-sysctl — move any custom kernel tunables into /etc/sysctl.d/<NN>-name.conf.

Containers, passthrough, and migration

cgroup v1 is removed. Containers running systemd older than 230 (CentOS 7, Ubuntu 16.04) won’t start — migrate those guests first.
PCI passthrough can break on the newer kernel (first widely reported on 6.14; the current 9.2 ships kernel 7.0). If a passthrough VM misbehaves, the known workaround is pinning an older kernel until it’s resolved.
Live migration between different CPU vendors (Intel↔AMD) can leave guests unresponsive — plan maintenance windows accordingly.
NVIDIA vGPU needs driver ≥570.158.02 (GRID 18.3+); Veeam is incompatible with QEMU machine version ≥10.0.

Six green lights before you touch a repo

The 8→9 mechanism is routine. These six pre-flight checks are where the whole risk lives. Get every lamp green before you run apt dist-upgrade — no exceptions.

1 · On PVE 8.4.1+, every nodepveversion

The pve8to9 checker only ships in the latest 8.4 packages.

2 · A tested backup of every guestvzdump / PBS

Not just taken — restore-tested. It is your only real undo.

3 · pve8to9 --full comes back cleanpve8to9 --full

It only reports; you fix each warning, then re-run until it is zero.

4 · NIC names pinnedNIC pinning

The new kernel can rename interfaces; a stale vmbr0 comes up with no network.

5 · Console that isn't the web GUIIPMI / tmux

The GUI's noVNC console dies with the services mid-upgrade. Use IPMI, physical, or SSH in tmux.

6 · Ceph on 19.2 Squid (if hyperconverged)ceph -v

Upgrade Ceph to Squid before PVE. No Ceph? This one is a free pass.

All six green → apt dist-upgrade Miss one and the upgrade can still “succeed” — then the node reboots onto no network, or won't boot at all. The checklist is the job.

techfuelhq.com · prerequisites per Proxmox's official Upgrade_from_8_to_9 guide

The upgrade itself

Once pve8to9 --full is clean and you’ve handled the gotchas above:

Migrate guests off the node you’re about to upgrade (on a cluster).
Point repositories at Trixie. Switch bookworm → trixie across your APT sources and the Proxmox repo (the deb822 .sources format is recommended on 9). Update Ceph repos to Squid/trixie if applicable.
Upgrade:
```
apt update
apt dist-upgrade
```
Answer the config-file prompts deliberately — for /etc/lvm/lvm.conf the maintainer version is recommended; for /etc/default/grub, diff it if you’ve customized it.
Reboot into the new kernel — required (the current 9.2 ships kernel 7.0). Reboot even if you were already running a 6.x kernel on 8; the 9 kernel is rebuilt against the new compiler and ABI. Then confirm:
```
pveversion # should report 9.x
```
Hard-refresh the web UI (Ctrl+Shift+R) so you’re not staring at a cached 8.x interface.

If you run a cluster

All nodes on 8.4.1+ before you start.
One node at a time, maintaining quorum throughout. Upgrade, reboot, confirm it rejoins healthy, then move on.
Ceph → 19.2 Squid first for hyperconverged setups.
HA groups are deprecated in favor of HA rules; the migration happens automatically once every node is on 9.0. If HA acts up, check journalctl -eu pve-ha-crm.

If you lean on community automation for cluster nodes, give the helper-scripts safety guide a read first — running anything as root mid-migration deserves the same caution.

Honest verdict: upgrade now, or wait?

If your Proxmox 8 setup is doing its job and you don’t need anything specific in 9, waiting for a point release you trust is perfectly reasonable — let the edge cases settle. The one thing that’s new in 2026: PVE 8 reaches end of standard support in August 2026, so “wait” now means “wait a few weeks, not indefinitely.” Being a release behind on a homelab is fine; sitting on an unsupported, unpatched hypervisor is a different call. There’s plenty of runway on the mature 9.2 line to land on before the cutoff.

When you do upgrade, the deciding factor isn’t timing, it’s preparation: a tested backup, a clean pve8to9 --full, pinned NIC names, real console access, and a read of the official release notes for your hardware. The upgrades that go sideways are almost always the ones that skipped the checklist — old GPUs, PCI passthrough, and shared-LVM storage are the usual suspects. Do the pre-flight, keep a solid backup you can fall back to, and the jump to 9 is routine.

Sources

Proxmox VE official upgrade guide — Upgrade from 8 to 9: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
Proxmox VE roadmap / 9.x release notes: https://pve.proxmox.com/wiki/Roadmap
Proxmox VE support lifecycle and end-of-life dates (FAQ): https://pve.proxmox.com/wiki/FAQ
Proxmox VE 9.2 release announcement (Debian 13.5, kernel 7.0, dynamic load balancer, WireGuard SDN): https://proxmox.com/en/about/company-details/press-releases/proxmox-virtual-environment-9-2
Proxmox forum — PVE 8 to 9 in-place upgrade reports: https://forum.proxmox.com/threads/pve-8-to-9-in-place-upgrade.170013/

SSD Endurance Calculator: How Long Will Your SSD Last?

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

How to use this calculator

Enter your drive’s capacity and its endurance rating — either as TBW (terabytes written, common on consumer SSDs) or as DWPD (drive writes per day, common on enterprise drives) plus the warranty period. Then set how much you write per day (pick a workload preset or enter your own) and, optionally, a write amplification factor. The calculator returns the estimated lifespan in years, your effective write rate in DWPD, and how much endurance you burn per year.

The defaults model a 1 TB TLC SSD (600 TBW) on a moderate homelab load. For an accurate result, use your drive’s real rated TBW or DWPD from its spec sheet.

TBW vs. DWPD — same rating, two units

Manufacturers express SSD endurance two ways. TBW is the total terabytes you can write over the warranty; DWPD is how many full-capacity overwrites per day the drive tolerates for the warranty period. They’re interchangeable:

TBW = DWPD × capacity (TB) × 365 × warranty years

So a 1 TB drive at 0.3 DWPD over a 5-year warranty is rated for 0.3 × 1 × 365 × 5 ≈ 548 TBW. Consumer drives usually quote TBW; datacenter drives quote DWPD because they’re built for constant rewriting. This tool accepts either and shows both.

Write amplification — the homelab multiplier

Your endurance is consumed by what the NAND flash actually writes, not what your OS reports. Because flash erases in large blocks, a small logical write can force a larger physical one — that ratio is the write amplification factor (WAF). Plain desktop use sits near 1; copy-on-write filesystems (ZFS, Btrfs), databases, and chatty logging push it to 2–10x. A WAF of 3 burns your TBW three times faster, so set it if you run ZFS or VM workloads on Proxmox — it’s the difference between “lasts decades” and “lasts a few years.”

What this pairs with

If your big write load is video, the Frigate NVR storage calculator estimates the GB/day a camera setup writes — plug that number in here to size an endurance-appropriate drive. And if you’re protecting that data, the Proxmox Backup Server 3-2-1 guide covers doing it right.

Subnet & CIDR Calculator: IP Ranges, Masks, Hosts

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

How to use this calculator

Type an IPv4 address and choose a CIDR prefix (the /24 part). The calculator instantly shows the network address, broadcast address, the usable host range, total and usable host counts, the subnet mask, and the wildcard mask — and tells you whether the address is private, public, or special-use. To plan VLANs or segments, set a longer split prefix and it lists every child subnet.

Everything runs in your browser; nothing is sent anywhere. The result is encoded in the URL, so you can copy a link to a specific calculation.

What CIDR notation actually means

CIDR (Classless Inter-Domain Routing) describes a network by how many leading bits are fixed. /24 means the first 24 of 32 bits are the network, leaving 8 for hosts — 256 addresses, 254 usable. Each extra bit halves the block: /25 = 128, /26 = 64, /27 = 32. It replaced the rigid Class A/B/C system, so you size a network to what you need instead of jumping in huge steps.

The two addresses you never assign to a device are the network address (first, all host bits 0) and the broadcast address (last, all host bits 1) — which is why usable hosts is total minus 2 (except /31 point-to-point links and /32 single hosts).

Private vs. public ranges

Range	CIDR	Use
10.0.0.0 – 10.255.255.255	`10.0.0.0/8`	Private (RFC 1918)
172.16.0.0 – 172.31.255.255	`172.16.0.0/12`	Private (RFC 1918)
192.168.0.0 – 192.168.255.255	`192.168.0.0/16`	Private (RFC 1918)
100.64.0.0 – 100.127.255.255	`100.64.0.0/10`	Carrier-grade NAT
169.254.0.0 – 169.254.255.255	`169.254.0.0/16`	Link-local (APIPA)
127.0.0.0 – 127.255.255.255	`127.0.0.0/8`	Loopback

Home and homelab networks live in the RFC 1918 ranges — most consumer routers default to a 192.168.x.0/24. If you’re segmenting a homelab into VLANs, the split feature above makes carving a /24 into per-VLAN /26s or /27s straightforward.

What this pairs with

Planning the physical side of the network too? The PoE power budget calculator sizes a switch for your APs and cameras, the Wi-Fi 7 homelab guide covers the wireless layer, and the budget networking gear guide rounds up switches and routers worth buying.

Which Local LLM Fits Your GPU in 2026? VRAM Tiers

LK Wood IV — Wed, 17 Jun 2026 00:00:00 -0500

Updated July 3, 2026 · file sizes verified against official Hugging Face model cards and GGUF repo listings.

“What’s the best model I can actually run on my card?” is the most-asked question in local AI, and it resets every time a new GPU or model drops. The answer is almost always decided by one number: VRAM. Get the tier right and a local LLM is fast and private; get it wrong and you’re either offloading to system RAM at a crawl or running a model too small to be useful. Here’s the 2026 map, tier by tier, with real GGUF file sizes and the memory math behind them.

TL;DR · What fits your card at Q4_K_M

8GB (3060 8GB / 4060 / 5060): a 7-8B dense model like Qwen3-8B (5.03GB file). Add 32GB system RAM and a small-active MoE model can offload to RAM and run above its weight.
12GB (3060 12GB / 5070): an 8B with long context, or a 14B at Q4.
16GB (4060 Ti 16GB / 4080 / 5080): a 14B comfortably, plus gpt-oss-20B (built to run in 16GB). A dense 27B spills to RAM here.
24GB (3090 / 4090 / 7900 XTX): the sweet spot. A 27B dense (Gemma-3-27B Q4_K_M is 16.55GB) with context, or a 32B.
48GB+ (2x 24GB / workstation / big unified memory): the only home path to a dense 70B (needs ~45-50GB).

Rule of thumb: total memory = weights (set by quant) + KV cache (grows with context) + compute buffers (~fixed). Default to Q4_K_M and match the model to the tier.

The rule of thumb: weights + KV cache + overhead

Total VRAM for inference breaks into three parts, and it helps to think about all three rather than a single number. The primary llama.cpp discussion on memory estimation lays it out cleanly: model data (the weights, fixed by quantization), a KV cache that grows with how many tokens of context you hold, and compute buffers that are roughly fixed. In its worked example, gpt-oss-20B needs 12.0GB of weights + 2.7GB of compute buffers + roughly 0.2GB of KV cache per 8,192 tokens of context — about 14.9GB at 8k, ~15.5GB at 32k, and ~17.9GB at the full 131,072 tokens — the same model, heavier purely from a longer context window. That KV-cache creep is the single most common reason a model that “fits” on paper still runs out of memory in practice.

For the weights themselves, the shorthand is:

~2 GB per billion parameters at FP16 (full precision).
~0.5 GB per billion at 4-bit, then add headroom for the KV cache and compute buffers on top.

One nuance worth internalizing: Q4_K_M isn’t true 4-bit. It’s mixed precision averaging about 4.83 bits per weight, so real GGUF files run a little larger than the clean 0.5 GB/B estimate — but it’s the everyday default, roughly half the memory of FP16 for a small quality drop. That’s why the tables below quote actual file sizes rather than the estimate. For a given card, fitting a bigger model at Q4_K_M usually beats a smaller one at Q8.

There’s one more concept that reshaped the 2026 tiers: Mixture-of-Experts (MoE). An MoE model activates only a slice of its parameters per token, so it computes like a small model but must still fit like a large one. OpenAI’s gpt-oss-20b card states 21B total parameters with only 3.6B active, natively MXFP4-quantized, and “designed to run within 16GB of memory.” Meta’s Llama 4 Scout card is starker: 17B active but 109B total across 16 experts — so its VRAM footprint is 70B-class despite the tiny active count. The takeaway for fit: MoE needs total params in memory, not active. The escape hatch is that llama.cpp can offload the inactive expert layers to system RAM (--n-cpu-moe), keeping the small active set on a modest GPU.

For an exact figure including your context length, run the numbers through the LLM VRAM Calculator; for how fast it’ll generate, the LLM Speed Calculator.

The tiers (all at Q4_K_M unless noted)

VRAM tier ladder for local LLMs, 2026

Real GGUF file sizes at Q4_K_M · add KV cache + overhead on top

VRAM	Example cards	Comfortable pick	Q4_K_M file size (anchor)
8 GB	RTX 3060 8GB, 4060, 5060	Qwen3-8B (dense)	Qwen3-8B = 5.03 GB
12 GB	RTX 3060 12GB, 5070	8B long-context, or a 14B	Qwen3-8B Q8_0 = 8.71 GB
16 GB	4060 Ti 16GB, 4080, 5080	14B, or gpt-oss-20B (MoE)	gpt-oss-20B ~14.9 GB @ 8k ctx
24 GB	RTX 3090, 4090, 7900 XTX	27B dense, up to a 32B	Gemma-3-27B = 16.55 GB
32 GB	RTX 5090	27-32B at higher quant / long ctx	27B at Q6/Q8 + context
48 GB+	2x 24GB, workstation, unified	Dense 70B	Llama-3.3-70B = 42.52 GB

techfuelhq.com · July 2026 · sizes from bartowski GGUF repo listings

8 GB — entry (RTX 3060 8GB, 4060, 5060)

A 7-8B dense model. Qwen3-8B is a dense 8.2B model per its official card, and the bartowski Qwen3-8B GGUF listing puts Q4_K_M at 5.03 GB; with the KV cache and overhead it lands ~6-7 GB, comfortable at moderate context. This is the fast-8B-chat-and-coding tier.

The change since 2025 is the MoE-offload path. A small-active MoE model (like gpt-oss-20B, 3.6B active) keeps its active layers on the 8GB card and pushes the rest to system RAM via --n-cpu-moe, so with 32GB of system RAM an 8GB card can run models it could never fit whole. It’s slower than pure-GPU, but usable — and it’s the community’s default trick for stretching an 8GB card in 2026.

12 GB — comfortable small (RTX 3060 12GB, 5070)

8B with room for long context, or a 14B at Q4. The extra 4GB over the 8GB tier mostly buys KV-cache headroom: you can hold a much longer context on an 8B, or step up to a dense 14B like Phi-4 (14B, though note its 16K context is short next to the Qwen/Gemma peers). The 3060 12GB is a genuinely good LLM card for its price precisely because capacity, not raw speed, decides what fits here.

16 GB — the mid tier (RTX 4060 Ti 16GB, 4080, 5080)

A 14B comfortably, plus gpt-oss-20B. OpenAI’s gpt-oss-20b is explicitly “designed to run within 16GB of memory” — it’s an MoE with only 3.6B active params, natively MXFP4-quantized, about 14.9GB total at 8k context (rising to ~15.5GB at 32k) per the llama.cpp worked example. Cap the context to stay inside 16GB. A dense 27B does not fit here and spills to system RAM, which collapses throughput, so treat a 16GB card as a strong 14B / MoE-20B machine rather than a 27B one.

24 GB — the sweet spot (RTX 3090, 4090, 7900 XTX)

A 27B dense model, up to a 32B. Gemma-3-27B-it is a dense 27B with a 128K context window per its card, and the bartowski Gemma-3-27B GGUF listing puts Q4_K_M at 16.55 GB, leaving real headroom for KV cache. Mistral-Small-3.2-24B is another dense pick that fits here. This is the best single-card tier for serious local work. What it can’t do comfortably is a dense 70B at Q4 — that needs ~45-50GB.

32 GB — headroom (RTX 5090)

A 27-32B at higher quant (Q5/Q6) or with a long context, and gpt-oss-20B with room to spare. This is the tier where a dense 27B stops spilling under real workloads and you can run it productively without fighting for every megabyte. A dense 70B at Q4 (~45-50GB) still doesn’t fit a single 32GB card — you’d be offloading — but for a comfortable 27B or several smaller models at once, this is plenty.

48 GB+ — the 70B club (2x 24GB, workstation cards, big unified memory)

A dense 70B at Q4_K_M needs roughly 45-50GB. The bartowski Llama-3.3-70B GGUF listing puts Q4_K_M weights at 42.52 GB (marked the recommended default), and KV cache plus overhead push the working total higher. So the paths are: two 24GB GPUs (48GB), a 48GB-or-larger workstation card, or a large unified-memory machine (Apple Silicon or similar) that treats system RAM as model memory and trades raw speed for capacity. The genuinely huge MoE models — DeepSeek-V3.1 at 671B total (37B active) — are data-center territory, useful mainly as the ceiling reference: even at low quant, the total must fit.

The models worth running in 2026

The first-party-confirmed open-weights lineup, by class:

~4B: Qwen3-4B (dense, 4.0B) and Gemma 3 4B — both fit even 4-6GB cards; Qwen3-4B Q4_K_M is 2.50 GB per its GGUF listing.
7-9B: Qwen3-8B (dense, 8.2B) — the 8GB workhorse.
12-14B: Phi-4 (dense, 14B) and Gemma 3 12B.
24-32B: Mistral-Small-3.2-24B and Gemma-3-27B, both dense — the 24GB-tier models.
MoE: gpt-oss-20b (21B total / 3.6B active, runs in 16GB) and Llama 4 Scout (17B active / 109B total).

What changed since 2025 — the freshness moat: the Gemma 3 family ships in 1B/4B/12B/27B with 128K context on the larger sizes, gpt-oss brought a genuinely 16GB-friendly MoE, and Meta’s Llama 4 moved to native MoE. Qwen’s newer generations are live too — the Qwen3.5-27B and Qwen3.6-27B cards are 27B-class multimodal models (image-text-to-text) using a hybrid attention + sparse-MoE architecture, with a 262K native context window — a real KV-cache consideration on top of the weights, and a different fit profile than the plain dense text models above. Beyond that, community users on the low-VRAM tiers increasingly reach for small-active-param MoE models offloaded to RAM as the way to run bigger-feeling models on modest cards; treat the newest community model names as usage signal and verify the exact card before you commit VRAM to it.

A useful pattern holds across all of them: MoE models punch above their size for speed because only a few billion parameters activate per token — but they still occupy their full size in memory, so plan the fit around total params, not active.

Fit is half the question — speed is the other

A model fitting in VRAM doesn’t mean it runs fast. Generation speed is bound by memory bandwidth (each token reads the active weights once), so a big model on a modest card can fit yet feel sluggish, and the same reason is why a dedicated GPU beats CPU or unified memory on throughput even when all three technically “fit” the model. Check both before you commit to a model or a card: the VRAM calculator for fit and the speed calculator for tokens/sec. And if you’re building around a specific card, the single-RTX-5060 local-LLM walkthrough shows the full setup end to end, with real tokens/sec on one card, and the $1,000 local-AI workstation build pairs a parts list to the 16GB tier with the cloud-vs-local cost math. For the bigger picture beyond chat models — image generation, speech, and coding assistants — see the self-hosted AI stack overview.

Bottom line

For most homelab GPUs, the practical pick is simple: an 8B at Q4_K_M on 8-12GB cards (with a small-active MoE offloaded to system RAM when you want more), a 14B-20B on 16GB, and a 27-32B at Q4_K_M on a 24GB card — the single-card sweet spot. Reach for 48GB+ only when a dense 70B is genuinely worth the cost and complexity. Match the model to the VRAM tier, remember that weights + KV cache + overhead all count, default to Q4_K_M, and you’ll get fast, private inference without fighting your hardware.

Sources and methodology

Every model name, size, and file figure above is grounded in the page that carries it — an official model card or a GGUF quant repo file listing — rather than a release announcement or a rehost.

Primary sources cited:

Qwen3-4B card and Qwen3-8B card — dense parameter counts and context windows
Gemma-3-27B-it card — Gemma 3 family sizes (1B/4B/12B/27B) and 128K context
Phi-4 card — dense 14B, 16K context
Mistral-Small-3.2-24B card — dense 24B
gpt-oss-20b card — 21B total / 3.6B active MoE, MXFP4, “runs within 16GB”
Llama 4 Scout card — 17B active / 109B total MoE
DeepSeek-V3.1 card — 671B total / 37B active (ceiling reference)
Qwen3.5-27B and Qwen3.6-27B cards — 2026 27B-class multimodal (image-text-to-text), hybrid attention + sparse MoE, 262K native context
GGUF file-size anchors from the bartowski quant repos: Qwen3-4B (Q4_K_M 2.50GB), Qwen3-8B (Q4_K_M 5.03GB, Q8_0 8.71GB), Gemma-3-27B (Q4_K_M 16.55GB), Qwen3-32B (Q4_K_M 19.76GB), Llama-3.3-70B (Q4_K_M 42.52GB)
llama.cpp memory-estimation discussion — weights + KV cache + compute buffers breakdown; gpt-oss-20B 14.9GB @ 8k (12.0 + 2.7 + ~0.2 KV per 8k tokens) rising to 17.9GB @ 131k context; --n-cpu-moe offload

Email corrections to hello@techfuelhq.com.

Home Assistant Automations: A Practical Guide (2026)

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-16 · ~15 min read · St. Louis County, MO

Home Assistant automations follow a consistent structure: something happens (trigger), check if conditions are met (conditions), then do things (actions). Once you understand that structure, you can write almost any automation. This guide is examples-first — real working YAML for the automations that actually matter.

If you haven’t set up Home Assistant yet, the Home Assistant on Proxmox guide covers the install. For Zigbee/Z-Wave devices, the integration guide covers pairing.

The automation structure

automation:
 - alias: "My Automation Name"
 trigger:
 - platform: <trigger_type>
 # trigger-specific fields
 condition:
 - condition: <condition_type>
 # condition-specific fields
 action:
 - service: <domain.service>
 target:
 entity_id: <entity_id>
 data:
 # service-specific data

Trigger: what initiates the automation (state change, time, zone entry, webhook, etc.) Condition: optional guards — the automation only proceeds if all conditions pass Action: what happens when the trigger fires and conditions pass

Lighting automations

Turn on lights at sunset

automation:
 - alias: "Living Room — Lights On at Sunset"
 trigger:
 - platform: sun
 event: sunset
 offset: "-00:30:00" # 30 minutes before actual sunset
 action:
 - service: light.turn_on
 target:
 entity_id: light.living_room
 data:
 brightness_pct: 60
 color_temp: 400 # warm color temperature (mireds)

The offset field accepts positive or negative durations. -00:30:00 means 30 minutes before the event.

Adaptive lighting: dim at night

automation:
 - alias: "Bedroom — Dim Lights After 10 PM"
 trigger:
 - platform: time
 at: "22:00:00"
 condition:
 - condition: state
 entity_id: light.bedroom
 state: "on"
 action:
 - service: light.turn_on
 target:
 entity_id: light.bedroom
 data:
 brightness_pct: 20
 color_temp: 500 # very warm
 transition: 10 # 10-second transition

The condition here prevents the automation from triggering the bedroom lights if they’re already off — you don’t want the lights turning on at 10 PM just to dim them.

Motion-triggered lights with timeout

automation:
 - alias: "Hallway — Motion Light"
 trigger:
 - platform: state
 entity_id: binary_sensor.hallway_motion
 to: "on"
 action:
 - service: light.turn_on
 target:
 entity_id: light.hallway
 - delay: "00:05:00" # wait 5 minutes
 - condition: state  # only turn off if still no motion
 entity_id: binary_sensor.hallway_motion
 state: "off"
 - service: light.turn_off
 target:
 entity_id: light.hallway

For more reliable motion timeout behavior, use the wait_for_trigger action instead of delay:

action:
 - service: light.turn_on
 target:
 entity_id: light.hallway
 - wait_for_trigger:
 - platform: state
 entity_id: binary_sensor.hallway_motion
 to: "off"
 for: "00:05:00"
 - service: light.turn_off
 target:
 entity_id: light.hallway

wait_for_trigger pauses the action sequence until the trigger fires, then continues. If the motion sensor never clears, the action sequence waits indefinitely (use timeout: to cap it).

Presence-based automations

Welcome home scene

automation:
 - alias: "Welcome Home — Set Living Room Scene"
 trigger:
 - platform: zone
 entity_id: person.lk
 zone: zone.home
 event: enter
 condition:
 - condition: sun
 after: sunset
 before: sunrise
 action:
 - service: scene.turn_on
 target:
 entity_id: scene.living_room_evening
 - service: climate.set_temperature
 target:
 entity_id: climate.main_thermostat
 data:
 temperature: 70

The sun condition ensures the welcome home lighting only triggers after dark. Arriving home at noon doesn’t need the lights on.

Everyone left — eco mode

automation:
 - alias: "All Away — Energy Saving Mode"
 trigger:
 - platform: state
 entity_id:
 - person.lk
 - person.partner  # list multiple people
 to: "not_home"
 condition:
 - condition: state
 entity_id: person.lk
 state: "not_home"
 - condition: state
 entity_id: person.partner
 state: "not_home"
 action:
 - service: climate.set_temperature
 target:
 entity_id: climate.main_thermostat
 data:
 temperature: 65 # setback temperature
 - service: light.turn_off
 target:
 area_id: living_room
 - service: notify.mobile_app_phone
 data:
 message: "Away mode activated."

The trigger fires when any person changes to not_home. The conditions verify that ALL tracked people are away before applying eco mode — so the trigger fires but conditions gate it until the last person leaves.

Notification automations

Dishwasher done

This works with a smart plug that measures wattage (Zigbee or Z-Wave smart outlet):

automation:
 - alias: "Dishwasher — Done Notification"
 trigger:
 - platform: numeric_state
 entity_id: sensor.dishwasher_power
 below: 5 # watts — below this = cycle complete
 for: "00:02:00"
 condition:
 - condition: numeric_state
 entity_id: sensor.dishwasher_power
 above: 0.1 # was actually running (not just idle/off)
 action:
 - service: notify.mobile_app_phone
 data:
 title: "Dishwasher Done"
 message: "Cycle complete."

The for: "00:02:00" on the trigger prevents false positives from mid-cycle power dips — the wattage has to stay below 5W for two minutes before triggering.

Low battery alert

automation:
 - alias: "Low Battery — All Devices"
 trigger:
 - platform: numeric_state
 entity_id:
 - sensor.front_door_lock_battery
 - sensor.bedroom_motion_battery
 - sensor.thermostat_battery
 - sensor.smoke_detector_battery
 below: 20
 action:
 - service: notify.mobile_app_phone
 data:
 title: "Low Battery"
 message: "{{ trigger.to_state.name }} is at {{ trigger.to_state.state }}%"

The template {{ trigger.to_state.name }} and {{ trigger.to_state.state }} pull the entity’s display name and current value from the trigger context — so one automation handles multiple devices and tells you specifically which one is low.

Template-based automations

Door left open warning

automation:
 - alias: "Front Door — Left Open Alert"
 trigger:
 - platform: state
 entity_id: binary_sensor.front_door
 to: "on"
 for: "00:10:00" # open for 10 minutes
 condition:
 - condition: template
 value_template: "{{ states('person.lk') == 'home' }}"
 action:
 - service: notify.mobile_app_phone
 data:
 message: "Front door has been open for 10 minutes."
 - service: tts.speak
 target:
 entity_id: media_player.kitchen_speaker
 data:
 message: "The front door is still open."

The template condition checks that someone is home before sending the alert — no point in notifying if no one is there to close it.

Thermostat override protection

automation:
 - alias: "Thermostat — Override Detection"
 trigger:
 - platform: state
 entity_id: climate.main_thermostat
 attribute: temperature
 condition:
 - condition: template
 value_template: >
 {{ trigger.to_state.attributes.temperature | float > 78 and
 now().hour >= 1 and now().hour < 6 }}
 action:
 - service: climate.set_temperature
 target:
 entity_id: climate.main_thermostat
 data:
 temperature: 70
 - service: notify.mobile_app_phone
 data:
 message: "Thermostat was set above 78°F at night — reset to 70°F."

Choose blocks: conditional action branching

When you need the automation to do different things based on a condition, use choose:

automation:
 - alias: "Motion — Lighting by Time of Day"
 trigger:
 - platform: state
 entity_id: binary_sensor.living_room_motion
 to: "on"
 action:
 - choose:
 - conditions:
 - condition: time
 after: "06:00:00"
 before: "20:00:00"
 sequence:
 - service: light.turn_on
 target:
 entity_id: light.living_room
 data:
 brightness_pct: 90
 color_temp: 250 # cooler, daytime
 - conditions:
 - condition: time
 after: "20:00:00"
 before: "23:00:00"
 sequence:
 - service: light.turn_on
 target:
 entity_id: light.living_room
 data:
 brightness_pct: 40
 color_temp: 500 # warm, evening
 default:
 - service: light.turn_on
 target:
 entity_id: light.living_room
 data:
 brightness_pct: 10
 color_temp: 600 # very warm, late night

Scripts: reusable action sequences

Put repeated action sequences in scripts:

# configuration.yaml
script:
 good_morning:
 alias: "Good Morning Routine"
 sequence:
 - service: light.turn_on
 target:
 area_id: bedroom
 data:
 brightness_pct: 30
 color_temp: 200 # cool/bright
 transition: 120 # 2-minute sunrise
 - service: climate.set_temperature
 target:
 entity_id: climate.main_thermostat
 data:
 temperature: 70
 - delay: "00:02:00"
 - service: light.turn_on
 target:
 entity_id: light.kitchen
 data:
 brightness_pct: 80

Call this script from any automation or button press:

action:
 - service: script.good_morning

Debugging automations

Trace view: Settings → Automations → open automation → Traces. Shows every firing with the trigger value, each condition result (pass/fail with values), and each action outcome.

Template testing: Developer Tools → Template. Paste any Jinja2 expression and see it evaluate against current state in real time. Use this to test conditions before putting them in an automation.

Entity history: Developer Tools → States. See the current value and last-changed time for any entity. Useful when an automation isn’t triggering — check if the entity state is actually what you think it is.

Logbook: Settings → Logbook. Shows state changes and automation fires in chronological order. Filter by entity to see exactly when something changed.

Best practices

Use for: on state triggers to avoid automations firing on momentary state changes (a sensor flickering, a button double-press).

Avoid complex logic in a single automation — break it into an automation that calls a script, with multiple scripts for different conditions. Simpler automations are easier to debug.

Version control your config — store your configuration.yaml and automation files in a Gitea repository. The Docker Compose starter stack includes Gitea for exactly this.

Use areas and labels — Home Assistant’s area grouping lets you target all lights in a room without listing entity IDs. area_id: living_room in a target covers everything in that area, including devices added later.

This guide extends the setup work from the Home Assistant on Proxmox guide and the Zigbee/Z-Wave integration guide. The automations here assume your devices are already paired and showing correct state in HA.

Sources

Home Assistant: Automating Home Assistant – official overview of the trigger/condition/action automation model.
Home Assistant: Automation triggers – official reference for state, time, sun, zone, and numeric_state triggers.
Home Assistant: Conditions – official reference for state, numeric_state, template, time, and sun conditions.
Home Assistant: Script syntax – official reference for action sequences, choose blocks, delay, and wait_for_trigger.
Home Assistant: Templating – official reference for the Jinja2 templates used in value_template and action data.

LLM VRAM Calculator

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

Pick your GPU, the model size you want to run, a quantization level, and a context length. The calculator estimates total VRAM as three parts: the model weights, the KV cache that holds your context, and a small runtime overhead. Here is how to read those numbers.

Weights are the big, predictable cost. A model’s weight memory is just its parameter count times the bits-per-weight of the quantization, divided by eight. An 8B model at FP16 is about 16 GB; the same model at Q4_K_M is about 4.8 GB. This is why quantization is the first lever to reach for when a model does not fit.

The KV cache scales with context, not parameters. Every token in your context window is cached per layer, so a long context can quietly cost more memory than the weights on a small model. The tool estimates the cache from the attention shape of modern GQA models and lets you quantize it (Q8 or Q4) to claw back room.

Headroom matters. The verdict bands leave a margin: a model that needs 92 percent of your VRAM is marked tight, not safe, because runtimes, the desktop, and transient spikes all want a slice. Size for the green band and you avoid out-of-memory errors mid-generation.

These are planning estimates that assume a llama.cpp / GGUF-style setup. Your exact numbers depend on the specific model, the runtime, and how much you batch.

MikroTik CRS305 Review 2026: The $80 10GbE Homelab Switch

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-16 · ~9 min read · St. Louis County, MO

Rating: 4.5 / 5

The CRS305 is the switch that comes up in every homelab 10GbE conversation, consistently, because nothing else at its price point makes as much sense. Four SFP+ ports, one 1GbE copper management port, a MikroTik-documented idle draw of 6.5–7.1W, and an $80–100 street price with no software subscription fees. That’s the case for it.

The case against: RouterOS has a learning curve that surprises people coming from consumer switches, and the web interface looks like it was designed in 2009 (it was). These are real considerations, not negligible footnotes.

Still deciding whether 10GbE is even worth it over 2.5GbE for your homelab? Start with 2.5GbE vs 10GbE: which to buy — this review assumes you’ve already landed on 10GbE.

Here’s the full picture.

What you’re actually buying

Hardware:

4× SFP+ ports at 1/2.5/10 Gbps
1× RJ45 Gigabit Ethernet (management)
Desktop/rack mount (no ears included, MikroTik sells a bracket kit)
External 24V passive PoE power supply (included)
No fan — passively cooled chassis

Firmware options:

RouterOS 7 (default): full networking OS with Winbox GUI, CLI, web interface
SwOS: simplified switch-mode firmware, browser-only, for pure Layer 2 operation

Published specs (MikroTik product page, accessed 2026-06):

Max power consumption: 9.1W
Idle power: 6.5–7.1W (measured by third parties; MikroTik doesn’t publish idle separately)
Dimensions: 113 × 89 × 28 mm (fits on a shelf, not just in a rack)
Operating temperature: 0–55°C

Who this switch is for

The CRS305 makes sense if:

You have 2-4 machines that need 10GbE connectivity. The sweet spot: two mini PCs + a NAS. Three SFP+ ports cover all three devices, the fourth port goes to your router or another switch for uplink.
Your runs are under 5 meters. Passive DAC cables (SFP+ Direct Attach Copper) work perfectly at this distance, cost $15–20 each, draw less than 0.5W, and have zero transceiver compatibility issues on the CRS305.
You care about power consumption. 7W total for a 10GbE switch is exceptional. The QNap QSW-308S (8× SFP+) pulls 20–25W. The Ubiquiti USW-Pro-Max 16 (16-port 10GbE) pulls 30–40W. The CRS305 is the most efficient 10GbE switch option in 2026 at its port count.
You don’t need PoE on the 10G ports. SFP+ ports don’t do PoE. If you need PoE (for APs, cameras, phones), you need a separate switch — the CRS305 is pure data.

Setup path: SwOS for most homelab users

When the switch arrives, it runs RouterOS. For a pure homelab switch (no routing), SwOS is the better choice — it’s a simpler web UI that does exactly what you need.

Switch to SwOS:

Connect a laptop to the 1GbE management port via RJ45
Set your laptop’s IP to 192.168.88.2 /24 (the CRS305 defaults to 192.168.88.1)
Navigate to 192.168.88.1 in a browser → log in with admin/no-password
Go to System → RouterBOOT → Boot OS → select SwOS → Apply → reboot

After reboot, access 192.168.88.1 in a browser — you’re now in SwOS. The interface shows all ports and lets you configure VLANs, aggregation, and mirror ports from a single page.

VLAN setup in SwOS — for a typical homelab with separate IoT and trusted VLANs:

In SwOS → VLANs tab: add VLAN IDs (e.g., 10 for trusted, 20 for IoT, 99 for management)
For each port: set VLAN mode (access or trunk), tagged VLANs (for trunk ports to router/Proxmox), and default VLAN ID (for access ports)
Port 5 (the 1GbE copper port) becomes the management interface

Full VLAN config walkthrough is in the VLANs for the Homelab guide.

The RouterOS path: more power, more complexity

If you want the CRS305 to handle routing alongside switching — running DHCP for your LAN, NAT, or acting as a firewall — RouterOS is appropriate. RouterOS on the CRS305 supports:

Full L3 routing between subnets
Firewall rules (stateful, connection tracking)
DHCP server with static leases
OSPF and BGP (yes, on this $80 switch)
Traffic shaping and queuing

The Winbox desktop application (Windows/Mac/Linux via Wine) is the most ergonomic way to configure RouterOS — it connects directly over Layer 2 MAC address, so you can configure the switch even if you mess up the IP settings. The web interface is functional but slow. The CLI via SSH is identical to Cisco-style IOS if you’re used to that workflow.

Realistic use case for RouterOS: a 2-node homelab where the CRS305 handles both 10GbE switching between nodes and routes traffic from a DSL/cable modem to the nodes without a separate router box. Not a configuration I’d recommend for complex VLANs or firewall rules — OPNsense on a mini PC handles that better — but it works for minimal setups.

Power draw in practice

The published 9.1W max and community-measured 6.5–7.1W idle figures hold up. In a typical homelab setup with two DAC-connected nodes active:

Idle (switch powered, no traffic): 6.5–7W
Active traffic (NAS backup, file transfers): 7–8W
Max under sustained load: ~8.5W (consistent with the published 9.1W ceiling)

At $0.13/kWh running 24/7, the CRS305 adds ~$8/year to your electricity bill. It’s not a consideration. Compare to a used Cisco SG350-28 at 35–50W for a 28-port managed switch — the Cisco costs $35–50/year in electricity for a homelab with 8 active ports.

What the CRS305 doesn’t do well

Port count. Four SFP+ ports means four 10GbE connections plus the 1GbE management. If you need 6+ 10GbE devices, you’re looking at the CRS309-1G-8S+ (8× SFP+, ~$180) or the CRS312-4C+8XG (mixed copper + SFP+, ~$280).

PoE. None. The SFP+ standard doesn’t carry DC power. If your homelab includes Unifi APs, IP cameras, or VoIP phones that need PoE, add a dedicated PoE switch for those devices — a $35 TP-Link TL-SG108PE handles 8 PoE devices at up to 64W total PoE budget.

RouterOS UI. If you’ve never used MikroTik equipment, RouterOS feels like it predates every modern network management interface. The Winbox application has been the primary configuration tool for 20 years and it shows. Winbox works, it’s stable, and the MikroTik documentation is comprehensive — but expect 30–60 minutes of learning before a typical VLAN configuration feels natural.

No SFP (1GbE SFP) ports. The CRS305’s four ports are SFP+ only. You can plug standard 1GbE SFP modules into SFP+ ports — they negotiate down — but the module costs money and uses a 10GbE slot. The CRS305 is optimized for 10GbE devices.

Price and where to buy

Street price: $80–100 USD as of mid-2026. Check MikroTik’s authorized distributor page for the nearest warehouse-stocked source — resellers in the US include Baltic Networks, Streakwave, and Winncom. Amazon carries it but usually at $95–110 and sold through third parties.

There’s no used market pricing consideration with MikroTik the way there is with Cisco — MikroTik hardware holds value because there’s no licensing distinction between new and used units (RouterOS is perpetually licensed to the hardware, not an account).

Verdict

The CRS305-1G-4S+IN is the correct answer for most homelab 10GbE setups in 2026. The four SFP+ ports cover the typical 2–3 node + NAS topology, the passive cooling and 7W idle make it the most power-efficient 10GbE option at its port count, and the open SFP+ standard means no vendor module lock-in.

RouterOS has a learning curve, but it’s a one-time investment — once you’ve configured your VLAN and port setup, you set it and forget it. The CRS305 doesn’t need firmware updates more than a couple of times per year, and MikroTik’s release cadence is methodical rather than aggressive.

Buy it. If you outgrow four SFP+ ports, the CRS309 is the natural upgrade.

For the full 10GbE homelab setup — NIC selection, DAC vs. fiber, and three budget tiers — see the 10GbE Homelab Networking guide. For VLAN configuration on this switch (and integration with OPNsense + Proxmox), the VLANs for the Homelab guide has exact commands for MikroTik SwOS. The Homelab Networking Gear Under $200 roundup puts this switch in context alongside routers and wireless APs.

Network Transfer Time Calculator

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

Enter how much data you’re moving, the connection, and the drives at each end. The calculator gives you the realistic transfer time, not the marketing one. Here’s the logic behind it.

Effective speed is the slower of the link and the disk, minus overhead. A transfer can only go as fast as its slowest part. If your 10GbE link can carry 1,250 MB/s but the source is a single hard drive that reads at 180 MB/s, you move data at 180 MB/s. The tool takes the lower of the two, then trims it by a real-world efficiency factor for protocol overhead.

The bottleneck readout is the useful part. It tells you whether spending money on faster networking would actually help. If the drive is the limit, a 10GbE card changes nothing until you add disks or switch to SSDs. If the link is the limit, faster networking pays off directly.

Time is just size divided by speed. Once the effective speed is set, the math is exact: a 1 TB file at 280 MB/s takes about an hour. The per-link table shows the same transfer across every common Ethernet speed so you can see where the gains flatten out for your storage.

Sizes use decimal units (1 TB = 1,000 GB) to match how both drives and network speeds are quoted.

Proxmox Cluster Setup: 2-Node and 3-Node HA (2026)

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-16 · ~18 min read · St. Louis County, MO

A single Proxmox node is fine until it isn’t. The drive fails. The NIC dies. You need to reboot for a kernel update and everything goes down. A Proxmox cluster solves this — two or more nodes that share cluster state, can migrate VMs between them, and optionally restart VMs automatically when a node fails.

This guide covers building a cluster from scratch: the correct 2-node architecture with a QDevice, the cleaner 3-node architecture that doesn’t need one, shared storage options, live migration, HA groups, and the fencing question you can’t skip.

What a Proxmox cluster actually gives you

Proxmox clustering has two distinct features that people sometimes conflate:

1. Cluster management (no shared storage required)

Unified web UI: manage all nodes from one panel
Centralized user and permission management
Pool-based resource allocation across nodes
Live migration between nodes (with shared storage)

2. High Availability (HA) — requires shared storage + fencing

Automatic VM restart on surviving node when a node fails
HA watchdog groups with priority ordering
Fencing to prevent split-brain and data corruption

You can run a cluster for live migration and unified management without HA. HA is the more complex addition and has specific hardware requirements (shared storage, fencing).

Architecture: 2-node vs 3-node

3-node cluster (recommended)

Three nodes each have a vote in corosync. Quorum is 2 votes (majority). If any single node fails:

2 surviving nodes form quorum
Cluster continues operating
HA restarts VMs on surviving nodes

This is the clean architecture. No workarounds, no QDevice, straightforward HA.

2-node cluster with QDevice

Two nodes cannot hold quorum on their own — each losing the other would leave one node alone, and one vote does not equal majority of two. The solution is a QDevice: a third machine running corosync-qdevice that provides a tie-breaking vote.

Node 1 (vote) + Node 2 (vote) + QDevice (vote) = 3 votes total
Quorum = 2 votes required

If Node 1 fails: Node 2 + QDevice = 2 votes → quorum → cluster continues. If the QDevice fails: Node 1 + Node 2 = 2 votes → quorum maintained (QDevice is just a tiebreaker). If Node 1 + QDevice both fail: Node 2 alone = 1 vote → no quorum → node fences itself.

The QDevice can be anything running Debian/Ubuntu with a network connection — a Raspberry Pi, an LXC on a third server, even a VM on a NAS. It requires minimal resources: 256MB RAM, a few hundred MB of disk, and a stable network connection to both nodes.

Prerequisites

For a 2-node + QDevice cluster:

2 Proxmox hosts (any hardware, same or different specs)
1 QDevice host (Raspberry Pi, mini PC, or any Debian/Ubuntu system)
All three on the same network (or VLANs with routing between them)
No existing Proxmox clusters on any node — clusters can only be created, not merged

For HA (optional, beyond basic clustering):

Shared storage accessible from all nodes (NFS, iSCSI, or Ceph)
Fencing mechanism (IPMI, BMC, or kernel watchdog)

Step 1: Create the cluster on node 1

Log into node 1’s Proxmox web UI or SSH in:

# Create the cluster (run on node 1 only)
pvecm create mycluster --link0 <node1-ip>

Verify the cluster is created:

pvecm status
# Should show: Quorum information, Node ID 1, Member count 1

Step 2: Join node 2 to the cluster

From node 2, join the existing cluster:

# Run on node 2
pvecm add <node1-ip> --link0 <node2-ip>

This prompts for node 1’s root password. After joining, verify from node 1:

pvecm nodes
# Should show both nodes listed

At this point, both nodes appear in the web UI under Datacenter. The cluster exists but has no quorum capability — with 2 nodes and 2 votes needed for quorum, losing either node means no quorum.

Step 3: Set up the QDevice

On the QDevice machine (Debian/Ubuntu):

apt update && apt install -y corosync-qdevice

On node 1, configure the QDevice:

pvecm qdevice setup <qdevice-ip>

This copies the cluster SSH key to the QDevice and configures corosync on all nodes to include the QDevice vote. Verify:

pvecm status
# Quorate: Yes
# Total votes: 3 (node1 + node2 + qdevice)
# Expected votes: 2 (quorum threshold)

Step 4: Configure shared storage (required for live migration and HA)

NFS (easiest for homelab)

If you have a TrueNAS or any NFS server:

In Proxmox web UI: Datacenter → Storage → Add → NFS

Setting	Value
ID	`nfs-shared`
Server	`192.168.1.x` (NFS server IP)
Export	`/mnt/pool/proxmox` (your NFS export path)
Content	`Disk image, CT template, ISO image, VZDump backup file`
Nodes	All (select all cluster nodes)

After adding, both nodes should see the same NFS storage in their storage list.

Verify from both nodes:

# On both node1 and node2
ls /mnt/pve/nfs-shared/
# Both should show the same directory contents

iSCSI

For better performance than NFS, an iSCSI target (TrueNAS, OpenMediaVault, or a dedicated SAN):

# Discover iSCSI targets
iscsiadm -m discovery -t st -p <iscsi-server-ip>

# Log in to target
iscsiadm -m node -T <target-name> -p <iscsi-server-ip> --login

Add in Proxmox UI: Datacenter → Storage → Add → iSCSI. Wrap it in LVM-thin for thin-provisioned VM disks.

Ceph (advanced, distributed storage)

Ceph runs on the Proxmox nodes themselves — each node contributes disks to a distributed object store. No separate NAS required.

Ceph requires:

3+ Proxmox nodes (Ceph needs an odd number of OSDs for quorum)
A dedicated disk per node for Ceph OSD (separate from the OS disk)
Low-latency network between nodes (10GbE strongly recommended)

Set up via Proxmox web UI: Datacenter → Ceph → Install → follow wizard. Ceph is powerful but adds complexity; for a 2-node homelab, NFS is simpler.

Step 5: Live migration

With shared storage, you can migrate running VMs between nodes. In the web UI:

Select a VM
Right-click → Migrate
Target node: select the other node
Check “Online” for zero-downtime live migration (requires VM disk on shared storage)
Click Migrate

From the CLI:

# Live migrate VM ID 100 to node2
qm migrate 100 node2 --online

Migration over 10GbE takes 10–30 seconds for a typical VM. On 1GbE with a large-memory VM, plan for several minutes.

Step 6: Enable High Availability

HA requires fencing configured before enabling. Without fencing, HA is dangerous — if a node becomes unreachable (not actually down), the surviving node might try to restart VMs while the original node is still running them, potentially causing data corruption on shared storage.

Fencing option 1: IPMI/iLO/iDRAC (recommended for production)

If your servers have IPMI (most enterprise/workstation boards):

Datacenter → HA → Groups → Resources → Fencing:

# /etc/pve/ha/resources.cfg example:
vm: 100
 group: ha-group
 max_restart: 3
 max_relocate: 3

IPMI fencing configuration: Datacenter → HA → Fencing → Add IPMI fence agent with IP, username, password for each node’s IPMI interface.

Fencing option 2: Kernel watchdog (homelab without IPMI)

The Linux kernel watchdog causes a node to self-reboot if it loses cluster communication. It’s not hardware fencing, but it prevents split-brain.

# On each Proxmox node:
echo "softdog" >> /etc/modules
modprobe softdog

# Verify
ls /dev/watchdog

Configure in /etc/pve/ha/resources.cfg:

watchdog-mux: yes

Enable HA for a VM

Once fencing is configured:

Web UI → Select VM → More → Manage HA
Click “Add HA”
Set Group (optional: assign to a specific HA group)
Max Restart: 3 (restart attempts before abandoning)
Max Relocate: 3 (move attempts to another node)

Or CLI:

ha-manager add vm:100 --state started --max_restart 3 --max_relocate 3

Check HA status:

ha-manager status
# Shows: vm:100 in state started, node: node1

When node1 fails, HA manager on node2 detects the node timeout, confirms fencing (node has powered off or watchdog-rebooted), and starts VM 100 on node2.

Step 7: HA groups and priorities

HA groups let you prefer specific VMs on specific nodes while allowing failover to others:

# Create a group that prefers node1 but allows node2
ha-manager groupadd ha-group1 --nodes node1:2,node2:1 --restricted 0
# node1:2 = priority 2 (preferred), node2:1 = priority 1 (failover)
# restricted 0 = allow running on any listed node

Assign VMs to the group:

ha-manager set vm:100 --group ha-group1

With this config, VM 100 will preferably run on node1. If node1 fails, it migrates to node2. When node1 comes back, it migrates back (if --nofailback 0, the default).

Monitoring cluster health

# Overall cluster status
pvecm status

# Node status 
pvecm nodes

# HA manager status
ha-manager status

# Corosync ring status (network health between nodes)
corosync-cfgtool -s

# Check for quorum issues
corosync-quorumtool

In the web UI: Datacenter → Summary shows all nodes with CPU/RAM/disk graphs and cluster status.

Common issues

“Cluster not quorate” — Usually means the QDevice is unreachable or a node went offline without fencing. Check corosync-cfgtool -s for ring status. Confirm QDevice is running systemctl status corosync-qdevice.

Live migration fails with “node already contains this VM” — The VM disk is on local storage, not shared storage. Move the disk to shared storage first: VM → Hardware → Disk → Move Disk → Target shared storage.

HA manager won’t start VMs — Check ha-manager status for fencing errors. If fencing isn’t configured correctly, HA manager refuses to start VMs on surviving nodes (correct behavior — without fencing, it can’t safely assume the failed node is truly offline).

Corosync ring 0 errors — Network instability between nodes. Check physical connectivity, switch port speed (ensure both nodes are at full duplex), and that the corosync network isn’t saturated. Corosync is very sensitive to dropped packets.

Network recommendations

Dedicate a network interface or VLAN for corosync (--link0 parameter)
VM traffic on a separate interface or VLAN from cluster communication
10GbE between nodes for live migration (1GbE works but migration is slow)
Storage traffic on a third interface if possible

The VLANs for the homelab guide covers network segmentation for cluster + storage + VM traffic with OPNsense and managed switches.

Cluster storage architecture connects to ZFS. The ZFS on Proxmox guide covers local storage pool creation; for cluster scenarios, set up local ZFS before joining nodes to the cluster. For backup strategy across a cluster, the Proxmox Backup Server guide covers PBS with cluster-aware storage repos.

Sources

Proxmox VE Cluster Manager – official wiki for pvecm, corosync, quorum, and QDevice setup.
Proxmox VE High Availability – official docs for ha-manager, groups, fencing, and the watchdog.
Proxmox VE Storage – official reference for NFS, iSCSI, and other shared storage used by HA and live migration.
Deploy Hyper-Converged Ceph Cluster – official wiki for the Ceph distributed storage option run on cluster nodes.

Wi-Fi 7 for the Homelab and Home Network in 2026: Is It Worth It?

LK Wood IV — Tue, 16 Jun 2026 00:00:00 -0500

Every Wi-Fi 7 router box prints a number that no device on your network will ever hit. The marketing says 46 Gbps. Your laptop will see a few. That gap is the whole story of whether Wi-Fi 7 is worth it in 2026, and the honest answer depends almost entirely on what you actually run.

For a homelab the wireless generation barely matters, because the gear you care about is wired. For a busy house with multi-gig internet and a stack of latency-sensitive clients, the new standard earns its price for one feature that has nothing to do with the headline speed. Here is where each case lands.

What Wi-Fi 7 (802.11be) actually is, and when it shipped

The “Extremely High Throughput” standard and the January 2024 launch

Wi-Fi 7 is the IEEE 802.11be standard, branded Extremely High Throughput (EHT). The Wi-Fi Alliance launched its Wi-Fi CERTIFIED 7 interoperability program on January 8, 2024 in Austin, Texas. That date is when the ecosystem got a stamp that one vendor’s Wi-Fi 7 router and another vendor’s Wi-Fi 7 client are supposed to talk to each other correctly. The Alliance projected 233 million Wi-Fi 7 devices shipping in 2024, growing to 2.1 billion by 2028, so this is the generation most new phones, laptops, and routers ship with now whether or not you went looking for it.

The three real upgrades: 320 MHz channels, 4K-QAM, and Multi-Link Operation

There are three headline features over Wi-Fi 6E, and they are worth understanding because two of them are conditional and one of them is the reason to buy in.

320 MHz channels — double Wi-Fi 6E’s 160 MHz, but available only where regulators have opened the 6 GHz band. This is where the big peak numbers come from, and it only exists at 6 GHz.
4K-QAM (4096-QAM) — a denser modulation that achieves 20% higher transmission rates than the 1024-QAM used in Wi-Fi 6. It needs a clean, strong signal to hold, so it helps most close to the access point.
Multi-Link Operation (MLO) — simultaneous transmit and receive over multiple links. This is the feature that actually changes how the network feels, and I will come back to it.

Per the Wi-Fi Alliance, 320 MHz channels raise the peak modulation-coding-scheme data rate from 2.409 Gbps in Wi-Fi 6 to 5.7648 Gbps for a two-spatial-stream (2x2) device. Hold onto that 5.76 Gbps number — it is the honest ceiling for a normal client.

Marketing peak numbers vs real-world throughput

Where the 46 Gbps headline comes from

Wi-Fi 7’s theoretical maximum data rate is about 46 Gbps, versus roughly 9.6 Gbps for Wi-Fi 6/6E. That figure assumes a high-end multi-antenna access point running every band at once under ideal conditions. It describes the whole AP’s aggregate capacity, not what a single client pulls down. No phone, no laptop, no anything you own gets near it. It is the headline on the box and nothing more.

The honest 2x2-client ceiling and the 6 GHz requirement

A realistic 2x2 client device supporting 320 MHz channels, 4096-QAM, and MLO has a theoretical maximum of 5.76 Gbps — far below the 46 Gbps quoted for whole-AP capacity. And even that requires the 320 MHz channels that exist only in the 6 GHz band. On 2.4 GHz and 5 GHz the headline throughput is simply unachievable, and most client devices will not see the theoretical figures regardless. If a client lacks 6 GHz, or sits in a region where wide 6 GHz channels are not available, the top rates are off the table before you start.

What field trials and benchmarks actually measured

The real numbers are good, just not magic. An earlier Wireless Broadband Alliance residential Wi-Fi 7 field trial measured real-world throughput consistently above 3.5 Gbps — well below theoretical peaks but a strong result for wireless. Independent benchmarking lines up with that: Wi-Fi 7 sustained over 1 Gbps up to 40 feet from the AP in the 6 GHz band, hit up to about 3.7 Gbps downlink at close range with a 320 MHz channel, and held 2+ Gbps across the same floor as the AP.

So the mental model is: a few hundred MB/s to roughly 450 MB/s at close range under good conditions, dropping to gigabit-class at distance. That is a real upgrade over a high-speed Wi-Fi 6 router, which typically maxes practical throughput around 1 Gbps. It is not a 46 Gbps anything.

Multi-Link Operation: the feature that matters most

How MLO aggregates bands and cuts latency

MLO lets one client and AP establish multiple band links — for example 5 GHz plus 6 GHz — simultaneously under a single association. Instead of being stuck on one band at a time and re-associating when conditions change, the connection aggregates throughput across links and, more usefully, routes traffic over whichever link is cleaner at that instant. That is what lowers latency and smooths out jitter.

Field-trial latency numbers and what “wired-like” means

This is where the recent data is genuinely interesting. In the Wireless Broadband Alliance / CableLabs / Intel Phase 2 residential field trial, completed February 26, 2026 in a 4,500 sq ft home, Wi-Fi 7 MLO doubled throughput under interference and cut application-layer latency by 35-48%, with up to a 40% reduction in MAC-layer jitter — delivering wired-like determinism.

For a competitive gamer or anyone living on video calls, that consistency matters more than a higher peak download number ever will. A connection that holds steady under interference is the upgrade you feel; a bigger ceiling you never reach is the one you only read about. If your edge router is the bottleneck for that traffic, the homelab firewall and router stack comparison covers where routing and WireGuard throughput actually cap out.

Does Wi-Fi 7 help a homelab? Mostly no, with caveats

Servers and NAS are wired — the wireless gen rarely touches them

Here is the part vendors will not put on the box: for a homelab, the priority is a strong wired Ethernet backbone, because servers and NAS boxes are wired. Your Proxmox host, your TrueNAS box, your hypervisor cluster — none of them talk over Wi-Fi, and the traffic you care about most never touches the wireless radio. Spending on the wireless generation to speed up a homelab is solving the wrong problem.

The money is better spent on the wired side. 2.5GbE is widely viewed as the 2026 sweet spot, while 10GbE is justified mainly for editing 4K off a NAS, large simultaneous backups, moving terabytes, or VM storage over the network. I broke that tradeoff down in detail in 2.5GbE vs 10GbE for the homelab, and the short version holds here: moving to 10GbE means upgrading every device in the chain, a 10GbE switch can cost roughly three times a gigabit switch with the same port count, and NAS performance is often capped by mechanical hard drives long before 10GbE is saturated. None of that changes because a new Wi-Fi standard exists.

Where Wi-Fi 7 does help the homelab

The caveat is real, though. Wi-Fi 7 helps your homelab at the edge: the laptop you administer from, the phone running dashboards, roaming clients that move around the house, and dense IoT environments where a lot of small devices contend for airtime. If you back up a laptop to the NAS over wireless, or pull large files to a tablet, the higher ceiling and MLO consistency show up there. Just keep it in proportion — that is the client experience, not the core of the lab.

The wired backhaul reality: 2.5GbE vs 10GbE

Why a Wi-Fi 7 router needs multi-gig ports to mean anything

A Wi-Fi 7 client can exceed 2 Gbps. If the router it connects to has only gigabit Ethernet ports, that router is a fast engine on a narrow straw — the wired uplink and any wired devices are bottlenecked back down to a single gigabit. This is why Wi-Fi 7 routers commonly include multi-gig Ethernet (2.5G, 5G, or 10G) on WAN and LAN. Without a multi-gig backbone, the wireless ceiling is academic. Look for at least a 2.5GbE WAN/LAN port; flagships add 10GbE.

Mesh backhaul: the 1GbE trap

Mesh is where this bites hardest. Most mesh nodes still use only 1GbE wired backhaul, which caps wired-backhauled throughput to gigabit. A Wi-Fi 7 mesh cannot show its full capability without 2.5GbE-or-faster backhaul, and wiring at least one node back to the gateway materially improves mesh performance. If you are buying a Wi-Fi 7 mesh kit and running it on gigabit backhaul, you paid for a ceiling you capped yourself.

2.5GbE as the 2026 sweet spot vs the cost of going 10GbE

For most homes and homelabs, 2.5GbE is the right backbone in 2026: it runs on existing cabling, it is cheap, and it clears the gigabit bottleneck that makes Wi-Fi 7 pointless. 10GbE is the answer only for the specific NAS and VM workloads above. If you want concrete gear picks, the best homelab networking gear under $200 and the budget 10GbE home networking guide both cover switches and NICs that pair with a Wi-Fi 7 router without overspending.

Client-support and availability reality in 2026

Chipsets you’ll actually encounter

The client chip decides what you actually get. In smartphones, Qualcomm’s FastConnect 7800 is the widely used Wi-Fi 7 client chip in flagship phones. Intel dominates Wi-Fi 7 laptop modules — the BE200, BE201, and BE202 — and Broadcom powers most high-end routers. Intel’s BE200 (Gale Peak 2) is the common one you will find in a laptop or as an add-in card: it supports MLO, 4096-QAM, and 320 MHz channels, with 6 GHz at 320 MHz rated at 5800 Mbps and a maximum PHY rate up to 8774 Mbps.

The AMD-platform and 320 MHz gotchas

Two traps worth knowing before you buy a card. First, many BE200 cards are limited to Intel CPU platforms and do not support AMD — if you are putting one in an AMD desktop or laptop, check compatibility first, because plenty of people have bought one and found it would not initialize. Second, the top speeds require 320 MHz channels, which exist only in the 6 GHz band; only three 320 MHz channels fit in the US 6 GHz band, and US 6 GHz operation has to coexist with tens of thousands of incumbent licensed users between 5.925 and 7.125 GHz. The practical effect is that 320 MHz is a best-case, close-range, clean-spectrum scenario, not a guarantee.

Should you upgrade, or stay on Wi-Fi 6 / 6E?

This is the decision section. Sort yourself into one of these and the answer falls out. One thing to rule out first: if your complaint is a connection that keeps dropping rather than one that is merely slow, no router generation fixes that — work through Wi-Fi that keeps disconnecting before you spend anything.

Stay on Wi-Fi 6/6E if:

You have gigabit-or-slower internet. Even high-speed Wi-Fi 6 routers typically max practical throughput around 1 Gbps, and your plan is the limit, not your radio.
Your core is all-wired — servers, NAS, desktop on Ethernet.
You have no 6 GHz clients. Without 6 GHz, the marquee Wi-Fi 7 features do not apply, and the practical gain is small.

Upgrade to Wi-Fi 7 if:

You have multi-gig internet. ISPs increasingly offer multi-gig plans — AT&T and Frontier at 5 Gbps, Ziply Fiber at 10 Gbps — and that is exactly where Wi-Fi 7’s higher ceiling becomes useful.
You have a busy, dense client environment — a household full of phones, laptops, TVs, and IoT all contending at once.
You are latency-sensitive: competitive gaming, heavy video conferencing, anything where consistent latency beats peak download speed.

Wi-Fi 7 is most worth it for multi-gig internet, busy households, gamers, and work-from-home users who value consistent latency — the same households, incidentally, most likely to run into a monthly data cap, which the data usage calculator will size for you. On a standard gigabit-or-slower plan, the gains are mainly better multi-device handling and lower latency rather than dramatically faster top speed — and that may still be enough reason on its own, just go in knowing that is what you are buying.

Pricing snapshot for 2026

Wi-Fi 7 router pricing in 2026 spans a wide range, and the right tier depends on whether you need 6 GHz and multi-gig ports at all.

Tier	Price	Notes
Entry dual-band	Under $100	e.g. TP-Link Archer BE3600 — omits 6 GHz, so no 320 MHz
Mid-range tri-band	~$200–$350	The sweet spot: 6 GHz, MLO, usually multi-gig ports
Traditional flagship	~$500–$600	e.g. Archer BE800 (~$599) with dual 10GbE
Wi-Fi 7 mesh kit	~$1,000–$1,800	e.g. eero Max 7, Orbi 970

The entry tier is the trap. A sub-$100 dual-band Wi-Fi 7 router that omits 6 GHz cannot do 320 MHz channels, so you are paying for the label without the feature that justifies it. If you are going to buy in, the mid-range tri-band tier around $200–$350 is where the actual Wi-Fi 7 experience starts, and it usually includes the 2.5GbE port you need for it to matter. The mesh kits only make sense if you also wire the backhaul.

Bottom line: who Wi-Fi 7 is genuinely for in 2026

For a homelab, Wi-Fi 7 is not a priority — put that money into a 2.5GbE wired backbone and a router that can route. For a home network, the answer turns on two things: do you have multi-gig internet or a wired path that can feed it, and do you have the kind of busy, latency-sensitive client mix that MLO actually helps. If yes to both, the mid-range tri-band tier is a real upgrade and MLO is the reason. If your internet is gigabit, your core is wired, and you have no 6 GHz clients, stay where you are — Wi-Fi 6E already does almost everything you would feel, and the 46 Gbps on the box was never coming home.

$1,000 Local AI Workstation: RTX 5080-Class Build Guide (2026)

LK Wood IV — Mon, 15 Jun 2026 00:00:00 -0500

By LK Wood IV · 2026-06-15 · ~15 min read · St. Louis County, MO

Current cost — June 2026 (shortage-adjusted). The 2026 AI-driven DRAM/NAND shortage has hit this build’s memory and storage hard since these tables were priced: the 64GB DDR5-6000 kit now runs ~$600+ (was $130) and 32GB ~$420–$460 (was $75), and the 1TB NVMe drives have roughly doubled ($120–$160). That pushes the real totals to roughly **$2,800 for the Maximum build and ~$1,550 for the Value build** (64GB figure per Tom’s Hardware’s RAM price tracker; 32GB live Amazon, June 2026). The build tables below are the pre-shortage reference — every non-memory/storage part is about what it was. See the 2026 RAM and SSD price crisis for why, and the budget AM5 build for a fully current-priced build.

The inflection point for local AI inference happened somewhere around late 2024. Quantized versions of capable large language models started fitting in 16GB of VRAM. Inference libraries matured to where CPU→GPU bottlenecks largely vanished. And cloud API costs for heavy users got expensive enough that the math started working in local hardware’s favor.

This is what a well-reasoned local AI workstation looks like at the $1,000–1,500 price point in 2026, what you can actually run on it, and an honest answer to whether it makes financial sense versus paying per token.

What “local AI workstation” means here

A dedicated machine (or a homelab node) running an open-weight LLM via llama.cpp, Ollama, LM Studio, or a similar inference runtime — available to you at zero per-token cost, with full privacy, no internet dependency, and the latency of your local network.

This is not a training rig. Training LLMs requires far more VRAM and takes weeks on consumer hardware. This is inference — loading and running a pre-trained model — which is tractable on consumer GPUs with the right quantization.

The GPU is the only constraint that matters

For local AI inference, VRAM is the primary constraint. Model performance scales with VRAM — not CPU speed, not RAM speed (mostly), not storage IO. The entire model weights need to fit in GPU VRAM for full-speed inference. If they don’t, layers fall back to system RAM or disk, and throughput drops by 5–20× depending on how much spills over. Two calculators take the guesswork out of this: the LLM VRAM calculator shows whether a given model and quantization fit your card, and the LLM speed calculator estimates the tokens/sec you’ll get from your GPU’s memory bandwidth.

RTX 5080: 16GB GDDR7. At 4-bit quantization (Q4_K_M, the standard for quality/size tradeoff — roughly 0.6 bytes per parameter, per the VRAM calculator), 16GB fits:

Llama 3.1 8B — ~4.9GB, runs fast with giant context windows
Phi-4 14B / Qwen2.5 14B — ~9GB, the current sweet spot for quality per gigabyte
Mistral Small 24B — ~14GB, the largest class that fits with real context headroom
Gemma 3 27B — the ceiling case: ~16GB at Q4_K_M, so it needs a Q3-class quant or partial offload
What does NOT fit: the 70B class. Llama 3.3 70B at Q4_K_M is a ~42GB file, Qwen2.5 72B ~47GB, and Mixtral 8x7B ~26GB. Those run only with most layers offloaded to system RAM, at single-digit tokens/second.

RTX 5060 Ti 16GB: same VRAM, 60% of the throughput on large models. At current pricing (RTX 5060 Ti 16GB ~$450–500, RTX 5080 ~$1,000–1,100), the 5060 Ti has a dramatically better AI inference $/GB-VRAM ratio. The 5080 makes sense if you also game at 4K, run video production work, or want the absolute fastest inference. Both are 16GB cards, so both live in the same VRAM tier for what fits; for the full map of which models each capacity actually runs — 8GB through 48GB+, with real GGUF file sizes — see which local LLM fits your GPU by VRAM.

Component build

This is the build I run: Ryzen 7 7800X3D + ROG Astral RTX 5080 OC. Not the most cost-efficient for pure inference, but the 7800X3D’s cache benefits gaming when the GPU isn’t running inference, and the 5080 handles everything I throw at it. Prices are approximate as of June 2026 and shift week to week.

Maximum performance build (~$2,800 today / ~$2,250 pre-shortage, GPU-heavy):

Component	Part	~Price
CPU	AMD Ryzen 7 7800X3D	$350
Motherboard	ASUS ROG STRIX B650-A WiFi	$220
RAM	64GB DDR5-6000 (2×32GB)	$130
GPU	ASUS ROG Astral RTX 5080 OC	$1,100
Storage	Samsung 980 Pro 1TB NVMe	$90
PSU	EVGA SuperNOVA 1000 GT	$140
CPU Cooler	NZXT Kraken 360 AIO	$120
Case	Fractal North / Meshify C	$100
Total (pre-shortage ref.)		~$2,250 · ~$2,800 at current RAM/SSD prices

This is literally the system I’m running. The 7800X3D is overkill for inference — it’s there for gaming. A Ryzen 5 7600X at $200 would perform identically for LLM inference. To verify PSU sizing for your specific component selection, the PSU Wattage Calculator shows peak draw and efficiency headroom at a glance.

Value inference build (~$1,550 today / ~$1,180 pre-shortage):

Component	Part	~Price
CPU	AMD Ryzen 5 7600X	$190
Motherboard	MSI B650 Tomahawk WiFi	$170
RAM	32GB DDR5-5200 (2×16GB)	$75
GPU	RTX 5060 Ti 16GB	$480
Storage	WD Blue SN580 1TB NVMe	$65
PSU	Corsair RM750e	$90
CPU Cooler	Thermalright Peerless Assassin 120	$40
Case	Fractal Pop Air	$70
Total (pre-shortage ref.)		~$1,180 · ~$1,550 at current RAM/SSD prices

The 5060 Ti 16GB is the correct choice here. Same VRAM as the 5080, handles all the same models — just at about half the token rate (448 vs ~960 GB/s bandwidth): roughly 25–35 tokens/second on a 14B Q4 model against the 5080’s 50–65. For interactive use, you won’t feel the difference in a real conversation. For batch processing thousands of requests, you will.

What to install

Ollama is the fastest path to a working inference server. It handles model downloads, VRAM allocation, and exposes a local API compatible with OpenAI’s format:

# Install
curl -fsSL https://ollama.com/install.sh | sh

# Pull and run Qwen2.5 14B (Q4_K_M by default — a ~9GB fit in 16GB VRAM)
ollama pull qwen2.5:14b

# Start inference server
ollama serve

Ollama listens on port 11434. The OpenAI-compatible API endpoint is at /v1/chat/completions — configure any OpenAI SDK to point at http://localhost:11434/v1 and it works without code changes.

llama.cpp for more control over quantization, batch size, and GPU layers:

# Build with CUDA support
git clone https://github.com/ggerganov/llama.cpp
cd llama.cpp
cmake -B build -DLLAMA_CUDA=ON
cmake --build build -j$(nproc)

# Run with full GPU offload
./build/bin/llama-server \
 -m /models/mistral-small-24b-Q4_K_M.gguf \
 --n-gpu-layers 999 \
 --ctx-size 8192 \
 --host 0.0.0.0 --port 8080

The --n-gpu-layers 999 flag loads all layers to the GPU. If you exceed VRAM, layers fall back to CPU automatically — the number just means “as many as fit.”

Open WebUI for a ChatGPT-like interface over your local Ollama:

docker run -d --gpus all \
 -p 3000:8080 \
 -v open-webui:/app/backend/data \
 --add-host=host.docker.internal:host-gateway \
 ghcr.io/open-webui/open-webui:cuda

Open http://localhost:3000, connect to Ollama at http://host.docker.internal:11434.

The financial math

Cloud API pricing as of June 2026 (approximate, check current pricing):

OpenAI GPT-4o: ~$2.50/1M input tokens, ~$10/1M output tokens
Anthropic Claude 3.5 Haiku: ~$0.80/1M input, ~$4/1M output
Meta Llama 3.3 via Groq: ~$0.59/1M tokens

For comparison: a local open-weight model (the 8B–24B class this card actually fits) at zero marginal cost per token.

Break-even analysis at different usage levels:

Daily usage	Cloud cost/month (Llama via API ~$0.60/1M)	Local electricity/month	Break-even on $1,200 build
100K tokens	~$1.80	~$15–20	Never (cloud cheaper)
1M tokens	~$18	~$15–20	Effectively never — electricity alone eats the savings
5M tokens	~$90	~$15–20	17 months
20M tokens	~$360	~$15–20	4 months

The tipping point is somewhere around 2–3M tokens per day for a non-GPU-optimized cloud model. If you’re running summarization pipelines, document processing, coding assistants, or anything generating volume, local inference wins quickly.

Privacy factor. If your workload involves sensitive documents — contracts, medical records, proprietary code, personal communications — local inference isn’t just cheaper past the break-even point; it’s the only option that keeps data off external servers. That value is real even if you can’t put a dollar figure on it.

Power cost over 3 years

Using the Power & Cost Calculator for the full build:

Idle (no inference): ~85W
Under inference load: ~280–380W depending on model size, batch size, and GPU utilization
At 4 hours/day inference load + 20 hours idle, $0.13/kWh: roughly $10–14/month

Over 3 years: ~$360–500 in electricity for the GPU workstation. That’s the operating cost to factor into your break-even calculation. At $1,200 hardware + $480 electricity = $1,680 total 3-year cost. Compare to how much you’d spend on tokens. For a closer look at how draw and throughput behave under continuous load, the breakdown of RTX 5080 performance per watt running AI 24/7 measures where the power actually goes during inference.

What a build like this earns its keep on

The workload mix a 16GB local-inference box handles well:

Coding assistance — Qwen2.5-Coder-14B via the Continue.dev extension in VS Code. Fits in VRAM with room for context, no token costs, no code leaving the machine. (The 32B coder variant is a ~20GB file — it runs only with partial offload and a real speed penalty.)
Document summarization — batch-processing PDFs through a local API endpoint at zero marginal cost.
Image generation — ComfyUI with FLUX.1 models. The 16GB VRAM handles full-res generation without offloading.
Research drafting — a long-context 14B with 8K+ context for drafting sections with citations.

A setup like this doesn’t replace cloud APIs entirely — frontier models still win where answer quality matters more than volume. But the bulk-token workloads (summarization, coding autocomplete, drafts) are exactly the ones that move local — and once the LLM is running, the rest of a self-hosted AI stack (image generation, speech, a coding backend) drops onto the same box.

Want to see the RTX 5080’s specs and photos up close? The dataset page has the full breakdown. For keeping this workstation running efficiently, see the undervolt guide. Running a lower-cost GPU for local AI? The RTX 5060 local LLM setup tutorial covers Ollama, llama.cpp, and Open WebUI from scratch.

TechFuel HQ

Self-Hosted Read-It-Later Apps: Life After Pocket (2026)

What actually happened to Pocket

Read-it-later or bookmark manager? Answer this first

The tools, by the job they do

Readeck — the closest thing to “Pocket, self-hosted”

wallabag — the veteran, and the one with real export

linkding — minimal, fast, and archiving is opt-in

Shiori — one Go binary, slow and steady

Footprint and capability, side by side

What the Pocket export actually gives you

Gotchas the project docs don’t mention

Which one should you run?

Related reading

Sources

What PSU Does an RTX 5070 Need? (2026)

The card’s actual power specification

What a 5070 build actually draws

When 650W is not the answer

Transient spikes, honestly

The connector

If you already own the power supply

Lowering the number

Sources

What PSU Does an RTX 5080 Need? (2026)

The card’s actual power specification

Which 5080 did you buy?

When 850W becomes 1000W

Transient spikes, honestly

The undervolt that can buy a tier back

If you are coming from a smaller card

Sources

GPU Undervolt Settings Database: Real Results by Card (2026)

The results

How to read it

Contribute your card

What the data shows so far

Sources and methodology

How to Undervolt Your GPU: The Complete Guide (2026)

What undervolting actually does

Before you start: baseline your card

NVIDIA: the MSI Afterburner curve

AMD: the Adrenalin voltage offset

Test for stability (don’t skip this)

What to expect

Card-specific guides and the CPU too

Sources

PC Part Prices 2026: Verified Reference Dataset

The short version

When these prices were last verified

2026 PC part prices by category

Why a verified snapshot, and not a live tracker

Where the prices come from

Use the data (CC BY 4.0)

Related reading

Sources

The 3-2-1 Backup Rule for Homelabs (2026)

The short version

What the three numbers actually mean

RAID is not a backup. Neither is a snapshot on the same box.

Choose your three copies before you choose a tool

The off-site copy: how to actually build copy 3

The per-platform how-tos

3-2-1-1-0: the modern extension, and why ransomware forced it

The gotchas that never make it into the diagram

Related reading

Sources

9800X3D Undervolt Guide: Curve Optimizer Done Right

The first X3D chip AMD actually let you tune

Decide which outcome you want first

Know your stock numbers

Step 1: Baseline before you touch anything

Step 2: Find Curve Optimizer in your BIOS

Step 3: Set a conservative negative offset

Step 4: Only if you want the performance path

Step 5: Test for stability the right way

What to expect

Worth doing?

Sources

Authelia vs Authentik: Which Self-Hosted SSO (2026)