You are having difficulty with your print driver.  Spool32 is mostly related
to printing, as you have already noticed.  Errors on boot-up are usually
related to a bad print job stuck in the spooler.  This 'stuck' print job may
or may not be a legitmate print request.  When the driver is acting flakey,
simple things like a printer on-line status request can cause the spooler to
think a job is pending.  At the next boot-up, the spooler wants to notify
you that it has a job pending, do you want to print or cancel, but instead
something causes an invalid page fault.  If you can't update your printer
driver (you are using the best one now) I would recommend you change the
spooler setting to RAW. Click on your printer's Icon and select properties,
and change the spooler settings.  You can experiment with your other spooler
settings too.  If you have one of those scanners that connects through your
printer parallel port, I recommend you throw it out and get a usb scanner.
I have had all types of collateral damage with a parallel port scanner and
its twain driver, although the darn thing scans fine.  Last, if you are
using a parallel port printer, do you know what the bios cmos setting is for
your parallel port?  Verify it is set to the printer's prefered setting, and
you are using the proper cable.  If your printer wants the high end IEEE
cable, go purchase one.
You should be able to fix this without resorting to a windows re-install.  I
will admit to throwing a cheap Cannon inkjet away rather than dig into and
solve its flakey behavior. Good luck.
Tom Turak

-----Original Message-----
From: Ted Saselli [mailto:[log in to unmask]]
Sent: Thursday, January 03, 2002 10:39 PM


This one is driving me nuts and I hope someone can point me in the right
direction.  In the last 9 months, my machine has crashed 124 times due to
the following:

SPOOL32 caused an invalid page fault in
module SPOOL32.EXE at 017f:00402015.

Some specifics.  My machine is a HP Pavilion 6645C, Intel Celeron 566mhz,
128mb RAM, Windows 98SE.  This problem only occurs at boot up.
Let me repeat that.  THIS PROBLEM ONLY OCCURS AT BOOT UP.  Never when
printing or scanning.

Some things I have done to correct the problem:
1.  Disabled Norton Anti-Virus
2.  Diabled Norton Utilities
3.  Thinking that I might have a corrupted spool32.exe file, I replaced it.

               The NOSPIN Group Promotions is now offering
              Mandrake Linux or Red Hat Linux CD sets along
         with our NOSPIN Power Linux CD...  at a great price!!!
             http://freepctech.com/goodies/promotions.shtml