Print spooler service does not restart

If your service is loading a copy of the message queuing driver (Mqac.sys) per instance, it's likely that you are running out of System View Space memory pool. Each instance of MSMQ uses 4MB of this pool and by default the pool size is only 16MB.

Whether this is actually happening will really depend on how (if at all) your service uses the MSMQ system, and whether it references it directly (loads its libraries) or uses some other method such as sockets to communicate with it.

If it turns out you are loading multiple instances of MSMQ you can mitigate your problem by increasing the system view space pool. This can be done by:

1. Open the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
2. Create a new DWORD value called SystemViewSize.
3. Calculate and specify this value as follows:
   • Use this formula: (16 + (the number of Message Queuing resources loaded x 4)).
   • For example, the value for a cluster with three Message Queuing resources equals 28.
4. Reboot

The low disk space could be an issue if the server tries to spool a job and there is not enough space. How low is low space?

There is an issue with the sppoler service addresed by a hotfix. It is related to drivers being copied to clients from the server MS Support Article

Have also seen a similar issue were removing all printers and adding them again resolved constant crashes of the spooler.