this post was submitted on 23 Jul 2024
180 points (97.4% liked)

Technology

57904 readers
4399 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
enu@lemm.ee
fry@fry.gs
L3s@fry.gs
enu@lemmy.world
L4s@fry.gs
L4s@lemmy.world
180
Intel breaks silence on 13th and 14th-gen Raptor Lake desktop CPU instability issues (www.notebookcheck.net)
submitted 1 month ago by floofloof@lemmy.ca to c/technology@lemmy.world
33 comments fedilink hide all child comments
top 33 comments
sorted by: hot top controversial new old
[–] olosta@lemmy.world 76 points 1 month ago (2 children)

"Gamers Nexus, on the other hand, thinks the issue is more deep rooted and originates from a foundry-level fault."

  • The GN piece makes it very clear that this claim is not definitely true but is a line of inquiry.
  • Intel statement does not definitely exclude this hypothesis, the flawed CPU might need the lower voltage to work around the flaw.
  • The obvious question this article does not address is what will be the performance hit for the patched parts?

That's a bit annoying to see GN so grossly misquoted when Steve spends half the run time of the video explaining that they are not sure of anything at this point.

[–] wjs018@lemmy.world 39 points 1 month ago (1 children)

Intel confirmed on reddit that oxidation did impact some chips.

More than one thing can be wrong at the same time, so everybody can be right!

[–] jlh@lemmy.jlh.name 15 points 1 month ago (1 children)

They admitted that there was an oxidation defect and they haven't started a recall or even listed serial numbers?

[–] fuckwit_mcbumcrumble@lemmy.dbzer0.com 11 points 1 month ago (1 children)

It's a lot cheaper to say "if you think you're affected contact us" than it is to proactively reach out with a recall.

[–] jlh@lemmy.jlh.name 7 points 1 month ago

It's also a lot easier to scam people by keeping them in the dark and denying them RMAs until their warranty runs out after you sold them a broken product. The whole thing smells like stalling until after the AMD launch next week.

[–] ZealousSealion@discuss.tchncs.de 0 points 1 month ago (2 children)

Steve does go on, and on, and on, and on... Quite challenging, if you have a tight deadline.

[–] jlh@lemmy.jlh.name 15 points 1 month ago

He's just really thorough. They have a text-based website too if you prefer that format for reviews, but they don't always have time to make text articles of their investigative pieces and news reports.

https://gamersnexus.net/

[–] fuckwit_mcbumcrumble@lemmy.dbzer0.com 6 points 1 month ago

For most of their videos you can just play it in the background.

But that said, why are you watching any youtube videos if you have a "tight deadline"?

[–] ColeSloth@discuss.tchncs.de 46 points 1 month ago* (last edited 1 month ago) (1 children)

"We're going to undervolt them. You're stuck with the damage done, and you won't have luck overclocking or getting as much performance from our chips."

[–] dditty@lemm.ee 4 points 1 month ago

Not only that, but I don't think stability issues like this would've been known around or shortly after launch, so Intel (likely unknowingly) got to mislead consumers and reviewers into thinking that their 13th/14th HEDT processors were close to competitive with AMD's, when they were anything but. It's never been more apparent how stagnant Intel truly has become, and that's already been a trope for years.

[–] cmnybo@discuss.tchncs.de 38 points 1 month ago (3 children)

Nice one Intel. My next computer certainly will not contain an Intel CPU.

I wish someone would start making desktop motherboards with socketed RISC-V and ARM CPUs.

[–] cyberpunk007@lemmy.ca 17 points 1 month ago

Why I chose AMD in 2019.

[–] CaptDust@sh.itjust.works 12 points 1 month ago* (last edited 1 month ago)

risc v wouldn't be worth much right now but snapdragon I could see getting socketed at some point.

[–] Tarball@lemmy.world 4 points 1 month ago (2 children)
[–] cmnybo@discuss.tchncs.de 10 points 1 month ago (4 children)

That would be great for a server, but 1.7GHz is a bit slow for a desktop.

[–] Tarball@lemmy.world 4 points 1 month ago* (last edited 1 month ago) (1 children)

Up to 128 cores. Not meant for gaming, but it cranks at server tasks, compiling & coding tasks, etc.

There’s a windows dev kit (ARM) that I think is 3ghz: https://www.microsoft.com/en-us/d/windows-dev-kit-2023

But bleeding edge stuff from MS means likely driver issues, and this isn’t something you’ll throw a dedicated graphics card in.

Still, feels like the tide is changing away from Intel. I too was looking at “ARM for Desktop” options a couple weeks back.

[–] aard@kyu.de 3 points 1 month ago

I have a 96 core one. While it'll be fine as a desktop for compiling I'd stick with an AMD system.

The devkit has 6 memory channels, and you'll want to fill them all - there's a surprisingly high performance penalty if you don't. Even then, compiling a code base which could be spread over hundreds of cores is still significantly slower on the ampere compared to my old 3970x.

[–] fuckwit_mcbumcrumble@lemmy.dbzer0.com 2 points 1 month ago

It's not like risc-v is any faster at the moment.

[–] Peffse@lemmy.world 2 points 1 month ago

My first thought went to the Milk-V Pioneer since it has mATX form factor, but both products are priced way higher than your average desktop.

https://milkv.io/pioneer

[–] umbrella@lemmy.ml 1 points 1 month ago

not to mention its a dev kit. at this point not everything will run\be problem free.

[–] jlh@lemmy.jlh.name 5 points 1 month ago

Ampere is pretty slow compared to AMD and Intel.

https://www.phoronix.com/review/intel-xeon-6700e-ampere-altra/6

[–] just_another_person@lemmy.world 33 points 1 month ago (2 children)

AMD stock should have gone through the roof on this news.

[–] qaz@lemmy.world 9 points 1 month ago* (last edited 1 month ago) (3 children)

Fyi. AMD has gone down 13% this week. Intel went up today.

[–] just_another_person@lemmy.world 20 points 1 month ago

No clue why. AMD is killing it right now, and they're just slaughtering Intel's positions in the market for the next number of years.

[–] altima_neo@lemmy.zip 3 points 1 month ago

Everyone's excited for Battle mage

[–] Blue_Morpho@lemmy.world 3 points 1 month ago

I think insiders already knew about this problem. It would explain why the stock has been dropping over the past few months.

[–] tal@lemmy.today 1 points 1 month ago (1 children)

This is actually good for Intel, if they think that they can actually fix the problem in microcode.

[–] sploosh@lemmy.world 2 points 1 month ago

They can keep the problem from starting, but any processors that are already impacted need to be RMA'd

[–] melroy@kbin.melroy.org 14 points 1 month ago

Go with amd for now.

[–] jlh@lemmy.jlh.name 5 points 1 month ago (1 children)

This doesn't seem like the whole story, and it's awfully convenient that everything will be fixed AFTER the AMD launch next week, when they've known about this issue for over a year.

Alderon Games is accusing Intel of running damage control here.

https://www.reddit.com/r/intel/comments/1e9mf04/comment/leg5umu/

[–] floofloof@lemmy.ca 2 points 1 month ago

It's not the whole story. After Intel's press release about voltage issues and an upcoming microcode patch, they quietly snuck out an admission that there is an oxidization problem after all. It smells like they're trying to downplay that and avoid having to replace their faulty CPUs.

https://youtu.be/OVdmK1UGzGs?si=P4QfyLmAW3dUJ7nE

[–] SeaJ@lemm.ee 3 points 1 month ago (1 children)

Level1Tech looked a good amount into it and he's not convinced microcode updates, which they have released many, will fix the issue.

[–] floofloof@lemmy.ca 1 points 1 month ago* (last edited 1 month ago)

They won't, since Intel has quietly admitted now that there is an oxidization issue too. Microcode can't fix that, and if it can work around it, it will do so at a significant performance cost.