"Microsoft Word has stopped working" when I close the program

Anonymous
2013-03-10T02:28:28+00:00

I installed Office 2013. 

All programs launch and work OK.

When I close Excel and Word, I get a message that "Microsoft Word has stopped working."

Word then looks for a solution.

Sometimes it restarts, sometimes it shuts down.

Outlook sometimes shuts down while open.

I then get a message that "Microsoft Outlook has stopped working,"

Outlook then looks for a solution.

Sometimes it restarts, sometimes it shuts down.

I have disabled all add ons. I have uninstalled and re-installed 2013.

What do I try next?

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-04-09T13:50:57+00:00

I called Microsoft technical support (800-642-7676).

The friendly technician tracked the problem to a conflict with a NVIDIA driver from my video card.

The offending driver was: NVWGF2UM.DLL

The technician renamed it: NVWGF2UM.old

She left everything else the same.

I am still using the PNY NVIDIA GeForce 210 Graphic Card in Windows 7 pro and I am having no problem with any program in the Office 2013 suite.

She found the problem driver in the event log.

But do not install any future video card driver updates. The offending driver will be reinstalled.

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments

58 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-11-13T16:47:58+00:00

    ROBERTCWRIGHT  ABOVE IS A SPAMMER. DO NOT CALL THAT NUMBER, IT IS NOT MICROSOFT. HE WILL TRY TO GET YOUR INFO AND GET INTO YOUR PC. DO NOT CALL THAT PHONE #.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-09-17T09:42:09+00:00

    In a mixed vendor environment the much used tactic when errors are occurring is: "Blame it on the other".

    But reality is more often: the crashing main program has an unhandled condition and is not recovering in a decent manner from that condition.

    Blaming it on an other vendor is easier than making a slight change in your own code.

    The vendor of the crashing (called) module is dodging the bullet with: "You're calling my module with an incomplete environment. Or your parameter list is invalid. Or the product is end of life".

    A program like Word should not crash on a driver or other external program. If you're using it you're responsible. The only two exeptions are:

    • the external module results in an unrecoverable error in the kernel presenting you with a nice BSOD
    • you're program has  the possibility of third party add-ons which can ruin your environment. Not wise to give them that chance, but nevertheless.

    Was this answer helpful?

    0 comments No comments