Word 2008 Crashes Consistently

Alpaca · Feb 15, 2008

After a brand new install of Office 2008 yesterday, I began using Word as I normally do, and found, to my great distress, that it crashes with frightening reliability, and apparently does so when I do just about anything. Hitting backspace a couple of times in a row will do it. Copy-pasting text will do it. Ironically enough, even quitting the application will crash it. None of the other components of the Office suite appear to be affected, but Word is rendered unusable.

The error output upon crash is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-14 22:38:03 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: Microsoft Word
Crashed Module Version: 12.0.0.071130
Crashed Module Offset: 0x00349844
Blame Module Name: Microsoft Word
Blame Module Version: 12.0.0.071130
Blame Module Offset: 0x00349844
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0034a844 in _wdCommandDispatch + 0x00021A3C (Microsoft Word + 0x00349844)
# 2 0x008a4da4 in _wdCommandDispatch + 0x0057BF9C (Microsoft Word + 0x008a3da4)
# 3 0x008f9d1c in _wdCommandDispatch + 0x005D0F14 (Microsoft Word + 0x008f8d1c)
# 4 0x00afe43c in _wdCommandDispatch + 0x007D5634 (Microsoft Word + 0x00afd43c)
# 5 0x022dd2f8 in _DispatchMessageA + 0x000000D4 (MicrosoftOffice + 0x004d12f8)
# 6 0x022dd420 in _DispatchMessageA + 0x000001FC (MicrosoftOffice + 0x004d1420)
# 7 0x01616fbc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x00000230 (MicrosoftComponentPlugin + 0x000a4fbc)
# 8 0x9254df68 in .objc_class_name_IPMDFontRange + 0x921EE428 (HIToolbox + 0x00007f68)
# 9 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 10 0x9254cf1c in .objc_class_name_IPMDFontRange + 0x921ED3DC (HIToolbox + 0x00006f1c)
# 11 0x9257d824 in .objc_class_name_IPMDFontRange + 0x9221DCE4 (HIToolbox + 0x00037824)
# 12 0x9254e3bc in .objc_class_name_IPMDFontRange + 0x921EE87C (HIToolbox + 0x000083bc)
# 13 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 14 0x9256a0e0 in .objc_class_name_IPMDFontRange + 0x9220A5A0 (HIToolbox + 0x000240e0)
# 15 0x0166d14c in _McpFDispatchEventRef + 0x000000B4 (MicrosoftComponentPlugin + 0x000fb14c)
# 16 0x0166d65c in _McpRunApplicationEventLoop + 0x00000470 (MicrosoftComponentPlugin + 0x000fb65c)
# 17 0x00af7cbc in _wdCommandDispatch + 0x007CEEB4 (Microsoft Word + 0x00af6cbc)
# 18 0x00b00be8 in _wdCommandDispatch + 0x007D7DE0 (Microsoft Word + 0x00affbe8)
# 19 0x022e7bbc in __WlmMain + 0x00000050 (MicrosoftOffice + 0x004dbbbc)
# 20 0x00ae5454 in _wdCommandDispatch + 0x007BC64C (Microsoft Word + 0x00ae4454)
# 21 0x000032c0 in __mh_execute_header + 0x000022C0 (Microsoft Word + 0x000022c0)
# 22 0x00002fc4 in __mh_execute_header + 0x00001FC4 (Microsoft Word + 0x00001fc4)

PPC Thread State:
srr0: 0x0034a844 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x008a4da4 ctr: 0x000000be mq:0x00000000
r0: 0x000000be r1: 0xbfffdf80 r2: 0x00000000 r3:0x00000001
r4: 0x050d83ac r5: 0x00000004 r6: 0xfe000000 r7:0xbfffdfb8
r8: 0x11efc080 r9: 0x626c655f r10: 0x014b30d0 r11:0x00000000
r12: 0x05957bf6 r13: 0xbfffe060 r14: 0x01410000 r15:0x01410000
r16: 0x01410000 r17: 0x01410000 r18: 0x01410000 r19:0x013d0000
r20: 0x01410000 r21: 0x014b3460 r22: 0x014ba490 r23:0x01410000
r24: 0x01410000 r25: 0xbfffdfd4 r26: 0xbfffdfc8 r27:0x00000000
r28: 0xbfffdfc0 r29: 0x00000000 r30: 0xbfffdfbc r31:0x014b30e0

Thread 1:

# 1 0x93e7aaf8 in _atantblEntry + 0x93CA0328 (libSystem.B.dylib + 0x00001af8)
# 2 0x93f06910 in _atantblEntry + 0x93D2C140 (libSystem.B.dylib + 0x0008d910)
# 3 0x93f1dcdc in _atantblEntry + 0x93D4350C (libSystem.B.dylib + 0x0

CyberTaz · Feb 15, 2008

Which level of OS X & what type of Mac?

Have you tried repairing disk permissions & restarting the unit?

Regards |:>)
Bob Jones
[MVP] Office:Mac

Alpaca · Feb 15, 2008

OSX 10.5.2 on a PowerPC G5 iMac. Done all the usual permission repairing, rebooting, clearing of all sorts of system caches, etc.

Thanks for your help!

John McGhie · Feb 15, 2008

Hmmm....

Looking at your crash dump, it "might" be fonts.

As an experiment, move the Microsoft folder from /Library/Fonts/ to your
desktop, then re-boot.

Let us know what (if anything) changes...

Hope this helps

OSX 10.5.2 on a PowerPC G5 iMac. Done all the usual permission repairing,
rebooting, clearing of all sorts of system caches, etc.

Thanks for your help!

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50

Alpaca · Feb 16, 2008

It still crashes, despite my having moved the Microsoft directory to the desktop.

I also realized that my first post got truncated somehow and thus doesn't have the full crashlog, so I put it into a pastebin, in case that would be of any help.

<http://slexy.org/view/s21DcdSBrg>

John McGhie · Feb 16, 2008

So the next thing to try is to remove your Normal template and your
settings.

Close all Microsoft Office applications, then find your Normal.dotm and
delete it, then search for any other files on the computer named "Normal"
(there may be two, from older versions of Word). If they are there, they
will have no extension.

Move the older files to the desktop.

Now find ~/Library/Preferences/Microsoft/Word Settings (10) and
~/Library/Preferences/Microsoft/Word Settings (11)

If either are there, delete them.

Now delete
User/Library/Preferences/com.Microsoft.Word.plist

User/Library/Preferences/Microsoft/Office 2008 (the whole folder!)

Try that.

Sadly, Office 2008 does crash a lot on a PowerPC. We are waiting on fixes
from Microsoft. These solutions may at least move the crashes further
apart...

Hope this helps

It still crashes, despite my having moved the Microsoft directory to the
desktop.

I also realized that my first post got truncated somehow and thus doesn't have
the full crashlog, so I put it into a pastebin, in case that would be of any
help.

<http://slexy.org/view/s21DcdSBrg>

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50

Alpaca · Feb 16, 2008

That does seem to alleviate the issue, hopefully until an update. For the record, Spotlight couldn't find a Normal file, which might account for something.

Thanks for your help!

John McGhie · Feb 17, 2008

If Spotlight is looking in the Documents folder, and it can't find any files
named Normal, that's a good sign

Word 2008 is programmed to import settings from the previous Normal
template. Unfortunately, we have now discovered that people's Normal
templates can contain incompatible settings that cause crashes.

That's a bug, too, and they're working on that one too

Cheers

That does seem to alleviate the issue, hopefully until an update. For the
record, Spotlight couldn't find a Normal file, which might account for
something.

Thanks for your help!

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
+61 4 1209 1410, mailto:[email protected]
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia

David Rood · Feb 17, 2008

I don't know if this is the same problem but my Word will not launch. The splash screen just hangs there with no menus or documents.
I trashed prefs and permissions but it had no effect.

Beth Rosengard · Feb 18, 2008

Hi David,

You're in Word 2008 too? What version of the OS?

See if the first item here helps:
<http://word.mvps.org/mac/Word2008Issues.html>

--
***Please always reply to the newsgroup!***

Beth Rosengard
Mac MVP

Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html>
My Site: <http://www.bethrosengard.com>

Albuquer-JAY · Feb 18, 2008

Thanks Beth - your post fixed my problem.... removing the preferences in the system folder enabled word to start - - FINALLY! Muchas Gracias.

<http://word.mvps.org/mac/Word2008Issues.html>

Emilyz · Apr 2, 2008

I have had my mac for less than a month, and my microsoft office is doing the same thing- crashing everytime i try to work on anyway (frustrating seeing as how I have fifty page paper due in 3 weeks). I tried to follow the instructions given that seemed your fix your problem, but I am not very computer saavy and could not figure it out. do you think you could let me know what you did to fix it?
Thanks!

Emilyz · Apr 2, 2008

I have had my mac for less than a month, and my microsoft office is doing the same thing- crashing everytime i try to work on anyway (frustrating seeing as how I have fifty page paper due in 3 weeks). I tried to follow the instructions given that seemed your fix your problem, but I am not very computer saavy and could not figure it out. do you think you could let me know what you did to fix it?
Thanks!

John McGhie · Apr 4, 2008

Is this "one" document that's crashing, or "any" document.

If it's only "one" document, it's a corrupt document. Try a Maggie:

1) Create a new blank document

2) Carefully select all of the text in the bad document EXCEPT the last
paragraph mark

3) Copy it.

4) Paste in the new document.

5) Save under a new file name and close all, then re-open.

This technique for de-corrupting is known as "Doing a 'Maggie'", after
Margaret Secara from the Word PC-L mailing list who first publicised the
technique.

If that doesn't fix it, try a Save as Web Page:

1. Open the document
2. File>Save As... And choose Web Page
3. In the bottom of the dialog, make CERTAIN ³Save entire file² is checked.
4. Save the file and close the document
5. Quit Word and re-start it
6. Open the Web Page version of the file
7. File>Save as and this time choose ³Document²
8. Give the file a different name, so you have the old one to go back to.
9. Check the file for missing bits.

If you choose ³Save Display information only² you strip out the code in the
file that enables Word to re-create a document from it later. By forcing
Word to re-express the file in a different format, you cause it to discard
any code it cannot understand. That fixes the problem, but it can lead to
missing text.

Hope this helps

I have had my mac for less than a month, and my microsoft office is doing the
same thing- crashing everytime i try to work on anyway (frustrating seeing as
how I have fifty page paper due in 3 weeks). I tried to follow the
instructions given that seemed your fix your problem, but I am not very
computer saavy and could not figure it out. do you think you could let me know
what you did to fix it?
Thanks!

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]

mxk · Apr 4, 2008

After a brand new install of Office 2008 yesterday, I began usingWordas I normally do, and found, to my great distress, that it crashes with frightening reliability, and apparently does so when I do just about anything. Hitting backspace a couple of times in a row will do it. Copy-pasting text will doit. Ironically enough, even quitting the application will crash it. None ofthe other components of the Office suite appear to be affected, butWordis rendered unusable.

The error output upon crash is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-14 22:38:03 -0500
Application Name: MicrosoftWord
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: MicrosoftWord
Crashed Module Version: 12.0.0.071130
Crashed Module Offset: 0x00349844
Blame Module Name: MicrosoftWord
Blame Module Version: 12.0.0.071130
Blame Module Offset: 0x00349844
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0034a844 in _wdCommandDispatch + 0x00021A3C (MicrosoftWord+ 0x00349844)
# 2 0x008a4da4 in _wdCommandDispatch + 0x0057BF9C (MicrosoftWord+ 0x008a3da4)
# 3 0x008f9d1c in _wdCommandDispatch + 0x005D0F14 (MicrosoftWord+ 0x008f8d1c)
# 4 0x00afe43c in _wdCommandDispatch + 0x007D5634 (MicrosoftWord+ 0x00afd43c)
# 5 0x022dd2f8 in _DispatchMessageA + 0x000000D4 (MicrosoftOffice + 0x004d12f8)
# 6 0x022dd420 in _DispatchMessageA + 0x000001FC (MicrosoftOffice + 0x004d1420)
# 7 0x01616fbc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x00000230 (MicrosoftComponentPlugin + 0x000a4fbc)
# 8 0x9254df68 in .objc_class_name_IPMDFontRange + 0x921EE428 (HIToolbox +0x00007f68)
# 9 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox +0x00007100)
# 10 0x9254cf1c in .objc_class_name_IPMDFontRange + 0x921ED3DC (HIToolbox + 0x00006f1c)
# 11 0x9257d824 in .objc_class_name_IPMDFontRange + 0x9221DCE4 (HIToolbox + 0x00037824)
# 12 0x9254e3bc in .objc_class_name_IPMDFontRange + 0x921EE87C (HIToolbox + 0x000083bc)
# 13 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 14 0x9256a0e0 in .objc_class_name_IPMDFontRange + 0x9220A5A0 (HIToolbox + 0x000240e0)
# 15 0x0166d14c in _McpFDispatchEventRef + 0x000000B4 (MicrosoftComponentPlugin + 0x000fb14c)
# 16 0x0166d65c in _McpRunApplicationEventLoop + 0x00000470 (MicrosoftComponentPlugin + 0x000fb65c)
# 17 0x00af7cbc in _wdCommandDispatch + 0x007CEEB4 (MicrosoftWord+ 0x00af6cbc)
# 18 0x00b00be8 in _wdCommandDispatch + 0x007D7DE0 (MicrosoftWord+ 0x00affbe8)
# 19 0x022e7bbc in __WlmMain + 0x00000050 (MicrosoftOffice + 0x004dbbbc)
# 20 0x00ae5454 in _wdCommandDispatch + 0x007BC64C (MicrosoftWord+ 0x00ae4454)
# 21 0x000032c0 in __mh_execute_header + 0x000022C0 (MicrosoftWord+ 0x000022c0)
# 22 0x00002fc4 in __mh_execute_header + 0x00001FC4 (MicrosoftWord+ 0x00001fc4)

PPC Thread State:
srr0: 0x0034a844 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x008a4da4 ctr: 0x000000be mq:0x00000000
r0: 0x000000be r1: 0xbfffdf80 r2: 0x00000000 r3:0x00000001
r4: 0x050d83ac r5: 0x00000004 r6: 0xfe000000 r7:0xbfffdfb8
r8: 0x11efc080 r9: 0x626c655f r10: 0x014b30d0 r11:0x00000000
r12: 0x05957bf6 r13: 0xbfffe060 r14: 0x01410000 r15:0x01410000
r16: 0x01410000 r17: 0x01410000 r18: 0x01410000 r19:0x013d0000
r20: 0x01410000 r21: 0x014b3460 r22: 0x014ba490 r23:0x01410000
r24: 0x01410000 r25: 0xbfffdfd4 r26: 0xbfffdfc8 r27:0x00000000
r28: 0xbfffdfc0 r29: 0x00000000 r30: 0xbfffdfbc r31:0x014b30e0

Thread 1:

# 1 0x93e7aaf8 in _atantblEntry + 0x93CA0328 (libSystem.B.dylib + 0x00001af8)
# 2 0x93f06910 in _atantblEntry + 0x93D2C140 (libSystem.B.dylib + 0x0008d910)
# 3 0x93f1dcdc in _atantblEntry + 0x93D4350C (libSystem.B.dylib + 0x0

Hi,

Why not try Advanced Word Repair at http://www.datanumen.com/awr/ ?
It recovers several important Word documents for me and is really
helpful!

Alan

mxk · Apr 4, 2008

After a brand new install of Office 2008 yesterday, I began usingWordas I normally do, and found, to my great distress, that it crashes with frightening reliability, and apparently does so when I do just about anything. Hitting backspace a couple of times in a row will do it. Copy-pasting text will doit. Ironically enough, even quitting the application will crash it. None ofthe other components of the Office suite appear to be affected, butWordis rendered unusable.

The error output upon crash is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-14 22:38:03 -0500
Application Name: MicrosoftWord
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: MicrosoftWord
Crashed Module Version: 12.0.0.071130
Crashed Module Offset: 0x00349844
Blame Module Name: MicrosoftWord
Blame Module Version: 12.0.0.071130
Blame Module Offset: 0x00349844
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0034a844 in _wdCommandDispatch + 0x00021A3C (MicrosoftWord+ 0x00349844)
# 2 0x008a4da4 in _wdCommandDispatch + 0x0057BF9C (MicrosoftWord+ 0x008a3da4)
# 3 0x008f9d1c in _wdCommandDispatch + 0x005D0F14 (MicrosoftWord+ 0x008f8d1c)
# 4 0x00afe43c in _wdCommandDispatch + 0x007D5634 (MicrosoftWord+ 0x00afd43c)
# 5 0x022dd2f8 in _DispatchMessageA + 0x000000D4 (MicrosoftOffice + 0x004d12f8)
# 6 0x022dd420 in _DispatchMessageA + 0x000001FC (MicrosoftOffice + 0x004d1420)
# 7 0x01616fbc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x00000230 (MicrosoftComponentPlugin + 0x000a4fbc)
# 8 0x9254df68 in .objc_class_name_IPMDFontRange + 0x921EE428 (HIToolbox +0x00007f68)
# 9 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox +0x00007100)
# 10 0x9254cf1c in .objc_class_name_IPMDFontRange + 0x921ED3DC (HIToolbox + 0x00006f1c)
# 11 0x9257d824 in .objc_class_name_IPMDFontRange + 0x9221DCE4 (HIToolbox + 0x00037824)
# 12 0x9254e3bc in .objc_class_name_IPMDFontRange + 0x921EE87C (HIToolbox + 0x000083bc)
# 13 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 14 0x9256a0e0 in .objc_class_name_IPMDFontRange + 0x9220A5A0 (HIToolbox + 0x000240e0)
# 15 0x0166d14c in _McpFDispatchEventRef + 0x000000B4 (MicrosoftComponentPlugin + 0x000fb14c)
# 16 0x0166d65c in _McpRunApplicationEventLoop + 0x00000470 (MicrosoftComponentPlugin + 0x000fb65c)
# 17 0x00af7cbc in _wdCommandDispatch + 0x007CEEB4 (MicrosoftWord+ 0x00af6cbc)
# 18 0x00b00be8 in _wdCommandDispatch + 0x007D7DE0 (MicrosoftWord+ 0x00affbe8)
# 19 0x022e7bbc in __WlmMain + 0x00000050 (MicrosoftOffice + 0x004dbbbc)
# 20 0x00ae5454 in _wdCommandDispatch + 0x007BC64C (MicrosoftWord+ 0x00ae4454)
# 21 0x000032c0 in __mh_execute_header + 0x000022C0 (MicrosoftWord+ 0x000022c0)
# 22 0x00002fc4 in __mh_execute_header + 0x00001FC4 (MicrosoftWord+ 0x00001fc4)

PPC Thread State:
srr0: 0x0034a844 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x008a4da4 ctr: 0x000000be mq:0x00000000
r0: 0x000000be r1: 0xbfffdf80 r2: 0x00000000 r3:0x00000001
r4: 0x050d83ac r5: 0x00000004 r6: 0xfe000000 r7:0xbfffdfb8
r8: 0x11efc080 r9: 0x626c655f r10: 0x014b30d0 r11:0x00000000
r12: 0x05957bf6 r13: 0xbfffe060 r14: 0x01410000 r15:0x01410000
r16: 0x01410000 r17: 0x01410000 r18: 0x01410000 r19:0x013d0000
r20: 0x01410000 r21: 0x014b3460 r22: 0x014ba490 r23:0x01410000
r24: 0x01410000 r25: 0xbfffdfd4 r26: 0xbfffdfc8 r27:0x00000000
r28: 0xbfffdfc0 r29: 0x00000000 r30: 0xbfffdfbc r31:0x014b30e0

Thread 1:

# 1 0x93e7aaf8 in _atantblEntry + 0x93CA0328 (libSystem.B.dylib + 0x00001af8)
# 2 0x93f06910 in _atantblEntry + 0x93D2C140 (libSystem.B.dylib + 0x0008d910)
# 3 0x93f1dcdc in _atantblEntry + 0x93D4350C (libSystem.B.dylib + 0x0

Hi,

Why not try Advanced Word Repair at http://www.datanumen.com/awr/ ?
It recovers several important Word documents for me and is really
helpful!

Alan

mxk · Apr 4, 2008

After a brand new install of Office 2008 yesterday, I began usingWordas I normally do, and found, to my great distress, that it crashes with frightening reliability, and apparently does so when I do just about anything. Hitting backspace a couple of times in a row will do it. Copy-pasting text will doit. Ironically enough, even quitting the application will crash it. None ofthe other components of the Office suite appear to be affected, butWordis rendered unusable.

The error output upon crash is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-14 22:38:03 -0500
Application Name: MicrosoftWord
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: MicrosoftWord
Crashed Module Version: 12.0.0.071130
Crashed Module Offset: 0x00349844
Blame Module Name: MicrosoftWord
Blame Module Version: 12.0.0.071130
Blame Module Offset: 0x00349844
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0034a844 in _wdCommandDispatch + 0x00021A3C (MicrosoftWord+ 0x00349844)
# 2 0x008a4da4 in _wdCommandDispatch + 0x0057BF9C (MicrosoftWord+ 0x008a3da4)
# 3 0x008f9d1c in _wdCommandDispatch + 0x005D0F14 (MicrosoftWord+ 0x008f8d1c)
# 4 0x00afe43c in _wdCommandDispatch + 0x007D5634 (MicrosoftWord+ 0x00afd43c)
# 5 0x022dd2f8 in _DispatchMessageA + 0x000000D4 (MicrosoftOffice + 0x004d12f8)
# 6 0x022dd420 in _DispatchMessageA + 0x000001FC (MicrosoftOffice + 0x004d1420)
# 7 0x01616fbc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x00000230 (MicrosoftComponentPlugin + 0x000a4fbc)
# 8 0x9254df68 in .objc_class_name_IPMDFontRange + 0x921EE428 (HIToolbox +0x00007f68)
# 9 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox +0x00007100)
# 10 0x9254cf1c in .objc_class_name_IPMDFontRange + 0x921ED3DC (HIToolbox + 0x00006f1c)
# 11 0x9257d824 in .objc_class_name_IPMDFontRange + 0x9221DCE4 (HIToolbox + 0x00037824)
# 12 0x9254e3bc in .objc_class_name_IPMDFontRange + 0x921EE87C (HIToolbox + 0x000083bc)
# 13 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 14 0x9256a0e0 in .objc_class_name_IPMDFontRange + 0x9220A5A0 (HIToolbox + 0x000240e0)
# 15 0x0166d14c in _McpFDispatchEventRef + 0x000000B4 (MicrosoftComponentPlugin + 0x000fb14c)
# 16 0x0166d65c in _McpRunApplicationEventLoop + 0x00000470 (MicrosoftComponentPlugin + 0x000fb65c)
# 17 0x00af7cbc in _wdCommandDispatch + 0x007CEEB4 (MicrosoftWord+ 0x00af6cbc)
# 18 0x00b00be8 in _wdCommandDispatch + 0x007D7DE0 (MicrosoftWord+ 0x00affbe8)
# 19 0x022e7bbc in __WlmMain + 0x00000050 (MicrosoftOffice + 0x004dbbbc)
# 20 0x00ae5454 in _wdCommandDispatch + 0x007BC64C (MicrosoftWord+ 0x00ae4454)
# 21 0x000032c0 in __mh_execute_header + 0x000022C0 (MicrosoftWord+ 0x000022c0)
# 22 0x00002fc4 in __mh_execute_header + 0x00001FC4 (MicrosoftWord+ 0x00001fc4)

PPC Thread State:
srr0: 0x0034a844 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x008a4da4 ctr: 0x000000be mq:0x00000000
r0: 0x000000be r1: 0xbfffdf80 r2: 0x00000000 r3:0x00000001
r4: 0x050d83ac r5: 0x00000004 r6: 0xfe000000 r7:0xbfffdfb8
r8: 0x11efc080 r9: 0x626c655f r10: 0x014b30d0 r11:0x00000000
r12: 0x05957bf6 r13: 0xbfffe060 r14: 0x01410000 r15:0x01410000
r16: 0x01410000 r17: 0x01410000 r18: 0x01410000 r19:0x013d0000
r20: 0x01410000 r21: 0x014b3460 r22: 0x014ba490 r23:0x01410000
r24: 0x01410000 r25: 0xbfffdfd4 r26: 0xbfffdfc8 r27:0x00000000
r28: 0xbfffdfc0 r29: 0x00000000 r30: 0xbfffdfbc r31:0x014b30e0

Thread 1:

# 1 0x93e7aaf8 in _atantblEntry + 0x93CA0328 (libSystem.B.dylib + 0x00001af8)
# 2 0x93f06910 in _atantblEntry + 0x93D2C140 (libSystem.B.dylib + 0x0008d910)
# 3 0x93f1dcdc in _atantblEntry + 0x93D4350C (libSystem.B.dylib + 0x0

Hi,

Why not try Advanced Word Repair at http://www.datanumen.com/awr/ ?
It recovers several important Word documents for me and is really
helpful!

Alan

mxk · Apr 4, 2008

After a brand new install of Office 2008 yesterday, I began usingWordas I normally do, and found, to my great distress, that it crashes with frightening reliability, and apparently does so when I do just about anything. Hitting backspace a couple of times in a row will do it. Copy-pasting text will doit. Ironically enough, even quitting the application will crash it. None ofthe other components of the Office suite appear to be affected, butWordis rendered unusable.

The error output upon crash is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-14 22:38:03 -0500
Application Name: MicrosoftWord
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: MicrosoftWord
Crashed Module Version: 12.0.0.071130
Crashed Module Offset: 0x00349844
Blame Module Name: MicrosoftWord
Blame Module Version: 12.0.0.071130
Blame Module Offset: 0x00349844
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0034a844 in _wdCommandDispatch + 0x00021A3C (MicrosoftWord+ 0x00349844)
# 2 0x008a4da4 in _wdCommandDispatch + 0x0057BF9C (MicrosoftWord+ 0x008a3da4)
# 3 0x008f9d1c in _wdCommandDispatch + 0x005D0F14 (MicrosoftWord+ 0x008f8d1c)
# 4 0x00afe43c in _wdCommandDispatch + 0x007D5634 (MicrosoftWord+ 0x00afd43c)
# 5 0x022dd2f8 in _DispatchMessageA + 0x000000D4 (MicrosoftOffice + 0x004d12f8)
# 6 0x022dd420 in _DispatchMessageA + 0x000001FC (MicrosoftOffice + 0x004d1420)
# 7 0x01616fbc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x00000230 (MicrosoftComponentPlugin + 0x000a4fbc)
# 8 0x9254df68 in .objc_class_name_IPMDFontRange + 0x921EE428 (HIToolbox +0x00007f68)
# 9 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox +0x00007100)
# 10 0x9254cf1c in .objc_class_name_IPMDFontRange + 0x921ED3DC (HIToolbox + 0x00006f1c)
# 11 0x9257d824 in .objc_class_name_IPMDFontRange + 0x9221DCE4 (HIToolbox + 0x00037824)
# 12 0x9254e3bc in .objc_class_name_IPMDFontRange + 0x921EE87C (HIToolbox + 0x000083bc)
# 13 0x9254d100 in .objc_class_name_IPMDFontRange + 0x921ED5C0 (HIToolbox + 0x00007100)
# 14 0x9256a0e0 in .objc_class_name_IPMDFontRange + 0x9220A5A0 (HIToolbox + 0x000240e0)
# 15 0x0166d14c in _McpFDispatchEventRef + 0x000000B4 (MicrosoftComponentPlugin + 0x000fb14c)
# 16 0x0166d65c in _McpRunApplicationEventLoop + 0x00000470 (MicrosoftComponentPlugin + 0x000fb65c)
# 17 0x00af7cbc in _wdCommandDispatch + 0x007CEEB4 (MicrosoftWord+ 0x00af6cbc)
# 18 0x00b00be8 in _wdCommandDispatch + 0x007D7DE0 (MicrosoftWord+ 0x00affbe8)
# 19 0x022e7bbc in __WlmMain + 0x00000050 (MicrosoftOffice + 0x004dbbbc)
# 20 0x00ae5454 in _wdCommandDispatch + 0x007BC64C (MicrosoftWord+ 0x00ae4454)
# 21 0x000032c0 in __mh_execute_header + 0x000022C0 (MicrosoftWord+ 0x000022c0)
# 22 0x00002fc4 in __mh_execute_header + 0x00001FC4 (MicrosoftWord+ 0x00001fc4)

PPC Thread State:
srr0: 0x0034a844 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x008a4da4 ctr: 0x000000be mq:0x00000000
r0: 0x000000be r1: 0xbfffdf80 r2: 0x00000000 r3:0x00000001
r4: 0x050d83ac r5: 0x00000004 r6: 0xfe000000 r7:0xbfffdfb8
r8: 0x11efc080 r9: 0x626c655f r10: 0x014b30d0 r11:0x00000000
r12: 0x05957bf6 r13: 0xbfffe060 r14: 0x01410000 r15:0x01410000
r16: 0x01410000 r17: 0x01410000 r18: 0x01410000 r19:0x013d0000
r20: 0x01410000 r21: 0x014b3460 r22: 0x014ba490 r23:0x01410000
r24: 0x01410000 r25: 0xbfffdfd4 r26: 0xbfffdfc8 r27:0x00000000
r28: 0xbfffdfc0 r29: 0x00000000 r30: 0xbfffdfbc r31:0x014b30e0

Thread 1:

# 1 0x93e7aaf8 in _atantblEntry + 0x93CA0328 (libSystem.B.dylib + 0x00001af8)
# 2 0x93f06910 in _atantblEntry + 0x93D2C140 (libSystem.B.dylib + 0x0008d910)
# 3 0x93f1dcdc in _atantblEntry + 0x93D4350C (libSystem.B.dylib + 0x0

Hi,

Why not try Advanced Word Repair at http://www.datanumen.com/awr/ ?
It recovers several important Word documents for me and is really
helpful!

Alan

Gabriel · Apr 4, 2008

I noticed that you are still using the 12.0.0 version. Run a microsoft update, that should do the trick. The same was happening to me, except Word would just crash at the start. Now it works for me. The updater is in /Library/Application Support/Microsoft/MAU2.0 run that and it should have some updates to install. :smile: :worried:

John McGhie · Apr 6, 2008

Because, you brain-dead piece of slime, it does not run on a Macintosh!! I
assume this is the level of intellectual effort that went into the
development of all your products, so they must all be rubbish!

Sorry people, we have a persistent spammer aboard.

We'll get rid of him, but it will take time!

Hi,

Why not try Advanced Word Repair at http://www.datanumen.com/awr/ ?
It recovers several important Word documents for me and is really
helpful!

Alan

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]

Mac Word shuts down sometimes when saving ordoing spell check in another language	1	May 31, 2009
Word Crashes when selecting help menu	6	Nov 27, 2008
Word 2008 Will Not Launch on iMac G5	3	Jan 16, 2008
Word 2008 crashes after update	5	Mar 7, 2009
Word crash - don't know the reason	8	May 5, 2009
No luck with Word 2008: crash at launch	6	Apr 19, 2008
Error upon opening any word document or clicking on the help	6	May 13, 2010
Word crashing after 12.1.2 update	12	Aug 27, 2008

Word 2008 Crashes Consistently

Alpaca

CyberTaz

Alpaca

John McGhie

Alpaca

John McGhie

Alpaca

John McGhie

David Rood

Beth Rosengard

Albuquer-JAY

Emilyz

Emilyz

John McGhie

mxk

mxk

mxk

mxk

Gabriel

John McGhie

Ask a Question

Similar Threads