Fatal Error message on FSX launch...need some help (re-posting)

[Lateral-G]

I'm re-posting this subject again since the previous thread was locked due to forum formatting problems and I have yet to find a solution......



This just started happening and not sure why:

I boot up FSX and get "a fatal error has occurred" dialog box.

I deleted the cfg files and am able to get to the settings menu but as soon as i try free flight up comes the fatal error screen.

I've deleted the logbook thinking that may be the problem but no joy there either.

I've tried searching the web but I get little info other than deleting the cfg file or the prefetch file (which I tried as well to no effect)

I'm running XP and the sim worked fine yesterday. No recent add-ons or programs have been installed either.

I'm at a loss here. Any suggestions?

-G-

[Oelwanne]

Maybe you have a wrong Entry in the dll.xml? Just an idea....
That had caused a same Problem for me once.
If you have installed an Addon witch uses a specific dll there must be " normaly" a backup called
dll-xml-before_AddonXXX_was_installed. If you have such an Backup try to use that dll.xml.
You found it in the same location as the fsx.cfg.
Don´t forget to backup your current dll.xml.

[Daube]

Does this happen even if you try to start with the Cessna 172 at Seattle ?
Did you check what kind of modules are active during a flight ? Did you try to kill them first ?

[Lateral-G]

Does this happen even if you try to start with the Cessna 172 at Seattle ?
Did you check what kind of modules are active during a flight ? Did you try to kill them first ?

You can't even get the menu screen to come up. All that happens is the splash screen appears for about 30 to 40 seconds then the fatal error window pops up.

If I could get to a menu it might help but that won't even happen.


Oelwanne:
Maybe you have a wrong Entry in the dll.xml? Just an idea....
That had caused a same Problem for me once.
If you have installed an Addon witch uses a specific dll there must be " normaly" a backup called
dll-xml-before_AddonXXX_was_installed. If you have such an Backup try to use that dll.xml.
You found it in the same location as the fsx.cfg.
Don´t forget to backup your current dll.xml. What would a 'wrong' entry in the dll.xml look like? The problem just started. I had not installed any add-ons for some time prior.

What would this Backup that you mention look like? what sort of file name?

[BASys]

Hi Folks

Lateral-G -
Cheers for re-opening this thread.

Sorry I didn't get back earlier,
been tied up prepping for house move.



Before editing your dll.XML and exe.xml
there's something I'd noticed from your fsx.CFG.

FSX is trying to preload your default flight.

If there's an issue with locating either aircraft or required scenery,
it might cause your error.



In your fsx.CFG, section titled [Main],
please try adding the following -

DisablePreload=1

Fire up FSX.
Does that allow fsx to load fully ?

If so,
create and save a new default flight.



If otherwise,
next step will be to investigate be those dll.XML and exe.xml addon entries.



HTH
ATB
Paul

[Lateral-G]

Paul,

No joy on that code added to the fsx.cfg file..............

-G-

[BASys]

Hi Folks

Lateral-G -
My apologies I mean't to edit my post to add -

Please zip up your dll.xml and exe.xml
then attach the zip to your post.

I'll then clean them up to default state.

If unable to add attachments,
please see you PMs, and email them to that address.

HTH
ATB
Paul

[Lateral-G]

Paul,

I'll get the files to you this evening......

thanks

[Lateral-G]

Paul,

Noted files attached.....

[BASys]

Hi Folks

Lateral-G-
Please find a zip of clean dll.xml and exe.xml files attached.

Does FSX now boot to the GUI menu ?

If YES, try a flight.

Does FSX launch the flight successfully ?

Does the FSX in-game menu display the 3 SDK tools ?



HTH
ATB
Paul

[Lateral-G]

Hi Paul,

Unfortunately no joy. The same fatal error occurs before FSX can even get to any menu screen. I installed the two files and launched FSX. It went thru a routine of rebuilding the scenery files then right after that promptly crashed.

.......

-G-

[BASys]

Hi Folks

Lateral -
Ok, so its not java related, nor the dll.xml related addons.

Just to be sure -
- rename dll.xml as dll.disabled
- rename exe.xml as exe.disabled



Question -
Whenever you've tried to launch fsx since the problem began,
does it attempt to rebuild the scenery index -
- sometimes ?
- every time ?
- this last time only ?

Please zip and attach your scenery.cfg.



Could you also please -


Download Martin Gossman's ADE9X-Environment-Checker-Setup (http://www.interkultur.de/gossmann/fsx/download.php)
Run ADE-Checker to generate a PC / FS configuration report.
Save that report (menu -> File -> Save report).

Then zip and attach the report here.



HTH
ATB
Paul

[Lateral-G]

Hi Folks

Lateral -
Ok, so its not java related, nor the dll.xml related addons.

Just to be sure -
- rename dll.xml as dll.disabled
- rename exe.xml as exe.disabled


I completely removed the old files and installed the new ones from your zip.

do you want me to also rename those new xml files just installed to .disabled?



Question -
Whenever you've tried to launch fsx since the problem began,
does it attempt to rebuild the scenery index -
- sometimes ?
- every time ?
- this last time only ?
This last time only.



Please zip and attach your scenery.cfg.
see attached...



Could you also please -


Download Martin Gossman's ADE9X-Environment-Checker-Setup (http://www.interkultur.de/gossmann/fsx/download.php)
Run ADE-Checker to generate a PC / FS configuration report.
Save that report (menu -> File -> Save report).

Then zip and attach the report here.
also see attached..

[BASys]

Hi Folks

Lateral -
Yes, rename both xmls as disabled.



Looking back at your original thread posts
prompted my request for your ADE-Check report.

The report shows your current active FSX installation,
as extracted from your registry, as -
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X\

Your SDK installation -
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll
also utilises this registry path entry.
i.e.
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll



If I've understood your posts correctly -

Your NEW FSX installation,
which you're trying to run,
is located at -
C:\a old pc\Program Files\Microsoft Games\Microsoft Flight Simulator X\

Your OLD FSX installation,
which you should have uninstalled,
is located at -
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X\



Please download the free FSX Registry Utility, from -
http://www.tweakfs.com/store/free_tools.php

Run it to correct your FSX path.
It'll likely prevent your old installation on H:\ from running.



Does the new FSX version on C:\ now launch correctly ?



HTH
ATB
Paul

[Lateral-G]

Hi Folks

Lateral -
Yes, rename both xmls as disabled.



Looking back at your original thread posts
prompted my request for your ADE-Check report.

The report shows your current active FSX installation,
as extracted from your registry, as -
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X\

Your SDK installation -
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll
also utilises this registry path entry.
i.e.
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll



If I've understood your posts correctly -

Your NEW FSX installation,
which you're trying to run,
is located at -
C:\a old pc\Program Files\Microsoft Games\Microsoft Flight Simulator X\

Your OLD FSX installation,
which you should have uninstalled,
is located at -
H:\Program Files\Microsoft Games\Microsoft Flight Simulator X\



Please download the free FSX Registry Utility, from -
http://www.tweakfs.com/store/free_tools.php

Run it to correct your FSX path.
It'll likely prevent your old installation on H:\ from running.



Does the new FSX version on C:\ now launch correctly ?



HTH
ATB
Paul

The "new" version of FSX on the C drive is actually my old install of FSX. My PC suffered a bad virus early this year. I had/have two hard drives. The original C drive was my main drive and was the one infected and had to be reformatted. The files were able to be saved and were moved to the newer, secondary hard drive I had (which was primarily used for data storage). This save included my original install of FSX. The original hard drive ended up being re-named H. The second hard drive (with all the recovered files) was re-named C. Confused yet?

Anyway, I re-installed FSX on the H drive (the original one). I kept the previous install intact on the secondary drive (which is now called C). Until this problem I had been running FSX from the H drive. Once the fatal error started I was able to run the other FSX install from the C drive. This install on the C drive works. However, I still want to be able to run FSX from it's location on the main drive (H).

Previously I was able to run FSX from either drive.

[Spikehughes]

"I boot up FSX and get "a fatal error has occurred" dialog box.

This happened to me and my solution was to remove the D3d9.dll startup and enbseries.ini files in the root FSX folder. Relaunching FSX without these made it all work. If you use these mods give it a try.

Spike

[Lateral-G]

"I boot up FSX and get "a fatal error has occurred" dialog box.

This happened to me and my solution was to remove the D3d9.dll startup and enbseries.ini files in the root FSX folder. Relaunching FSX without these made it all work. If you use these mods give it a try.

Spike


The files you noted are not in the main FSX folder (H:\Program Files\Microsoft Games\Microsoft Flight Simulator X)

TheD3d9.dll is located in the H:\WINDOWS\system32 folder. I do not have enbseries.ini anywhere.

Can you elaborate as to what these files do?

-G-

[Spikehughes]

If you don't know what they do then chances are they are not the issue. Both files are part of HDR lighting effects. Used instead of the built in FSX HDR because their performance is better. You would have had to manually install them as an enhancement.
Please - Do not delete the System32 D3D9.Dll.

Spike

[BASys]

Hi Folks

Lateral -
Ok, so H:\ is your primary FSX installation.

Did you rename both xmls as .disabled ?

After doing so,
on launching FSX -
Does FSX display the GUI menu ?

If yes -
Try clicking freeflight, and launching an entirely new flight,
(NOT loading a saved, NOR your default situation).

Does this new flight load ?

HTH
ATB
Paul

[Lateral-G]

Hi Folks

Lateral -
Ok, so H:\ is your primary FSX installation.

Did you rename both xmls as .disabled ?

After doing so,
on launching FSX -
Does FSX display the GUI menu ?

If yes -
Try clicking freeflight, and launching an entirely new flight,
(NOT loading a saved, NOR your default situation).

Does this new flight load ?

HTH
ATB
Paul

Both were labeled as .disabled

Still no joy.....fatal error.

I did download the registry editor and looked at the registry entries:

the HKEY_CURRENT_USER points to the C drive location for my "backup" FSX

the HKEY_LOCAL_MACHINE points to the H drive for the other FSX

[BASys]

Hi Folks

Lateral -
Set both registry paths to point at H:\

ATB
Paul

[Lateral-G]

Hi Folks

Lateral -
Set both registry paths to point at H:\

ATB
Paul

If I do and it still doesn't work can I revert back?

[BASys]

Hi Folks


If I do and it still doesn't work can I revert back?
Lateral -
You're missing the point -

The FSX path registry entry is NOT optional,

It's essential to the functioning of FSX.



However,
Yes, it could be reverted afterwards.

Do not revert back until we've got this working.



HTH
ATB
Paul

[Lateral-G]

Hi Folks


Lateral -
You're missing the point -

The FSX path registry entry is NOT optional,

It's essential to the functioning of FSX.



However,
Yes, it could be reverted afterwards.

Do not revert back until we've got this working.



HTH
ATB
Paul


I changed the registry entries to match.

Still no joy.....

[BASys]

Hi Folks

Lateral -
As you've now corrected the registry paths,
please look at your Event Log,
and post the errors reported for FSX.

ATB
Paul

[Lateral-G]

Hi Folks

Lateral -
As you've now corrected the registry paths,
please look at your Event Log,
and post the errors reported for FSX.

ATB
Paul

There was no item in the event log for FSX...........

:confused:

[BASys]

Hi Folks

Lateral -
OK.

Please look at the properties of the shortcut which you use to launch FSX.

Ensure that both - Target and Start In,
point to your H:\ drive FSX installation.

ATB
Paul