Why Lenovo Legion Go stutters (or pages)
Native or near-native 1600p textures inflate the graphics working set versus 1080p Ally/Deck targets. With only 16GB total, a 4G UMA underserves the panel while an 8G UMA starves Windows. The classic symptom is hitching in FC/Alan Wake-class titles when Legion Space + Windows Defender scan during a shader compile.
What to buy or configure
Buy Legion Go knowing RAM is fixed. Prefer lower in-game render resolutions with FSR if you refuse to leave 6G UMA. If you need expandable memory for productivity docking, pick Framework 13 or a dual-SO-DIMM mini-PC instead of waiting for a Legion Go RAM kit that does not exist.
Memory deep dive
Lenovo Legion Go pairs Z1 Extreme with a high-pixel-density display and 16GB soldered LPDDR5X-7500. Bandwidth is strong; the editorial story is resolution-driven VRAM pressure against a Windows handheld OS. There are no SO-DIMM slots — optimization is BIOS UMA, pagefile, and render-scale discipline.
Clearance / form factor: Not applicable — LPDDR5X packages are soldered under the shield.
Tuning notes: Enter BIOS via Volume Up + Power → BIOS Setup → More Settings → Configuration → UMA Frame Buffer Size → 6G. Auto/3G–4G often under-allocates for 1600p UI + game buffers. Keep a fixed Windows pagefile and close Legion overlay extras while benchmarking.