Fix: RAM not running at advertised speed

I know this one drives you nuts—you just spent good money on 3600MHz RAM and CPU-Z shows 2133. It's not broken. It's XMP (or DOCP on AMD) not enabled. Let's fix that right now.

The fix: enable XMP in BIOS

Restart your PC and mash Del or F2 during boot to enter BIOS. On some boards it's F10 (HP), F1 (Lenovo), or Esc (some Asus).
Find XMP/DOCP — look under AI Tweaker (Asus), OC Tweaker (ASRock), Extreme Tweaker (some Asus), or Performance (MSI). On Gigabyte, it's under Tweaker > Extreme Memory Profile (XMP). You're looking for a toggle or dropdown.
Enable Profile 1 — select the XMP profile that matches your kit's advertised speed, usually Profile 1. If you see two, pick the first one.
Save and exit — usually F10, then confirm. The PC will reboot and should run at the correct speed.

That's it. Nine times out of ten, this is the fix. But since you're reading this, yours might be the tenth case. Let's check why.

Why this works

Your RAM sticks are rated for a certain speed, but they default to a JEDEC standard (usually 2133 or 2400MHz) to guarantee compatibility across all systems. XMP is a pre-validated overclocking profile stored on the RAM stick itself. The motherboard reads it and applies the timings, voltage, and frequency the manufacturer tested. Without XMP, the board plays it safe and runs the RAM at the slowest common denominator. Enabling XMP tells the motherboard to trust the profile.

On AMD Ryzen systems, you might see DOCP (Direct Overclock Profile) or EOCP—same thing, different name. On some newer boards, it's under Memory Frequency and you manually set it to the rated speed. Auto doesn't work there.

Less common variations

1. XMP is enabled but speed still wrong

This usually means your CPU memory controller can't handle the speed. On Ryzen 3000-series, 3600MHz is the sweet spot. On older Ryzen (1000/2000), 3200MHz is a stretch. On Intel 12th/13th gen, you might need to update BIOS to support XMP on DDR5 kits.

Fix: Manually set the frequency lower, like 3200MHz, and leave the timings from the XMP profile. Or update your BIOS. I've seen a single BIOS update fix this on MSI Z690 boards with Corsair Vengeance DDR5.

2. Only two sticks out of four work at speed

Running four sticks puts extra load on the memory controller. Even if your kit is sold as a 4-stick set, the controller might max out at 3200MHz instead of 3600. Drop the speed by one notch (e.g., 3400 instead of 3600) and test stability with MemTest86.

3. Cold boot fails but works after restart

Classic sign of borderline voltage or timing stability. You need more voltage to the memory controller or the RAM itself. On Ryzen, try bumping SOC voltage to 1.15V (max safe is 1.2V). On Intel, increase VCCSA or VCCIO to 1.2V–1.25V. This is advanced—don't go above 1.35V on RAM voltage unless you know your kit's limits.

4. XMP option isn't visible in BIOS

Some OEM boards (Dell, HP, Lenovo) lock XMP. You can't enable it in BIOS. Workarounds: use Intel XTU or AMD Ryzen Master to apply the profile in Windows, but it's not persistent. Best long-term fix is a proper aftermarket motherboard. Painful but true.

How to avoid this next time

Check the motherboard's QVL (Qualified Vendor List) before buying. RAM kits are tested and listed there for specific motherboards. If your kit isn't on the list, it might work, but you're gambling on speed compatibility.
Buy RAM from a reputable manufacturer — Corsair, G.Skill, Kingston, Crucial. Off-brand sticks often have worse XMP profiles or fake ratings.
Update your BIOS before troubleshooting RAM issues. I've seen boards ship with buggy memory training code that gets fixed in a later revision.
Use two sticks, not four if you're chasing max speed. Dual-channel with two sticks is easier on the memory controller and almost always clocks higher than four sticks.

If you've done all this and still stuck, try a CMOS reset (remove the coin battery for 30 seconds with the PSU unplugged). Sometimes the board gets confused after failed attempts and needs a clean slate. Then re-enable XMP fresh.

That should get your RAM running where you paid for it. If not, your sticks might be defective or your CPU memory controller is the weak link. Either way, you've eliminated the easy causes.