General Category > General Discussion

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

<< < (2/4) > >>

virtuali:

--- Quote from: data63 on December 22, 2014, 08:07:03 pm ---I didn't run the Installers "offline" (maybe I'll try that...)
--- End quote ---

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:

--- Quote from: virtuali on December 22, 2014, 09:11:46 pm ---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.

--- End quote ---

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:

--- Quote from: Lude2Envy on December 22, 2014, 10:42:27 pm ---Installed KLAS and I'm having the same CTDs. Here's the event view summary but its not showing the faulting module:
--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version