BSODing after updating to SP2

[R-H]

Hi everyone!

After updating a computer to SP2, it's been BSODing right after the XP loading screen. The only way to boot XP up is through Safe Mode. I remember this having happened awhile ago, the first time I tried updating to SP2, but I don't remember what I did then to repair the install.

I did some googling about this problem, and apparently it happens because the SP1 Sysprep image was prepared on an Intel machine and when the SP2 Sysprep image is applied it will try to load the Intel processor driver (Intelppm.sys).

I found two solutions (I hope) to the problem

1)REG ADD HKLM\SYSTEM\ControlSet001\Services\Intelppm" /V Start /T REG_DWORD /D 4 /F

JSIFaq

2)same as the one above, but ControlSet000, "so it changed the current controlset rather than a backup one"

RunPCRun Fix

Which of the two should I use? What exactly do I type in when I go to edit the registry (exactly what link 1 says? REG ADD... /F)

Any help would be much appreciated

Thanks

Edit: Forgot to include the error code

STOP: 0x0000007E (0xC0000005, 0xF6A33750, 0xF795F430, 0xF795F12C)

The computer was bought from a vendor (Seanix) and was upgraded 2 years ago from S754 to S939.

Edited December 24, 2007 by R-H

[nitroshift]

Just my 2 cents... Since you are talking about socket 754 and 939, what is an Intel driver doing in your system? Socket 754 and 939 are AMD...

[R-H]

Just my 2 cents... Since you are talking about socket 754 and 939, what is an Intel driver doing in your system? Socket 754 and 939 are AMD...

Not a clue. According to MS, the problem occurs if the Sysprep SP1 image was created on an Intel machine, and you update it to SP2 on an AMD machine.

[R-H]

I just decided to uninstall SP2. Is a slow uninstall normal?

Thanks

[R-H]

It's not just slow, it hangs. No progress past "Inspecting Current Configuration". I tried uninstalling through the Control Panel and from c:\windows\...

I have no idea what to do now.

Thanks

[RJARRRPCGP]

Hi everyone!

After updating a computer to SP2, it's been BSODing right after the XP loading screen. The only way to boot XP up is through Safe Mode. I remember this having happened awhile ago, the first time I tried updating to SP2, but I don't remember what I did then to repair the install.

I did some googling about this problem, and apparently it happens because the SP1 Sysprep image was prepared on an Intel machine and when the SP2 Sysprep image is applied it will try to load the Intel processor driver (Intelppm.sys).

I found two solutions (I hope) to the problem

1)REG ADD HKLM\SYSTEM\ControlSet001\Services\Intelppm" /V Start /T REG_DWORD /D 4 /F

JSIFaq

2)same as the one above, but ControlSet000, "so it changed the current controlset rather than a backup one"

RunPCRun Fix

Which of the two should I use? What exactly do I type in when I go to edit the registry (exactly what link 1 says? REG ADD... /F)

Any help would be much appreciated

Thanks

Edit: Forgot to include the error code

STOP: 0x0000007E (0xC0000005, 0xF6A33750, 0xF795F430, 0xF795F12C)

The computer was bought from a vendor (Seanix) and was upgraded 2 years ago from S754 to S939.

Known problem, except for the stop error code.

On some copies of Windows XP, after you install SP2 and after the SP2 installer restarts Windows to complete the SP2 installation, Windows XP then reboots instead of giving me the configuration screen for automatic updates.

This may be a hard disk drive and southbridge combination issue. Saw this with my MSI 845E Max (Intel 82801DB southbridge) when using a Samsung SpinPoint 80 GB, model SP0802N.

It is a strange issue, because the MSI 845E Max is 100 percent compatible with Windows XP.

Edited December 24, 2007 by RJARRRPCGP