There have been many reports (Google AMD XP "serice pack 3" or visit Microsofts support forum) of problems primarily with AMD based computers after installing XP SP3.  Tom's Hardware http://www.tomshardware.com/news/Windows-XP-SP3,5334.html was the first report of this we found, but Computerworld http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9084418 also posted an article the same day.


 

Yesterday the following was published on Microsft TechNet:

"Today we are happy to announce that Windows XP Service Pack 3 (SP3) has released to manufacturing (RTM). Windows XP SP3 bits are now working their way through our manufacturing channels to be available to OEM and Enterprise customers. [more]

We are also in the final stages of preparing for release to the web (i.e. you!) on April 29th, via Windows Update and the Microsoft Download Center. Online documentation for Windows XP SP3, such as Microsoft Knowledge Base articles and the Microsoft TechNet Windows XP TechCenter, will be updated then. For customers who use Windows XP at home, Windows XP SP3 Automatic Update distribution for users at home will begin in early summer. 

Thanks to everyone here who installed the public betas – you not only gave us detailed feedback but also helped each other out with timely troubleshooting. Through the beta program we found several important issues and were able to confirm some essential fixes. We couldn’t have done this without you.

We will still be monitoring this forum during the next few weeks in case you have more feedback about the release of Windows XP SP3.

On behalf of myself, Shashank Bansal and Windows Serviceability, many thanks.

Chris Keroack
Release Manager, Windows XP Service Pack 3
Windows Serviceability"

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3214173&SiteID=17

http://www.microsoft.com/downloads/details.aspx?FamilyID=68c48dad-bc34-40be-8d85-6bb4f56f5110&displaylang=en

UPDATE: This morning Microsoft released XP SP3 to the public and then delayed it because of a compatibility problem with their Dynamics software products.  I didn't see a posting on Microsoft's site, but I did see this article: http://www.crn.com/software/207403064