Log Name: Application

Source: Application Error

Date: 10/4/2012 9:43:52 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Ryan-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

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

Exception code: 0xc0000005

Fault offset: 0xc74c85c3

Faulting process id: 0xd68

Faulting application start time: 0x01cda2a5d0fb0306

Faulting application path: C:\FSX\fsx.exe

Faulting module path: unknown

Report Id: e0f241a4-0e9e-11e2-9647-c8bcc8920370

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="2012-10-05T03:43:52.000000000Z" />

<EventRecordID>2616</EventRecordID>

<Channel>Application</Channel>

<Computer>Ryan-PC</Computer>

<Security />

</System>

<EventData>

<Data>fsx.exe</Data>

<Data>10.0.61472.0</Data>

<Data>475e17d3</Data>

<Data>unknown</Data>

<Data>0.0.0.0</Data>

<Data>00000000</Data>

<Data>c0000005</Data>

<Data>c74c85c3</Data>

<Data>d68</Data>

<Data>01cda2a5d0fb0306</Data>

<Data>C:\FSX\fsx.exe</Data>

<Data>unknown</Data>

<Data>e0f241a4-0e9e-11e2-9647-c8bcc8920370</Data>

</EventData>

</Event>

 

I am running windows 7 64BIT any help would be greatly appreciated

Hi Ryan,

We need to know what you were doing before the crash. Where did it crash? After FSX was fully loaded or at the startup screen? What aircraft? What scenery (commercial or default). The only thing that shows up in the above report is that you had a memory_access_violation. So, when FSX was trying to call a texture, a gauge, an effect, a module, it couldn't as the item was not where it was suppose to be. Normally there are faulting modules shown in the CTD report but yours shows none which indicates to me it's not a module but a texture or gauge. Did you just install something new into FSX? An aircraft or scenery? You can troubleshoot sceneries by going into the Scenery Library and disabling the top scenery (that's normally the last scenery you installed unless you moved it up/down in the Scenery Library. Another possibility is your video card drivers. If you recently updated your video card drivers, perhaps they did not install correctly.

 

Another possibility is overheating/overclocking your computer and system BIOS settings are not set properly. If your CPU voltage is too high or too low, FSX will crash. If your system memory is not set properly in the BIOS (timing, frequencies, voltages), FSX will crash.

 

Lastly, FSX relies on Microsoft.net (dotnet) to run properly. Dotnet also handles memory functions for FSX and any addons. Windows 7 should have installed all versions of dotnet on your computer and you should look in your Windows/Microsoft.net/Framework32/(a folder for each version). Dotnet applications are not backward compatible. Most important is that Dotnet 3.5 is installed. Same goes with Microsoft Visuals C++ Redistributables 2005, 2008 and 2010. MSV's are used by Microsoft and addon developers to properly install FSX and addons. FSX was built around MSV 2005 but later addons were developed with MSV 2008 and 2010.

 

Hope this helps.

 

Best regards,

Jim

I just slapped myself in the face! Forgot to mention one of the best methods of fixing a CTD is to rename your FSX.cfg to say, FSX.orig then restart FSX and let the config rebuild. If the crash goes away then it was something in your FSX.cfg that caused the problem. If the CTD's continue you can simply go back and rename the fsx.orig back to fsx.cfg and follow my suggestions above.

 

Best regards,

Jim