Ken Springer wrote:
> I'm "rebuilding" an old Gateway E-4600 computer, to give away via a
> local social agency. And I've run into some strange happenings, just
> short of being "possessed", that I've never come across before. :-)
>
> Operating system is XP Home, and the COA product ID is valid.
>
> As I write this, I'm in the midst of the 3rd attempt to get all updates
> to install *without* preventing the computer from shutting down. Each
> install has given me minor differences in the updates available, but I
> didn't keep sufficiently detailed records of what was offered to be
> specific in those differences. :-( I'll know better from here on out!
> LOL
>
> I didn't realize a problem existed in the shutdown until I was almost
> finished with the first rebuild, which included software installation.
>
> During the second and third rebuilds, I extensively used System Restore
> to isolate any problem, and found the following:
>
> KB 2393802 Security Update for Windows prevents the computer from
> shutting down using shutdown from XP. The only way I've found to shut
> it down is to hold the power button in or unplug the computer. I didn't
> actually unplug it, but that obviously has to work! LOL
>
> More interestingly, the KB article refers to Intel and AMD graphic
> adapters, and this computer has an NVIDIA GeForce2 MX/MX 400 display
> adapter (via Belarc Advisor).
>
> I'm still trying to find an answer online, but nothing so far. :-(
>
> Thoughts and suggestions?
>
>
http://blogs.technet.com/b/asiasupp/...kb2393802.aspx
"We have heard numerous reports of systems experiencing a BSOD after
applying this update, and we have been able to confirm this issue
results from kernel stack exhaustion. KB 2393802 leaves less stack
space available in the Windows kernel for other kernel modules to use."
http://www.symantec.com/connect/foru...fter-kb2393802
"Results of the investigation
After reviewing a number of memory dump files, our engineering team
has determined the following:
* Windows XP leaves approximately 12,000 bytes of shared stack space for
kernel modules to share.
* Windows provides no way to identify available stack space; it just BSODs
when the stack overruns.
* PGP WDE 10.0.2 and below use approximately 600 bytes of stack space.
* In the PGP WDE 10.1, we proactively reduced this to approximately 100 bytes
of stack space.
* KB 2393802 leaves less stack space available in the Windows kernel for
other kernel modules to use.
* PGP WDE (pgpwded.sys) is generally the last driver loaded. As a result,
when we try to grab our modest stack space, the blue screen will display
our driver name as the responsible driver.
* In our testing, almost every system suffering from this problem used the
Intel graphics driver. This uses about 7,000 bytes(!) of stack space.
Without this single driver using over half of this available shared resource,
there would be plenty of room for the WDE driver.
"
But your machine probably has a separate graphics card, and not integrated Intel.
(It's a P4 with RDRAM as far as I know, and I don't think they did integrated
graphics in the associated chipsets.)
Stack space is used for things like subroutine calls, and I didn't think it
was used for other purposes. And that's probably why that space is so small
to begin with. Being the home of the kernel, that 12000 bytes isn't used
by applications, and the quality of code running there, has to be a lot
better than your general purpose software. (Otherwise, it would have been
crash city before KB2393802.)
Have you checked the Event Log ? It's probably too late, when something
like that happens, for an entry in the Event Log, but take a look and see.
Paul