Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
I would also wait until 2-3 months after BIOS updates are released because those can break the system. I seen it happen for Gen 1.
Also, do not forget about the AMD Chipset driver. And of course, save the current working BIOS somewhere before updating, just in case it fails.
And please read all red lettering disclaimers for your motherboards and follow those directions carefully and fully. Do not skip anything! Pay attention...
"Hey guys we know you recently upgraded but anyone who bought this series cpu, um, your board and cpu may be permanently ruined. But, we fixed it."
I don't mind the incompetence in this specific situation. Knowing my board might melt/cave in at any moment? it's the kind of exhilaration that beating a game just can't get me.
That it was done with malicious intent? I find this unlikely. Incompetence, maybe.
That AMD isn't responding satisfactorily? AMD is offering support to anyone affected. They've also issued a new AGESA/BIOS to stop the boards from giving the SoC too much voltage when Expo is used (almost like when they say memory overclocking is overclocking, they mean it or something, who knew?). If you're not affected, update your BIOS to mitigate the risk going forward.
That things should always be perfect and mistakes should never happen? As much as I wish it with you, that's not the reality of our world. I said in my last post but I've watched this happen across the gamut of companies and the gamut of PC parts (or rather, gamut of markets because it happens everywhere).
And at least it was addressed this time. I've seen plenty of "responses" where the issue gets swept under the rug. Sometimes the part gets a revision and those on the old one are left dealing with it. Been there done that recently with Intel. Samsung recently did it with SSDs. nVidia's done it. Microsoft has done it. Has anyone NOT made a mistake?
Thats the expo it was sold under, 1.35v 6000mhz expo.
The SoC is the "system on a chip". It's part of the CPU itself. The IMC (integrated memory controller) is part of that, and it will need more voltage with more demanding memory configurations. For example, I see mine (on both Zen 2 and 3 CPUs, so not Zen 4) go to ~1.1V (see picture in my first post) instead of a more normal 1.05V for those CPUs, probably because I have four modules of dual rank RAM running at 3,600 MHz. Apparently this runs much higher with Zen 4 though.
So when Expo was enabled, the IMC was being given these higher voltages to be able to run with the RAM at that speed. Apparently there were also spikes ABOVE this 1.35V which is, from the way I'm interpreting it, what was really contributing to the problem.
While the problem has been identified that it could affect any AM5 CPUs, the fact that it infamously started with the 7800X3D, a recent CPU, means the damage was done in short order. So if you have a non-X3D CPU and apply the BIOS update, I really wouldn't worry too much.
It seems typical for it to run higher on Zen 4 though. I'm not sure if there's any tolerance difference but there's still going to be a limit of course, and apparently they are flirting with it. Running at 1.35V+ long term and/or spiking even higher (1.4V or 1.5V) is risking burning them up.
the imc on the cpu is different
And apparently it's only for the 3d versions
There are multiple simultaneous issues which are getting conflated together. The issue on the CPU side is not only on the X3D versions but they are more sensitive to the issue.
The issues on the motherboard side for those that have them is that the voltage set (regardless of being set to Auto or manually set to a specific voltage) isn't respected and runs beyond the safe spec provided by AMD.
the boards mfg are being lazy and not forcing safe voltages or current protections
at 1v, pulling 200w is 0.005ohm, nearly a dead short, which is what the board would need to detect after things go horribly wrong to protect the board and its socket