X370 Taichi BIOS 2.00 |
Post Reply | Page <1234> |
Author | |
Nocturnal
Newbie Joined: 21 Mar 2017 Status: Offline Points: 37 |
Post Options
Thanks(0)
|
Thank you. I understand, so lets now wait for Command Rate = 2 setting in new BIOS.
|
|
datonyb
Senior Member Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
|
nocturnal
it would seem that in fact gigabyte are ALSO having 1004 reported in aida as 1003 but in fact it is 1004 "quote" We find in the latest BIOS dated new versions for these three components:
AMD confirmed to us that microcode 800111C brings well the fix for the bug of the FMA3. The AGESA 1.0.0.4a (which you will also find under the notation 1.0.0.3a in some manufacturers like Gigabyte) brings on its side the improvement of latency. We do not know what the EMS update does, it does not seem to correct existing bugs like the fact that we sometimes find ourselves with voltage readings (more precisely VID) blocked at 1.55V by example. source : https://translate.googleusercontent.com/translate_c?depth=1&hl=en&prev=search&rurl=translate.google.co.uk&sl=fr&sp=nmt4&u=http://www.hardware.fr/articles/959-5/nouvel-agesa-diminuer-latence-ram.html&usg=ALkJrhh2jnBon0Nrtnxt8dw7b3IH_XowMA sorry long url as its also translated from french to english |
|
[url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
|
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
That is the gods honest truth. It took me three days of major Time Zone differences to make that point to them. It's good to read they answered you correctly. MSI is now having this same issue over on their forums. One User even stated he had read that the file(s) had actually come from AMD with the incorrect versioning stated with in. Regardless, I have extracted the microcode and compared it side by side to a KNOWN 1.0.0.4b and this I state above is correct concerning versioning. So let's move along concerning this and cease with the conspiracy theories. It doesn't make anyone appear smart just spouting off rumors, whining, and uttering conjecture. |
|
Nocturnal
Newbie Joined: 21 Mar 2017 Status: Offline Points: 37 |
Post Options
Thanks(0)
|
I've written to support and today they answered me. Briefly:
"We forgot to update string in BIOS file that identifying AGESA version. Don't look at this." But to be honest I don't believe. I think support don't have enough time to all this work with bioses, agesa, memory compatibility issues etc. Marketing considerations don't allow to say client truth. But such situation is bad, it decline users loyalty. |
|
datonyb
Senior Member Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
|
it would appear they answered in another thread unrelated to the agesa question
and that answer seems to be it is 1004 but is incorrectly reported as 1003 |
|
[url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
|
Nocturnal
Newbie Joined: 21 Mar 2017 Status: Offline Points: 37 |
Post Options
Thanks(0)
|
We need new BIOS with new AGESA and support CR2, as many another vendors MB already have it
|
|
mysticjbyrd
Newbie Joined: 27 Mar 2017 Location: USA Status: Offline Points: 36 |
Post Options
Thanks(0)
|
That would explain why I didn't see any latency improvements that others were talking about.
|
|
Is "God" able, but not willing to stop evil? Then he is malevolent.
Is he both able and willing? Then whence cometh evil? Is he neither able nor willing? Then why call him God??? ??Epicurus |
|
Nocturnal
Newbie Joined: 21 Mar 2017 Status: Offline Points: 37 |
Post Options
Thanks(0)
|
Support ignore us. We bought sup-top board, but there is no support.
|
|
lowdog
Newbie Joined: 16 Apr 2017 Location: Australia Status: Offline Points: 194 |
Post Options
Thanks(0)
|
Pretty sure as well bios 2.0 is AGESA 1.0.0.3 and the code string ends in xxxx111C which is the same code MSI was using in their beta 1.4x bios that they pulled because it could potentialy damage boards.
A mod or ASRock rep needs to investigate this and confirm one way or another because ASRock should be using AGESA 1.0.0.4a or 1.0.0.4b code now which is what all other vendors are using and NOT still be using code 1.0.0.3 which has potentialy hardware bricking bugs. |
|
Nocturnal
Newbie Joined: 21 Mar 2017 Status: Offline Points: 37 |
Post Options
Thanks(0)
|
it's not so because memory latency is not fixed as on other motherboards |
|
Post Reply | Page <1234> |
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 |