<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>ASRock Forums : X370 Gaming K4 Mem Help</title>
  <link>https://forum.asrock.com/</link>
  <description><![CDATA[This is an XML content feed of; ASRock Forums : AMD Motherboards : X370 Gaming K4 Mem Help]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Thu, 04 Jun 2026 15:21:26 +0000</pubDate>
  <lastBuildDate>Sat, 01 Apr 2017 02:38:57 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://forum.asrock.com/RSS_post_feed.asp?TID=4723</WebWizForums:feedURL>
  <image>
   <title><![CDATA[ASRock Forums]]></title>
   <url>https://forum.asrock.com/forum_images/web_wiz_forums_black.png</url>
   <link>https://forum.asrock.com/</link>
  </image>
  <item>
   <title><![CDATA[X370 Gaming K4 Mem Help : As parsec noted in another thread, ...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=4723&amp;PID=26397&amp;title=x370-gaming-k4-mem-help#26397</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=5131">twf85</a><br /><strong>Subject:</strong> 4723<br /><strong>Posted:</strong> 01 Apr 2017 at 2:38am<br /><br />As parsec noted in <a href="http://forum.asrock.com/forum_posts.asp%3FTID=4713&amp;PN=3&amp;title=x370-future-memory-support" rel="nofollow">another thread</a>,&nbsp;<div><br></div><div><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by parsec" alt="Originally posted by parsec" style="vertical-align: text-bottom;" /> <strong>parsec wrote:</strong><br /><br />...&nbsp;the DDR4 XMP profile data for Intel X99 processor memory controllers won't work with the Ryzen memory controller. The memory controllers are different, and some of the memory settings are different. When using DDR4 memory&nbsp;<b>designed for other systems</b>&nbsp;with a Ryzen system, the memory timings must be set manually.<br><br>How can the Ryzen memory controller, a piece of hardware that is part of the CPU, be changed by a UEFI/BIOS update to support the XMP data/settings for the memory controller of Intel Haswell-E and Broadwell-E processors? The good news is at least your Corsair memory will work with a Ryzen system.<br><br>All modern memory also contains multiple sets of basic timing data for different non-over clocked supported speeds of a model of memory. That data is referred to as the JEDEC or SPD data, which you can view in the CPU-Z SPD tab. One set of that data is the memory timing data used for the default speed of your memory, most likely 2133. The SPD data allows a mother board's UEFI/BIOS to automatically set the timing parameters for our memory.<br><br>XMP data is simply another convenience for setting memory timings to the correct values for the "E<b>X</b>treme&nbsp;<b>M</b>emory&nbsp;<b>P</b>erformance" speed of memory. That is the over clocked speed of your memory, which is any speed beyond the specifications of the memory controller in your CPU. Unfortunately, we've become used to using it, and the memory manufactures don't provide any other information about the timing settings for their products.<br><br>If you cannot set memory parameters manually, you'll simply need to wait for Ryzen specific memory to be available. Of course a valid question is, what are the correct timing settings to be used with the Ryzen memory controller with your model of memory?&nbsp;<br><br>That is something that Corsair should provide for you. If they tell you to use the XMP profile, you know that does not work, and is a wrong answer. If they tell you to wait for mother board BIOS support, they are putting you off, and just hoping the mother board manufacture will do their work for them.<br><br>Here are some example timings for your memory that was CPU-Z verified on a good sized set of Ryzen boards. Note that setting the Command Rate (CR) to 1T is needed for achieving higher speeds, which is something that will&nbsp;<i><b>never</b></i>&nbsp;be found in DDR4 XMP data for Intel processors. Also note, reaching 3200 is very rare (so far), and if you are at 2666 now, you are above average.<br><br><a href="http://rymem.vraith.com/detailed_ram/715" target="_blank" rel="nofollow">http://rymem.vraith.com/detailed_ram/715</a></td></tr></table></div><div><br></div><div>I know you saw the response there, but in case someone else stumbles upon this one, I think his response will be useful.</div>]]>
   </description>
   <pubDate>Sat, 01 Apr 2017 02:38:57 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=4723&amp;PID=26397&amp;title=x370-gaming-k4-mem-help#26397</guid>
  </item> 
  <item>
   <title><![CDATA[X370 Gaming K4 Mem Help : Hey guys,Just got a X370 Gaming...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=4723&amp;PID=26246&amp;title=x370-gaming-k4-mem-help#26246</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=5307">juanvr</a><br /><strong>Subject:</strong> 4723<br /><strong>Posted:</strong> 29 Mar 2017 at 4:27pm<br /><br />Hey guys,<div><br></div><div>Just got a X370 Gaming K4.</div><div>Using Corsair Vengeance LPX 16GB Kit: CMK16GX4M2B3200C16W</div><div><br></div><div>Best I could get out of this 3200 CL&nbsp;16-18-18-36 kit is 2667 18-18-36-62... Very demoralizing especially since I just built it and I read LPX kits are compatible, just not <b>THESE </b>LPX kits...</div><div><br></div><div>Any help to get it running better would be appreciated. Im pretty sad.</div>]]>
   </description>
   <pubDate>Wed, 29 Mar 2017 16:27:26 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=4723&amp;PID=26246&amp;title=x370-gaming-k4-mem-help#26246</guid>
  </item> 
 </channel>
</rss>