Microsoft Word 2013 has stopped working

Anonymous
2013-02-17T08:24:10+00:00

Whenever I try to open Word 2013 (safe mode is working fine), it says Word 2013 has stopped working. All other Office 2013 are working correctly.

Here's the event log:

Faulting application name: WINWORD.EXE, version: 15.0.4454.1504, time stamp: 0x50be98da

Faulting module name: btmofficea.dll, version: 1.0.0.49, time stamp: 0x4d382a1a

Exception code: 0xc0000005

Fault offset: 0x00000000000065ff

Faulting process id: 0x1318

Faulting application start time: 0x01ce0ce707fd2419

Faulting application path: C:\Program Files\Microsoft Office\Office15\WINWORD.EXE

Faulting module path: c:\Program Files (x86)\Intel\Bluetooth\btmofficea.dll

Report Id: 487fb2ad-78da-11e2-98a3-005056c00008

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
Answer accepted by question author
Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
2013-02-17T08:41:14+00:00

Sounds like you may have a Bluetooth Add-in that is causing the problem.  Click on the File menu, then Options and then on Add-Ins and then click on the Go button alongside Manage Add-ins and if there is a Bluetooth Add-in, disable it.

Was this answer helpful?

90+ people found this answer helpful.
0 comments

134 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-17T14:39:44+00:00

    My story is the same as the one over a year ago, except... My problem began with Outlook's not working. I uninstalled Office 2013 Professional and installed it again. Within 24 hours Outlook stopped working again. Now, two days later, the same is happening with Word. Safe mode works for both. Here is the event log for Word. Nothing in the module path that would point to a solution such as the one you found last year with Bluetooth. Thanks in advance for your advice!

    Log Name:      Application

    Source:        Application Error

    Date:          5/17/2014 9:04:29 AM

    Faulting application name: winword.exe, version: 15.0.4420.1017, time stamp: 0x5067344b

    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

    Exception code: 0xc0000005

    Fault offset: 0x0040cde0

    Faulting process id: 0xc58

    Faulting application start time: 0x01cf71d07df52fe5

    Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\winword.exe

    Faulting module path: unknown

    Report Id: c75ef59d-ddc3-11e3-a422-f82fa8e61c98

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-03-14T21:18:24+00:00

    Yes I have and it did work thank.

    Was this answer helpful?

    0 comments
  3. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2014-03-12T22:17:41+00:00

    Have you tried the suggestions in my response of January 17, 2014?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-03-12T14:34:15+00:00

    I'm having the same problem with all Office 365 applications.  This is the message I get when I try to open a file in Word.  Please help

    Problem Event Name: BEX

      Application Name: WINWORD.EXE

      Application Version: 15.0.4569.1503

      Application Timestamp: 52b0b1b2

      Fault Module Name: unknown

      Fault Module Version: 0.0.0.0

      Fault Module Timestamp: 00000000

      Exception Offset: 003ad7e8

      Exception Code: c0000005

      Exception Data: 00000008

      OS Version: 6.1.7601.2.1.0.768.3

      Locale ID: 1033

    Additional information about the problem:

      LCID: 1033

      skulcid: 1033

    Read our privacy statement online:

    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:

    C:\Windows\system32\en-US\erofflps.txt

    Thank you

    Was this answer helpful?

    0 comments