Deutsch   English   Français   Italiano  
<slrnvadqu3.1e7m.candycanearter07@candydeb.host.invalid>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.sys.ibm.pc.games.action
Subject: Re: Intel's High-End CPU Problem
Date: Mon, 29 Jul 2024 01:10:04 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 38
Message-ID: <slrnvadqu3.1e7m.candycanearter07@candydeb.host.invalid>
References: <2jkl1jdq6oqce5a88od8k19s95ciasjj9j@4ax.com>
 <13hbaj5hpbe64gq7hlru5ioe31ifb3bc1p@4ax.com>
Injection-Date: Mon, 29 Jul 2024 03:10:04 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="4de8d21f39bcc08907fe0af0379a9422";
	logging-data="192801"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19aBH2fsadaMQMMdM6UlI1xLCgWaN+5JOjWChtixhZz6w=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:Jk2rRMronfiWMHnPZ7+exc7yyOk=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 2798

Spalls Hurgenson <spallshurgenson@gmail.com> wrote at 04:16 this Sunday (GMT):
> On Sat, 13 Apr 2024 15:06:16 -0400, Spalls Hurgenson
><spallshurgenson@gmail.com> wrote:
>
>>
>>This isn't really news - in fact, I posted about the problem being
>>reported back in February - but the story* is gaining more traction
>>recently.
>
> Just a bit of an update on this story:
>
> Intel is working on a microcode update that should prevent this bug on
> future 13900K/14900K CPUs. It turns out not /all/ the blame can be
> laid on motherboard manufacturers, as there were issues in the CPUs'
> microcode and manufacturing which allowed the CPU to overvolt. 
>
> Unfortunately, people who already are experiencing crashes won't find
> relief from these updates; the damage has been done. The only way to
> restore stability is to undervolt/down-clock the CPU through the BIOS.
> However, long term the only real solution would be to replace the CPU.
>
> Despite acknowledging the flaw was at least partially to blame on
> Intel, they've steadfastedly refused to recall the chips, replace them
> at Intel's cost, or even extend the warranty. Real classy, Intel.

classic "its not our fault so we wont refund you"

> Obviously I'm a bit sore about this. I really don't want to have to
> spend $500 on a new CPU. But I might have to.
>
>
> Read more details here:
> https://www.theverge.com/2024/7/26/24206529/intel-13th-14th-gen-crashing-instability-cpu-voltage-q-a


best of luck :D
-- 
user <candycane> is generated from /dev/urandom