While primary timings like CAS Latency (tCL) dominate product marketing, they only tell a fraction of the performance story. The real key to maximizing frame pacing, eliminating micro-stutter, and achieving the lowest possible system latency lies in the secondary and tertiary timings. Because DDR5 architecture utilizes dual 32-bit subchannels per module, the memory controller must manage a complex web of concurrent read and write operations. Leaving these settings on “Auto” forces motherboards to apply ultra-conservative safety margins, leaving significant gaming performance on the table.

To achieve the best ddr5 subtimings for low latency gaming, we must prioritize settings that reduce the idle time of the memory cells. By minimizing the time the memory controller waits between row activations, refreshes, and read/write handshakes, you directly reduce the time your CPU spends waiting for assets. In the 2026 hardware landscape, where modern game engines stream massive open-world assets dynamically, this optimization translates directly to vastly improved 1% low frame rates and a much smoother gaming experience.

The table below outlines the sweet-spot targets for high-quality DDR5 kits (specifically those using SK Hynix M-die or A-die silicon). These values represent the ideal balance between aggressive latency reduction and system stability.

Setting (BIOS Label) Recommended Value Why It Matters for Gaming
tREFI (Refresh Interval) 65,535 to 262,143 Delays the forced cell refresh cycle, allowing the RAM to accept read/write commands for longer stretches without interruption.
tRFC / tRFC2 (Refresh Cycle Time) 380 / 300 (A-die) | 480 / 380 (M-die) Controls how long a module must recover after a refresh. Lower numbers drastically reduce latency spikes.
tFAW (Four Activate Window) 16 Restricts how closely four separate row activations can occur. Lowering this to the absolute minimum of 16 maximizes burst command efficiency.
tRRD_S (Row-to-Row Delay Short) 4 Sets the minimum delay between activating rows in different bank groups. Essential for fast texture streaming.
tRRD_L (Row-to-Row Delay Long) 8 Sets the delay between activating rows within the same bank group. Must be paired tightly with tRRD_S.
tWR (Write Recovery Time) 48 (or 12-16 if using Link) The time required for data to write from the internal latch to the memory cells before a precharge command.
tWTR_S (Write-to-Read Delay Short) 4 Minimizes the delay when switching from a write operation to a read operation in different bank groups.
tWTR_L (Write-to-Read Delay Long) 12 to 16 Controls the write-to-read transition delay within the same bank group. Directly impacts memory turnaround speeds.

Setting-by-Setting

tREFI (Refresh Interval)

Exact Value: 65,535 (Safe/All-around) to 262,143 (Enthusiast/Max performance).

The Trade-off: This is the single most impactful subtiming for gaming latency. Normally, DRAM cells must be refreshed regularly to prevent data loss, during which the RAM cannot process CPU requests. Raising tREFI keeps the memory open for business longer. The trade-off is extreme thermal sensitivity. At higher tREFI values, if your memory modules exceed 55°C to 60°C under load, the cells will lose charge before the next refresh cycle occurs, resulting in silent data corruption, game crashes, or blue screens. Active cooling (a dedicated fan over the RAM) is highly recommended for values above 65,535.

tRFC / tRFC2 / tRFCpb (Refresh Cycle Time)

Exact Value: tRFC1: 380–480 cycles; tRFC2: 300–380 cycles; tRFCpb: 240–300 cycles.

The Trade-off: While tREFI dictates how often the RAM refreshes, tRFC determines how long each refresh cycle takes. Lowering these values allows the memory cells to recover and return to an active state much faster. The main trade-off is cold-boot stability. A system that passes stress tests when warm may fail to boot from a cold start if tRFC is set too low, as the silicon requires slightly longer recovery times at lower ambient temperatures.

tRRD_S / tRRD_L and tFAW (The Activation Trio)

Exact Value: tRRD_S = 4, tRRD_L = 8, tFAW = 16.

The Trade-off: This trio governs how quickly the memory controller can open new rows in the RAM banks. For optimal efficiency, tFAW must always be set to exactly four times the value of tRRD_S (4 x 4 = 16). Tightening these values to 4-8-16 forces the memory controller to pipeline activations at maximum speed. The trade-off is an increase in power consumption and thermal output from both the DRAM modules and the CPU’s integrated memory controller (IMC).

tWTR_S and tWTR_L (Write-to-Read Delays)

Exact Value: tWTR_S = 4, tWTR_L = 12 (or 16 depending on memory controller quality).

The Trade-off: These values control the dead-time required when the memory controller switches from writing data to reading data. Lowering these timings minimizes the latency penalty during complex game engine operations that constantly swap between reading geometry data and writing frame buffers. The trade-off is high stress on the CPU’s silicon; pushing tWTR too low requires higher System Agent (VCCSA) or VDDIO voltages to maintain stability, which can degrade the CPU over time if pushed past safe limits.

By Hardware Tier

Low-Tier: Micron & Samsung Die Kits (5600 to 6000 MT/s)

Entry-level DDR5 kits, particularly those using Micron A-die or older Samsung B-die, do not scale well with voltage and feature highly sensitive silicon. For these kits, your priority is moderate latency reduction without triggering thermal instability. Set tREFI to a safe 32,768 to prevent thermal runaway. Lower tRFC to 480 (Samsung) or 520 (Micron). Keep the activation trio at tRRD_S = 4, tRRD_L = 8, and tFAW = 24. These settings provide a noticeable reduction in micro-stutters without requiring active cooling or voltages exceeding 1.35V VDD.

Mid-Tier: SK Hynix M-Die Kits (6000 to 6800 MT/s)

SK Hynix M-die is the sweet spot for the vast majority of gaming rigs. It handles voltage scaling beautifully and can easily tolerate tighter timings. Set your DRAM VDD and VDDQ voltages to 1.40V. Program tREFI to 65,535 and drop tRFC1 to 420 (tRFC2 to 320). Tighten the activation trio to the absolute minimums of tRRD_S = 4, tRRD_L = 8, and tFAW = 16. Lower tWTR_S to 4 and tWTR_L to 12. This configuration drops overall latency from a loose stock average of ~75ns down to a crisp ~58ns, greatly smoothing out frame delivery in competitive shooters.

High-Tier: SK Hynix A-Die & 24Gb M-Die (7200 to 8400+ MT/s)

This tier represents enthusiast-grade hardware, typically paired with high-end motherboards featuring 2-DIMM memory layouts optimized for extreme signaling. Push DRAM VDD to 1.45V–1.48V (with active cooling). Maximize tREFI to 131,072 or 262,143. Drop tRFC1 to 380 and tRFC2 to 300. Lock the activation trio at 4-8-16. Tighten tWR to 48 (or 12 if utilizing the tWR_LNK option in advanced BIOS menus). These settings require high-quality motherboard VRMs and an exceptionally strong CPU memory controller, but they unlock the absolute lowest possible latency floor (sub-50ns) for high-refresh-rate gaming.

Common Mistakes

Mistake 1: Thermal Runaway and tREFI Instability

  • What causes it: Setting a high tREFI value (such as 262,143) while feeding the RAM high VDD voltage (>1.43V). As the system runs intensive games, heat from the graphics card rises directly into the RAM slots, pushing RAM temperatures past 55°C. At this temperature, the physical capacitors in the RAM lose charge faster than the extended refresh window allows, leading to memory corruption.
  • How to check: Download HWiNFO64 and run a dedicated memory stress test like TestMem5 (using the “extreme@anta777” profile) or y-cruncher (VT3 test). Monitor the “DRAM Temperature” sensors. If you see errors pop up only after the RAM exceeds 52°C, your tREFI is too high for your cooling solution.
  • What to do: Either install a dedicated 120mm fan blowing directly onto your RAM modules, or enter your BIOS and lower your tREFI to a safer value like 65,535 or 32,768.
  • How to undo: Restart your PC, press Delete or F2 repeatedly to enter the BIOS. Navigate to the memory configuration page (e.g., Extreme Tweaker on ASUS or OC Tweaker on ASRock), select tREFI, and change it back to Auto. Save and exit (F10).

Mistake 2: Leaving tFAW Unlocked While Tuning tRRD_S

  • What causes it: Manually tightening tRRD_S to 4 but leaving tFAW on Auto. The motherboard BIOS will often default tFAW to a safe value of 32 or 48. This mismatch completely neutralizes the latency benefits of your manual tRRD_S setting because the memory controller is forced to wait for the larger tFAW window to clear anyway.
  • How to check: Open ZenTimings (for AMD Ryzen systems) or Asrock Timing Configurator (for Intel systems) inside Windows. Look at the values for tRRD_S and tFAW. If tFAW is not exactly four times the value of tRRD_S (e.g., if tRRD_S is 4 and tFAW is 32), your configuration is unoptimized.
  • What to do: Restart your PC, enter the BIOS, and navigate to the DRAM Timing Control menu. Locate tFAW and manually input 16. Ensure tRRD_S is set to 4 and tRRD_L is set to 8.
  • How to undo: Enter the BIOS, navigate back to the DRAM Timing Control menu, highlight tFAW, tRRD_S, and tRRD_L, press the Spacebar or type 0 to set them back to Auto, then save and restart.

Mistake 3: Insufficient System Agent and Memory Controller Voltages

  • What causes it: Tightening secondary timings like tWTR_S and tWTR_L to aggressive values (4 and 12) without providing enough electrical pressure to the CPU’s Integrated Memory Controller (IMC). The system may boot to the desktop but crash instantly when a heavy 3D game engine initializes.
  • How to check: Check Windows Event Viewer (press Win + X, select Event Viewer). Expand Windows Logs, click on System, and look for “WHEA-Logger” warnings or application crash logs displaying error code 0xc0000005 (Access Violation).
  • What to do: Enter your BIOS and locate your CPU voltage controls. For Intel CPUs, locate CPU VCCSA Voltage and set it to a manual override of 1.20V to 1.25V. For AMD CPUs, locate CPU VDDIO_MC Voltage and set it to 1.30V, and ensure VDD_SOC is set to 1.20V (do not exceed 1.30V SOC on AM5).
  • How to undo: Enter your BIOS, navigate to the voltage configuration menu, highlight the adjusted VCCSA, VDDIO_MC, or SOC voltage settings, and type Auto to restore default motherboard voltage management.

FAQ

Do subtimings actually increase FPS in games?

Yes, but not in the way most users expect. Tuning subtimings rarely boosts your maximum or average FPS by massive margins. Instead, it targets the “1% low” and “0.1% low” frame rates. By reducing memory latency, you prevent the CPU from stalling when loading new assets, which eliminates micro-stutters. This results in a much smoother, more consistent visual experience, particularly in fast-paced multiplayer shooters or open-world games with rapid camera movements.

Is it safe to run high tREFI values without active cooling?

No. High tREFI values (above 65,535) force the RAM to wait longer between refresh cycles. If the temperature of the physical memory chips exceeds 50°C to 55°C, the electrical charges holding your data will begin to decay before the next refresh cycle occurs. This leads to silent data corruption, which can ruin operating system files and cause sudden game crashes. If you do not have a fan blowing directly over your RAM, keep tREFI at or below 65,535.

Why does my PC take so long to boot after changing subtimings?

When you change memory timings, the motherboard’s BIOS must run through a process called “Memory Training” upon the next boot. During this time, the motherboard sends test signals through the RAM channels to find the optimal electrical alignments for your new settings. To speed up subsequent boots, look for settings named Memory Context Restore (on AMD) or Fast Boot / Fast Training (on Intel) in your BIOS and enable them. This allows the motherboard to save and reuse the successful training profile rather than retraining on every cold boot.

Which is better for low latency: higher MT/s or tighter subtimings?

For gaming, a balance of both is required, but low latency is heavily dictated by the controller mode. On AMD Ryzen platforms, you must keep the memory clock (UCLK) in a 1:1 ratio with the memory controller clock (MCLK), which typically tops out at 6000 to 6200 MT/s. Going higher forces a 1:2 ratio, which introduces a massive latency penalty. On Intel platforms, you can run higher speeds (7200+ MT/s in Gear 2 mode), but you must pair those high speeds with tight subtimings to offset the inherent latency penalty of Gear 2 signaling.

Related guides