CAS latency is the number buried in your RAM’s spec that tells you how many clock cycles the memory waits before it hands over data. It’s the “CL” in a spec like CL18-22-22-42, and it matters because two kits at the same speed can feel different depending on those timings. Maybe you’re checking whether your sticks are running their rated latency, maybe you’re comparing kits before an upgrade, or maybe a benchmark looked off and you want the real numbers. Either way, you don’t need to open the case. Windows and a couple of free utilities will read the exact CAS latency your memory is running right now, and this walkthrough shows every step. If you’re shopping while you’re at it, our gaming RAM guide and DDR5 breakdown list current picks.
What you’ll need
Not much. A Windows PC, a few minutes, and one free utility. CPU-Z is the go-to, and it’s what we’ll lean on because it reads timings straight off the memory’s SPD chip. Task Manager and the built-in msinfo tool cover the basics, but they won’t show CAS latency directly, so CPU-Z fills the gap. That’s the whole kit. No screwdriver, no BIOS dive unless you want to change settings later. If you’re eyeing a memory upgrade rather than just checking, a labeled kit like the G.SKILL Ripjaws V DDR4 32GB (2x16GB) 3600 spells its timings right on the spec, CL18-22-22-42 at 1.35V, which is handy for comparison.
Pros
- DDR4-3600 XMP at 1.35V is the Ryzen AM4 sweet spot, aligning FCLK 1:1 at 1800MHz for best latency.
- Matched 2x16GB kit is factory-tested as a pair, reducing dual-channel instability compared to mixing sticks.
- Compatible with both Intel XMP and AMD DOCP/A-XMP BIOS profiles without manual sub-timing adjustments.
- Ships with JEDEC SPD fallback so the system always boots safe at default clocks before XMP is enabled.
Cons
- CL18 primary latency is mid-range; DDR4-3600 CL16 kits exist for buyers prioritizing tighter timings.
- No ECC support, so workstation or Threadripper ECC builds need a different kit entirely.
The G.SKILL RipjawsV F4-3600C18D-32GVK is a mid-range DDR4 desktop kit targeting Intel and AMD mainstream platform builders who want 32GB capacity at DDR4-3600 without overpaying for CL14 or CL16 enthusiast kits. It ships as a matched 2x16GB dual-channel pair in the standard 288-pin U-DIMM form factor.
The defining spec here is the XMP profile: DDR4-3600 at CL18-22-22-42, 1.35V. On AMD AM4 Ryzen systems, 3600MHz is the well-documented sweet spot for achieving a 1:1 FCLK ratio at 1800MHz, which keeps infinity fabric latency in check and translates to measurable gains in lightly-threaded workloads and gaming frame times compared to DDR4-3200 or lower.
CL18 is a genuine trade-off at this speed. Competing DDR4-3600 kits with CL16 or CL14 exist and offer lower absolute latency, though they typically carry a price premium. Owners report stable XMP operation across a wide range of B450, X570, and Z490/Z590 boards, but reaching rated speed on some budget AM4 boards may require manual sub-timing adjustments or AGESA microcode updates.
Buy this if you are building or upgrading an AM4 Ryzen or Intel LGA1700 desktop and want reliable 32GB DDR4-3600 dual-channel performance without tuning. Skip this if you need CL16 or tighter for competitive latency, or if your board has a limited QVL and you have not verified compatibility via G.SKILL's configurator tool first.
Platform Support: This kit uses 288-pin DDR4 U-DIMM and is compatible with Intel LGA1700 (Z690/Z790) and AMD AM4 (B450/X470/B550/X570) platforms. AM5 uses DDR5 exclusively, so this kit is not compatible with Ryzen 7000/9000 series builds on AM5 boards.
XMP and DOCP Activation: Rated speed of DDR4-3600 CL18-22-22-42 at 1.35V requires enabling XMP (Intel) or DOCP/A-XMP (AMD) in BIOS. Default JEDEC SPD boots at DDR4-2133 or DDR4-2400. On AM4, DDR4-3600 aligns FCLK at 1800MHz for a 1:1 ratio, which is the recommended operating point for Ryzen 3000 and 5000 series CPUs.
Slot Population and Mixing: Install both sticks in the recommended dual-channel slots per your motherboard manual, typically A2 and B2 in a 4-slot board. G.SKILL explicitly warns against mixing this kit with other modules; doing so voids the matched-pair guarantee and risks instability at XMP speeds.
Cooler Clearance: Exact heatspreader height is not specified in the source data, but RipjawsV modules are noted for a lower profile than Trident Z or RGB variants, reducing conflicts with wide tower coolers. Verify clearance if using a low-clearance cooler on a tight ITX board.
Step 1: Confirm your RAM speed and channel in Task Manager
Start with what Windows already knows. Right-click the taskbar, open Task Manager, click Performance, then Memory. You’ll see your total capacity, the speed in MT/s, the form factor, and how many slots are used. This won’t show CAS latency, but it sets the stage. Note the speed, because latency only makes sense next to it. A CL18 kit at 3600 MT/s behaves very differently from CL18 at 2400.
Check that the reported speed matches what you paid for. If you bought a 3600 MT/s kit and Windows says 2133 or 2400, your memory is running at its default JEDEC speed, not its rated profile, and its real timings won’t match the box. That’s a flag to enable XMP or EXPO later. For now, just record the speed and move on to read the actual timings.
While you’re on this screen, note the “Slots used” line too. If you’ve got a dual-channel kit but only one slot shows populated, or the sticks are in the wrong slot pair, you’re losing bandwidth before latency even enters the picture. Most boards want matched sticks in slots A2 and B2, usually the second and fourth from the CPU, to run dual-channel. Task Manager won’t spell out channel mode directly, but the slot count plus your motherboard manual tells you whether the kit is seated right. Fix that first if it’s wrong, because no timing tweak matters if half your memory bandwidth is missing.
Step 2: Download and open CPU-Z
Grab CPU-Z from the official CPUID site, install it, and launch it. It’s a tiny, free utility that’s been the enthusiast standard for reading hardware detail for years. When it opens, it’ll land on the CPU tab. Don’t worry about that yet. The information you want lives two tabs over, and CPU-Z reads it live from the hardware, so the numbers reflect exactly how your system is configured this second.
If Windows Defender or your browser warns on the download, that’s normal for low-level hardware tools; just use the official source rather than a mirror. Once it’s running, you’re 30 seconds from your answer. CPU-Z doesn’t change any settings, it only reads, so there’s nothing to break here.
Step 3: Read CAS latency on the Memory tab
Click the Memory tab. Look for the Timings section. The first value, labeled “CAS# Latency (CL),” is your CAS latency. Next to it you’ll see RAS to CAS Delay (tRCD), RAS Precharge (tRP), and Cycle Time (tRAS). Those four numbers are the timing string you see on a spec sheet. If CPU-Z shows CL 18, tRCD 22, tRP 22, tRAS 42, that’s the same CL18-22-22-42 printed on a kit like the G.SKILL Ripjaws V above.
One catch trips people up. The Memory tab shows the current running frequency under “DRAM Frequency,” and for DDR memory you double it to get the rated speed. So 1800 MHz here means 3600 MT/s. Make sure the CAS latency you’re reading lines up with the speed you expect. If the frequency is low and the CL looks tight, your kit is probably running a fallback JEDEC profile rather than its rated one.
It helps to know what the CAS number actually measures. CAS latency is the delay, in clock cycles, between the memory controller asking for a column of data and the RAM delivering it. Lower is quicker, but cycles aren’t time on their own. To get the real latency in nanoseconds, you divide the CL by the clock speed and multiply. A CL16 kit at 3200 MT/s and a CL18 kit at 3600 MT/s land at almost the same true latency, roughly 10 nanoseconds, because the faster clock offsets the higher cycle count. That’s why comparing CAS numbers across different speeds is meaningless unless you do the math. Reading the raw CL is step one; understanding it next to the frequency is what makes the number useful.
Step 4: Cross-check the rated timings on the SPD tab
Now click the SPD tab. This reads the memory module’s onboard SPD chip, which stores the JEDEC fallback profiles and the XMP or EXPO profile the manufacturer programmed. Pick a slot from the dropdown, and you’ll see the part number, the manufacturer, and a table of timings for each supported speed. This is where you confirm what your RAM is capable of, versus what Step 3 showed it actually running.
Compare the two. If the SPD tab lists an XMP profile of CL18 at 3600, but the Memory tab showed CL16 at 2400, your XMP profile isn’t enabled and you’re leaving performance on the table. The SPD tab tells you the rated numbers; the Memory tab tells you the live numbers. When they match, your kit is running as intended. When they don’t, that’s your cue for Step 5.
Step 5: Enable XMP or EXPO if the timings are wrong
If your live timings don’t match the rated profile, the fix is in the BIOS. Reboot, tap Delete or F2 to enter BIOS, and look for XMP (Intel) or EXPO (AMD) in the memory or overclocking section. Select the rated profile, save, and exit. On boot, the system applies the manufacturer’s speed and timings automatically. It’s a one-toggle change for most boards, not manual tuning.
Reopen CPU-Z after the reboot and recheck the Memory tab. The DRAM frequency should now reflect the rated speed, and the CAS latency should match the SPD profile. If the system won’t post after enabling XMP, clear CMOS and try again, and confirm your kit is on the motherboard’s memory compatibility list. A stable XMP profile is the difference between paying for fast RAM and actually using it. For upgrade options, our budget RAM guide covers kits with clean profiles.
If you want to verify stability after enabling the profile, run a memory stress utility like MemTest86 from a USB stick, or the Windows Memory Diagnostic, for a pass or two. An unstable XMP profile can throw errors that corrupt files quietly rather than crashing outright, so a clean pass is worth the 20 minutes. Should errors show up, you don’t have to abandon the rated speed entirely. Many boards let you loosen a timing or two, or bump the memory voltage slightly within the kit’s rated range, to reach stability while keeping most of the speed. That’s the last mile of getting your rated CAS latency to actually stick.
Troubleshooting common issues
CPU-Z shows a lower speed than my kit is rated for
That means your memory is running its default JEDEC profile, not XMP or EXPO. Enter the BIOS and enable the rated profile as described in Step 5. Until you do, both the speed and the CAS latency will read lower than the box promised, because JEDEC fallback timings are conservative.
The Memory tab frequency looks half of what I expected
That’s normal. CPU-Z reports the real clock, and DDR (double data rate) memory transfers twice per cycle. So 1800 MHz on the Memory tab equals 3600 MT/s on the spec sheet. Double the number you see and it’ll match the rating. Nothing is wrong with your RAM.
The SPD tab is blank for some slots
Empty slots show no data, so a blank entry usually just means nothing is installed there. Cycle through the slot dropdown to find your populated sticks. If a slot you know is filled reads blank, reseat the module, since a poorly seated stick can fail to report its SPD data even while the system boots on the others.
My two kits show different timings
Mixing kits can force the motherboard to run the slower or looser timings across all sticks for stability, and it can prevent a clean XMP profile entirely. Check each slot on the SPD tab. If the profiles differ, the safest path is a single matched kit bought together, which is why buying one 2x16GB kit beats stacking two 1x16GB sticks.
The timings look right but performance still feels off
CAS latency is only one piece. If your CL and speed match the rating but the system feels sluggish, check that both channels are populated and that the sticks sit in the correct slot pair for dual-channel. Single-channel memory halves bandwidth regardless of how tight the timings are. Also confirm no background app is eating RAM. A CPU-Z reading can be perfect while a memory-hungry program or a full drive drags the whole system down, so latency isn’t always the thing to chase.
Wrapping up
Checking CAS latency is a five-minute job once you know where to look: Task Manager for the speed, CPU-Z’s Memory tab for the live timings, and the SPD tab for the rated profile. If the two don’t match, enabling XMP or EXPO usually closes the gap. The number itself only matters next to the speed, so read them together, and remember that a tighter CL at a higher MT/s is what you’re after. Now you can verify any kit you own, or vet a new one against the timings on its spec before you buy.
One last habit worth building: recheck these numbers any time you change hardware or update the BIOS. A motherboard firmware update can reset memory settings to defaults, quietly dropping you back to a slow JEDEC profile without any warning, and you’d never know unless you looked. Adding or swapping a stick can force looser shared timings too. A 30-second CPU-Z check after any memory or BIOS change confirms your kit is still running the speed and CAS latency you paid for, and catches a silent downgrade before it costs you frames or productivity.
Write Your Review
No reviews yet. Be the first to share your experience!