From: "Geo." 

Yes, running low on space can cause it especially if it's trying to expand
the swap file and only little fragments of space are available. Might want
to free up a little more and then do a defrag. You also might consider
moving the swap file to the other disk. (control panel/system)

Geo.

"Ellen K"  wrote in message
news:309de6.6683dc{at}harborwebs.com...
> C drive showed no problems, but only had 115 MB free (out of 8 GB).  Do
you
> think the problem could have occurred due to insufficient free space?  I
moved
> some stuff so now it has 561.
>
> Haven't checked E drive yet, that one is newer, 40 GB and NTFS.  (C is FAT
32,
> I was too chicken to change it.)
>
> > From: "Geo." 
> > from a command line get to each disk drive and type
> > chkdsk /f /r
> > You'll get a warning that one of the disks can't be done without a
reboot,
> > do the reboot. See if you have a bad sector or something on the disk.
> > Typically it's a swapping error of some type and usually I find it's a
sign
> > that a disk has a problem. Can also be caused by a failed cpu fan or a
> > memory chip that needs reseating.
> > Geo.
> > "Ellen K"  wrote in message
> > news:109dd7.65a92a{at}harborwebs.com...
> >> What is a kernel stack inpage error?  I can't find anything on MSDN.

--- BBBS/NT v4.01 Flag-5