F5F Stay Refreshed Hardware Desktop Verify system compatibility before reducing Ryzen BIOS version.

Verify system compatibility before reducing Ryzen BIOS version.

Verify system compatibility before reducing Ryzen BIOS version.

K
ko16654
Member
121
12-12-2019, 11:40 PM
#1
I have an Asrock Fatal1ty B450 Gaming ITX motherboard with a 3600 CPU. I need to switch it down to a 2600 CPU for testing. The documentation mentions that Pinnacle Ridge CPUs shouldn<|pad|> to be updated if you're using newer models. Since the 2600 uses Pinnacle Ridge, I should revert the BIOS to an older version—specifically 3.4, which is the latest safe option. This should resolve the warning without issues.
K
ko16654
12-12-2019, 11:40 PM #1

I have an Asrock Fatal1ty B450 Gaming ITX motherboard with a 3600 CPU. I need to switch it down to a 2600 CPU for testing. The documentation mentions that Pinnacle Ridge CPUs shouldn<|pad|> to be updated if you're using newer models. Since the 2600 uses Pinnacle Ridge, I should revert the BIOS to an older version—specifically 3.4, which is the latest safe option. This should resolve the warning without issues.

U
UnleqitWizard
Member
122
12-13-2019, 12:22 AM
#2
Consensus reached. If testing on a bench, I’d swap the CPU before downgrading to check boot functionality. Probably needs multiple attempts if it’s housed in a case—likely three tries total. It seems the microcode data must be carefully selected for each CPU due to limited ROM space, forcing trade-offs between compatibility and functionality.
U
UnleqitWizard
12-13-2019, 12:22 AM #2

Consensus reached. If testing on a bench, I’d swap the CPU before downgrading to check boot functionality. Probably needs multiple attempts if it’s housed in a case—likely three tries total. It seems the microcode data must be carefully selected for each CPU due to limited ROM space, forcing trade-offs between compatibility and functionality.

A
Aquanow
Member
167
12-13-2019, 07:55 PM
#3
I faced this situation before. I saw some discussions online. Some folks thought it functioned well, while others warned against using it. You might want to boot around the 2600 and see how it starts.
A
Aquanow
12-13-2019, 07:55 PM #3

I faced this situation before. I saw some discussions online. Some folks thought it functioned well, while others warned against using it. You might want to boot around the 2600 and see how it starts.

M
maximumpats
Junior Member
46
12-28-2019, 04:12 AM
#4
I didn't bring it up before, but I also have a 1700 without a home. I can switch between that and the 2600 when testing is needed. I believe it's better to lower the bios than risk it if the newer version doesn't work. Appreciate your feedback.
M
maximumpats
12-28-2019, 04:12 AM #4

I didn't bring it up before, but I also have a 1700 without a home. I can switch between that and the 2600 when testing is needed. I believe it's better to lower the bios than risk it if the newer version doesn't work. Appreciate your feedback.

W
WelfareBaby
Member
148
01-01-2020, 08:37 AM
#5
Bios update went well. Installed at 2600 and started normally. Ran a 5-minute Aida64 test to verify stability and I can shut it down now. Updated to 3600 and posted on the sales forum. Task completed for today; I’m excited to consider Zen 3 next time.
W
WelfareBaby
01-01-2020, 08:37 AM #5

Bios update went well. Installed at 2600 and started normally. Ran a 5-minute Aida64 test to verify stability and I can shut it down now. Updated to 3600 and posted on the sales forum. Task completed for today; I’m excited to consider Zen 3 next time.

Z
ZentrixsYT
Junior Member
1
01-04-2020, 04:39 PM
#6
The warning appeared when updating the BIOS, not the bios itself. Once the BIOS is current, the issue should resolve. The concern relates to chipset drivers. The Asus website advises updating the driver before changing the BIOS. It seems there was a compatibility problem between chipset, core model, and BIOS updates. Edit: I refer to all board manufacturers. Because AsRock uses the same BIOS as Asus, error codes and post codes will be alike. In essence, you likely spent time rolling back the BIOS revision only to need it updated again later.
Z
ZentrixsYT
01-04-2020, 04:39 PM #6

The warning appeared when updating the BIOS, not the bios itself. Once the BIOS is current, the issue should resolve. The concern relates to chipset drivers. The Asus website advises updating the driver before changing the BIOS. It seems there was a compatibility problem between chipset, core model, and BIOS updates. Edit: I refer to all board manufacturers. Because AsRock uses the same BIOS as Asus, error codes and post codes will be alike. In essence, you likely spent time rolling back the BIOS revision only to need it updated again later.

M
mmillaa
Member
197
01-04-2020, 08:03 PM
#7
Revisiting their warning, I understand now. It advises against updating it with those CPUs and also against disabling its use. For testing, I likely need the most recent supported BIOS installed. I'll be ready when the time comes.
M
mmillaa
01-04-2020, 08:03 PM #7

Revisiting their warning, I understand now. It advises against updating it with those CPUs and also against disabling its use. For testing, I likely need the most recent supported BIOS installed. I'll be ready when the time comes.