Word crashed on 10.4.7

Hello
Last night I updated to 10.4.7.
It isn't buggy at all. For the first part of the day everything seems te be normal (Entourage, Excel, Firefox, GraphicConverter, Acrobat.
But when I openend Word and edit some old text I recognised a strange behaviour. I got message from all the programms that are open in background that they unexpectedly. The last Program that crashes is Word. Then the finder crashed and rebootet with a (mac) bluescreen.
After a reboot the same problem!
After a reboot and a permission repair with the harddisk utilty program still the same problem.
So I would suggest that the ßeta-testers has done a very bad job (and also the quality control of Apple)
I don't know if the problem also occured on a PPC Mac. I own an Intel MacBook Pro

Welcome to Apple Discussions!
iMac G5 has no problem from Print or Print Preview with Excel on an 18 page document. Your problem must be with something else. Please start a new topic thread if your issue is not resolved by this existing thread:
http://discussions.apple.com/forum.jspa?forumID=752&start=0
First off, you'll get a wider audience who may be able to solve your problem. Secondly, responses to you won't confuse the original poster with solutions that don't apply to them. And thirdly, you'll know for certain whether or not a response applies to you.

Similar Messages

  • Last night I downloaded the latest Word update. Today the first Word document crashed and I lost 45 minutes of work in spite of having saved the document numerous times. Why is Word crashing the day after a safety update? I have Office 2008 for Mac

    Last night I downloaded the latest Word update. Today the first Word document crashed and I lost 45 minutes of work in spite of having saved the document numerous times. Why is Word crashing the day after a safety update? I have Office 2008 for Mac

    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.
    If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.
    Check the System Preferences>Other Row, for 3rd party Pref Panes.
    Also look in these if they exist, some are invisible...
    /private/var/run/StartupItems
    /Library/StartupItems
    /System/Library/StartupItems
    /System/Library/LaunchDaemons
    /Library/LaunchDaemons
    Open Console in Applications>Utilities, check the system log for the date/time of the last problem  & next startup for clues.

  • Word crashes mid PDF creation - Word 2003 Acrobat 9.3.0

    I have a new PC and a fresh clean install of CS5 Design Permuim, including Arobat 9. The organisation is still using Office 2003 and no upgrade path in sight for that. Myself and several colleagues with the same software profile are now experiencing frequent problems with Word crashing mid PDF creation.
    This has always been an issue with the ocassional Word file in Acrobat 8, but Distiller always worked as an alternative - NOT this time!
    PDF Maker gives no error message, just that Word has encounted a problem and needs to close.
    Distiller produces the following log message, then freezes completely. I then have to force quit Word to exit!
    %%[ ProductName: Distiller ]%%
    %%[ Error: syntaxerror; OffendingCommand: --nostringval-- ]%%
    Stack:
    /mF_OTF_V
    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%
    Not all documents are affected, but I can remove almost all of the content from the affected document and it still causes the error.
    I have tried repairing Acrobat - no change.
    One other odd symptom - after each crash, the default printer on the machine has changed to Adobe PDF.
    I can successfulkly make the PDF on another machine which has not been upgraded to Acrobat 9. The rest of the settings are identical on the two machines, they are both running a standard organisation environment, with the same verion of word etc.
    Can anyone suggest how to fix or at least isolate the cause of the problem?

    Please update to latest Acrobat 9 release which is 9.4.2.
    Also do let us know
    a) office 2003 flavour: Standard or professional?
    b) OS flavour? Also whether it is 32bit or 64bit?
    Also as you mentioned that "Not all documents are affected", so we would require any of your affected file to analyze the issue. Can you please share the file? You can use acrobat.com to share the file.
    Thanks,
    Vishal

  • 2013 word crashes when "save as" .Word freezes "not responding after a few minutes.

    2013 word crashes  when using the "save as" command. It does save the document but crashes. After working for 3 minutes or so on a document the programme will stop running with the screen frozen. Have to use the windows task manager to close.
    Any ideas? Very disappointed as I have already also spent a day trying to get outlook to work using all the advice on these forums. Just not impressed. I'm I going to have the same issues with excel?

    Hi,
    In regarding of the issue, it may be caused some reason, let's try to narrow down the root cause with the following methods:
    1.Try disable all the add-ins to see if this behavior could be caused by the 3rd-party add-ins, if this behavior won't occur with all the add-ins disabled, we can enable them one by one to find out which one might cause the issue.
    2.Try repair your Office as a quick fix
    3.Try start Word in
    safe mode to see if this behavior will still occur, if this behaivor won't occur in safe mode, the behavior might be caused by certain items that are loaded with Word.
    4.Try configure Windows in
    clean boot mode to check if this behavior could be caused by the 3rd-party services, if this behavior won't occur in clean boot mode, try follow the instructions in the
    How to determine what is causing the problem by performing a clean boot section in the following support article:
    http://support.microsoft.com/kb/929135
    Here is a similar issue:
    http://social.technet.microsoft.com/Forums/en-US/0d2ed46c-ba1c-4107-9651-9ff97d583720/microsoft-word-2007-freezes-when-saving?forum=word
    We could try to Delete the Word Data registry subkey to test.please try follow the instructions in the following support article:
    http://support.microsoft.com/kb/921541
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word\Data
    Note: Backup your registry key before you modified.
    Regards,
    George Zhao
    TechNet Community Support

  • Microsoft word crashes when I open a file or try to save document

    Every time I try to open an existing document or save a new one Microsoft word crashes.  I am able to start a new document but if I try to save it all of the action/editing buttons fade/unhighlight (save, print, quit, copy paste, etc) and I am ubable to do anything.  However, most of the buttons in view, history, bookmarks, tools, window & help still work.  Then I have to force quit because the option to quit is no longer available.
    Please help.  I can no longer open & create new documents

    Are you using Office 2004 and did you install the recent security update? If so then open Software Update and download and install the new security update version which should fix the issue.

  • Word Crashing When Discarding Checkout for Document Stored in SharePoint

    We have recently noticed an issue when we have a Word file checked out from SharePoint, if we then discard the checkout from Word, Word crashes. The error details point to an issue in wwlib.dll.
    Having done some further investigation into this it appears this only happens if the document has an attached template which contains a custom ribbon.  We use SharePoint 2013 and Word 2010, although I have tested using Word 2013 with the same results.
    This was noticed on our company templates which contain a custom ribbon tab and a number of custom buttons. I have since tested it by creating a template with a single button on a custom tab with the same results.
    Has anyone else come across this issue and and is there any way to resolve it?
    Thanks,
    Richard

    Hi Daniel,
    Thanks for the response.
    The issue only happens when discarding checkout. Editing and saving a document back to SharePoint does not cause an issue. I am using a dotm template. I am not storing the template
    as a content type. When I say I created a custom tab, this was created by adding the XML to create the ribbon tab and button. I used the 'Custom UI Editor for Microsoft Office' to add this. The file created for this is called customUI14.xml and the
    XML is as follows (in the basic test template that I created):
    <customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">
    <ribbon startFromScratch="false">
    <tabs>
    <tab id="customTab" label="Custom Tab">
    <group id="customGroup" label="Custom Group">
    <button id="customButton" label="Test Ribbon Button" imageMso="HappyFace" size="large" onAction="TestRibbonCrash" />
    </group>
    </tab>
    </tabs>
    </ribbon>
    </customUI>
    The code this points to is as follows:
    Sub TestRibbonCrash(ByRef Ctrl As IRibbonControl)
        MsgBox "Ribbon button working"
    End Sub
    Following your reply I have tested it by adding a custom tab and button through the GUI and the problem doesn't occur when using that method of creating the tab and button.
    I will see if I can find anything useful in the ULS logs although no correlation ID is displayed when the error happens and in my experience even with a correlation ID, 99% of the time the ULS logs don't provide any useful information.
    I've also observed that Word doesn't crash if I discard checkout when I have another document open at the same time which is based on the same template.
    I have already posted on a MS Word forum. Is there more chance of getting some help on one of the other Word forums you have suggested?
    http://answers.microsoft.com/en-us/office/forum/office_2010-word/word-crashing-when-discarding-checkout-for/95565f9e-411b-4f11-b14d-d3771e2e2ba4
    Thanks,
    Richard

  • MS Word crashes when I do find/replace with the OS X 10.5.6

    Does anyone know what I can do about MS Word crashing when I do a find and/or replace in a document? It happens constantly. The interesting thing is that is doesn't occur every single time I do find/replace but the SECOND time I use the feature. The only way I can manage to avoid the crash is to do find/replace, then exit out of the dialog box, and then open it up again. If I do a find/replace once and then continue using the same dialog box, Word crashes. Also, find/replace doesn't work most of the time.
    This never happened when I was using Word with my older OS.
    Help, please!!!
    Many thanks.

    Hmm...what about deleting the MS Word preferences? Does excel crash as well when doing the same function?
    To delete the preference put this in spotlight:
    com.microsoft.Word.plist
    Move it to the desktop, restart and see if the problem persists.
    It might be another preference that is the source of the problem.

  • Word crash with sharepoint document and copy-pasting image from paint

    Initially I've posted this to another forum but there the rec was to post it here as well.
    I have a very annoying issue occurring in specific circumstances (but unfortunately for me that is my daily work), it happens when a document is stored on a SharePoint server. When I copy-paste an image from ms paint into word, often I get the message 'word
    has encountered an error' but then I can continue, but every 5-10 times Word crashes completely.
    When the error (not the crash) occurs, there is this nothing-saying error message stated below. Think of it.. my ‘floppy disk’ is not full, I have 8 GB of ram and I’ve all the permissions I require. The virus scanner is Symantec Endpoint
    Protection.
    All systems are in a world-wide enterprise environment (>20.000 users) – So I guess from that side everything is configured OK.
    There is a problem saving the file.
    Usually this is because the disk or floppy disk is too small for the file or is full, RAM memory is low, or there is a permission problem with the drive the file is being saved to.
    If the amount of disk space for a paging file is low, save the file to another drive. If the RAM memory is low, increase available RAM. If permissions to the drive do not allow you to save to that drive, save the file to another drive or request
    permissions from the administrator to save files to the drive.
    Note   This error can also occur if the computer is running a version of antivirus software that is incompatible with the Microsoft Office or must be updated.

    Hi,
    What is the version of Word?
    Sometimes the Preview Pane in Windows File Explorer may conflict with Word, thus the error message appears. If you have enabled the Preview Pane in File Explorer, disable it to check the result. For example, in Windows 8.1, Open File Explorer, click
    View tab on the top -> Panes -> Click Preview Pane to enable or disable it.
    If the issue persists, I suggest you collect the event logs to find the cause of the crash:
    Press Win + R, type "eventvwr" in the blank box, press Enter to open Event Viewer. Browse to Windows Logs -> Application, check if there is any error about the crash.
    You can send the event logs to our email address and we can help analyze the problem:
    [email protected]
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • MS Word Crashes after saving document

    I'm using MS Office 2011. After upgrading my Macbook Pro to OS X 10.9.4, my Microsoft Word (version 14.4.3) crashes after saving a Word document. I've tried using Word in Safe Boot and the same crashing happens after two or three saves to the Word document I'm working on. I've also tried emptying the AutoRecovery folder, and moving the files "com.microsoft.Word.plist" and "Normal" to the desktop. All to no avail. Word still crashes after two or three saves to the document. Please help! It's so frustrating to lose the changes I'm making in a document due to Word crashing after saving.

    First test in a new User to verify that Office is now working correctly in another User. Log into Guest User or create a new User in System Preferences.
    If the problem goes away, the problem is in your User's account.
    If the problem exists in the new User.... you need to reinstall Office.
    Be sure to fully update after reinstalling.
    Be sure you have your CD Key for activation.
    Updaters have to be applied in order. Depending on what version installer you have, there are only two combo updaters that you might need.
    (If you have an early installer you'll first need to update to 14.1.0)
    Microsoft Office for Mac 2011 Service Pack 1 (14.1.0)
    http://www.microsoft.com/en-us/download/details.aspx?id=17198
    (Later installers installed 14.2 or higher.)
    Microsoft Office for Mac 2011 14.4.3 Update (requires 14.1.0 or newer)
    http://www.microsoft.com/en-us/download/confirmation.aspx?id=43378
    Install Basics
    Not only should Safari be quit but all browsers and hidden Microsoft processes like the Microsoft Database daemon and SyncServicesAgent. To disable these applications:
    Log out under the Apple in the Menu bar
    Log in and hold down the Shift key (this disables all startup items including the hidden ones)
    Restart after installing 14.1.0 and again after installing 14.4.3
    Note for the MAU and MERP updaters you do NOT have to restart after updating. These are found in the root Library:
    /Library/Application Support/Microsoft/
    Why Restart?
    The Restart after updater will force a file that stores the version info to update. This should happen automatically but sometimes it doesn't. The next updater will fail and you will have to re-install Office. The restart is a quick step that will save time in the long term.

  • Word Crashes after changing the style of 'Bullets'

    Hi,
    I hope someone can help me this problem. The problem occurs when I use Microsoft Word 2004 for Mac.
    Word crashes when I go into the Formatting Palette > Bullets and Numbering and then try to change the style of the bullet. I noticed that in the drop down box of bullet styles there are two or three blanks spaces rather than an actual bullet. Then when I move the mouse over the blank entries in order to click on an actual bullet style, Word crashes.
    Should I uninstall Word and then reinstall it? Or is there a much simpler way of fixing the problem?
    I have only had my MacBook for 10 days and I am already having so many problems with Microsoft Word.
    Thanks in advance.
      Mac OS X (10.4.9)  

    Since Word is not an Apple product, you'll get better response if you use a forum dedicated to Microsoft's Mac products such as <http://groups.google.com/groups/dir?sel=33607053> rather than an Apple forum.
    Be sure to search the forum first in case someone has already had a similar question answered. You'll get your answer faster this way. Post your question in the forum if you don't find anything that helps you.

  • Word crashes when I try to save after installing the Canon driver.

    I have Windows Vista running Microsoft Office 2007.  Word was working just fine until I installed the Canon MX432 driver. Now every time I try to save a document, Word crashes.  I have tried to repair Office.  I have uninstalled and reinstalled the Office program.  I have closed the Canon solutions menu on the desktop.  Nothing works.  Any suggestions?

    I love these stab in the dark solutions (on my part)...here goes...
    If I were you, I'd try changing the printer default to something other than the MX432 just in case Word doesn't like the new printer.  If that solves the crashing problem, try to  reinstall the driver again before setting the printer default to the MX432.  Are you sure you've got the driver that is compatible with Vista?  Vista is finicky when it comes to drivers.  
    If that doesn't work at all, I'd do a driver uninstall then a system restore to before the install.  This will put everything back to when it was hunky dory, as they say.  G'luck.

  • MS Word crash when exporting to PDF, and font style is bold

    If i try to convert a doc file to PDF from Microsoft Word using fonts like Times New Roman, everything works fine; by using a font like Myriad Pro, Minion pro, etc. if i use even a single word in BOLD style, with other plain text, during export Word crashes, faulting in module pscript5.dll.
    Any information about this problem?
    Thanks.

    >issue with the latest version of Acrobat and not previous versions?
    I certainly don't work for Adobe, so this is only a GENERAL comment, based on many years experience with many different programs from several vendors
    When a program goes from 8.0 to 8.1 it is usually bug fixes but no major changes to the actual source code
    When a program goes from 7.0 to 8.0 that usually indicates major changes in function AND in the source code to create the program
    As an application programmer (used to be COBOL, now in a different job and use MS Access) I know that any program with more than a few hundred lines of source code WILL have problems
    When you consider that Acrobat is most likely written in C/C++ and will most likely have MANY thousands of lines of source code... it is not at all surprising that it went from 8.0 to 8.1.0 to 8.1.1
    It would not surprise me at all if Acrobat's routines for checking and using fonts had changes in that part of the source code... and IF that happened it MAY be that font handling is either "stricter" and that leads to "catching" a font that is "marginal" in operation... or that the error trapping routine changed and is causing a problem
    I personally have no idea if a corrupt font is your problem, but it does not surprise me at all that a 7.0 to 8.0 program change COULD introduce changes in the way fonts are processed

  • WORD crashes in Yosemite OS 10.10

    Hi,
    I am posting again, since my previous post got deleted somehow.
    I am writing my thesis using microsoft office for mac 2011, microsoft word
    I upgraded the operating system yesterday, with excitement
    However, i found out today that whenever i try to open my thesis (many pages), word opens it up for few mins and then suddenly terminate itself.
    I am wondering if anyone else has experience the problem.

    I have seen yes and no but that was on Yosemite forum (very busy as can imagine) and on MBP
    OS X Yosemite
    And of course like every new OS,
    wait, check for updates, make sure you have a safety net (clone of prior system), check RoaringApps
    http://roaringapps.com/apps?index=a
    One of my favorites:
    http://www.xlr8yourmac.com/
    http://www.macintouch.com/
    Both tend to be good for getting and central "clearing house" for reports that otherwise get lost in forums.
    Apple already has some Yosemite Security Software Updates.
    You mean this thread?
    microsoft word crashes on yosemite

  • Microsoft Word crashes as soon is it is clicked on

    Microsoft Word crashes as soon as I open it on one of our teachers' MacBooks running OS X 10.6.1.  It bounces in the dock for several seconds and the gives and error report.  The report can be seen below.  Any ideas?  Thanks in advance.
    Process:         Word [860]
    Path:            /Applications/Microsoft Office X/Microsoft Word
    Identifier:      com.microsoft.Word
    Version:         10.1.1 (10.1.1)
    Code Type:       PPC (Translated)
    Parent Process:  launchd [757]
    Date/Time:       2011-12-06 13:50:45.336 -0500
    OS Version:      Mac OS X 10.6.1 (10A2062)
    Report Version:  6
    Interval Since Last Report:          441 sec
    Crashes Since Last Report:           5
    Per-App Interval Since Last Report:  5 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                      F7F2C32E-3360-4EE1-82D2-9A8672DB3C4E
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   LaunchCFMApp                            0xb80c5e94 0xb8000000 + 810644
    1   LaunchCFMApp                            0xb80c01bb 0xb8000000 + 786875
    2   LaunchCFMApp                            0xb80dda6c 0xb8000000 + 907884
    3   LaunchCFMApp                            0xb8145da1 spin_lock_wrapper + 3973
    4   LaunchCFMApp                            0xb801d03b 0xb8000000 + 118843
    Thread 1:
    0   libSystem.B.dylib                       0x800c57da mach_msg_trap + 10
    1   libSystem.B.dylib                       0x800c5f47 mach_msg + 68
    2   LaunchCFMApp                            0xb819448f CallPPCFunctionAtAddressInt + 206155
    3   libSystem.B.dylib                       0x800f2f39 _pthread_start + 345
    4   libSystem.B.dylib                       0x800f2dbe thread_start + 34
    Thread 2:
    0   LaunchCFMApp                            0xb815ae44 spin_lock_wrapper + 90152
    1   LaunchCFMApp                            0xb8179d27 CallPPCFunctionAtAddressInt + 97763
    2   LaunchCFMApp                            0xb80c6c97 0xb8000000 + 814231
    3   LaunchCFMApp                            0xb80c01bb 0xb8000000 + 786875
    4   LaunchCFMApp                            0xb80dda6c 0xb8000000 + 907884
    5   LaunchCFMApp                            0xb814551b spin_lock_wrapper + 1791
    6   LaunchCFMApp                            0xb801d03b 0xb8000000 + 118843
    Thread 3:
    0   LaunchCFMApp                            0xb815aa83 spin_lock_wrapper + 89191
    1   LaunchCFMApp                            0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2   LaunchCFMApp                            0xb80c6c97 0xb8000000 + 814231
    3   LaunchCFMApp                            0xb80c01bb 0xb8000000 + 786875
    4   LaunchCFMApp                            0xb80dda6c 0xb8000000 + 907884
    5   LaunchCFMApp                            0xb814551b spin_lock_wrapper + 1791
    6   LaunchCFMApp                            0xb801d03b 0xb8000000 + 118843
    Thread 4:
    0   LaunchCFMApp                            0xb815aa83 spin_lock_wrapper + 89191
    1   LaunchCFMApp                            0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2   LaunchCFMApp                            0xb80c6c97 0xb8000000 + 814231
    3   LaunchCFMApp                            0xb80c01bb 0xb8000000 + 786875
    4   LaunchCFMApp                            0xb80dda6c 0xb8000000 + 907884
    5   LaunchCFMApp                            0xb814551b spin_lock_wrapper + 1791
    6   LaunchCFMApp                            0xb801d03b 0xb8000000 + 118843
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0xb80c5e6c  ecx: 0x00000000  edx: 0x0000001f
      edi: 0x00000000  esi: 0x804037f0  ebp: 0xb7fffa08  esp: 0xb7fff9d0
       ss: 0x0000001f  efl: 0x00010202  eip: 0xb80c5e94   cs: 0x00000017
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
      cr2: 0x00000000
    Binary Images:
    0x80000000 - 0x8006afe7  libstdc++.6.dylib ??? (???) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
    0x800c5000 - 0x80269feb  libSystem.B.dylib ??? (???) <37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib
    0x802e9000 - 0x802ecfe7  libmathCommon.A.dylib ??? (???) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x8fe00000 - 0x8fe4162b  dyld 132.1 (???) <226BF7A0-94E0-2F4C-6D6B-9189C952331C> /usr/lib/dyld
    0xb8000000 - 0xb81defff  LaunchCFMApp ??? (???) <3E4E06B8-E1FC-B232-1371-643DC0FBE8C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
    0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???) <37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib
    Translated Code Information:
    Rosetta Version:  22.23
    Args:            /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMAp p /Applications/Microsoft Office X/Microsoft Word
    Exception: EXC_BAD_ACCESS (0x0001)
    Thread 0: (0xb009ad38, 0xb815ae44)
    0x92ac0588: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
    0x92ac00c0: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 320
    0x92ac0244: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 364
    0x92ac0380: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
    0x929e0da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0
    PPC Thread State
    srr0: 0x00000000          srr1: 0x00000000                                 vrsave: 0x00000000
    cr:  0xXXXXXXXX                    xer: 0x20000000                     lr: 0x92ac0550                    ctr: 0x929842d4
    r00: 0x0000016b           r01: 0xf0080bb0           r02: 0x00000000           r03: 0x00000004
    r04: 0x00000000           r05: 0x00000000           r06: 0xf0080d0c           r07: 0x00000001
    r08: 0xf0080d28           r09: 0x00000000           r10: 0x0000003c           r11: 0xa0455524
    r12: 0x929842d4           r13: 0x10624dd3           r14: 0x92b0fb2c           r15: 0xf0080c0c
    r16: 0xf0080c8c           r17: 0xa04704ac           r18: 0xf0080d28           r19: 0xa046a4f8
    r20: 0xa046b4f8           r21: 0xf0080d0c           r22: 0xa046a478           r23: 0xa046a3f8
    r24: 0xa04704ac           r25: 0x00000000           r26: 0x00000000           r27: 0xa045c5c8
    r28: 0xa045c300           r29: 0xa045c5c8           r30: 0xf0080d28           r31: 0x92ac04ac
    Thread 1: (0xb019ed74, 0xb815aa83)
    0x92ac20b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
    0x92ac03a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
    0x929e0da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0
    PPC Thread State
    srr0: 0x00000000          srr1: 0x00000000                                 vrsave: 0x00000000
    cr:  0xXXXXXXXX                    xer: 0x20000000                     lr: 0x92ac20cc                    ctr: 0x929406c0
    r00: 0xffffffda           r01: 0xf0182dc0           r02: 0x00000000           r03: 0x00002403
    r04: 0x00000040           r05: 0x3b9a8e95           r06: 0x00000020           r07: 0x00000000
    r08: 0x3b9a8e95           r09: 0x00000000           r10: 0x3b9a8e95           r11: 0xa0456670
    r12: 0x929406c0           r13: 0x00000000           r14: 0x00000000           r15: 0x00000000
    r16: 0x00000000           r17: 0x00000000           r18: 0x00000000           r19: 0x00000000
    r20: 0x00000000           r21: 0xa045c790           r22: 0xa045c784           r23: 0xa045c78c
    r24: 0x00001709           r25: 0x111a8642           r26: 0xa045c4d0           r27: 0x00000040
    r28: 0x0000000f           r29: 0x224d0e95           r30: 0xa045c764           r31: 0x92ac1fc4
    Thread 2: (0xb011cd74, 0xb815aa83)
    0x92ac20b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
    0x92ac03a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
    0x929e0da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0
    PPC Thread State
    srr0: 0x00000000          srr1: 0x00000000                                 vrsave: 0x00000000
    cr:  0xXXXXXXXX                    xer: 0x20000000                     lr: 0x92ac20cc                    ctr: 0x929406c0
    r00: 0xffffffda           r01: 0xf0101dc0           r02: 0x00000000           r03: 0x00002403
    r04: 0x00000040           r05: 0x3b9ab336           r06: 0x00000020           r07: 0x00000000
    r08: 0x3b9ab336           r09: 0x00000000           r10: 0x3b9ab336           r11: 0xa0456670
    r12: 0x929406c0           r13: 0x00000000           r14: 0x00000000           r15: 0x00000000
    r16: 0x00000000           r17: 0x00000000           r18: 0x00000000           r19: 0x00000000
    r20: 0x00000000           r21: 0xa045c790           r22: 0xa045c784           r23: 0xa045c78c
    r24: 0x00001708           r25: 0xe64b7d88           r26: 0xa045c4d0           r27: 0x00000040
    r28: 0x0000000f           r29: 0x224d3336           r30: 0xa045c764           r31: 0x92ac1fc4
    Thread 3: Crashed (0xb7fff9d0, 0xb80c5e94)
    0x84ae07d0: No symbol
    0x84adc130: No symbol
    0x84ada84c: No symbol
    0x842fc7d4: No symbol
    0x84dca57c: No symbol
    0x84c52a10: No symbol
    0x84c527fc: No symbol
    0x84cd672c: No symbol
    0x84cd63f8: No symbol
    0x84c19cd4: No symbol
    0x84bfee84: No symbol
    0x84bfd040: No symbol
    0x8425addc: No symbol
    0x84bfcd88: No symbol
    0x85499644: No symbol
    PPC Thread State
    srr0: 0x00000000          srr1: 0x00000000                                 vrsave: 0x00000000
    cr:  0xXXXXXXXX                    xer: 0x20000000                     lr: 0x84ae07d0                    ctr: 0x92a29140
    r00: 0x84ae07d0           r01: 0xbfffcc10           r02: 0x01069800           r03: 0x0028ba90
    r04: 0x00000048           r05: 0x6c730000           r06: 0x00000000           r07: 0x00300000
    r08: 0x00000007           r09: 0xa085479c           r10: 0x948bbfe0           r11: 0xa08560ec
    r12: 0x92a29140           r13: 0x00000000           r14: 0x00000000           r15: 0x00000003
    r16: 0xbfffea80           r17: 0x00000058           r18: 0x00000001           r19: 0x00000000
    r20: 0x00000004           r21: 0x00000000           r22: 0x00000000           r23: 0x0000004f
    r24: 0x00000001           r25: 0x007a7b90           r26: 0x007e02d0           r27: 0x854ad528
    r28: 0x010b7a98           r29: 0x010659f4           r30: 0x01065a0c           r31: 0x00000000

    Hi all--this worked for me:
    1. Uninstall Office using the Remove Office program.
    2. Remove (trash) the microsoft folder from the fonts folder. Then delete the word plist from your user library preferences folder.
    3. Run disk utility to repair permissions and restart.
    4. Run Snow Leopard cache cleaner and do a deep clean on the cache of your system.
    5. Run Easy Find to find "fontcachetool" (it's an invisiable file, so make sure you enable easyfind to locate invisible files. Trash the fontcachetool file once it's located. Note: I actually had two of these files, and I trashed them both.
    6. Restart.
    7. Run disk utility to repair permissions again, and restart.
    8. Install Office 2008.
    9. Do NOT open any Office programs, and restart.
    10. Install SP 1 (note: I installed this from a disk image. My previous attempts to use the automatic check for updates "feature" in Office to download and install the program did not work--believe me, I uninstalled and reinstalled Office three times before performing the tasks I am listing here. You can download the disk images of the SP here:
    SP 1 (12.1.0): http://www.microsoft.com/downloads/details.aspx?familyid=395D1487-A3A6-4106-A0F8 -4D6E1D6D89D2&displaylang=en
    SP 2 (12.2.0): http://support.microsoft.com/kb/973254
    Update 3 (12.2.1): http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=9730452B -E6AD-4330-93E4-57F66293BF1C#viewer
    11. Restart
    12. Install 12.2.0. Restart.
    13. Install 12.2.1. Restart
    14. Repair permissions.
    15. Restart.
    So far so good. I hope this helps.
    Antonio

  • MS Word crashes

    This seems to be the only forum where this topic fits; if you know a more appropriate one, please tell me.
    On MS Office 2008, Word crashes when I try to make mailing labels to merge with a word processing document. When Appleworks crashes, it is recommended to trash preferences and several other files. What works with Word?
    Thanks in advance for any help you can give me.

    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
    (Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
    If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
    Is there any change in behavior after this?

  • I just upgraded to OS X Lion and now MS Word crashes. Help needed!

    I just upgraded to OS X Lion and now MS Word crashes.No problem with Powerpoint or Excel. Any assistance greatly appreciated
    The error is:
    Microsoft Error Reporting log version: 2.0
    Error Signature:
    Exception: EXC_BAD_ACCESS
    Date/Time: 2012-06-12 10:37:05 +0000
    Application Name: Microsoft Word
    Application Bundle ID: com.microsoft.Word
    Application Signature: MSWD
    Application Version: 12.3.3.120411
    Crashed Module Name: CoreFoundation
    Crashed Module Version: 635.21
    Crashed Module Offset: 0x00008fc1
    Blame Module Name: MicrosoftComponentPlugin
    Blame Module Version: 12.3.3.120411
    Blame Module Offset: 0x000ed299
    Application LCID: 1033
    Extra app info: Reg=en Loc=0x0409
    Crashed thread: 0

    As I said, there have been reports on there of problems for some people using 2008, as you have experienced with particular components of the suite.
    Best solution would be an upgrade to 2011...I have had no issues at all using 2011 with Mac OS X 10.7.4.

Maybe you are looking for

  • Follow up/Replacement article

    Hi All I need to configure Follow Up Article/Replacement Artcle. I have done configuration Setting in SPRO and Maintain articles in Easy Access (T.C - WRFFUART) My Quesiton - How do i check up..(Provide i check up in T.C - ME21N and VA01) or any othe

  • ACH/EFT Payment Methods

    ACH/EFT Payment Methods will be used for what?(vendors or customers). kindly confirm me Thanks Sap Guru

  • CUP v5.3 - Password Self Service - HR Fields Out or Order

    Hello everyone, I have set up Password Self Service in CUP v5.3 for SAP HR.  In the Configuration --> Self Service, I have created a few Infotype/Subtype entries.  When I go to reset a test user ID's password, the Infotype/Subtype fields appear in a

  • Adobe Application Manager will be crashed

    When I start up Adobe Application Manager on my Yosemite machine he will be crashed. After a few seconds he gives a problem report messages and says that Adobe Application Manager quit unexpectedly. I have tried to reinstall the application for the a

  • Urgent: Website hosting on my MacBook Pro (Lion 10.7.4)

    Hi, Sorry that I am not able to use good technical terms in this.  Please be patient and read through.  I need solution a little urgently. Please. I have registered a domain (Let us say MyDomain.Com) with some webhosting registrar. I feel, my domain