Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.

Locked Visual Basic Compiler has Stopped Working

  • Wednesday, August 13, 2008 9:37 PM
     
     
    I am getting the following message in VS 2005 Standard Edition using VB for a Windows Form Application:

    Microsoft (R) Visual Basic Compiler has Stopped Working.

    A problem caused the program to stop working correctly.
    Windows will close the program and notify you if a solution is available.

    <Debug>  <Close Program>

    Clicking on either Debug or Close Program shuts down Visual Studio.


    Happens when pasting code from 1 form into another. Seems random but usually about 5-7 pastes or every 10-15 minutes.

    I have looked at FIX: The Visual Studio 2005 IDE may randomly crash when you build a Visual Basic .NET solution (Article 942124) but it states this should happen when doing a Build or Rebuild.

    The Workaround says:
    To work around this problem, use the whole project as the reference.

    What exactly does this mean and how would I do this?

    Installed Products:

    Microsoft Visual Studio 2005
    Version 8.0.50727.867  (vsvista.050727-8600)
    Microsoft .NET Framework
    Version 2.0.50727 SP1

    Installed Edition: Standard

    Microsoft Visual Basic 2005   77633-235-2833766-41228
    Microsoft Visual Basic 2005

    Microsoft Visual C# 2005   77633-235-2833766-41228
    Microsoft Visual C# 2005

    Microsoft Visual C++ 2005   77633-235-2833766-41228
    Microsoft Visual C++ 2005

    Microsoft Visual J# 2005   77633-235-2833766-41228
    Microsoft Visual J# 2005

    Microsoft Visual Web Developer 2005   77633-235-2833766-41228
    Microsoft Visual Web Developer 2005

    Microsoft Web Application Projects 2005   77633-235-2833766-41228
    Microsoft Web Application Projects 2005
    Version 8.0.50727.867

    Microsoft Visual Studio 2005 Standard Edition - ENU Service Pack 1 (KB926601)  
    This service pack is for Microsoft Visual Studio 2005 Standard Edition - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/926601

    SQL Server Reporting Services  
    Microsoft SQL Server Reporting Services Designers
    Version 9.00.3042.00

    Update for Microsoft Visual Studio 2005 Standard Edition - ENU (KB932232)  
    This Update is for Microsoft Visual Studio 2005 Standard Edition - ENU.
    If you later install a more recent service pack, this Update will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/932232



    Thanks.


All Replies

  • Friday, August 22, 2008 7:52 AM
     
     
    Anybody else having this problem?
  • Thursday, June 18, 2009 6:55 AM
     
     
    Yes, I am having the same problem and can´t find an easy way to fix it.
  • Monday, January 25, 2010 5:54 AM
     
     
    Yes, I am facing this problem from last 3 months and quit helpless now... please help me to solve this as soon as possible.
  • Wednesday, April 21, 2010 11:10 PM
     
     Proposed
    For me it the compiler was crashing because of a syntax error (an "implements" after an event without specifying the interface).  I fixed the error manually with notepad then opened the solution and all was well. 
    N I C K
    • Proposed As Answer by JosephAK Monday, July 25, 2011 12:13 PM
    •  
  • Monday, July 25, 2011 12:14 PM
     
     

    You could also try this if your OS is 64 bit:

    Right click Project > Properties > Compile > Advance Compile Options > Target CPU: x86

  • Friday, September 09, 2011 11:09 AM
     
     
    It is working for me for VS2005
  • Friday, January 27, 2012 9:00 PM
     
     

    I encountered a similar issue, but the error would display right after VS finished loading one of my projects.

    I deleted the project's .suo file and the error went away.  To anyone else having an issue like this:  Try deleting the project's .suo file!