solution for Application: w3wp.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 6E870702 (6E7D0000) with exit code 80131506. RRS feed

  • Question

  • When you run a Microsoft .NET Framework 4-based application, the application may crash intermittently. When this issue occurs, two error events that resemble the following are logged in the Application log. 

    Event 1

    Log Name: Application
    Source: .NET Runtime
    Event ID: 1023
    Task Category: None
    Level: Error
    Keywords: Classic

    Application: <var class="sbody-var"><Application name></var>
    Framework Version: v4.0.21006
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 6B484BC2 (6B300000) with exit code 80131506.

    Event 2

    Log Name: Application
    Source: Application Error
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic

    Faulting application name: <var class="sbody-var"><Application name></var>, version: <var class="sbody-var"><Application Version></var>, time stamp: 0x4e11b8da
    Faulting module name: clr.dll, version: 4.0.30319.235, time stamp: 0x4da4281c
    Exception code: 0xc0000005
    Fault offset: 0x0000000000037413
    Faulting process id: 0x1b4c
    Faulting application start time: 0x01cc3aed2d08224a
    Faulting application path: <path>
    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    Report Id: 0bdfb3f5-a6f9-11e0-acdb-0024e854572f

    Thursday, May 12, 2016 4:33 PM


All replies

  • Exception code: 0xc0000005 is "Access denied".

    Your code is trying to access resource (memory, file, hardware, etc.) that it's currect account has not been given permission to, or in some case it could be because the resource is currently using by others.

    Check what your code is supposed to be doing at that time to try to figure out what had happened.

    Also check the multiple suggestions here. Especially the one regarding a bug in GC. Your runtime's build number is lower than that fix. Probably it's time to update your .NET runtime to newer version.
    Friday, May 13, 2016 2:23 AM
  • Thanks your reply. This had happened only the production server, when the higher user hit situation (HTTP request )

    How can i figure out?

    Friday, May 13, 2016 2:45 AM
  • If you know how to investigate the bug with windbg, you may configure the IIS to create memory dump next time when app crash occurs .

    Otherwise, there's very little you can do.

    My advise would still be try to update the .NET runtime, as the build number of the runtime shown in the event log is old and contains known problem that can lead to this.

    Friday, May 13, 2016 7:12 AM
  • Following is the dibugdiag analyzed report when the issues occur. Please advice


    Description Recommendation
    In w3wp__DMS_DIMO__PID__3732__Date__05_24_2016__Time_02_13_24PM__537__First chance exception 0X04242420.dmp the assembly instruction at KERNELBASE!RaiseException+48 in C:\Windows\System32\KERNELBASE.dll from Microsoft Corporation
    This exception originated from clr!Debugger::SendRawEvent.
    has caused an unknown exception (0x04242420) on thread 7

    This exception originated from clr!Debugger::SendRawEvent+5d.

    Review the faulting call stack for thread 7 to determine root cause for the exception.

    Please follow up with vendor Microsoft Corporation for problem resolution concerning the following file: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll.

    Description Recommendation
    Analysis results may be incomplete because an error occurred while initializing the CLR diagnostic runtime for w3wp__DMS_DIMO__PID__3732__Date__05_24_2016__Time_02_13_24PM__537__First chance exception 0X04242420.dmp.

    Dump File:  w3wp__DMS_DIMO__PID__3732__Date__05_24_2016__Time_02_13_24PM__537__First chance exception 0X04242420.dmp

    Type:  Microsoft.Diagnostics.Runtime.ClrDiagnosticsException

    Message:  This runtime is not initialized and contains no data.

    Stack Trace:
    Microsoft.Diagnostics.Runtime.RuntimeBase..ctor(DataTargetImpl dataTarget, DacLibrary lib)
    Microsoft.Diagnostics.Runtime.Desktop.V45Runtime..ctor(DataTargetImpl dt, DacLibrary lib)
    Microsoft.Diagnostics.Runtime.DataTargetImpl.CreateRuntime(String dacFilename)
    DebugDiag.DotNet.NetDbgObj.CreateRuntime(String symbolPath, DataTarget target, Int32 runtimeIndex, ClrInfo& clrInfo)
    DebugDiag.DotNet.NetDbgObj.CreateRuntimeAndGetHeap(String dumpPath, IDbgObj3 legacyDebugger, String symbolPath, Boolean throwOnBitnessMismatch, Boolean loadClrHeap)

    HResult: RuntimeUninitialized
    This message means that the CLR Runtime is loaded but the ThreadStore or GC Heap information is not initialized.

    • Edited by samant123 Tuesday, May 24, 2016 9:07 AM
    Tuesday, May 24, 2016 9:06 AM
  • This first exception is generated by debugger itself, you can ignore it.

    The second exception occurs when you attempt to analyse the dump file on machine running different version of runtime.

    Both of them is not related to the problem you're facing.

    Btw, I'm not familiar with debug tool so maybe you should try find other people to assist you find out the problem.
    Wednesday, May 25, 2016 1:18 AM
  • check with .net framework 4.6.1, but issue is still happen
    Wednesday, May 25, 2016 7:02 AM