It has happened 3 or 4 times. Last time, I copied the reports from Event viewer:at 11:35:47.NET Runtime version 2.0.50727.5448 - Fatal Execution Engine Error (6757E932) (80131506)At 11:35:47Faulting application name: AS2012_Exec.exe, version: 13.1.4387.37836, time stamp: 0x4f069a39Faulting module name: mscorwks.dll, version: 2.0.50727.5448, time stamp: 0x4e154bceException code: 0xc0000005Fault offset: 0x000a86bfFaulting process id: 0x%9Faulting application start time: 0x%10Faulting application path: %11Faulting module path: %12Report Id: %13at 11:37:19The program AS2012_Exec.exe version 13.1.4387.37836 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.Process ID: 6fcStart Time: 01ccf4697173def9Termination Time: 0Application Path: C:\Program Files\HiFi\AS2012\AS2012_Exec.exeReport Id: 73bb772d-605d-11e1-bca8-001731f8cf2dCould anyone please give some feedback on if it's some system culprit or AS2012?

Not sure of the culprit but have had a similar issue on occasion, not a regular happening:Faulting application name: AS2012_Exec.exe, version: 13.1.4387.37836, time stamp: 0x4f069a39Faulting module name: mscorwks.dll, version: 2.0.50727.5448, time stamp: 0x4e154bceException code: 0xc0000005Fault offset: 0x000ad97cFaulting process id: 0x%9Faulting application start time: 0x%10Faulting application path: %11Faulting module path: %12Report Id: %13

It has happened 3 or 4 times. Last time, I copied the reports from Event viewer:at 11:35:47.NET Runtime version 2.0.50727.5448 - Fatal Execution Engine Error (6757E932) (80131506)At 11:35:47Faulting application name: AS2012_Exec.exe, version: 13.1.4387.37836, time stamp: 0x4f069a39Faulting module name: mscorwks.dll, version: 2.0.50727.5448, time stamp: 0x4e154bceException code: 0xc0000005Fault offset: 0x000a86bfFaulting process id: 0x%9Faulting application start time: 0x%10Faulting application path: %11Faulting module path: %12Report Id: %13at 11:37:19The program AS2012_Exec.exe version 13.1.4387.37836 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.Process ID: 6fcStart Time: 01ccf4697173def9Termination Time: 0Application Path: C:Program FilesHiFiAS2012AS2012_Exec.exeReport Id: 73bb772d-605d-11e1-bca8-001731f8cf2dCould anyone please give some feedback on if it's some system culprit or AS2012?

mscorwks.dll is a core library for the .NET 2.0 framework. The first thing you can do is make sure that you have applied all available service packs to the framework and that the framework is installed properly by using the tool found here http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx. This will require you to have some degree of computer competence since it is a command line tool. If you aren't comfortable with that then a support ticket is probably in order along with the crash event data you've provided here and a description of what you were doing at the time it occurred - if a crash dump got generated and you know how to find it, it would be good to include it. If this always occurs with a particular flight plan or at a particular place then be sure and include the plan or location or both. One other thing you might try is to install the 4387 beta patch above. This error was never seen during AS2012 testing and basically means that something got stepped on in memory when .NET was asked to do something by the program.DJ

DJ,I ran the .NET Framework verification tool and it returned no errors.AS2012 has crashed a total of only 3 times in a two month period with the same error. If it occurs again will submit a ticket.Have been running 4387 since it became available.EDIT: As an after thought I'm certain this has occured each time when starting FSX. having processed a flightplan and submitted snapshots from AS2012 via client.

Edited February 26, 201214 yr by srcooke

DJ,I ran the .NET Framework verification tool and it returned no errors.AS2012 has crashed a total of only 3 times in a two month period with the same error. If it occurs again will submit a ticket.Have been running 4387 since it became available.EDIT: As an after thought I'm certain this has occured each time when starting FSX. having processed a flightplan and submitted snapshots from AS2012 via client.

Good to know and I do recommend the ticket route - you might also make a habit of generating a log prior to loading up FSX so that you have the details on hand when the crash/lockup occurs.DJ

The beta 4387 is installed. I cannot remember if all hangups occured after beta installation or not. The sure thing is that there were hangups after the beta.The .NET verifier found and confirmed the following versions:2 sp23 sp23.5 sp14 client4 fullAll the others were not found.Where could I look for a crash dump?I am certain that it does not involve a particular place or flight plan.

The beta 4387 is installed. I cannot remember if all hangups occured after beta installation or not. The sure thing is that there were hangups after the beta.The .NET verifier found and confirmed the following versions:2 sp23 sp23.5 sp14 client4 fullAll the others were not found.Where could I look for a crash dump?I am certain that it does not involve a particular place or flight plan.

It looks like .NET is up to date. Dumps are found in C:Users(username)AppDataLocalCrashDumps if generated - they aren't readable by tools other than debuggers, but are handy to send to HiFi.DJ

No crash dumps I am afraid for AS. I just found FSX dumps.Do I have to activate somehow the crash dumps for AS2012?

No crash dumps I am afraid for AS. I just found FSX dumps.Do I have to activate somehow the crash dumps for AS2012?

To get dumps you can download a tool from Microsoft... http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4060 that will generate a dump for Win32 processes when a crash occurs. There is no system based setting that will do so for any process that I'm aware of. Other tools are things like winDebug, but if you aren't a programmer don't even go there...Dumps aren't critical - what is important is to open a ticket with all of the information that you have when the hang occurs...DJ