Blame game: Microsoft and AMD say the XP SP3 rebooting issue is everyone’s fault but their own
- May 13th, 2008
- 4 Comments
All the craziness going on with XP’s SP3 and AMD processors is complex, but Microsoft wants you to know it’s not their fault, it’s HP’s fault, among others.
It turns out that the OEMs, including HP, have been installing the wrong sysprep before XP, using an sysprep designed for Intel’s platform. So it’s not a Microsoft issue, or an AMD issue, it’s a configuration issue.
There’s no patch yet, though Microsoft is working on the problem. We’ll let you know when there’s a fix.
Sung (Who am I?)
3 months ago
My parents have a Compaq computer with AMD Sempron I updated with SP3 but had the rebooting issue. The Compaq is about 3 maybe 4 years old. Isn’t that before HP bought or merged with Compaq?
Jonas (Who am I?)
3 months ago
Had the same Issue with my athlon Xp2000 on a K7S5A Board. But on the Bluescreen were one file mentioned: gdi32.dll
Copying the right one from the servicepack folder into system32 through the rescue console put everything right in place. Could have been caused by the installed BricoPack, apart from that it was a vanilla xp install from msdnaa, did not have any manufacture-brand one it…
diamond david lee (Who am I?)
3 months ago
Any fix on this yet? Windows really wants me to update. It’s giving me the yellow shield icon w/ an exclamation point in the notification area. I tried the SP3 update the day it came out and I had to reboot in safe mode and uninstall it. I’ve got an HP desktop w/ an Athlon X2 3800
Buzz123 (Who am I?)
3 months ago
HP fix: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-60484-1&cc=us&lc=en&dlc=en&product=390426
MS fix: http://support.microsoft.com/default.aspx/kb/888372/en-us
HP used an Intel image to load up AMD boxes (against the rules) and shot themselves (and customers) in the foot in the process…
Simple registry fix (either beofre or after the fact) fixes the issue!
Reply