• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

B550 phantom Gaming ITX/AX bios problem.

Joined
Sep 5, 2016
Messages
19 (0.01/day)
Hello all

My friend has a B550 Phantom Gaming ITX/AX motherboard with BIOS version L2.61 installed. However, in the BIOS HW Monitor section, there's an error in detecting temperature and fan RPM (CPU temp: 6500°C, M/B temp: -1°C, and fan RPM: 65535 RPM).

I’m planning to update the BIOS, but I’m confused because BIOS version L2.61 is not listed on the B550 Phantom Gaming ITX/AX motherboard’s support page. Additionally, the website states: "To support Ryzen 5000G series processors, it requires updating the BIOS with a Matisse, Renoir, or Vermeer CPU."

What should I do? If I need to update the BIOS, which version should I update to?

Thank you
 
What cpu is in there?
 
Ryzen 5 5600G
2.61 is on there the L denotes a early beta bios.

Anyways its Ryzen 3000, 4000, 5000 that must be present to flash, it just means the bios chip isnt large enough to support a Ryzen 1000 or 2000 apu.
 
Should I update the BIOS directly, or do I need to use a Matisse, Renoir, or Vermeer processor to update it? Because 5600G processor is a "Cezanne."
 
Should I update the BIOS directly, or do I need to use a Matisse, Renoir, or Vermeer processor to update it? Because 5600G processor is a "Cezanne."
Its already working, you can try it or contact asrock.
 
Hello all

My friend has a B550 Phantom Gaming ITX/AX motherboard with BIOS version L2.61 installed. However, in the BIOS HW Monitor section, there's an error in detecting temperature and fan RPM (CPU temp: 6500°C, M/B temp: -1°C, and fan RPM: 65535 RPM).
That's a beta bios. Personally I wouldn't stay on the beta BIOS, I would flash up to UEFI/BIOS P3.30 or P3.40 however there is always a risk of something going wrong when flashing so you will need to use your best judgement if it's worth the risk. This motherboard does not have flashback capability.
I’m planning to update the BIOS, but I’m confused because BIOS version L2.61 is not listed on the B550 Phantom Gaming ITX/AX motherboard’s support page. Additionally, the website states: "To support Ryzen 5000G series processors, it requires updating the BIOS with a Matisse, Renoir, or Vermeer CPU."
That message is if you are flashing prior to 5000G support. You are already past that point.
What should I do? If I need to update the BIOS, which version should I update to?

Thank you
I have two of these boards and UEFI/BIOS P3.40 seems to be just fine at least with 5950x and 5800x. YMMV with different hardware. Before flashing you need to remember to disable TPM, save, reboot, then flash, reboot, reset to default, save, reboot, finally reapply any custom settings, save, reboot. If you have any custom applied settings be sure to write them down before flashing so you can apply them again after flashing.

As a side note these boards may be a bit weird about voltages. I recall early UEFI/BIOS versions of this board like to set 1.2v SOC by default but after some update they stopped doing that and changed up something about how they applied default voltages including dropping the LLC options to their lowest settings.

After that happened I got stable again by adjusting voltages like in the image below (and increasing LLC back to mid range values) but I wouldn't bother changing anything with voltages or LLC if your system is already running stable.

Amazon indicated this board was an often returned item so I think perhaps the quality must be a bit of hit or miss. My second board is just fine (besides the voltage adjustment noted in the below image) the first one started to have issues after about a year or two of use and after 6 months of eventually replacing all parts of that build it occasionally still has an issue with crashing programs. In addition to the voltage adjustment noted below returning to 1.2v SOC helped increase stability of that first problematic motherboard that was having issues.

1741097367655.png
 
Last edited:
That's a beta bios. Personally I wouldn't stay on the beta BIOS, I would flash up to UEFI/BIOS P3.30 or P3.40 however there is always a risk of something going wrong when flashing so you will need to use your best judgement if it's worth the risk. This motherboard does not have flashback capability.

That message is if you are flashing prior to 5000G support. You are already past that point.

I have two of these boards and UEFI/BIOS P3.40 seems to be just fine at least with 5950x and 5800x. YMMV with different hardware. Before flashing you need to remember to disable TPM, save, reboot, then flash, reboot, reset to default, save, reboot, finally reapply any custom settings, save, reboot. If you have any custom applied settings be sure to write them down before flashing so you can apply them again after flashing.

As a side note these boards may be a bit weird about voltages. I recall early UEFI/BIOS versions of this board like to set 1.2v SOC by default but after some update they stopped doing that and changed up something about how they applied default voltages including dropping the LLC options to their lowest settings.

After that happened I got stable again by adjusting voltages like in the image below (and increasing LLC back to mid range values) but I wouldn't bother changing anything with voltages or LLC if your system is already running stable.

Amazon indicated this board was an often returned item so I think perhaps the quality must be a bit of hit or miss. My second board is just fine (besides the voltage adjustment noted in the below image) the first one started to have issues after about a year or two of use and after 6 months of eventually replacing all parts of that build it occasionally still has an issue with crashing programs. In addition to the voltage adjustment noted below returning to 1.2v SOC helped increase stability of that first problematic motherboard that was having issues.

View attachment 387777
Thank you for your answer. Tomorrow, I will try updating directly from L2.61 to P3.40. Hopefully, it goes well—failure is not an option!
 
Thank you for your answer. Tomorrow, I will try updating directly from L2.61 to P3.40. Hopefully, it goes well—failure is not an option!
Some instances betas fix everything, but never get a release. This mobo on hand has plenty of updates, so its advised

That's a beta bios. Personally I wouldn't stay on the beta BIOS, I would flash up to UEFI/BIOS P3.30 or P3.40 however there is always a risk of something going wrong when flashing so you will need to use your best judgement if it's worth the risk. This motherboard does not have flashback capability.

That message is if you are flashing prior to 5000G support. You are already past that point.

I have two of these boards and UEFI/BIOS P3.40 seems to be just fine at least with 5950x and 5800x. YMMV with different hardware. Before flashing you need to remember to disable TPM, save, reboot, then flash, reboot, reset to default, save, reboot, finally reapply any custom settings, save, reboot. If you have any custom applied settings be sure to write them down before flashing so you can apply them again after flashing.

As a side note these boards may be a bit weird about voltages. I recall early UEFI/BIOS versions of this board like to set 1.2v SOC by default but after some update they stopped doing that and changed up something about how they applied default voltages including dropping the LLC options to their lowest settings.

After that happened I got stable again by adjusting voltages like in the image below (and increasing LLC back to mid range values) but I wouldn't bother changing anything with voltages or LLC if your system is already running stable.

Amazon indicated this board was an often returned item so I think perhaps the quality must be a bit of hit or miss. My second board is just fine (besides the voltage adjustment noted in the below image) the first one started to have issues after about a year or two of use and after 6 months of eventually replacing all parts of that build it occasionally still has an issue with crashing programs. In addition to the voltage adjustment noted below returning to 1.2v SOC helped increase stability of that first problematic motherboard that was having issues.

View attachment 387777
 
Thank you for your answer. Tomorrow, I will try updating directly from L2.61 to P3.40. Hopefully, it goes well—failure is not an option!
Good luck. Let us know how it works out.
 
I've updated the BIOS, and it's slightly better than before. However, in the BIOS H/W Monitor section, it still has errors detecting the temperature and fan RPM.
If you use HWiNFO64 do the reading still look bad?
 
I didn’t have a chance to check, maybe tomorrow. But even if it’s detected correctly in HWiNFO, it still feels uncomfortable.
Here is what mine looks like for reference. If I get a chance this afternoon I'll take a peek in my UEFI/BIOS to see what it's doing. I may not have noticed if it's bugged or not otherwise it appears to be working fine in HWiNFO.

1741185093675.png
 
That would be helpful, thanks! If you get a chance to check, let me know what you find.
I checked both my ITX's and the temp and fan speeds were fine with P3.40 UEFI/BIOS and HWiNFO64. The motherboard you are working with may be defective.
 
I checked both my ITX's and the temp and fan speeds were fine with P3.40 UEFI/BIOS and HWiNFO64. The motherboard you are working with may be defective.
Here’s a photo of my H/W Monitor, and I just realized that the Vcore is way too high—there’s no way it should be this high. Could it be a faulty motherboard or PSU?
 

Attachments

  • IMG_20250304_191359.jpg
    IMG_20250304_191359.jpg
    2.7 MB · Views: 63
Here’s a photo of my H/W Monitor, and I just realized that the Vcore is way too high—there’s no way it should be this high. Could it be a faulty motherboard or PSU?
If that vcore reading were true the CPU would have already melted by now. I would guess faulty motherboard or corrupted UEFI/BIOS.
 
Sorry for the late post,
Thank you all for your amazing answers; they were really helpful. It turns out that the motherboard was indeed the problem. The owner has already taken it back, so the case is now closed. Thank you very much, everyone!
 
Back
Top