The process was terminated due to an internal error in the .NET Runtime at IP 70232022 (70230000) with exit code 80131506 - by Nathanvdk

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 669096 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/18/2011 5:06:44 AM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

When opening Visual studio 2010 I get a message saying: Microsoft visual studio has stopped working. 

In the event the following message is logged:

Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: clr.dll, version: 4.0.30319.431, time stamp: 0x4d5344db
Exception code: 0xc0000005
Fault offset: 0x00002022
Faulting process id: 0x1c0c
Faulting application start time: 0x01cc154fa67a69dc
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: fe02f460-8142-11e0-ad46-005056c00008

and also:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 70232022 (70230000) with exit code 80131506.
Sign in to post a comment.
Posted by scrapdog on 2/24/2012 at 7:13 AM
Also experiencing this issue. Is there a resolution?
Posted by Microsoft on 6/14/2011 at 1:41 PM
Thanks for the feedback.  It's been awhile since our last communication so I'm going to resolve and close this issue.  If you're still experiencing problems, please reactivate or create a new Connect bug.
Posted by Microsoft on 6/8/2011 at 12:13 PM
We tried analyzing the files but unfortunately there was nothing telling there. Does uninstalling .NET 4.0 and reinstalling work? Did you recently install any other applications that could cause this issue?

Thanks,
Visual Studio Platform Team
Posted by Pixelxx on 5/19/2011 at 2:34 AM
Hello:

The same thing happens to me today.

Solution for me:

unistall framework 4.0 (repair doesn't work) and reinstall again.

Posted by Microsoft on 5/18/2011 at 7:27 PM
Hi Nathanvdk,

Please collect a copy of all *.winperf files from "{SystemDrive}:\Users\{UserName}\AppData\Roaming\Microsoft\VisualStudio\10.0” directory
Posted by MS-Moderator07 [Feedback Moderator] on 5/18/2011 at 7:13 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.