General Category > General Discussion

bglmanx.dll error (random)

<< < (2/2)

bojote:
BTW, if you are wondering why I'm so obssesed with 'bugs' or problems in my FSX setup it is because in March 2009 (after 30 minutes of making cockpit preparations, getting clerance and right on time for my time slot in cross the pond 2009 (a VATSIM event) I suffered a CTD when opening the Level-D ground menu. Evidently, I lost my slot and departed last that day.

Ever since that problem, I check and re-check my setup for 'potential' problems... so, far the only two were 'Add-On Manager' (when starting FSX and NOT critical) and the level-D CTD ground menu (non-critical as well) because it happens very very few times. However, as a programer I'm pretty sure that even though some times I don't get a CTD something could be leaking memory and it will manifest itself as a CTD in the middle of the atlantic ocean.... so, I'm sorry to be a pest, but afterall it help us all...

P.D still going like the energizer bunny starting and re-starting FSX... no more 'Splash screen freezes'

virtuali:

--- Quote from: bojote on January 26, 2010, 06:28:22 pm ---and the level-D CTD ground menu (non-critical as well) because it happens very very few times. However, as a programer I'm pretty sure that even though some times I don't get a CTD something could be leaking memory and it will manifest itself as a CTD in the middle of the atlantic ocean.... so, I'm sorry to be a pest, but afterall it help us all...
--- End quote ---

Wasn't the Level-D crash happening inside NTDLL.DLL ? In that case, I think it's a very different issue, since NTDLL.DLL is part of the basic Windows services, and there's only one NTDLL.DLL in all the system so, it's nothing related to C++ runtimes and the issues of having different versions of the runtimes installed at the same time, which in turns involves WinSxS, and all related complications with manifests, etc.

It might be helpful, soon after it happens, to check the Windows Event viewer to find the error, and report to Level-D people the various error codes of the Event, maybe they might have a better idea what they mean.

bojote:

--- Quote from: virtuali on January 26, 2010, 08:05:17 pm ---Wasn't the Level-D crash happening inside NTDLL.DLL ? In that case, I think it's a very different issue, since NTDLL.DLL is part of the
--- End quote ---

Yes, it is. in fact, its a NTDLL.DLL C000005 error, which is an access violation memory error. I'm guessing its a bad pointer of conflicting memory location but the ocurrence is random, hard to replicate and happens very, very few times. I plan on using process explorer to see the stack and analyze whats going on behind the scenes. as a last resort I'll try to use a Windows Version of the Linux utility strace to see what else I can see.

Its hard to tell a developer about a bug if you can not even have a test case scenario to replicate it. The only solid clue I have so far is that this bug is related somehow to the 'transparent' window use of those menus, maybe a conflict with the FSX ATC (which is already disabled) but maybe it is still creating a conflict. I have some other ideas under my sleeve but, they will have to wait... time for Mass Effect 2 :)

Navigation

[0] Message Index

[*] Previous page