Visual Studio 2015 Update 1 RTM - Crash when loading .NET Framework Components


  • When I try to add new item in Toolbox from .NET Framework Components, during the loading of Items in .NET Components, the Visual Studio IDE will restart.

    I check the Event Viewer Application Log, I found out this log event

    Application Error
    Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
    Faulting module name: clr.dll, version: 4.6.1055.0, time stamp: 0x563c0f73
    Exception code: 0xc0000005
    Fault offset: 0x002c6836
    Faulting process id: 0x2288
    Faulting application start time: 0x01d1328a60c9e5cf
    Faulting application path: C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    Report Id: 1868cf4b-9e7f-11e5-a48c-14dae92252f6

    .NET Runtime
    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 68496836 (681D0000) with exit code 80131506.

    I try also run the visual studio in Safemode and reset the settings, but the problem still occurred.

    Anyone knows how to fix it?

    Thursday, December 10, 2015 10:10 AM


  • Hi tvz0go00_Gary,

    Thanks for your post.

    I did a research for the error message. I found Exception code 0xc0000005 is an Access Violation. And I also found a similar thread to yours.

    The cause of  the error in this thread is that the user he used without admin rights.

    So I suggest you could change another user which has local admin rights then try it again.

    If the error still occurred. I suppose whether the problem is in your test project or in your VS.

    In order to validate it. I suggest you could create a new project. Add a new item in Toolbox from then check if the error will occurred.

    1. If it works well for the new project. I think the cause is in your application.

    In this case, I wonder if you could share us your application so that we could reproduce the error in my side so that we could troubleshoot the issue.

    2. If same error occurred for the new project. I suppose the something was wrong during your VS installation.

    You could try to repair your VS and try it again, If after repairing your VS, it still has the issue.

    I suggest you could use the   collect.exe tool to collect the installation logs. After using it, you will find from %temp% folder.

    Then  upload the file to    and share the link here.

    Best Regards,

    Lake Xiao

    Monday, December 14, 2015 6:15 AM