Spooler Subsystem App problems with network printer

G

Guest

Everytime I go to print a document on my network printer (Oki Data C5500) I
get this message:
----
The Spooler Substyem App has stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: spoolsv.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b734
Fault Module Name: OPHD_UM.DLL
Fault Module Version: 0.3.0.0
Fault Module Timestamp: 445f1841
Exception Code: c0000005
Exception Offset: 0000b7f9
OS Version: 6.0.6000.2.0.0.768.2
Locale ID: 1033
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
----
The network printer drive is installed on Windows XP on a HP Desktop
computer and the problem lies with my Vista Basic Dell 1500 laptop not
printing over the network. Other laptops in my household that have Vista do
not have this problem.

I did have it printing over the network, then I installed the Oki Data
printer drive directly onto the laptop, and printed using a USB cable. Now
that I am back to the wireless network it isn't working.

Any help would be greatly appreciated!

Thanks,
Joy
 
A

Alan Morris [MSFT]

Be sure to send those app crash dump files to Microsoft. They do make their
way to Okidata. Currently there are over 10000 spooler crashes when this
driver accesses an invalid pointer.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

jawaglen

I think the printer and printer driver are of NO issue to this
problem. The problem is deeper than a specific printer driver. I
have a new Sony Vaio running Windows Vista Business. I get the same
problem. I cannot add printers (of several kinds) without getting
the
Microsoft Message:

"Spooler SubSystem App stopped working and was closed. A problem
caused the application to stop working correctly. Windows will
notify
you if a solution is available." And an error message comes on that
gives "Operation could not be completed. Error 0x000006be."
Microsoft has no help in the Knowledge Base or tech help site.


The Windows Control Panel / Administrative Tools / Services / Print
Spooler can be set to automatic and started but does not stay
started. It shows started but apparently is stopped. It does the
same in Manuel and Started. It does not stay started even though it
shows started.


I wish Microsoft would get this solved. If anyone finds a solution,
please post it or email me.
Thanks
jawag
 
D

Dave Collmann

I have the EXACT same problem. Same laptop. Same symptoms, just started the
last few days. No new printers installed. I'll check your link below to see
if it helps.

Alan Morris said:
chttp://members.shaw.ca/bsanders/CleanPrinterDrivers.htm

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

I think the printer and printer driver are of NO issue to this
problem. The problem is deeper than a specific printer driver. I
have a new Sony Vaio running Windows Vista Business. I get the same
problem. I cannot add printers (of several kinds) without getting
the
Microsoft Message:

"Spooler SubSystem App stopped working and was closed. A problem
caused the application to stop working correctly. Windows will
notify
you if a solution is available." And an error message comes on that
gives "Operation could not be completed. Error 0x000006be."
Microsoft has no help in the Knowledge Base or tech help site.


The Windows Control Panel / Administrative Tools / Services / Print
Spooler can be set to automatic and started but does not stay
started. It shows started but apparently is stopped. It does the
same in Manuel and Started. It does not stay started even though it
shows started.


I wish Microsoft would get this solved. If anyone finds a solution,
please post it or email me.
Thanks
jawag
 
C

Chuck

It may also be that the new driver package over rote registry entries for
the other printer.
This has been an issue that resulted in "cleanup" utilities for specific
Mfrs. and printer models.
(HP among them) This can be quite confusing to track down, since it's
difficult to spot the differences.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top