Hi,
We have a application running with target framework .NET 4.5 in a windows server 2012 where .NET 4.6 is installed. From now and then we are observing our application process getting terminated suddenly and in the event viewer we can see a .NET runtime error.
If we restart the application it is working fine again.
Following is from the event viewer:
1.
Faulting application name: Application.exe, version: Application Version, time stamp: 0x560bc88c
Faulting module name: clr.dll, version: 4.6.106.0, time stamp: 0x55da8e7d
Exception code: 0xc0000005
Fault offset: 0x0000000000180145
Faulting process id: 0xfdec
Faulting application start time: 0x01d11c669b19a0f9
Faulting application path: Application Path
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 0df94e68-8930-11e5-9449-121d0b6da159
2.
Application: Application.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FA6BAB0145 (000007FA6B930000) with exit code 80131506.
Error Report:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Application.exe
P2: Application Version
P3: 560bc88c
P4: clr.dll
P5: 4.6.106.0
P6: 55da8e7d
P7: c0000005
P8: 0000000000180145
P9:
P10:
Attached files:
AppData\Local\Temp\WERB7ED.tmp.appcompat.txt
AppData\Local\Temp\WERC5D3.tmp.WERInternalMetadata.xml
AppData\Local\Temp\WERF4C1.tmp.dmp
AppData\Local\Temp\WERFA5D.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Application_51c92268ea3e9980e6128fbe30689a70577d9b1a_cab_ecf1fa59
Analysis symbol:
Rechecking for solution: 0
Report Id: 0df94e68-8930-11e5-9449-121d0b6da159
Report Status: 4
WERInternatlMetadata.xml entry:
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.2</WindowsNTVersion>
<Build>9200 </Build>
<Product>(0x7): Windows Server 2012 Standard</Product>
<Edition>ServerStandard</Edition>
<BuildString>9200.17231.amd64fre.win8_gdr.150114-2006</BuildString>
<Revision>Unknown</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ProcessInformation>
<Pid>65004</Pid>
<ImageName>Application.exe</ImageName>
<CmdLineSignature>00000000</CmdLineSignature>
<Uptime>92006681</Uptime>
<ProcessVmInformation>
<PeakVirtualSize>7610032128</PeakVirtualSize>
<VirtualSize>7539445760</VirtualSize>
<PageFaultCount>5795999</PageFaultCount>
<PeakWorkingSetSize>6560456704</PeakWorkingSetSize>
<WorkingSetSize>6385553408</WorkingSetSize>
<QuotaPeakPagedPoolUsage>3530880</QuotaPeakPagedPoolUsage>
<QuotaPagedPoolUsage>1774056</QuotaPagedPoolUsage>
<QuotaPeakNonPagedPoolUsage>3005000</QuotaPeakNonPagedPoolUsage>
<QuotaNonPagedPoolUsage>606680</QuotaNonPagedPoolUsage>
<PagefileUsage>6117928960</PagefileUsage>
<PeakPagefileUsage>6363242496</PeakPagefileUsage>
<PrivateUsage>6117928960</PrivateUsage>
</ProcessVmInformation>
<ParentProcess>
<ProcessInformation>
<Pid>796</Pid>
<ImageName>services.exe</ImageName>
<CmdLineSignature>00000000</CmdLineSignature>
<Uptime>1035596954</Uptime>
<ProcessVmInformation>
<PeakVirtualSize>5439467520</PeakVirtualSize>
<VirtualSize>329666560</VirtualSize>
<PageFaultCount>17142993</PageFaultCount>
<PeakWorkingSetSize>24195072</PeakWorkingSetSize>
<WorkingSetSize>18575360</WorkingSetSize>
<QuotaPeakPagedPoolUsage>160296</QuotaPeakPagedPoolUsage>
<QuotaPagedPoolUsage>151144</QuotaPagedPoolUsage>
<QuotaPeakNonPagedPoolUsage>56576</QuotaPeakNonPagedPoolUsage>
<QuotaNonPagedPoolUsage>17152</QuotaNonPagedPoolUsage>
<PagefileUsage>18518016</PagefileUsage>
<PeakPagefileUsage>35635200</PeakPagefileUsage>
<PrivateUsage>18518016</PrivateUsage>
</ProcessVmInformation>
</ProcessInformation>
</ParentProcess>
</ProcessInformation>
<ProblemSignatures>
<EventType>APPCRASH</EventType>
<Parameter0>Application.exe</Parameter0>
<Parameter1>Application Version</Parameter1>
<Parameter2>560bc88c</Parameter2>
<Parameter3>clr.dll</Parameter3>
<Parameter4>4.6.106.0</Parameter4>
<Parameter5>55da8e7d</Parameter5>
<Parameter6>c0000005</Parameter6>
<Parameter7>0000000000180145</Parameter7>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.2.9200.2.0.0.272.7</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>e01c</Parameter22>
<Parameter23>e01c7bc0c87806fb290de81bc774dd17</Parameter23>
<Parameter24>5be9</Parameter24>
<Parameter25>5be9abeb302ac8cf9783533ec83935b1</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID>83875B7A-FF55-4CE1-98A6-E04370D6539B</MID>
<SystemManufacturer>Xen</SystemManufacturer>
<SystemProductName>HVM domU</SystemProductName>
<BIOSVersion>---</BIOSVersion>
<OSInstallDate>1389256814</OSInstallDate>
</SystemInformation>
<DAMInformation>
</DAMInformation>
<Integrator>
<Flags>80000000</Flags>
<SuspensionTimeDelta>NULL</SuspensionTimeDelta>
<ExemptionTimeDelta>NULL</ExemptionTimeDelta>
</Integrator>
</WERReportMetadata>
Can someone tell me what is the root cause of this error. We haven't made any changes to registry settings after or before installing .NET 4.6.
