ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - AGESA 1.0.0.6b
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

AGESA 1.0.0.6b
 Post Reply Post Reply Page  <1 45678 12>
Author
Message Reverse Sort Order
  Topic Search Topic Search  Topic Options Topic Options
nangu View Drop Down
Newbie
Newbie
Avatar

Joined: 06 Jul 2017
Status: Offline
Points: 120 		Post Options Post Options   Thanks (0) Thanks(0)   Quote nangu Quote  Post ReplyReply Direct Link To This Post Posted: 20 Sep 2017 at 11:30pm
Was a little bored yesterday and decided to take another shoot at memory OC.

Tried 3066, managed to get it past boot and stress test it on Windows. After two hours of stress testing while watching a stream without errors, decided to look at some benchmarks to compare with my previous results @2933.

Rebooted to UEFI, adjusted fan curves a bit, save, restart, and bam!! Dr Debug's F9 festival. I couldn't boot anymore with memory @3066 :-(

I think AMD and motherboard's vendors need to address this cold boot / memory training problems. I find hard to believe a setting which is stable at stress testing, never sticks at reboot or cold boot.

Tha same applies at memory's voltage at boot. I can run perfectly stable @2933 at my memory rated voltage of 1.35v, but It need 1.375v to avoid F9 fest at cold boot. Hint: We need memory boot voltage setting in UEFI as ASUS boards.

Also, going from @2933 to @3066 needs a lot of voltages increase (when it posts if you're lucky enough). VDram from 1.375v to 1.40v, SoC from 0.92v to 1.1v.

I don't know where the culpruit lies: It's a weak IMC controller on the CPU? It's a memory automatic settings and/or training issues? It's a poor DDR4 design on motherboard?

I know AMD's specs lists @2666 as max memory supported btw, so @2933 I can reach stable is a bonus actually, but I think there is a problem somewhere anyway, because a stress test stable RAM @3066 on Windows which doesn't past training 9 of 10 times, it's an AGESA and/or UEFI design problem in my books. 

Thanks for reading, and sorry for my little rant :-) 
R7 1700 @3.90 1.25v - GSkill TridentZ 3200c16 Hynix MFR @2933 14-16-16-32 - Fatal1ty Gaming X370 K4 - Gigabyte GTX 1070 G1 - WD 256 Black M2 Nvme as Windows 10 boot drive - EVGA Gold 650W
Back to Top
SternRabbit View Drop Down
Newbie
Newbie


Joined: 20 Sep 2017
Status: Offline
Points: 7 		Post Options Post Options   Thanks (0) Thanks(0)   Quote SternRabbit Quote  Post ReplyReply Direct Link To This Post Posted: 20 Sep 2017 at 9:18pm
I agree with lowdog, something indeed is wrong.
Same setup here with pstates but volts could be up to 0.05v higher than before or lower.
My lowest voltage is 0.384v vCore and highest up to 1.41v vCore
Previously it was 0.880v vCore and 1.36v vCore.

If i have 1.36v i have a low of 0.384v
If i have 1.41v i have a low of 0.880v

Changes with every boot

CPU LLC1
SoC LLC3



Edited by SternRabbit - 20 Sep 2017 at 9:36pm
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: 20 Sep 2017 at 4:57am
Originally posted by datonyb datonyb wrote:

you know llc 5 is the weakest ?
llc 2 or 1 is the tightest to maintain voltage as set

i ask because if i was having voltage move about more than i wanted MY llc would be set to level 1



As I mentioned these are the exact same settings I had in bios 3.0 with Agesa 1.0.0.6a and it did not exhibit the same behaviour that is occurring with bios 3.10 with Agesa 1.0.0.6b......the problem lies in the new bios.

Edited by lowdog - 20 Sep 2017 at 4:58am
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
seanpatrick View Drop Down
Newbie
Newbie
Avatar

Joined: 28 Apr 2017
Location: Toronto
Status: Offline
Points: 8 		Post Options Post Options   Thanks (0) Thanks(0)   Quote seanpatrick Quote  Post ReplyReply Direct Link To This Post Posted: 20 Sep 2017 at 2:47am
This is a problem with the BIOS and p-state overclocking, perhaps with voltage offsets - it's not attributable to LLC adjustments in this context.
Back to Top
datonyb View Drop Down
Senior Member
Senior Member


Joined: 11 Apr 2017
Location: London U.K.
Status: Offline
Points: 3154 		Post Options Post Options   Thanks (0) Thanks(0)   Quote datonyb Quote  Post ReplyReply Direct Link To This Post Posted: 20 Sep 2017 at 1:26am
you know llc 5 is the weakest ?
llc 2 or 1 is the tightest to maintain voltage as set

i ask because if i was having voltage move about more than i wanted MY llc would be set to level 1
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
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: 19 Sep 2017 at 6:14pm
Originally posted by foppe foppe wrote:

Question is, dare I install this with the reports about cpu voltages running rampant on a few other motherboards that got this update?



I'm on the X370 Pro Fat Gaming and bios 3.10 with the 1.0.0.6b Agesa does indeed have a vcore problem. With the same P state setting I did with bios 3.00 which gave me a solid stable vcore of 1.344/1.36 load with Level 5 LLC this bios will give the same vcore with the same settings.... BUT!!!...it gradually creeps up over time till it's sitting at 1.4V almost constantly, even when idle and hardly down clocks.....temps are pushing 50C when the comp is just idleing.

This bios has a SEVERE vcore issue that need reporting to Asrock ASAP before cpu's start frying.

Going to flash back to 1.0.0.6a bios 3.00 till this overvolting vcore creep up is sorted in a new bios.

Edited by lowdog - 20 Sep 2017 at 4:59am
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
GabyGancia View Drop Down
Newbie
Newbie
Avatar

Joined: 17 Sep 2017
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote GabyGancia Quote  Post ReplyReply Direct Link To This Post Posted: 17 Sep 2017 at 7:44am
Hi, I want to raise the memory at 3000Mhz but It wasn't possible with my current configuration, only up 2666Mhz. Should I update to BIOS 3.30? Will I get any benefit if I update?
Thanks!
Ryzen R7 1700 @3.7Ghz
Asrock X370 Gaming K4 Bios 3.00
Corsair 2x8Gb @2666Mhz CMR16GX4M2C3000C15
Back to Top
Denroth View Drop Down
Newbie
Newbie
Avatar

Joined: 02 Apr 2017
Status: Offline
Points: 46 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Denroth Quote  Post ReplyReply Direct Link To This Post Posted: 16 Sep 2017 at 10:05pm
Originally posted by wardog wardog wrote:

Originally posted by Denroth Denroth wrote:

@wardog
so should I install this latest bios on x370 killer?


Absolutely.

You still have that Killer SLI? Absolutely.

All my Sammy B-Die kits love 1.0.0.6b


Thanks man <3 with the new bios I can overclock ram at 3066mhz :D (stable)

https://i.imgur.com/qggKdLD.png




Edited by Denroth - 16 Sep 2017 at 10:06pm
Ryzen R7 1700 3.8ghz 1.3v| Msi R9 390 8GB DDR5| Ram GSkill Ripjaws V 3200mhz b-die F4-3200C15D-16GVR(3066mhz)
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: 16 Sep 2017 at 11:12am
Originally posted by PinetreeRoad PinetreeRoad wrote:

After reading a few comments saying they didn't have increased boot times, i decided to reinstall the v3.10 BIOS. So i rolled back the BIOS to v3 and reinstalled v3.10 (both) from a USB drive this time and i no longer have the increased boot times i bitched out before.

So i'm wondering if my boot issue was related to installing the BIOS through the internet flash utility within the v3 BIOS. Maybe it was just a fluke.

So for the record if anyone else had issues with the latest BIOS increasing boot times, roll back the BIOS and reinstall the latest BIOS.

I also want to point out a bug  that has been present in the BIOS for a few versions, as it seems nobody is aware of it. If you apply a saved on board profile while in UEFI mode (CSM disabled) the BIOS will completely freeze. It doesn't recover, and you have to manually power down the system. It will still apply all the settings from the profile though (you can verify this after force rebooting). With CSM enabled profiles apply as expected.


Myself and a few others are aware and have mentioned the bug (in other threads) where loading a profile in the UEFI/BIOS with CSM disabled causes the freezing of the UEFI as you described. Installing Windows and running the board's firmware in full UEFI booting mode (CSM disabled) is still rare and not done by many people.

This is an odd bug, since I have been setting CSM to disabled on my many ASRock boards since my Z77 Extreme4 board, and every Intel Z chipset, X99, and an AMD 970 board since then, and have never experienced this even once. As you said, it is also not a new bug for Ryzen board UEFIs, although I forget if the very early UEFI versions for my board had this bug.

Also, I'm not sure about the profile being applied after the UEFI freezes. Personally, I press the Reset button when I was stuck with the UEFI freeze. Powering down the board when there is a UEFI/BIOS problem, such as a failed UEFI update, is not at all recommended, and can result in a bricked board. This loading a profile situation may be different than that, but I've seen too many bricked boards after powering down after a UEFI update failure, which sticks in my mind. Powering down the PC as you do should not perform a Save and Exit of the UEFI, or if the Reset button is pressed. It may be that loading a profile automatically applies it without doing a Save and Exit, but that would be new information to me. You may be correct, I'm just not sure.

As a workaround, we could set CSM to enabled, Save and Exit, go right back into the UEFI, load the profile (with CSM disabled), and Save and Exit when complete. A bit cumbersome, but at least no freezing in the UEFI.

Thanks for pointing this out, the more that do, the more likely it will be addressed.
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: 16 Sep 2017 at 2:47am
Originally posted by Denroth Denroth wrote:

@wardog
so should I install this latest bios on x370 killer?


Absolutely.

You still have that Killer SLI? Absolutely.

All my Sammy B-Die kits love 1.0.0.6b
Back to Top
 Post Reply Post Reply Page  <1 45678 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.078 seconds.