The frustration is real
You bought 3200MHz RAM and CPU-Z shows it running at 2133MHz. You enabled XMP in BIOS, it booted once, then crashed or reverted. I've been there, and I'm going to show you the fix that actually works, not just the one everyone repeats.
The fix: manual timing entry
Skip XMP entirely if it's flaky. Go into BIOS, find the memory settings (often under Advanced > DRAM Configuration or Ai Tweaker on ASUS), and set these manually:
- Set
AI Overclock TunerorMemory Frequencyto your RAM's rated speed (e.g., 3200MHz). - Enter the primary timings from the RAM's spec sheet. Most kits list them at 16-18-18-38 or similar. Find the exact ones for your kit.
- Set
Command Rateto 2T (also shown as2N). This is the first thing to relax if stability is iffy. - Set
DRAM Voltageto the rated value. For DDR4 at 3200MHz, that's usually 1.35V. For DDR5 at 5600MHz, it's 1.1V. Check the sticker on the sticks.
Save, reboot, and check with CPU-Z. If it holds, you're done. If it still crashes, bump Command Rate to 3T or increase voltage by 0.02V (don't exceed 1.4V for daily use).
Why this works
What's actually happening is that XMP is a one-size-fits-all profile, and your motherboard's memory training may not agree with it. The board reads the XMP data, tries to run those timings, but if the CPU's memory controller (IMC) can't handle them at the rated voltage, it silently falls back to the JEDEC base spec (2133MHz). That's the crash or the stuck speed.
When you enter the timings manually, you're doing the same thing XMP does, but you control the exact values and voltage. The reason this works when XMP fails is that you can relax secondary timings (like Command Rate) that XMP sets aggressively. The board also skips the handshake that sometimes misbehaves.
Less common variations
RAM runs at half speed
You see 1600MHz when it should be 3200MHz. That's not an error—DDR stands for Double Data Rate. CPU-Z shows the effective speed in the Memory tab, but the actual clock is half. Don't panic if it shows half; that's normal. If it shows 1066MHz for a 2133MHz kit, that's fine too.
XMP works but crashes in games
This is a stability issue, not a speed issue. Your IMC can't hold those timings under load. Drop the frequency one step (e.g., 3200 to 3000) and keep the same timings. Or raise voltage to 1.38V if your cooling allows. Use MemTest86 (free) to verify at least 4 passes.
Only one stick runs at full speed
You have two sticks, and CPU-Z shows one at 3200 and the other at 2133. That's a hardware fault or poor seating. Reseat both, swap slots. If it follows the stick, that stick is dead. If it follows the slot, the motherboard slot may be damaged.
AMD vs Intel differences
On AMD Ryzen, the Infinity Fabric (FCLK) is tied to memory speed. For 3200MHz, FCLK should be 1600MHz (1:1). If you manually set memory speed without adjusting FCLK, you'll get a penalty. Check your BIOS for Infinity Fabric Frequency and Multiplier and set it to the memory speed divided by two.
Prevention for next time
Before you buy RAM, check the motherboard QVL (Qualified Vendor List). That's a list of tested kits. It doesn't guarantee compatibility, but it filters out most no-post scenarios. Also, buy kits sold as a set—two sticks from different batches won't run at XMP speeds reliably.
After any BIOS update, your XMP profile resets. Re-enable it, and if it fails, re-enter your manual timings. Save your working BIOS settings as a profile (F11 on most boards) so you can reload after a reset.
If you're on an older board (Z170, B450) with a newer CPU, expect XMP issues. The board's memory trace layout was designed for slower memory, and it can't handle fast sticks no matter what you do. In that case, a mild overclock (like 2800MHz on a 3200 kit) is the smart play. Don't force it—the performance difference between 2800 and 3200 is often less than 3%.
One more thing: don't update BIOS just to get XMP working unless you have a reason. A BIOS update can break more than it fixes. If your current BIOS has the manual options, use them.