GamersCrib
05-15-2008, 08:10 PM
Hewlett-Packard is working to fix the problems that were caused when customers attempted to download Microsoft’s XP Service Patch 3 onto desktops that were based on Advanced Micro Devices processors.
The reboot problems with certain HP desktops and SP3 began appearing after Microsoft posted the patch on its Web site earlier this month. The issues have been discussed in detail, especially on blogs such as the one maintained by Jesper Johansson, a former Microsoft employee, who noticed the problem and has been issuing a series of solutions for the reboot problem since May 8.
On its Web site, HP (http://www.hp.com/cgi-bin/hpsupport/index.pl) is offering support for those trying to fix the rebooting problems and also an article on how to recover from the error. (http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c01457284&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN)
“This is not an AMD or Microsoft issue,” wrote Graves. “It’s an issue of matching the correct software image with the correct hardware. I talked to our software engineers and it seems the real culprit is a driver called intelppm.sys. By the name, you can probably tell that this is an Intel driver... and it causes issues with AMD-based systems.”
http://www.eweek.com/c/a/Desktops-and-Notebooks/HP-Fixing-XP-SP3-Problems/
The reboot problems with certain HP desktops and SP3 began appearing after Microsoft posted the patch on its Web site earlier this month. The issues have been discussed in detail, especially on blogs such as the one maintained by Jesper Johansson, a former Microsoft employee, who noticed the problem and has been issuing a series of solutions for the reboot problem since May 8.
On its Web site, HP (http://www.hp.com/cgi-bin/hpsupport/index.pl) is offering support for those trying to fix the rebooting problems and also an article on how to recover from the error. (http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c01457284&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN)
“This is not an AMD or Microsoft issue,” wrote Graves. “It’s an issue of matching the correct software image with the correct hardware. I talked to our software engineers and it seems the real culprit is a driver called intelppm.sys. By the name, you can probably tell that this is an Intel driver... and it causes issues with AMD-based systems.”
http://www.eweek.com/c/a/Desktops-and-Notebooks/HP-Fixing-XP-SP3-Problems/