Word crashes when I try to add a custom dictionary

When I try to add or create a new custom dictionary or create a new custom dictionary, Word crashes. I've tried:

1. Creating a new custom dictionary from the Custom Dictionaries window. Word crashes after I click New.

2. Adding a new custom dictionary .txtfile to the UProof folder. When I try to add it from the Custom Dictionaries window, Word crashes.

I've tried:

1. Updating Office365

2. Repairing Office365

3. Reinstalling Office365

|

Hello Mezzofan

 

Thank you for your contribution to the Microsoft Community.

 

I understand that you want to add a custom dictionary but Word crashes. This must have caused problems in your life and work.

 

First, I need to confirm some information:

  • The version of Word you are using. File>Account. Please provide a screenshot if it is convenient.

  • You mentioned that Word crashed. Is there an error message? Is there a record in the Event Viewer? Please provide a screenshot if it is convenient.

  • Does this problem only occur in this one file? or does it occur in all Word files? Please create a new file to test.

 

Here's a tutorial for adding a custom dictionary:

Add or edit words in a spell check dictionary - Microsoft Support

You have tried to fix or even reinstall Microsoft 365. I will give some other scenarios:

  • Cancel the add-on

    Click the file > option in the upper left corner of the document> change the place where Add-ons > Management to COM Add-ins> then select "Go", uncheck all add-ins > click OK > restart the word document and see the effect.

  • Delete the Word template

    Close all documents, press Windows + R, type %AppData%MicrosoftTemplates in the run box that opens, press enter,

    Back up and delete files with .dotm suffix, such as Normal.dotm, and then reopen the word document attempt

  • Registry reset Office

    Press Windows + R, type regedit in the run box that opens, press enter,

    Rename the Office folder by navigating to the following key (right-click on it and select Rename, e.g. Rename Office to Officeold)

    HKEY_CURRENT_USER\Software\Microsoft\Office

    Then reopen the word document to try the effect.

Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click here to view the article.

How to back up and restore the registry in Windows - Microsoft Support

If there is a mistake in my understanding, please describe it in more detail. Looking forward to your further reply so that we can serve you better.

 

Best wishes, 

  

Rel - MSFT | Microsoft Community Support Specialist

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Many thanks for your response and suggestions.

Info you requested:

1. Word Version: Microsoft Word for Microsoft 365 MSO (Version 2403 Build 16.017425.20176) 64-bit.

2. No error messages when it crashes; it just closes then restarts. Event viewer log data pasted below.

3. The problem occurs in all tested existing files and in new blank file.

What I tried, per your suggestions:

A. Tried cancelling all add-ons -- no change.

B. Tried deleting templates -- no change

C. Tried renaming the Office registry entry to "Officeold" and restarting Word -- no change.

EVENT VIEWER LOG

Log Name: Application Source: Application Error Date: 5/5/2024 2:10:09 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: D****S\m****o Computer: D****S Description: Faulting application name: WINWORD.EXE, version: 16.0.17425.20176, time stamp: 0x6610b4cd Faulting module name: mso.dll, version: 0.0.0.0, time stamp: 0x6610b248 Exception code: 0xc0000005 Fault offset: 0x00000000012e26a9 Faulting process id: 0x0x57B4 Faulting application start time: 0x0x1DA9F21C9B618CE Faulting application path: C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso.dll Report Id: c1ceead3-b91f-4912-ad2d-63e5a02b1842 Faulting package full name: Faulting package-relative application ID: Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 1000 0 2 100 0 0x8000000000000000 13586 Application D****S WINWORD.EXE 16.0.17425.20176 6610b4cd mso.dll 0.0.0.0 6610b248 c0000005 00000000012e26a9 0x57b4 0x1da9f21c9b618ce C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE C:\Program Files\Common Files\Microsoft Shared\Office16\mso.dll c1ceead3-b91f-4912-ad2d-63e5a02b1842

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Mezzofan

 

Thank you for your reply.

 

I noticed that you are experiencing an error message 0xc0000005. This means that the application is trying to access an invalid or forbidden location in memory.

Also, the mso.dll file is a very important file that is part of Microsoft Office and Microsoft Visual Studio.

I understand that sometimes troubleshooting can be a bit time-consuming and the fact that the issue is still not resolved is frustrating. However, by performing the previous steps, we have already eliminated some possible causes of the problem and we are getting closer to a solution. Your continued patience and cooperation are highly appreciated. To troubleshoot our issue further, let's perform the following steps:  

  • How to perform a clean boot in Windows - Microsoft Support

    Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background program is interfering with your game or program and to isolate the cause of a problem. 

    These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get you back on track.

  

Rel - MSFT | Microsoft Community Support Specialist

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated May 16, 2024 Views 35 Applies to: