locked
0xc0000374 RRS feed

  • Question

  • User502832308 posted

    Hello,

    I'm getting this error almost once every hour:

    A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was 'XXXX'. The process exit code was '0xc0000374'.

    What is it and what's the solution to this?

    Tuesday, August 5, 2008 3:08 PM

Answers

  • User-35293355 posted
    It has been a week with no error. I checked through the source changes and there were a few so someone tested this on IIS 7 and corrected the iis specific issues. It seems that there may have been a slight change in memory handling in this version and that would explain why dll that worked on 5 & 6 was causing heap issues.
    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 7, 2009 10:32 AM

All replies

  • User844605415 posted

    Hi,

    It is an internal error, typically involving heap corruption. There is not enough information on the thread to suggest a solution. The best bet at this point is to get a memory dump of the process when it exits and have it reviewed. You could also attach a debugger and try troubleshooting.

    Thanks,

    Mukhtar Desai

    IIS Performance Team

    Tuesday, August 5, 2008 4:49 PM
  • User502832308 posted

    OK, here are some more information:

     

    Log Name:      System
    Source:        Microsoft-Windows-WAS
    Date:          8/6/2008 3:42:24 AM
    Event ID:      5009
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER
    Description:
    A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '2948'. The process exit code was '0xc0000374'.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
        <EventID Qualifiers="32768">5009</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-08-05T21:42:24.000Z" />
        <EventRecordID>11416</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>SERVER</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="AppPoolID">DefaultAppPool</Data>
        <Data Name="ProcessID">2948</Data>
        <Data Name="ExitCode">c0000374</Data>
      </EventData>
    </Event>

    Wednesday, August 6, 2008 2:13 AM
  • User844605415 posted

    Sorry an event log is not of much use here. As I mentioned in my previous post the best bet here is a memory dump. Be forewarned that heap corruptions are quite challenging to figure out even with dumps as there are very few clues to go with.

    Thanks,

    Mukhtar Desai
    IIS Performance Team

    Wednesday, August 6, 2008 9:23 PM
  • User-35293355 posted
    I'm getting in my logs mostly 374:

    Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0x12ec, application start time 0x01c96694475a2dc0.

    I did apply originally KB956120 hotfix from QFE so i wondered if that was the issue. I noticed that in logs I see sometimes same line repeated for every subsequent request as if the logging fix screwed up something. So I uninstalled the KB but it still happens
    Thursday, December 25, 2008 11:22 AM
  • User-35293355 posted
    the errors coincide with IIS warnings:

    A process serving application pool 'insert_pool_name_here' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4844'. The data field contains the error number.

    the detail only contains one 4 byte word: 8007006D - i gather that would be an error code suggesting nothing more than that the application pool died on the other side of the handle (ie broken pipe error) so it is not very useful.

    I have created many application pools, one per website, and i seem to be getting problem mostly from one instance. The pools are unmanaged and do not contain .net code.
    Thursday, December 25, 2008 12:27 PM
  • User511787461 posted

    The error code 0xc0000374 indicates a heap corruption - like Mukhtar said earlier, you will need to collect a crash dump and debug it to figure out what code is causing the heap corruption - also, you can use gflags/app-verifier to enable page-heap which will ease debugging of heap corruption.  If you do not know how to enable page-heap/collect a crash dump/debug it, you should open a case with microsoft support and they can guide you through it.

    Thursday, December 25, 2008 4:23 PM
  • User-35293355 posted
    This is on my personal server and I'm not sure whether that kind of support is part of the 2008 Web Edition OEM or not. I certainly would not want to pay for it, i'd rather wait until it is resolved by someone else if it is not included. The licensing is way too complicated for person like me to parse and figure out what kind of support is included so i am reluctant to open any case of any sort with microsoft. I'll look around to see if i can figure how to enable crash dump without going that route.
    Monday, December 29, 2008 8:41 AM
  • User-35293355 posted
    The pool that I'm using was native pool with isapi dll from tomcat jakarta project. While the dll works great under 5/6, it may have been allocating memory in incompatible format or in a way that IIS7 does not like. I upgraded the DLL today on the machine because I saw that a lot of changes went into main source of the isapi plugin in last few months and i'll be watching for the issue. So far no crash yet.
    Monday, December 29, 2008 6:22 PM
  • User-35293355 posted
    It has been a week with no error. I checked through the source changes and there were a few so someone tested this on IIS 7 and corrected the iis specific issues. It seems that there may have been a slight change in memory handling in this version and that would explain why dll that worked on 5 & 6 was causing heap issues.
    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 7, 2009 10:32 AM
  • User844605415 posted

    Thanks for sharing the info. It will help other with similar problems.

    Thanks,
    Mukhtar Desai
    IIS Performance Team

    Wednesday, January 7, 2009 3:26 PM
  • User-42599584 posted
    I'm getting a similar error while attempting to load OCS Group Chat on my workstation. The event log is below. I don't know how to take a crash dump, would this be necessary for my situation, and can you tell me how to do it?

    Faulting application GroupChatConsole.exe, version 3.5.6907.0, time stamp 0x49477636, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000374, fault offset 0x000afaf8, process id 0x1fa4, application start time 0x01ca326718753304.

     Thanks,

    Vinny

    Thursday, September 10, 2009 6:42 PM