ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - B350 Fatal1ty RAM question
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

B350 Fatal1ty RAM question

 Post Reply Post Reply
Author
Message
MSahan View Drop Down
Newbie
Newbie
Avatar

Joined: 08 Jun 2017
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote MSahan Quote  Post ReplyReply Direct Link To This Post Topic: B350 Fatal1ty RAM question
    Posted: 08 Jun 2017 at 6:20am
Hi Guys,

I bought the B350 Fatal1ty mobo and a QVL listed G.Skill 3200 MHZ DDR set of 16gb's (F4-3200C14D-16GFX). 

After having installed everything i updated the UEFI to 2.5. Everything went well so far.

However, it seems that i cannot get my RAM above 2933 MHZ. Is that currently possible? I thought the QVL ram was tested and proven to work at said speeds. Was i wrong?

Looking forward to hearing from you!
Back to Top
datonyb View Drop Down
Senior Member
Senior Member


Joined: 11 Apr 2017
Location: London U.K.
Status: Offline
Points: 3139
Post Options Post Options   Thanks (0) Thanks(0)   Quote datonyb Quote  Post ReplyReply Direct Link To This Post Posted: 08 Jun 2017 at 7:21am
not all cpus and rams were created equal .....................

have you tried setting the speed and timings manually ?

eg not clicking xmp

also try (if you board allows it )
increasing SOC voltage to 1.1 volt or 1.0 volt
(it helps the cpu memory controller work better)
also try manually upping the ram volts to 1,4volt
and try loosening the ram timings to cl 16
if and hopefully when you get it to boot 3200 stable
then carefully try one thing at a time to tighten it up

eg try cl15 then cl14 timings
then try lowering dram volts back to 1,35

its basic ryzen ram testing/trianing methods plenty of advice on google if you want to read up
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 08 Jun 2017 at 9:21am
Originally posted by MSahan MSahan wrote:

Hi Guys,

I bought the B350 Fatal1ty mobo and a QVL listed G.Skill 3200 MHZ DDR set of 16gb's (F4-3200C14D-16GFX). 

After having installed everything i updated the UEFI to 2.5. Everything went well so far.

However, it seems that i cannot get my RAM above 2933 MHZ. Is that currently possible? I thought the QVL ram was tested and proven to work at said speeds. Was i wrong?

Looking forward to hearing from you!


What Ryzen CPU are you using?

Any Ryzen memory speed above 2667 is a memory OC, and unfortunately not guaranteed. That is what G.SKILL states, if you check the fourth review from the top of the first page, here:

https://www.newegg.com/Product/Product.aspx?Item=N82E16820232530&cm_re=F4-3200C14D-16GFX-_-20-232-530-_-Product

The memory QVL is a list of compatible memory that will work with a board, but memory over clocks cannot be guaranteed.

I use the same model of memory with my ASRock X370 Killer SLI/ac board, with a 1700X CPU, and I also cannot reach 3200. So far, 2933 is the maximum at the rated timings.

Check the G.SKILL QVL for this memory, so far they only list the ASRock X370 Taichi as compatible at 3200.

http://gskill.com/en/product/f4-3200c14d-16gfx

As stated above, you can try increasing the SOC voltage if your board's UEFI has that option. Also, future AMD AGESA CPU microcode updates that are included in UEFI/BIOS updates may help us reach 3200. The recently released version 1.0.0.6 by AMD should be available in the next few weeks.

Ryzen memory compatibility is the main issue it has, and we still don't have all the memory timing options in the UEFI that we have had with DRAM memory for years. Some of those options will be added with the AGESA 1.0.0.6 microcode update, which are finally being supplied by AMD.
Back to Top
Zombies_Eat_You View Drop Down
Newbie
Newbie
Avatar

Joined: 26 Aug 2017
Location: USA
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote Zombies_Eat_You Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2017 at 2:27am
I have the same mobo/RAM and activated XMP and Ram is showing (according to CPU-Z) 1596 x 2, 3192 mhz. 3200 in bios though. Weird number for CPU to record.
B350 Fatal1ty GamingK4/Ryzen 1600/16GB Gskill FlareX/H100v2/Seasonic titanium 650/Thermaltake Core X31
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2017 at 3:00am
Originally posted by Zombies_Eat_You Zombies_Eat_You wrote:

I have the same mobo/RAM and activated XMP and Ram is showing (according to CPU-Z) 1596 x 2, 3192 mhz. 3200 in bios though. Weird number for CPU to record.


That diff is attributable to how the BIOS interprets the sticks XMP Profile.
Back to Top
MisterJ View Drop Down
Senior Member
Senior Member


Joined: 19 Apr 2017
Status: Offline
Points: 1097
Post Options Post Options   Thanks (0) Thanks(0)   Quote MisterJ Quote  Post ReplyReply Direct Link To This Post Posted: 26 Aug 2017 at 3:06am
CPU-Z always shows me weird numbers for all frequencies.  I just assume it has to do with what each is using for a master clock.  What is the time/frequency standard?  I suspect the measurement chip has one and the various timing systems have their own, so some differences.  Enjoy, John.
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.359 seconds.