locked
Constant Freeze while working on a 1.1MB file (with charts and check boxes) RRS feed

  • Question

  • Hi I work with a .doc file that's a template provided by someone else.  The draft.doc is about 50+ pages, 8000+ words, with charts, and check boxes.  The file itself takes 10-30 seconds to open and close.  It constantly freezes when I try to "check" the check boxes or add a new line/paragraph.  This is occuring on multiple computers. I've checked my computer's usuage and it's not using even half of the CPU or memory. Is there a patch that can fix this issue?

    Here's a little info on my computer:

    OS: Windows 7 32bit (the issue occurs on 64bit too)

    Office: 2010 Pro Plus; Version: 14.0.6123.5001

    Event Log (after it freezes and crashes):

    Log Name:      Application
    Source:        Application Error
    Date:          9/12/2012 12:13:39 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      gc-22-046.health.dohmh.nycnet
    Description:
    Faulting application name: WINWORD.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e310
    Faulting module name: MSVCR90.dll, version: 9.0.30729.4148, time stamp: 0x4a594c79
    Exception code: 0xc0000417
    Fault offset: 0x000320f0
    Faulting process id: 0x1158
    Faulting application start time: 0x01cd90f8d9b3d745
    Faulting application path: C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
    Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_none_5090ab56bcba71c2\MSVCR90.dll
    Report Id: cf9e4989-fcf4-11e1-a0bc-6c626dac1ff5
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-09-12T16:13:39.000000000Z" />
        <EventRecordID>25792</EventRecordID>
        <Channel>Application</Channel>
        <Computer>gc-22-046.health.dohmh.nycnet</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WINWORD.EXE</Data>
        <Data>14.0.6024.1000</Data>
        <Data>4d83e310</Data>
        <Data>MSVCR90.dll</Data>
        <Data>9.0.30729.4148</Data>
        <Data>4a594c79</Data>
        <Data>c0000417</Data>
        <Data>000320f0</Data>
        <Data>1158</Data>
        <Data>01cd90f8d9b3d745</Data>
        <Data>C:\Program Files\Microsoft Office\Office14\WINWORD.EXE</Data>
        <Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_none_5090ab56bcba71c2\MSVCR90.dll</Data>
        <Data>cf9e4989-fcf4-11e1-a0bc-6c626dac1ff5</Data>
      </EventData>
    </Event>

    Friday, September 14, 2012 9:00 PM

Answers

  • ok... in that case you might try to gather more info with procdump. It allows you to retrieve a dump file from when the application crashes.

    Get it here: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

    I've used it a couple of times with the -h switch which writes a dump file if the window hangs (ie 'not responding'), but in this case maybe the -e switch is more useful: "Write a dump when the process encounters an unhandled exception. Include the 1 to create dump on first chance exceptions."

    hope this helps,


    David
    :: Please vote if the info helped you :: Please post back so everyone can benefit from the solution ::

    • Marked as answer by Rex Zhang Monday, September 24, 2012 3:21 AM
    Wednesday, September 19, 2012 12:32 AM

All replies

  • You happen to have an MS Works converter installed? The issue you are describing and the dump data are very similar to this:

    http://social.technet.microsoft.com/Forums/en-US/word/thread/0f54cc7c-de27-4162-91b1-dfa6e8f7bee9/

    hope this helps,


    David
    :: Please vote if the info helped you :: Please post back so everyone can benefit from the solution ::

    Friday, September 14, 2012 11:07 PM
  • No, we dont have MS Works converter install.. any other ideas :(

    Thanks!

    Monday, September 17, 2012 1:52 PM
  • ok... in that case you might try to gather more info with procdump. It allows you to retrieve a dump file from when the application crashes.

    Get it here: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

    I've used it a couple of times with the -h switch which writes a dump file if the window hangs (ie 'not responding'), but in this case maybe the -e switch is more useful: "Write a dump when the process encounters an unhandled exception. Include the 1 to create dump on first chance exceptions."

    hope this helps,


    David
    :: Please vote if the info helped you :: Please post back so everyone can benefit from the solution ::

    • Marked as answer by Rex Zhang Monday, September 24, 2012 3:21 AM
    Wednesday, September 19, 2012 12:32 AM