this post was submitted on 25 Jul 2024
607 points (96.1% liked)

linuxmemes

21160 readers
1354 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    607
    My PC didn't crash three times making this meme (lemmy.dbzer0.com)
    submitted 3 months ago by [email protected] to c/[email protected]
    26 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 13 points 3 months ago (4 children)

    Intel crashes?

    [–] [email protected] 7 points 3 months ago

    Oxidation in the fab process. They have simultaneously claimed that oxidation isn't causing any issues, and that it's caused only "some" crashing issues. Because they've been so wishy washy, it's probably safe to assume that any 13th or 14th gen CPU that experiences any kind of crash or BSOD is degraded and should be RMA'ed immediately, otherwise you risk getting stuck with a permanently physically degraded CPU.

    Intel says they identified the issue sometime in 2023 and fixed the fab process. So the good news is that any newly manufactured Raptor Lake CPU shouldn't have this issue. The bad news is that Intel won't give a date range of when the fab issue occurred, or exactly what CPUs it affected (by date code), so really the only choice consumers have at this point (before we get to the inevitable class action lawsuit) is to RMA at the slightest sign of instability.

    Intel is also planning to release a microcode update in August, but there's a lot of doubt that this can be fixed via microcode.

    This was affecting 50% of Raptor Lake CPUs in data centers, and it's become clear via video game telemetry that it has also affected a significant number of consumer chips.

    https://youtu.be/OVdmK1UGzGs

    [–] [email protected] 4 points 3 months ago

    Not only do the 13th and 14th gen crash, but vendors ask for about 1000 dollars more for supporting servers with those chips.

    [–] [email protected] 19 points 3 months ago (2 children)
    [–] [email protected] 5 points 3 months ago

    AFAIK the current drama is not about a bug but manufacturing problems

    [–] [email protected] 7 points 3 months ago* (last edited 3 months ago)

    Oh well... that is not nice for the new Novacustom coreboot laptops!

    Edit: doesnt matter, as they ship new revisions.

    [–] [email protected] 29 points 3 months ago

    Yeah... Their desktop CPUs are in all the news right now for crashing linke crazy