Question Ryzen 5650g is not locked(?)

Jun 7, 2022
10
0
10
In the official page of 5650g Pro APU it is clearly stated that the chip is locked for overclocking.

I also found this thread, where someone complaints about it https://linustechtips.com/topic/1408281-ryzen-5-5650g-is-locked/

My experience is completely different. I've bought this chip and installed it on an ASUS Prime B350M-A board (latest 6042 BIOS). From the BIOS I can most definitely change the CPU core multiplier,RAM speed, voltage for anything etc (static overclock). I can also change the pstates of the chip, so it downclocks when needed (more dynamic overclock).

There is also a section in the BIOS about AMD overclocking, which only lacks the automatic PBO settings. Is this supposed to mean that the CPU is 'locked'? Because it can't be overclocked with (only) PBO?

I've managed to change the CPU core multiplier to 45 and achieve an all-core stable overclock of 4.5ghz with one click (1.35v).

How is this chip supposed to be 'locked'?
 
In the official page of 5650g Pro APU it is clearly stated that the chip is locked for overclocking.

I also found this thread, where someone complaints about it https://linustechtips.com/topic/1408281-ryzen-5-5650g-is-locked/

My experience is completely different. I've bought this chip and installed it on an ASUS Prime B350M-A board (latest 6042 BIOS). From the BIOS I can most definitely change the CPU core multiplier,RAM speed, voltage for anything etc (static overclock). I can also change the pstates of the chip, so it downclocks when needed (more dynamic overclock).

There is also a section in the BIOS about AMD overclocking, which only lacks the automatic PBO settings. Is this supposed to mean that the CPU is 'locked'? Because it can't be overclocked with (only) PBO?

I've managed to change the CPU core multiplier to 45 and achieve an all-core stable overclock of 4.5ghz with one click (1.35v).

How is this chip supposed to be 'locked'?
did you updated the bios to the latest?
 
Please see my post (latest BIOS). But also: I'm not posting this as a problem but as a question. The CPU is supposed to be 'locked' but to me appears completely unlocked (and this is ok 😏 )
 
Please see my post (latest BIOS). But also: I'm not posting this as a problem but as a question. The CPU is supposed to be 'locked' but to me appears completely unlocked (and this is ok 😏 )
well it seems it's because the cpu support page says it doesnt support it officially for cezanne and vermeer cpus, it could be because of it XD (But if agesa is there the microcode update is there too, checked with ryzen SMU checker)

Seems beneficial eh? that chip could run 4000mhz+++ 1:1 real easy
 
Sorry I can't totally understand you, what is XD? The official page indeed says no OC, yet I can do everything with the chip from the BIOS (not with PBO or Ryzen master).
I guess it could reach 4ghz easily but I'm limited by my motherboard (Asus b350m-a), which supports only up to 3200 ram and IF.
 
thats not true, that 3200mhz limit was on first gen ryzen
with 3000/5000cpu you can go 3600+ on ram

I'm not sure, because as soon as I hit 3266 I've got instability and the specs of the mobo say max 3200. Anyway I highly doubt that I'll ever be able to go higher than 3200 with a relatively cheap 2400 stick, with only one 2466 XMP OC profile.
But that's not the issue here...
 
I'm not sure, because as soon as I hit 3266 I've got instability and the specs of the mobo say max 3200. Anyway I highly doubt that I'll ever be able to go higher than 3200 with a relatively cheap 2400 stick, with only one 2466 XMP OC profile.
But that's not the issue here...
yea, overclockable sticks are prefered 😀
mainboard was specced with gen 1 ryzen in mind, im still on x370 and it is also specced for 3200max, but i could push it to 3400 with 1600x, and with gen2 ryzen it can do 3733 with1:1 (gear1) or 4000 with 1:2 (gear2)
 
I'm not sure, because as soon as I hit 3266 I've got instability and the specs of the mobo say max 3200. Anyway I highly doubt that I'll ever be able to go higher than 3200 with a relatively cheap 2400 stick, with only one 2466 XMP OC profile.
But that's not the issue here...
IMC is never locked on Ryzen CPUs, that part would be able to OC even if multiplier is locked. On the other hand, 300 chipset series have notoriously bad memory architecture so 3000 - 3200MHz RAM is difficult to achieve even with best RAM of that frequency let alone some cheap RAM of much lover XMP.
PS.
PBO is not overclocking.
 
  • Like
Reactions: nikoskazanakis
yea, overclockable sticks are prefered 😀
mainboard was specced with gen 1 ryzen in mind, im still on x370 and it is also specced for 3200max, but i could push it to 3400 with 1600x, and with gen2 ryzen it can do 3733 with1:1 (gear1) or 4000 with 1:2 (gear2)

Ok,but what sticks do you have?I guess close or over 3200,not 2400 ones...
 
That is not on the supported CPU list. So your motherboard isn't correctly recognizing the CPU.

The CPU is fully recognised and fully works as intended.
ASUS have done a terrible job of updating the supported CPUs list in B350 chipset and this particular board (Prime B350M-A): BIOS 6042 has updated AGESA to V2 PI 1.2.0.7., so all Ryzen 3 series CPUS are supported and working correctly, including 5650g. I know this because I'm writing this on such a system.

On the other hand the board with BIOS 6042 can no longer support older AM4 Bristol Ridge Gen A-series/Athlon X4 CPUs like the same BIOS in the equivalent A320 board: https://www.asus.com/Motherboards-Components/Motherboards/PRIME/PRIME-A320M-A/HelpDesk_CPU/
Support for these CPUs has been dropped since BIOS 5862: https://www.asus.com/Motherboards-Components/Motherboards/PRIME/PRIME-A320M-A/HelpDesk_BIOS/

But ASUS has criminally failed to update the CPU support list for the Prime B350M-A after the latest BIOS, in contrast to what they have done with the support list of the (inferior) A320 chipset, as per the link above. Meaning that someone with, say, an A8-9600 CPU trying to update to the latest 6042 BIOS will be greeted with a nice no-POST situation. And they will not know what to do, since this is not even mentioned in the release notes of BIOS 6042...
 
Last edited: