alessandro@lemmy.ca to PC Gaming@lemmy.ca · 4 months agoIntel's CPU instability and crashing issues also impact mainstream 65W and higher 'non-K' models — damage is irreversible, no planned recallwww.tomshardware.comexternal-linkmessage-square20fedilinkarrow-up1212arrow-down10cross-posted to: [email protected]
arrow-up1212arrow-down1external-linkIntel's CPU instability and crashing issues also impact mainstream 65W and higher 'non-K' models — damage is irreversible, no planned recallwww.tomshardware.comalessandro@lemmy.ca to PC Gaming@lemmy.ca · 4 months agomessage-square20fedilinkcross-posted to: [email protected]
minus-squareqaz@lemmy.worldlinkfedilinkarrow-up18arrow-down1·edit-24 months agoWindows required CPU’s to have certain extensions/instructions to use the newest version, which might have required buying a new CPU and thus getting one of the affected ones. However, I don’t think it’s reasonable to blame Microsoft for this.
minus-squaremsage@programming.devlinkfedilinkarrow-up15·4 months agoM$ is not the source of this problem, but they did force TPM 2.0 on their OS, forcing people to throw away older CPUs, so they made it much worse.
minus-squareqaz@lemmy.worldlinkfedilinkarrow-up4arrow-down1·4 months agoOh yeah, I forgot about TPM 2.0 and was just thinking about POPCNT etc.
Windows required CPU’s to have certain extensions/instructions to use the newest version, which might have required buying a new CPU and thus getting one of the affected ones. However, I don’t think it’s reasonable to blame Microsoft for this.
M$ is not the source of this problem, but they did force TPM 2.0 on their OS, forcing people to throw away older CPUs, so they made it much worse.
Oh yeah, I forgot about TPM 2.0 and was just thinking about
POPCNTetc.