IIS w3wp.exe error on app poolRSS

2 replies

Last post Aug 14, 2017 08:35 PM by csiga00

  • IIS w3wp.exe error on app pool

    Feb 24, 2015 12:19 PM|meramez|LINK

    Hi,

    The dedicated app pool on my website fires a strange error on the IIS w3wp.exe, I created an error dump using DebugDiag:

    Exception Information
    In w3wp__[AppPoolName]__PID__5748__Date__02_23_2015__Time_11_12_05AM__248__Second_Chance_Exception_C0000374.dmp the assembly instruction at ntdll!RtlReportCriticalFailure+83 in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused an unknown exception (0xc0000374) on thread 27

    Module Information 
    Image Name: C:\Windows\System32\ntdll.dll Symbol Type: PDB 
    Base address: 0x00905a4d Time Stamp: Sat Jan 10 09:39:59 2015 
    Checksum: 0x00000000 Comments: 
    COM DLL: False Company Name: Microsoft Corporation 
    ISAPIExtension: False File Description: NT Layer DLL 
    ISAPIFilter: False File Version: 6.3.9600.17630 (winblue_r7.150109-2022) 
    Managed DLL: False Internal Name: ntdll.dll 
    VB DLL: False Legal Copyright: © Microsoft Corporation. All rights reserved. 
    Loaded Image Name: ntdll.dll Legal Trademarks: 
    Mapped Image Name: Original filename: ntdll.dll 
    Module name: ntdll Private Build: 
    Single Threaded: False Product Name: Microsoft® Windows® Operating System 
    Module Size: 1.43 MBytes Product Version: 6.3.9600.17630 
    Symbol File Name: c:\symcache\wntdll.pdb\47A7658334C547BCA03E6293A78C675F2\wntdll.pdb Special Build: & 

    Entry point ntdll!TppWorkerThread 
    Create time 2/23/2015 10:00:00 AM 
    Time spent in user mode 0 Days 0:0:0.0 
    Time spent in kernel mode 0 Days 0:0:0.0 

    Function Arg 1 Arg 2 Arg 3 Arg 4 Source
    ntdll!RtlReportCriticalFailure+57 c0000374 771a4270 0115f578 7716f739
    ntdll!RtlpReportHeapFailure+21 00000002 7882dee3 00000000 00230000
    ntdll!RtlpLogHeapFailure+a1 00000008 00230000 1d5adbb8 00000000
    ntdll!RtlFreeHeap+64 00230000 00000000 1d5adbc0 0115f5e0
    kernel32!HeapFree+14 00230000 00000000 1d5adbc0 0115f670
    cachhttp!RESPONSE_ENTRY::~RESPONSE_ENTRY+ac 01302e38 0115f614 70ce4a92 00000001
    cachhttp!RESPONSE_ENTRY::`scalar deleting destructor'+d 00000001 01302dc0 70ce4b1a 01302aa8
    cachhttp!RESPONSE_ENTRY::DereferenceResponseEntry+20 01302aa8 70ce4bc8 01302aa8 70ce4c0e
    cachhttp!OUTPUT_ENTRY::ClearIdentityResponseEntry+1b 01302aa8 70ce4c0e 01302aa8 0115f628
    cachhttp!OUTPUT_ENTRY::~OUTPUT_ENTRY+a 01302aa8 0115f628 70ce5309 00000001
    cachhttp!OUTPUT_ENTRY::`scalar deleting destructor'+d 00000001 0115f67c 70ce8ffa 0115f648
    cachhttp!OUTPUT_ENTRY::DereferenceOutputEntry+1d 0115f648 72566031 01302aa8 ffffffff
    cachhttp!OUTPUT_CACHE::AddRefRecord+24 01302aa8 ffffffff 011b31f0 011b4c8c
    iisutil!CLKRLinearHashTable::_DeleteNode+1f 011b4c88 0115f670 0115f66c 0115f67c
    iisutil!CLKRLinearHashTable::_DeleteIf+a3 70ce387e 0115f6b4 0115f6a0 00000000
    iisutil!CLKRHashTable::DeleteIf+4a 70ce387e 0115f6b4 70ce89ae 00000000
    cachhttp!CTypedHashTable<OUTPUT_CACHE,OUTPUT_ENTRY,OUTPUT_KEY *,CLKRHashTable>::DeleteIf+2b 70ce89ae 00000000 00000000 01191b20
    cachhttp!OUTPUT_CACHE::ScavengerCallback+d2 00000000 00000001 7882dcc3 770d27d8
    ntdll!RtlpTpTimerCallback+7a 0115f7b8 01191b20 1d3e2a90 0027f420
    ntdll!TppTimerpExecuteCallback+10f 0115f7b8 1d3e2af0 7882d347 00000000
    ntdll!TppWorkerThread+572 0027f418 0115f928 770d9f72 0027f418
    kernel32!BaseThreadInitThunk+e 0027f418 7882d2b3 00000000 00000000
    ntdll!__RtlUserThreadStart+70 770f3e85 0027f418 ffffffff 77167428
    ntdll!_RtlUserThreadStart+1b 770f3e85 0027f418 00000000 00000000

    Notes:

    • The app pool uses .NET 4
    • The app pool has only 1 website running.
    • The website is using MVC 4.0
    • I don't have PHP or MySQL installed on the server.
    • SQLServer 2012 is installed.
    • The issue occurs on 2 different Windows Servers, 2008 and 2012.


    Appreciate your assistance??

    debugdiag ntdll.dll w3wp.exe error bug

  • Rovastar Rovastar

    5460 Posts

    MVP

    Moderator

    Re: IIS w3wp.exe error on app pool

    Feb 24, 2015 05:38 PM|Rovastar|LINK

    I cannot see anything obvious there.
    debugdiag troubleshooting is really beyond the scope of these forums your should open a support case with Microsoft.
    Troubleshoot IIS in style
    https://www.leansentry.com/
  • Re: IIS w3wp.exe error on app pool

    Aug 14, 2017 08:35 PM|csiga00|LINK

    Hi,

    I know that his has been asked a long time ago, but for future readers...we had a similar problem with a similar stack trace from the dump file (symptoms: w3wp and web application crashed and restarted randomly):

    # 85  Id: f14.294 Suspend: 0 Teb: fec49000 Unfrozen
     # ChildEBP RetAddr  
    00 368ae9b8 771b1292 ntdll!NtGetContextThread+0xc
    01 368aea20 77107551 ntdll!PsspCaptureVaSpaceInformation+0x419
    02 368aea44 771afee2 ntdll!RtlQueryPerformanceCounter+0x4c
    03 368aead0 7717a113 ntdll!PssNtCaptureSnapshot+0x304
    04 368aef28 77179fbb ntdll!RtlReportExceptionEx+0x118
    05 368aef80 771a2ffc ntdll!RtlReportException+0x9b
    06 368aef90 770fe244 ntdll!RtlReportCriticalFailure+0xa7
    07 368aefa4 7714fc13 ntdll!_EH4_CallFilterFunc+0x12
    08 368aefcc 771514d1 ntdll!_except_handler4_common+0x8d
    09 368aefec 770fdf81 ntdll!_except_handler4+0x20
    0a 368af010 770fdf53 ntdll!ExecuteHandler2+0x26
    0b 368af0dc 770fddbb ntdll!ExecuteHandler+0x24
    0c 368af0dc 771a2fd8 ntdll!KiUserExceptionDispatcher+0xf
    0d 368af638 771a5ac8 ntdll!RtlReportCriticalFailure+0x83
    0e 368af648 771a6379 ntdll!RtlpHeapHandleError+0x1c
    0f 368af678 7715e5ff ntdll!RtlpLogHeapFailure+0xa1
    10 368af6d4 72ad7094 ntdll!RtlFreeHeap+0x5feaa
    11 368af708 72ad451f cachhttp!RESPONSE_ENTRY::~RESPONSE_ENTRY+0xfa
    12 368af710 72ad44c6 cachhttp!RESPONSE_ENTRY::DereferenceResponseEntry+0x1a
    13 368af718 72ad4571 cachhttp!OUTPUT_ENTRY::ClearIdentityResponseEntry+0x1f
    14 368af720 72ad4d7e cachhttp!OUTPUT_ENTRY::DereferenceOutputEntry+0x17
    15 368af728 736ab975 cachhttp!CTypedHashTable<OUTPUT_CACHE,OUTPUT_ENTRY,OUTPUT_KEY *,CLKRHashTable>::_AddRefRecord+0x25
    16 368af74c 736ac22f iisutil!CLKRLinearHashTable::_DeleteNode+0x20
    17 368af788 736abf82 iisutil!CLKRLinearHashTable::_DeleteIf+0xaf
    18 368af7ac 72ad3c2d iisutil!CLKRHashTable::DeleteIf+0x4a
    19 368af7c8 72ad667f cachhttp!CTypedHashTable<OUTPUT_CACHE,OUTPUT_ENTRY,OUTPUT_KEY *,CLKRHashTable>::DeleteIf+0x2b
    1a 368af830 770c501f cachhttp!OUTPUT_CACHE::ScavengerCallback+0xcf
    1b 368af874 770dd7ff ntdll!RtlpTpTimerCallback+0x5f
    1c 368af89c 770df6c0 ntdll!TppTimerpExecuteCallback+0x64
    1d 368afa34 7685495d ntdll!TppWorkerThread+0x487
    WARNING: Stack unwind information not available. Following frames may be wrong.
    1e 368afa40 771098ee kernel32+0x1495d
    1f 368afa84 771098c4 ntdll!__RtlUserThreadStart+0x20
    20 368afa94 00000000 ntdll!_RtlUserThreadStart+0x1b

    After searching for iisutil + cachhttp + heap corruption (because Event Viewer showed Exception code: 0xc0000374 and that means heap corruption) I found this:

    https://blogs.msdn.microsoft.com/asiatech/2010/10/18/heap-corruption-in-httpcachemodule-while-you-try-to-remove-http-headers-in-your-custom-http-module/

    In case this site is disappeared in the future, our problem was that we tried to remove headers from response in Global.asax.cs, something like this (this is copied from the site above):

            public void Init(HttpApplication app)
            {
                app.PreSendRequestHeaders += new EventHandler(this.PreSendRequestHeaders);
            }


            private void PreSendRequestHeaders(object sender, EventArgs e)
            {
                HttpContext.Current.Response.Headers.Remove("Server");
                HttpContext.Current.Response.Headers.Remove("X-AspNet-Version");
                HttpContext.Current.Response.Headers.Remove("X-Powered-By");
            }

    "The reason why this problem occurs is because the HttpCacheModule and IIS pipleline assume that the response will not be modified once it is taken from the output cache.

    The problem can be avoided if the HTTP headers are removed on any event before UpdateRequestCache event.

    (Refer to http://learn.iis.net/page.aspx/243/aspnet-integration-with-iis-7/  for more details on request pipeline)"

    Hope this helps!

    All credits go to XinJin and APGC DSI Team!

    Regards,

    Csiga