Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
btw, it still doesn't make much sense about the claim that there is no fix because of oxidation, but doesn't explain why crashes can be solved by just pushing more core voltage, meanwhile the rest of the CPU is bing chilling, using the same voltages and core and other frequencies.
Oxidation is accelerated by voltage and temps and the environment its used it, so it makes sense that a bios update to lower voltage would extend its life, but if the chip is suffering from oxidation, think of it as rust, the only real way to prevent rust is protect it right? If its unprotected which some of the chips were from a manufacturing error, just like a naked piece of steel, it'll rust eventually, in this case oxidize. Could be matter of when, not if.
BROKEN Come Ryzen Get Well
If you wanted more cores the AMD R9 x3D chips would have been the go to thing to look at for gaming, or the R9 non-x3D for general use.
2. It's already confirmed that it was a manufacturing issue in regards to VIA oxidation which was a smaller number of affected users compared to the eTVB bug which is entirely microcode. If it was a hardware level issue then it would be affecting far more users, the rate of issues is still low enough that there's been more issues and failures found in Ryzen 7000 series, at least based on Puget Systems' own data which was taken from both problems found by Puget themselves and by their customers. It's not a 100% failure rate across the entirety of Raptor Lake users, there are tons of users that haven't had a single crash yet and many of them claimed they hadn't even updated BIOS for the recent microcode updates.
It's a risky decision to buy into it but it's not the end of the world, there's no guarantee that buyers will experience problems and people shouldn't be making any guarantees on that, the data doesn't back it up. That's not to say people shouldn't worry about it, quite the opposite, but there's no guarantees that it's going to be any more risky than going with AM5, the rates are easily just as bad if not worse going with AMD.
https://www.pugetsystems.com/blog/2024/08/02/puget-systems-perspective-on-intel-cpu-instability-issues/
Note how 11th gen was considerably worse in failure rates, yet nobody really noticed or complained, mostly because it was an ignored generation. Raptor isn't that bad.
1) No they have not and are not, they are intentionally being vauge and have shown a willingness to deny valid RMA's and to outright avoid any direct responses to questions on this issue.
2) They have not "confirmed" anything, they have changed their own story multiple times and continue to keep changing it.
Linder - You are normally better educated on this type of stuff. Might want to study up on it a bit more before sounding like an intel rep and parroting intel's bad PR failure that at best can be described as them being in deceptive damage control mode.
https://www.youtube.com/watch?v=b6vQlvefGxk
Take the time and ^^^watch the vid^^^. Its a pretty comprehensive overview of just how shady and directly deceptive Intel is being here. Intel knows they screwed up, and Intel is working hand over fist to minimize the financial impact at the cost of the consumers, all in a situation where they wont even cop to what they have done.
Even the Puget Systems Perspective is being mis-represented by you in the way you are looking at it. Yes 11th gen had failures, but the issue r/n is more about how many 13'th and 14th gen are having *in the field failures* aka degradation *after deployment*.
Again, kinda sad to see you so behind on this one, you are typically on the ball. But not this time. Intel is clearly in the wrong, clearly being deceptive, and you are falling for their deception hook line and sinker.
https://www.intel.com/content/www/us/en/support/articles/000099567/processors.html
GN reported that Intel initially denied RMAs which was before their partners even knew about the issues which was when they were blaming instability on them, it changed after their partners found out about VIA oxidation and microcode potentially causing problems. That's obviously bad, it's a no-brainer, but it changed once the likely causes were properly identified and known by all parties.
Yes, Intel has changed things multiple times but their statement earlier this month still shows that they're promising up to 5 years on warranties for Raptor Lake CPUs.
2. GN has been getting a lot of attention, both positive and negative, because of the hit pieces they've made on companies, the LTT one was a rough patch because they did it prematurely and absolutely put Linus on blast while he was already trying to fix the problems that were addressed. The video divided people, forced LTT to stop everything for a month instead of working on things over time, hurt the relationship between GN and LTT, it wasn't a good look for either one of them.
People are reading way too much into the Intel situation acting like every single time you buy a Raptor Lake CPU, you're going to have problems, which isn't true, and even if something happens, the rate of which can't possibly be worse than having issues with AM5, and Intel will now more than likely honor their end which admittedly could be because of GN's coverage in part, however they still need to be more cautious about how they approach things and how they get the message across, because it's far too easy for people to take something and spin it however they please.
3. AMD has had their fair share of shady dealings, the difference is these days it's cool to burn Intel alive for it while AMD is forgiven too quickly. They're both slimy corporations, and you yourself possibly exposed something they could be doing when it comes to tray processors being found in boxed/retail packages, CPUs which don't receive the same warranty rules and could potentially allow them to refuse warranty on someone that bought it at retail, over a SKU#.
I'm not defending either Intel nor AMD, I'm calling things as I see it and looking at things realistically and not in the lens of good vs evil. They're all turdbags but we need both to keep the competition going, otherwise it'll be years of stagnation all over again.
It's in the book with title "Steve Jobs". He explained there, how he reacted when his company main product was cought with some issues. He explained the issue, he explained the resolution and finished his talk with sentense "but other companies have similar problems". Exactly this sequence.
I want to believe you did the same with no specific reason 😂
2. Already mentioned the fact that they're packing tray CPUs (which AMD doesn't directly support, they leave it up to OEMs to deal with) in boxed processor packages, meaning people who bought a retail processor could potentially be denied RMA if they had no proof that they specifically bought a retail packaged CPU and not an OEM/tray packaged product. There should be no reason why a tray SKU would be packaged in a retail SKU box. None at all.
3. Issues between EXPO and 7000X3D which mostly got blamed on ASUS and Gigabyte. AMD had to make significant changes to BIOS to prevent high vSOC with some EXPO profiles so that X3D CPUs wouldn't bulge and so VRMs wouldn't melt or explode... so a microcode issue. Same calibre of an issue as Intel's eTVB bug but it was destroying both CPUs and motherboards. AMD didn't get grilled anywhere near as hard because they didn't suck at damage control.
4. Intermittent USB issues that took years for AMD to fix and still happens on latest BIOS revisions for a lot of people. Blackscreen issues with GPU drivers that have been going on since RX 5000 series launched. Various other known issues with BIOS and drivers that get left unfixed for way too long which leads to users wanting to switch to Intel/NVIDIA where the rate of issues has trended lower most of the time, and I was one of those people, I used to love AMD hardware for the performance per dollar value but had far too many problems that AMD just wouldn't fix, switched to Intel and NVIDIA years ago and haven't had significant problems since.
The thing is, people think that they would be better than someone like Steve Jobs was, or any CEO they dislike for that matter, but the reality is that they lack the perspective to understand that if they were put in those shoes, they would be more or less the same. You're going to defend your position, your lifestyle, who you are, etc. regardless of what path you take. It's rare to ever see a rich CEO that isn't a total douchebag behind closed doors.
It is ok to discuss other companies issues, but please respect the topic. Make another one.
This is an error AMD CPUs will show if a machine check exception was caught by the CPU. Since a machine check exceptions is only flagged by either a CPU or RAM (I think, anyway?), and RAM can only do it if it's ECC RAM, then it only means said part identified it, not that said part is causing it.
I had that exact error. It showed up after I got a new video card. I did an RMA on the video card and it went away (I've still had the issue occur once in on instance afterwards so I'm not sure what to make of it, maybe that particular modded Minecraft configuration is just doing something the new video card or system still doesn't like). Oddly, the error got worse if I disabled XMP. And it's worth noting I do have a pretty "heavy" RAM configuration (but that's why it getting worse at slower speeds seemed odd to me). All in all, it definitely wasn't fun, but nothing about it provided me with enough data to say "there's definitely a reproducible and provable problem here and it's AMD's fault and they have to fix it" because I don't know that. All I do know is that from troubleshooting, the results didn't lie that introducing the video card brought the error, and doing an RMA resolved (mostly) it, so that error was apparently being thrown because of a faulty video card for me.
Some issues aren't as they appear, and others are cascading results where what seems to be causing it is only "failing" in that instance because some underlying thing it relies on failed first.
I had these on my 7800 XT (the actual cause of the above issue), another GPU infamous for it, and I don't think this one is drivers. I think it's bad hardware.
I also want to mention that I've seen people with nVidia cards (namely, RTX 30 and 40) reporting the same, even on lower wattage ones like RTX 3060s and 3070s.
Might be worse on AMD, I don't know, but I don't think this one is as simple as "bad drivers". Sort of have a suspicion quality is downhill these last few years and VRAM or some other part may be getting bad batches? No clue.
None of this is to defend AMD. I do have some qualms I could mention about their stuff. Things like Windows overwriting Adrenalin (and who's fault would that even be, anyway?). That one was infuriating until I stopped Windows from doing it. And things like new issues in certain drivers, but usually the issues are "this particular driver has this particular changed behavior under this particular method I'm running this particular game" and not so much the "the driver itself is unstable and crashing" like people tend to think. I've had none of these supposed stability issues with Adrenalin. None. Issues with certain drivers behaving an undesired way with certain things I do? Yes. But not crashing my system left and right. Not even once (yet...). And in fact, the extra features of Adrenalin over nVidia's control panel won me over. I can record with less performance loss than Afterburner, and get smaller file size and greater quality with AV1. That's been nice. Sure, there's OBS, but... why should I need all that extra software? Hopefully the nVidia App goes over well because nVidia needs to get out of the 2000s with its drivers. And I issues with both Intel and nVidia (drivers) too. Lots of them with nVidia. In other words, "same thing, different day" (or brand).
But I just wanted to comment on these two things you mentioned in particular as someone who experienced them, and give my input on them.