text model · Qwen3 · Windows
Can I run Qwen3 235B A22B on AMD Radeon RX 7900 XTX (24GB)?
No. Qwen3 235B A22B needs ~136.9 GB even at Q4_K_M, but AMD Radeon RX 7900 XTX (24GB) only has ~23 GB usable.
Needs ~136.9 GB even at Q4_K_M, but only ~23 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 113.9 GB: Qwen3 235B A22B needs roughly 136.9 GB at Q4_K_M and AMD Radeon RX 7900 XTX (24GB) leaves only about 23 GB usable for a model. The lightest tracked hardware that runs Qwen3 235B A22B is the Apple M3 Ultra (256GB) at 256 GB. See Qwen3 235B A22B on Apple M3 Ultra (256GB).
- Q4_K_M needed
- ~136.9 GB
- Usable on device
- ~23 GB
- Device memory
- 24 GB
Which quant fits
- Parameters
- 235B (MoE, 22B active)
- Q4_K_M size
- 132.39 GB
- Q8_0 size
- 232.77 GB
- Context
- 128k
- Ollama tag
- qwen3:235b
- Memory
- 24 GB vram
- Usable for weights
- ~23 GB
- Power draw
- ~355 W
- Best runtime
- Ollama (ROCm) / llama.cpp ROCm (Linux)
What you can run instead
Run Qwen3 235B A22B on other hardware
FAQ
Can AMD Radeon RX 7900 XTX (24GB) run Qwen3 235B A22B?
No. Qwen3 235B A22B needs ~136.9 GB even at Q4_K_M, but AMD Radeon RX 7900 XTX (24GB) only has ~23 GB usable.
How much memory does Qwen3 235B A22B need?
AMD Radeon RX 7900 XTX (24GB) does not have enough memory. At Q4_K_M the weights are ~132.39 GB; with KV cache and runtime overhead, budget ~136.9 GB at a 4k context. It is a Mixture-of-Experts model (235B total / 22B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Qwen3 235B A22B on Windows?
LM Studio for a simple setup; Ollama (CUDA) for the most speed. AMD GPUs run via Vulkan/ROCm at roughly half CUDA throughput. NVIDIA is the smooth path on Windows.
Embed this
[](https://localmodel.run/can-i-run/qwen3-235b-a22b/amd-rx-7900-xtx-24gb) Sources
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.