X370 Tai Chi - Issues

as strange as it sounds try
bankgroup auto /enabled
geardown auto/enabled

failing that set the ram timings to 16/14/14/14/

i also have a taichi and have been playing with my gskill trident z for quite some time now

what i can get from the ram in windows and on warmboot/restart is much tighter and faster than any cold boot (mine will always do the boot loop thing and then reset defualts)

yet runs all day without issue when set and rebooted warm

no reboot issues here.



Edited by prodev42 - 30 Jul 2017 at 10:07pm

prodev

my taichi and r7 1700 gets 3.900 at 1.3 volts and has from day one

i set llc 2
and turn off all the power saving stuff you mentioned
pstate settings
9c
8
27
set voltage to fixed on first page and llc level 2
hope this helps


Edited by datonyb - 31 Jul 2017 at 1:18am

Hey do staff ever check these forums or do I need to call Asrock directly?

Haaviko wrote: Hello, I've recently purchased the X370 TaiChi motherboard along with the G Skill 3200Mhz Flare X Ryzen Ram & the Ryzen 7 1700 CPU. My BIOS settings are as followed: OC Tweaker CPU Freqency(Mhz): 3800 CPU Voltage(V): 1.35v - LLC2 XMP Settings Profile for 3200Mhz C14 SoC Voltage: 1.1v - LLC2 Advanced > CPU Configuration Cool n Quiet: Disabled C6 Mode: Disabled Advanced > AMD CBS > Zen Common Options Core Performance Boost: Disabled Global C State: Disabled Since I'm using 1DPC (2 modules total) single rank modules (GSkill Flare X 3200Mhz 16GB Kit) my settings for optimal performance is:  BankGroupSwap: Disabled BankGroupSwap Alt: Enabled GearDownMode: Disabled 1T So using these settings I've managed to get into Windows, do some benchmarks.. gaming and even Prime95 with no WHEA errors. But as soon as I shut down the computer or restart, I usually get a BIOS error code with black screen. Something like 68 or 0d etc. Can somebody help me out? Kind Regards, Haaviko.

So you get "something like 68 or 0d etc."

POST codes are rather specific, and your statement is rather unspecific. How are we supposed to know what the issue might be if we don't know what POST code is shown on the Dr Debug display? You gave us two codes, and etc? What it etc?

Then you said this usually happens when you shutdown or restart. So it is also intermittent? Doesn't happen all the time? Intermittent issues are the most difficult to diagnose.

So sometimes a shutdown fails, and the PC remains on with a black screen? POST does not run on a shutdown, but you see a code displayed? A POST code on a failed cold boot or restart, when POST runs is when the codes are displayed.

If POST fails, a single code is displayed and stays displayed. Is that not happening in your situation? I ask because of the "68 or 0d etc." thing. POST codes that are shown and then disappear means that test passed.

Going with 68, which is Chipset Initialization error, that is a difficult one, could be many things. The standard cure for a chipset initialization error is simply clearing the UEFI/CMOS or pressing the Reset button. No idea if you tried that, and if so, does it work even temporarily?

What UEFI/BIOS version are you using?

Do you get this behavior with say stock CPU and memory speeds?

Your memory at 3200 is right at the edge of stability with a Ryzen system. My FlareX 3200 is not stable at 3200 with a different Ryzen board, I must use it at 2933. Have you tried a lower memory speed, say 2933 or 3033?

Have you tried setting the three memory options you listed at their default settings? GearDownMode, per AMD rules, is enabled by default above a memory speed of 2667 (any memory OC), so Auto = Enabled. Setting it to Disabled is pushing it. Your SOC voltage at 1.200V might help.

No information about the rest of your hardware, or Windows version being used, or AMD chipset driver version installed, and Windows Power Plan. Chipset problems can be related to hardware connected to the chipset, such as the drives in the system.

If you were hoping for a well known, simple fix, I'm sorry but I don't have one for you. Your issue is rather unique, not something we often or at all see in Ryzen related threads.