T-Force Delta TUF Gaming RGB Memory Review

Memory (DDR4/DDR5) and Storage (SSD/NVMe) 367 Page 7 of 14 Published by

teaser

CPUz & XMP

XMP, or Extreme Memory Profile, or how to over-egg something...

Even when talking about something as potentially dull as memory, the hardware market and vendors do just love to over-egg things, don't they? We will start by quickly looking at CPU-Z with the XMP enabled, to make sure that all is as should be with this kit. Enabling XMP must be done by the user, otherwise, your kit of DDR4 will be running at the default spec of 2133Mhz. This was fairly common back in the early days of DDR4 but now is practically glacial when compared to some of the 4000Mhz and above kits that are sold & ratified for use on modern platforms.


Cpuz_cpu

Cpuz_ram


XMP should, in theory, work straight out of the box. Some kits have 2 profile to use, with the second being a slightly looser/more downclocked version of the first. In an ideal world, selecting XMP 1 and doing a 'save & exit' from the BIOS should enable the profile and allow the system to boot straight back up without problems. If it doesn't, you might have more luck dialling in exactly the settings listed on the kit. If that doesn't work... um, cry and be annoyed? It's not an ideal start, however, when we look at the QVL on MSI's site for Summit Ridge and the B350M mainboard that I own. Only a single Team Group 3200Mz kit is actually ratified to work on this board, a Samsung chip equipped and single rank 16GB (2x 8GB) affair. I do, however, have high hopes for this kit being able to work regardless. So... did it?


Cpuz_memory_overclocked

Cpuz_memory_oced


Thankfully, it did. I legitimately had absolutely no doubt it would, to be fair. Much has changed since the very early days of Ryzen Summit Ridge, and now I would venture the majority of even half decent memory kits that are rated for 3200Mhz are able to hit such a speed on even Gen 1 Ryzen. Note that this kit did actually come with two installed XMP profiles. The first was, oddly enough, a downclocked version running at 2933Mhz with the same timings. The second was the one I booted into successfully. Remember that CPUZ (and most monitoring tools in general) will display the memory clock at half of what it is actually running at, thanks to memory being 'DDR' or 'Double Data Rate.' So, you see 1600? 1600 x 2 = 3200. Simple. Note you can also see the RAM timings on the correct subpage, and CPUZ confirms what Team Group state. 16-18-18-36, with a command rate of 1T. Note, as with timings, the higher the DRAM Command Rate, the more chance you have of your 'out of spec' memory overclock being stable. You can see this in the screenshots on this page, with CPU-Z showing the memory running at 1600Mhz, with the default XMP timings of 16-18-18-38.

Share this content
Twitter Facebook Reddit WhatsApp Email Print