Fix For Restart Bug In Windows XP SP3
If you’re an AMD processor users, you must have been greeted by the Blue Screen of Death, after installing Windows XP SP3 on rebooting their computer. The error begins with something like this: STOP: 0×0000007E (0xC0000005 and contains the error text SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. And after this, the computers reboots again and keeps repeating this.
Windows XP SP3 apparently copies an Intel power management driver to the computer that was not there before the installation of SP3 and that is said to be the cause for the restart bug. But thanks to HP, a fix has been given for this bug.
The following fix can only be used if you use a non-Intel processor and encounter the restart bug after installing Windows XP Service Pack 3. Below are the fixes given by HP and Microsoft:
Remember: Make sure you make a quick backup of your system using System Restore. And also backup your Registry entries.
HP’s Fix For XP SP3 Restart Bug:
- Boot Computer in Safe Mode
- Use Windows Explorer to browse to C:\Windows\System32\Drivers
- Right-click intelppm.sys and rename it to XXXintelppm.syx
- Restart Windows
If the computer is unable to boot into safe mode do the following:
- Press F8 during startup and load the Microsoft Windows Recovery Console
- Type the number that corresponds to your Windows installation
- Log in as an administrator
- Type cd c:\windows\system32\drivers at the command prompt
- Type rename intelppm.sys XXXintelppm.syx
- Restart Windows
Microsoft’s Fix For XP SP3 Restart Bug:
- Boot the Computer into Safe Mode
- Press Windows R, type regedit, hit enter
- Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Intelppm
- right-click the Start entry in the right pane and select modify
- Enter 4 in the Value Data box
- Close regedit, restart the computer.
I hope this fixes your restart problem in Windows XP after installing to SP3.
[Via gHacks]
Author: Haris NadeemHe is the founder of Sizzled Core and a Pakistani blogger who loves gadgets and exploring out the web!


7 Comments
Blogs DNA
Great Haris perfect time for this post. This is going to be popular post for this week. i was pretty lucky not to install SP3 coz of my laziness (mine is AMD sempron processer) and got saved by this ridiculous bug
May 19th, 2008
Panther
Thanks, this will definitely come in handy when upgrading my HP/AMD machine. Kudos!
May 20th, 2008
IP
I haven’t installed sp3 on my amd64 yet… i did on an intel laptop and worked fine. I wonder why HP solution is to rename the file that way… why not erase it?
Also, if this blue screen appears to any amd processor user (like me) as you stated before… does this mean microsoft hasn’t tested sp3 on an amd processor? :s Maybe they were too busy trying to make Windows Vista a decent OS.
May 20th, 2008
Haris
@IP:
I have no idea whether Microsoft tested SP3 on AMDs or not, but as far as I remember, the public beta that was released first, didn’t had this bug. It’s only in the final release. Don’t know what Microsoft is being up to.
May 20th, 2008
Leave a Reply