text model · EXAONE · Windows
Can I run EXAONE 4.0 32B on AMD Ryzen AI Halo (128GB)?
Yes. EXAONE 4.0 32B runs on AMD Ryzen AI Halo (128GB) at Q4_K_M (~20.2 GB of ~96 GB usable).
Runs at Q4_K_M using ~20.2 GB of ~96 GB usable. You have room for FP16 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. AMD Ryzen AI Halo (128GB) leaves ~75.8 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~20.2 GB
- Usable on device
- ~96 GB
- Device memory
- 128 GB
- Best quant
- Q4_K_M
Which quant fits
Running cost · estimate
- Power draw
- ~120 W
- Electricity / 1M tokens
- ~$0.56
At ~$0.15/kWh and the estimated ~9 tok/s, a million generated tokens costs about $0.56 in electricity. TDP is the peak draw, so this is an upper bound. Assumptions.
Run it
Pick your tool. All 2 load the same Q4_K_M weights.
llama-cli -hf LGAI-EXAONE/EXAONE-4.0-32B-GGUF:Q4_K_M lms get LGAI-EXAONE/EXAONE-4.0-32B-GGUF How to run it
On Windows use LM Studio (Best GUI on Windows, auto-detects CUDA/Vulkan backends.).
- Parameters
- 32B
- Q4_K_M size
- 18.02 GB
- Q8_0 size
- 31.67 GB
- Context
- 131k
- Memory
- 128 GB unified
- Usable for weights
- ~96 GB
- Power draw
- ~120 W
- Best runtime
- llama.cpp (Vulkan/ROCm) / LM Studio
You could also run
Run EXAONE 4.0 32B on other hardware
FAQ
Can AMD Ryzen AI Halo (128GB) run EXAONE 4.0 32B?
Yes. EXAONE 4.0 32B runs on AMD Ryzen AI Halo (128GB) at Q4_K_M (~20.2 GB of ~96 GB usable).
How much memory does EXAONE 4.0 32B need?
AMD Ryzen AI Halo (128GB) has room to spare. At Q4_K_M the weights are ~18.02 GB; with KV cache and runtime overhead, budget ~20.2 GB at a 4k context.
What is the best tool to run EXAONE 4.0 32B 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
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/exaone-4-32b/amd-ryzen-ai-halo-128gb) 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.