Re: Maximus P7 Plus Flash File Frp File Fastboot Mode Fix Care Firmware
Matt Dreher
Hello,
I would like to report an issue that started with AGESA 1.2.0.5 and continues with AGESA 1.2.0.6 and 1.2.0.7 for Ryzen 3000 CPU owners.
Currently, I have BIOS 3801 based on AGESA 1.2.0.3 and SMU version for Matisse (Ryzen 3000) processors is 46.71.0.
On this BIOS version everything works as it should (apart from the fTPM problem with Windows 11 which causes a stutter supposed to be fixed with AGESA 1.2.0.7).
Since BIOS version 3904 (i.e. 3904 - 4002 - 4006 and 4201) the AGESA has gone from 1.2.0.3 to 1.2.0.5 then 1.2.0.6 and finally 1.2.0.7 and the SMU for the Matisse CPU (Ryzen 3000) is increased from 46.71. 0 to 46.72.0 and from this version (AGESA and/or SMU) it is almost impossible to start or restart the computer without Q-Code error, black screen, BSOD, as soon as the DOCP profile is activated or the memory frequency is set manually. The only way to make the BIOS based on these AGESA versions work is to leave the RAM frequency on "default" which is not ideal because in my case for example it means 2133 Mhz.
Of course, reverting to an earlier BIOS like the 3801 (which I'm currently using) fixes the issues instantly.
I did some memtests and other tests, the problem is not with my hardware. I researched various forums (including Asus and MSI) and found that this is a common problem among owners of Ryzen 3000 processors and an X570 motherboard or B550. I even saw a person having the same problem, who solved the problem by changing their Ryzen 3000 pro processor to a Ryzen 5000.
So, I really hope this is not a trick from AMD to let Ryzen 3000 users down, and you will do something about it.
PS: I have already contacted Asus support, they have already offered me several solutions, none have worked, and none will work as long as it is a problem within the AGESA, and it comes from you.
My problem seems to be solved thanks to Asus. They promised, and they delivered, it's been almost 5 days now that I'm using a modified BIOS specially made for my board and Corsair RAMs, and it's 100% functional, no problem whatsoever so far. I'd like to thank Asus for the hard work and Corsair for borrowing memory sticks to them. I hope they will publicly release it and make it work with more models.
Maximus P7 Plus Flash File Frp File Fastboot Mode Fix Care Firmware
Download https://vittuv.com/2yLxhT
Conclusion :
Even if there were 0 doubt about it unlike what some people said, it wasn't a memory issue, it was a BIOS issue like I stated before. Nothing to have with die model, memory brand or motherboard brand, everything was compatible and functional. If Asus and Corsair proved me something is that, they care and as a customer that's all what I ask for. I hope AMD will find a solution that they can share with other brands too. Thank you to all the people that shared their feedbacks and have been patient.
Thanks for the answer,
As you may know, having a Q-Code or a black screen before OS loading has nothing to do with any driver (chipset included), even though my chipset driver is already up-to-date.
XMP Profile is Intel's terminology, on an AMD platform it's called DOCP and as mentioned, yes ! I tried DOCP profile and I also tried setting up memory manually it's in both cases the source of the problem with BIOSes based on AGESA 1.2.0.5 and newer, only way is to "fix" this is to go back to an earlier BIOS or setting everything RAM related to "Default" which isn't an option for me because whether I'm losing performance or I'm having stutters because of the fTPM implementation in Windows 11 which 1.2.0.7 was supposed to fix.
Upgrade my CPU to a different model ? Why would I buy a new CPU when mine is more than sufficient and perfectly working ? The problem is in the AGESA provided by AMD to the manufacturers, not in my hardware.
I don't think they will fix it but it never hurts to try to open a support ticket. That way you have a higher chance to actually having an AMD employee look into this.
As a workaround I would suggest to manually set the timings for your RAM. There is probably a memory training error on the motherboard on the latest BIOS versions that prevents the PC to boot. I see that you have 4 sticks of 3000 CL 15. I don't know how the ASUS bios works or if it has some auto memory tuning enabled, I would suggest to turn off anything related to that and you manually set them to 2966 CL15-17-17-35 or even higher 3200 CL16-18-18-36 and don't forget to manually set the DRAM voltage to 1,35V. With four sticks of RAM I would also manually set GDM to on (geardown mode) and command rate to 2T.
@hawkeye as mentioned already set up manually as soon as I reach 2800 Mhz problems begin, I don't think that has something to do with the number of sticks, I saw people having the same issue with only 2 sticks. I also rised the ram voltage (just for testing) up to 1.42v which is a lot for just 3000 Mhz. I always set Gear Down Mode to disabled, so it won't turn the 15 into 16
@ThreeDee DOCP is nothing but XMP on an Asus AMD platform and in the end of the day manufacturers are free to call it whatever they want (XMP or A-XMP or DOCP) especially that most RAM kits are "Intel XMP Certified" anyway (just look at the box that came with your RAM) or look at this example anyway that's not the problem
And to answer your other message 4 or 2 sticks (even 1) didn't change a thing for me or other people, I went up to 1.42v for Memory Voltage and same thing. Unfortunately, my RAM has only one XMP/DOCP profile
My RAM sticks work like a charm on 3801 BIOS (based on AGESA 1.2.0.3) 4 sticks with 1.35v, I even managed to OC up to 3600 C16 but it wasn't for a daily use just a test, and no error whatsoever. So I really don't think the problem is in the hardware, it's in these buggy BIOS version (and to be precise the AGESA)
I went thru some wonky BIOS's on my ASRock x570 Taichi and my daughter's x570 Steel Legend (3700x & 3800XT) where XMP would work .. then it wouldn't and I had to manually set what where the XMP timings and THEN it was fine .. it was annoying is all. But not since running 2000 series Ryzen's have I had issues with running my RAM's rated speed
As far as DOCP(ASUS)/EOCP(Gigabyte?)/XMP(everybody else) .. I was merely pointing out that ASUS is the only motherboard company that uses that nomenclature when you were "correcting" @jawntem .. not everybody runs ASUS stuff so they call it what their respective BIOS's label it (most times) but we all know what they mean/are talking about/referring to
On my system I have only set the Memory frequency to DDR4-3200MHz
No DOCP (Direct Over Clock Profile). Gear Down Mode and all other memory settings are Auto or at its default settings.
And it is working.
With memory frequency increased (above) the DRAM Voltage is automatically increased from 1.2V to 1.35V (this could vary) after DRAM voltage training.
Changes will not take effect until F10 (Save & Exit) and Re-enter Bios if one would like to check the dram voltage.
XMP (Extreme Memory Profiles) is an Intel tech introduction to automatically set DRAM to intended data rates over and above a base level (for DDR3 it applies to DRAM 1600 and up), DDR4 for DRAM 2400 and up. You enable the feature, it reads the profile off the DRAM sticks and applies it in BIOS.
DOCP (Direct Over Clock Profile), is from ASUS for AMD motherboards and came as the motherboard makers didn't want to pay royalties to Intel to implement XMP on AMD motherboards. It effectively uses the DRAM XMP profile to set up data rates and comparative timings on the AMD motherboards for a variety of data rates.
Within the last couple of years, more and more the AMD motherboard makers are simply moving to XMP as it's an industry standard and much easier to keep up in the BIOS than other methods with the proliferation of new DRAM, tighter timings, etc.
I tried to manually set memory frequency, timing and ram voltage, as soon as I reach 2800 Mhz problems begin, and it's random, sometimes I can't even access Windows, as soon as I start I have a Q-Code (random Q-Codes) mostly RAM related, but sometimes I have "BIOS Recovery mode" which is totally weird, and sometimes I can access Windows normally but as soon as I restart, back to square one.
Since I have a similar setup with Asus ROG Crosshair VIII Hero (wi-fi), AMD Ryzen 9 3950X, Corsair Vengeance LPX 2x8GB 3200MHz CL16 and have Not had any issues with my RAM, regardless BIOS version except that I haven't tested beta BIOS ver. I find the whole thing strange and I highly suspect that incompatible memory's are the problem, even if it works (perhaps only occasionally) with prior BIOS ver.
The risk of getting corrupt data, problems to read/write to the memory cells are increased and could eventually cause apps & programs even the operating system to crash/hang.
Best regards from Sweden (I'm sorry for my English grammar).
[Edited]
It is indeed the CMW32GX4M4C3000C15 that I have, but I can assure you it is NOT a hardware issue or incompatibility, I contacted Corsair support before buying them back then in 2019, and they assured me they're compatible, and I also checked the QVL list for Crosshair VIII Hero (Wi-Fi) and they were and still are on the list (check back they're on both PDF for Ryzen 3000 in the link you provided), plus they were and still are working fine since I bought them back then and with all BIOS versions except those with AGESA 1.2.0.5 and superior where I'm forced to lower the speed frequency.
And today I wanted to get all software issues out of the equation, so I decided to fresh install Windows 11 after flashing the new BIOS, same result, Black screen - random Q-Codes F2 - F3 ... (BIOS related) I couldn't even install Windows when I managed to pass these errors, telling me that there are a missing file or couldn't load it or bad signature. I flashed back 3801 used the same BIOS settings (manually), I installed Windows flawlessly, so it appears for me, in my case, it's 100% BIOS related nothing to do with Windows and its softwares or my hardware. Everything else is a constant except the BIOS which is the only variable.
7fc3f7cf58