Jump to content

Fatal Error


Zorak442

Recommended Posts

Hi Everyone,

 

I am new here.

Back in the day, I was a member of quite a few FS forums.

 

Anyways...

I am running Windows 7 and I just installed FSX for the first time.

As the splash screen comes up, within seconds, I get a window saying "A Fatal Error Has occurred."

 

I have Googled this a few times and issues from 2010 are the top results.

I was wondering if anyone could shine some light on this issue for me.

 

I tried installing that .dll file and placing in the FSX folder, but of course that did not solve the problem either.

 

Thanks so much!

Link to comment
Share on other sites

Welcome! In order to assist you we will need to know what the faulting module is that's causing the fatal error.

 

Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events.

One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area.

 

Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting.

 

 

BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE!

 

General Tab:

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

Faulting module name: This is what we need to Know!

Exception code: 0xc0000005

Fault offset: 0x0000ee3a

Faulting process id: 0x748

Faulting application start time: 0x01ce0253dc4b69d4

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

Faulting module path: R:\FSX\window.dll

Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1

 

If there is not one listed:

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

you will need to do as previously noted

 

 

No Faulting Module? ->

Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test.

Be sure to test each thoroughly before moving on to the next

Still thinking about a new flightsim only computer!  ✈️

Link to comment
Share on other sites

Here a texture issue is suggested as cause.

Poster tries "Repair", but eventually finds texture issue was the cause indeed.

 

(repair fixed the simprop error, but then a visualfx error showed. Could have been the visualfx error causing it all along. Sometimes one module crashes (visualfx for example), and causes another (simprop.dll) to crash as well. The simprop error is then in the logs, and the original faulting module is not shown.)

 

btw, faulting module sounds weird, but is just, "module that crashes".

Doesn't have to be a faulty .dll file. And actually usually isn't. But instead, the module crashes because it tries to show another file, and that is missing so it can't be called. (in this case a texture.)

 

This is the thread:

http://www.avsim.com/topic/389803-fsx-wont-load-simpropdll-fault/

[sIGPIC][/sIGPIC]
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...