In this article
Radeon RX 7700 XT has 12 GB GDDR6, while the official non-XT RX 7700 names a different 16 GB configuration.
Radeon RX 7700 XT has 12 GB GDDR6, while the official non-XT RX 7700 names a different 16 GB configuration. In this pair, the XT suffix does not mean a larger memory capacity.
Official variants and the memory boundary
The table follows AMD materials for this model. It describes dedicated device memory, not system RAM. A “not verified” entry preserves a source gap; a neighboring configuration cannot supply the missing specification.
| AMD variant | Dedicated memory | Board power |
|---|---|---|
| 12 GB | 12 GB GDDR6 | 245 W |
Establish the LLM software path
The ROCm Core SDK 10.1.0 device list includes Radeon RX 7700 XT. This is an exact hardware entry, not approval for every operating system, PyTorch build, or quantization format. Select the specific GPU and OS in the compatibility matrix, then record the driver, runtime, and framework release. A listed card does not establish that every kernel used by an inference engine works correctly. Establish device detection, loading of a saved model revision, and a reference request before exploring sustained operation or concurrent requests.
A practical scenario for this model
The scenario is correcting a script that selects a profile by the number 7700 and assumes XT has more VRAM. For these products, that assumption changes the memory budget in the wrong direction. Record the full device name and detected memory, then match them against the product specification. When migrating a 16 GB profile, validate weight placement first and the required context on 12 GB afterward. If the engine automatically shortens context or leaves layers on the CPU, preserve that as a changed profile. Merely correcting the displayed model name cannot restore the missing resources. Automation should therefore rely on exact identity and validated configuration rather than an assumed performance ordering of letter suffixes. Such an inventory fix prevents later deployment steps from repeating the same mistaken capacity choice.
Validate Blender Cycles separately
RDNA 3 meets the HIP hardware floor in the Blender Cycles 5.2 LTS manual: RDNA 1 or newer. This renderer requirement is independent of ROCm LLM support; validate the actual driver, build, and scene on the intended machine.
When moving a scene from a 16 GB card, preserve all resources and compare a completed frame. Removing large objects to enable startup creates a simplified scene that belongs in a separate project variant.
Preserve a machine-level acceptance record
The table gives AMD board-power specifications, not measured whole-computer consumption. Check the power supply, connectors, card dimensions, and airflow path for the actual system separately. Board power cannot establish inference speed.
The profile should state RX 7700 XT, 12 GB, and the 245 W board specification. Keep validated context limits separate from the model name and original user expectations.
The acceptance artifact should connect board identity, software versions, model revision, and the workload actually exercised. After any of those changes, the old result describes its original run rather than establishing compatibility of the new configuration.
Related reading
RAM and VRAM: which memory matters for an AI server?; Make llama.cpp automatic fit settings reproducible; NVIDIA and AMD GPU catalogue for LLM inference and server rendering.