Hi Guy's

i have been running FSX successfully on the sme maching foe several years now. However i now have a fatal error CTD at various points through my FSX experience.

often when on load up but today i have suffered on after 10.5 hrs of tsable from from LAX to LHR. very. frustrating!

 

i havent changed anything for a while and certainly not anything to coincide with my problem.

 

the information in the fatal box says

 

Files that help describe the problem:

C:\Users\Desktop\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\Desktop\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\Desktop\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\Desktop\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\Desktop\AppData\Roaming\Microsoft\FSX\dll.xml

Read our privacy statement online:

http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

 

can anyone help please?

 

Cheers

Daz

dial 911 or 999 and ask for Word Not Allowed.......Dr. FSX :lol:

dial 911 or 999 and ask for Word Not Allowed.......Dr. FSX :lol:

 

? lost me

what does that mean?

Word Not Allowed is an AVSIM Staff Member who can help with your problem, send him a PM.

the information in the fatal box says

 

You need to send us information from your Event Viewer. This records every CTD or 'event' that occurs on your computer. To get to the Event Viewer, click on the Start button and, in the search box, type Event Viewer, then look up in the menu and click on Event Viewer. Once open, open Windows Logs, then Application. In the far right column under Actions, click on Find.... In that box type FSX then hit return. You will then get every FSX error. Click on the last one you referenced in your post. Again, look in the far right column and click on Copy then Copy details as text. Now post again and click paste the information in your post. The cause of your crash should be shown but not a guarantee it's the actual problem. We have to investigate. From my experiences, long flight crashes are caused by overheating or your CPU voltage set too high or too low. Please provide us with information on your system too. Are you running FSX in Windows 7 64 bit? Thanks.

 

Best regards,

Jim

You need to send us information from your Event Viewer. This records every CTD or 'event' that occurs on your computer. To get to the Event Viewer, click on the Start button and, in the search box, type Event Viewer, then look up in the menu and click on Event Viewer. Once open, open Windows Logs, then Application. In the far right column under Actions, click on Find.... In that box type FSX then hit return. You will then get every FSX error. Click on the last one you referenced in your post. Again, look in the far right column and click on Copy then Copy details as text. Now post again and click paste the information in your post. The cause of your crash should be shown but not a guarantee it's the actual problem. We have to investigate. From my experiences, long flight crashes are caused by overheating or your CPU voltage set too high or too low. Please provide us with information on your system too. Are you running FSX in Windows 7 64 bit? Thanks.

 

Best regards,

Jim

 

 

Excellent - Thanks for your help

 

there are 4 errors in very close succession. copied below

 

Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.

 

Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgosweep.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="ia64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.

 

Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgocvt.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="ia64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: d3d9.dll, version: 0.0.0.0, time stamp: 0x4b926eb5

Exception code: 0xc0000005

Fault offset: 0x0000155f

Faulting process id: 0x778

Faulting application start time: 0x01cd7bc5e52d14e6

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\d3d9.dll

Report Id: 47da73db-e7b9-11e1-bb97-00235451a15f

 

Look forward to hearing back from you

 

thanks again

Look forward to hearing back from you

 

Looks like you have the ENB series module installed. It has been causing major problems for many. I do not know of any solutions. I had problems with it too and had to remove it. Here's a link that might help you - http://forum.avsim.net/topic/302491-enbseries-plug-in-and-altenter-crash/. You can find more discussions on the ENB series by Googling 'ENB Series FSX crash'.

 

Best regards,

Jim

 

And here's another great link on the subject - http://forum.avsim.net/topic/382877-enb-wow/.

 

Best regards,

Jim

HI,

I eventually removed AS2012 after reading the article and submitted a ticket to HIFI. they came back and said they were investigating after the confirmed they ahve never seen that problem before.

 

I have run up FSX this morning and it crashed again within a few minutes. Here is the event log.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7b3

Exception code: 0xc0000005

Fault offset: 0x00034a17

Faulting process id: 0xf84

Faulting application start time: 0x01cd8113a862778a

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Windows\system32\d3d9.dll

Report Id: 063ba2de-ed08-11e1-bae1-00235451a15f

 

 

what have i done wrong?

I eventually removed AS2012 after reading the article and submitted a ticket to HIFI.

 

I am not sure why you removed AS2012 and submitted a ticket to HiFi. The d3d9.dll in your Windows/System32/ folder is related to DirectX. The crash report you reported earlier showed the d3d9.dll in the FSX main directory caused the crash. This dll should be removed or deleted from your main FSX folder. It is a problem with the ENB Series Mod that you installed on your system. You need to delete the d3d9.dll AND the enb.ini in your main FSX directory as this is causing your computer to crash. This Mod has caused a lot of FSX crashes and I think it's not compatible with Windows 7. Why you got the d3d9.dll error in the report above is not known but it is related to DirectX installations. You could have a bad video card driver install or your DirectX installation is corrupted. You can find out if there are any problems with DirectX by doing the following:

 

Click on the Start button, then All Programs, then Accessories and click on Run. Once the run command is open, type the following and hit return: dxdiag. Click on each tab and see if there are any errors. If none, then you will need to scan your system and have it look for corrupted system files. The following link provides details on how to scan your system: http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.

 

 

Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.

 

A: I would delete Adobe Air. Go to Adobe.com and download the latest version.

 

Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgosweep.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="ia64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.

 

Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgocvt.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="ia64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.

 

For the other two errors above: Errors indicate your system is missing a Microsoft Visual C++ Redistributable 2008 package. Based on above information the version you are missing is for VC9 (9.0.21022.8, VC++ 2008 sp1) and its processor architecture is for a 64bit operating system. You can download theMicrosoft Visual C++ 2008 SP1 Redistributable Package (IA64) here.

Hope this helps!

Best regards,

Jim

HI,

Sorry about as2012 - Error in my understanding..

I undertook all the actions above and the only issue that was apprent was the presence of the d3d9 file as you stated./ I have removed that and flown a flight of approximatly 2 hours. Whilst on approach i suffered another CTD annotated as a fatal error again.

 

here is the vent viewer report

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0xb35ea18c

Faulting process id: 0xf34

Faulting application start time: 0x01cd821d8b3d083a

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: 482fa413-ee22-11e1-a7b1-00235451a15f

 

This appears to be a new error?

 

thanks again for your help

 

Daz

This appears to be a new error?

 

This error does not provide any useful information other than you are continuing to have a crash because of a Memory Access Violation (Exception Code: 0xc0000005). Did you download and install that Microsoft Visual 2008 package? That program helps FSX run the way the developers wanted it to run.

 

Best regards,

Jim

Morning,

I did install it yes.

Would I be better to start again and re install fsx? It has been a few years since I installed.

 

Thanks again for your help. I would be stuck without it.

 

Daz

Would I be better to start again and re install fsx? It has been a few years since I installed.

 

In one of the error reports above (Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgosweep.exe"), the Microsoft program 'pgosweep.exe' is used to write all profile data from a running program to the .pgc file. It is possible that this file can be corrupted or replaced by a hacker and turned into a virus or malware. The fact you installed Microsoft Visual 2008 should have replaced this file and your system is back to running normally. I would run an anti-virus program if you haven't already to see if your system is infected. If it is a virus or malware, it will bring your system down with all kinds of problems and slow your system to a crawl. You have not indicated this has occurred, this a couple of crashes running FSX. I would also run a malware program and the best I have seen is Malwarebytes - http://www.malwarebytes.org/. The freeware version will work perfectly. I would also run a freeware registry cleaner. I use Advanced System Care 5 at least weekly to clean up my system - http://www.iobit.com/download.html. They also have a great uninstaller2 program that works better than the Windows Add/Remove program.

 

Before uninstalling/installing FSX, I would check out the info I provided above first and see if that doesn't clean things up a bit and make your system run better. Deleting or renaming the FSX.cfg then restarting FSX will allow the FSX.cfg to rebuild and you'll be back to your default settings. That sometimes fixes all FSX problems. I would make uninstalling/reinstalling FSX a last resort.

 

Make sure you have all of the Microsoft Visual C++ Redistributable packages that are required by FSX and FSX addons. They should be listed in your Add/Remove Programs and they should be from Microsoft Visual 2005, 2008, and 2010 (and soon 2012). There are several updates to these packages. Here's a link to the 2005 SP1 package and below that in the area that says 'what others are downloading', you'll see links to all of the other packages - http://www.microsoft.com/en-us/download/details.aspx?id=5638. After installing any package, make sure you run Windows Update as these packages are updated frequently.

 

Hope this helps.

 

Best regards,

Jim

hello all here is mine report

please help

regards

-----------//------------//------------//------------

Log Name:      Application

Source:        Application Error

Date:          18/3/2013 11:03:13 μμ

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      diatzelo1-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: TCAS2v7.dll, version: 1.1.6.0, time stamp: 0x4633aecd

Exception code: 0xc0000005

Fault offset: 0x00006186

Faulting process id: 0x10d4

Faulting application start time: 0x01ce23fd90bbe52e

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\TCAS2v7.dll

Report Id: 3e768a3e-900f-11e2-92fc-902b34acb2be

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-03-18T21:03:13.000000000Z" />

    <EventRecordID>4314</EventRecordID>

    <Channel>Application</Channel>

    <Computer>diatzelo1-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>TCAS2v7.dll</Data>

    <Data>1.1.6.0</Data>

    <Data>4633aecd</Data>

    <Data>c0000005</Data>

    <Data>00006186</Data>

    <Data>10d4</Data>

    <Data>01ce23fd90bbe52e</Data>

    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\TCAS2v7.dll</Data>

    <Data>3e768a3e-900f-11e2-92fc-902b34acb2be</Data>

  </EventData>

</Event>

The faulting module, the TCAS2v7.dll, is installed with several commercial and freeware addons that was developed by Lee Hetherington's (sp?) TCAS system.  In any case, from my research, it appears you have the latest version installed.  My suggestion would be to reinstall the program that is using the TCAS2v7.dll.  Just do a search for the file on your computer and see what folder it is located in if you do not know what aircraft is using the module.

 

I might add you should make sure you have the latest version of MSV 2005, 2008 and 2010 installed.  I noticed last year that I had suggested this and you indicated you had updated the MSV 2005 but, to be sure, here are the links - 2005 - http://www.microsoft.com/en-us/download/details.aspx?id=26347; 2008 - http://www.microsoft.com/en-us/download/details.aspx?id=26368; and 2010 - http://www.microsoft.com/en-us/download/details.aspx?id=26999.  Since your last error from last year, I have found that the AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html provides more detailed info than the Event Viewer.  If you continue to have problems, please run this program and copy and paste the report back here in this forum.

 

Best regards,

Jim