Somewhere in your driver list is one bad driver crashing the whole printing system. This guide finds it the way technicians do — evidence first, then one removal at a time, never a blind reinstall of everything.
The spooler itself is rarely the criminal; it is the room where one driver keeps starting a fire. This guide gives you the hunt in order: read the faulting module name, build the suspect list, remove one printer at a time, and reinstall with proof — so the fix stays fixed.
Every driver on this list loads into the spooler's world. The crash usually belongs to one of them — often the oldest, strangest one.
Printer drivers are written by printer makers, not Microsoft, and they run with deep access inside the printing system. A buggy driver — especially an old one carried through years of Windows upgrades — can crash spoolsv.exe outright, taking every printer on the PC down with it.
This is why the spooler so often dies on a PC where one specific printer was recently added, replaced, or updated — and why the same PC printed happily for years before that day.
Before removing anything, collect evidence. In Event Viewer → Windows Logs → Application, the crash event for spoolsv.exe lists a Faulting module name. If that DLL belongs to one printer's driver, your hunt is already half done — start with that printer.
If the faulting module is a Windows file like ntdll.dll, the driver may still be the trigger passing bad data; continue with the removal test below.
This is the discipline that makes the hunt work:
printmanagement.msc) → All Drivers → right-click the driver → Remove Driver PackageIt is tempting to wipe all printers and start fresh. Resist it. If you remove five printers and the crashing stops, you know one of five was guilty — and when you reinstall all five, the guilty one returns and so does the crash, and you have learned nothing except that the problem lives somewhere in a pile you rebuilt identically.
One at a time is slower by an hour and faster by a week.
Sometimes the maker's current driver is genuinely broken with your Windows build. Your honest options, in order: try the maker's universal driver (most big brands publish one), try the driver for the nearest older model in the same family, or isolate that driver so its crashes stop taking the spooler down while you wait for a fixed release.
What does not work: installing the same crashing driver again more carefully. The result will be the same crash with better intentions.
The full print spooler repair — finding the real culprit and stopping the crash loop — is shown step by step in the video.
▶️ Watch Full VideoTwo ways that agree with each other. Event Viewer's crash event names the faulting module — match that DLL to a printer brand. And the removal test proves it: remove one printer, and if the spooler stops crashing and stays stable, that printer's driver was the culprit.
No. Driver updater utilities are unreliable and a known source of bundled junk and malware. Get the driver from the printer maker's official support page for your exact model — that is the only source worth trusting for something that runs this deep in Windows.
Then reinstall is your test: remove the printer and its driver package completely, restart, and install the newest driver from the maker. If the maker's newest driver still crashes the spooler, use their universal driver, or set that driver to Isolated mode in Print Management so its faults stop killing the whole service.