Start the service, it runs, it stops. Start it again, same story. The restart feels like a fix because printing works for a minute — but the cause is still sitting there, waiting. Here is why the loop happens and how to break it properly.
Every spooler guide on the internet starts with restart the service — and for a repeating problem, that is exactly where they go wrong. This article explains the mechanism honestly: what the spooler loads when it starts, the three things that crash it again, and the fifteen-minute diagnosis that replaces fifteen restarts.
The Print Spooler service terminated unexpectedly. It has done this 14 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Fourteen restarts in the log means fourteen crashes — the restart is recording the problem, not solving it.
Starting the Print Spooler service loads spoolsv.exe, which immediately does three things: it reads the jobs waiting in the spool folder, loads every printer driver, and starts listening for new print jobs. Nothing in that sequence repairs anything.
So if the thing that crashed it is still present — a damaged job file in C:\Windows\System32\spool\PRINTERS, or a driver DLL with a bug — the spooler walks straight back into the same crash. The restart is a reset button on a machine that is still jammed.
One: a poisoned job. A single corrupt or half-written job file is processed first at every start and kills the service instantly. The spooler often stops within seconds of starting, even with nobody printing.
Two: a faulty driver. The service survives until someone prints to one particular printer, or until that printer's driver is loaded. The crash follows the printer, not the clock.
Three: a driver that broke after an update. A Windows update — especially the printer security hardening updates — replaced or restricted something the old driver depended on. It worked yesterday, it crashes today, and the driver is the difference.
You do not need any tool for this test — just watch when it stops:
Work the cause, in this order: clear the spool folder once, properly. Then open Event Viewer → Windows Logs → Application and read the faulting module in the spoolsv.exe crash event. Then repair or remove that one driver and reinstall it from the maker's website.
That sequence takes about fifteen minutes and ends the problem. Fifteen restarts take fifteen days of interruptions and end nothing.
While you investigate, the Recovery tab in the spooler's properties can restart the service automatically a minute after each crash. That is a reasonable safety net for a busy office — users keep printing while you fix the cause.
Just do not mistake it for the solution. If you set auto-restart and walk away, you have a printer that crashes quietly forever, and the Event log filling with proof.
The full print spooler repair — finding the real culprit and stopping the crash loop — is shown step by step in the video.
▶️ Watch Full VideoOnce can be a freak corrupt job. Twice with the same pattern means something on the PC — a stuck job file or a driver — is crashing it on purpose-like regularity. From the second repeat, stop restarting and start diagnosing: clear the spool folder and check Event Viewer.
Because at startup it loads all drivers and processes leftover job files. A corrupt job in the spool folder or a driver that fails while loading will kill it with no user printing at all. That timing is actually a strong clue pointing at the spool folder or a driver.
No. Automatic only decides that the service starts with Windows. It says nothing about crashes. A spooler set to Automatic will still stop every time the bad job or bad driver crashes it — it will just also be stopped fresh every morning.