RAM not running at rated speed – XMP/DOCP fix
RAM stuck at 2133MHz? That's the JEDEC default. XMP/DOCP in BIOS is the fix. Here's how to set it right.
Quick answer: Enter BIOS, enable XMP (Intel) or DOCP (AMD) profile for your RAM, save and exit. Reboot and check speed in CPU-Z or Task Manager.
Had a client last month who bought a shiny new DDR5-6000 kit, installed it, and saw 4800MHz in Windows. He thought the RAM was defective. Nope. RAM sticks ship at a safe JEDEC standard speed (usually 2133, 2400, or 4800 for DDR5). The rated speed you paid for is an overclock profile stored on the sticks. You have to tell the motherboard to use it. That's XMP on Intel boards, DOCP on AMD. If you skip this step, your fancy 3600MHz kit runs like a basic 2133MHz one. Total waste of money.
Here's the deal: the memory controller on your CPU has to be able to handle that speed. Most modern CPUs (Intel 12th gen and up, AMD Ryzen 3000 series and up) handle 3200MHz fine. DDR5-6000 can be trickier—it depends on your motherboard's BIOS version and your specific CPU's memory controller quality (silicon lottery). I've seen Ryzen 7000 systems that just won't run 6000MHz stable without tweaking voltages. Start with the profile and see if it boots.
Step-by-step fix: Enable XMP/DOCP
- Restart your PC and mash the DEL or F2 key during boot to enter BIOS. On some boards it's F1 or F10—check your manual if you're not sure.
- Look for an overclocking or memory section. On ASUS boards it's usually under "AI Tweaker" or "Extreme Tweaker". MSI calls it "OC". Gigabyte has "M.I.T.". ASRock uses "OC Tweaker". On AMD boards, the DOCP setting is often under "Memory Frequency" or directly labeled "DOCP".
- Find the XMP or DOCP setting. It's usually a dropdown or an "Enable" button. On Ryzen boards, you'll see DOCP instead of XMP—same thing, different name. Select the profile that matches your RAM's rated speed (e.g., DDR4-3600 18-22-22-42). Don't pick the lower one if there are multiple.
- Save and exit (usually F10). The PC will reboot and may take a bit longer to train the memory. If it fails and boots to a black screen, don't panic—clear CMOS by jumping the pins or removing the battery for 30 seconds, then try again.
- Once Windows loads, check the speed. Download CPU-Z (free, no bloat) and look under the Memory tab for DRAM Frequency. Double it—DDR stands for Double Data Rate. So if it says 1600MHz, you're at 3200MHz. Or just check Task Manager > Performance > Memory > Speed.
If XMP/DOCP doesn't work
Sometimes the board just won't boot with the profile. I've had this on older Z370 boards with cheap RAM. Here are three fixes:
- Update your BIOS. Manufacturers add memory compatibility fixes constantly. On my own Z690 board, a BIOS update let me run DDR5-6400 stable where before it crashed at 5600. Check your motherboard's support page, download the latest BIOS, and flash it using the built-in tool (USB stick, FAT32 format).
- Manually set speed and timings. Instead of the profile, go into BIOS and set the RAM speed to, say, 2933 or 3000 if 3200 fails. Then set the primary timings (CAS, tRCD, tRP, tRAS) to the numbers printed on the stick label. Leave voltage at 1.35V for DDR4, 1.25V for DDR5 to start. If it works, try bumping up 100MHz at a time.
- Check CPU memory controller limits. Intel 10th gen and older often max out at 2933MHz. AMD Ryzen 1000 series tops out around 2933 too. If you're running a Ryzen 5 1600 with a 3600MHz kit, you're stuck—sell the RAM or replace the CPU. No workaround.
Prevention tip for next time
Before you buy RAM, check your motherboard's QVL (qualified vendor list) on the manufacturer's site. That list shows exactly which kits they tested at which speeds. If your exact model isn't on it, you're gambling. I learned this the hard way with a G.Skill kit that wouldn't run above 2666 on an ASRock B450—the QVL showed it tested at 3200, but only with a specific BIOS version. Always cross-reference. Also, buy 2 sticks instead of 4 if you want higher speeds—dual-rank setups are easier on the memory controller than quad-rank.
"I spent $200 on fast RAM and got slow RAM because I didn't enable XMP. Now I know." — every client I've ever had, basically.
Was this solution helpful?