Info Motherboard software bug can accidentally kill AMD Ryzen X3D CPUs

[DrMrLordX]

Anything so long as it smears AMD.

Yeah pretty much.

 

[Abwx]

Anything so long as it smears AMD.

From post number one that was the purpose of this thread...

 

[TheELF]

So you're claiming that "hackers" are going to try to overvolt and kill your X3D CPU using the same hooks used by MSI's software?

You can try to protect AMD all you want but people don't have goldfish memories, they remember things.
This happened just one year ago.
In this case it wasn't a huge deal because the CPUs wouldn't fry immediately but with an x3d CPU many CPUs would have died.

AMD Confirms Its GPU Drivers Are Overclocking CPUs Without Asking

Radeon Adrenalin drivers have a mind of their own

www.tomshardware.com

AMD has confirmed to Tom's Hardware that a bug in its GPU driver is, in fact, changing Ryzen CPU settings in the BIOS without permission. This condition has been shown to auto-overclock Ryzen CPUs without the user's knowledge.

Overclocking a Ryzen CPU requires the software to manipulate the BIOS settings, just as we see with other software overclocking utilities. For AMD, this can mean simply engaging the auto-overclocking Precision Boost Overdrive (PBO) feature. This feature does all the dirty work, like adjusting voltages and frequency on the fly, to give you a one-click automatic overclock.

 

[TheELF]

So post in the vulnerabilities thread? Doesn't seem to have much relevance in this very specific thread.

Doesn't have much relevance?!
This is the only thing this thread is about!
Have you read the title?!
"software bug can accidentally kill AMD Ryzen X3D CPUs"

 

[Steltek]

From post number one that was the purpose of this thread...

You are welcome to your opinion FWIW, but that wasn't the reason that I made the original post.

I personally don't have a preference for Intel or AMD. My next system will probably be built using AMD, but that is more due to AMD's current power efficiency over Intel (which is impressive) rather than anything related to performance (which, for everyday use is a wash). The fanboi idiots can take their opinions and stick them up their rear orifices so far as I am concerned. I don't pay attention to any of them either way.

However, more than one of the prominent hardware folks that I happen to tend to follow closely had indicated that there might be a problem that people needed to be aware of.

Nothing more, nothing less.

 

[Abwx]

You are welcome to your opinion FWIW, but that wasn't the reason that I made the original post.

I personally don't have a preference for Intel or AMD. My next system will probably be built using AMD, but that is more due to AMD's current power efficiency over Intel (which is impressive) rather than anything related to performance (which, for everyday use is a wash). The fanboi idiots can take their opinions and stick them up their rear orifices so far as I am concerned. I don't pay attention to any of them either way.

However, more than one of the prominent hardware folks that I happen to tend to follow closely had indicated that there might be a problem that people needed to be aware of.

Nothing more, nothing less.

Fact is that there s no software bug, as pointed by many members here there s no way to kill the CPU if one doesnt go in manual settings that offset the voltage auto values, it has to be a voluntarly badly set voltage to get this result, if there s no such manipulation then there s absolutely no risk for the user contrary to your sayings, because a software bug would be something that is badly set even at stock settings, wich is obviously not the case.

 

[jpiniero]

There are too many idiots out there> lets just agree that its NOT AMDs fault.

I'd say it's the board makers fault. There's a reason why AMD had wanted to lock down the overclocking on the vcache chips.

 

[DrMrLordX]

You can try to protect AMD all you want

They don't need any protection.

but people don't have goldfish memories, they remember things.
This happened just one year ago.
In this case it wasn't a huge deal because the CPUs wouldn't fry immediately but with an x3d CPU many CPUs would have died.

AMD Confirms Its GPU Drivers Are Overclocking CPUs Without Asking

Radeon Adrenalin drivers have a mind of their own

www.tomshardware.com

That's totally unrelated to the issue at hand. The GPU driver wouldn't then (and won't now) "accidentally" overclock 5800X3D CPUs. Only the MSI software is doing it.