F5F Stay Refreshed Hardware Desktop RAM problems vary with AGESA versions from 1.2.0.5 to 1.2.0.7

RAM problems vary with AGESA versions from 1.2.0.5 to 1.2.0.7

RAM problems vary with AGESA versions from 1.2.0.5 to 1.2.0.7

Pages (3): 1 2 3 Next
G
gui1go
Member
177
11-01-2021, 01:43 PM
#1
Hello, I’m here to share a concern that began with AGESA 1.2.0.5 and has progressed through versions 1.2.0.6 and 1.2.0.7 for users running Ryzen 3000 processors. At the moment, my system uses BIOS 3801 based on AGESA 1.2.0.3 with SMU version 46.71.0 for the Matisse (Ryzen 3000). Everything functions normally except for an fTPM issue with Windows 11, which causes stuttering and is expected to be resolved by AGESA 1.2.0.7. Starting from BIOS 3904 (versions 3904–4201), the AGESA transitioned through several releases, and the SMU for the Matisse CPU increased from 46.71.0 to 46.72.0. After this point, starting or restarting the computer without using Q-Code usually results in a crash—either a blue screen, BSOD, or error messages (mostly). Once the DOCP profile is enabled or memory frequency is manually set above 2733 MHz, these problems become extremely difficult to overcome. The only practical solution is to keep the BIOS unchanged, though this isn’t ideal as it leaves the system at a lower frequency. Changing RAM speed settings or adjusting core voltages didn’t resolve the issue. I’ve performed various tests—adjusting vcore, voltage, etc.—but the problem remains consistent. I attempted a fresh Windows 11 installation on the latest BIOS, but it failed due to Q-Codes and file corruption warnings. When I switched back to BIOS 3801 (AGESA 1.2.0.3), the installation succeeded without issues. Others I spoke with reported similar difficulties and suggested upgrading to a different processor model (e.g., Ryzen 5000) as a workaround. I reached out to Asus France support, who offered several fixes but none worked consistently for their users. AMD France declined to escalate the matter, stating that if it runs smoothly at lower frequencies (like 2133 MHz or 2666 MHz), there’s no concern—something clearly isn’t right with this build. This situation is well-documented in forums, including among users with X570 or B550 motherboards. I’m seeking a reliable solution to get my system stable without compromising performance.
G
gui1go
11-01-2021, 01:43 PM #1

Hello, I’m here to share a concern that began with AGESA 1.2.0.5 and has progressed through versions 1.2.0.6 and 1.2.0.7 for users running Ryzen 3000 processors. At the moment, my system uses BIOS 3801 based on AGESA 1.2.0.3 with SMU version 46.71.0 for the Matisse (Ryzen 3000). Everything functions normally except for an fTPM issue with Windows 11, which causes stuttering and is expected to be resolved by AGESA 1.2.0.7. Starting from BIOS 3904 (versions 3904–4201), the AGESA transitioned through several releases, and the SMU for the Matisse CPU increased from 46.71.0 to 46.72.0. After this point, starting or restarting the computer without using Q-Code usually results in a crash—either a blue screen, BSOD, or error messages (mostly). Once the DOCP profile is enabled or memory frequency is manually set above 2733 MHz, these problems become extremely difficult to overcome. The only practical solution is to keep the BIOS unchanged, though this isn’t ideal as it leaves the system at a lower frequency. Changing RAM speed settings or adjusting core voltages didn’t resolve the issue. I’ve performed various tests—adjusting vcore, voltage, etc.—but the problem remains consistent. I attempted a fresh Windows 11 installation on the latest BIOS, but it failed due to Q-Codes and file corruption warnings. When I switched back to BIOS 3801 (AGESA 1.2.0.3), the installation succeeded without issues. Others I spoke with reported similar difficulties and suggested upgrading to a different processor model (e.g., Ryzen 5000) as a workaround. I reached out to Asus France support, who offered several fixes but none worked consistently for their users. AMD France declined to escalate the matter, stating that if it runs smoothly at lower frequencies (like 2133 MHz or 2666 MHz), there’s no concern—something clearly isn’t right with this build. This situation is well-documented in forums, including among users with X570 or B550 motherboards. I’m seeking a reliable solution to get my system stable without compromising performance.

S
196
11-03-2021, 02:07 AM
#2
S
StampyKittenNZ
11-03-2021, 02:07 AM #2

C
ClassicMan_YT
Member
140
11-03-2021, 07:43 AM
#3
I promise those Corsair Vengeance rams are a big problem for many people. Whenever I encounter a ram error, it usually involves Corsair rams. I own a B450 Aorus M and a B450M S2H V2, both working perfectly on 1.2.0.7 with Kingston rams that use Micron and Hynix DRAM chips. It wouldn’t surprise me if your problem stems from those RAMs rather than the AGESA version.
C
ClassicMan_YT
11-03-2021, 07:43 AM #3

I promise those Corsair Vengeance rams are a big problem for many people. Whenever I encounter a ram error, it usually involves Corsair rams. I own a B450 Aorus M and a B450M S2H V2, both working perfectly on 1.2.0.7 with Kingston rams that use Micron and Hynix DRAM chips. It wouldn’t surprise me if your problem stems from those RAMs rather than the AGESA version.

F
Flade1337
Member
71
11-05-2021, 12:29 AM
#4
It isn't a hardware or RAM concern; your system functions perfectly up to BIOS 3801, and it works flawlessly on this version. The issues appear only with BIOS 3904 and later. Could you tell me the CPU model?
F
Flade1337
11-05-2021, 12:29 AM #4

It isn't a hardware or RAM concern; your system functions perfectly up to BIOS 3801, and it works flawlessly on this version. The issues appear only with BIOS 3904 and later. Could you tell me the CPU model?

X
xX_SiMoNk_Xx
Member
78
11-06-2021, 01:56 PM
#5
No, not all four models share identical RAM. Checking different pairings may yield consistent results.
X
xX_SiMoNk_Xx
11-06-2021, 01:56 PM #5

No, not all four models share identical RAM. Checking different pairings may yield consistent results.

G
Gamer13_YT
Junior Member
14
11-12-2021, 10:19 PM
#6
Are you sure it's not just Asus with its odd BIOS updates? I've faced problems on my latest rog board, consistently using a very old version that supports stable overclocking. The same happened with my Crosshair VII Hero and Maximus XI hero. If you haven't turned off ASUS Armoury Crate in the BIOS and removed it via the uninstallation tool here: https://www.asus.com/supportonly/Armoury Crate/HelpDesk_Download/, you might be experiencing these issues.
G
Gamer13_YT
11-12-2021, 10:19 PM #6

Are you sure it's not just Asus with its odd BIOS updates? I've faced problems on my latest rog board, consistently using a very old version that supports stable overclocking. The same happened with my Crosshair VII Hero and Maximus XI hero. If you haven't turned off ASUS Armoury Crate in the BIOS and removed it via the uninstallation tool here: https://www.asus.com/supportonly/Armoury Crate/HelpDesk_Download/, you might be experiencing these issues.

J
JoaquinXDDD
Member
205
11-27-2021, 08:06 PM
#7
3100 and 3600. After reviewing many Corsair RAM problems, I think the issue might lie with the RAM itself. I’m not claiming rams are broken, but they seem less reliable with Ryzen processors.
J
JoaquinXDDD
11-27-2021, 08:06 PM #7

3100 and 3600. After reviewing many Corsair RAM problems, I think the issue might lie with the RAM itself. I’m not claiming rams are broken, but they seem less reliable with Ryzen processors.

A
aaaa2016
Junior Member
34
11-28-2021, 03:18 AM
#8
They're all 4 part of the same kit and came in the same box, can't do better It's not only Asus, I saw the same with MSI boards, and I doubt it's Armoury Crate (as buggy as it can be), I couldn't even install Windows with these recent BIOS versions (AGESA 1.2.0.5 and later) while everything went fine with BIOS 3801 (AGESA 1.2.0.3)
A
aaaa2016
11-28-2021, 03:18 AM #8

They're all 4 part of the same kit and came in the same box, can't do better It's not only Asus, I saw the same with MSI boards, and I doubt it's Armoury Crate (as buggy as it can be), I couldn't even install Windows with these recent BIOS versions (AGESA 1.2.0.5 and later) while everything went fine with BIOS 3801 (AGESA 1.2.0.3)

H
hahahalo21
Junior Member
46
11-28-2021, 08:31 AM
#9
I've encountered identical issues on other forums, and my setup includes: Asus ROG Crosshair VIII Dark Hero, Ryzen 7 3700X, 32GB (4x8) Thermaltake Toughram Z-One RGB (3200mhz).
H
hahahalo21
11-28-2021, 08:31 AM #9

I've encountered identical issues on other forums, and my setup includes: Asus ROG Crosshair VIII Dark Hero, Ryzen 7 3700X, 32GB (4x8) Thermaltake Toughram Z-One RGB (3200mhz).

L
LuffySenpaaai
Member
53
11-30-2021, 04:32 PM
#10
It seems like there might be a technical or procedural concern. Would you like to explore alternative solutions or check the status of version 3801?
L
LuffySenpaaai
11-30-2021, 04:32 PM #10

It seems like there might be a technical or procedural concern. Would you like to explore alternative solutions or check the status of version 3801?

Pages (3): 1 2 3 Next