- Asrock Taichi X470 (not ultimate)

 - Ryzen 2700X

 - Gskill ripjaws V 3200mhz C14 

 - MSI GT 1030 

 - 960 EVO 250gb

Before POST and that menu where it says to enter F2 /del for bios, F11 for boot menu etc.. it's ~10 seconds black screen (sometimes saying power settings on monitor). I guess it has something to do with graphic card also..

I use HDMI on graphic card.

In OC Tweaker, should I use ASRock settings or AMD CBS setting?

SHould I change overclock mode from auto to manual? (when I go to manual, it says APU/PCIE frequency at 100mhz... is that same as SMBUS frequency? If that is not SMBUS, should I find it and change or keep at 100mhz?

CPU freq and voltage are at auto, SMT mode enabled.

DRAM settings I set at XMP 2.0 profile 1: 14-14-14-34 1.35V 3200

In advanced it's like this:

coolnquiet - enables

AMD ftpm switch - disabled

SVM mode - disabled

CPB mode - enabled

C6 mode - enabled

Not sure what would be best setup for my CPU.. I didn't do OCing for 10y+.. last I did on old Barton/Throughbred B.. :D

This!

Black screens typically are caused by too little CPU voltage. 

You might be choking the CPU and that's how it responds. I've seen it myself with the 1800X and 1600.

I undervolted them to find their minimum (for thermal reasons). 

Moving to a better cooler was a better idea. The 2700X is smart and if you give it enough thermal headroom, it will effectively overclock itself. 

I have put fast mode: ultra fast (it was disabled) and now I can't get to bios anymore.. I click F2 or del but nothing (sometimes I see menu on start, sometimes I don't).

Cooler is noctua NH-U14S

1.21 is pretty low voltage. I would suggest bumping it up to 1.3 and set your LLC.

If you are at 1.21 and getting v-droop, then boom... black screen.

Anything below 1.425 is safe for long-term daily use, per AMD engineering.

How can I enter in bios now? Since when I press F2 or del nothing.. so strange.

LLC = Load-Line Calibration is a feature added to boards that allows the board to compensate for vDroop (voltage sag that might otherwise make your clock unstable) under times of load. Different "levels" of LLC apply different variations of compensation to your chosen vCore when load is applied to the processor.

You probably need to clear CMOs at this point and either 1) leave things stock or 2) give the CPU more voltage (and increase your LLC setting).

I'm 99% sure that bumping the voltage up will help a lot. Also, recall that SOC voltage should be increased as well. Robert from AMD suggests 1.1 V

ultrafast fastboot  is preventing you from entering bios, u would know that if u would bother reading description for that setting

install ascrock reszatz to uefi tool to get to bios

In my experience, the Restart to UEFI utility doesn't work when the ultrafast boot setting is enabled.

Probably need to clear CMoS

1. Put CPU freq and voltage in manual mode and change there

(If I just put on manual, then CPU will not OC itself anymore?)

2. Go in Voltage configuration, under CPU Vcore change from auto to fixed or offset

Should I choose number 2, go fixed and write 1.3?

I tried looking in mbo manaul but it's not described in detail.. noting about fixed or offset modes is mentioned.

mate can i say again

many many very experianced ryzen system builders are saying dont bother overclocking the cpu

why are you messing around with yours ?

amd seem to have a very very good job with the auto clocks,

I have put 1.3V under fixed and same.. black screen.

Is this normal when I power on?

https://youtu.be/xqg2Uu8dfRw" rel="nofollow - https://youtu.be/xqg2Uu8dfRw

You only have an issue if a code remains on the debug display and the system has stopped responding/posting. The POST code display shows the code for each part of the POST process, if the system fails at any one of these Power On Self Tests, the corresponding code will remain on the display to let you know where the problem is, otherwise they simply flash on the display and change to the next code until POST is complete. There is also a POST code that is displayed while in the UEFI, this is normal too, this is because entering the UEFI interrupts the POST process. 

What about reseting everything by removing battery?