AGESA 1.0.0.6b |
Post Reply | Page 123 12> |
Author | ||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
Posted: 06 Sep 2017 at 10:32am |
|
Share your experiences.
But please, before beginning any LONG troubleshooting, begin a new Thread. And remember, whether asking or answering, to have created a Sig so others know what you have. Thanks, .... wardog Edited by Xaltar - 02 Feb 2018 at 8:54pm |
||
AlbinoRhino
Newbie Joined: 28 Apr 2017 Status: Offline Points: 153 |
Post Options
Thanks(0)
|
|
Performance is degraded significantly on the Killer SLI A/C using the same Bios settings when updating from v3.1 to v3.2.
-221 points in Cinebench. Performance score dropped from almost 1700 points down to 1470.
|
||
Asrock X370 Killer SLI A/C Rev 1.03 b3.1, Ryzen 1700X - 3.9@1.34V, Nvidia Geforce GTX1080 FTW2 ICX, 2x8GB Corsair Vengeance LED 3200@2933Mhz (3200 unobtainable)
|
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
grenrozo
Newbie Joined: 17 Apr 2017 Status: Offline Points: 13 |
Post Options
Thanks(0)
|
|
no changes in Cinebench by my side - Ryzen 1600X @Fatal1ty X370 Gaming K4 (bios cleared before update).
|
||
AlbinoRhino
Newbie Joined: 28 Apr 2017 Status: Offline Points: 153 |
Post Options
Thanks(0)
|
|
The procedure I used is one that I've always used. 1. Download bios, unpack it to my USB drive. 2. Boot into UEFI, Load Bios Defaults, Save and Exit, reboot into Windows once. 3. Boot into UEFI, flash new Bios, Save and Exit. Load Windows once. 4. Boot into UEFI, apply CPU OC, Save and Exit. Boot into Windows once. 5. Boot into UEFI, apply RAM OC, Save and Exit. Boot into Windows, Benchmark. As soon as I reverted back to 3.1 using the above method my scores are normal again. Next I will clear the CMOS with a battery pull and a jumper reset to see if it makes a difference. |
||
Asrock X370 Killer SLI A/C Rev 1.03 b3.1, Ryzen 1700X - 3.9@1.34V, Nvidia Geforce GTX1080 FTW2 ICX, 2x8GB Corsair Vengeance LED 3200@2933Mhz (3200 unobtainable)
|
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
Meh, you don't need to go to Windows FYI.
As far as you doing RAM and CPU separately, ... well, that's something I don't do either. BUT, if on the odd chance after flashing it kept any Saved Profiles, consider the junk/toast and overwrite them once on the new BIOS. Never, NEVER, reuse them from one BIOS to another. Big no no. |
||
AlbinoRhino
Newbie Joined: 28 Apr 2017 Status: Offline Points: 153 |
Post Options
Thanks(0)
|
|
No profiles are saved. You also can't use a profile you've saved on a USB drive on an alternate Bios. Ex: a saved profile from 3.1 will not be recognized at all on 3.2.
I do my CPU OC first since I always attempt a lower CPU voltage to see if the new Bios improves it. The RAM OC is simply setting XMP to 2933 since I've given up on 3200 and cannot remember how I got 3066 stable. I wasn't expecting a change in the XMP profile this go around since it stated in the release notes that the compatibility code wasn't touched. Kudos to ASRock on the change notes BTW. |
||
Asrock X370 Killer SLI A/C Rev 1.03 b3.1, Ryzen 1700X - 3.9@1.34V, Nvidia Geforce GTX1080 FTW2 ICX, 2x8GB Corsair Vengeance LED 3200@2933Mhz (3200 unobtainable)
|
||
Ricky
Newbie Joined: 25 Jun 2017 Status: Offline Points: 43 |
Post Options
Thanks(0)
|
|
Is pstate oc with CPU voltage offset broken in Bios 3.20? Since i notice the CPU Vcore is not consistent in Bios or is it a display error and readout bug? For example, in previous Bios 3.10, i will add 0.08125v under CPU offset voltage to reach Vcore 1.248v. From H/W Monitor in bios, the Vcore is quite stable and always shown 1.248v every time i check it. For Bios 3.20, i also do the same by adding 0.08125v CPU offset voltage to get Vcore 1.248v. But, somehow the H/W Monitor in Bios display the Vcore as 1.298v. So, i reboot the system and check it again in Bios, this time it show Vcore 1.248v. But after i try to reboot and check it again in bios at 3rd time , the Vcore will show 1.298v. In other words, with pstate oc and CPU voltage offset in Bios 3.20, the CPU Vcore in Bios become different each time after we reboot the system. As a result, i cannot set an accurate value of CPU Vcore. Besides, i don't use any user profile and will always clear cmos / reset default before flashing to new Bios. And this issue will not happen if i use OC Tweaker in Bios to OC the CPU. So, i think maybe is some bug with Bios 3.20? Fyi, i use LLC level 4 and using Asrock X370 K4.
Edited by Ricky - 07 Sep 2017 at 2:57am |
||
Ken429
Newbie Joined: 30 Sep 2015 Location: Indiana Status: Offline Points: 225 |
Post Options
Thanks(0)
|
|
Updated the BIOS on my Taichi from 3.0 to 3.1. IBT ran ~160.16 seconds on 3.0 and 163.09 seconds on 3.1. The max core temp increased from 65.5C to 67.5C. Cinebench cpu numbers went from 1718 on 3.0 to 1717 on 3.1 and the OpenGL numbers went from 95.35 on 3.0 to 94.66 on 3.1. I guess the differences could be attributed to needle quiver!?
However, using Pstates for the 3.9GHz OC under 3.1 the minimum idle Vcore drops to ~.368V versus the .900V in Pstate2. The minimum cpu speed dropped to 2200 as it should have based on the Pstate2 settings. That is a step backward from 3.0 where the minimum Vcore and cpu speed were the same as Pstate2 specified. Edited by Ken429 - 07 Sep 2017 at 4:21am |
||
X470 Taichi, 3800X (BIOS Defaults), BIOS v3.60, Sandisk Extreme Pro 240GB, 2 crucial MX500 1TB, G.Skill 2X 2X8 3200-14, EVGA 1660Ti SC, EVGA 750 G3, W10 1903
|
||
Ricky
Newbie Joined: 25 Jun 2017 Status: Offline Points: 43 |
Post Options
Thanks(0)
|
|
downgrade back to Bios 3.10, no more issue like this. Waste few hours on this
|
||
Post Reply | Page 123 12> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |