Sport & Auto
- About Future
- Digital Future
- Cookies Policy
- Terms & Conditions
- Investor Relations
- Contact Future
If you've been a victim of the AMD-based HP and Compaq BSOD-reboot loop after installing Windows XP SP3 or you've been waiting for a solution, take your choice. Real solutions include:
Microsoft's current "answer" falls into the Not-so-Good category:
HP and Microsoft's approaches bring us to the following questions: Does HP talk to Microsoft? Does Microsoft talk to HP?
Microsoft frequently is slammed by computer users for a multitude of sins, but this time, it's clearly not Microsoft's fault.
Way back when Windows XP SP2 was being rolled out, OEM vendors had used the same corner-cutting method of using a common image for earlier generations of AMD and Intel-based systems, and the same BSOD-reboot loop happened. Microsoft's KB888372 discussed why this happened with SP2, and unfortunately required only minor editing to bring it up to date for the SP3 problem.
So, history repeated itself with the rollout of Windows XP SP3. How can we keep this problem from happening again?
Part of the solution already exists: Windows Vista, unlike Windows XP, handles differences in hardware better, so you can prepare a common image that can be deployed to different systems. However, Windows XP still has a long way to go before it joins Windows 98 in the grooveyard of forgotten operating system favorites. What should vendors - and users - do now?