- Jun 10, 2004
- 14,595
- 6,067
- 136
MLID (yeah, I know) presses X to doubt Intel:
My take:
After months of "nothing to see here, move along" Intel finally makes two big admissions:
1) The problem is real (I still think they are downplaying the scope)
2) Damage is permanent
To their credit, they are saying users can reach out to Intel about affected chips. How the end user diagnoses and proves this for RMA approval is up in the air. Hopefully they don't deny RMAs like they have been, either.
Intel also conveniently punts a fix that supposedly has no performance impact to after the competitor launches their next gen. While quietly launching a a i9-14901KE with only P-cores that peaks with TVB at 5.8GHz.
Wait. 5.8GHz for max boost and max TVB? Almost like they're hitting a hard wall at that frequency... hmm, what could possibly be the reason for that?
My take:
After months of "nothing to see here, move along" Intel finally makes two big admissions:
1) The problem is real (I still think they are downplaying the scope)
2) Damage is permanent
To their credit, they are saying users can reach out to Intel about affected chips. How the end user diagnoses and proves this for RMA approval is up in the air. Hopefully they don't deny RMAs like they have been, either.
Intel also conveniently punts a fix that supposedly has no performance impact to after the competitor launches their next gen. While quietly launching a a i9-14901KE with only P-cores that peaks with TVB at 5.8GHz.
Wait. 5.8GHz for max boost and max TVB? Almost like they're hitting a hard wall at that frequency... hmm, what could possibly be the reason for that?