text model · MiniMax · Windows
Can I run MiniMax-M1-80k on Nvidia GeForce RTX 5090 (32GB)?
No. MiniMax-M1-80k needs ~284.6 GB even at Q4_K_M, but Nvidia GeForce RTX 5090 (32GB) only has ~31 GB usable.
Needs ~284.6 GB even at Q4_K_M, but only ~31 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 253.6 GB: MiniMax-M1-80k needs roughly 284.6 GB at Q4_K_M and Nvidia GeForce RTX 5090 (32GB) leaves only about 31 GB usable for a model. No single tracked device has enough memory; MiniMax-M1-80k needs a multi-GPU or high-memory rig.
- Q4_K_M needed
- ~284.6 GB
- Usable on device
- ~31 GB
- Device memory
- 32 GB
Which quant fits
How to run it
On Windows use LM Studio (Best GUI on Windows, auto-detects CUDA/Vulkan backends.).
- Parameters
- 456B (MoE, 45.9B active)
- Q4_K_M size
- 278.7 GB
- Context
- 1000k
- Memory
- 32 GB vram
- Usable for weights
- ~31 GB
- Power draw
- ~575 W
- Best runtime
- vLLM (Linux) / Ollama (CUDA)
What you can run instead
FAQ
Can Nvidia GeForce RTX 5090 (32GB) run MiniMax-M1-80k?
No. MiniMax-M1-80k needs ~284.6 GB even at Q4_K_M, but Nvidia GeForce RTX 5090 (32GB) only has ~31 GB usable.
How much memory does MiniMax-M1-80k need?
Nvidia GeForce RTX 5090 (32GB) does not have enough memory. At Q4_K_M the weights are ~278.7 GB; with KV cache and runtime overhead, budget ~284.6 GB at a 4k context. It is a Mixture-of-Experts model (456B total / 45.9B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run MiniMax-M1-80k 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/minimax-m1-80k/nvidia-rtx-5090-32gb) 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.