Windows XP Service Pack 3 and HP AMD systems
Filed under: BSOD, Hewlett Packard, Windows XP
Comments: None
If an HP computer has an AMD processor do not run SP3 without running the script below first, otherwise it will BSOD on restart.
To fix the problem, boot into safe mode, or boot to a WinPE disk, or into the recovery console, and disable the intelppm.sys driver.
WARNING: Do NOT under any circumstance disable the intelppm driver on an Intel-based computer. It will make your computer not boot! If your computer will not boot because you disabled the intelppm driver on an Intel-based computer, follow the directions in the Recovery Console section below.
If you have an AMD-based computer, however, you do not need the intelppm driver and can disable it. Boot into Safe Mode by hitting the F8 key as above, but select Safe Mode instead. You will need your Administrator account to log on in safe mode. To disable the driver, take the following steps:
If you booted into the recovery console, from a command prompt, run “disable intelppm”
If you booted into safe mode you can run “sc config intelppm start= disabled”
If you booted into WinPE, you have to manually edit the registry. Do this:
-
Run regedit
-
Click on HKEY_LOCAL_MACHINE
-
From the File menu, select “Load hive”
-
Navigate to %systemdriver%\Windows\System32\Config on the dead system and select the file name System
-
Name it something you can remember, such as “horked”
-
Navigate to horked\<the current control set>\Services\IntelPPM. See below for how to determine which one is the current control set.
-
Double click the Start value and set it to 4
-
If you did what I did and completely destroyed things by running a disk check, navigate to <the current control set>\Control\SessionManager. Open the BootExecute value and clear out the autochk entries
-
Reboot
Step 6 asks you to navigate to <the current control set>. Under HKEY_LOCAL_MACHINE\SYSTEM there are typically at least two numbered control sets, and sometimes there are up to four. They are called ControlSet001, ControlSet002, and so on. Control sets hold all the configuration data for the computer, including all drivers that load. One of them is designated the current one, and the others are backups of previous configurations that worked. The control set that is currently used as the current one is the one listed in the “Current” value under HKEY_LOCAL_MACHINE\SYSTEM\Select. That is the control set that you need to modify in step 6. If you modify one of the other control sets it will not solve the problem. You need to modify the current one. If you manage to boot the computer, CurrentControlSet will be a pointer to the current one and you can modify that one. If you boot from the recovery disk you have to figure out which one is the current to modify the proper one. It will not always be ControlSet001.
If this was your problem, the computer should now reboot just fine.