1. Your system's specs.

2. The BIOS version that was installed before updating, and the version you updated to.

3. Update method (BIOS/DOS/WINDOWS).

4. Your experience so far with the new BIOS.

If you read through this forum, you will find quite a few people who cannot get their RAM up to their max rated speed. Right now, you need to have compatible sticks to get the speeds you are looking for.

This is a good resource -  http://forum.asrock.com/forum_posts.asp%3FTID=4565&title=am4-ryzen-specific-memory-and-tips" rel="nofollow - AM4/Ryzen Specific Memory and Tips

What BIOS version were you using prior to updating to 2.0?

What RAM are you specifically using? (e.g. my sticks are F4-3200C14D-16GFX)

How did you perform the BIOS update to version 2.0?

Other then failing to get the RAM up to the speed you'd like, what else have you noticed since updating to 2.0? Is the system stable when you run your RAM at lower speeds?

1.

1800X @ 4000

https://www.newegg.com/Product/Product.aspx%3FItem=N82E16820232530" rel="nofollow - F4-3200C14D-16GFX x 2 (16GB) @ 3200

Samsung 950 Pro 512GB / M.2_1

Windows 10 Pro 64bit / v.1607 b.14393.969

2.

v1.6

3.

Windows / UpdateBIOS.bat

4.

No major issues, aside from a few minor nuisances.

Still experiencing a bug in the Restart to UEFI app with RAM at 3200/XMP that isn't present if I cycle down to 2400/Auto. I run the App, the system restarts, but at the first post screen, it stutters and then restarts again. Then the computer boots as normal, taking me into Windows.

Also, my boot times seem higher than they should be. First boot with the updated BIOS (with most of the settings reset) returned a boot time of ~12.7 seconds, versus the ~17.6 seconds its at now. Seems odd that the time would increase with quicker RAM, but oh well. I guess this board and RAM combo has trouble with XMP profiles.

Lastly, I had my first BSOD with this system after updating. While I was watching a show or something on the TV I connect to occasionally, an email notification came in. The wonderful noise that kept repeating until it restarted was one of the final notes in the alert that had sounded. The BSOD was related to the graphics driver, so probably not to do with the new BIOS. More likely due to the speed I have the RAM at, or the fact that I had forgotten to disable CSM Compatibility after updating.

NOTE: If you are running a UEFI OS, make sure you go in and turn off CSM Compatibility after you update the BIOS. This shaved my boot time from ~20.8 seconds down to ~17.6, and the system seems a touch more stable than with CSM enabled.

3. Windows UpdateBIOS.bat file

4. Great so far, the only issue I ran into, I run a bunch of Virtual Machines on my box and CPU Virtualization got disabled after flashing it, (can't remember the exact name of the setting).

Yes thats the setting, yeah it was on by default when I first got the board, no issues until I updated that EUFI, but once I got it flipped on everything was good.

    16GB of G.Skill 3200C14 Samsung B-die

2. Updated from 1.93d

3. Used the BIOS Instant Flash

4. Been basically the same; RAM still works at XMP settings and processor is still stable at 4GHz on the same settings I had previous. I do get some glitchy graphic when shutting down or booting up though. Can't be certain if this is BIOS or the new GPU, haven't tried reinstalling the card physically either yet. I did have a scare with my primary SSD today though. Switched SATA ports and BIOS picked it back up, haven't put it back where it was though so can't say if I lost a SATA port randomly or not.

Is the graphics card UEFI enabled? If it's a relatively new card (>2013-14), then you should be safe.

If your OS is UEFI, go to the BOOT tab in this BIOS, scroll to the bottom, and click on "CSM Compatibility". That is enabled by default, and will get reset after a BIOS update. If the "glitchy" graphics you're referring to is the OS loading screen appearing and then reappearing before you see your login screen, then I'd hazard a guess that your OS is UEFI and that you have CSM Compatibility enabled.

If you disable CSM Compatibility, and all you see is a black screen after hitting the power button, then your graphics card is probably not UEFI capable. Resetting the CMOS is probably the only way forward after that.

Fan curves don't seem to work at all- all my fans run at a constant speed no matter which settings I use. I can change the speed by messing with fan curves but it doesn't react to CPU temperature at all, and it doesn't seem to respond to the mobo temp reading either.  I think maybe it's trying to use the PECI temp for the CPU, and since that's stuck at 40C, it always uses the corresponding fan speed.  Also F-Stream Tuning stopped working for me after the Windows Creator update so that's not an option either.

It's driving me nuts and even though I know it's incredibly unlikely, I'm paranoid that I caused thermal damage during stress testing when I was trying to figure out what was going on.

1. Were you overclocking the CPU during your stress tests?

2. What program are you using to monitor temps?

P-phase overclocked (3.9 ghz 1.36 Vcore 1.15 VSoC, shown to clock up and down properly in hwinfo) and using HWinfo64 for monitoring, most recent beta.

Yes, I understand how to set up fan curves perfectly well- in fact I set them up before the BIOS update and they worked fine.

The fatal1ty Pro Gaming detects whether your fans are PWM or DC for all headers except one, which I set to DC control manually for a 3 pin fan.  The fans remain at constant RPM no matter what profile is chosen (even my own custom curves) and do so whether they're set to monitor CPU temps or mobo temps.  Also the silent profile is not a constant speed, it just ramps up at a higher temp and to a lower speed.

I'm using a Noctua NH-D15 with 2 PWM fans that's already been proven to work since it worked properly on the Gigabye AX370 Gaming 5 I switched from.

F-Stream Tuning does not work for me with windows creator update.

This screenshot is from HWinfo after over a day of uptime with normal usage including gaming and streaming, no stress testing.  The values are current, min, max, and average and as you can see they're all virtually the same other than chassis2 which occasionally throws weird reading at start up for some reason, hence the weird min/max.  I even set CPU_OPT to monitor mobo temps to see if it would make a difference but apparently it doesn't.

This happens with any fan curve, default or otherwise.

Since the socket temp stays in such a small range that explains why the fan speeds barely change.  As a follow up, in general should I be monitoring the socket or die temps?  AMD said tjmax for R7 is 75C but I'm not sure which reading they're referring to.  This is my first AMD system since the Athlon so I'm still getting used to their terminology.

If these forums are any indication, you are not alone in your frustration over RAM speeds. All we can do is be patient, or buy RAM that is known to play nice with Ryzen.

Speaking to your case in particular, you must've had a reason to jump on board as an early adopter, and these are, as they say, "the breaks". I don't say that devoid of any empathy, as I was recently in your shoes; however, using a mixture of uppercase words and acronyms to convey your point and express your frustration only makes for very difficult reading.

Were I you, I would try to find a way to be thankful that I hadn't bricked my board in my lust for faster speeds, and then I would try to find a solution that either involved patience or my checking account.

Hiya  my Experience of the v2 bios this morning !

My ASrock X370 motherboard fails to post after Bios Update

I tried updtating to the version 2.00 Bios from the AS Rock Website (Using the windows method)

This was to fix issues locking up on startup of windows

Lockups in Payday 2

But otherwise the system seam to be running stable in many other games

I am an IT enginer by trade so im used to updating and building systems and i followed the bios update procedure on the ASRock Website

http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Professional%20Gaming/#BIOS" rel="nofollow - http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Professional%20Gaming/#BIOS

http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Professional%20Gaming/#Specification" rel="nofollow - http://www.asrock.com/mb/AMD/Fatal1ty%20X370%20Professional%20Gaming/#Specification

Further Info

1. Unfortunatly its not posting to a Screen so im unable to try and Re-flash the Bios currently with either the DOS or Bios option

2. I have tried removing 3 of the 4 sticks of ram  G-SKills Trident Z which was working fine

3. I can send a vidio the Debug LED cyles round and round 55, 43 65,67, 07  then goes very fast back to 55

Im Happy to try any suggestions or contact my supplier to RMA

2. The BIOS version that was installed before updating to 2.0. - 1.50(original)

3. Update method (BIOS/DOS/WINDOWS). - DOS

4. Your experience so far with the new BIOS.  - Had an issue with my M.2 drive vanishing (not being detected in the bios, by the system at all) after rebooting,  which hasn't happened since updating to 2.0
I haven't had a lot of free time to dig into the settings(or work on overclocking) but I've had no other issues since the build.  XMP settings, with my memory, just worked (as they should).

I reordered some of the reading to make it easy to view at a glance but it's hwinfo 5.51-3135.

I was informed that the 'CPU' reading that things like AIDA64 read from by default are the socket temps as read by a sensor included on all the x370 mobos I've seen- dunno if it's actually standard or just really common.  It's always way lower than tctl/tide (same for me since I have a 1700 but I've seen the same thing w/ socket temps even on 1700x/1800x systems).  Other programs like hwinfo also showed that same generic 'CPU' temp (an older version I tried, I think updates changed this) that was definitely not tctl or tdie even with a 20C offset, and I saw that same with my X370 Gaming 5 before I switched over to Asrock.

I have a X370 Pro Gamer/1800x@4.0Ghz - G.Skill F4-3000C14D-16GTZ@3200Mhz

Boot drive Samsung 960PRO SSD 2TB.

Video- two EVGA GTX 1080 Hydro Coppers in SLI.

The motherboard came with Vers 1.40. I updated to 1.50 through windows 10 and and Used quick flash to v1.55., then 1.60.

Got everything running stable. It games pretty good at 4.1Ghz smt off.

When I tried using BIOS v1.93 everything was still stable but CPUID HWMonitor was indicating

a huge voltage fluctuation in CPU VCORE.  From 1.392v to 2.8v. I went back to v1.60 and 

the problem went away. When v2.0 came out it did the same thing with unstable voltages.

I'm hoping that the next BIOS version takes care of the problem.

BTW, to get the overclock and not have such a high voltage(1.44) all of the time, I started using

Voltage offset mode and Load Line Calibration for both CPU and VDDR_SOC voltages.

The Cpu idles at around .608V or less and with load up to 1.44V. VDDR_SOC stays around 1.92V

Is anyone else having problems like mine with the newer BIOS versions or is there a workaround.

I went into the BIOS and checked the mem settings. 

XMT on showing 3000mhz 14-14-14-36 1.35v.

My settings 3200Mhz 16-16-16-38 1.40v

I didn't notice it before, but even at CPU 4.0GHz and 3200Mhz mem selected, after boot CPUID verifies

that DRAM Freq is 1599.6 MHz 16-16-16-38-75-1T.

BIOS versions higher than v1.60?

Duh. I just answered my own question. I will contact support.

I was looking for compatible chips and the Samsung single rank DIMMS fit my profile.

They run 3000MHz 14-14-14-36 1T at stock speeds, but only need

a bump to 1.40v to go along with a 4GHZ overclock and 16-16-16-38 1T

for the 4.1GHz overclock. I needed to turn off SMT to get the 1800x to 4.1GHz, but

when I'm gaming I don't really need all 16 threads.

I can only comment on what I've witnessed. I've followed the releases of BIOS updates for the X370 Fatal1ty Gaming Pro board since the launch of Ryzen, on a daily basis. Due to the high failure rate of the BETA updates, my guess is that we won't be seeing much of those in the future.

Sure, ASRock says we are responsible (for the outcome of updating the BIOS), but I have yet to see one angry thread from someone (who bricked their board) complaining that ASRock wouldn't accept their board for RMA. ASRock is obviously eating the cost of these bricked boards.. Great for our wallets, bad for theirs.

They had a hell of a hill to climb at launch. If you've read up on the rumors and reports concerning AMD and manufacturers, then it's not hard to imagine just how much work ASRock and others have put into making these systems functional; in such a short time period and under extreme pressure. It makes sense that there were frequent updates in the early days, but I think from here on out, it would be logical to expect the frequency between future updates to steadily increase.

I think I'm going to give it a whirl to see if they fixed the Restart to UEFI issue..

1.

1800X @ 4000

https://www.newegg.com/Product/Product.aspx%3FItem=N82E16820232530" rel="nofollow - F4-3200C14D-16GFX  x 2 (16GB) @ 3200

Samsung 950 Pro 512GB / M.2_1

Windows 10 Pro 64bit / v.1607 b.14393.1066

2.

v2.0

3.

BIOS / Instant Flash

4.

Still having trouble with Restart to UEFI (ver:1.0.5). Same behavior that was present in previous BIOS: prior to loading the ASRock splash screen, the computer restarts again and boots as normal.

CSM Support disabled? Secure Boot enabled?

EDIT: I ask because I feel like my BIOS settings were kept intact between 1.6 and 2.0, as I don't recall having to reset some things.. But I definitely had to go through and reset everything after the jump from 2.0 to 2.2. Even my Saved settings were cleared.

For me, when I'm programming, I often change things around as a project evolves. Naming conventions, for example, often evolve as the scope of a project expands. I can see why they wouldn't want to risk boot-looping someone's system with an invalid selection/value or incomplete configuration, so they just default the update behavior to reset everything. Fewer calls to tech support / RMA's.

I get what you're saying though. If I had a spent hours customizing my settings, that would really tick me off. Especially given the number of updates since launch.

I think it would be wise to hold off on that level of customization until they've solved a lot of the basic problems people are experiencing, namely RAM compatibility (which if I recall correctly, is one of your major issues, currently).

This whole Ryzen launch sort of reminds me of when I went on a 8-month "vacation", courtesy of the Arizona Department of Corrections. The entire time I was there, the situation never sunk in. My mind wouldn't accept it, so I'd often complain about being treated like less than a person. To which someone around me would always say, "You're in prison, dude".

"Buy the ticket, take the ride."

We're all along for the ride at this point, no sense complaining about it.

I hope that the new microcode that's on the way helps make Ryzen more accessible to consumers. I know that it's a new platform, and I know that we're still in the early days. But it is a little disconcerting to see that the 1800X has dropped $35 (7%) in ~2.5 months :\ Not quite the same feeling I had while I was sitting in an almost empty theater for King Arthur this weekend, but close.

1.

1800X @ 4000

https://www.newegg.com/Product/Product.aspx%3FItem=N82E16820232530" rel="nofollow - F4-3200C14D-16GFX  x 2 (16GB) @ 3200

Samsung 950 Pro 512GB / M.2_1

http://www.ebay.com/sch/i.html%3c_nkw=windows+10+pro+64bit" rel="nofollow - Windows 10 Pro 64bit  / v.1703 b.15063.296

2.

v2.2

3.

BIOS / Instant Flash

4.

Still having trouble with Restart to UEFI (ver:1.0.5). Same behavior that was present in previous BIOS: prior to loading the ASRock splash screen, the computer restarts again and boots as normal.

CRC32: 64A892F4
MD5: B0EF9C4F4DA912BB9C757344F4F9D793
SHA-1: 820B1B0D57351BF2E76AA32F789D166758BD83DA
SHA-256: 8C4EBA5BB40611243E8836404A9DFCBBC7C601CDE41F58433ADB9D8F7F72A483
SHA-512: 07B7F0E22F4A7F770FA8D4B0451E87F5EDF61ED4C695FF56CEC19457AB7D773490981D4C7457BACCBB69022C2E8A816F692B3193C1640D0411DA567D9588EEE9

I tried uinstalling it and then reinstalling it, but no luck. I can use Restart to UEFI if I lower my RAM speed down to 2400, but no higher. With or without XMP enabled.

MisterJ wrote: What are you using to display the temperature of the CPU?  Apparently AMD added 20 C and some applications subtract it (AIDA64, for example).

I'm using HWiNFO64 (v5.50). CoreTemp http://www.alcpu.com/forums/viewtopic.php%3Ff=64&t=5825&start=25" rel="nofollow - might will be working soon , which is what I prefer using (I like the tray temp icon).

Anyway, I forgot I was folding :( I reverted to 2.2, and saw that my temps were @ ~50°C, so I was a little concerned. I just updated to the Creators Update last night, and thought maybe that was behind it. Then I realized I was folding, paused it, and then my temps went back down to the mid-30s.

SO.. If I was seeing temps around ~60°C while folding on 2.3, that's still approximately a 10° increase over 2.2. 

My 4Ghz/3200Mhz overclock runs fine on 2.2, with low temps, so I'm gonna' stick with 2.2 for now. No point in using 2.3 when it didn't fix the Restart to UEFI issue. I probably wouldn't have kept it anyway, given the increase in temp.

When we have a BIOS with the new microcode, I'll give that whirl. All I really care about now is reducing my startup times and system stability. I'm beginning to doubt that we'll see 3600 on the first iteration of Zen. They'll probably use that as a selling point for Zen+ to try and lure some of the early adopters away from 1st gen, so I think I've taken this system as far as it can *safely* go (apart from upgrading to a 960 Pro, but SSD prices are skyrocketing right now and I doubt that will change anytime soon).

1.

1800X @ 4000 / 1.375V / LLC 4 & 3

https://www.newegg.com/Product/Product.aspx%3FItem=N82E16820232530" rel="nofollow - F4-3200C14D-16GFX  x 2 (16GB) @ 3200 / 1.35V

Samsung 950 Pro 512GB / M.2_1

http://www.ebay.com/sch/i.html%3c_nkw=windows+10+pro+64bit" rel="nofollow - Windows 10 Pro 64bit  / v.1703 b.15063.332

2.

v2.2 -> v2.4

3.

BIOS / Instant Flash

4.

The temperature issues I noticed in 2.3 have disappeared. Hovering around ~30-40°C now. So that's a step in the right direction ;)

Still no progress on the boot up issue. Still fails during the first try, so Restart to UEFI does not work.

I have never really had a need to try that.. not with these FlareX sticks. At least, not to get the system to boot/function at max speed. I paid the premium for them so I wouldn't have to mess with a bunch of settings.

Should I poke around in there? What would I be looking to change?

When powering the computer on, or restarting it, I can hear the fans spin up. My monitors will sometimes blink on as well (just the little power light indicators changing from Orange to Blue). Then, the fans die off almost entirely, and the monitors revert back to Standby mode (waiting for input). Then the fans whir up again, the monitors indicate they've received a signal, and the computer boots as normal.

The best way I can describe it is a "stutter" start. Comes on, tries to start, fails, tries again and succeeds.

Correct me if I'm wrong, but don't you have to use the same memory (speed, capacity, etc) in concert with one another?

One thing I did set to Level 1 both CPU Load-Line Calibration and VDDCR Load-Line Calibration.

That's your system restarting itself after failing to post at the DRAM settings that you have set it at.  Unless you go into DRAM Timings Configuration to change the Fail Count, the system will try 3 times before defaulting back to 2400mhz.

Mojobaggins wrote: With the new 2.4 bios, I am finally able to get my G.Skill FlareX F4-3200C14D-16GFX to run at 3333mhz at CL14-14-14-34 using the XMP settings wtih my R7 1700 at 3.9ghz.

Glad to hear you've made some progress!

I think there's a way to disable the ASRock splash screen, which would enable the AM screen.. I'm not sure, but that might show what you're looking for.

The problem with that explanation..  

Nevermind. Disabling "Full Screen Logo" will only show you what UEFI version you're on. Not RAM/CPU speed info. That was what you were after, right?

MisterJ wrote: Could this be the tuning* going on during boot?  Have you tried disabling the tuning, or is this a bad idea?  Thanks and enjoy, John. EDIT:  *I should have called this "Advanced Boot Training". ..I suspect this was the "training".  You did not say what you meant by "Still fails during the first try", but I thought it may be the boot training.  It seems most are trying to disable it to reduce boot time.  I have not tried it at all.  Restart to UEFI works fine for me.  If you think this may be useful, I suggest give it a try.  Enjoy, John.

Well, wouldn't you know it. Bingo-presto..! You were right. Disabling AM4 Advanced Boot Training did the trick. I can use Restart to UEFI now! Not only that, but my boot times have dropped from 14.4 to 12.1 seconds. That's right around the startup time of my 8350. It's still nowhere near the startup time of my laptop, but it's progress in the right direction ;) THANK YOU!

What in the world was that meant to help with? Does it matter, considering the system was failing to start with it enabled?

I'm now thinking this isn't the best strategy. Even though I've conditioned myself to save my work frequently, it would be better, if for only the sake of my peace of mind, that I ran a stress test. What do you normally use?

Loaded Agesa 2.40 today and tried to load xmp 1.0 profile to run memroy at 3200mhz - FAILED

set it back to auto by default.

Then tried to overclock cpu (1700x) to 3800 and reboot - FAILED

Basically the system would turn on and off 3 times then booted into Window with cpu/memory running at factory setting. 

I would really appreciate if someone can shed some light on how to overclock on this board. This is my first experience with Asrock board ever (been with ASus for the past 20 years and everything was smooth - never even a hiccup).

Thanks in advance

Here is my system spec:

- Ryzen 1700X

- Asrock X370 Fatal1ty professional gaming (bios Agesa 2.40)

- G.Skill 8gig x 2 DDR4 3200 Flare X series 14-14-14-34 CAS 14 (F4-3200C14D-16GFX)

- Powercolor 580X 8 gig

- EVGA G3 750 80 Gold

- EVGA clc 280 AIO

- 960 EVO M.2

- 860 EVO SSD

What do you have set for Voltage Mode?

LLC?

Voltage for RAM?

AM4 Advance Boot Training?

EDIT:

Here are some screen caps from an earlier BIOS revision with my settings. The only thing I have done differently is that I am no longer using AM4 Advance Boot Training:

https://ibb.co/dJumVv" rel="nofollow"> https://ibb.co/cErBxa" rel="nofollow"> https://ibb.co/nQ76Vv" rel="nofollow">

EDIT2:

Without setting "CPU Load-Line Calibration" to Level 3 and "VDDCR_SOC Load-Line Calibration" to Level 4, I am unable to Post. I can't confirm the same for "Voltage Mode", but that doesn't mean it isn't necessary; I just haven't tested it without it tuned to "OC Mode".

Interesting.. OC'in the CPU as well? What voltage do you have the RAM set to?

Yes, 1700 oc'd to 3.8 at 1.3v and I haven't touched a thing for the ram except use the XMP profile so it's using 1.35v

I tried to oc'd the ram higher with no luck but all I did was try to loosen the timings to 16-16-16, I didn't increase the volatage at all.