Quick answer

Your DDR5 kit runs at its JEDEC default until you load the memory profile in UEFI, usually 4800 MT/s at a lower voltage. Enable XMP or EXPO in the board’s tweaker menu, save, then verify the reported speed and run a memory test before you trust it with data.

Contents

At a glance

Class
Tutorial

Provenance

  • Nov 16, 2026Published

You paid for 6000 MT/s and your machine is running at 4800. Nothing is broken. The kit is sitting on its JEDEC default speed, which is the safe configuration every board can boot, and the rated number on the box is an overclock profile the module vendor validated and stored in the DIMM’s SPD chip. Corsair publishes both numbers side by side for its Vengeance 6000 CL30 kit: 4800MHz at CL40 and 1.1V by default, 6000 MT/s at CL30 and 1.40V on the tested profile. G.Skill lists the same split.

Turning the profile on takes about ninety seconds in UEFI. Proving the machine is actually stable at that speed takes longer, and it is the half of the job most people skip. Here is the full sequence, including what to do when the board refuses to boot.

1. Why your DDR5 kit boots at JEDEC speed

A DDR5 module carries two sets of numbers. The SPD default is what the memory presents to any board with no configuration: a conservative speed, loose timings and 1.1V. The overclock profile is what the vendor tested and certified, and both Intel XMP and AMD EXPO are just standardized containers for it. ASUS describes the job plainly on its support page: the board loads the preset overclock file and DRAM timing from the memory SPD chip.

SpecificationCorsair Vengeance CMK32GX5M2B6000Z30G.Skill Flare X5 F5-6000J3038F16GX2-FX5
Default (SPD) speed4800MHz4800 MT/s
Default SPD latencyCL40not published as a CL value
Default SPD voltage1.1V1.10V
Tested profile speed6000 MT/s6000 MT/s
Tested profile timingsCL3030-38-38-96
Tested profile voltage1.40V1.35V
Profile standardAMD EXPO and Intel XMPIntel XMP 3.0 and AMD EXPO

Those two kits are not slow hardware. They are hardware waiting for a setting. AMD’s EXPO page describes the profiles as a way to get easy DDR5 overclocking on socket AM5 with Ryzen-optimized settings, which is the same bargain Intel’s XMP makes on its platforms: one menu choice instead of hand-entering timings.

One caution belongs up front, because AMD is explicit about it. AMD’s own footnotes state that overclocking processors and memory outside AMD’s published specifications, including altering memory timing or voltage, will void any applicable AMD product warranty, even when it is enabled through AMD hardware or software. Enabling EXPO is that kind of change. If the machine has to stay inside a support contract, that is a decision to make deliberately.

2. Step 1: Confirm the rated profile and the slot pair

Before you open UEFI, establish three facts.

The exact kit. Read the part number from the module label or from the memory details in Windows, then look it up on the vendor’s own specification page. You want the tested speed, the tested primary timings and the tested voltage. If the page lists only an Intel XMP 3.0 profile and your board is AM5, the board may still accept it as DOCP, but you are now outside the kit’s documented path.

Whether the pair is a matched kit. G.Skill’s specification page for the Flare X5 states it directly: do not mix memory kits, because kits are sold as matched sets designed to run together. Two separately purchased pairs are not the same thing as one four-module kit, even when the part numbers match.

The slot pair. ASUS’s failure checklist starts with using modules from its qualified vendors list, keeping a kit together rather than mixing modules, and testing a single module in the recommended slot. That is the practical version of the rule: two DIMMs in the pair your manual calls out, not two in whichever slots were easiest to reach. The DDR5 buying guide covers why pairs behave this way, and the live RAM price index is the place to check kit pricing before buying a second pair you do not need.

AMD also publishes a tested-memory list that flags each kit as EXPO-certified, certified with Ultra Low Latency, or merely XMP-compatible. Worth checking when a profile keeps failing.

3. Step 2: Load XMP or EXPO in UEFI

The menu sequence below is ASUS’s documented path, because that is the vendor documentation I can point you at line by line. On MSI, Gigabyte and ASRock boards the same toggle lives in that vendor’s overclocking or tweaker section under its own label, so follow your board manual rather than assuming the ASUS wording appears on your screen.

  1. Restart the machine and tap Del or F2 during POST to enter BIOS setup. Most boards land in an EZ Mode summary screen.
  2. Press F7 to switch to Advanced Mode. If the board boots straight into Advanced Mode, skip this.
  3. Open the Ai Tweaker page. Some ROG boards label this tab Extreme Tweaker.
  4. Select Ai Overclock Tuner. On an Intel 600-series or newer board with an XMP kit, choose XMP I or XMP II. On an AMD AM5 board with an EXPO kit, choose EXPO I or EXPO II. On an AMD board with an XMP kit, ASUS uses DOCP to apply the XMP timings.
  5. Press F10 and confirm to save and exit. The board reboots on its own.

Two checks are worth making before you leave UEFI. The EZ Mode memory information panel shows the DRAM frequency the board intends to run, and Tool → SPD Information shows whether the installed module reports an XMP profile or an EXPO profile at all. A kit with no visible profile is a kit that will not accept one.

What changes after the reboot: the board retrains memory against the new timings. That first POST after enabling a profile routinely takes longer than a normal boot, sometimes with a dark screen or a pause on the memory LED, and cutting power during that window is how people turn a two-minute setting into a CMOS clear. Let it finish. Once Windows loads, open Task Manager, go to Performance → Memory, and read the Speed figure. ASUS documents exactly this check. If it says 6000 MT/s, the profile is live; if it still says 4800, the profile did not take, and the next section is for you.

4. Step 3: Recover a failed boot without guessing

A board that cannot train the profile generally does not sit there blinking at you forever; most fall back to defaults and boot. Do not read a successful desktop as proof the profile applied. Check the speed.

If the machine genuinely will not come back, clear CMOS. ASUS documents three methods on its boards, and the same three exist in some form on every consumer board:

MethodWhat you doNotes
Clear CMOS buttonPower off, unplug the cord, hold the button about 5-10 secondsPresent on many mid-range and high-end boards
CLRTC pinsPower off, unplug, short the two pins about 5-10 seconds with a jumper cap or metal objectMost common on boards without a button
CMOS batteryPower off, unplug, remove the battery, then clear with the pin or buttonNeeded when the other two are inaccessible

After restoring power, the board announces that BIOS settings were reset. Press F1 to enter setup, F5 to load optimized defaults, F10 to save and exit. Your fan curves, boot order and memory profile are all gone at that point, so plan to set them again.

If the board posts but stays at JEDEC speed after you enabled the profile, work the list in order: confirm the two DIMMs are in the recommended pair, pull one module and try again, check whether the profile is one the kit actually carries, and look at the firmware version. An older BIOS with a stale memory-training routine is a real cause of profiles that refuse to train, and our BIOS update walkthrough covers how to flash one safely. If the machine never reaches the point of training memory at all, the no-power checklist and the diagnostic workbench separate a memory problem from a power or board problem.

5. Step 4: Prove the profile is stable

A machine that boots and games for an hour is not the same as a machine that stores data correctly. HCI Design’s MemTest manual is blunt about the consequence: an unstable system gets worse over time as corrupted data is written to the hard disk. That is the failure mode worth spending an afternoon to avoid, because it looks like a filesystem problem or a bad game install long before it looks like memory.

Two tools do the job, and I use them for different stages.

MemTest86, booted from USB, is the check that counts. PassMark’s technical documentation lists DDR5 SPD reporting, including kits that carry Intel XMP 3.0 or AMD EXPO profiles, plus per-module error tracking and a running count of uncorrected and corrected errors. Because it runs before any operating system, nothing else is occupying the memory it is testing. I start it, leave it overnight, and treat any error as a failed profile. There is no pass count that turns a reported error into an acceptable one.

HCI MemTest, run inside Windows, is the faster sanity check. Its manual gives concrete numbers: 100 percent coverage is a very thorough test that catches all but the most intermittent problems, running to 400 percent is what catches the rare ones, and 60 percent of bad RAM is detected after just 10 percent coverage. On a multi-core machine it recommends one instance per core with the RAM divided between them. I use it when I want a quick answer before committing to an overnight run.

Alongside the memory test, check the two places Windows reports what actually happened:

  • Task Manager → Performance → Memory → Speed should show the rated figure, not 4800.
  • Event Viewer → Windows Logs → System, scanned for new WHEA entries after a test run. Microsoft describes WHEA as the architecture Windows uses for hardware error reporting and recovery, so a fresh WHEA entry during a stress run is a signal that something in the platform, not just the memory test, objected.

A profile that passes an overnight bootable run, shows the rated speed in Windows, and logs no new hardware errors is a profile I will leave enabled. A profile that passes only the quick test gets re-run overnight before I trust it.

6. XMP and EXPO are not manual tuning

The profile is a starting point the module vendor validated, and it changes a defined set of values: the data rate, the primary timings, and the voltage. On the Corsair kit in the table, that is 1.40V against a 1.1V default; on the G.Skill kit, 1.35V against 1.10V. Everything the profile sets, the vendor tested as a combination.

Manual tuning is a different activity. You set the voltage yourself, you change the primary timings yourself, and you take on the secondary and tertiary timings and the refresh interval, which the profile leaves to the board’s training. That is where enthusiasts find the last few percent, and it is also where a machine that passes a short test starts corrupting files a month later. Motherboard “try it” presets are not the same thing, because nobody certified them against your specific modules.

My rule: enable the profile, prove it, and stop there. Manual tuning only makes sense against a specific problem you can measure, and it needs a longer stability proof than the profile does.

7. When to leave the profile at JEDEC

Some machines are better off at the default speed, and I would rather say so than pretend every kit should be overclocked.

  • Four modules or a mixed set. Matching the kit matters more than the headline speed. If you need the capacity, buy one larger matched pair instead of adding a second pair.
  • A profile that fails a bootable memory test. The gap between 4800 and 6000 is worth less than the files a corrupted write can destroy.
  • A compact build with no airflow over the DIMMs. Voltage headroom and module temperature are related, and a sealed small-form-factor case is not the place to discover that.
  • A machine under a support contract. AMD’s own warranty language treats memory overclocking as outside its published specifications. That decision is yours, not the profile’s.

For everyone else, the sequence is the same: enable the profile, confirm the speed in Task Manager, run the bootable test until it has earned your trust, and check again after every BIOS update, because a flash puts the kit straight back on its default. If you are still choosing a kit, the DDR5-6000 CL30 explainer covers why that speed and timing combination became the AM5 default recommendation, and the PC Builder will check the kit against the rest of a parts list.

Frequently asked questions

Why is my RAM still at 4800 MT/s after I enabled XMP or EXPO?
Check three things in order. First, confirm the profile actually saved: reboot into UEFI and look at the memory frequency on the main screen, then check Task Manager under Performance and Memory for the speed Windows reports. Second, confirm the two DIMMs are in the slot pair your board manual recommends, because a single module or the second-best slots can fail memory training. Third, check that the kit’s rated profile is one your board and CPU support, since a profile the platform cannot train will fall back to defaults instead of failing loudly.
Is XMP the same thing as EXPO?
They are two names for the same idea from different vendors. Intel XMP is the Extreme Memory Profile standard, and AMD describes EXPO as AMD Extended Profiles for Overclocking, developed for user-friendly memory overclocking of DDR5 on socket AM5 with Ryzen-optimized profiles. Many DDR5 kits ship with both an Intel XMP 3.0 profile and an AMD EXPO profile, and the board decides which one to load.
What happens if the PC will not boot after enabling the memory profile?
Clear CMOS. ASUS documents three methods on its motherboards: a Clear CMOS button held for about five to ten seconds with the power cord removed, shorting the two CLRTC pins with a jumper cap or metal object for the same time, or removing the CMOS battery. After you restore power, the board prompts that settings were reset; press F1 to enter BIOS, F5 to load optimized defaults, and F10 to save and exit.
Does enabling XMP or EXPO void my warranty?
AMD’s own footnotes say overclocking processors and memory outside AMD published specifications, including altering memory timing or voltage, will void any applicable AMD product warranty, even when enabled through AMD hardware or software. That is the vendor’s stated position for EXPO, which is a memory overclock rather than a JEDEC default. For other brands and for prebuilt systems, read the warranty terms supplied with the board and the machine.
How long should I test memory after enabling the profile?
HCI Design’s MemTest manual calls 100 percent coverage a very thorough test that catches all but the most intermittent problems, and recommends running to 400 percent coverage to catch those rarer errors. It also notes that 60 percent of bad RAM is detected after just 10 percent coverage, so a short run is better than nothing but not a clean bill of health. I run a bootable MemTest86 session overnight instead of watching a progress bar.
Do I use XMP I or XMP II?
ASUS lists both as selectable values for the Ai Overclock Tuner setting on Intel boards, alongside XMP Tweaked, and its own walkthrough uses XMP I for an XMP kit. Treat the numbered variants as vendor-defined profile slots rather than as a stability ladder, pick the one your board manual describes for a first enable, and validate the result with a memory test either way.
Does a BIOS update turn the profile back off?
Yes. Flashing firmware resets stored setup values, so the memory profile, fan curves and boot order return to defaults and the kit comes back up at its SPD speed. Re-enable XMP or EXPO after the flash finishes, then re-run your stability check; a profile that passed on one firmware revision is not automatically validated on the next.
Can I run XMP or EXPO with four sticks installed?
Four modules are harder to train than two, and a kit is validated as the matched pair it was sold as. G.Skill warns against mixing memory kits, and ASUS recommends using its qualified vendors list and matched kits rather than mixed modules when a profile fails. If you need more capacity, buy a single larger matched pair rather than adding a second pair to the first.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 9 cited sources, listed below, each checked against the original page on the date above. BIOS paths, the Task Manager speed check, the SPD Information check and the three CMOS-clear methods come from ASUS support articles read on November 16, 2026. Rated-versus-default memory figures come from the Corsair and G.Skill specification pages for the two kits named in the table, and AMD EXPO wording including the warranty footnote comes from AMD’s own EXPO page. Stability testing guidance comes from HCI Design’s MemTest manual and PassMark’s MemTest86 technical documentation. Vendor menus differ; only the ASUS path is reproduced as a specific menu sequence, and every other board is described generically on purpose.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.