Explore builds
STARTER BUILD / RigAtlas starter

Ryzen 9 9950X3D2 Dual Edition + RTX 5090 PC Build.

Reference imageImages are for reference only. Refer to the linked store for actual product images.
ABOUT THIS BUILD

A dual-cache 16-core CPU, 32 GB GeForce GPU and 96 GB DDR5 for demanding mixed workloads. A large chassis and 420 mm AIO are selected; check radiator position and memory QVL. High-end stock and pricing may push the purchase total well above this target. This USD budget is an illustrative planning target, not a verified parts total or a retailer quote. Check current local prices, BIOS support and mounting clearances. Images are for reference only. Refer to the linked store for actual product images. MSI X870 Tomahawk is listed by ARCTIC for pump clearance; confirm exact CPU BIOS support separately.

8 componentsBudget in USD
CONFIGURATION

Flagship dual-cache · GeForce RTX 5090

8 / 8 core parts
COMPONENTYOUR SELECTIONRECORDED PRICE
Processor
AM5 · DDR5
Checking price…
Not recorded
Motherboard
AM5 · DDR5 · ATX
Checking price…
Not recorded
Graphics card
32 GB GDDR7
Checking price…
Not recorded
Memory
DDR5 · UDIMM
Checking price…
Not recorded
Storage
M.2 2280
Checking price…
Not recorded
Power supply
ATX
Checking price…
Not recorded
CPU cooler
420 mm AIO
Checking price…
Not recorded
Case
Full-tower
Checking price…
Not recorded
Recorded prices are entered by you in USD. Retailer prices, tax and delivery may differ.
AI & YOUR BUILD

What AI work can this PC handle?

Explore cloud use, local language models and image generation with the parts you selected. Memory estimates are not speed benchmarks.

System memory96 GB
Dedicated graphics memory32 GB
Selected graphics cardGeForce RTX 5090 32G VENTUS 3X OC

Cloud AI

Inference runs on the service’s servers.

A larger local GPU is not required just to chat with a cloud model or request cloud-generated images. Check the service account, availability in your region, internet connection and supported browser or client.

Local editing, 3D work and running several apps still use your PC’s resources. This does not guarantee a service’s response time.

How cloud inference works

Local image generation

Choose the exact model and workflow first.

Check the exact GPU, driver and CUDA support in your chosen application.

Image size, batch size, model components and extra nodes change memory use. CPU offloading can reduce VRAM demand but may be slow. Video generation, training and fine-tuning require separate assessments.

ComfyUI hardware requirementsModel memory and offloading

Local language models

Change the assumptions to explore the memory tradeoff. These are model sizes, not recommendations for a specific model.

Weights may fit; full inference still needs verification.

Theoretical weight storage only: 3.7 GiB · 8B / 4-bit

Actual use is higher: quantization metadata, unquantized tensors, KV cache, compute buffers and the runtime also need memory. Total installed memory is not the same as free memory.

Weight storage scenarios at the selected precision
ParametersWeight lower boundCompared with selected VRAM
3B1.4 GiBWeights only; overhead not included
8B3.7 GiBWeights only; overhead not included
14B6.5 GiBWeights only; overhead not included
32B14.9 GiBWeights only; overhead not included
70B32.6 GiBNot enough for weights alone
  • Check the exact GPU, driver and CUDA support in your chosen application.
  • Longer context increases KV-cache demand. A weights-only fit does not establish whether your selected context or concurrent requests will fit.
  • Check CPU instruction support, the exact OS version, drivers and available SSD space for model downloads. LM Studio on Windows x64 requires AVX2; this catalog does not verify instruction sets.
Method, limits and how to verify

Weight lower bound = total parameters × bits ÷ 8. B means one billion parameters; GiB means 2³⁰ bytes. All parameters are counted, including inactive experts in a mixture-of-experts model. Nominal catalog RAM and VRAM capacities are used as GiB for this planning comparison.

Shared system memory is not added to dedicated VRAM. RAM kit capacity is counted once. Already-owned parts still count as installed hardware. No throughput or “smooth performance” claim is made.

After assembly, use the actual model file and context setting with the runtime’s resource estimator, then measure response speed and memory use in your workload.

LM Studio resource estimation

Weight estimates · Context and memory · GPU runtime support · Application requirements

Selected GPU manufacturer specifications · 2026-09-10

AI documentation checked: 2026-09-19
THE CHOICES BEHIND THIS PARTS LIST

Who this build is for

A large, high-capacity enthusiast configuration combining Ryzen 9 9950X3D2 Dual Edition, a 32 GB RTX 5090 and 96 GB system memory. It requires careful workload justification and installation planning.

Why these components are together

The CPU and GPU are separate high-end choices, not a guarantee of proportionate benefit in ordinary applications. Confirm that your workload uses the extra compute and memory resources.

The 96 GB memory kit and 4 TB 9100 PRO expand capacity and storage capability. Verify the exact kit, firmware, M.2 connection and heatsink requirements rather than relying on capacity labels.

The 420 mm Liquid Freezer III Pro, 7000D AIRFLOW and 1200 W Straight Power 12 make physical installation and cabling major parts of the plan. Read the exact radiator and motherboard pump-clearance guidance.

Tradeoffs and checks before ordering

  • Board support and the installed BIOS must cover the exact Dual Edition CPU.
  • The radiator and fans must fit as a complete stack in a documented position.
  • Check the GPU's approved power connection, bend space and support arrangement before closing the case.

What to change first

Validate the current workload before adding still more hardware. External backup, application workflow and display requirements can be more relevant than another specification increase. Record real project results instead of treating the flagship label as evidence.

This is an editorial parts-list explanation. The planning target is not a current retailer total, and this configuration has not been benchmarked by RigAtlas.

Component specification sources