Compilation Error - CS0583: Internal Compiler Error likely culprit is 'CODEGEN'.


  • I just received this error today.  I'm running Visual Studio 2008

    Everything was working just fine.  I made no code changes just rebooted.    Website runs just fine when running in debug mode but when running through IIS 7.0 I get the error.

    I tried the following info:

    Compiler Error Message: CS0583: Internal Compiler Error (0xc0000005 at address 00000005380E0F9D): likely culprit is 'CODEGEN'.

    c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\9809d9e0\f16415d5\App_Web_irs06hdd.6.cs: error CS0584: Internal Compiler Error: stage 'COMPILE' symbol '<global namespace>'
    c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\9809d9e0\f16415d5\App_Web_irs06hdd.6.cs: error CS0586: Internal Compiler Error: stage 'COMPILE'
    error CS0587: Internal Compiler Error: stage 'COMPILE'
    error CS0587: Internal Compiler Error: stage 'BEGIN'



    Wednesday, September 15, 2010 5:41 AM

All replies

  • Hi,

    Please refer below link, may be it is useful,



    Wednesday, September 15, 2010 6:59 AM
  • This is the first thing I did.  I searched for all pdb files and deleted them.  Then I did a clean solution and a complete rebuild.  I get the exact same error.  The weird thing was everything was working just fine a day ago.  Nothing changed.   When I run the code through Visual Studio 2008 debugger where the website runs within Visual Studio everything works just fine.  But when running within IIS7 I get the error.   I also tried deleting the Temporary ASP.NET temporary Files but still get the error. 

    Has Microsoft fixed this bug in Visual Studio 2008?  

    Before I uninstall/reinstall Visual Studio 2008 is there something I can do such as get a more detail report and send it to Microsoft? 

    I have another development box setup with the exact same setup.  I'm going to copy my project over to that environment and test it out.  If it loads successfully on the other machine then I know that the compiler on the current dev box is corrupted.  If I'm able to replicate the issue on another development box then what I might end reinstalling VS 2008 and trying it again.  Worst case I'll upgrade to Visual Studio 2010 but this would require a lot of work to migrate all projects.

    Wednesday, September 15, 2010 3:16 PM
  • Hi plandis,

    Since it is issue, I suggest you post it on forum, where you can get better reply.


    Best regards,

    Guang-ming Bian

    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact

    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    Monday, September 20, 2010 5:05 AM