Blame game: Microsoft and AMD say the XP SP3 rebooting issue is everyone's fault but their own

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.

[PR0F3TA]

hahaha ohh Microsoft... when will you build a better working OS lol

XP was perfect and then you went and copied OSX. Thats why i went with the latter

[Bladestar]

ohh why anti-microsoft developed the ability to learn how to read...

let me guess... HP install a driver/software from a different hardware and manufacturer.. this cause the OS to not work properly... and it's Microsoft's fault?... strange... I am pretty sure if you try to install windows driver for a MAC or linux... the OS may not be too happy... but nevermind ... probably have no Idea what I am talking about... if that's really you in the picture... I wouldn't blame you... I blame your parents.

[PR0F3TA]

your 100% right... WTF is a driver, is it that plug n play?

my Digital Cam, PSP, HDD, KeyBoards and Controllers didn't need a driver, they just worked.

[jaja1434]

^^^ I have no idea if you're be ironic or just stupid. *boggle*

[v1c1ous]

deja vu?

[CRIMS0N_W0LF]

i have nothing from hp and my pc randomly crashes since i installed SP3

[Bladestar]

what?... HP does not make a specific hardware component in question.. so you will not find a CPU or hard drive made by HP... you may want to check the hardware you PC has and ensure that it has the proper drivers...

[CRIMS0N_W0LF]

don't tell me how to use a pc i have a diploma in computing.

What i meant is I have not even 1 driver from HP because I have ZERO HP products

[Skynetone]

cant they just check your configuration before installing sp3

[player911]

The problem was that HP installed a version of Windows that had Intel chipset drivers installed running an AMD chipset. They ran into the exact same problems with SP2... and now SP3. So basically:

HP is the original person to blame for screwing up the installs and instead of fixing it, they just covered it up with AMD drivers.

Microsoft is the one to blame now since it was a known problem and should have checked to see if conflicting hardware exists, patch drivers, and install the update.

AMD, Intel, or any other 3rd party isn't responsible. The fixes are out there, Microsoft just didn't include the fix nor checked to see if anyone would be affected.

But regardless, things happen. That is one of the downfalls of owning a PC (vs a MAC, etc) is that Microsoft has to write software to accommodate EVERY hardware configuration. In a perfect world things would work out, but it's not, thus some have issues. You can't expect a service patch to be released without it having some issues. That's why corporations are never bleeding edge; they wait for the bugs to get worked out.

Anyone to jump the gun and be the first to download a pack of updates without having the know-how to fix any problems that may arise are idiots anyway.