I put on the last of my warpaint when it was revealed they knew about the fab defects and were still denying RMAs for DC by the 1000s. It turns out Hardware Times never got the promised refund either.
This thread has obviously deviated from its topic, courtesy of the OP, who is clearly more interested in ragebait.
I would suggest the forum overseers shut this thread down.
There's nothing more to be discussed here.
ASUS has outed new BIOS with updated settings profile called Intel Baseline Profile.
View attachment 97318Finally this crap is going to end. Now Intel just needs to enforce this profile on initial setup across all vendors.
No, I never intended to post the new one. I posted one of his vids on the topic months back and regret it. He has no integrity or journalistic ethics. He will do or say anything for money. He needs to take some of his shillions of dollars and go to fat camp instead of playing the sympathy card over his health issues with the audience. And using it as an excuse why his bumbling sidekicks were making content that shilled so hard, and was so incompetent, that he had to respond while recovering from surgery.You posted just his old video, you probably wanted to post the new one or both.
The Haha reaction i gave your post was insufficient.I think my favorite was this sillyness, from 8 years ago... took me a few minutes to find it. Time queued up at best part... the drilling of the mobo for a water cooler block.
The Haha reaction i gave your post was insufficient.
can you imagine if TSMC had these fab issues?Der8auer jumps on the bandwagon with a reaction video for clicks... I'm kidding he has a short video with a very nice explanation about how via oxidation works. He also concludes with a common sense request: Intel must find ways to maximize the number of customers who are made aware of the microcode issue.
Fun fact, chips affected by oxidation never stood a chance: not only did oxidation accelerate aging, it also provided the perfect catalyst for the erroneous high voltage to wreak havoc through the die. What a perfect storm.
I should mention I never contested the experience he was having with that 13900K system, I just disagree with the poorly documented diagnosis. Even if we trust TYC and he trusts the source, the message was lost in translation. There's nothing of substance for us to work with.As for TYC's view on the intel stuff, his explanation may not be the best but he seemed to trust his source who mentioned it to him at computex.
I'm having a lot of fun with this "me too" movement. Surprising how many journalists had major issues with their 13900K/14900K and they kept mostly quiet.When Digital Foundry is considering switching to AMD CPUs, we are in the "hell freezing over" territory:
can you imagine TSMC having such issue and covering it up for 1 year or more?can you imagine if TSMC had these fab issues?
Wendell talked about some of the psychology on the MLID interview.I'm having a lot of fun with this "me too" movement. Surprising how many journalists had major issues with their 13900K/14900K and they kept mostly quiet.
Wendel gave voice to so many vulnerable journalists!
Agree with you when it comes to data centers or game dev, but with journalists the tune is somewhat different. Part of journalism is investigation, probably the best part too. Maybe it will be worth to develop this topic later, after the Intel problems reach some kind of resolution.Wendell talked about some of the psychology on the MLID interview.
i dont excuse them, but in terms of the delay in entertaining the possibility of an issue we really havent seen a screw up this big in a while.Agree with you when it comes to data centers or game dev, but with journalists the tune is somewhat different. Part of journalism is investigation, probably the best part too. Maybe it will be worth to develop this topic later, after the Intel problems reach some kind of resolution.
Igor did joking talk about copy and pasters of anything he says on comments to the previous news items on igorlabs.de, and basically said he had to wait with the internal leak:Another article on Tom's. They just recap points from Igor's lab, apparently coming from Intel:
Here's a snippet of the purportedly leaked communications given to Igor's Lab:
– Intel observes a significant increase to the minimum operating voltage (Vmin) across multiple cores on returned affected processors from customers.
– This increase is similar in outcome to parts subjected to elevated voltage and temperature conditions for reliability testing.
– Factors contributing to this Vmin increase include elevated voltage, high frequency, and elevated temperature.
– Even under idle conditions at relatively cool temperatures, sporadic elevated voltages are observed when the processor is resumed from low power states in order to service background operations before entering a low power state again.
– At a sufficiently high voltage, these short-duration events can accumulate over time, contributing to the increase in Vmin.
– Intel analysis indicates a need to reduce the maximum voltage requested by the processor in order to reduce or eliminate accumulated exposure to voltages which may result in an increase to Vmin.
– While Intel has confirmed elevated voltages impact the increase in Vmin, investigation continues in order to fully understand root cause and address other potential aspects of this issue.
––Intel—
Leaked internal reports allegedly reveal Intel's instability problems are not over — elevated voltages could be only one of the causes of CPU crashing
Intel purportedly doesn't know if the mid-August microcode update will fully rectify Raptor Lake's stability issues.www.tomshardware.com
Nah, hell only freezes over when they switch away from Nvidia GPUsWhen Digital Foundry is considering switching to AMD CPUs, we are in the "hell freezing over" territory:
One of the hosts, who has one of the affected / degraded 13900K CPUs, that he is downclocking etc, to keep it from crashing.
Cheaper, and the intel hedt chips are all crap atm.Since so many professionals are running standard desktop processors, doesn't the longevity of the socket matter to them?
I would have thought that they also could keep their overall cost down, by simple CPU upgrades?
Maybe 0.5 to make that 3 objectives would be to keep the chipset team busy. I bet the AMD chipset team has a lot less work to do than the ones at Intel and also a lot less time spent trying to invent "new" stuff for the next chipset family.I suspect that for Intel socket shortevity always had 2.5 objectives:
1. Keep Intel's older foundries busy (also see Atom for at least a decade after inception)
2. Keep OEMs happy with something new to sell.
2.5 match each CPU gen to an exact chipset gen, and have less work doing firmware updates.
But the driving motivation behind it is purely profit because they make both the CPU and the chipset.The easiest explanation is probably the right one - they just put themselves on a cadence.