It's my understanding that despite being warned by MS, HP used the same image for AMD systems as they had created for Intel systems. VERY stupid on HP's behalf. They earned the malfunction honestly (or dishonestly) and were kind enough to pass it on to their customers. I'm really surprised this has not reared it's ugly head before now.
I'm unconvinced by this logic that it's HP's doing for the following reason:
MS writes the code that installs SP3. As I understand it, the problem occurs because this service pack installs an Intel chip driver and replaces my AMD chip driver. This causes the BSOD and looped booting.
I have numerous software apps that have no problem indentifying I'm running an HP computer with an AMD chipset. If these apps can easily do this so can MS. Therefore, MS has absolutely no business force installing an Intel chip driver on my AMD machine and thereby rendering it useless.
As you can tell Phoon, in my mind, the primary fault for this is MS.