Skip to main content
AMD Strix Halo (Ryzen AI Max+ 395/495) offers up to 192 GB of unified memory in a compact mini-PC form factor. The 128GB configuration is the sweet spot for 70B models at Q4, while the 192GB developer platform (Ryzen AI Max+ Pro 495) unlocks 120B+ MoE models. This guide covers what fits, what doesn’t, and the critical Vulkan vs ROCm backend decision.
Last verified: 2026-10-21. ROCm support for Strix Halo is evolving rapidly. Check the ROCm documentation and community benchmarks for the latest compatibility updates.

Hardware overview

AMD Strix Halo is a system-on-chip (SoC) that combines AMD’s Zen 5 CPU cores with RDNA 3.5 integrated graphics and up to 192 GB of unified LPDDR5X memory.
The 192GB Pro 495 has 160 GB GPU-accessible. The remaining 32 GB is reserved for the system. This is the key advantage over standard 128GB systems — you get 25% more memory for model weights.

What fits (and what doesn’t)

128 GB configuration (Ryzen AI Max+ 395)

Fits comfortably:
  • Qwen3.5-122B-A10B at Q4_K_M (~70 GB, 10-18 tok/s)
  • GPT-OSS 120B at Q4 (~59 GB, 35-51 tok/s)
  • GLM-4.5-Air at Q6_K_XL (~60 GB, 10-15 tok/s)
  • Qwen3.6-35B-A3B at Q4 (~20 GB, 54+ tok/s)
  • Qwen3 70B at Q4 (~40 GB, 12-20 tok/s)
Does NOT fit:
  • DeepSeek V4.1 Flash (763B) — smallest GGUF is ~233 GB, nearly 2x the 128GB
  • DeepSeek V4-Flash-0731 (284B) — needs ~155 GB, exceeds 128GB
  • GLM-5.2 (753B) — needs ~377 GB at Q4, far beyond 128GB
  • Qwen3.5-397B at Q4 (~224 GB) — exceeds 128GB
Best use case: 70B dense models at Q4 or 120B MoE models at Q4 with room for KV cache.

192 GB configuration (Ryzen AI Max+ Pro 495)

Fits comfortably:
  • Everything that fits on 128GB, plus:
  • Qwen3 235B at Q3_K_M (~130 GB, 8-12 tok/s)
  • DeepSeek V4-Flash-0731 (284B) at Q3 (~130 GB, 10-15 tok/s) — tight fit
  • Multiple 70B models simultaneously
Does NOT fit:
  • DeepSeek V4.1 Flash (763B) — still too large
  • GLM-5.2 (753B) — still too large
  • Qwen3.5-397B at Q4 (~224 GB) — exceeds 192GB
Best use case: 120B+ MoE models at higher quantization (Q6-Q8) or 200B+ models at Q3.
DeepSeek V4.1 Flash does not fit on any Strix Halo configuration. The model’s 763B total parameters require at least ~233 GB at the smallest usable quantization. For V4.1 Flash, you need 2x DGX Spark (256GB), Mac Studio M5 Ultra 512GB, or 4x RTX PRO 6000 Max-Q (384GB).

Backend decision: Vulkan vs ROCm

The most important decision for Strix Halo users is which inference backend to use. The choice between Vulkan and ROCm dramatically affects performance, stability, and ease of use. Best for: Stability, ease of use, broad model support
  • Pros: Works out of the box, no special drivers needed, broad model support via llama.cpp
  • Cons: 10-20% slower than ROCm (when ROCm works), no native AMD tensor core acceleration
  • Performance: ~10-18 tok/s on 120B MoE models
  • Setup: Use llama.cpp with Vulkan backend
When to choose Vulkan:
  • You want a stable, supported path
  • You’re running GGUF quantization models
  • You don’t want to deal with ROCm driver issues
  • You’re okay with 10-20% lower performance

ROCm 7.2 (for advanced users)

Best for: Maximum performance, native AMD acceleration
  • Pros: 20-30% faster than Vulkan (when it works), native RDNA 3.5 acceleration
  • Cons: Requires HSA_OVERRIDE_GFX_VERSION=11.5.1 environment variable, limited model support, driver issues
  • Performance: ~15-25 tok/s on 120B MoE models (when working)
  • Setup: Use vLLM or llama.cpp with ROCm backend
When to choose ROCm:
  • You need maximum performance and accept the tinkering
  • You’re running AWQ or FP8 quantization (better supported in ROCm)
  • You’re comfortable debugging driver issues
  • You’re on Linux (ROCm has limited Windows support)
ROCm on Strix Halo is not officially supported. AMD’s ROCm targets datacenter and professional GPUs, not consumer APUs. The HSA_OVERRIDE_GFX_VERSION=11.5.1 workaround makes it work, but you may encounter:
  • Crashes on certain model architectures
  • Slower performance than expected
  • Driver incompatibilities after system updates
Recommendation: Start with Vulkan. Only switch to ROCm if you need the extra performance and accept the unsupported path.

Model recommendations by use case

Individual developer (128 GB config)

Research / power user (192 GB config)

Maximum performance (ROCm path)

System vendors

Strix Halo is available in mini-PCs, laptops, and desktops from several vendors.

Mini-PCs

Desktops

Laptops

Memory is soldered — buy the configuration you need at purchase. There is no SO-DIMM slot or expansion option. The 128GB vs 192GB decision is permanent.

Performance benchmarks

Community benchmarks show Strix Halo delivers competitive performance for 70B-120B models, but falls behind DGX Spark and Mac Studio on larger models.

Single-user inference (Vulkan backend)

Comparison to other platforms

Strix Halo is 2x slower than DGX Spark on the same model, but costs ~$500 less. It’s a good value for 70B-120B models, but not competitive for larger models or high-throughput serving.

Setup guide

  1. Install Ubuntu 22.04 or 24.04
    • Use a USB installer (Rufus or balenaEtcher)
    • Select “Install alongside Windows” for dual-boot
  2. Install prerequisites
  3. Build llama.cpp with Vulkan support
  4. Download a model
  5. Run inference

Windows

  1. Install Ollama
    • Download from ollama.com
    • Ollama automatically detects Vulkan-capable GPUs
  2. Pull a model
  3. Run inference

ROCm setup (advanced)

  1. Install ROCm 7.2
  2. Set environment variable
  3. Build llama.cpp with ROCm support
  4. Run inference

Common issues and troubleshooting

Issue: Vulkan not detected

Cause: Missing Vulkan drivers or llama.cpp not built with Vulkan support. Fix:

Issue: ROCm crashes on certain models

Cause: ROCm does not fully support RDNA 3.5 on Strix Halo. Fix:
  • Switch to Vulkan backend (recommended)
  • Try a different model architecture (some work better than others)
  • Update to latest ROCm version
  • Check community forums for model-specific workarounds

Issue: Slow performance on 120B models

Cause: Memory bandwidth bottleneck (256 GB/s is lower than DGX Spark’s 273 GB/s or Mac Studio’s 1,200 GB/s). Fix:
  • Use smaller models (70B instead of 120B)
  • Use MoE models with fewer active parameters (Qwen3.6-35B-A3B has 3B active)
  • Accept the performance — Strix Halo is not designed for maximum throughput
  • Upgrade to DGX Spark or Mac Studio for 2-4x faster inference

Issue: Out of memory on large models

Cause: Model + KV cache exceeds available memory. Fix:
  • Use lower quantization (Q4 instead of Q8)
  • Reduce --ctx-size to limit KV cache
  • Use a smaller model
  • Upgrade to 192GB Pro 495 configuration

Is Strix Halo right for you?

Choose Strix Halo if:
  • You need 128GB unified memory in a compact form factor
  • You want a quiet, low-power system (15-54W TDP)
  • You’re running 70B-120B models at Q4-Q6
  • You prefer Linux or are comfortable with Vulkan backend
  • Budget is $2,500-4,300
Avoid Strix Halo if:
  • You need to run frontier models (V4.1 Flash, GLM-5.2) — they don’t fit
  • You need maximum throughput — DGX Spark is 2x faster
  • You want plug-and-play simplicity — Mac Studio is easier
  • You need CUDA support — Strix Halo is AMD-only
  • You’re on a tight budget — used RTX 3090 (24GB) is $700-900

Next steps

Hardware reference

Compare Strix Halo against DGX Spark, Mac Studio, RTX PRO, and budget hacker tier.

Mac Studio M5 Ultra buying guide

Apple alternative with 256-512GB unified memory and 1,200 GB/s bandwidth.

DGX Spark model compatibility

See which models fit on DGX Spark’s 128GB unified memory (2x faster than Strix Halo).

Model fit

Calculate which model sizes and quantizations fit your Strix Halo’s unified memory.