RAM troubleshooting · 4 min read

ASUS TUF B650-PLUS WIFI: four DDR5 sticks will not boot

Restore an A2/B2 baseline, compare DDR5 modules at defaults and check kit population when adding RAM breaks startup or EXPO.

Adding a second DDR5 kit can change whether TUF GAMING B650-PLUS WIFI starts at the old EXPO setting. Return to default memory operation, verify the original pair in A2/B2, and test added modules before blaming the four slots.

Separate capacity detection from profile stability

This article covers the ATX TUF GAMING B650-PLUS WIFI. Note whether the failure began when adding modules or only after re-enabling EXPO. Also distinguish a completely blank startup from a machine that enters UEFI but reports less memory than expected.

Four occupied slots place a different load on the memory system from two modules. ASUS notes that supported memory frequency depends on the CPU, and its profile guidance recommends a qualified matched kit rather than mixed kits. Two separately purchased pairs with the same marketing name should not be assumed to be one validated four-module set.

Keep the complete part numbers and kit labels. Capacity and advertised speed alone are insufficient identifiers for a compatibility check.

Restore a known-working pair at default settings

If UEFI is accessible, return the memory tuning to Auto/default operation before testing. In ASUS's AM5 BIOS documentation, Ai Overclock Tuner distinguishes Auto from EXPO and DOCP profiles; the options shown depend on the memory and firmware.

If settings prevent any image, follow this exact board's CLRTC instructions to restore defaults. Disconnect mains power before using the header, and identify it from the manual. Preserve recovery keys and record known boot/storage settings before a firmware reset; do not clear the TPM as part of memory troubleshooting.

With the machine off and unplugged, reinstall the original matched pair in DIMM_A2 and DIMM_B2. The manual's single-module position is DIMM_A2. Confirm this baseline starts and shows the expected capacity before adding the other pair.

Compare modules without changing several variables

If the original pair works, test added modules individually in A2 at the same default settings. Shut down and unplug before each change. Record which module was installed, whether UEFI appeared and the detected capacity.

This makes the next branch clearer: one module failing the same test deserves individual investigation; every module working alone but failing as a four-module set points toward the combined configuration, compatibility or firmware. It does not prove that the unused slots are broken.

Allow memory initialization after configuration changes. Observe whether the DRAM Q-LED is a temporary startup stage or a persistent stop, rather than repeatedly resetting during initialization.

Check the QVL for the actual configuration

Review ASUS's memory support list for the exact kit and supported socket population, together with the installed CPU's memory requirements. Do not read a two-module test entry as a promise for four modules or reuse the old pair's profile as a guaranteed setting for the expanded system.

If four modules boot at defaults, verify the full capacity and run memory diagnostics before considering a profile. Prefer a stable supported configuration over preserving an advertised transfer rate at any cost. Avoid trial-and-error voltage increases.

Recheck after a justified BIOS update

If release notes identify a relevant memory-compatibility change, update only using this model's official procedure and a stable configuration. Then repeat the default-setting baseline before restoring tuning.

For a persistent problem, send support the CPU, BIOS, exact kit identities, module-count history and comparison results. A report that says “the original pair works in A2/B2 at defaults; four modules do not” is substantially more actionable than “DDR5 is broken.”

Original sources

Check the exact model, PCB revision and current manufacturer instructions before acting.

Source-linked editorial guide · Reviewed 2026-10-29 · Not hardware-tested

How this guide was prepared · Report a correction