Home / News / PC Component News / Intel Recalls Sandy Bridge Processors

Intel Recalls Sandy Bridge Processors

David Gilbert

by

Intel Recalls Cougar Point Chipsets

You would imagine that a single transistor that's prone to a slightly higher current leakage than tolerable would not cost too much to fix. That is of course as long as the transistor in question is not on a support chipset for Intel’s new Sandy Bridge processor and then the estimated cost rises significantly - to around $700 million.

Yes, on Monday Intel confirmed it was stopping all shipments of its 6 Series or Cougar Point chipsets having identified “a design issue” which affects SATA-linked devices such as HDDs and DVD drives. The 6 Series chipsets are used in PCs sporting Intel's much-vaunted Sandy Bridge processors. Intel in a statement said it had stopped shipments of the broken chip and corrected the flawed design: “Intel has corrected the design issue, and has begun manufacturing a new version of the support chip which will resolve the issue. The Sandy Bridge microprocessor is unaffected and no other products are affected by this issue.”

The problem is down to a single transistor which can not only diminish performance over the 3Gbps SATA ports, it can actually make them fail altogether. However the problem does not affect the 6Gbps SATA ports so if you are only using these then there will be no need to send your machine back to get it fixed. A repair and replacement service is now taking place for everyone affected by the flaw and Intel said: “Intel will work with its OEM partners to accept the return of the affected chipsets, and plans to support modifications or replacements needed on motherboards or systems.” Systems affected have been shipping since 9 January but Intel believes “relatively few consumers are impacted by this issue.” Second generation i5 or i7 quad-core based systems are the only ones affected.

Intel said it expects to begin delivering the updated version of the chipset to customers in late February and expects full volume recovery in April. It estimates the cost of the recall and replacement at $700 million and has revised it Q1 revenue downwards by $300 million as a result, though it expects full-year revenue to remain unaffected.

Source: Anandtech via Engadget

Mattj

February 1, 2011, 6:54 pm

The fault isn't in the processor, it's in the motherboard, which is more of an issue- CPU's are easy enough to swap out. Motherboards less so.

miha

February 1, 2011, 6:58 pm

Could you please correct the (misleading) title and the starting paragraph of the news article, as it reads as if the fault was found in the Sandy Bridge processors, when in fact it was discovered in the supporting Cougar Point chipset? Thanks!

David Gilbert

February 1, 2011, 7:14 pm

@miha The headline and first paragraph have been changed, though the initial headline that Sandy Bridge processors had been recalled is technically true I see how it could be mis-interpreted. Also the opening paragraph said the issue was with the SB chipset rather than the SB processor itself.

Steve

February 1, 2011, 8:41 pm

I was due to take delivery of my new SB i2500K beast this week, this has really screwed things up. Not happy. To be fair, PC Specialist are not dispatching until there is some sort of plan in place, they have been very good at dealing with this nightmare so far. So good in fact that I might just tell them to hold my PC (and my cash) and just swap out the board once they become available in Feb/March.





I don't see the point in taking delivery of my new beast only to send it back a month later.

trained KILLA

February 2, 2011, 2:50 pm

I don't want to be pedantic but could you please use the word supporting instead of sporting. I have seen this in more than one article at Trustedreviews.





Thanks





Koray

supamario

February 2, 2011, 4:02 pm

@ trained KILLA


uh, sporting is correct. It means "contains", as opposed to supporting which means "can contain"

MonkeyBollocks

February 3, 2011, 1:38 am

@ trained KILLA


Doh, FAIL!!

comments powered by Disqus