A KINDLY GEEK has produced a free tool to resurrect AMD machines borked by installing Service Pack 3 for Windows XP.
The fault affects mainly HP machines with an OEM splash screen and a number of Asus mobos, to which XP refuses to talk on the grounds that they're not fully ACPI compliant.
Jesper, over at msinfluentials, has a handy tool you can get your hands on for nothing which is said to fix the problem. Not having tried it ourselves, we cannot say for sure if it works or not, but if you've got a dead AMD system, whaddya got to lose?
Jesper warns against putting his tool in an Intel system, because it'll break it.
The INQ accepts no responsibility whatsoever for any damage, distress, embarrassing itching or hair loss caused by the use of Jesper's tool. µ
L'Inq
Jesper's
Blog
Tried buggeredthang & it told me this computer has fix in it for SP3 download already, ONE Problem: it won't start up, Wah, tears of pain.

Also Bios change is spoken of in article & This is both INTENTIONAL Bug from Microsoft in Buying original mainboards from Asus thru Third Party vendor in Ultimate Promo dept, those Mainboards chosen first 590, NOT Too good, then suddenly 690 chipsets ( they hoped to wait for 790 for moment year ago) Chosen Mainboards DO NOT have Upagradable BIOS. So Tough Luck, CCHHUUUMMMPPPPs!.& intentionally written into SP3 beta/RC& RTM as well as awaitied final release, NO Doubt Simply to Break XP On Those Machines Addected.

THOMAS STEWART von Microsoft ex parte President.....

Its Blooper to Most, yet if you got it, they got you.
Signed:TS drashek
The VBS script the guy wrote is a whole lot of code to change a simple registry key (HKLM\SYSTEM\CurrentControlSet\Services\IntelPPM\Start)
to the value of '4' to disable the IntelPPM service. This jives w/ the Micr0$ucks solution of deleting / renaming the IntelPPM.sys driver for the service so it cannot start.

Jim
Not being a programmer, I would never suspected a programmed fix to take so many lines of code.

I guess navigating to the single line in the registry as Microsoft instructed was just too simple. Wow, glad I lucked up on this article, now I too can impress my friends with a super sophisticated program to change a single character.

I'd comment further, but I have to go rent a mobile crane to take out my garbage. Wow, all these years I was just grabbing it and dropping it into the can. Now I understand the simple way is not the best way. Totally invalidates Ockham's Razor but hey, this is Windows.
I was reading half-way into that first comment!!

It's THE Drashek, a yet misunderstood phenomena that without startrek's universal translator makes no sense!!!

Please god, make Drashek infertile.
For machines affected with the windows virus, the answer to all your problems is here:

http://www.centos.org

You can tell if you are infected by the Windows virus by the following tests:

1)Your wallet is lighter than it should be.
2)Your computer is slow to respond, despite having immensly powerful hardware.
3)It crashes or reboots alot.
4)Incessantly requires updates
5)If you change even the smallest part of the hardware of your system, your computer may stop working.

or

6)It may request you call number to explain why you changed that part of your computer, so it can decide whether or not you are allowed to carry on running the windows virus. At this point it may attempt to get more money from you as well - you have been warned...
I had that particular problem and used Jesters script to fix the problem and it worked. Nice for those of us who do NOT like to get in the registry and mess around with something we know nothing about!
that this was a motherboard issue. I know you get that error if you do a windows repair on a system that has a ghost (or equivalent) image from an intel pc put on an amd system (hp are the worst offenders for this). You can use autoruns to delete the driver before doing the update.
If you play WOW with Intel and SP3. 
Get rid of SP3 and you will stop haveing crashes while playing.
Seems not only AMD cps but Intel cpus also have problems in certain games.
Uninstalled SP3 on a Intel machine and game WOW went back to normal no more crashes.
SP3 on your machine more trouble than its worth.