- winword.exe/ntdll.dll (or oleaut32.dll, gdi32.dll
Basically, it appears that any member of the Office family of applications may show up in this event. As a precaution, you may (re)install the latest service pack for Microsoft Office but sometimes this type of error may indicate a conflict with another application.
From a newsgroup post: "Your problem may be a conflict with the Norton Office Plug-in. But see the "Problems opening Word" link for some troubleshooting tips that also apply to problems closing Word."
From a newsgroup post: "Run the update from the Microsoft Office XP site (http://office.microsoft.com/Downloads/default.aspx). I had frequent crashes in Outlook 2002, went to the update site and found crucial updates posted there for Outlook and for Word. Since I downloaded those updates I haven't had a crash in those programs."
I fixed the problem by creating a new User Profile.
1. Save Files in your User Profile
2. Create a Backup of the User Profile by the "Copy To" function in the User Profiles Menu (only for worst case)
3. Deleting the User Profile with an Administrator Account
4. Logon with the deleted Profilename
Other solutions like analyse the Word crash with MS Process Monitor didn't work in my case.
The fix i used was this:
- Make sure Outlook is closed.
- Go to the folder c:\documents and settings\%username%\applicaiton data\microsoft\outlook. Replace %username% accordingly.
- Create a new folder and move all files from this folder into it (for backup).
- Open outlook again and test.
Application: Word 2010, module: btmofficea.dll - I went in to File, Options, Add-ins. Set manage to com addins and clicked Go. Highlighted the Bluetooth module and clicked Remove. Word is now working just fine.
The problem for me was with Word's default template. If fixed by following these steps:
1. Close Word.
2. Rename %appdata%\Microsoft\Templates\Normal.dot to Normal.dot.old.
3. Re-open Word, error should be gone.
For me an simply deleting (or renaming) the default template file (i.e. Normal.dot for Word) solved that problem. Word recreated it at next start and worked fine since then. Normal.dot can be found in the user's profile\Application Data\Microsoft\Templates.
In my case, Word was the culprit. Download ProcessMonitor from Microsoft (was from Sysinternals) and run it on your PC. Create a filter in process monitor to ONLY show you system activity for WinWord.exe. Now, open Word and at the point where it crashes have a look at ProcessMonitor and you will see the file that it was trying to access when it crashed. If Word gives you an message that it cannot start, DO NOT click on OK until after you have looked at ProcessMonitor. For me, the problem ended up being a file in C:\Windows\System32\spool\drivers\w32x86\3. It was a file related to a Xerox Printer. After deleting the printer and that file Word worked fine.
If this occurs with Excel and the message is regarding the mso.dll file, you may want to try deleting the user's *.xlb files. These files contain information that has to do with the user's toolbar customization and they are not so important and will be recreated automatically. They are stored in c:\documents and settings\%username%\application data\microsoft\excel\. Make back-ups just in case.
- Application: winword.exe, module: mso.dll - On our desktops, but more frequently on Citrix utilizing Hummingbird DM 5.1 and Word XP SP3, we had frequent user crashes with this event being logged. There are two Office XP Post-SP3 hotfixes released to fix winword.exe and mso.dll. Both of them are described in Microsoft article ME871240
. It is important to note these will not show up on the Office update page and you have to call Microsoft to get them. There are some other issues resolved by these hotfixes, not related to document management systems.
- Application: winword.exe, module: hpbafd32.dll - According to ME330903
, this issue occurs because of a problem with the HP printer drivers. Install newer drivers to replace the hpbafd32.dll file.
- Application: msaccess.exe, module: vbe6.dll - From a newsgroup post: "One of our developers noticed that we had gotten angled quotation mark characters rather than the typical straight apostrophe as a string delimiter. We aren't quite sure how this happened, but once this was corrected, things seemed to start working correctly".
In our case, a client called with this problem. After deleting the "normal.dot" file, the problem was solved. See the link to "Normal.dot Template Explained" for information about the "normal.dot" file.
This event appeared also in our organization. In our case, there was a “.dll” file namely msgrnl32.dll version 220.127.116.11 that was erratic. This is the Dutch grammar dll from Polderland Language & Speech Technology. Replacing this version with an older one (18.104.22.168 from Lernout & Houspie) was the solution. Microsoft addressed this issue in ME329289
, but the workaround did not work for us.
In my case, this error was due to the Add-In "Plaxo". Remove the Add In from Outlook Client by going to Tools -> Options -> Other Tab -> Advanced Options -> Add Ins and uncheck then remove the Plaxo application.
See the link to "EventID 1000 from source MicrosoftOffice10" for information regarding this event.
I received this error after changing the security settings to restrict access to the C: drive on a limited user profile on Win XP Pro. I had removed the Users and Everyone group from the ACL. After adding back the Users group with default permissions, the problem was resolved.
Outlook would open just fine, just not Excel or Word. We updated all the MS Small Business Edition Office software, and that didn't provide a fix. We finally had to uninstall Norton S.W. 2003 (including NAV). We followed it with a new install of Symantec Corporate Anti-Virus v 8.1. Now the Office software runs fine.
It turned out to be the fact that the default printer was a paperport printer from Visioneer. See Microsoft Knowledge Base Article ME323124