AGESA 1.0.0.6b

It would seem that this latest BIOS is a few steps back. The board takes longer to boot, and p-states are completely broken for me.

There are tons of new option in the recent BIOS updates that are completely undocumented. They either don't have descriptions, or the description are super vague, and they are not in the manual at all. Every option in the BIOS has a QR code for the same PDF manual hasn't been updated ever.

Also what's going on with the ASRock software? F-stream just doesn't work at all anymore for me, even after a fresh Windows install.

seanpatrick wrote: P-state overclocking does indeed seem to be problematic with this Bios.   Although the processor is indeed downclocking, the Vcore barely moves at lower speeds - in fact I'm getting fairly large Vcore spikes with it.   For instance, I run an offset that usually brings my Vcore under stress testing to about 1.392 (I'm overclocking obviously) however with the new bios it stays at or near 1.392 even when the processor speed is at about 1.5mhz.  In addition I'm getting spikes with the same offset I've used for the last 4 bios updates up to about 1.488!  I've since switched back to the previous one and all is returned to normal with the Vcore dropping to .9 something when the cores are idle at 1.5mhz.

When they will release the update for chipsets b350, i have asrock b350

By thew way it is possible that Asrock manufacturer unlock the Promontory options and add a way to disable ASMEDIA controllers through Bios? also adding an HPET 32 bit or 64 bit?

Looks i have locked this PROMONTORY OPTIONS:
PROM4, PROM2, PROM1 are locked i cannot enter.
And it seems that there is the culprit or problem of my mouse inconsistent hz


Another thing is that i don't get it must be something wrong with my motherboard or with the asrock ab350 fatality k4 gaming, they add a F-STREAM software to changes polling rate hz on F-PORTS, but when downloading the software it came like with features locked, there is no such options like (TOOLS)

This is the pictures of F_STREAM that asrock shows for my mobo



And when downloading the software through my manufacturer motherboard model
This is what i get, there is not tools options or whats so ever.




So with all of this problem i'm getting inconsistent HZ this never happen before in my old machine :/ things what i have do.
1- Turning off C6, al C-states
2- Turning AMD COOL& QUIET
3- Disabling all SUPER IO in bios

In device manager windows turn off (saving features on hid and usb controllers)

And problem persist:
this is how it looks the hz.
1000hz


500hz


333 hz


250hz


200hz


125hz
http://cdn.overclock.net/0/08/08accf6d_125hz.png

And yes i have tried my g9 on all usb ports and type C, also the F-ports and i test my 3.0 usb mice logitech m100 which is a cheap mouse and it doesnt work properly, HZ are fluctuating...

People in other forums spoke me about the ASMEDIA in bios hidding and promontory options, plus some... problems attached to HPET that are in 32 bit which would be fine if AMD release hpet 32 and 64. thanks.

Edited by x58haze - 08 Sep 2017 at 5:47am

AlbinoRhino wrote: 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.

The AGESA block was updated and being so will make a diff.

What wasn't touched was the AGESA loader and mem training routines.



And I agree. More info is always nice.

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