For those on AM5, keep an eye out for BIOS updates in the coming days, and do them

[Illusion of Progress]

I don't often do disclaimer type stuff, but I felt this one might be worthwhile if it saves a CPU or spreads awareness. I haven't seen it mentioned by anyone here in the last few days, but I presume a few may be aware of it anyway. Some may not be.

There have been some reports on AM5 CPUs, at least the 7800X3D, developing problems with the bottom of the CPU visibly bulging and the motherboard also having damage (discoloration or burn marks).

While it's thus far been a small number of people, apparently the problem has been considered a risk for all Ryzen 7000 series CPUs, namely when using Expo (in short, memory overclocking, like DOCP/XMP). The SoC voltage is getting high and I guess that's part of what's causing the issues, so the fix is to limit this voltage, which the upcoming BIOS updates will do. So the good news is a fix is coming for a problem that has been identified.

If you're on AM5, I would heavily recommend keeping an eye on your board manufacturer's website for your particular motherboard, and wait for the BIOS update, and then apply it. I would do this whether you've been having issues or not.

And I, personally, would probably remove the CPU from the board and inspect both the CPU and motherboard socket for damage too, especially if you have a 7800X3D, 7900X3D, or 7950X3D, or if you've been using Expo (or otherwise overclocking the memory and thus SoC), or PBO or adjusting voltages from default. I'd probably even check it regardless if I wasn't doing any of those things and just had a regular Ryzen 7000 series CPU just to be sure.

https://www.tomshardware.com/news/amd-issues-follow-up-statement-on-ryzen-burnout-issues-limits-soc-voltages

In the meantime, you may also want to keep an eye on your SoC voltages, and if they go above ~1.3V is when problems can supposedly occur. I don't have a Ryzen 7000 series, but this is the voltage to keep an eye on. If you see it at or going above 1.3V commonly (mine mostly stays static but I'm not sure if it moves on Ryzen 7000), then it's probably not good and I'd double recommend physically inspecting for damage.

https://i.imgur.com/eqYbb4G.png

Use Libre Hardware Monitor, Ryzen Master, HwInfo64, or possibly others if you already have them on hand to check the SoC voltage.

[󠀡󠀡]

MSI just rolled out another update for BIO

[Illusion of Progress]

I expect they may continue for a short while at least.

There was an article I read shortly after this whole thing started that the initial BIOS fixes weren't entirely rectifying the situation and/or created issues of its own.

https://www.tomshardware.com/news/ryzen-burnout-fix-1007-bugs

[Rod]

尺．し工几句ヨ尺님이 먼저 게시:

Tiberius님이 먼저 게시:

Regarding undervolting/eco mode, do i need to leave ryzen master open at every startup?

No, you can close it, and you can also set it up in BIOS, no need for Ryzen Master.

Ryzen bloat master. It used to mess with timers too. Bios all day for me.

[r.linder]

Rod님이 먼저 게시:

尺．し工几句ヨ尺님이 먼저 게시:

No, you can close it, and you can also set it up in BIOS, no need for Ryzen Master.

Ryzen bloat master. It used to mess with timers too. Bios all day for me.

It can also brick your system if your settings are bad enough to instantly crash the system when RM loads, which would then force you to reset CMOS or boot into safe mode and remove RM to fix it if RM loads automatically at startup.

[Illusion of Progress]

The only issue I've had with Ryzen Master, and I THINK this is Ryzen Master based on searching but it's something else from AMD if not, is occasionally I'll get a CMD window showing up with "AMDAutoupdate". It steals focus from whatever I'm doing. I've considered removing it just because of that. The odd thing is I never had this until recently, or at least it seems it's become far more frequent/pervasive recently. I like the program otherwise (but don't need it) but haven't found a way to stop this.

[Guydodge]

Tiberius님이 먼저 게시:

First it was nvidia with its vhpwr, now it's amd. I upgrade at the worst time ever

just sell it and go intel why play Russian Roulette with such high end gear.i mean a cpu that cant take more than 1.3volts is absurd

[The Commendatore]

Yeah, I swapped out my 7950X3D and Hero board and went back to my 13900K for a while.

Won't be using the Sus brand for a while until they get their act together, if they ever do. I saw their beta BIOS and just laughed at it.

[Rod]

Illusion of Progress님이 먼저 게시:

The only issue I've had with Ryzen Master, and I THINK this is Ryzen Master based on searching but it's something else from AMD if not, is occasionally I'll get a CMD window showing up with "AMDAutoupdate". It steals focus from whatever I'm doing. I've considered removing it just because of that. The odd thing is I never had this until recently, or at least it seems it's become far more frequent/pervasive recently. I like the program otherwise (but don't need it) but haven't found a way to stop this.

Its stealing cpu cycles as well you just gave another reason to not use it.

[Illusion of Progress]

Guydodge님이 먼저 게시:

Tiberius님이 먼저 게시:

First it was nvidia with its vhpwr, now it's amd. I upgrade at the worst time ever

just sell it and go intel why play Russian Roulette with such high end gear.i mean a cpu that cant take more than 1.3volts is absurd

A given voltage is an arbitrary thing, so weird thing to fixate on when they are different products made in different ways, made on different process nodes, and different parts of the CPU will have different voltage limitations (even on Intel).

The SoC voltage isn't vcore. What voltages are people commonly using for VCCIO and VCCSA these days?

AM4 (in my experience) is setting the SoC voltage to 1.05V or 1.1V. The latter is with a "heavy" memory configuration so I'm not sure why you'd need much more on a (AMD) DDR4 system. I guess AM5 probably needs more now that the IF is running at 3,000 MHz instead of 1,800 MHz (plus or minus) and keeping up with faster DDR5 speeds. Problem was the 1.35V and spiking to 1.4V to 1.5V was doing quick damage.

[Illusion of Progress]

Rod님이 먼저 게시:

Illusion of Progress님이 먼저 게시:

The only issue I've had with Ryzen Master, and I THINK this is Ryzen Master based on searching but it's something else from AMD if not, is occasionally I'll get a CMD window showing up with "AMDAutoupdate". It steals focus from whatever I'm doing. I've considered removing it just because of that. The odd thing is I never had this until recently, or at least it seems it's become far more frequent/pervasive recently. I like the program otherwise (but don't need it) but haven't found a way to stop this.

Its stealing cpu cycles as well you just gave another reason to not use it.

Anything and everything that processes uses resources.

Interrupting my focus just to show a CMD window with no way to stop it is what bothers me. What confuses me is i would have figured there was a way AMD could do that part "silently". Why steam focus with a CMD prompts that has no information that the user has to manually close? It's silly.

[r.linder]

Guydodge님이 먼저 게시:

Tiberius님이 먼저 게시:

First it was nvidia with its vhpwr, now it's amd. I upgrade at the worst time ever

just sell it and go intel why play Russian Roulette with such high end gear.i mean a cpu that cant take more than 1.3volts is absurd

Voltage is arbitrary, and it sustains more SOC voltage than a lot of the older chips could, up until now most Ryzen CPUs weren't even supposed to go above 1.2V SOC (according to AMD) and usually ran between 1v and 1.1v SOC out of the box, now because of EXPO it's much higher as it needs more.

SOC voltage is also completely different than CPU voltages. it's system on a chip voltage that affects multiple things, and it was always pretty sensitive. Intel has similar settings but I'm pretty sure that it's spread out between at least 3 different voltages.

[Rod]

Is Gigabyte still acceptable? Asrock Tachi B650e and Aorus Master b650e are extreme if you know what i mean $$$ and really the Asus Strix B650E E was the affordable one!


Yet a day before the Asus bios thing i posted they were a trash brand and always let me down when i buy then. So really i gotta spend £411 UK GBP on a midrange Gigabyte board?!? What happened to AMD value brand lol.

[r.linder]

GIgabyte has issues as well

[Rod]

尺．し工几句ヨ尺님이 먼저 게시:

GIgabyte has issues as well

It got reviewed as S Tier. Whats the issues around Gigabyte right now?

[Guydodge]

stonks님이 먼저 게시:

The Commendatore님이 먼저 게시:

Won't be using the Sus brand for a while until they get their act together, if they ever do. I saw their beta BIOS and just laughed at it.

Sus brand.. I lol'ed

My Sus brand mobo arrives soon for my all new fire hazard build. Between Nividias's "don't ever bend it" cable and Asus' amazing AM5 BIOS it should be a good time. I'm actually not worried

the fact that 1.3volts is its limit means alot !!! how long do you think the cpu is going to last before degradation sets in ? not a gamble anyone should take.return it if you can