Critical update for Intel Core CPUs is out

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 X6800, XC6700 and XC6800.

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. µ

A microcode reliability update is available that improves the reliability of systems that use Intel processors

A microcode reliability update is available that improves the reliability of systems that use Intel processors

dudes, how come my vista with my fx-60...i dont feel the dual core
its like the system can be so slow like shit and hang (i know this stupid original vista is unstable) but is there anyway to check?
in the task manager, the bars for each cores memang lain
how eh

Microcode updating is not really new, not just Intel have this problem. AMD K6 series and older Pentium III/4 have the same problem. Newer K7/K8 doesn't inherit this problem.

So update is your best choice if you are using Windows.

is this hotfix gonna rewrite some register or memory inside the processor?

The K7 and K8 also have microcode update mechanisms, and they have had microcode updates IIRC. There was even a big deal in some circles a few years ago because some ppl managed to crack the K7 microcode update mechanism.

edit: Apparently i did remember correctly. Scroll down to bios update V1.4, point 2.
http://www.uabit.com/index.php?option=com_...atal1ty+AN9+32X

Yup, many motherboard update includes microcode update but in this case it is an update relating to Windows operating system specifically.

Makes no difference whether it is updated via windows or the BIOS. End result is the same.

Yup, but affecting Windows only? Humm, that's kinda funny. It is not the CPU problem that's bother me, it's Windows unreadiness to adapt future hardware.

I don't like to bash Windows, because I am using it and proud of it, just a small funny story like this tickles.

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.

If it requires a microcode update, it's not microsoft's problem, it means the problem is in the chip. It probably happens that microsoft stumbled upon the problem, some instruction or combination of instructions they use trigger the problem. I'm sure more people run windows update than update their bios, so the best bet is to just fix it there.

Does this affect the T-series cores?

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.

so do we have to update windows with this patch every time we format or is it just a one time process? Dunno whether same like 'flashing'.

What a bout laptops? Reason is i'm getting my laptop tomorrow and i don't think BIOS upgrades for laptops are all that easy to find.

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.

In rare instances, improper TLB invalidation may result in unpredictable
system behavior, such as system hangs or incorrect data. Developers of operating systems should take this documentation into account when
designing TLB invalidation algorithms. For the processors affected, Intel has provided a recommended update to system and BIOS vendors to incorporate into their BIOS to resolve this issue.

Hardware Home: Intel Core 2 CPU error discovered and patched
By: Oscar Meade - Published June 28, 2007 at 4:22 PM EDT - Writer Archive
Error in TLB cache in Intel Core 2 CPUs that is used to improve the speed of virtual address translations fixed.
Via The Inq: "At first Intel posted the details about these particular errata back in late April inside a Core 2 Specification Update PDF document, explaing how this error could cause memory leaks and ultimately, lead to crashes.

"We've addressed a processor issue by providing a BIOS update for our customers that in no way affects system performance. We have documented this as an errata. All processors from all companies have errata, and Intel has a well-known errata communication process to inform our customers and the public. Keep in mind the probability of encountering this issue is low. Intel documented the issue a few months ago - Specification Updates for the affected processors are available at http://developer.intel.com."

The errata inside all Core 2 processors (T series, E series, Q series, QX series and Xeon 5000 series) can appear in very rare cases, and it can result a computer refusing to accept keyboard of mouse inputs. In Windows environment, it may result with a worldly known Blue Screen of Death, while Linux'es of this world may end up with kernel panic.

In conclusion, this problem has been fixed, with BIOS updates for motherboards containing fixes after the erratum was posted on developer.intel.com. Microsoft came up with a patch that will stop errata from possibly appearing, Apple already updated Mac OS X while the Linux status is unknown at time of writing*. It remains to be seen whether the companies will rather choose to go full disclosure of every error that happens in the future"

here another article of it
by the way, could any1 upload to another website so i could update also? Because i using pirated win XP PRO?

Intel Core 2 Duo Has 'Non-Fixable' Bugs, OpenBSD Founder Alleges

Source : http://www.extremetech.com/article2/0,1558...2129TX1K0000532

i used the patch
seems no rasa

Well, I don't think it is overhyped.  It is about time we hear some serious erratas from INTEL.  We can't just blame Windows all the time when we get a BSOD.  The CPU is at fault not Windows for a change!

e6300 need this upgrade?

Theo de Raat (OpenBSD guy) has a lot of bad blood with Intel just because Intel refuses to provide all tech docs on their wireless drivers. Most Linux/BSD VVIPs don't like him much.

yea, i've been wondering too. can someone pls enlighten us? 

The errata inside all Core 2 processors (T series, E series, Q series, QX series and Xeon 5000 series) can appear in very rare cases, and it can result a computer refusing to accept keyboard of mouse inputs. In Windows environment, it may result with a worldly known Blue Screen of Death, while Linux'es of this world may end up with kernel panic.

any application or software that can caused bsod with this particular bug?

If ur proc starts with E, better panic