New Microcode to further enhance AMD Ryzen memory compatibility
AMD will be releasing a new AGESA microcode update this month, this is now being worked on by the motherboard manufacturers. The new microcode (which is located in your BIOS) will further enhance memory compatibility.
This news has reached us by way of Gigabyte. A technical marketing employee has been explaining that AGESA 1.0.0.6 for Ryzen processors will enhance memory compatibility with high clocked DIMMs and would open up 20 new memory registers.
Gigabyte employee: Wish I could drop in and give you guys a new BIOS but I don't have them yet. Latest word is they are working on a new set with AGESA 1006.
Just to recap these are the issue being worked on:
- For those looking for IOMMU fixes we are hopefully going to have an option to force boot off a specific PCIe slot. Its not the grouping fix, but a work around for now.
- Disable LAN (Per request)
- Disable Audio (Per request)
- "ROM Image update" (Being worked on with AMI, no ETA)
- Cold boot / Wont boot. Have to re-flash BIOS. (people have referred to this as "soft brick")
- AGESA 1006 - improve memory (Got high hopes for this one. Going to enable 20+ memory register)
That means there will be another 20 memory kits added and supported. AMD back in April already released AGESA 1.0.0.4a which brought slightly better performance, lower memory latency and also increased memory support as well as faster bootup (post) times.
As you can see AGESA 1006 is in the works and should see the light of day with initial Beta BIOS updates soon. Btw the Gigabyte employee mentions AGESA 1006 twice, he could actually mean 1005 as the last AGESA release from AMD was 1004a.
Source: Gigabyte via hwi & reddit
Member
Posts: 47
Joined: 2007-08-25
I have achieved stability at 2933MHz with my Ryzen 1800x, Corsair Dominator 16GB (8x2), Nvidia Titan X Pascal & the ASRock Fatal1ty X370 Professional Gaming motherboard.
I can share my info if you all like. This is with the just released "SummitPI-AM4 1.0.0.4a" AGESA micro-code updated for this BIOS (version 2.20) - Dated: 5/4/2017
Tim
Member
Posts: 25
Joined: 2017-05-09
Hey about that 5820k you had, what was it running at; frequency and voltage wise? Currently have mine at 4.6 ghz 1.297V with CAS 15 3k memory attached to it.
Junior Member
Posts: 1
Joined: 2017-05-25
I used Asus OC in Bios to tune CPU to 3.65GHz x16 at stock voltage
To fix my ram Issue - Bios shows 2400 for the SLOTS
and D.O.C.P shows 2933 | But this doesn't boot without the following...
So after OC setup ran,
I then manually added the 2400 specs into the
AI Tweaker / override DRAM Timings, so set them to : 17,17,17,39
This worked, and machine is stable,
To stop windows "lagging or freezing",
I run Bill2s Process Manager ( Has English, great tool Merci Bill )
I've defined Default is
Priority : Below Normal
Affinity : CPU1+HT, CPU2+HT
Everything else I group into either of these custom groups by exe name
Above Normal : 3-6
High Priority : 7-8
I Place games/applications into the thread group that works best..
I've only had the system a few days, so still learning.
Also, I've enabled Windows Power core Parking min cores as :
25 % : which is 100% / 16 Threads x 4 for rounding, 4 threads never parked
Max Processor Freq 3650
Cooling : Passive !
Core Parking max cores : 100 % ( When reduced, drops more threads quicker )
- Still looking into the effect of these if any.
- use regedt32 or powercfg to enable the drop downs in power menu
- I use HWiNFO64 and powershell for Info
- CPU 21 - 93 Watts (32.8 to 53 Deg C ) so far
-
Senior Member
Posts: 2549
Joined: 2012-04-16
Ryzen is like a bad early access game, pricey and really not that good.
Senior Member
Posts: 7161
Joined: 2012-11-10
I did that - I even increased them beyond their defaults and it still couldn't boot beyond 2666MHz.
I've done that too and it's still unbootable. I even used XMP settings but lowered the RAM speed and that too was unbootable.
I heard those who have DS (double-sided) RAM have the most problems. I'm hoping the new AGESA update addresses this.
EDIT:
So I checked dmidecode in Linux. It says the "speed" is 1067MHz, but it says the "Configured clock speed" is 1333Mhz. It's also reporting the wrong voltage - I set it to 1.35v but it claims its at 1.2v, including configured voltage.