ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - Asrock X399 & Memory issues on my build
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Asrock X399 & Memory issues on my build

 Post Reply Post Reply Page  12>
Author
Message Reverse Sort Order
Albylion View Drop Down
Newbie
Newbie


Joined: 17 Oct 2018
Location: U.S.
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Albylion Quote  Post ReplyReply Direct Link To This Post Topic: Asrock X399 & Memory issues on my build
    Posted: 17 Oct 2018 at 1:24pm
Just chiming in a year later to say I had the same problem, and the same solution.  I have an x399 Fatal1ty Professional Gaming motherboard, Threadripper 2990wx, and 4 x 8GB Kingston HyperX 2400 DDR4 (HX424C15FW2K4/32).  DIMM_B2 (on the far right of the board) wouldn't recognize anything.  Switching out RAM sticks didn't work.  Unplugging the PSU and mashing the Clear CMOS button for ten seconds, then upgrading to BIOS 2.2, then to 3.3, didn't solve the problem.  (My computer would just power cycle continually with 2.2 as it couldn't recognize the Threadripper 2--I had to use the Flashback button and a USB stick without powering on [cool feature!].)  Then I took off the cooler and TIM, raised and lowered the TR4 bracket down as straight as I could, reapplied TIM and cooler, and ë moë! Problem solved!  Thanks! 

Fatal1ty DIMM_B2 wont recognize RAM sticks
Back to Top
lowdog View Drop Down
Newbie
Newbie


Joined: 16 Apr 2017
Location: Australia
Status: Offline
Points: 194
Post Options Post Options   Thanks (0) Thanks(0)   Quote lowdog Quote  Post ReplyReply Direct Link To This Post Posted: 24 Nov 2017 at 1:36pm
Originally posted by LurkerLito LurkerLito wrote:

Well all I can say is that with the latest bios 1.80 I can run 3200 but it isn't stable. I can run for hours but at some point Win 10 Pro will BSOD. So 1.80 did make the memory stable enough to even run a full HCI memtest overnight in both Windows and booting to it's own mem test program (bought the memtest deluxe program), but still for some reason as soon as I start using the system it will just randomly BSOD. So I dropped the ram speed to 3066 and now everything is perfectly stable with 0 BSODs since. The memory definitely isn't bad, and I doubt anything else is either, but for my system 3200 is just not working properly.



Exactly the same scenario with my system, 3200MHz will run but random freezing and BSOD but 2933MHz is fine......didn't bother with trying 3066MHz either yet.

Sure it's a bios issue that need addressing on the AGESA level more than likely.
X399 Fat Pro Gaming bios 3.10 - TR4 1900X - 64GB G-SKILL TridentZ F4-3200C14Q-64GTZ @ 3133MHz - Vega 64 AIO with EK block - WC Custom loop - 1500W Silverstone PSU - yay
Back to Top
ssateneth View Drop Down
Newbie
Newbie


Joined: 19 Oct 2017
Status: Offline
Points: 114
Post Options Post Options   Thanks (0) Thanks(0)   Quote ssateneth Quote  Post ReplyReply Direct Link To This Post Posted: 21 Nov 2017 at 9:13am
You also have to keep in mind that the fastest officially supported speed is 2667MHz (Single rank, 1 DIMM per channel). Anything past that is overclocking and not guaranteed. Dual rank DIMMs and 2 DIMM per channel decreases the official speed, depending on the combination, to as low as 1867MHz. If you get more than 2667MHz, great, but if you don't, according to manufacturer, that's not their problem. AMD provides tools to aid in operation above 2667MHz, but success is not guaranteed.

So try not to blame hardware as 'faulty' when you're running it above spec.

Anyways, as far as a more 'helpful' comment, 3200 can be difficult to attain, depending on chip quality and board used. I have an MSI X399 that did not play well at any speed above 2933, but the asrock taichi x399 allowed 3333 without a problem using mostly auto settings. Most of it comes down to silicon lottery. Using 4 samsing b-die 3600MHz rated dual rank DIMMs
MB: X399 Taichi, UEFI L3.32
VGA: EVGA 1080 Ti FTW3
PSU: Seasonic PRIME 1300 W PLATINUM
CPU: AMD Ryzen Threadripper 2950X
MEM: 4x16GB, 3600MHz G.Skill Trident Z F4-3600C17Q-64GTZKW
Back to Top
LurkerLito View Drop Down
Newbie
Newbie


Joined: 23 Sep 2017
Status: Offline
Points: 46
Post Options Post Options   Thanks (0) Thanks(0)   Quote LurkerLito Quote  Post ReplyReply Direct Link To This Post Posted: 21 Nov 2017 at 8:50am
Wow I didn't think someone had a calculator for it. I'll have to give it a try. Thanks!


Edited by LurkerLito - 21 Nov 2017 at 8:50am
AMD 1950x; ASRock X399 Fatal1ty V2.00; 64GB(4x16GB) G.Skill Trident Z DDR4 3200 CL14 (running 3066); EVGA 1080Ti SC2 Hybrid; Enermax TR4 360 AIO
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 (1) Thanks(1)   Quote datonyb Quote  Post ReplyReply Direct Link To This Post Posted: 21 Nov 2017 at 4:38am
its basically not 100% happy with the settings in bios for xmp (remember these settings are designed for intel bios ,and intel bios has been tweaked by board makers to use these rams


soooooooo  what do you do ?

i suggest using the ryzen dram calculator to tweak the stock xmp settings to suit amd
follow the guide and remember to change all settings as they work WITH EACH OTHER

http://www.overclock.net/t/1640919/ryzen-dram-calculator-overclocking-dram

remember to set all left hand colum to your specs eg
ram quaility UHQ
dual sided
4 sticks
3200 mhz

then copy in the fields as shown in guide

hit calculate 'safe' settings and she should boot with the given numbers quite happily


Edited by datonyb - 21 Nov 2017 at 4:38am
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
Back to Top
LurkerLito View Drop Down
Newbie
Newbie


Joined: 23 Sep 2017
Status: Offline
Points: 46
Post Options Post Options   Thanks (0) Thanks(0)   Quote LurkerLito Quote  Post ReplyReply Direct Link To This Post Posted: 21 Nov 2017 at 3:26am
Well all I can say is that with the latest bios 1.80 I can run 3200 but it isn't stable. I can run for hours but at some point Win 10 Pro will BSOD. So 1.80 did make the memory stable enough to even run a full HCI memtest overnight in both Windows and booting to it's own mem test program (bought the memtest deluxe program), but still for some reason as soon as I start using the system it will just randomly BSOD. So I dropped the ram speed to 3066 and now everything is perfectly stable with 0 BSODs since. The memory definitely isn't bad, and I doubt anything else is either, but for my system 3200 is just not working properly.
AMD 1950x; ASRock X399 Fatal1ty V2.00; 64GB(4x16GB) G.Skill Trident Z DDR4 3200 CL14 (running 3066); EVGA 1080Ti SC2 Hybrid; Enermax TR4 360 AIO
Back to Top
daddyo View Drop Down
Newbie
Newbie
Avatar

Joined: 30 Oct 2017
Status: Offline
Points: 54
Post Options Post Options   Thanks (0) Thanks(0)   Quote daddyo Quote  Post ReplyReply Direct Link To This Post Posted: 21 Nov 2017 at 2:07am
My memory was not faulty. I ran mem test for an entire day with it. 

It seems you misunderstand what I said. I doubt the RAM was faulty in the first place. There seems to be little consensus on what RAM is best suited for this platform.

After switching to the gskill flareX, same as yours, I have not had any issues. I did end up RMA'ing the motherboard for good measure.




Edited by daddyo - 21 Nov 2017 at 2:09am
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: 18 Nov 2017 at 6:54am
Keats, please post your specifications in yur signature as I have and include the versions of your OS and BIOS and power supply.  I find the BIOS quite well done and works mostly - RAID is an exception.  You must explain exactly what your failures are not just "didn't work" especially BIOS update.  Before BIOS is updated, you should open BIOS hit F9 (Load UEFI Defaults), F10 (Save and Exit), open BIOS and use the Instant Flash (never Windows!!!) to update BIOS then open BIOS and do F9, F10.  Let us know how it goes.  Do not mess with Memory Interleaving.  It does not surprise me at all that your memory did not work at speed on the old BIOS/AGESA.  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
Keats View Drop Down
Newbie
Newbie


Joined: 16 Nov 2017
Status: Offline
Points: 5
Post Options Post Options   Thanks (0) Thanks(0)   Quote Keats Quote  Post ReplyReply Direct Link To This Post Posted: 18 Nov 2017 at 6:53am
Originally posted by JUANNY JUANNY wrote:

Originally posted by Keats Keats wrote:

Originally posted by daddyo daddyo wrote:

It's not necessarily Asrock's fault. I can tell you I had problems with 3200mhz tridentZ RAM. I bought a 4x16gb kit.

The RAM reported 1100mhz in UEFI, and things were not working right. I didn't have issues on the first week, and even was able to stress test the RAM all day with no errors. Eventually, I ran into problems, and I suspect it's the RAM.

Many people have recommended not bothering pushing your RAM speed over 3000mhz with Threadripper, as it won't be a stable system. If you want anything over 2400 because you want to overclock, I recommend getting the Flare X modules from Gskill that just came out. So again, this points out to a platform wide problem, rather than with one particular motherboard model.

Some others might have had some luck with other modules, but you should wait for confirmations before trying a specific RAM/motherboard configuration.


I respectfully disagree with your assessment. I've read about plenty of (Threadripper and other) builds using this particular memory. The memory is generic 3200Mhz and should be easily able to achieve those speeds.  The fact that all the sticks worked in any of the slots except the 8th slot or in any combination with the 8th slot clearly points to a memory controller issue on the cpu. It's either a Foxconn problem that actually doesn't seat the cpu right (which I find highly unlikely), or it's an actual bug in the AMD BIOS that is causing the memory controller on the cpu to not get addressed properly. I mean seriously, the sockets don't allow much room for error and inserting the cpu wrong is almost impossible. Combine that with the fact that not just on mine, but on other people's machines as well, re-seating the cpu fixed the issue right away? Clearly something gets reset internally which allows it to work.

My next step is to OC the BCLK, we'll see how well Ryzen likes faster memory.


I think your memory or your board is faulty. I just finished putting together my 1950x build using the x399 fatality pro. Im using the new flare x that is optimized for TR

F4-2933C14Q-64GFX It booted fine and is now running at 2933 cl 14 fully stable BTW can anyone see my sig cause I cant




Hey I can see your signature!

I was able to get mine to work at 3200Mhz (as you can see from my original post in the Edit section. I don't think my memory or motherboard were faulty.
Back to Top
JUANNY View Drop Down
Newbie
Newbie


Joined: 13 Oct 2017
Status: Offline
Points: 50
Post Options Post Options   Thanks (0) Thanks(0)   Quote JUANNY Quote  Post ReplyReply Direct Link To This Post Posted: 18 Nov 2017 at 6:50am
Originally posted by Keats Keats wrote:

Originally posted by daddyo daddyo wrote:

It's not necessarily Asrock's fault. I can tell you I had problems with 3200mhz tridentZ RAM. I bought a 4x16gb kit.

The RAM reported 1100mhz in UEFI, and things were not working right. I didn't have issues on the first week, and even was able to stress test the RAM all day with no errors. Eventually, I ran into problems, and I suspect it's the RAM.

Many people have recommended not bothering pushing your RAM speed over 3000mhz with Threadripper, as it won't be a stable system. If you want anything over 2400 because you want to overclock, I recommend getting the Flare X modules from Gskill that just came out. So again, this points out to a platform wide problem, rather than with one particular motherboard model.

Some others might have had some luck with other modules, but you should wait for confirmations before trying a specific RAM/motherboard configuration.


I respectfully disagree with your assessment. I've read about plenty of (Threadripper and other) builds using this particular memory. The memory is generic 3200Mhz and should be easily able to achieve those speeds.  The fact that all the sticks worked in any of the slots except the 8th slot or in any combination with the 8th slot clearly points to a memory controller issue on the cpu. It's either a Foxconn problem that actually doesn't seat the cpu right (which I find highly unlikely), or it's an actual bug in the AMD BIOS that is causing the memory controller on the cpu to not get addressed properly. I mean seriously, the sockets don't allow much room for error and inserting the cpu wrong is almost impossible. Combine that with the fact that not just on mine, but on other people's machines as well, re-seating the cpu fixed the issue right away? Clearly something gets reset internally which allows it to work.

My next step is to OC the BCLK, we'll see how well Ryzen likes faster memory.


I think your memory or your board is faulty. I just finished putting together my 1950x build using the x399 fatality pro. Im using the new flare x that is optimized for TR

F4-2933C14Q-64GFX It booted fine and is now running at 2933 cl 14 fully stable BTW can anyone see my sig cause I cant

Asrock X399 Fatality Pro Gaming Bios 2.0 Threadripper 1950X Cpu cooler Enermax 360 mm TR4 GSkill 64 GB F4-2933C14Q-64GFX Windows 10 X64 PRO Version 1709 Build 16299.19 2X EVGA 1080 TI in SLI mode
Back to Top
 Post Reply Post Reply Page  12>
  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.430 seconds.