Page 1 of 1

Using .NET Memory Profiler

Posted: Fri Feb 01, 2013 12:52 am
by mrichards
Hi there,

I've started having issues profiling a specific .NET 4.0 (C#) application here locally v4.0.133.0 of the .NET Memory Profiler. I have been able to profile this application before and can still profile other .NET 4.0 applications.

The application starts, then crashes after about 1 second. When it crashes I see the following 2 events in the event viewer (also attached)
Application: Everest.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEDF737125 (000007FEDF730000) with exit code 80131506.
and then
Faulting application name: Everest.exe, version:, time stamp: 0x510b098a
Faulting module name: clr.dll, version: 4.0.30319.17626, time stamp: 0x4f9f103d
Exception code: 0xc0000005
Fault offset: 0x0000000000007125
Faulting process id: 0x1f68
Faulting application start time: 0x01ce00117f53a6bc
Faulting application path: C:\SVNRepository\BMSProducts\LoanTradeDesk\trunk\Source Code\LTD\BMS.LTD.Presentation.WinForm\bin\Debug\Everest.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: c2a37274-6c04-11e2-84d2-d067e5387189
I've looked around and found similar errors here:
I got the hotfixes but cannot install them as it says that my system is not eligible. I'm assuming this is because my computer's newer version of the CLR already has those changes.

Has anyone run into this error before?