Word crashes on startup

B

bluvoodoo7

Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel OK, I have uninstalled/reinstalled about 5 times. I have installed on another user account. I have turned off fonts, deleted fonts, reinstalled fonts. Deleted preference files, etc. etc. etc.

Everything I can think of. But word keeps crashing when I start it. All other office programs open just fine. Here is the error report. Any help would definitely be appreciated!!!

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-04-01 13:11:39 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.1.1.080522
Crashed Module Name: MicrosoftOffice
Crashed Module Version: unknown
Crashed Module Offset: 0x004c3c0e
Blame Module Name: MicrosoftOffice
Blame Module Version: unknown
Blame Module Offset: 0x004c3c0e
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x02267c0e in _GetFontData + 0x0000047A (MicrosoftOffice + 0x004c3c0e)
# 2 0x022702a2 in _TextOutA + 0x000005C3 (MicrosoftOffice + 0x004cc2a2)
# 3 0x02269688 in _GetTextMetricsA + 0x00000063 (MicrosoftOffice + 0x004c5688)
# 4 0x00978868 in _wdGetApplicationObject + 0x002440DE (Microsoft Word + 0x00977868)
# 5 0x0097903a in _wdGetApplicationObject + 0x002448B0 (Microsoft Word + 0x0097803a)
# 6 0x00679549 in _wdCommandDispatch + 0x0035CB29 (Microsoft Word + 0x00678549)
# 7 0x00ae68ab in _wdGetApplicationObject + 0x003B2121 (Microsoft Word + 0x00ae58ab)
# 8 0x00aef237 in _wdGetApplicationObject + 0x003BAAAD (Microsoft Word + 0x00aee237)
# 9 0x0224799c in __WlmMain + 0x00000047 (MicrosoftOffice + 0x004a399c)
# 10 0x00ad48fc in _wdGetApplicationObject + 0x003A0172 (Microsoft Word + 0x00ad38fc)
# 11 0x00002a22 in __mh_execute_header + 0x00001A22 (Microsoft Word + 0x00001a22)
# 12 0x00002949 in __mh_execute_header + 0x00001949 (Microsoft Word + 0x00001949)

X86 Thread State:
 eax: 0x00000000 ebx: 0x02267afb ecx: 0xa01b30a4 edx:0x00000000
 edi: 0x00000000 esi: 0x046d9548 ebp: 0xbffff478 esp:0xbffff440
  ss: 0x0000001f eip: 0x02267c0e cs: 0x00000017 ds:0x0000001f
  es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010246

Thread 1:

# 1 0x95203386 in _signgam + 0x9505C462 (libSystem.B.dylib + 0x00001386)
# 2 0x9528aeab in _signgam + 0x950E3F87 (libSystem.B.dylib + 0x00088eab)
# 3 0x01ab2d7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x01ab23e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x01ab246c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x01ab2f25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 8 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
 eax: 0xffffffa6 ebx: 0x9527a287 ecx: 0xb00a0a5c edx:0x95203386
 edi: 0x00000f9c esi: 0x27fc6dd3 ebp: 0xb00a0ac8 esp:0xb00a0a5c
  ss: 0x0000001f eip: 0x95203386 cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000206

Thread 2:

# 1 0x9520a44e in _signgam + 0x9506352A (libSystem.B.dylib + 0x0000844e)
# 2 0x95234dcd in _signgam + 0x9508DEA9 (libSystem.B.dylib + 0x00032dcd)
# 3 0x96fdb3f8 in __CMProfileID + 0x96F082D4 (ColorSync + 0x000333f8)
# 4 0x96fedd4e in __CMProfileID + 0x96F1AC2A (ColorSync + 0x00045d4e)
# 5 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 6 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
 eax: 0x0000014e ebx: 0x95234ded ecx: 0xb0122e7c edx:0x9520a44e
 edi: 0x04842ba4 esi: 0xb0123000 ebp: 0xb0122ef8 esp:0xb0122e7c
  ss: 0x0000001f eip: 0x9520a44e cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246

Loaded modules:

0: Microsoft Word (12.1.1.080522 Reg=en Loc=0x0409): /Applicatio
 
C

CyberTaz

How about thinking of getting Office updated? :) the error report indicates
that you're still running 12.1.1, but 12.2.4 is the current update level.

Go to Help> Check for Updates & accept everything it throws at you... While
in the AutoUpdate dialog you might also consider setting it to run Weekly or
Monthly so you don't get behind again.

BTW: "Uninstalling/reinstalling" is never the solution for most issues.
Also, it sets your installation back to the level on the source disk so all
more current updates have to be re-applied each time you do it.

HTH |:>)
Bob Jones
[MVP] Office:Mac
 
J

John McGhie

Looking at that crash report, we can see that you have not applied the
latest updates.

If you had, you would see Application Version: 12.2.4.010025 instead of
Application Version: 12.1.1.080522

We can also see that you have not "Resolved Duplicates" using font book.

Word is crashing either because you have a damaged font installed, or
because it cannot resolve conflicts amongst your fonts. The second is more
likely.

First: Apply all the latest updates to OS X, then to Office.

Then restart the computer, start Font Book, and Resolve Duplicates.

When you run into these problems, you need to carry out a sequence of tasks
in a specific order, because in a computer, everything affects everything
else.

The sequence is this:

1. Ascertain adequate machine resources

2. Get rid of Haxies and Helpers

3. Disconnect all but the boot drive.

4. Remove Office

5. Remove all previous resources and prefs from previous installations

6. Check and update the printer driver

7. Update the Operating System

8. Power-off restart

9. Fix disk permissions

10. Install Office 2008

11. Install two service packs and all the updates to 12.2.4

12. Resolve all Font Duplicates by removing the old versions from the
System.

13. Clear out all caches

14. Launch Word

15. Clean out old documents

16. DON¹T attempt to run any software that offers to ³reduce the size² of
Microsoft Office.

In your case, I think you can begin at Step 5 and continue to Step 14. I
would use OnyX to clean the caches. If you need more information, please
get back to us.

Cheers


Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel OK, I
have uninstalled/reinstalled about 5 times. I have installed on another user
account. I have turned off fonts, deleted fonts, reinstalled fonts. Deleted
preference files, etc. etc. etc.

Everything I can think of. But word keeps crashing when I start it. All other
office programs open just fine. Here is the error report. Any help would
definitely be appreciated!!!

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-04-01 13:11:39 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.1.1.080522
Crashed Module Name: MicrosoftOffice
Crashed Module Version: unknown
Crashed Module Offset: 0x004c3c0e
Blame Module Name: MicrosoftOffice
Blame Module Version: unknown
Blame Module Offset: 0x004c3c0e
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x02267c0e in _GetFontData + 0x0000047A (MicrosoftOffice + 0x004c3c0e)
# 2 0x022702a2 in _TextOutA + 0x000005C3 (MicrosoftOffice + 0x004cc2a2)
# 3 0x02269688 in _GetTextMetricsA + 0x00000063 (MicrosoftOffice +
0x004c5688)
# 4 0x00978868 in _wdGetApplicationObject + 0x002440DE (Microsoft Word +
0x00977868)
# 5 0x0097903a in _wdGetApplicationObject + 0x002448B0 (Microsoft Word +
0x0097803a)
# 6 0x00679549 in _wdCommandDispatch + 0x0035CB29 (Microsoft Word +
0x00678549)
# 7 0x00ae68ab in _wdGetApplicationObject + 0x003B2121 (Microsoft Word +
0x00ae58ab)
# 8 0x00aef237 in _wdGetApplicationObject + 0x003BAAAD (Microsoft Word +
0x00aee237)
# 9 0x0224799c in __WlmMain + 0x00000047 (MicrosoftOffice + 0x004a399c)
# 10 0x00ad48fc in _wdGetApplicationObject + 0x003A0172 (Microsoft Word +
0x00ad38fc)
# 11 0x00002a22 in __mh_execute_header + 0x00001A22 (Microsoft Word +
0x00001a22)
# 12 0x00002949 in __mh_execute_header + 0x00001949 (Microsoft Word +
0x00001949)

X86 Thread State:
eax: 0x00000000 ebx: 0x02267afb ecx: 0xa01b30a4 edx:0x00000000
edi: 0x00000000 esi: 0x046d9548 ebp: 0xbffff478 esp:0xbffff440
ss: 0x0000001f eip: 0x02267c0e cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010246

Thread 1:

# 1 0x95203386 in _signgam + 0x9505C462 (libSystem.B.dylib + 0x00001386)
# 2 0x9528aeab in _signgam + 0x950E3F87 (libSystem.B.dylib + 0x00088eab)
# 3 0x01ab2d7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x01ab23e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x01ab246c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x01ab2f25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 8 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0xffffffa6 ebx: 0x9527a287 ecx: 0xb00a0a5c edx:0x95203386
edi: 0x00000f9c esi: 0x27fc6dd3 ebp: 0xb00a0ac8 esp:0xb00a0a5c
ss: 0x0000001f eip: 0x95203386 cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000206

Thread 2:

# 1 0x9520a44e in _signgam + 0x9506352A (libSystem.B.dylib + 0x0000844e)
# 2 0x95234dcd in _signgam + 0x9508DEA9 (libSystem.B.dylib + 0x00032dcd)
# 3 0x96fdb3f8 in __CMProfileID + 0x96F082D4 (ColorSync + 0x000333f8)
# 4 0x96fedd4e in __CMProfileID + 0x96F1AC2A (ColorSync + 0x00045d4e)
# 5 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 6 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0x0000014e ebx: 0x95234ded ecx: 0xb0122e7c edx:0x9520a44e
edi: 0x04842ba4 esi: 0xb0123000 ebp: 0xb0122ef8 esp:0xb0122e7c
ss: 0x0000001f eip: 0x9520a44e cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246

Loaded modules:

0: Microsoft Word (12.1.1.080522 Reg=en Loc=0x0409): /Applicatio
Click to expand...

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]
 
C

CyberTaz

This part of your error report may very well say it all: Application
Version: 12.1.1.080522

Office is now at 12.2.4, so the first thing I'd suggest is that you get
Office fully updated, then repair disk permissions & restart your Mac.

Additionally, avoid the Windows-mentality universal panacea of re-installing
whenever something goes wrong. That's typically not the proper approach for
complex apps/suites that run on a Mac. In fact, doing so can quite often
complicate the issue & cause others to arise. The cause of misbehaviors have
nothing to do with what is reinstalled & at the very least it sets the app
back to whatever level is on the source disk causing them to be out of sync
with the user/system-specific files.

In any Office app go to Help> Check for Updates & accept all updates
offered. If you still have a problem reply in detail for further
suggestions. It's pointless to chase symptoms until the software is fully
updated, though.
 
B

bluvoodoo7

have looked at the past postings and I have done everything I can find. None of these things has fixed my problem. (see my first posting). So I need some further suggestions please. Or if someone can at least narrow down my search based on the info in the log.
 
J

John McGhie

Well, your crash dump indicates that you're missing several updates: you're
at 12.1.1, you need to be at 12.2.4.

Keep updating until you get there, and it will probably cure the issue.

You may also need to go to Font Book and Resolve Duplicates.

Cheers


have looked at the past postings and I have done everything I can find. None
of these things has fixed my problem. (see my first posting). So I need some
further suggestions please. Or if someone can at least narrow down my search
based on the info in the log.
Click to expand...

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
 
B

bluvoodoo7

As stated above, I have updated to the latest version, I have also done the resolve duplicates. Here's a new dump just for fun.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-04-05 08:53:26 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.2.4.100205
Crashed Module Name: MicrosoftOffice
Crashed Module Version: unknown
Crashed Module Offset: 0x004d661a
Blame Module Name: MicrosoftOffice
Blame Module Version: unknown
Blame Module Offset: 0x004d661a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x022f061a in _GetFontData + 0x0000047A (MicrosoftOffice + 0x004d661a)
# 2 0x022f8cae in _TextOutA + 0x000005C3 (MicrosoftOffice + 0x004decae)
# 3 0x022f2094 in _GetTextMetricsA + 0x00000063 (MicrosoftOffice + 0x004d8094)
# 4 0x00983bb2 in _wdGetApplicationObject + 0x00244FE8 (Microsoft Word + 0x00982bb2)
# 5 0x00984382 in _wdGetApplicationObject + 0x002457B8 (Microsoft Word + 0x00983382)
# 6 0x0068326b in _wdCommandDispatch + 0x0035E92F (Microsoft Word + 0x0068226b)
# 7 0x00af2a53 in _wdGetApplicationObject + 0x003B3E89 (Microsoft Word + 0x00af1a53)
# 8 0x00afb3df in _wdGetApplicationObject + 0x003BC815 (Microsoft Word + 0x00afa3df)
# 9 0x022d0554 in __WlmMain + 0x00000047 (MicrosoftOffice + 0x004b6554)
# 10 0x00ae0a54 in _wdGetApplicationObject + 0x003A1E8A (Microsoft Word + 0x00adfa54)
# 11 0x00003022 in __mh_execute_header + 0x00002022 (Microsoft Word + 0x00002022)
# 12 0x00002f49 in __mh_execute_header + 0x00001F49 (Microsoft Word + 0x00001f49)

X86 Thread State:
 eax: 0x00000000 ebx: 0x022f0507 ecx: 0xa01b30a4 edx:0x00000000
 edi: 0x00000000 esi: 0x047db7e8 ebp: 0xbffff478 esp:0xbffff440
  ss: 0x0000001f eip: 0x022f061a cs: 0x00000017 ds:0x0000001f
  es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010246

Thread 1:

# 1 0x95203386 in _signgam + 0x9505C462 (libSystem.B.dylib + 0x00001386)
# 2 0x9528aeab in _signgam + 0x950E3F87 (libSystem.B.dylib + 0x00088eab)
# 3 0x01b29d7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x01b293e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x01b2946c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x01b29f25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 8 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
 eax: 0xffffffa6 ebx: 0x9527a287 ecx: 0xb00a0a5c edx:0x95203386
 edi: 0x00000041 esi: 0x70bb836e ebp: 0xb00a0ac8 esp:0xb00a0a5c
  ss: 0x0000001f eip: 0x95203386 cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000206

Thread 2:

# 1 0x9520a44e in _signgam + 0x9506352A (libSystem.B.dylib + 0x0000844e)
# 2 0x95234dcd in _signgam + 0x9508DEA9 (libSystem.B.dylib + 0x00032dcd)
# 3 0x96fdb3f8 in __CMProfileID + 0x96F082D4 (ColorSync + 0x000333f8)
# 4 0x96fedd4e in __CMProfileID + 0x96F1AC2A (ColorSync + 0x00045d4e)
# 5 0x95234155 in _signgam + 0x9508D231 (libSystem.B.dylib + 0x00032155)
# 6 0x95234012 in _signgam + 0x9508D0EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
 eax: 0x0000014e ebx: 0x95234ded ecx: 0xb0122e7c edx:0x9520a44e
 edi: 0x04809fa4 esi: 0xb0123000 ebp: 0xb0122ef8 esp:0xb0122e7c
  ss: 0x0000001f eip: 0x9520a44e cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246

Loaded modules:

0: Microsoft Word (12.2.4.100205 Reg=en Loc=0x0409): /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
1: MicrosoftComponentPlugin: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/../Frameworks/MicrosoftComponentPlugin.framework/Versions/12/MicrosoftCompone
 
J

John McGhie

Cool. That crash is a classic "Bad font cache or corrupt font" crash.

Somewhere on your system, there is an incompatible font that is crashing
Word.

Things to check:

1) Did you remove the duplicate fonts from the system, or did you simply
switch them off? Switching off is not sufficient.

2) Did you do a power-off re-start after fixing the fonts? If you didn't,
the system didn't rebuild its font cache and the problem is still with you.

3) Do you have fonts in play that came up from old OS 9 versions of Mac OS?
Some of those fonts contain PostScript macros that will crash Word: replace
them with the modern equivalents provided by Apple or Microsoft.

Hope this helps


As stated above, I have updated to the latest version, I have also done the
resolve duplicates. Here's a new dump just for fun.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-04-05 08:53:26 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.2.4.100205
Crashed Module Name: MicrosoftOffice
Crashed Module Version: unknown
Crashed Module Offset: 0x004d661a
Blame Module Name: MicrosoftOffice
Blame Module Version: unknown
Blame Module Offset: 0x004d661a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x022f061a in _GetFontData + 0x0000047A (MicrosoftOffice + 0x004d661a)
# 2 0x022f8cae in _TextOutA + 0x000005C3 (MicrosoftOffice + 0x004decae)
# 3 0x022f2094 in _GetTextMetricsA + 0x00000063 (MicrosoftOffice +
0x004d8094)
Click to expand...

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]
 
B

bluvoodoo7

I replaced the fonts in System>Library>Fonts from another system. And now it's working!! Finally!!
 
J

John McGhie

Well done! That would have fixed it :)


I replaced the fonts in System>Library>Fonts from another system. And now it's
working!! Finally!!
Click to expand...

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Error upon opening any word document or clicking on the help 6
Word crash - don't know the reason 8
MS Word 2008 always "quits unexpectedly" 16
Sync Servises Error 3
microsoft sync services--since downloadingupdate to Blackberry Desktop manager 1
constant error report. 4
Micro sync service 0
error messages for word, powerpoint & excel 6

Top