@alessandro@lemmy.ca to PC Gaming@lemmy.ca • 9 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-up1213arrow-down10
arrow-up1213arrow-down1external-linkIntel's CPU instability and crashing issues also impact mainstream 65W and higher 'non-K' models — damage is irreversible, no planned recallwww.tomshardware.com@alessandro@lemmy.ca to PC Gaming@lemmy.ca • 9 months agomessage-square20fedilink
minus-square@Flatfire@lemmy.calinkfedilink9•8 months agoWat. This has nothing to do with Windows 11 system requirements.
minus-squareqazlinkfedilink17•edit-28 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-square@msage@programming.devlinkfedilink15•8 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-squareqazlinkfedilink3•8 months agoOh yeah, I forgot about TPM 2.0 and was just thinking about POPCNT etc.
Wat. This has nothing to do with Windows 11 system requirements.
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.