Depending on the chipset, motherboard manufacturer, BIOS version, and CPU, installing Microsoft Windows XP Service Pack 2 can result in an unbootable computer system.
The problem is generally associated with Intel "Prescott" CPUs and its chipsets, but not every such combination will cause a problem. As of this writing, motherboards exhibiting the behavior include:
- Albatron PX865 PE Pro
- Shuttle SB61G2
- Jetway i875P
- Soyo P4I865P
- Aopen AX4SG Max
- Asus P4P800-E deluxe
- Abit IS7-V
- Foxconn 865A01-G-6EKRS
Technically speaking, the problem revolves around the machine's BIOS not installing a production level microcode update. To check whether the BIOS is at the correct level, download the Intel Processor Frequency ID utility. The microcode version is identified by this utility as CPU Revision, which should equal at least 8.
Solution 1
If the Intel utility shows that you have the wrong microcode
version, the primary solution to the problem is to update the system BIOS for
your motherboard before you install SP2. Here are some motherboard manufacturer
links:
BIOS updates
BIOS updates can be dangerous -- please follow the manufacturer's instructions very closely to avoid a major catastrophe.
Solution 2
If you have already installed XP SP2 and have a PC that will not boot because of this microcode version problem, there are two workarounds you can try to get to a bootable state.
In the BIOS setup you should temporarily disable the L1 and L2 cache. On some motherboards, this will allow the computer to boot. You should then remove SP2, turn the L1 and L2 cache back on, and then update the BIOS to reflect the correct microcode version. After completing these steps, you should be able to re-install SP2 without running into this particular problem again.
If disabling L1 and L2 cache does not work, you can use a second workaround suggested by a representative at Intel: Boot the problem computer with an alternative OS or to the safe mode command line if possible. Assuming you can get to the Windows directory on the boot partition, navigate to this file and change its name so that it does not load the next time the machine is booted:
windows\system32\drivers\update.sys
After rebooting you should be able to install XP SP2, but keep in mind this is a temporary fix -- the system will be unstable until you update the BIOS and reactivate the update.sys file.
TechRepublic is the online community
and information resource for all IT professionals, from support staff to executives. We offer in-depth technical articles
written for IT professionals by IT professionals. In addition to articles on everything from Windows to e-mail to firewalls,
we offer IT industry analysis, downloads, management tips, discussion forums, and
e-newsletters.
©2004 TechRepublic, Inc.
4%
4%
Genuine Intel D865GLC motherboard afflicted also.
You would think that Intel would have tested all their motherboards with XP SP2 for problems, seeing they are often so chummy with Microsoft.
Customer had this problem today. Unfortunately they found out after XP2 proceeded to install itself on the system, and it rebooted continually.
Fortunately, we were able to get to safe mode, and the command line.
Reminds me of the CIH virus that zapped the CMOS a few years ago, resulting in a dead motherboard. The solution there was to replace the motherboard and install anti-virus protection. The customers payed for that one.
Who pays for the time I wasted fixing the oversight? Microsoft, or Intel?
A pretty poor show for two industry leaders.