FSX crashes with bglmanx.dll V2.9.25 **SOLVED**

[data63]

Hi,

After I reinstalled some FSDT Sceneries getting the newest bglmanx.dll my FSXe crashes every time I start it (sometimes before the start-screen, sometimes in the loading process after the start-screen.

I reverted back to the previous (2.9.24) version which seems to have fixed the problem.

Happy Landings

juergen

[virtuali]

You must have mixed up versions somehow, you cannot revert back or updated just by replacing the .dll file, if the .dll file and the associated .dat files are not all from the same version, FSX will surely crash on start.

You cannot get mixed up version by running the installers normally, the only way is to manually replace files, because all installers downloads the very latest version online.

Just run the current Stand-Alone Addon Manager and don't replace files manually. If you are still getting a crash, contact me in private so I can have a look at your system.

[data63]

I did go back to 2.9.24 reverting the dll and dat files 

however installing the newest version (2.9.25 - standalone or within a scenery installer, I tried both for several times) brought me that crashing FSX.

with 2.9.24 it's running flawless.

[virtuali]

I did go back to 2.9.24 reverting the dll and dat files

Running the installer with the network disconnected too ?

however installing the newest version (2.9.25 - standalone or within a scenery installer, I tried both for several times) brought me that crashing FSX.

Try to go into the Windows Event Viewer, and see the error details for your FSX.EXE crash, and report back with the details, so we can check what really crashed.

[data63]

Hi!
I didn't run the Installers "offline" (maybe I'll try that...)

the Event-Viewer just says

--------
Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0xffb800ae
ID des fehlerhaften Prozesses: 0x1474
Startzeit der fehlerhaften Anwendung: 0x01d01e03fc1c030c
Pfad der fehlerhaften Anwendung: D:\FSX\fsx.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: f4c3e2f6-89f7-11e4-9b68-7824af41c979
---------

[virtuali]

I didn't run the Installers "offline" (maybe I'll try that...)

That's only useful if you want to "revert" back to an old version, provided you have the installer for that. If you run the installer online, it will always get you the correct files, provided nothing bad happens while downloading, which includes (for example) an antivirus blocking some files and passing others, creating a version mismatch, or the antivirus trying to "heal" the file, corrupting it.

Try to install again the latest Addon Manager and, after the download, check the digital signature of the D:\FSX\bglmanx.dll file. If it's valid, you know you got the right download, if it's not, perhaps the antivirus has corrupted it trying to "heal" it, so you must be sure you have turned it off when downloading and installing.

[willultra99]

this is happening to me as well.  I downloaded the latest Stand alone add-on manger for GSX.  ever since than I have been getting CTD's.  I downloaded it today.  I uninstalled all FSdreamteam and Flightbeam sceneries and have not had any trouble since.  When I go into details after FSX crashes two files come up C:\user\myaccount\AppData\Local\Wer4157.tmpWERI
                                                                                                                                                         C:\user\myaccount\AppData\Local\WER5832.tmpmdmp

I have no sceneries of FSdreamteam and Flightbeam installed.  Any help would be great.

Thanks,
William Coade

[virtuali]

As I've said in my previous message, try to go into the Windows Event Viewer, and see the error details for your FSX.EXE crash, and report back with the details, so we can check what really crashed.

And, check the digital signature of the FSX\bglmanx.dll file. If it's valid, you know you got the right download, if it's not, perhaps the antivirus has corrupted it trying to "heal" it, so you must be sure you have turned it off when downloading and installing.

[Lude2Envy]

As I've said in my previous message, try to go into the Windows Event Viewer, and see the error details for your FSX.EXE crash, and report back with the details, so we can check what really crashed.

And, check the digital signature of the FSX\bglmanx.dll file. If it's valid, you know you got the right download, if it's not, perhaps the antivirus has corrupted it trying to "heal" it, so you must be sure you have turned it off when downloading and installing.

I just reinstalled KLAS and I'm having the same CTDs. Here's the event view summary but its not showing the faulting module:

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: 0xffba00ae
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

[virtuali]

Installed KLAS and I'm having the same CTDs. Here's the event view summary but its not showing the faulting module:

That seems to indicate your crash doesn't have anything to do with any of our modules. If it did, you would have seen a crash in bglmanx.dll or Couatl.exe.

And, as I've said in my previous two replies, check the digital signature of the FSX\bglmanx.dll file.

If it's valid, you know you got the right download, if it's not, perhaps the antivirus has corrupted it trying to "heal" it, so you must be sure you have turned it off when downloading and installing.

[sebyh]

Umberto could the issues reported in this form be linked to the new addon manager update and the "STEAM version message" me and others have been having.

Could some of the above users have installed the update and failed to notice the Steam message?

[virtuali]

Umberto could the issues reported in this form be linked to the new addon manager update and the "STEAM version message" me and others have been having.

There's a new Addon Manager to support Steam, but the "steam version" message was an installer bug which has been fixed already in the current installer, and can't have anything to do with supposed crashes (which I can't see in any of the logs they are caused by the Addon Manager), because the installation didn't proceed in that case.

Could you please try again reinstalling, checking your bglmanx.dll digital signature file is valid ?

[space_coast]

After some continous trial and error, I saw the following:

FSX + GoFlight Driver + FSDT Products = bglmanx.dll issue
FSX + GoFlight = works fine
FSX + FSDT = works fine
FSX = as itself, works fine


What do these two models have in common?

[virtuali]

After some continous trial and error, I saw the following:

FSX + GoFlight Driver + FSDT Products = bglmanx.dll issue
FSX + GoFlight = works fine
FSX + FSDT = works fine
FSX = as itself, works fine


What do these two models have in common?¡

I've installed the GoFlight software, and there are no problems with it together with any FSDT modules. But since I don't have any GoFlight hardware, I can't possibly know if the conflict appears only if there's a GoFlight hardware connected.

I had a look at their software, and while they install several versions of VC++ runtimes (the most likely cause of potential conflicts), they seem to use only the Visual Studio 2012 version of the runtimes. We use the 2005 version, intentionally, because that's the one used by FSX itself so, in theory, it should be the safest to use when running inside FSX.

[data63]

I didn't run the Installers "offline" (maybe I'll try that...)

That's only useful if you want to "revert" back to an old version, provided you have the installer for that. If you run the installer online, it will always get you the correct files, provided nothing bad happens while downloading, which includes (for example) an antivirus blocking some files and passing others, creating a version mismatch, or the antivirus trying to "heal" the file, corrupting it.

Try to install again the latest Addon Manager and, after the download, check the digital signature of the D:\FSX\bglmanx.dll file. If it's valid, you know you got the right download, if it's not, perhaps the antivirus has corrupted it trying to "heal" it, so you must be sure you have turned it off when downloading and installing.

I finally removed KJFK2 (instead of KIAH) - an reinstalledit with a freshly dowloaded installer - now anything looks ok!

the bglmanx - although same Version indicated - has a different size (digital sig is ok) - maybe AV is teh culprit (I checked the logs - no sign of blocked files)

thanks for all helping

happy landings

juergen