Ryzen 3000 series support

https://community.amd.com/thread/245196
For information about 1.0.0.4b

thats the only fix its an asrock patch not an amd patch

3.92 out
1. Fix LAN i211 Enabled / Disabled
2. Fix WLan 3168 Enabled / Disabled
3. Fix Bluetooth Enabled / Disabled
(a ClearCMOS may be required !)

does anyone know how to contact with technical support beside form on website? they don't reply, it pisses me off.

Xaltar wrote: ViCe, what is your RAM rated for? From your posts I understood it to be rated at DDR4 3200. If that is the case then the new BIOS simply does not overclock as well (beyond your RAM's XMP) as the last BIOS you used. I have a 3600 kit that can't hit 3733 no matter the voltage and settings but works fine at 3600 all day long and another kit rated at 2800 @1.2v that can hit 3800 @1.35v but only on one of my systems. My point is, XMP profiles come from the RAM, it's basically a table saved on the RAM's firmware that contains a JDEC (sometimes up to 3 JDEC profiles) and typically one XMP profile complete with voltages, timings and frequencies. It's basically a RAM overclock that the RAM manufacturer tested and guarantees in a compatible board. They then have a QVL of their own listing what boards the RAM was able to run on with that XMP profile. Anything beyond your RAM's rated XMP is not guaranteed. The list of frequencies under the XMP drop down menu in your UEFI isn't a list of "supported" frequencies for your RAM, it's just a list of frequencies you can manually select and try to force, either lower (because your default XMP is unstable or won't post) or higher (a very simple overclock that uses default XMP timings and voltages but tries to force a higher frequency). XMP is a real pain in the rear and a lot of industry pros hate it. It has created the illusion that RAM overclocking is a right and that it should just work. Unlike JDEC it doesn't adhere to any standards and it was invented by RAM manufacturers to market their RAM at higher than rated (JDEC) speeds. That is fine and makes sense but without proper standards it makes it very difficult to maintain broad compatibility. This is why so many of us use Ryzen Calc and Thaiphoon Burner etc to manually determine and lock in the best possible settings for our RAM. Now if your RAM is rated higher than 3200 and you were able to achieve it's rated frequency with a previous BIOS then that is an entirely different matter. In that case the new BIOS broke compatibility with your rated XMP on your particular RAM kit. This happens all the time on AM4 and is one of the reason so many people update so often, hoping for better support for their particular RAM.

My ram rated for 3200
But here the thing:
1) I tried to ways to achieve xmp stats - enabling xmp profile from ram with jdec 16-18-18-38 and custom (some changes in subtimings), but it doesn't boot, just short power on, then boot loop, then boot with default settings with 2133
2) even 2400 work with some interesting effect - double boot
3) on 3.90 Aida can't read ram info correctly, on 3.60 - no problem
4) memory banks and their topology used in more faster ram with xmp 3400 and 3600
5) on Reddit several users wrote about 2 gpus compatibility error with 3.90, but I can't proof that - my liquid system doesn't allow use my gpus separately, even if I disable PCI-e, voltage still go to gpu and Mobo detects it
6) 3.60 works fine, ram clocks is 3600 with custom timings - it works stable, no errors in mem test and Aida test, but cpu clocks are lower if compare with agesa 1.0.0.4 (lab test from hardware luxx)