| View previous topic :: View next topic |
| Author |
Message |
corroonb
Joined: 04 Aug 2006
|
 Posted: Thu Jun 28, 2007 8:09 am Post subject: Critical update for Intel Core CPUs is out |
 |
|
http://www.theinquirer.net/default.aspx?article=40567
| Quote: |
Have Intel processor? Download the fix right now
By Theo Valich: Tuesday 26 June 2007, 07:26
A COUPLE OF WEEKS ago, we heard that Dell was dealing with a certain situation considering Intel dual-core MCW and quad-core KC marchitecture, and that the company was releasing urgent BIOS and microcode versions for its line up.
We learned that the affected CPUs are the Core 2 Duo E4000/E6000, Core 2 Quad Q6600, Core 2 Xtreme QX6800, QX6700 and QX6800.
In the mobile world, people with the Core 2 Duo T5000 and T7000 need to visit Microsoft's site, while the server guys will want to use motherboard BIOSes if they do not rely on Microsoft Windows operating systems.
The affected servers are Xeon 3000, 3200, 5100 and 5300s - or just about every model from the second generation of Core marchitecture.
Oddly enough, Yonah - 32-bit Core Duo processor - isn't among the affected cores.
We are assured that no product recall will happen, and that La Intella took all appropriate steps in order to minimise damage to its public image, because if a product recall happened, Intel's credibility would be ruined for good.
Anyway, if you have a Core CPU based machine, go to the link below to download the update. AMD processors are not affected at all, in case you were wondering. |
Link to update from MS: http://support.microsoft.com/?kbid=936357 |
|
| Back to top |
|
 |
hanguker
Joined: 16 Mar 2005
Location: Korea
|
| Posted: Thu Jun 28, 2007 2:11 pm Post subject: |
|
|
I'm interested about where they got the information that only Core 2 Duo E4000/E6000, Core 2 Quad Q6600, Core 2 Xtreme QX6800, QX6700 and QX6800 were affected.
I went to the Microsoft link and they didn't specify any particular model. |
|
| Back to top |
|
|
mrsquirrel
Joined: 13 Dec 2006
|
| Posted: Thu Jun 28, 2007 3:48 pm Post subject: |
|
|
| Does it only effect Windows machines or all Core 2 chips? |
|
| Back to top |
|
|
mrsquirrel
Joined: 13 Dec 2006
|
| Posted: Thu Jun 28, 2007 4:23 pm Post subject: |
|
|
| Quote: |
Around April 10th, 2007, Intel released a microcode update (BIOS flash to the rest of us) so resolve several major issues with how Intel Core 2 series processors operate.
Intel has provided a microcode update as a critical software fix. This Intel microcode update addresses an improper Translation Lookaside Buffer (TLB) invalidation that may result in unpredictable system behavior such as system hangs or incorrect data. OEM's are making available a system BIOS upgrade that integrates a new version of this Intel microcode to address this potential but extremely rare issue. While the occurrence of this issue is extremely rare, OEM's strongly recommends upgrading the system BIOS to an updated version. Intel has indicated that the microcode update has no known measurable performance impact and provides a complete and comprehensive resolution to this issue.
The issues can affect any workstation that uses Intel Core2 Duo desktop processor E4000 and E6000 sequences, Intel Core2 Quad desktop processor Q6600 and Intel Core2 Extreme processors X6800 and QX6700 processors.
While the implications of the issue are difficult to quantify, any of the following symptoms can occur:
The system may stop responding to keyboard or mouse input.
A system operating in a Microsoft Windows environment may generate a blue screen.
A system operating in a Linux environment may generate a kernel panic.
Thanks to Guest for disclosing this information in General Hardware.
Watch for BIOS updates for your motherboards |
This appears to have be known since April |
|
| Back to top |
|
|
Demophobe
Joined: 17 May 2004
|
| Posted: Thu Jun 28, 2007 4:23 pm Post subject: |
|
|
| mrsquirrel wrote: |
| Does it only effect Windows machines or all Core 2 chips? |
While I understand that computer + problem = MS for many, the article was pretty darn clear that it was a hardware problem. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
