You flipped on XMP in the BIOS, hit save, and now your board is stuck on the DRAM debug LED, fans spin up, then it restarts. Again. And again. I know this loop is infuriating, especially when the RAM is advertised at 3600 or 6000 MT/s and you just want the speed you paid for. Deep breath. This is almost always a memory training failure, and there's a ladder of fixes. Start at step one. Stop when it boots.
Why the DRAM light comes on with XMP/DOCP
XMP (Intel) and DOCP (AMD, basically the same thing) are just factory overclock profiles burned into the RAM's SPD chip. They raise frequency, tighten timings, and bump voltage above the JEDEC default of 2133 or 2400 MT/s. Your CPU's memory controller has to actually hold those speeds. If it can't, the board fails memory training before POST and lights the DRAM LED.
The usual culprits: a weak integrated memory controller (IMC), a motherboard that can't push four DIMMs at high speed, RAM slots populated in the wrong order, or an outdated BIOS that doesn't know how to talk to your kit. On AMD Ryzen 7000 series, anything above 6000 MT/s in a 1:1 ratio is often a losing battle.
Step 1: The 30-second fix — clear CMOS and back off
Your board is stuck mid-training. Kill the power completely — flip the PSU switch off, unplug it, then hold the case power button for 5 seconds to drain the caps. Now find the CMOS jumper or button on your board (check the manual; on most ASUS boards it's labeled CLRTC, on MSI it's JBAT1). Short it for 10 seconds, or pull the CR2032 coin cell for 30 seconds if you don't have a jumper.
Power back on. The board should POST at JEDEC defaults (2133/2400/4800 depending on DDR generation). If it does, you've confirmed the RAM itself is fine and the issue is purely the XMP profile.
Now — and this matters — before re-enabling XMP, drop to one stick. Pull all but the DIMM in slot A2 (the second slot from the CPU on most boards). One stick, one slot. Re-enable XMP. If it boots, add the second stick. If it fails with two, your IMC is the bottleneck, not the RAM.
I've seen a dozen builds where A1/B1 worked fine but A2/B2 failed, or vice versa. Slot order is real. Read your manual's recommended dual-channel layout, don't guess.
Step 2: The 5-minute fix — update BIOS and lower the speed one notch
If clearing CMOS got you into the BIOS but enabling XMP still fails, do two things.
Update the BIOS
Memory compatibility is the single biggest thing BIOS updates fix. A board shipped in 2021 with an early AGESA for Ryzen 5000 might not handle a 3600 CL16 kit that a 2023 BIOS handles without blinking. Grab the latest non-beta BIOS from your motherboard vendor's site. Use the vendor's flashback or EZ Flash tool, not Windows.
Drop the XMP speed one step
Don't disable XMP entirely. Instead, enable it, then manually set the DRAM frequency one or two notches below the profile. If your kit is 3600, try 3466 or 3200. Timings stay as XMP set them. Nine times out of ten, this boots instantly.
Also check two often-missed settings:
- DRAM voltage. Most XMP kits want 1.35V. Some boards default to 1.20V when you manually change frequency. Set it explicitly:
1.35Vfor DDR4,1.35Vor1.40Vfor DDR5. - SoC voltage (AMD only). For Ryzen, the SoC voltage feeds the memory controller. 1.10V is a safe starting point. Don't go above 1.15V unless you know exactly what you're doing — you can degrade the chip.
Step 3: The 15-minute fix — manual timing tune
Still fighting the DRAM light? Time to stop trusting the XMP profile and dial it in yourself. This is where people who "just want it to work" give up, and where the actual fix lives.
- Enable XMP, then manually set frequency to the highest stable value from Step 2 (say 3200).
- Loosen the primary timings by one or two cycles. If XMP says 16-18-18-38, try 18-20-20-40.
- Set Command Rate to 2T. It costs you maybe 1% performance and buys a ton of stability.
- Boot. Run MemTest86 from a USB stick for at least one full pass (about 30-60 minutes for 16GB).
- If it passes, tighten one timing at a time and retest. If it fails, back off.
On DDR5 with four DIMMs, expect to top out around 4800-5200 MT/s no matter what the sticks are rated for. That's a platform limit, not user error.
When to give up on XMP and just run JEDEC
Honestly? If you're at 3600 CL16 stock and can only stabilize 3200 CL16, the real-world difference in gaming is a few frames. I've benchmarked it. It's not worth a week of your life. Run stable JEDEC, move on, play games.
The one case worth pushing: a workstation or a build where you're rendering or compiling all day. There, 5% memory bandwidth matters. For everyone else, stability wins.
Quick reference
| Symptom | Likely cause | Fix |
|---|---|---|
| DRAM LED, no POST, restart loop | Failed memory training at XMP speed | Clear CMOS, back off frequency |
| Boots with 1 stick, fails with 2 | IMC can't handle dual-channel at that speed | Lower XMP frequency one step |
| Boots but BSODs under load | Voltage too low or timings too tight | Raise DRAM voltage to 1.35V, set 2T |
| Fails on 4 DIMMs, works on 2 | Four-rank load on memory controller | Run 2 sticks or drop to 4800 |
If you've cleared CMOS, updated BIOS, dropped to one stick, backed off frequency, and it still won't post? Then it's likely a dead IMC in the CPU or a bad DIMM. Swap the RAM into another machine and see. If it trains there, RMA the board or CPU — you've exhausted the software side.