Pick one job for the upgrade, record the machine as it is, check the resource that job uses (M.2 lanes, display bandwidth, power or cooling), install one change, and retest the old job as well as the new one. The template starts from the author’s 7800X3D and RTX 5080 rig, so replace its parts with yours.
Contents
Provenance
- Oct 3, 2026Published
- Nov 18, 2026Last substantive update
Expansion rule
Preserve the known machine first. Pick one job for the change, check the resource it consumes, and define the result that would justify keeping it. The owner build and dataset stay attached as the baseline.
Start from the existing 4K rig. This template represents LK Wood IV’s authored Ryzen 7 7800X3D and RTX 5080 system. It should not be used as proof that another machine has the same parts, cooling, power behavior, or benchmark results.
If your own PC has a 7800X3D and an RTX 5080, use the template as a worked example and replace its parts with yours before you check anything.
This is an expansion project. The source build documents the exact 4K rig LK Wood IV runs, and the linked ROG Astral RTX 5080 dataset preserves its first-party benchmark and power record; the useful move is to keep that baseline intact while asking whether one additional job deserves hardware and time, plus another failure surface.
1. Capture the machine before proposing a change
Open the template and confirm the build. PC Builder restores the exact Ryzen 7 7800X3D, ROG Astral RTX 5080 OC and ROG STRIX B650-A. The Samsung 970 EVO Plus 1TB, EVGA SuperNOVA 1000 GT and HYTE Y60 aren’t in its catalogue, the NZXT Kraken 360 is outside its checks, and the memory kit is unspecified, so those stay listed for manual checks. Don’t auto-select replacements. Then record the current state that matters to this expansion:
- The installed motherboard, firmware version, memory configuration, storage devices, power supply, case, and cooling path.
- The display connection from GPU port to cable, adapter or receiver, and panel.
- The occupied expansion slots, M.2 sockets, SATA ports, and power connectors.
- Any existing fault or workaround that the change must not hide.
The source article names the owner’s actual core configuration and separates it from the parts recommended for a fresh build. Keep that distinction. A B650E suggestion in the article does not turn the owner’s B650 board into B650E, and a fresh-build PSU recommendation does not replace the supply already installed. Photograph the cable routing and card clearances before touching the machine, and note where those photos live in the project record.
2. Give the expansion one primary job
Write one sentence that begins with a verb: add fast project storage, hold a larger local model, connect a higher-bandwidth display, reduce load noise, or create a clean capture path. If the sentence contains three jobs, split them into phases. Then define a stop condition, such as one more usable NVMe drive without taking a GPU lane, a display mode the whole output chain can carry, or a storage target that fits without moving active data onto an unprotected drive. A stop condition keeps a successful first phase from turning into an unnecessary rebuild.
I would also state what remains fixed. On this project, the 7800X3D and RTX 5080 are the baseline unless the expansion evidence proves they block the job. A new generation alone is not that evidence.
3. Route the job to the constrained resource
Each expansion spends a different resource. Check the one your plan consumes before shopping.
NVMe or add-in storage
Open the NVMe Expansion Checker and select the exact motherboard record when it exists. It shows modeled socket and lane-sharing limits, but it doesn’t replace the board manual: confirm the exact socket, supported drive length, heatsink clearance, lane sharing and any port that configuration disables in the maker’s documentation. If the board is missing from the checker, record that as a limitation rather than picking a similar board; a nearby model can have a different lane map.
Display or capture path
Use the DisplayPort and HDMI Bandwidth Calculator for the resolution, refresh rate, color depth and chroma you want, then check every device between the GPU and the panel. The weakest cable, adapter, capture device, receiver or input decides what the path can carry. If a new display symptom appears, open the Diagnostic Workbench and record the full display path before swapping more parts.
Power or cooling change
The source build includes first-party power observations for this exact owner rig. Keep those observations attached as baseline evidence, then use the PSU Wattage Calculator for the changed configuration. Do not turn the existing measurement into a promise about a different card, power limit, workload, or supply.
For cooling, write down the problem you’re solving: temperature, noise, sustained clocks or physical clearance. “Better cooling” can’t be verified; a temperature limit or a before-and-after noise check under the same workload can.
Local AI or memory pressure
Start with the local LLM VRAM guide, the 16GB RTX 5080 measurements and the LLM VRAM Calculator. Record model, quantization, context length and the speed you need. An RTX 5080 doesn’t make every model fit, and system memory or storage may become the next limit after VRAM.
4. Change one layer, then retest the baseline
Before installation, export the project and record the last known-good state. After installation:
- Confirm the machine reaches the same idle desktop and display mode it held before.
- Confirm the new device appears with the expected identity and capacity.
- Run the shortest test that exercises the new job.
- Recheck the old job most likely to be affected by the shared resource.
- Record the outcome before changing firmware, drivers, cables, or settings again.
That order protects cause and effect. Installing an SSD, updating firmware, changing the GPU driver and rerouting the display cable in one pass creates four suspects if the machine stops behaving. Use the Diagnostic Workbench for a failed retest.
5. Close the project with a keep, revert, or follow-up decision
An expansion is complete when the new job passes its stop condition and the original job still passes its own. Close it with one of three outcomes:
- Keep: the expansion earned its place and the baseline remains healthy.
- Revert: the cost, instability, noise, lost lanes, or physical compromise is larger than the benefit.
- Follow up: one named uncertainty remains, with the next test and owner written down.
Export the final project after the outcome. A shared project link carries the title, part names and tool inputs but leaves out the use case, constraints, evidence and diagnostic notes; send the exported file when someone needs the full record.
What the sources establish
The 4K build article establishes the owner’s actual system, its build decisions, and the boundary between installed parts and fresh-build alternatives. The open GPU dataset establishes the measurements it publishes for that rig, while the ROG Astral review provides the ownership verdict around the same card and this guide contributes only a change-control path, without adding a measured result, fit claim, price, or statement that the owner’s system represents every 7800X3D and RTX 5080 build. Any new component needs its own exact model check and a fresh result after installation.
Updates and corrections
- Last updated
- Methodology
- See our methodology for research and review standards.
- Update log
- 2026-11-18 — Listed exactly which of the rig’s parts PC Builder restores, including the HYTE Y60 and Kraken 360 it can’t, and cut the tool-operation detail.
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.