Printer Rendering Engine Crash – Fix in 3 Steps

Quick answer for pros

Stop the spooler service (net stop spooler as admin), delete everything inside C:\Windows\System32\spool\PRINTERS, restart the spooler (net start spooler), re-send your print job.

Why this crash happens

When a print job starts failing, Windows sends it to the spooler—a background service that holds the data until the printer can take it. If that spool file gets corrupted (a power loss, a hung app like Adobe Reader, or a bad printer driver update), the rendering engine in the driver can't parse it. The whole pipeline crashes: the spooler stops, the print dialog freezes, and you get an error like "Print job failed" or "Rendering error."

What's actually happening here is the spooler process (spoolsv.exe) tries to feed the broken file to the printer driver's rendering component. That component throws an exception, and Windows kills the whole spooler to protect itself. You'll see Event ID 7031 or 7034 in the System log if you check.

The real fix

1. Open Command Prompt as admin. Press Win+R, type cmd, then Ctrl+Shift+Enter. This gives you the power to stop system services.
2. Stop the spooler. Run net stop spooler. It'll say "The Print Spooler service is stopping." Wait 5 seconds.
3. Delete all files in the spool folder. In the same cmd window, run del /q /f C:\Windows\System32\spool\PRINTERS\*. The /f forces deletion even if Windows thinks they're in use.
4. Restart the spooler. Run net start spooler. That's it—your print queue is clean.
5. Send your document again. Open the file, hit Print. It should render and print now.

The reason step 3 works is we're removing the corrupt file that was stuck in the spool folder. Once it's gone, the spooler starts fresh and can handle the next job without crashing.

If the main fix doesn't work

Sometimes the corrupt file isn't the only problem. The driver itself is broken. Try these alternatives:

• Remove the printer and reinstall it. Open Settings > Bluetooth & devices > Printers & scanners. Click your printer, select Remove. Then add it again—Windows will download a fresh driver from Windows Update or the manufacturer's site.
• Use the built-in troubleshooter. In Windows 10/11, go to Settings > System > Troubleshoot > Other troubleshooters > Printer. It'll scan for common issues—but in my experience it misses the corrupt spool fix half the time. Only try this if the manual steps fail.
• Reinstall the spooler service itself (advanced). If the spooler crashes again after step 4, run sfc /scannow to check system files. Then DISM /Online /Cleanup-Image /RestoreHealth. This fixes deeper corruption in the spooler binaries.

Prevention tip

Don't let your printer driver auto-update. I've seen HP and Lexmark driver updates break rendering engines. Set your printer to manual updates: in Device Manager, right-click your printer, go to Properties > Driver tab > Update Driver > Browse my computer > Let me pick. Stick with the driver that worked for you. On Windows 11, you can also go to Settings > Windows Update > Advanced options > Receive updates for other Microsoft products—turn that off to stop driver updates from rolling in unexpectedly.

Also, if you cancel a print job mid-print, always wait 10 seconds before sending another one. That avoids the race condition where the spooler writes a partial file while you're trying to delete it.