Print Spooler Crashes Every Few Minutes – Fix It

You're working away and suddenly your printer's gone. You check Services.msc and the Print Spooler shows 'Stopped.' You restart it, and it runs for maybe 5 minutes, then dies again. I had a client last month whose whole office hit this—every single machine, every five minutes, like clockwork. It's not random. It's almost always a corrupted print job or a bad driver that's stuck in the queue.

What's Really Happening

The spooler service goes down because a print job gets stuck—usually a PDF that choked on a missing font or a driver that wrote bad data to the spool folder. When the spooler tries to process that job, it chokes and crashes. Then Windows auto-restarts it, but it hits the same bad job again. That's the cycle: crash, restart, crash, restart. The Event Viewer will show Event ID 7034 for the spooler service.

Some people blame network printers or USB hardware, but I've seen this happen with a printer that wasn't even turned on. The job sits in the queue, waiting for a device that doesn't exist, and takes down the whole service. Don't waste time uninstalling printers or running SFC scans—skip that. The fix is to kill the bad job directly.

How to Fix It – Step by Step

You'll need to stop the spooler, delete the stuck jobs, then restart it. Here's exactly how, with no fluff.

Open an Admin Command Prompt – Click Start, type cmd, right-click and select 'Run as administrator.'
Stop the spooler – Run this command:
```
net stop spooler
```
Wait until you see 'The Print Spooler service was stopped successfully.' If it hangs, force stop via Task Manager (Services tab).
Delete the stuck jobs – Go to the spool folder:
```
del /q /f C:\Windows\System32\spool\PRINTERS\*.*
```
Yes, this deletes all pending print jobs. That's what you want.
Clean up drivers too – Sometimes a bad driver file sits in the drivers folder. Run this:
```
del /q /f C:\Windows\System32\spool\DRIVERS\*.*
```
(this deletes driver files, but Windows will reinstall them on the next print)
Start the spooler – Run:
```
net start spooler
```
Check Services.msc to make sure it's running and set to Automatic.
Clear the print queue in PowerShell (extra insurance) – In the same admin prompt, run:
```
Get-PrintJob | Remove-PrintJob
```
This nukes any jobs that might still be cached.

After that, try printing a test page from Notepad (not a complex PDF). If it prints, you're golden. I've done this on dozens of machines, and it fixes 9 out of 10 cases.

If It Still Crashes After That

If the spooler still dies, you've got a deeper driver issue. Here's what to check:

Remove all printer drivers – Go to Settings > Printers & Scanners > click on any printer > Remove device. Then open Device Manager > View > Show hidden devices > expand Printers and right-click delete any ghost printers.
Rename the spool folder – Stop the spooler, rename the PRINTERS folder to PRINTERS.old, restart the spooler. Windows will create a fresh folder.
Check for third-party print managers – Stuff like PaperCut, HP Easy Start, or Brother utilities can inject bad filters. Uninstall them temporarily to test.
Look at Event Viewer – Filter to Event ID 7034 for the spooler, and Event ID 20 for print job failures. The error message often points to the exact driver or file causing the crash.

I once spent two hours on a machine where the culprit was an old HP PCL6 driver from 2019. Switched to the built-in Microsoft IPP Class Driver, and it never crashed again. Moral of the story: if you're using a manufacturer's 'full feature' driver and it's older than two years, switch to the basic driver from Windows Update.

One last thing—if you're on a domain, the spooler might crash because of group policy pushing a bad driver. Check the print server's queue and clear it there too. Sometimes the bad job lives on the server, not the local machine.

That's it. No need to reinstall Windows or buy a new printer. Clear the queue, kill the bad job, and you're back in business. If it still fails after all this, I'd bet money on a faulty printer port (try a different USB port or switch from WSD to TCP/IP). But 99% of the time, the steps above will solve it.