Windows Print Spooler Crashes Repeatedly

Brown SOLIVER 0 Reputation points
2026-10-28T00:45:59.3233333+00:00

The Print Spooler service repeatedly crashes when users print specific documents. How can I identify problematic print drivers, corrupted spool files, and application-specific printing failures?

Windows for business | Windows Client for IT Pros | User experience | Print, fax, and scan
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Senthil kumar 2,915 Reputation points
    2026-10-28T04:44:13.0866667+00:00

    Hi @Brown SOLIVER

    1. A faulty printer driver
    2. A corrupted spool file (.SPL/.SHD)
    3. An application generating invalid print data

    A structured isolation approach helps determine which one is responsible.

    1. Check Event Viewer for the Crash Source

    Open Event Viewer:

    Plain Text

    eventvwr.msc

    Review:

    Plain Text

    Windows Logs > Application

    Windows Logs > System

     

    Look for:

    • Event ID 1000 (Application Error)
    • Event ID 7031 (Service terminated unexpectedly)
    • PrintService related events

    If Event ID 1000 shows a faulting DLL such as:

    Plain Text

    hp*.dll

    canon*.dll

    xerox*.dll

    kyocera*.dll

    the printer driver is usually the culprit. A faulting vendor DLL often identifies the problematic driver directly.

    1. Determine Whether the Issue Is Document-Specific

    Test the same printer using:

    Plain Text

    Notepad

    Paint

    WordPad

    Questions to answer:
    Test Result
    Same document from another application Crash?
    Different document from original application Crash?
    Test page from Windows Crash?

    If:

    • Only one file crashes → corrupted document
    • Only one application crashes → application-specific rendering issue
    • Everything crashes → printer driver or spooler issue

    Microsoft recommends comparing behavior across applications and printers to isolate the cause.

    1. Check for Corrupted Spool Files

    Stop the spooler:

    BAT

    net stop spooler

    Navigate to:

    Plain Text

    C:\Windows\System32\spool\PRINTERS

    Delete all files:

    Plain Text

    *.SPL

    *.SHD

    Then restart:

    BAT

    net start spooler

     

    Old or corrupted spool files can repeatedly crash the Print Spooler service.

    Thanks.

    Was this answer helpful?

    0 comments
  2. Xuan Nhu 1,535 Reputation points Independent Advisor
    2026-10-28T01:18:47.81+00:00

    Good day, Mr.Brown!

    To identify problematic drivers and corrupted spool files, please stop the service with Stop-Service spoolsv and clear stuck .SHD and .SPL files from C:\Windows\System32\spool\PRINTERS. Then, check Event Viewer under Application (Event ID 1000) and PrintService > Operational logs to pinpoint the exact crashing driver DLL located in C:\Windows\System32\spool\drivers\x64\3.

    To prevent future crashes from taking down the spooler, open printmanagement.msc, right-click the suspect driver, and set Driver Isolation to Isolated. This isolates rendering to PrintIsolationHost.exe so application-specific failures won't crash spoolsv.exe.

    Please give it a try and let me know if it works. I'm here to assist!

    Xuan Nhu.

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-10-28T00:46:22.5333333+00:00

    Use a structured isolation approach:

    1. Confirm whether the failure is document-specific or app-specific
      • Try printing the same content from another app, such as Notepad or Paint.
      • Try printing a different file from the original app.
      • If only one app or one file fails, the issue is likely application-specific rather than a general spooler failure.
    2. Check and clear the print queue first
      • In Windows 11: Start > Settings > Bluetooth & devices > Printers & scanners.
      • In Windows 10: Start > Settings > Devices > Printers & scanners.
      • Open the printer queue and cancel all jobs.
      • Stuck jobs can keep the spooler unstable and prevent clean testing.
    3. Restart the Print Spooler service
      • Open services.msc.
      • Find Print Spooler and select Restart.
      • Command-line options:
        • Command Prompt as administrator:
          • net stop spooler
          • net start spooler
        • PowerShell as administrator:
          • Restart-Service -Name spooler
      • This clears transient failures and helps determine whether the crash is repeatable with the same document.
    4. Inspect the Spool folder for corrupted spool files
      • Default Spool folder: systemroot\System32\Spool\Printers
      • If old or orphaned files remain there, move them out of the folder and test again.
      • Corrupted files in the Spool folder can cause Print Spooler crashes.
      • The configured spool path can be verified in the DefaultSpoolDirectory value under:
        • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
      • To remove files from the Spool folder, it may be necessary to stop the Print Spooler service first.
    5. Identify problematic print drivers
      • Open Device Manager.
      • Expand Print queues or Printers.
      • Remove unnecessary, old, or duplicate printer drivers.
      • Install the latest driver for the printer model from the manufacturer.
      • Outdated or conflicting drivers are a common cause of spooler crashes.
    6. Test whether jobs are spooling correctly before actual printing
      • Pause the printer so the job can spool without printing.
      • This helps confirm whether the crash happens during spooling or later in the print pipeline.
      • Another test is to configure the printer temporarily to use the NUL port:
        • Change the printer port to Local Port.
        • Select New Port.
        • Enter NUL as the port name.
      • This allows testing spool behavior without sending output to physical hardware.
    7. Check spooler dependencies and service state
      • By default, the Print Spooler depends only on RpcSs.
      • Verify the DependOnService value under:
        • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler
      • Also verify that dependent services are started.
    8. Review system and security interference
      • Check event logs for errors related to initializing the local print provider or other spooler startup failures.
      • Verify that no Group Policy is disabling or stopping the Print Spooler service.
      • Check whether antivirus is scanning the Spool folder or .SHD, .SPL, or .TMP files, because that can cause access denied errors, stuck jobs, and spooler instability.
    9. If the crash occurs only from Word, Excel, or another specific app
      • Verify the correct printer is selected in the app.
      • Check app print settings such as page size, orientation, layout, page range, and whether Print to PDF or Print to file is selected.
      • Print a Windows test page from Printer properties > General > Print Test Page.
      • If Windows test pages print successfully but the app still fails, repair Microsoft 365 or Office:
        • Start > Settings > Apps > Installed apps > Microsoft 365/Microsoft Office > Modify > Quick Repair
        • If needed, run Online Repair.
    10. Use the results to isolate the root cause
    • Only one document fails: likely document corruption or content-specific rendering issue.
    • Only one app fails: likely app settings or app installation issue.
    • Multiple apps fail on one printer: likely driver or spooler pipeline issue.
    • Failures stop after clearing Spool folder: likely corrupted spool files.
    • Failures stop after driver cleanup/update: likely problematic print driver.

    Warning: registry changes and manual removal of print components can affect printing broadly. Export HKLM\SYSTEM\CurrentControlSet\Control\Print before manually removing printing components from the registry.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.