Microsoft Word crashing — mid-document, on startup, when saving, or when opening a specific file — is disruptive enough to stop work entirely. The right fix depends heavily on when it crashes, so the pattern matters before trying anything. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Crashes on a specific document only: the document itself is likely corrupted. Open a blank document first — if that works fine, the file is the problem. Fix 5.
Crashes immediately on startup: add-ins or a corrupted Normal.dotm template. Safe Mode test (Fix 1) takes 30 seconds and tells you immediately which it is.
Crashes during saving: usually a location issue (OneDrive sync conflict, network drive problem) or disk issue. Fix 3.
Started crashing after a Word update or Office update: update rollback or Office Repair. Fix 4.
Fix 1: Safe Mode test — first and fastest
Hold Ctrl → click the Word icon. Word launches in Safe Mode, disabling all add-ins and using a minimal template. If Word works normally in Safe Mode: add-ins or the Normal.dotm template are causing the crashes. If it still crashes in Safe Mode: the problem is deeper — Office installation, a specific file, or Windows system files.
Safe Mode confirmed as stable → go to Fix 2 (add-ins) or reset Normal.dotm.
Fix 2: Add-ins
File → Options → Add-ins → at the bottom, Manage: COM Add-ins → Go → uncheck all → OK → restart Word normally. If Word is now stable: re-enable add-ins one at a time, restarting after each. The add-in that causes a crash when enabled is the culprit — remove it or check for an update from the publisher.
Common crash-causing add-ins: older Acrobat PDFMaker, Grammarly, DocuSign, MathType (older versions), and various CRM and productivity integrations. These are typically safe to disable if you don’t actively use them during sessions.
Fix 3: Normal.dotm template reset
Normal.dotm is Word’s default template — every new document inherits its settings. When this file becomes corrupted: Word behaves erratically, crashes on startup, or hangs when creating new documents.
Close Word. Navigate to %appdata%MicrosoftTemplates → rename Normal.dotm to Normal.dotm.old. Reopen Word. It creates a fresh Normal.dotm from defaults. If crashes stop: the old template was corrupted. Your custom styles from the old template are gone — you’d need to recreate them from the .old file if needed.
Fix 4: Office Repair
Settings → Apps → Microsoft 365 or Microsoft Office → Modify → Quick Repair first. Quick Repair takes 5 minutes and fixes most installation corruption. If crashes continue: Online Repair (same path). Online Repair takes 20–45 minutes but completely reinstalls Office components, resolving corruption that Quick Repair misses.
Don’t skip Quick Repair to go directly to Online Repair — Quick Repair resolves the majority of crash-causing installation issues in a fraction of the time.
Fix 5: Corrupted specific document
If only one document causes crashes: try recovering it. Word → File → Open → Browse → select the document → click the dropdown arrow next to “Open” → “Open and Repair.” This runs Word’s built-in document recovery, which fixes many types of file corruption.
If that fails: copy all content out of the corrupted document by opening it on a different machine (or an older Word version), selecting everything (Ctrl+A), and pasting into a fresh blank document. The content usually survives even when the file format has issues. Another approach: change the file extension from .docx to .zip, extract it, and inspect the XML files inside — Word documents are ZIP archives, and often only one XML component is corrupted, which can be edited directly.
Fix 6: Windows file system check
If Word crashes during save operations specifically — especially on a slow or older drive — disk errors may be corrupting the save operation. Administrator Command Prompt:
chkdsk C: /f /rSchedule on next restart → restart. This scans the system drive for file system errors. Also check drive health with CrystalDiskInfo — S.M.A.R.T. warnings on the drive explain save-related crashes that persist through all Office fixes.
Word and OneDrive sync conflicts
AutoSave in Word (when a document is saved to OneDrive or SharePoint) triggers continuous sync operations. When the OneDrive client has sync issues — quota exceeded, sync conflict on the same file, sync paused — AutoSave fails and Word often crashes rather than gracefully handling the save failure.
Check the OneDrive taskbar icon for any sync errors (red X, warning badge) before opening documents stored on OneDrive. Resolve any sync conflicts, ensure there’s storage headroom, and pause/resume OneDrive sync if it’s in a broken state. Alternatively: save the document locally (File → Save As → This PC) and copy to OneDrive after the session to bypass the sync-during-editing path.
Graphics and hardware acceleration
File → Options → Advanced → Display → check “Disable hardware graphics acceleration.” Word uses GPU acceleration for document rendering. On machines with GPU driver issues (same driver problems that affect Chrome and Edge rendering), Word crashes specifically when rendering complex layouts, tables with many columns, or images.
Disabling hardware acceleration forces CPU rendering — slower for complex documents but stable. Update the GPU driver from the manufacturer’s website and re-enable acceleration after updating.
Our guide on Microsoft Office performance issues covers the add-in conflict diagnostics and Office repair process that apply across the Microsoft 365 suite. For OneDrive sync problems that cause save failures in all Office apps, our OneDrive troubleshooting guide covers the sync conflict and quota diagnostics. Microsoft’s Word crash diagnostics covers the crash report collection through the Office Feedback Hub and the Support and Recovery Assistant (SaRA) tool that automates many of the diagnostic steps above.
Antivirus and macro security
Security software that scans Office macros or monitors file access during document operations can cause Word to crash when the scan takes too long and Word’s save timeout is exceeded. This is more common with documents that contain many macros, embedded objects, or complex field codes.
Add the Word installation folder (C:Program FilesMicrosoft OfficerootOffice16) and the Documents folder to the antivirus exclusion list. This prevents real-time scanning from interfering with Word’s file operations. The trade-off is reduced real-time scanning of Office files — mitigated by keeping Office and Windows security updates current.
Print driver and Word crashes
Word communicates with the default printer on startup to get page size and margin information. When the default printer driver is corrupted or the printer is unavailable (a network printer that’s offline): Word sometimes crashes or hangs during this initial printer query.
Test: change the default printer to “Microsoft Print to PDF” (which is always available locally regardless of network state) → reopen Word. If crashes stop: the previous default printer’s driver was causing the issue. Update or reinstall that printer’s driver, then restore it as the default.
Word and third-party fonts
A corrupted font that’s installed system-wide can crash Word when that font is used in a document or when Word loads the font for its UI. Word loads all available fonts on startup, and a corrupted font in that list causes an early crash that looks like a startup failure.
Control Panel → Fonts → look for recently installed fonts. Remove any unusual or recently installed fonts and test Word. Fonts from third-party sources are particularly susceptible to corruption during download — official font sources (Google Fonts, Adobe Fonts, system fonts) are generally safe.
32-bit vs 64-bit Office
Office installs as 32-bit by default even on 64-bit Windows systems. Older add-ins that are only available as 32-bit DLLs work with 32-bit Office but not 64-bit. If the 64-bit version of Office was installed and add-ins from older software are loading incompatible 32-bit components: Word crashes when those components load.
Check: File → Account → About Word → version line shows (32-bit) or (64-bit). If 64-bit and crashes are add-in related with no compatible 64-bit version available: switching to 32-bit Office (via Office installer with the right option selected) resolves the compatibility issue. Most users can’t tell the difference in daily use.
Event Viewer for crash details
Event Viewer → Windows Logs → Application → look for “Application Error” entries with winword.exe as the faulting application. The “Faulting module name” in these entries is the most specific diagnostic available: if it’s wwlib.dll → Word core corruption (Office Repair). If it’s a third-party DLL (grammarly.dll, acrobat.dll) → that add-in. If it’s ntdll.dll or a Windows system DLL → Windows system files (SFC /scannow).
This 5-minute Event Viewer check is more informative than almost any other diagnostic step because it directly names what crashed. Providing the faulting module name to Microsoft Support or the add-in publisher immediately tells them where to look.
Protected View and crashes when opening files
Files from email attachments, internet downloads, or network locations open in Protected View by default. Protected View uses a sandboxed renderer that’s separate from the main Word process. Some documents crash Protected View but work correctly when clicked through to edit mode.
File → Options → Trust Center → Trust Center Settings → Protected View → review the three Protected View checkboxes. For trusted locations: add them to the Trusted Locations list (Trust Center → Trusted Locations → Add new location) so files from those paths skip Protected View entirely. This reduces the number of Protected View crashes without completely disabling the security feature.
Word crashes on spell-check or autocorrect
Corrupted autocorrect or custom dictionary files cause Word to crash specifically when spell-check runs or when autocorrect triggers on typed text. Navigate to %appdata%MicrosoftOffice → look for .acl (autocorrect) and .dic (custom dictionary) files → rename them to .old to force Word to create fresh ones. The custom dictionary contains manually added words that won’t be retained until re-added, which is a minor inconvenience versus Word consistently crashing on text input.
Large document performance and crashes
Documents over 100MB, or documents with hundreds of tracked changes, thousands of comment bubbles, or dozens of embedded high-resolution images can exceed Word’s memory limits on machines with 8 GB or less. Word doesn’t gracefully handle running out of memory — it crashes rather than showing a low memory warning in most cases.
For large documents: close all other applications before working on them. Accept or reject tracked changes rather than accumulating them indefinitely (every tracked change requires extra memory for the revision history). For heavily-imaged documents: compress images (Picture Tools → Format → Compress Pictures → E-mail 96 ppi) to reduce document size without visible quality loss for screen viewing.
The most important diagnosis question is simply: when does it crash? The “when” narrows the cause to one of a small number of possibilities. Startup crash → Normal.dotm or add-in. Specific document → that file’s corruption. During save → OneDrive or disk issue. Spell-check → autocorrect file. This pattern-based approach gets to the right fix without working through all options sequentially.
For organisations deploying Microsoft 365 at scale: Word crashes across multiple machines simultaneously almost always indicate either a problematic Office update that was just deployed, a Group Policy configuration that’s incompatible with the current Office version, or a recently pushed add-in with a bug. The Microsoft 365 admin centre’s Service Health dashboard and the Office client event logs aggregated through Microsoft Endpoint Manager show crash patterns that would be invisible at the individual machine level — a single user reporting Word crashes is an individual problem; 20 users reporting the same crash the morning after an update is an infrastructure problem that IT needs to address at the deployment level.
Reinstalling Word vs full Office reinstall
Individual Office components (Word specifically) can’t be reinstalled independently through the standard Settings interface — Office reinstalls as a suite. However, using the Office Deployment Tool (downloadable from Microsoft) allows deploying or repairing individual applications. For IT administrators: this is the path to reinstalling Word specifically when the rest of Office is working correctly and a full suite reinstall would be unnecessarily disruptive.
For individual users: the Quick Repair → Online Repair → full uninstall and reinstall sequence achieves the same result through a simpler path. The Microsoft Support and Recovery Assistant (SaRA — downloadable from Microsoft’s support site) automates the uninstall and reinstall process, handling the registry cleanup and file removal that manual uninstalls sometimes miss, giving a truly clean installation.
One practical note on document recovery: always enable AutoRecover (File → Options → Save → keep “Save AutoRecover information every X minutes” checked, set to 5 minutes or less). AutoRecover doesn’t prevent crashes but ensures you lose at most 5 minutes of work when one happens. The AutoRecover file location (also in File → Options → Save) shows where Word stores the recovery files — knowing this location means you can manually retrieve a recovery file if Word’s automatic recovery dialog doesn’t appear after a crash. You might also run into Microsoft Word Keeps Crashing.
