X370 Killer SLI A/C 1.0.0.6

AlbinoRhino wrote: I haven't been able to use the XMP profile ever. I don't know much about XMP, but just judging from the settings it looks like a shortcut to simply inputting your own timings. Is that how it works? I also had the Flare X's and the Trident Z's. Both were CL14 B-Die sets and I also could not get them to 3200. After benching all of them I decided to keep the Corsair LEDs since they matched my build and the benchmarks were only nominally better with the CL14s. I'm happy at 2933.I can't imagine 3200 making a huge difference. The largest increase in performance benefit that I saw was going from 2133 to 2667. 2667 to 2933 proved a smaller increase. The only thing left for me to tackle is the m.2 slot 1. I couldn't figure out how to mount my boot drive in that slot because the included screw was too small. Oddly, the screw worked in slot 2 without a problem so that is where my boot drive is now. I don't think the difference between the speeds of the two slots would benefit me since I don't transfer massive files and most of my data sits on the secondary HDD.

That's right, the XMP profile is just a set of memory settings (a profile) programmed into the memory that can be read and applied by the UEFI to quickly configure the settings correctly.

The XMP profile is only one of several predefined memory setting profiles programmed into our DRAM memory. In general this is called the SPD data. That's where the default/Auto memory speed and timings come from. They really aren't programmed into the UEFI, that would be impossible for all the memory models that exist. XMP is just a profile in the memory in a standard location of its own that can be found by the UEFI when you enable the XMP option. By a standard it is the highest performance memory speed and settings that the memory is marketed to operate at.

CPU-Z will show you some of the timing settings for some or all of the various SPD profiles stored in a model of memory. That's on the SPD tab (sorry, this is from my Intel Z270 PC):



So you weren't able to use the XMP profile with both the FlareX and Corsair memory? I can use the FlareX XMP profile, but must set the memory speed to 2933. The XMP profile for the Corsair memory was designed for Intel Z170 or Z270 systems, so the XMP settings may not work well with Ryzen.

I hate to tell you, but the lower m2_2 M.2 slot only runs at PCIe 2.0 x2 (10Gbit/s), while the upper M2_1 slot runs at PCIe 3.0 x4 (32 Gbit/s). I have my 960 EVO in the upper m2_1 slot, and the screw worked fine. The standoffs are identical (or should be) for both M.2 slots, and the screw should fit any of the standoffs. But if you are happy with it as it is, keep it that way.

I believe some have, I am not sure if it is 3200 RAM, possibly higher rated, but I have seen users get 3200 stable on this board. 

I can run my Team Vulcan 3000 at 2933 16-18-18-38 no issues.

http://www.teamgroupinc.com/en/product/T-Force%20Gaming/Gaming%20Memory%20Modules/DDR4%20MEMORY%20MODULES/Vulcan%20DDR4

If you have issues with the new BIOS, make sure you reset the UEFI settings to Default before flashing.  Seems that not doing so can cause hiccups in the update.


Edited by moonstarmac - 15 Jun 2017 at 9:13pm

Seems really strange that AND would not just follow the standards of the ddr4. I know it's oc memory it is just really strange. Also it more feels like something with the board more so since people with the taichi or crosshair or msi titanium have had 3200 working

While it is hard to comment on memory models when all I know is they are made by Corsair, I can say that memory was most likely designed for Intel systems like X99, Z170, or Z270. Expecting the XMP profiles designed for Intel systems to work with Ryzen is a mistake.

XMP set to Auto means the XMP profile is not being used.

Don't forget the addition of AGESA 1.0.0.6 is the CPU microcode provided by AMD. The Ryzen memory controller is part of the CPU. While AMD, etc, talk about AGESA updates "improving memory compatibility", a very vague statement that really tells us very little, what if these updates are dialing in the Ryzen memory requirements tighter and tighter? Which means DDR4 memory designed for Intel systems would not be working better, due to their differences. I was afraid we might begin seeing that occur, and now it seems that might be happening.

I have this board, with 16GB G.SKILL 3200 FlareX, "designed for Ryzen". I'm still unable to run that memory above 2933 with the AGESA 1.0.0.6 update in 2.50.

The general consensus in the forum about AGESA 1.0.0.6 on various boards is the same as it was with 1.0.0.4a. The reports are better, worse, or the same memory speeds or compatibility. So it seems no revelations in memory usage with 1.0.0.6.

I've used a Samsung 960 EVO as the OS drive with my X370 Killer SLI/ac board from day one, and although I installed Windows 10 again due to corruption of the first installation from testing memory speeds, I've had zero problems with it.

Denroth, what model of G.SKILL Ripjaws are you using? There are many Ripjaws 4 series and Ripjaws V series DDR4 memory models. We need the full model number please.