HiI have installed windows 7 prof 32 bit on a few of our machine networks and so far so good ...apart from fromt he printer spooler keeps crashing at random intervals with the error code of 0x0000002.Im guessing its because our print server has probably dished out an xp driver and windows 7 doesnt like it ...thats a guess anyway. So far all windows 7 machines suffer and we have to restart the local spooler..So my question is seeing as we will be a mixed environment do i have to install the new drivers locally or can my win 2003 server dish out the correct onesCheersET

Have you narrowed it down to which printer could be causing the problem? What does the event logs say?MCSE, MCSA, MCDST

If you would like to find which printer driver cause the crash issue, I suggest you isolate each driver and run printing job. Please: 1. Open mmc in Start Search box.2. Click File->Add/Remove snap-in3. Add "Printer Management". Click Add "The Local Server". 4. Click Finish. 5. Expand Print Servers->[server name]. Click on Drivers. 6. Right-click on the first driver, choose "Set driver isolation"->"Isolated". 7. Start a printing job.8. If the issue still occurs, change the isolation to System Default for this driver, then isolate the next driver and start printing job. You can find which driver is the root cause. You need to involve a Windows 7 compatible driver for Windows 7 clients. If the driver is packed, you can extract the driver pack and add the driver from printer server console. However, if the driver is included in an installation file, you may try the following method. 1. Install the driver on one of the Windows 7 clients.2. Launch mmc from Start Search box.3. Click File->Add/Remove Snap-in.4. Add "Printer Management". Point to the server in "Specify the printer server". 5. Expand "Printer Management"->"Printer Servers"->"Drivers". 6. Right-click, then click "Add a driver". Please follow the instructions to add the Windows 7 printer driver. After doing so the driver should be added into the server. If the printer driver is not found, the driver should be not designed for enterprise environment. In this case you may need to add the printer from the client side manually.Arthur Xie - MSFT

Will try that thanks ...but so far all of our HP4100's suffer and even with Windows 7 drivers installed it still does it

Hi if it helps after a cold boot thats when we have to restart the spooler and yup the spooler is set to automatic...

Its not the drivers its the print spooler after every reboot the spooler needs restarting

We also have seen this with HP 4xx0 series. Users are quite frustrated. The last troubleshooting thing I did was to remove all printers mapped to the print server (2003) and map directly. It happens seemingly randomly. Sometimes print spooler will stay up for days, other times it will bounce over and over again. We thought it was related to PDF spooling but removing that didn't help.

We also have seen this with HP 4xx0 series. Users are quite frustrated. The last troubleshooting thing I did was to remove all printers mapped to the print server (2003) and map directly. It happens seemingly randomly. Sometimes print spooler will stay up for days, other times it will bounce over and over again. We thought it was related to PDF spooling but removing that didn't help.

Beyond a joke is this now...this printer issue is so annoying....I could map directly from each windows 7 client but that will take forever to do. Whats the point of a print server if you map directly !Anyone any ideas why this is happening ? I have tried every driver under the sunw ith no joyCheersET

hi,i have the same Problem and it is terrible that it occurs with HP Produkts. Many have the Problem and still no solution.....grr...cyaMarcus

its a joke...all this HP kit and I have to restart spoolers manually on clients. I hope HP are aware of this !!

We recently purchased some new HP laptops and Desktops. The laptops are running 32bit win7 and are having the same issues as posted above. The desktops however are running windows 7 64bit and have no issues with the print spooler. The 32bit machines randomly need the print spoolers restarted. I havent linked a certain event to the print spooler crashing yet. I removed all printers from the Server 2003 print management console and added them again. The print spooler on the 32bit machines is still crashing.

Be sure the follow the instructions on setting up the print drivers in Isolation so they do not cause spooler failures.Alan Morris Windows Printing Team

I was having the same problem with an HP laptop with W7 32 bit. I followed steps 6-14 of this article http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm and everything seems to be back to normal now. Good luck.

You can use certain software to fix the issues related with printer spooler. One of the best software which will help you to fix the issue is printer spooler fix wizard. The printer spooler fix wizard will help to fix printer spooler error messages and spoolsv.exe service. This software will help to fix the errors including “spooler sub system app stopped working and was closed” and spoolsv.exe service infection and corruption in Windows 7 computer.

I'm also having the same issue, but with Ricoh. We have about ~8000 workstations and 1000 printing devices (@ 80+ locations), in a mixed XP/W7 environment. And of those ~8000 computers about 10 (Windows 7 only) workstations are having problems where the print spooler will crash. (XP is fine) The system logs report that the PScript5.DLL file caused the spooler to crash, (the drivers are up-to-date). The really comical thing is when we go to delete the driver package (after deleting the queues from the Devices and Printers area), the system comes back reporting that the drivers are still in use and can't be deleted. (Restarting the spooler doesn't help, like it did in XP). The only way to delete these drivers is to start the removal process (via Print Manager > Drivers) and when prompted for confirmation, stop the spooler, restart the spooler and then immedately answer 'Yes' to the driver confirmation. That will get rid of the Post Script drivers. (PCL queues don't get locked by the OS whereas the Post Script queues all get locked) Even after getting rid of all the drivers and reinstalling them from scratch, the spooler is still being crashed by PScript5.dll. To date, we still don't have a solution.

Is there any additional information from the text based report.wer file in the ProgramData\Microsoft\Windows\WER\ReportQueue directory?Alan Morris Windows Printing Team

HI Print Spooler is one of the software programs that are responsible for managing all the printing jobs on your system. Print Spooler sends the printing request to the computer printer or to the print server. It can manage print jobs currently waiting to be printed on the printer. Print Spooler schedules printing jobs to be carried out on the system and transfers messages from the system to the printer for taking printouts. There are several problems which may cause Print Spooler to crash. If a Print Spooler error occurs, it can cause the printing process to fail. Some of the issues are compatibility issues and outdated drivers. Here are the reasons due to which Print Spooler crashes on Windows 7 and ways to resolve the errors: * Incompatibility * Corrupt printer driver * Print Spooler errors Incompatibility The main reason for Print Spooler crashing is because of its incompatibility with the Operating System. It may result in the failure of the printing process on the system. You can fix the issue by checking whether the printer supports the Operating System or not. If it does not support it, then you have to install the correct printer drivers from a website. This can resolve the compatibility issues. Corrupt printer driver If the existing printer drivers are corrupt, they may cause the printer driver to crash. Also, if the printer is not installed on the system, then Print Spooler will not be able to recognize the printer. You can fix the issue by starting the computer in Safe Mode. When you switch on the system, you need to go to the ‘Windows Advanced Option’ by pressing the ‘F8’ key and then select ‘Safe Mode‘. By doing that, you will be able to delete previously installed printer files. Print Spooler errors There are chances Print Spooler on the system will show errors. The documents in the queue will not be printed or deleted. This can lead to lock ups, slow system performance, disk space errors etc. The printing process may fail and as a result the Print Spooler may crash. You can fix the issue by downloading the Print Spooler repair tool which is called ‘PC Health Advisor’. Thanks

Yeah, they talk about it, but there is no util to download. Appears to be a subscription service only.

I am also having the same problem but cant seem to find the solution. Can anyone help? My thread is here: http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/3451fd1c-9c00-40aa-9a22-1154faaace30

I am also having the same problem but cant seem to find the solution. Can anyone help? My thread is here: http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/3451fd1c-9c00-40aa-9a22-1154faaace30

I am also having the same problem but cant seem to find the solution. Can anyone help? My thread is here: http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/3451fd1c-9c00-40aa-9a22-1154faaace30

Do you have any apple software running on your system? I have worked exstensively on this problem on my own laptop. What I have found is the solution is a two pronged approach. After reading the suggestions of many of the extremely qualified techs in this forum, I think I might have found what the cause of the issue is. I ended up formatting the hard drive twice but there is a very good possibility this could have been avoided. It has to do with bonjour. Finally after trial and error I noticed that the problem is linked back to apple software compatibility and the ability to print over a network of any size. Before I installed any apple products I noticed that the service name was print spooler. After installing apple products such as safari the name was changed to simply spooler. I also noticed that the problem did not occure until I installed the apple product, the name was changed, the spooler service was not controlled by me the admin on the local computer anymore, in other words the name and credentials changed when the apple product was installed. I then uninstalled the apple products and ran CMD with elevated priveleges sfc /SCANNOW. This fixed the problem. What I have not found out yet, is, how to make the apple product play nice with the microsoft GUI. However I am happy to have the problem solved this far and maybe someone else can give some words of advice to make the two giants play on the same block, lol. I will report if the error comes back again making this solution no longer valid but so far so good. I hope this helps. BTW uninstall the apple programs first then run the system file checker, I think you will find that your spooler will still be named spooler instead of print spooler but it is working properly. I also think the name change has something to do with the problem as well, once control over the service is changed. I have read a lot of solutions and tryed many of them. But only found this solution through good old trial and error, many hours of it.