ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - PSA: Stay away from 4.80 BIOS X370 Taichi
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

PSA: Stay away from 4.80 BIOS X370 Taichi

 Post Reply Post Reply Page  <1 23456 15>
Author
Message Reverse Sort Order
Jpe1701 View Drop Down
Newbie
Newbie


Joined: 19 Aug 2018
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jpe1701 Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2018 at 4:49pm
I tried different GPU and memory and disconnecting my SATA devices and I still get an E6 code with no post on 4.81 with pbo enabled. I reported it to ASRock support and they said they hadn't heard of the problem so I pointed them to ocn Taichi thread.

Edited by Jpe1701 - 23 Aug 2018 at 4:50pm
Back to Top
xhue View Drop Down
Groupie
Groupie


Joined: 17 Aug 2018
Status: Offline
Points: 634
Post Options Post Options   Thanks (0) Thanks(0)   Quote xhue Quote  Post ReplyReply Direct Link To This Post Posted: 23 Aug 2018 at 1:57am
Originally posted by virpz virpz wrote:

Originally posted by xhue xhue wrote:

Definately open a ticket too. Not that I ever got a response, though.

JZ's ability to help is limited.

That's classic AsRock.
I opened a new "ticket" listing the issues again and it's been twelve days, no answer. Clap



Check what this guy has to say: http://forum.asrock.com/forum_posts.asp?TID=9465&title=asrock-support-doesnt-bother-replying

Basically, he's suggesting to write an email directly, as if you're going to RMA. Maybe it's worth a shot?

Also, JZ has been really quiet on the other issues. I hate this type of silence.
Back to Top
virpz View Drop Down
Newbie
Newbie


Joined: 08 Aug 2018
Status: Offline
Points: 27
Post Options Post Options   Thanks (0) Thanks(0)   Quote virpz Quote  Post ReplyReply Direct Link To This Post Posted: 22 Aug 2018 at 8:43pm
Originally posted by xhue xhue wrote:

Definately open a ticket too. Not that I ever got a response, though.

JZ's ability to help is limited.

That's classic AsRock.
I opened a new "ticket" listing the issues again and it's been twelve days, no answer. Clap



Edited by virpz - 22 Aug 2018 at 8:43pm
Back to Top
xhue View Drop Down
Groupie
Groupie


Joined: 17 Aug 2018
Status: Offline
Points: 634
Post Options Post Options   Thanks (0) Thanks(0)   Quote xhue Quote  Post ReplyReply Direct Link To This Post Posted: 22 Aug 2018 at 1:21pm
Definately open a ticket too. Not that I ever got a response, though.

JZ's ability to help is limited.
Back to Top
shmerl View Drop Down
Groupie
Groupie


Joined: 23 Oct 2017
Status: Offline
Points: 612
Post Options Post Options   Thanks (0) Thanks(0)   Quote shmerl Quote  Post ReplyReply Direct Link To This Post Posted: 22 Aug 2018 at 8:15am
OK, I reverted back to 4.64, and virtualization issue is gone. So it's surely a bug in the firmware.

Originally posted by J Z J Z wrote:

See Link...


Can you direct it to Asrock please, or I should open an official ticket to report the bug?



Edited by shmerl - 22 Aug 2018 at 8:17am
Back to Top
shmerl View Drop Down
Groupie
Groupie


Joined: 23 Oct 2017
Status: Offline
Points: 612
Post Options Post Options   Thanks (0) Thanks(0)   Quote shmerl Quote  Post ReplyReply Direct Link To This Post Posted: 22 Aug 2018 at 7:25am
I spoke too soon. Virtualization stopped working for me with 4.81 (on Debian testing Linux). Even though I enabled SVM in the firmware, qemu/kvm are not working anymore:

Error starting domain: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.

Strangely, lscpu shows virtualization as available:

lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              16
On-line CPU(s) list: 0-15
Thread(s) per core:  2
Core(s) per socket:  8
Socket(s):           1
NUMA node(s):        1
Vendor ID:           AuthenticAMD
CPU family:          23
Model:               8
Model name:          AMD Ryzen 7 2700X Eight-Core Processor
Stepping:            2
CPU MHz:             2100.526
CPU max MHz:         3700.0000
CPU min MHz:         2200.0000
BogoMIPS:            7400.34
Virtualization:      AMD-V
L1d cache:           32K
L1i cache:           64K
L2 cache:            512K
L3 cache:            8192K
NUMA node0 CPU(s):   0-15
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca

Clearing CMOS didn't help.


Edited by shmerl - 22 Aug 2018 at 8:16am
Back to Top
shmerl View Drop Down
Groupie
Groupie


Joined: 23 Oct 2017
Status: Offline
Points: 612
Post Options Post Options   Thanks (0) Thanks(0)   Quote shmerl Quote  Post ReplyReply Direct Link To This Post Posted: 22 Aug 2018 at 12:52am
Just flashed 4.81 on X370 Taichi with Ryzen 2700X / G.Skill Flare X 3200 MHz. (2 x 8 GB). So far so good. I don't overclock the CPU, but run RAM at 3200 MHz using customized timings.


Edited by shmerl - 22 Aug 2018 at 12:52am
Back to Top
virpz View Drop Down
Newbie
Newbie


Joined: 08 Aug 2018
Status: Offline
Points: 27
Post Options Post Options   Thanks (0) Thanks(0)   Quote virpz Quote  Post ReplyReply Direct Link To This Post Posted: 21 Aug 2018 at 11:23pm
PBO boost is totally dependent on core temperature and while you may get a good boost ( 4.1, 4.2, 4.3GHz ) with a high end air cooler/high end AIO it will only last a few seconds before said cooling solutions get saturated and the clocks decreases. Long term maintaining of said PBO clocks across all cores will require a very good custom waterloop or even a chiller. No, no noctua air cooling will be able to keep these clocks across all cores while maintaining health temperatures.
Back to Top
xhue View Drop Down
Groupie
Groupie


Joined: 17 Aug 2018
Status: Offline
Points: 634
Post Options Post Options   Thanks (0) Thanks(0)   Quote xhue Quote  Post ReplyReply Direct Link To This Post Posted: 21 Aug 2018 at 6:57pm
Nobody advertised 4+ GHz on all cores. NO overclock is guaranteed.

What you see with other guys by no means will be also valid for you. Top GHz numbers put TREMENDOUS  pressure on all PC components. Even the slightest mistake will break your OC. Even something as trivial as coldplate not being seated properly, or poor TIM application.

This offset you're talking about is only used for fan control.
Back to Top
bigboss View Drop Down
Newbie
Newbie


Joined: 31 Jul 2017
Status: Offline
Points: 34
Post Options Post Options   Thanks (0) Thanks(0)   Quote bigboss Quote  Post ReplyReply Direct Link To This Post Posted: 21 Aug 2018 at 5:40pm
Originally posted by Jpe1701 Jpe1701 wrote:

Originally posted by bigboss bigboss wrote:

With all bioses and a nh-u14s cooler my max all core freq is 3925MHz. Should I change some settings to achieve the advertised 4GHz+ all core? I think the motherboard throttling CPU because it reaches Tdie 63C, and 73C with the temperature offset. I think that 10C offset is ruining it.

What are you using to check temps? I think we have to wait for the pbo to be fixed. 4.64 pbo works and I get about 4.075Ghz with a clc 280.

Hwinfo64, that's what im using.
Back to Top
 Post Reply Post Reply Page  <1 23456 15>
  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.527 seconds.