locked
Exception code: 0xc0000374 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a problem that occurs at interval  with Word 2010. The most helpful comment I have found so far is given in the next paragraph.

    The exception code 0xc0000374 indicates a heap corruption - to determine the solution, you would need to debug the crash in a debugger to figure out who is corrupting the heap.

    Where do I find the heap? What will be the file name? What tools can I use to debug?

    I have noticed that other errors can also be caused by exception code 0xc0000374 . Notably one causing the Print Spooler service to stop.

    Hope this helps, Gerry
    Sunday, January 15, 2012 12:23 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Problem has been solved here

    http://answers.microsoft.com/en-us/office/forum/office_2010-office_install/office-products-crashed-upon-launch-0xc0000374/9eb1251f-5a7d-4401-a955-155ac432e6ea

    Regards

    Milos

    Sunday, January 15, 2012 1:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Milos

    I had seen that thread before and ruled out the solutions suggested. However, a second look makes me wonder whether I can rule out this possibilty:

    l A faulty add-in enabled for Office applications:

    n You may use application safe for each Office application to open for example open Run (press Windows key + R), type winword /safe, excel /safe for Word and Excel respectively. If it works fine, disable the add-ins using File > Options > Add-ins for each applications

    I do use an Add On to provide an Office 2003 Menu to work around the horrible ribbon provided with Office 2010

    Hope this helps, Gerry
    Sunday, January 15, 2012 2:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Gerry

    give it a try without add-on. More elaborate analysis would be done with Process Monitor from Sysinternals. This will bring you to the internals.

    For debugging tools look here

    http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

    and use

    http://lysine.org/2009/02/using-pageheapexe.html

    http://www.windowsitpro.com/article/performance/administrators-intro-to-debugging

    Regards

    Milos

     


    Sunday, January 15, 2012 3:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Milos

    The problem with working without the Add On is that it totally destroys productivity. I have found this link since my last post:
    http://office.microsoft.com/en-us/templates/CL101817133.aspx?CTT=5&origin=HA101794130&AxInstalled=1&c=0

    I have printed off the Manual for the Word Menu to Ribbon reference. For Word it runs to 60 pages.

    Since I lasted tried using Word ( and Excel ) without the Add On I have customised the Quick Access Toolbar so I would now be less dependent on the Ribbon but it would be a major task to fully famililarise myselelf with all options. I have to balance the comparitive cost of two or three errors  a day against the loss of productivity. I fear it is a No Contest result.

    I have looked at Process Monitor in the past and found that I got such a deluge of information that it was impossible to tell what was relevant. It is likely that the utility has been improved. I will endeavour to take another look at Process Monitor to see if I can get it to focus on winword.exe and / or spoolsv.exe where the output would be less. Any tips on focussing the utility?

     

    Hope this helps, Gerry
    Sunday, January 15, 2012 4:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    I think the issue is better to post in Office Forum. Sorry for the inconvenience.

     

    http://social.technet.microsoft.com/Forums/en-US/word/threads

    Niki Han

    TechNet Community Support

    Tuesday, January 17, 2012 6:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Niki

    My opinion is that the questions I am asking are actually a Windows issue as they relate to heap corruption. The involvement of Word 2010 is coincidental. The common Print Spooler problem also involves heap corruption and exception code 0xc0000374 and I get those from time to time.  

    Hope this helps, Gerry
    Tuesday, January 17, 2012 8:56 AM