• olosta@lemmy.world
    link
    fedilink
    English
    arrow-up
    76
    ·
    3 months ago

    “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.

  • ColeSloth@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    46
    ·
    edit-2
    3 months ago

    “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.”

    • ditty@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 months 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
    link
    fedilink
    English
    arrow-up
    39
    arrow-down
    1
    ·
    3 months ago

    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.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

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

      • sploosh@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

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

    • floofloof@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months 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
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    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.caOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months 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.