KB971486 BSOD when booting

After running windows update yesterday I've been unable to reboot and get the
BSOD(0x0000007E) in normal and last good configuration or a kinder, gentler
empty pale blue screen that hangs when booting in safe mode.

Using a Dell Latitude D630 with XPhome SP2. Never run into a problem with
the windows updates before although I do them regularly.

Needed to boot from CD and use recovery console to uninstall the patches.
Removing KB971486 (and KB969947) fixed the problem. Not sure which one
actually caused the problem as there wasn't much information on the BSOD.
Internet searches point more toward KB971486, though.

Is a file named INTELPMM.SYS found on your computer?

How come you're just getting around to installing updates released on 13
Oct-09 and 10 Nov-09? Is Automatic Updates disabled?

Why hasn't SP3 been installed yet? Time's running out: Computers running
WinXP SP2 will NOT be offered any further critical security updates,
Automatic Updates will cease to function, and Windows Update website will
not be available after 12 April 2010 until SP3 is installed.

See the "How to obtain help" section of
http://support.microsoft.com/kb/971486

For home users, no-charge support is available by calling 1-866-PCSAFETY
and/or 1-866-234-6020 in the United States and in Canada or by contacting
your local Microsoft subsidiary. There is no-charge for support calls that
are associated with security updates. When you call, clearly state that
your problem is related to a Security Update and cite the update's KB number
(e.g., KB971486).

Or you can...

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Consumer Security Support home page
https://consumersecuritysupport.microsoft.com/

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002



jcrick wrote:
> After running windows update yesterday I've been unable to reboot and get
> the BSOD(0x0000007E) in normal and last good configuration or a kinder,
> gentler empty pale blue screen that hangs when booting in safe mode.
>
> Using a Dell Latitude D630 with XPhome SP2. Never run into a problem with
> the windows updates before although I do them regularly.
>
> Needed to boot from CD and use recovery console to uninstall the patches.
> Removing KB971486 (and KB969947) fixed the problem. Not sure which one
> actually caused the problem as there wasn't much information on the BSOD.
> Internet searches point more toward KB971486, though.

"jcrick" <> schrieb:

> After running windows update yesterday I've been unable to reboot and get the
> BSOD(0x0000007E) in normal and last good configuration or a kinder, gentler
> empty pale blue screen that hangs when booting in safe mode.
>
> Using a Dell Latitude D630 with XPhome SP2. Never run into a problem with
> the windows updates before although I do them regularly.

Whyever you don't have SP3 for Windows XP installed already, may I ask you,
if you've tried downloading KB971486 manually via DownloadCenter
http://www.microsoft.com/downloads/d...d-6709e8426068
already, saved the WindowsXP-KB971486-x86-ENU.exe and ran it with parameter
"/o" or "/overwriteOEM"?

Let's say, you've downloaded the WindowsXP-KB971486-x86-ENU.exe into
a folder "C:\Downloads", you'll have to type
"C:\Downloads\WindowsXP-KB971486-x86-ENU.exe" /o
*including* all quotes and spaces into Run in the Startmenu and execute
it from there by hitting [Enter] or clicking on OK.

In case that doesn't resolve the issue you ran into, would you mind sharing
which applications are running in the background after Windows has started?
Start -> Run -> msconfig [Enter/OK] -> System Start

Bye,
Freudi

there is no intelpmm.sys under my windows folder. I did not search the entire
machine.

Automatic updates are enabled. I run windows update all the time which is
how I got this. I have no control over when updates get offered to me.

thanks for the information.

"PA Bear [MS MVP]" wrote:

> Is a file named INTELPMM.SYS found on your computer?
>
> How come you're just getting around to installing updates released on 13
> Oct-09 and 10 Nov-09? Is Automatic Updates disabled?
>
> Why hasn't SP3 been installed yet? Time's running out: Computers running
> WinXP SP2 will NOT be offered any further critical security updates,
> Automatic Updates will cease to function, and Windows Update website will
> not be available after 12 April 2010 until SP3 is installed.
>
> See the "How to obtain help" section of
> http://support.microsoft.com/kb/971486
>
> For home users, no-charge support is available by calling 1-866-PCSAFETY
> and/or 1-866-234-6020 in the United States and in Canada or by contacting
> your local Microsoft subsidiary. There is no-charge for support calls that
> are associated with security updates. When you call, clearly state that
> your problem is related to a Security Update and cite the update's KB number
> (e.g., KB971486).
>
> Or you can...
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
>
> Consumer Security Support home page
> https://consumersecuritysupport.microsoft.com/
>
> For more information about how to contact your local Microsoft subsidiary
> for security update support issues, visit the International Support Web
> site: http://support.microsoft.com/common/international.aspx
>
> For enterprise customers, support for security updates is available through
> your usual support contacts.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Client - since 2002
>
>
>
> jcrick wrote:
> > After running windows update yesterday I've been unable to reboot and get
> > the BSOD(0x0000007E) in normal and last good configuration or a kinder,
> > gentler empty pale blue screen that hangs when booting in safe mode.
> >
> > Using a Dell Latitude D630 with XPhome SP2. Never run into a problem with
> > the windows updates before although I do them regularly.
> >
> > Needed to boot from CD and use recovery console to uninstall the patches.
> > Removing KB971486 (and KB969947) fixed the problem. Not sure which one
> > actually caused the problem as there wasn't much information on the BSOD.
> > Internet searches point more toward KB971486, though.
>
> .
>

Repost:

> See the "How to obtain help" section of
> http://support.microsoft.com/kb/971486
>
> For home users, no-charge support is available by calling 1-866-PCSAFETY
> and/or 1-866-234-6020 in the United States and in Canada or by contacting
> your local Microsoft subsidiary. There is no-charge for support calls
> that
> are associated with security updates. When you call, clearly state that
> your problem is related to a Security Update and cite the update's KB
> number
> (e.g., KB971486).
>
> Or you can...
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
>
> Consumer Security Support home page
> https://consumersecuritysupport.microsoft.com/
>
> For more information about how to contact your local Microsoft subsidiary
> for security update support issues, visit the International Support Web
> site: http://support.microsoft.com/common/international.aspx
>
> For enterprise customers, support for security updates is available
> through
> your usual support contacts.


jcrick wrote:
> there is no intelpmm.sys under my windows folder. I did not search the
> entire machine.
>
> Automatic updates are enabled. I run windows update all the time which is
> how I got this. I have no control over when updates get offered to me.
>
> thanks for the information.
>
> "PA Bear [MS MVP]" wrote:
>
>> Is a file named INTELPMM.SYS found on your computer?
>>
>> How come you're just getting around to installing updates released on 13
>> Oct-09 and 10 Nov-09? Is Automatic Updates disabled?
>>
>> Why hasn't SP3 been installed yet? Time's running out: Computers running
>> WinXP SP2 will NOT be offered any further critical security updates,
>> Automatic Updates will cease to function, and Windows Update website will
>> not be available after 12 April 2010 until SP3 is installed.
>>
>> See the "How to obtain help" section of
>> http://support.microsoft.com/kb/971486
>>
>> For home users, no-charge support is available by calling 1-866-PCSAFETY
>> and/or 1-866-234-6020 in the United States and in Canada or by contacting
>> your local Microsoft subsidiary. There is no-charge for support calls
>> that
>> are associated with security updates. When you call, clearly state that
>> your problem is related to a Security Update and cite the update's KB
>> number (e.g., KB971486).
>>
>> Or you can...
>>
>> Start a free Windows Update support incident request:
>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>
>> Consumer Security Support home page
>> https://consumersecuritysupport.microsoft.com/
>>
>> For more information about how to contact your local Microsoft subsidiary
>> for security update support issues, visit the International Support Web
>> site: http://support.microsoft.com/common/international.aspx
>>
>> For enterprise customers, support for security updates is available
>> through
>> your usual support contacts.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>
>>
>>
>> jcrick wrote:
>>> After running windows update yesterday I've been unable to reboot and
>>> get
>>> the BSOD(0x0000007E) in normal and last good configuration or a kinder,
>>> gentler empty pale blue screen that hangs when booting in safe mode.
>>>
>>> Using a Dell Latitude D630 with XPhome SP2. Never run into a problem
>>> with
>>> the windows updates before although I do them regularly.
>>>
>>> Needed to boot from CD and use recovery console to uninstall the
>>> patches.
>>> Removing KB971486 (and KB969947) fixed the problem. Not sure which one
>>> actually caused the problem as there wasn't much information on the
>>> BSOD.
>>> Internet searches point more toward KB971486, though.
>>
>> .