Full Diagnostic Tree & Step-by-Step Overview
At what exact moment during the print sequence does Microsoft Word crash or close?
- Word crashes immediately upon clicking 'File > Print' or pressing Ctrl + P before Print Preview loads.
- Print Preview displays fine, but Word crashes the moment you click the physical 'Print' button.
- Word crashes only when printing documents containing specific fonts, custom vector shapes, or embedded macros.
- Word crashes across all documents when printing to a network or shared enterprise printer spooler.
What underlying graphics, UI preview, or default printer driver component is failing on Print Preview load?
- Default physical printer driver DLL (e.g., HP, Canon, Epson) crashes during Word UI layout query.
- Corrupted global template (Normal.dotm) or Word Data registry keys corrupting Print Preview parameters.
- Hardware Graphics Acceleration or DirectWrite canvas initialization fails during preview rendering.
- Third-party Office add-in or PDF converter COM plugin intercepts print preview generation.
Isolating Default Printer Driver Faults and Switching to Microsoft Print to PDF
Solution:
Root Cause: Unhandled Exception in Vendor Printer Driver Graphics Module
When you open the Print tab in Microsoft Word (File > Print), Word automatically queries the active default printer driver to obtain page margins, printable area metrics, and color profile capabilities to render the live Print Preview. If the vendor driver DLL (such as hpmsl160.dll, epson10.dll, or cnmprs.dll) contains memory corruption, unhandled null pointers, or incompatible v3/v4 driver architecture, Word suffers an unhandled access violation (0xc0000005) and terminates immediately.
# Diagnostic Verification:
Open Event Viewer (eventvwr.msc) > Windows Logs > Application.Look for Error Event ID 1000 referencing WINWORD.EXE as the application name and a printer driver DLL as the faulting module.# Step-by-Step Fix:
Change Default Windows Printer to Virtual PDF Driver:Press Win + I to open Settings > go to Bluetooth & devices > Printers & scanners.Uncheck Let Windows manage my default printer if enabled.Click Microsoft Print to PDF > click Set as default.Verify Word Print Preview Functionality:Open Word and press Ctrl + P.If the Print screen loads cleanly without crashing, the previous default printer driver is confirmed as the root cause.Clean and Reinstall Vendor Driver via Print Management:Press Win + R, type printmanagement.msc, and hit Enter.Go to Custom Filters > All Drivers.Right-click the corrupted printer driver > select Delete Driver Package.Download and install the latest Type 4 (v4) driver directly from your printer manufacturer's official support portal.# Prevention & Long-Term Monitoring:
Use native Class/v4 print drivers rather than legacy v3 drivers in modern Windows environments to isolate driver crashes from user applications.
Rebuilding Corrupted `Normal.dotm` Template and Clearing Word Registry Data Keys
Solution:
Root Cause: Corrupted Global Template (Normal.dotm) and Registry Print Settings
Microsoft Word stores default page setup, page margins, printer settings, and macro configurations inside the global template file (Normal.dotm) and the Windows Registry under HKCU\Software\Microsoft\Office\16.0\Word\Data. If an improper shutdown or crashed print job writes corrupted page settings or invalid binary stream data to these locations, Word will crash every time it reads these parameters during Print Preview or print execution.
# Diagnostic Verification:
Launch Word in Safe Mode by holding Ctrl while double-clicking the Word icon, or running winword.exe /safe in Win + R.If Word prints successfully in Safe Mode, local template or registry corruption is active.# Step-by-Step Fix:
Rename Corrupted Normal.dotm Template:Close Word completely.Open File Explorer and navigate to: %appdata%\Microsoft\Templates
Locate Normal.dotm and rename it to Normal.old.*(Explanation: Word will automatically generate a clean, uncorrupted Normal.dotm file upon next launch.)*Reset Word Data Registry Keys via PowerShell:Open PowerShell as Administrator and run: Remove-Item -Path "HKCU:\Software\Microsoft\Office\16.0\Word\Data" -Recurse -Force -ErrorAction SilentlyContinue
Relaunch Word normally and test printing.# Prevention & Long-Term Monitoring:
Avoid force-killing WINWORD.EXE processes while document template saving operations are active in the background.
Disabling Hardware Acceleration and GDI Canvas Graphics Acceleration
Solution:
Root Cause: DirectWrite and GPU Hardware Acceleration Rendering Lockup
Word utilizes hardware graphics acceleration to draw the Print Preview page canvas, text anti-aliasing, and embedded vector objects. When GPU display drivers experience DirectX/DirectWrite surface state desynchronization or TDR timeout failures during layout rasterization, Word's UI rendering thread crashes.
# Diagnostic Verification:
Event Viewer reports d2d1.dll or d3d11.dll as the faulting module during WINWORD.EXE print crashes.# Step-by-Step Fix:
Disable Hardware Acceleration in Word Options (If accessible):Open Word > click File > Options > Advanced.Scroll down to the Display section.Check Disable Hardware Graphics Acceleration (if present in your Office version).Force Disable Hardware Acceleration via Registry:Press Win + R, type regedit, and navigate to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Graphics
*(If Graphics key does not exist, right-click Common > New > Key and name it Graphics).*Right-click Graphics > New > DWORD (32-bit) Value.Name it DisableHardwareAcceleration and set its value to 1.Restart Word and verify printing.# Prevention & Long-Term Monitoring:
Refer to the official Microsoft Official Support Guide for details on Office graphics pipeline compatibility flags.
Disabling Conflicting Office COM Add-ins and Virtual Print Hooks
Solution:
Root Cause: Unhandled Exception in Third-Party COM Print Hooks
Third-party COM add-ins (such as Adobe Acrobat PDFMaker, FineReader, Abbyy, or custom document management plugins) hook into Word's internal print pipeline (FilePrint and FilePrintDefault commands). If a third-party add-in encounters a memory inspection fault during the print command event, it causes Word to crash before the print job is sent to the spooler.
# Diagnostic Verification:
Running winword.exe /safe prevents Word from crashing on print.# Step-by-Step Fix:
Access Add-ins Manager in Word:Open Word > click File > Options > Add-ins.Disable COM Add-ins:At the bottom of the window, set Manage: to COM Add-ins and click Go....Uncheck all non-Microsoft add-ins (e.g., Acrobat PDFMaker, FineReader).Click OK.Test Printing:Attempt to print a document. If successful, re-enable add-ins one by one to isolate the faulty plugin.# Prevention & Long-Term Monitoring:
Keep enterprise document management add-ins updated to versions certified for your active Microsoft 365 or Office release.
What spooler, port, or buffer error occurs when the actual print job is submitted?
- Print Spooler service (`spoolsv.exe`) crashes or stops running the moment the print job executes.
- Word crashes due to duplexing, finishing, or tray assignment driver settings conflicts.
- Word crashes when sending large documents to raw TCP/IP or WSD printer ports.
- Word crashes when printing to local virtual file drivers (e.g., PDF, XPS, OneNote).
Clearing Spooler Cache and Resetting `spoolsv.exe` Service Dependencies
Solution:
Root Cause: Windows Print Spooler (spoolsv.exe) Process Crash and Corrupted PRN Queue
When you click 'Print', Word generates a spool file (.SPL / .SHD) and transmits it to the Windows Print Spooler service (spoolsv.exe). If the System32\spool\PRINTERS cache directory contains leftover corrupted spool files from previous failed print jobs, or if a driver processor DLL (winprint.dll) throws a buffer overflow, spoolsv.exe terminates abruptly. Because Word loses its active RPC connection to the spooler mid-transfer, WINWORD.EXE crashes simultaneously.
# Diagnostic Verification:
Open PowerShell as Administrator and run: Get-Service -Name "Spooler"
Observe if Status shows Stopped immediately after Word crashes during a print attempt.# Step-by-Step Fix:
Stop Print Spooler and Clear Corrupted Spool Cache via PowerShell:Open PowerShell as Administrator and execute: Stop-Service -Name "Spooler" -Force
Remove-Item -Path "$env:SystemRoot\System32\spool\PRINTERS\*" -Force -Recurse -ErrorAction SilentlyContinue
Start-Service -Name "Spooler"
Re-register Core Print Spooler DLLs:Open Command Prompt as Administrator and execute: regsvr32.exe /s %systemroot%\System32\spool\drivers\w32x86\3\winspool.drv
Test Word Printing:Relaunch Word and attempt to print.# Prevention & Long-Term Monitoring:
Periodically purge stale spool files on print servers and workstations using automated cleanup maintenance scripts.
Resetting Printer Preferences and Duplex/Tray Finishing Profiles
Solution:
Root Cause: Incompatible Device Mode (DEVMODE) Structure in Printer Preferences
When Word submits a print job, it attaches a binary DEVMODE structure containing user preferences (duplex printing, staple, punch, paper tray, media type). If a printer driver update alters the offset addresses inside the DEVMODE structure, but Word reads cached legacy settings from the document header or driver defaults, memory corruption occurs during job compilation, crashing Word.
# Diagnostic Verification:
Word prints fine on 'Default Settings', but crashes instantly if you select 'Print on Both Sides' or choose a specific manual paper tray.# Step-by-Step Fix:
Open Printer Properties:Go to Settings > Bluetooth & devices > Printers & scanners > select your printer.Reset Printing Defaults:Click Printing preferences.Look for a Restore Defaults or Reset button at the bottom of the driver interface.Click Apply and OK.Re-configure Driver Preferences in Word:Open Word > click File > Print > click Printer Properties.Manually re-select duplexing or tray options and test printing.# Prevention & Long-Term Monitoring:
Reset printer driver default preferences following major Windows feature updates or driver version upgrades.
Converting WSD Ports to Standard TCP/IP Port Connections
Solution:
Root Cause: Web Services for Devices (WSD) Port Timeout and RPC Dropped Packets
Windows frequently connects network printers using WSD (Web Services for Devices) ports. WSD relies on dynamic UDP multicast discoveries (WS-Discovery). When network switches drop multicast packets or when high-density Word documents are streamed over a WSD port, the connection drops silently. Word waits for a TCP acknowledgment, times out, and suffers a RPC thread failure.
# Diagnostic Verification:
Open Printers & scanners > select printer > Printer properties > Ports tab.Check if the active port starts with WSD- instead of a static IP address.# Step-by-Step Fix:
Add Standard TCP/IP Port:In the Ports tab of Printer Properties, click Add Port....Select Standard TCP/IP Port > click New Port....Enter the static IP address of the network printer (e.g., 192.168.1.150).Uncheck Query the printer and automatically select the driver to use.Click Next and Finish.Apply Port and Test:Ensure the checkbox next to the new TCP/IP port is selected.Click Apply > click Close.Print from Word.# Prevention & Long-Term Monitoring:
Always assign static IP addresses and Standard TCP/IP ports to networked office printers.
Repairing XPS / PDF Virtual Printer Driver Components
Solution:
Root Cause: Corrupted Virtual Print Engine (Microsoft XPS Document Writer / PDF)
Virtual print drivers (Microsoft Print to PDF, Microsoft XPS Document Writer) use internal Windows OS subsystem components (mscms.dll, xpsservices.dll). If these core OS files are corrupted or turned off in Windows Features, printing to virtual drivers causes Word to crash immediately.
# Diagnostic Verification:
Printing to physical printers works, but selecting Microsoft Print to PDF or Microsoft XPS Document Writer causes Word to crash.# Step-by-Step Fix:
Re-enable Virtual Printing Features via PowerShell:Open PowerShell as Administrator and run: Disable-WindowsOptionalFeature -Online -FeatureName "Printing-PrintToPDFServices-Features" -NoRestart
Enable-WindowsOptionalFeature -Online -FeatureName "Printing-PrintToPDFServices-Features"
Run DISM and SFC Repair Commands:In administrative PowerShell, run: DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Relaunch Word and test PDF export/print.# Prevention & Long-Term Monitoring:
Use built-in Office 'Save As PDF' feature as a stable alternative to virtual print drivers when generating digital documents.
What document element or font formatting is triggering the print engine crash?
- A corrupted TrueType (`.ttf`) or OpenType (`.otf`) font file crashes GDI font rasterization.
- Embedded high-resolution images, transparent PNG layers, or EPS vector graphics crash driver memory.
- Track Changes, inline comments, or hidden document markup triggers Print Preview rendering errors.
- Corrupted document XML elements or damaged section breaks break page layout compilation.
Clearing Windows Font Cache (`FNTCACHE.DAT`) and Isolating Corrupted Fonts
Solution:
Root Cause: Corrupted TrueType/OpenType Font File or Font Cache Database
When Word prints, it calls the Windows GDI (Graphics Device Interface) text engine to rasterize fonts into printable glyph curves. If a document utilizes a custom or third-party .ttf or .otf font file with corrupted glyph tables or invalid header metrics, GDI encounters an unhandled exception (0xc0000094 integer divide by zero or heap corruption). The Windows Font Cache database (FNTCACHE.DAT) can also store corrupted font indices, causing crashes even on standard fonts like Arial or Calibri.
# Diagnostic Verification:
Select all text in the document (Ctrl + A), change the font to standard Calibri or Times New Roman, and attempt to print.If the document prints without crashing, a specific custom font used in the document is corrupted.# Step-by-Step Fix:
Stop Font Cache Services and Purge Database via PowerShell:Open PowerShell as Administrator and run: Stop-Service -Name "FontCache" -Force
Stop-Service -Name "FontCache3.0.0.0" -ErrorAction SilentlyContinue
Remove-Item -Path "$env:SystemRoot\System32\FNTCACHE.DAT" -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:LocalFolder\ServiceProfiles\LocalService\AppData\Local\FontCache\*" -Force -Recurse -ErrorAction SilentlyContinue
Start-Service -Name "FontCache"
Reinstall Corrupted Custom Fonts:Go to C:\Windows\Fonts.Locate and delete any recently installed third-party fonts.Download fresh, validated copies of the fonts from trusted foundries and reinstall them.Test Printing in Word.# Prevention & Long-Term Monitoring:
Avoid installing unverified web fonts or legacy 16-bit Type 1 PostScript fonts on modern workstations.
Configuring Print Graphics Draft Quality and Rasterization Settings
Solution:
Root Cause: PostScript/PCL Graphic Rasterization Memory Exhaustion
Documents containing high-DPI uncompressed images, transparent PNG overlays, or vector EPS graphics require massive memory allocations when converted into PostScript or PCL print streams. If the printer driver's rasterizer runs out of heap memory while processing complex graphic layers, the driver host process crashes, causing Word to close.
# Diagnostic Verification:
Creating a copy of the document and deleting all images allows the document to print cleanly.# Step-by-Step Fix:
Enable Draft Output Printing in Word:Open Word > click File > Options > Advanced.Scroll down to Print.Check Use draft quality.Click OK and test printing.Print Options Adjustment (Disable Background Printing):In File > Options > Advanced > under Print:Uncheck Print in background.*(Explanation: Forcing Word to print in the foreground prevents background thread memory contention.)*Compress Images in Document:Click any image in the document > Picture Format tab > Compress Pictures.Choose Print (220 ppi) > click OK > save document and print.# Prevention & Long-Term Monitoring:
Downsample mega-pixel camera images prior to inserting them into Word documents.
Configuring Document Markup and Track Changes Print Options
Solution:
Root Cause: Unresolved Document Revision Markup Rendering Overhead
When printing documents containing extensive Track Changes revisions, inline comment bubbles, or hidden metadata, Word switches its layout compiler to 'Print Document with Markup' mode. In heavy documents with hundreds of markup pointers, the side-margin bubble layout calculation engine can encounter a stack overflow, causing Word to crash during page layout generation.
# Diagnostic Verification:
Changing the print target setting from 'Print Document with Markup' to 'Print Document Showing Document Only' resolves the crash.# Step-by-Step Fix:
Modify Print Range Options in Word:Open Word > press Ctrl + P.Under Settings, click the dropdown that says Print All Pages or Print Markup.Uncheck Print Markup (change selection to Document instead of *Document showing markup*).Accept or Reject Revisions (Permanent Fix):Go to the Review tab in Word.Click Accept > select Accept All Changes and Stop Tracking.Save document under a new name and test printing.# Prevention & Long-Term Monitoring:
Accept or finalize document revisions before sending large collaborative contracts to print queues.
Performing 'Open and Repair' or Rebuilding OpenXML Document Structure
Solution:
Root Cause: Damaged OpenXML Structure or Section Break Schema Corruption
Over time, heavily edited documents acquire corrupted OpenXML elements (such as orphaned <w:sectPr> section break tags or malformed table properties). While Word's editing engine can render damaged XML on screen, the print rendering engine enforces strict OpenXML schema validation. When it hits an invalid XML tag during print stream compilation, Word crashes.
# Diagnostic Verification:
The document crashes Word on print across multiple different computers and different printers.# Step-by-Step Fix:
Execute Open and Repair in Word:Open Word > click File > Open > Browse.Select the corrupted document file (single-click, do not double-click).Click the small arrow next to the Open button > select Open and Repair.Rebuild Document via Copying Uncorrupted Contents:Create a fresh, blank Word document (Ctrl + N).In the corrupted document, select all content EXCEPT the very last paragraph mark (Ctrl + A, then hold Shift and press Left Arrow).Copy (Ctrl + C) and paste (Ctrl + V) into the new document.*(Explanation: The final paragraph mark in Word stores section and document-level formatting schemas; excluding it strips structural XML corruption.)*Save new document and test printing.# Prevention & Long-Term Monitoring:
Avoid copying and pasting text directly between different legacy .doc and modern .docx file formats without clearing formatting.
What network protocol, print server, or enterprise domain policy is failing?
- Point and Print Group Policy restrictions block driver payload execution from print server.
- RPC over Named Pipes authentication or RPC sealing requirements (KB5005652) drop print calls.
- Universal Print cloud service or Azure AD identity mapping fails during job submission.
- User profile disk or redirected AppData folder permission locks block local print spool creation.
Configuring Point and Print Group Policy Restrictions and Driver Isolation
Solution:
Root Cause: Point and Print Security Hardening and Unisolated Driver Crashes
Following security patches for PrintNightmare (KB5005652), Windows enforces administrative credential prompts for Point and Print driver installations. If an enterprise print server attempts to push an unverified or unsigned print driver update to a client machine while Word is submitting a print job, the driver download fails silently, causing the local spooler RPC connection to drop and Word to crash.
# Diagnostic Verification:
Connecting directly to a locally attached USB printer works, but printing to shared network queues (\\PrintServer\QueueName) crashes Word.# Step-by-Step Fix:
Enable Driver Isolation on Print Server / Local Machine:Press Win + R, type printmanagement.msc, and hit Enter.Go to All Drivers.Right-click your shared printer driver > select Set Driver Isolation > choose Isolated.*(Explanation: Driver Isolation forces the printer driver to execute in a separate process (PrintIsolationHost.exe) so a driver crash will not crash WINWORD.EXE.)*Configure Point and Print Policy via GPO:Open gpedit.msc > go to Computer Configuration > Administrative Templates > Printers.Open Point and Print Restrictions.Set to Enabled and check Users can only point and print to these servers (enter your server FQDNs).Set security prompts to Do not show warning or elevation prompt for trusted servers.Run gpupdate /force in Command Prompt.# Prevention & Long-Term Monitoring:
Always configure enterprise print drivers in 'Isolated' or 'Shared' driver isolation modes.
Resolving RPC Connection Sealing and Pipe Authentication Hardening
Solution:
Root Cause: RPC Listener Sealing and Named Pipe Authentication Drop
Modern Windows RPC security hardening mandates RPC Sealing (rpc_c_authn_level_pkt_privacy) for print spooler communication between client machines and print servers. If a legacy print server or domain controller does not support RPC packet privacy, the spooler RPC port (ncacn_np) closes the socket abruptly during Word's spool transmission, triggering a fatal C++ exception in Word.
# Diagnostic Verification:
System Event Log displays Event ID 37 or 40 from source PrintSpooler stating *The server spooler failed to establish an RPC connection*.# Step-by-Step Fix:
Verify RPC Connection Registry Keys on Client:Open regedit and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
Ensure RpcAuthnLevelPrivacyEnabled is set to 1 (or set to 0 temporarily in controlled test environments to verify protocol mismatch).Force RPC over TCP Connection Protocol:Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC.Create a DWORD named RpcUseNamedPipesOnProtocol and set Value to 1.Restart Print Spooler Service via PowerShell:Restart-Service -Name "Spooler" -Force# Prevention & Long-Term Monitoring:
Ensure all domain print servers run updated Windows Server builds supporting secure RPC packet privacy.
Re-authenticating Microsoft Universal Print Cloud Service Tokens
Solution:
Root Cause: Expired Entra ID (Azure AD) OAuth Token in Universal Print Client
Organizations utilizing Microsoft Universal Print route print jobs over HTTPS cloud endpoints (global.print.microsoft.com). If the user's Entra ID OAuth 2.0 refresh token expires or suffers Web Account Manager (WAM) broker corruption, the Universal Print virtual driver fails to negotiate the TLS handshake when Word submits the job, crashing Word's print thread.
# Diagnostic Verification:
Printing via local desktop applications fails, but printing via Word Web App (Microsoft 365 browser) to Universal Print succeeds.# Step-by-Step Fix:
Re-authenticate User Session in Windows Settings:Press Win + I > Accounts > Access work or school.Select your corporate account > click Info > scroll down and click Sync.Remove and Re-add Universal Printer:Go to Settings > Bluetooth & devices > Printers & scanners.Select the Universal Print printer > click Remove.Click Add device > re-select the Universal Print queue from the cloud directory.Relaunch Word and test printing.# Prevention & Long-Term Monitoring:
Maintain active Primary Refresh Tokens (PRT) on domain-joined devices using dsregcmd /status.
Fixing Redirected AppData Folder Permissions for Temp Print Files
Solution:
Root Cause: Access Denied on Temporary Spool Directory in Redirected User Profiles
In enterprise environments utilizing Folder Redirection or Roaming Profiles, Word attempts to create temporary EMF/XPS spool files inside %localappdata%\Temp or %userprofile%\AppData\Local\Microsoft\Windows\INetCache. If SMB share permissions or offline file sync locks prevent Word from writing temporary spool files to the redirected profile path, Word crashes with an access violation error.
# Diagnostic Verification:
Logging into the workstation with a local Administrator account resolves the Word print crash.# Step-by-Step Fix:
Reset User Temp Directory Permissions via PowerShell:Open PowerShell as Administrator and run: icacls "$env:USERPROFILE\AppData\Local\Temp" /grant "$env:USERNAME:(OI)(CI)F" /t
Redirect Temp Variable to Local C: Drive:Press Win + R, type sysdm.cpl, and hit Enter.Go to the Advanced tab > click Environment Variables.Under User variables for [Username], edit TEMP and TMP to point to a local directory: C:\Temp.Ensure C:\Temp exists and has Full Control permissions for the user account.Restart Word and test printing.# Prevention & Long-Term Monitoring:
Keep %localappdata%\Temp directories on local physical drives rather than redirected network shares.