Visual C# Command Line Compiler error

About a week ago I had this error box pop up saying Visual C# Command Line Compiler had stopped working, and I thought it was just windows being windows so rebooted all ok. Then yesterday it appeared again, and I clicked closed and it went away. Has anyone come across this before?

In the action centre (i'm running windows 7 64-bit) it give this info:

Description
Faulting Application Path: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: csc.exe
Application Version: 8.0.50727.4927
Application Timestamp: 4a275157
Fault Module Name: csc.exe
Fault Module Version: 8.0.50727.4927
Fault Module Timestamp: 4a275157
Exception Code: c0000005
Exception Offset: 000000000000ee26
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 740b
Additional Information 2: 740be8efbc0ae3289d88713eaa9245f5
Additional Information 3: 4508
Additional Information 4: 4508307cfa77360d5b9f5b7a31a1ca50


I should add that my pc has been running fine with nothing going weird, and also internet speeds etc are fine.

Virus scan clean!

Does this error occur when launching a game? and is there a chance you are using ATI graphics?

Or is this a generic error?

It does not occur when starting a game, and both times it has happened my computer was just idle. I just had bbc news webpage open thats all. And yes I have a HD 6900 ATI card. I have not installed anything new apart from the normal windows updates, and this has me worried and confused!

What do you mean by generic error?

the csc is used by some older .net programs that want to dynamically create code on the fly.

I'm guessing you have some odd peice of software, that aside from been badly written, is failing in some way.

If you install process explorer (part of sysinternals suite) next time the error comes up, use process explorer and figure out which process spawned the csc error.

Quote:

---

Originally Posted by TheAnimus

the csc is used by some older .net programs that want to dynamically create code on the fly.

I'm guessing you have some odd peice of software, that aside from been badly written, is failing in some way.

If you install process explorer (part of sysinternals suite) next time the error comes up, use process explorer and figure out which process spawned the csc error.

---

I would have no idea how to do that :| Wish there was some simple fix, and its odd how it happened a week apart. Also no programs are running apart from firefox, which I think I had open yesterday but not sure.

csc.exe is just the c# compiler.
An easy way of fixing the problem would just be to go to add and remove programs and uninstall the .net framework, then reinstall it.

Download the latest version from Microsoft here, but you can leave it till an application asks for it.

Quote:

---

Originally Posted by hesham1516

An easy way of fixing the problem would just be to go to add and remove programs and uninstall the .net framework, then reinstall it.

---

Only if the problem is with the .net framework, rather than something running in the background that's trying to using it to compile some bad code. The only .NET problem that I can think of that might cause this is if it's happening during an optimisation of the global cache (I once had a laptop that used to grind to a halt one morning in three because of cache "optimisations" :rolleyes:) - that would be an occasional tasks (i.e. it wouldn't happen all the time) and I guess something could have been corrupted during a windows update which would explain why it only just started happening.

I don't think it's the most likely explanation though: whilst the only program *you* are running is firefox, that will be a long way from the only program your computer is running ;) There'll be tens, if not hundreds, of programs running in the background, and any one of them could be causing the problem. It could be scheduled or in response to certain activity, which may not be obvious or even any kind of input from you.

One option might be to look through the normal event log to see what else was happening around the time the csc.exe crashed, in case that gives any indication as to what might be the root cause. There's a reaonable chance that if something asked the compiler to do something and the compiler failed, another program will have stopped immediately after the failure. it may have left a trace in the event log. Probably worth a look...

I have updated my gfx drivers just in case, and will check my event log.

Quote:

---

Originally Posted by hesham1516

Does this error occur when launching a game? and is there a chance you are using ATI graphics?

Or is this a generic error?

---

It happened again :| Any reason why you asked if I had an AIT card, is there some link?

NET framework 2.0, 3.0 and 3.5 are installed on default on Windows 7 machine so it cannot be removed unless you mean the Windows Update of them. Another thing to look into is your anti-virus logs to see if it is locking or stopping CSC.exe.

Run "sfc /scannow" from elevated command prompt and give it a reboot to see if the error pops up. If that does not fix it, Start menu -> Control Panel -> Uninstall a program -> Turn Windows features on or off.

1. Check whether the checkbox of the .NET Framework 3.5.1 has been selected, if so, un-select the check box, click OK;
2. Open the Turn Windows features on or off window again, and select the checkbox of .NET Framework 3.5.1, click OK.

If that does not work, update your .NET framework to latest version which is 4.0

edit: If this happening weekly... sound like something is schedule to run so check task scheduler to see what is task has been created to run specifically that day or what programs have schedule to run that day.