AMD and HP reportedly responsible for XP SP3 glitches

by Stevie Smith - May 13 2008, 12:34

A host of related system glitches following last week’s reopening of public availability for Windows XP service pack 3 (SP3) didn’t exactly amount to the stress-free download experience that Microsoft Corp. was perhaps hoping for.

AMD and HP in the firing line for latest XP SP3 compatibility errors? Image: AMD/HP.

More pointedly, Microsoft’s online message board was subsequently hit with a wave of complaints soon after SP3 was reopened, with many disgruntled XP users highlighting computer crashes, system freezes and endless reboot cycles after installing the operating system’s final major update.While Redmond-based Microsoft is busy trying to ‘officially’ isolate the specific cause of this latest round of incompatibility glitches (Dynamics RMS was responsible for SP3’s prior download delay), it would appear that computer manufacturer Hewlett-Packard and chipmaker AMD are in the crosshairs when it comes to assigning blame.Specifically, a Microsoft customer service representative yesterday told ChannelWeb that installation problems related to SP3 seem to be rearing up solely on desktop computers produced by Hewlett-Packard. “I checked with the resources I have and it seems that we have not had any issues with any manufacturer other than HP,” the service representative wrote during an online chat with ChannelWeb regarding the most likely source of the SP3 reboot problem. That being said, Jesper Johansson, a former senior security strategist with Microsoft, has chipped in on the debate by revealing in a blog post that the recent spate of SP3 installation problems are also linked with certain desktop computers running on AMD processors.Beyond those two current targets, CRN reports that Microsoft has been aware of the SP3 installation errors since May 06 of this year, and has even published a related Knowledge Base article that includes a workaround for the problems. The Microsoft article outlines that system crashes and reboot problems have reared up from an orphaned registry key that is present on non-Intel (namely AMD) computers receiving an SP1 image created through an Intel-based system.“Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load,” which leads to reboot glitches, outlines the software giant. According to Johansson’s post on the problems, affected computers either fail to boot or crash completely with a STOP error code (0x0000007e); although safe mode booting will work as the problem drivers are not enabled there. Modifying the registry while in safe mode and removing the Intelppm.sys driver is Microsoft’s recommended workaround.“Microsoft is aware of a reboot issue experienced by some users who have attempted to install Windows XP SP3,“ a Microsoft spokesperson relayed to ChannelWeb following the rush of installation complaints. “While the root cause of this issue is complex, it results from OEMs improperly placing a Windows XP image created for an for Intel-based computer onto machines with non-Intel chipsets.”In terms of nailing down specific OEM (original equipment manufacturer) computers affected by the new SP3 incompatibility problems, Microsoft is refusing to spotlight a specific company, choosing instead to offer that the glitch is causing problems for “OEMs in general.”

Comment on this Story

Interested in a more interactive TTH? Join our Facebook Group
Want regular updates from The Tech Herald? Follow us on Twitter

Comment on this Story

Note our older Talkback system is still running below. We hope to import existing comments into the new system shortly. Guest posting is still allowed, however, you can now login with any number of social network accounts.

Talkback

Add your comment (no registration required)

page: 1

JBWMay 13th, 2008 - 22:39:12

So, if Microsoft knew about the problem, why didn't they stop SP3 until the AMD problems are resolved. AMD should sue for damages. Somebody should start a class action against Microsoft for knowingly rendering all HP AMD systems unusable.

Report this comment

JBWMay 13th, 2008 - 22:40:36

There is a registry update to intelppm that you can use, and set it to 4, but this is what worked for my HP AMD X2 desktop:
Most of the problems are that HP and others supplied the intelppm.sys module on AMD systems. DO NOT RENAME INTELPPM.SYS NOR ISSUE THE COMMAND IF YOU ARE AN INTEL SYSTEM - IT WILL PREVENT BOOTING, AND YOU MIGHT NOT EVEN BE ABLE TO GET INTO SAFE MODE. AMD USERS: One fix is to come up in safe mode and rename intelppm.sys. The fix I USED is to come up in safe mode with command prompt and issue EXACTLY this (with spaces where I put them):
sc config intelppm start= disabled
You should get a completed message.
This cured my AMD X2 HP media center. I read about this on some blogs, etc. Also, if you have a certain high ASUS board, then they say to plug a USB 'thumb drive', etc., into a usb port. This might get you to safe mode, I don't know. This is also an AMD issue, or as the story goes. As I said, the command above fixed my HP AMD system by stopping the Intel power management. I have powered off and on several times, and I am stable on XP SP3 now. P.S. If you install SP3, I have seen where it INSTALLS THE IE7 BROWSER, and you must remove SP3 to go back to IE6.

----------------------------------------------------------------------- ---------

Report this comment

max payneMay 14th, 2008 - 01:18:13

3 days with xp sp3 and my computer is a complete mess. it takes 4 min to open a word or excel document
nothing seems to work anymore
i saved my files and will reinstall xp with no sp3

stay away or have fun!

Report this comment

henk jaminMay 22nd, 2008 - 19:23:24

I have an ASUS M3A based AMD Phenom 9750 box that ran like molasses in the middle of winter after Windows Update installed sp3 on XP Prof... So this does not appear to be a purely HP isuue at all!.
I did an image restore, and all ran as before! Guess who turned off Windows Update?

Report this comment

jwsMay 29th, 2008 - 04:31:54

Both microsoft and HP should jointly be sued in a class action suit for damages and lost value. I have not installed SP3, but this reckless joint action has lowered the value of my pavilion HP.

Report this comment

rxsSep 27th, 2008 - 00:52:07

running
'sc config intelppm start= disabled'
fixed the problem on my Compaq Presario (AMD)

thanks, JBW

Report this comment

P. MooneyOct 9th, 2008 - 19:57:18

All I have to say is that a class action suit is available I will gladly sign it and get others to sign. I am not computer savvy and it ended up costing me $155 just to be able to get my computer to work again. You would think the company would at least make some restitution HA HA

Report this comment

page: 1

Add your comment (no registration required)

Software

AMD and HP reportedly responsible for XP SP3 glitches

Comment on this Story

Talkback

Latest

Latest Articles on Monsters&Critics

In The Tech Herald

Site

The Fine Print