If Print Spooler starts and then stops repeatedly, treat it as a service or print-component crash. Repeatedly clicking Start will not identify the corrupt queue, driver, or dependency.
Quick answer
Start by identifying which layer is failing
What to do first
The spooler manages Windows print jobs and drivers. A bad job, incompatible driver, damaged print component, or service dependency can make it stop when printing begins. Start with the least disruptive test that can separate a local problem from a wider Windows, network, printer, storage, or hardware issue.
Likely causes
What commonly produces this symptom
Common possibilities include corrupt queued job; incompatible or damaged printer driver; third-party print monitor; service dependency; system-file corruption. The symptom alone does not prove which one is responsible, so use the decision path before changing several things at once.
Diagnostic path
Use evidence before the bigger fixes
Open Services, find Print Spooler, and note whether it stops immediately or only when a job is submitted. Remove or pause the affected printer through Settings. Check Event Viewer only for corroborating errors. Test with a built-in or known-good printer driver before broad repair.
Record the exact message, when it began, and any update, driver, peripheral, or network change that preceded it.
Test the smallest comparison that applies: another device, account, cable, port, display, printer queue, or power source.
Make one reversible change, restart or retest, and note whether the symptom changes.
Fixes
Work from safest to most invasive
Stop Spooler from Services, clear the queue through the standard printer workflow, start it again, and test one printer; remove the problematic driver from Print Server Properties only when you recognize it; install the exact current driver; run SFC and DISM for wider Windows symptoms; restart after changes.
Use commands only when they match the evidence. An elevated Terminal may run sfc /scannow to check protected Windows files, followed by DISM /Online /Cleanup-Image /RestoreHealth when component repair is justified. Restart and test after the repair.
When to stop
Know when the next step is support
Do not delete arbitrary spool files or registry entries. If the service crashes with several known-good drivers or the PC is managed, escalate to an administrator or printer vendor. Avoid random registry edits, unknown driver tools, manual deletion of system folders, or a Windows reset simply because the first check did not work.