Ads by TechWords
Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 

Fixing the XP SP3 reboot blues

Rate this
Rated -11
395 Votes

What can I say? For me, XP SP3 was the cat's meow, the best Windows client operating system ever. But, for other people 'upgrading' to XP SP 3 is like being fed to a roaring lion.

They're seeing endless, and I mean endless-reboots. Many can't even escape to the relative safety of Windows' Safe mode much less get back to the safe harbor of a previously saved System Restore point. Most of the people experiencing this PC nightmare seem to be running computers with AMD chips.

The core problem though isn't that XP SP3 has a problem with AMD processors. It's that some vendors, and HP is the one that usually gets mentioned, used the same XP image on both their Intel and AMD systems. Usually that's not a problem. It's sloppy workmanship at the factory, but not a show-stopper. Well, until now anyway.

What happens on an AMD system is that when an Intel-only power driver-intelppm.sys--is loaded the newly patched PC throws a fit and locks you into reboot hell.

Well, actually it only seems like reboot hell. You can stop the madness by hitting the F8 key when you first see the black Windows XP screen. Then, on the character-based menu, select "Disable automatic restart on system failure." Chances are I didn't have to tell you that if you've been seeing the reboot cycle for a while. Then select Safe Mode. Once you're there, click on the System button, pick run and follow these instructions from Jesper Johansson, an ex-Microsoftie and now a Windows blogger,

1. Run regedit

2. Click on HKEY_LOCAL_MACHINE

3. From the File menu, select "Load hive"

4. Navigate to %systemdriver%\Windows\System32\Config on the dead system and select the file name System

5. Name it something you can remember, such as "horked"

6. Navigate to horked\ControlSet001\Services\IntelPPM

7. Double click the Start value and set it to 4

8. Repeat steps 6-7 for the other control sets.

9. Reboot

10. Send Johansson a thank you note if it works.

Johansson's blog also has advice on fixing other XP SP3 problems. If you're having trouble, be sure to visit it. Of course, what would be best is avoiding this entire mess in the first place. So, if your PC has an AMD CPU, you might consider following the steps above before applying SP3. Now, on my AMD PCs, I never ran into this problem, but if you want to be sure to avoid the reboot recycle, you may want to go ahead and fix your system before hand.

Just be sure not to remove the driver if you have an Intel-based PC. If you remove it then, you'll only give yourself an entirely different major problem. Johansson also gives instructions on how to get out of this mess.

There are other things you should do before installing XP SP3 that will help you avoid other possible upgrade woes. For example, you should turn off any start-up programs, especially anti-virus programs. If you're using the beta of Internet Explorer 8, ditch it. XP SP3 doesn't play with IE 8.

These steps may help, but I'm not as certain of them as I am of the earlier ones I'd mentioned. If you're already running a beta or release candidate of XP SP3, remove them before making the final upgrade. This personally gave me no trouble, but some people have reported trouble when they tried to do it.

Upgrading your drivers before the upgrade may help. Since I always run the latest drivers for my equipment, this wasn't an issue for me. In any case, it's usually a good idea to run the newest drivers to get the best and most secure performance from your equipment so you might as well update them as well so long as you're at it.

Last, but never least, whenever you do a major upgrade on any system, be sure to make a back-up. That way if everything falls apart at least you can restore your data and programs to another PC.

Good luck!

What People Are Saying

Rate this
Rated -3
165 Votes

Fixing the XP SP3 reboot blues

I took this opportunity to purchase and install Windows Vista Home Premium (SP1). This converted my HP boat anchor back into a working Media Center PC. On the plus side I got rid of all the HP crap-ware. I had no intention of moving to Vista but this problem convinced me. So far so good.

Rate this
Rated -4
338 Votes

HP's Fault (Again)

The endless-reboot problem is clearly *all* HP's fault, to the dismay of MS-bashers.

Before installing SP1 on my computer, I had to install HP-specific patches.

Before installing SP2 on my computer, I had to install more HP-specific patches.

If you have HP computers, it pays to be a late adaptor of Windows Service Packs.

That said, I love HP brand desktop computers.

Rate this
Rated -6
338 Votes

The Little Yellow Shield of DEATH!

This is a perfect example of why I always groan "oh no" when the little yellow shield from Microsoft shows up in my icon tray, telling me it wants to install something.

Since I'm running an HP-AMD machine, I'm sure glad I decided to wait to see if other people were having problems before installing XP3 when the little shield showed up last week.

Isn't it great working for free for Microsoft's quality assurance department?

Rate this
Rated -5
359 Votes

A simpler fix

Steve,

There's another reg fix for the
0x0000007E stop error that's actually a bit simpler. And better, I applied it on my Cpq PC before loading SP3, and had no reboot loop (I'd already loaded SP3, got into bootloop hell, and uninstalled SP3 from Safe Mode, then researched the issue, so I already knew my machine was susceptible). It will, of course, work after the fact in safe mode, too.

In regedit, navigate to HKLM\SYSTEM\CurrentControlSet\Services\intelppm
Double-click the "Start" keyword and change the value from "1" to "4" (or 0x00000004).

Install SP3 (if you haven't) or reboot from safe mode (if you have), and your computer will be happy.

It goes without saying that this key should only be changed on an AMD system (though I'm not sure what the effect would be if it were changed on an Intel based system), and if the intelppm folder isn't in the registry, it won't be a problem.

Rate this
Rated -4
80 Votes

re: a simpler fix

Wayne,

Your instructions were simple & easy to follow & allowed the less technical ones of us to fix the problem. I looked at several sets of fix instructions but yours were the only ones I could make sense of.

Thanks a million.
Problem solved in 5 minutes much to my surprise.

Rate this
Rated +9
279 Votes

Awesome! Your solution had

Awesome! Your solution had my reboot issue fixed within five minutes. Thanks!

Rate this
Rated +4
328 Votes

I'm pleased

Steve,

Good, impartial reporting. I know you're a linux geek (me too) and I appreciate the fact that you're still able to level with the M$ crowd. I'm sure that the M$ minions will cry, but you're right in what you're saying.

Personally, I think SP3 is an attempt to create a more "Vista-like" environment that will make the transition to Vista either less painful or more necessary. I haven't figured out which yet. All of the Vista-like add-ons that have been available seem to indicate the former. I'm waiting to see how SP3 performs in intermediate term. Considering that the IE7 issue is resolvable by pre-emption I suppose that it should be usable. Time will tell.

Rate this
Rated -12
334 Votes

XP

Steve,
As far as M$ goes I thought Win 2000 was the best of breed. It runs pretty much all of the Win 32 stuff but doesn't have the bloat or DRM crapware found in Windows XP\Vista.
I play with XP Pro & 2000 in a VirtualBox VM and 2000 is consistently faster booting & running Win 32 apps. The system footprint of Win2000 is also much smaller then XP by a large margin.
These days I only keep M$ safely contained in a VM so I can boot it up and see how it compares to my best friend, Tux.

Rate this
Rated +12
390 Votes

Happened to me on a Dell.

Happened to me on a Dell. I tried "Disable automatic restart on system failure." but that resulted in a BSOD. Ended up doing a repair using a bootable SP1a CD and then did the individual critical updates, bypassing SP3 this time.