Troubleshooting of stack fault error conditions is addressed here:
http://aumha.org/win4/kbesf.htm
Stack Faults occur if a program refers to a memory address that is beyond
the limit of a stack segment. Most of these, therefore, are actual program
bugs and, more often than not, the solution is to update some program or
module.
When core Windows components such as EXPLORER and KERNEL32.DLL are involved,
this may mean that one or the other has become corrupt and should be
replaced; it may mean there are hardware issues such as are discussed on
http://aumha.org/win4/a/kernel32.htm ; or it could be (and most often is)
that the problem is not in either of those modules but in some program you
are running at the moment of the error. Trying to pin down the circumstances
where this occurs is the first step. Looking at what changes you made on
your computer soon before this began is a further step. Also screen for
viruses and scumware (for example, browse to http://aumha.org/a/noads.htm
and let it analyze your system).
Possibly, your situation is described in the following KB article:
http://support.microsoft.com/?kbid=189952
If so, the solution is a Registry repair that is described in the article.
However, this seems to point to a specific situation not quite the same as
what you described. Never modify the Registry without first backing it up.
--
Jim Eshelman
MS-MVP, Windows Shell/User
http://aumha.org/
http://WinSupportCenter.com/