The process was terminated due to an internal error in the .NET Runtime at IP 710D46A9 (70F30000) with exit code 80131506. RRS feed

  • Question

  • Hi Team,

    I am getting below runtime error in my .net app using C#

    Please help me how to resolve this issue?

    === Windows Error Reporting (9/20/2018 10:03:03 AM)

    Fault bucket 2591910269, type 455639411

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: UCA.exe


    P3: 5b1f6af4

    P4: clr.dll

    P5: 4.7.3130.0

    P6: 5b175f1a

    P7: c0000005

    P8: 001a46a9



    Attached files:


    These files may be available here:


    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 44263bc3-bce6-11e8-98ed-40b034e24535

    Report Status: 1

    === Application Error (9/20/2018 10:03:01 AM)

    Faulting application name: UCA.exe, version:, time stamp: 0x5b1f6af4

    Faulting module name: clr.dll, version: 4.7.3130.0, time stamp: 0x5b175f1a

    Exception code: 0xc0000005

    Fault offset: 0x001a46a9

    Faulting process id: 0x4f80

    Faulting application start time: 0x01d450efec47a5c5

    Faulting application path: C:\Program Files (x86)\Mitel\Unified Communicator Advanced 7.3\UCA.exe

    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

    Report Id: 44263bc3-bce6-11e8-98ed-40b034e24535

    === .NET Runtime (9/20/2018 10:03:00 AM)

    Application: UCA.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an internal error in the .NET Runtime at IP 710D46A9 (70F30000) with exit code 80131506.



    Monday, September 24, 2018 6:02 AM

All replies

  • This isn't going to be that useful to us. It is just the standard Windows error information. You need to get the exception that is being thrown. The best way to do this is to have logging in your application. However if you haven't done that yet then when the app crashes WER will pop up the exception dialog. At that point it has generated a crash dump file. Provided that dialog is still up you can click on the tech details link (at least in some versions of Windows) and get the dump file. Loading that dump file up in Visual Studio along with the PDBs will let you see what was going on at the time (at least in a limited way).

    Ideally you should also be shipping your PDBs with your app. This will provide a better crash dump file and stack trace. BTW, did you happen to look in the Event Log to see if it might have generated a better error? 

    Finally, given just the information in the WER report you are getting an access denied error in the CLR. My running guess is that you're making an interop call and it is failing. But this would be a complete guess without knowing where in the code things are failing and no stack trace.

    Michael Taylor http://www.michaeltaylorp3.net

    Monday, September 24, 2018 2:18 PM