Word crashes after I use spell check

C

Cassandra

This is a new problem --- everything was fine until about a week ago. I'm using Word 2004 for Mac and each time I do spell check it crashes. If I cancel the spell check before it's finished, it's OK but if I wait until the dialogue box comes up it's too late and it seems to be getting worse. Here's the error message - any ideas?
Microsoft Error Reporting log version: 1.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-03-04 14:05:26 +1100
Application Name: Microsoft Word
Application Version: 11.3.8.070817
Module Name: MCPZ.stb
Module Version: 11.4.0.080117
Module Offset: 0x0006aed8
Extra app info: Reg=English Loc=0x0409

Thread 0 crashed:

# 1 0x005dbe68 in (MCPZ.stb + 0x0006aed8)
# 2 0x02381f34 in (Microsoft Word + 0x003624d4)
# 3 0x0261dea0 in (Microsoft Word + 0x005fe440)
# 4 0x0212f08c in (Microsoft Word + 0x0010f62c)
# 5 0x021d4fe4 in (Microsoft Word + 0x001b5584)
# 6 0x026e1e14 in (Microsoft Word + 0x006c23b4)
# 7 0x020f3b70 in (Microsoft Word + 0x000d4110)
# 8 0x01020820 in (Microsoft_Office_2001Z + 0x0000a280)
# 9 0x01020bb8 in (Microsoft_Office_2001Z + 0x0000a618)
# 10 0x010502f8 in (Microsoft_Office_2001Z + 0x00039d58)
# 11 0x0104fddc in (Microsoft_Office_2001Z + 0x0003983c)
# 12 0x0104fdac in (Microsoft_Office_2001Z + 0x0003980c)
# 13 0x00593b38 in (MCPZ.stb + 0x00022ba8)
# 14 0x901c516c in ___CFRunLoopDoTimer + 0x000000F0 (CoreFoundation + 0x0000516c)
# 15 0x901c24cc in ___CFRunLoopRun + 0x000005C4 (CoreFoundation + 0x000024cc)
# 16 0x901c69e0 in _CFRunLoopRunSpecific + 0x00000144 (CoreFoundation + 0x000069e0)
# 17 0x92886e0c in _RunCurrentEventLoopInMode + 0x000000A8 (HIToolbox + 0x00006e0c)
# 18 0x9288d4b0 in _ReceiveNextEventCommon + 0x000000F0 (HIToolbox + 0x0000d4b0)
# 19 0x928fe6b0 in _ReceiveNextEventInMode + 0x00000044 (HIToolbox + 0x0007e6b0)
# 20 0x0059381c in (MCPZ.stb + 0x0002288c)
# 21 0x020f3ab8 in (Microsoft Word + 0x000d4058)
# 22 0x020205f8 in (Microsoft Word + 0x00000b98)
# 23 0x01023460 in (Microsoft_Office_2001Z + 0x0000cec0)
# 24 0x02020074 in (Microsoft Word + 0x00000614)
# 25 0x02b070ac in (Microsoft Word + 0x00ae764c)

PPC Thread State:
srr0: 0x005dbe68 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000002 lr: 0x02381f34 ctr: 0x006b5300 mq:0x00000000
r0: 0x006b5300 r1: 0xbfffdff0 r2: 0x0077d000 r3:0x00000000
r4: 0x00000001 r5: 0x006d2580 r6: 0x01878bdf r7:0x00000000
r8: 0x00000000 r9: 0x00000000 r10: 0x00000784 r11:0x00001100
r12: 0x0077daa0 r13: 0x00000000 r14: 0x00000000 r15:0x00000001
r16: 0x00000058 r17: 0x00000157 r18: 0x00000004 r19:0xbfffeb30
r20: 0x00df00a7 r21: 0x00000006 r22: 0x00000000 r23:0x031750c0
r24: 0x0317343c r25: 0x0317b850 r26: 0x0316cf74 r27:0x03171a78
r28: 0x01a20400 r29: 0x00000000 r30: 0x00000006 r31:0x00000001

Thread 1:

# 1 0x900127c8 in _clock_sleep_trap + 0x00000008 (libSystem.B.dylib + 0x000127c8)
# 2 0x9000d9b8 in _nanosleep + 0x00000078 (libSystem.B.dylib + 0x0000d9b8)
# 3 0x9002d9a8 in _sleep + 0x00000048 (libSystem.B.dylib + 0x0002d9a8)
# 4 0x0177115c in _MerpUnregisterCFMFragment + 0x00000BAC (ShMem + 0x0006715c)
# 5 0x01770628 in _MerpUnregisterCFMFragment + 0x00000078 (ShMem + 0x00066628)
# 6 0x01770754 in _MerpUnregisterCFMFragment + 0x000001A4 (ShMem + 0x00066754)
# 7 0x01771234 in _MerpUnregisterCFMFragment + 0x00000C84 (ShMem + 0x00067234)
# 8 0x9002492c in __pthread_body + 0x00000024 (libSystem.B.dylib + 0x0002492c)

PPC Thread State:
srr0: 0x900127c8 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x00000004 lr: 0x9000d9b8 ctr: 0x900127c0 mq:0x00000000
r0: 0xffffffc2 r1: 0xf0080af0 r2: 0xf0080ac4 r3:0x00000507
r4: 0x00000001 r5: 0x00000001 r6: 0x00000000 r7:0xf0080b30
r8: 0x00000000 r9: 0x000063ae r10: 0x1aa899d8 r11:0xa000470c
r12: 0x900127c0 r13: 0x00000000 r14: 0x00000000 r15:0x00000000
r16: 0x
 
J

John McGhie

Is this all documents or just a particular document?

Which languages are marked in the text (which languages are in use)?

Cheers


This is a new problem --- everything was fine until about a week ago. I'm
using Word 2004 for Mac and each time I do spell check it crashes. If I cancel
the spell check before it's finished, it's OK but if I wait until the dialogue
box comes up it's too late and it seems to be getting worse. Here's the error
message - any ideas?
Microsoft Error Reporting log version: 1.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-03-04 14:05:26 +1100
Application Name: Microsoft Word
Application Version: 11.3.8.070817
Module Name: MCPZ.stb
Module Version: 11.4.0.080117
Module Offset: 0x0006aed8
Extra app info: Reg=English Loc=0x0409

Thread 0 crashed:

# 1 0x005dbe68 in (MCPZ.stb + 0x0006aed8)
# 2 0x02381f34 in (Microsoft Word + 0x003624d4)
# 3 0x0261dea0 in (Microsoft Word + 0x005fe440)
# 4 0x0212f08c in (Microsoft Word + 0x0010f62c)
# 5 0x021d4fe4 in (Microsoft Word + 0x001b5584)
# 6 0x026e1e14 in (Microsoft Word + 0x006c23b4)
# 7 0x020f3b70 in (Microsoft Word + 0x000d4110)
# 8 0x01020820 in (Microsoft_Office_2001Z + 0x0000a280)
# 9 0x01020bb8 in (Microsoft_Office_2001Z + 0x0000a618)
# 10 0x010502f8 in (Microsoft_Office_2001Z + 0x00039d58)
# 11 0x0104fddc in (Microsoft_Office_2001Z + 0x0003983c)
# 12 0x0104fdac in (Microsoft_Office_2001Z + 0x0003980c)
# 13 0x00593b38 in (MCPZ.stb + 0x00022ba8)
# 14 0x901c516c in ___CFRunLoopDoTimer + 0x000000F0 (CoreFoundation +
0x0000516c)
# 15 0x901c24cc in ___CFRunLoopRun + 0x000005C4 (CoreFoundation + 0x000024cc)
# 16 0x901c69e0 in _CFRunLoopRunSpecific + 0x00000144 (CoreFoundation +
0x000069e0)
# 17 0x92886e0c in _RunCurrentEventLoopInMode + 0x000000A8 (HIToolbox +
0x00006e0c)
# 18 0x9288d4b0 in _ReceiveNextEventCommon + 0x000000F0 (HIToolbox +
0x0000d4b0)
# 19 0x928fe6b0 in _ReceiveNextEventInMode + 0x00000044 (HIToolbox +
0x0007e6b0)
# 20 0x0059381c in (MCPZ.stb + 0x0002288c)
# 21 0x020f3ab8 in (Microsoft Word + 0x000d4058)
# 22 0x020205f8 in (Microsoft Word + 0x00000b98)
# 23 0x01023460 in (Microsoft_Office_2001Z + 0x0000cec0)
# 24 0x02020074 in (Microsoft Word + 0x00000614)
# 25 0x02b070ac in (Microsoft Word + 0x00ae764c)

PPC Thread State:
srr0: 0x005dbe68 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000002 lr: 0x02381f34 ctr: 0x006b5300 mq:0x00000000
r0: 0x006b5300 r1: 0xbfffdff0 r2: 0x0077d000 r3:0x00000000
r4: 0x00000001 r5: 0x006d2580 r6: 0x01878bdf r7:0x00000000
r8: 0x00000000 r9: 0x00000000 r10: 0x00000784 r11:0x00001100
r12: 0x0077daa0 r13: 0x00000000 r14: 0x00000000 r15:0x00000001
r16: 0x00000058 r17: 0x00000157 r18: 0x00000004 r19:0xbfffeb30
r20: 0x00df00a7 r21: 0x00000006 r22: 0x00000000 r23:0x031750c0
r24: 0x0317343c r25: 0x0317b850 r26: 0x0316cf74 r27:0x03171a78
r28: 0x01a20400 r29: 0x00000000 r30: 0x00000006 r31:0x00000001

Thread 1:

# 1 0x900127c8 in _clock_sleep_trap + 0x00000008 (libSystem.B.dylib +
0x000127c8)
# 2 0x9000d9b8 in _nanosleep + 0x00000078 (libSystem.B.dylib + 0x0000d9b8)
# 3 0x9002d9a8 in _sleep + 0x00000048 (libSystem.B.dylib + 0x0002d9a8)
# 4 0x0177115c in _MerpUnregisterCFMFragment + 0x00000BAC (ShMem + 0x0006715c)
# 5 0x01770628 in _MerpUnregisterCFMFragment + 0x00000078 (ShMem + 0x00066628)
# 6 0x01770754 in _MerpUnregisterCFMFragment + 0x000001A4 (ShMem + 0x00066754)
# 7 0x01771234 in _MerpUnregisterCFMFragment + 0x00000C84 (ShMem + 0x00067234)
# 8 0x9002492c in __pthread_body + 0x00000024 (libSystem.B.dylib + 0x0002492c)

PPC Thread State:
srr0: 0x900127c8 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x00000004 lr: 0x9000d9b8 ctr: 0x900127c0 mq:0x00000000
r0: 0xffffffc2 r1: 0xf0080af0 r2: 0xf0080ac4 r3:0x00000507
r4: 0x00000001 r5: 0x00000001 r6: 0x00000000 r7:0xf0080b30
r8: 0x00000000 r9: 0x000063ae r10: 0x1aa899d8 r11:0xa000470c
r12: 0x900127c0 r13: 0x00000000 r14: 0x00000000 r15:0x00000000
r16: 0x

--
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
 

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

Top