Microsoft recently release a patch (see KB article http://support.microsoft.com/kb/936357 ) that is a "microcode reliability update" for Intel Core2Duo processors. What the heck is this for? I did some searching on the net and it seems that vendors such as Dell are releasing BIOS updates for this, etc. I didn't see anything on Tom's on this yet, so I figured I'd post.
Intel reported that their Core2Duo had bugs that could affect the machine. I think since an old Pentium series had Math problem, Intel modified their design so an software could fix a bug in their processor. They sent those microcode to motherboard designer and OS. Those microcode must be reloaded each time you start your computer.
I've read some of the articles here on TH about the "errata" in some Intel processors. However, I'm not sure (since the KB article doesn't say and I couldn't find any info on this on Intel's site) exactly what the update is for. I have a Dell Dimension XPS 410 with a E6600 Core2Duo chip...I checked Dell's web site and there was a new BIOS update (2.5.0) for my computer posted on 06/26/2007...again with no info on what the update is for.
My point is that we shouldn't have to go on blind faith and install patches w/o knowing what they're supposed to fix. We need SOME level of detail.
I've read some of the articles here on TH about the "errata" in some Intel processors. However, I'm not sure (since the KB article doesn't say and I couldn't find any info on this on Intel's site) exactly what the update is for. I have a Dell Dimension XPS 410 with a E6600 Core2Duo chip...I checked Dell's web site and there was a new BIOS update (2.5.0) for my computer posted on 06/26/2007...again with no info on what the update is for.
My point is that we shouldn't have to go on blind faith and install patches w/o knowing what they're supposed to fix. We need SOME level of detail.
If MS gave that out, then only idiots would have installed the "Critical Update" containing WGA
The patch is microcode (firmware for a CPU, so to speak) to help work around or fix some of the bugs that the Core 2 Duo has. Microcode can either be loaded in the BIOS or by the OS, IIRC it's loaded into volatile memory and has to be reloaded at every boot. The BIOS can load the microcode or the OS can. The BIOS is easier to the end users as the ucode will always be loaded without user intervention and is immune to CMOS clears and OS reinstalls as the BIOS is in non-volatile and usually ROM storage.
------------------------------Upcoming Overdue Build: Dual-socket workstation, ~32 GB DDR3, OS on a fast SSD, high-end GPU, all wrapped up in a huge tower case. Coming H2 2011.
Yes, I am actually still running the Pentium III 1.0B Coppermine in the picture.
Reply to MU_Engineer
My concern, from a performance perspective, is why do I need fixes in BOTH the BIOS and the OS? It makes more sense to me to patch it at the BIOS level only (I'm assuming this is more efficient because it's at a lower level in the system) instead of the OS level; and if I patch the BIOS, why do I want the overhead (though I'm not sure the amount of overhead) of also patching the OS? For a single bug fix it's probably not a huge deal, but if there are multiple fixes it could (theoretically) have an impact.
This brings me back to my point...If more information was supplied (by both MS and my PC Vendor, DELL) as to what was being patched, I could determine myself to only patch the BIOS and not worry about the MS OS patch.
Installing KB936357 on a P4 system caused problems. The system would reboot or give BSOD with various stop errors including 0x000000be, .....50, .....24, .....8e, ......21a
System was a Compaq Presario S5600UK fitted with Asus P4SD-LA mainboard and P4 3000 processor. Updating Bios to version 3.28 (latest available) had no effect.
My solution was to perform a repair re-install of windows and deselect this windows update using custom windows update. KB936357 is not relevent to non dual-core processors.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.