ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - Ryzen 2xxx AGESA Code Potential Issues
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Ryzen 2xxx AGESA Code Potential Issues

 Post Reply Post Reply Page  <123
Author
Message
cristy6100 View Drop Down
Newbie
Newbie
Avatar

Joined: 15 Mar 2018
Location: Romania
Status: Offline
Points: 175
Post Options Post Options   Thanks (0) Thanks(0)   Quote cristy6100 Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2018 at 6:33pm
I have not tried the XFR because the values are in HEX I think, yes its just enabled/disable for the function, and you can set the power limits (those are the actual XFR 2.0 settings), and not documented, but I have tested the CPU up to 4150MHz with 1.45V, and the GPU up to 1650 with 1.25V, I can pass IntelBurnTest @ 4150MHz with maximum stress setting 10 passes, and the GPU I have played CS:GO for about 5-6 hours straight @ 1650MHz with no problems.
My opinion is that it overclocks ok, both the GPU and CPU part, but the actual procedure is not that straight forward in UEFI plus you loose the adaptive frequency/voltage scaling when idle, I tried with P-State but you also lose some of the power states, so for now I just run stock with turbo disabled because of the throttle bug when turbo is enabled, maybe next UEFI will fix it.

PS: you also loose the GPU adaptive frequency when you overclock it, instead of downclocking the GPU will stay at 1650MHz even in idle, and thats not good, until they fix these bugs better without OC


Edited by cristy6100 - 18 Apr 2018 at 6:41pm
Main Rig: AMD Ryzen 2400G | ASRock Fatality X370 ITX/ac BIOS 4.60 | Corsair LPX DDR4 2400@3200 1.35V | Corsair RM650i PSU | CM ML120L AiO Cooler
Back to Top
stree View Drop Down
Newbie
Newbie


Joined: 17 Dec 2015
Location: Lincolnshire
Status: Offline
Points: 239
Post Options Post Options   Thanks (0) Thanks(0)   Quote stree Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2018 at 10:28pm
thanks for that useful info and insight cristy600.
ASRock X370-ITX BIOS 4.50 2400G
16GB Ballistix Sport LT 2933
960Evo M.2 256GB, Firecuda 1TB
Win 10 Pro 64 1709
G-Unique Archdaemon 300 watt power
Realan E-W80 case
Back to Top
ShampooCA View Drop Down
Newbie
Newbie


Joined: 13 Jun 2017
Status: Offline
Points: 61
Post Options Post Options   Thanks (0) Thanks(0)   Quote ShampooCA Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2018 at 10:47am
There's XFR 2.0 and XFR 2.0 enhanced.
They're different.
Please have a look at AMD.
Back to Top
Reinvented View Drop Down
Newbie
Newbie


Joined: 22 Jun 2017
Status: Offline
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote Reinvented Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2018 at 1:25pm
I too have these same problems with PUBG and BF1.  I started a dialogue with ASRock Support about 4.60 for Taichi.  I have better stability on 4.60 compared to 3.20 overclocked.  But, 4.60 does not play well with these two applications and a few other things, like 3.20 does.  Hopefully this gets resolved soon. 
Back to Top
cristy6100 View Drop Down
Newbie
Newbie
Avatar

Joined: 15 Mar 2018
Location: Romania
Status: Offline
Points: 175
Post Options Post Options   Thanks (0) Thanks(0)   Quote cristy6100 Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2018 at 5:08pm
I will try to explain again:  XFR 2.0 (the enhanced part means its configurable tru' UEFI) will work on all X370 boards with Ryzen 2xxx CPU if the manufacturer of the board did not lock/disable/hide the option on porpouse, in case of ASRock they did leave the option enabled fully, so its enabled and configurable. Asus on the other hand removed/renamed the option, so did Gigabyte as far as I understand. Its just for marketing purpose because on the high end side there is 0 difference between X370 and X470, you need to understand that its the same silicone just made on a newer fab node for lower TDP, there is no additional logic vs X370, all "new" functions of X470 where added to X370 by ASRock with a UEFI update

EDIT: It seems ASRock (I hope temporary) is not listing the 2700X as compatible with the Fatality X370 ITX/ac and Fatality AB350 ITX/ac, for some unknown reason, all other X370 boards do list the 2700X, if they indeed do not certify the 2700X on these two boards its just because they released the X470 ITX/ac and this is called planned obsolence that the UE Commision is not very fond of


Edited by cristy6100 - 20 Apr 2018 at 2:34am
Main Rig: AMD Ryzen 2400G | ASRock Fatality X370 ITX/ac BIOS 4.60 | Corsair LPX DDR4 2400@3200 1.35V | Corsair RM650i PSU | CM ML120L AiO Cooler
Back to Top
JohnM View Drop Down
Newbie
Newbie
Avatar

Joined: 20 Feb 2018
Location: UK
Status: Offline
Points: 217
Post Options Post Options   Thanks (0) Thanks(0)   Quote JohnM Quote  Post ReplyReply Direct Link To This Post Posted: 22 Apr 2018 at 11:55am
Originally posted by cristy6100 cristy6100 wrote:

It seems ASRock (I hope temporary) is not listing the 2700X as compatible with the Fatality X370 ITX/ac and Fatality AB350 ITX/ac, for some unknown reason, all other X370 boards do list the 2700X, if they indeed do not certify the 2700X on these two boards its just because they released the X470 ITX/ac and this is called planned obsolence that the UE Commision is not very fond of

No, I don't think so. More likely it's just an omission. I haven't checked the X370 ITX but on the Specification page for the B350 ITX under CPU it says:

"Supports 105W Water Cooling (Pinnacle Ridge); Supports 95W Water Cooling (Summit Ridge); Supports 65W Water Cooling (Raven Ridge)"
ASRock Fatal1ty AB350 ITX P4.60, AMD Ryzen 5 2400G, 2x8GB Corsair CMK16GX4M2A2666C16, 250GB Samsung 960EVO, 500GB Samsung 850EVO, 4TB WD Blue, Windows 10 Pro 64, Corsair SF450, Cooler Master Elite 110
Back to Top
 Post Reply Post Reply Page  <123
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.06
Copyright ©2001-2016 Web Wiz Ltd.

This page was generated in 0.047 seconds.