none
Word 2010 crashing because of msvcr90.dll

    Question

  • Hello,

    We have recently deployed Office 2010 to all workstations in my company. On one workstation, Word crashes regularly, without an identifiable action triggering it so far. What the event viewer is telling me:

    • Event Type: Error
    • Event Source: Microsoft Office 14
    • Event Category: None
    • Event ID: 1000
    • Date: 02/08/2011
    • Time: 09:39:04
    • User: N/A
    • Computer: LUCYPORT
    • Description: Faulting application winword.exe, version 14.0.6024.1000, stamp 4d83e310, faulting module msvcr90.dll, version 9.0.30729.4148, stamp 4a594c79, debug? 0, fault address 0x000320f0

    I have looked on various forums but have been unable to find a solution so far. Office 2010 has been updated to SP1 + latest updates.

    Thank you.


    Rémi
    Tuesday, August 02, 2011 9:30 AM

Answers

  • Hi,

    Since the problem isn't happening anymore, it looks like uninstalling the old Works converter did the trick after all. Thanks for your help.


    Rémi
    • Marked as answer by Remi Kaupp Thursday, August 11, 2011 8:28 AM
    Thursday, August 11, 2011 8:28 AM

All replies

  • It could be possible that this file is broken. First identify, which of the many possible locations of this dll is used on your system. Use Process Explorer and press Ctrl-D - look in the lower pane and identify the path. It could be something like

    C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll

    If you like you can do a binary compare of msvcr90.dll from another system: fc /B c:\temp\msvcr90.dll c:\temp\othersystem_msvcr90.dll

    If the files are identical, then there must be another reason for the crash. We need a user dump to proceed and identify the cause. Use Procdump from 

    http://technet.microsoft.com/en-us/sysinternals/dd996900 and run

    procdump -e winword.exe c:\winword.dmp

    Start Word before you issue the command and let procdump run in the background until the crash happens.


    If the files are different, try to reinstall the "Microsoft Visual C++ 2008 SP1 Redistributable Package" and apply Windowsupdate again. You could even try sfc /scannow, but I'm not sure if the file is included in the check. At least the scanfile command failed in my test.
    You can try to replace the file manually, but it requires some additional effort to circumvent the TrustedInstaller protection: Make sure, the file is not in use (Safe Mode), take ownership, add full permissions, ... (see http://helpdeskgeek.com/windows-7/windows-7-how-to-delete-files-protected-by-trustedinstaller/)

     

    Tuesday, August 02, 2011 11:31 AM
  • Thank you. BEfore seeing your message, I uninstalled the "Microsfot Works 6-9 converter" (which should have been removed before as it is not compatible with Office 2010), rebooted, and the problem hasn't occurred since then. However since the issue can't be reproduced exactly it may still be a coincidence. If it does occur again I will have a look at your solution.

    Thank you for your time!


    Rémi
    Wednesday, August 03, 2011 10:36 AM
  • Hi,

     

    Re-installing does not usually fix anything.

    See the KnowledgeBase article "How to troubleshoot problems that occur when you start or use Word 2010, Word 2007, Word 2003, or Word 2002" at:

    http://support.microsoft.com/default.aspx/kb/921541?p=1

    http://office-2010.iyogi.com/microsoft-word-2010/word-2010-crashes.html

     

    Hope this information helps you.

     

    Thursday, August 11, 2011 6:46 AM
  • Hi,

    Since the problem isn't happening anymore, it looks like uninstalling the old Works converter did the trick after all. Thanks for your help.


    Rémi
    • Marked as answer by Remi Kaupp Thursday, August 11, 2011 8:28 AM
    Thursday, August 11, 2011 8:28 AM
  • another reason why every single office 2010 application will crash with the msvcr90.dll eventlog entry is the April 2017 security patch KB3141538
    • Proposed as answer by coop5885 Monday, April 17, 2017 6:41 PM
    Monday, April 17, 2017 2:51 PM
  • Removing this update worked for me.  Thank you for replying to a 6 year old thread today with this!
    Monday, April 17, 2017 6:42 PM
  • Re-install MS Office is not worked.

    Remove the patch KB3141538 is worked for me.
    Windows Server 2003R2 SP2, MS Office Professional Plus 2010.

    Thank you so much!!!

    Tuesday, April 18, 2017 12:47 PM
  • Just wanted to give you a big THANKS for sharing this.

    Have been searching hours for a customer who ran into this problem.

    Great that you decided to share it with others!

    Thursday, April 20, 2017 1:25 PM
  • thank you! saved me :)

     KB3141538 is bad for you!

    Saturday, April 22, 2017 5:18 AM
  • Thank you very much for your help. Removing this update worked for me too.
    Tuesday, April 25, 2017 7:11 AM
  • Thank you so much , removing that patch worked for me
    Monday, May 08, 2017 11:29 AM
  • I had previously fixed this issue by removing KB3141538, but the error came back today May 11th, 2017.  

    After working on it for several hours, I was able to determine that the May 9th security update KB3191899 also causes this issue.  You may need to remove it as well to resolve it. 

    • Proposed as answer by Fabio75 Wednesday, May 24, 2017 5:33 PM
    Friday, May 12, 2017 3:26 PM
  • Thank you for sharing your experience with this. Could you please indicate what your OS is, is it Win 2003 R2 SP2 by any chance? I am encountering this right now with Win 2003 R2 SP2, hoping it does not cause same effect in Win 7 or higher...

    Thanks!

    Saturday, May 13, 2017 5:10 PM
  • I had previously fixed this issue by removing KB3141538, but the error came back today May 11th, 2017.  

    After working on it for several hours, I was able to determine that the May 9th security update KB3191899 also causes this issue.  You may need to remove it as well to resolve it. 

    Update KB3191899 is superseded by KB3203460... guess what!
    • Proposed as answer by Fabio75 Wednesday, June 14, 2017 9:16 PM
    Wednesday, June 14, 2017 9:11 PM
  • Same problem here. Thanks for yiour Tips. Removing KB320346 works. But is there also a final solution?
    Friday, June 16, 2017 2:43 PM
  • Same problem here. Thanks for yiour Tips. Removing KB320346 works. But is there also a final solution?
    if you are using WSUS you can decline that update. Doing so all next superseding updates will be declined too (check your automatic approval rules).
    Friday, June 16, 2017 3:49 PM
  • I have had this issue pop up again on a server 2003. Removing KB3213624 was the new fix.

    https://support.microsoft.com/en-us/help/3213624
    • Edited by Jacob McCredie Monday, July 31, 2017 10:10 PM Updated Link
    • Proposed as answer by RECSupport Friday, August 11, 2017 6:50 AM
    Monday, July 31, 2017 8:24 PM
  • Thanks Jacob, removing KB3213624 also worked for me on a server 2003 R2 machine.
    Friday, August 11, 2017 6:53 AM
  • Feels strange that I´m following this old thread, but it is a must when you are running Office2010 on a 2003 server that I´m still have to do :D

    Thanks to you all!

    /Bengt


    • Edited by Beng123456 Friday, August 18, 2017 8:03 AM
    Friday, August 18, 2017 8:03 AM