Jump to content

Archived

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

robbier

Crash To Desktop Referencing "PMDGMD11.dll"

Recommended Posts

Hi Guys,I was about to intercept the localizer at KTPA, and just after pressing the "NAV" button, FSX crashed with a fatal error message referencing "PMDG_MD11.dll" (in the gauges folder).Here are the error logs: "Fault bucket 1206006660, type 1Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: fsx.exeP2: 10.0.61637.0P3: 46fadb14P4: PMDG_MD11.DLLP5: 10.0.61355.62P6: 49b7c81dP7: c0000005P8: 00118301P9: P10: Attached files:C:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\fsx.CFG.txtC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\dxdiag.txtC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\scenery.cfgC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\fdr.datC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\dll.xmlC:\Users\Robert Deichert\AppData\Local\Temp\WER8C1C.tmp.WERInternalMetadata.xmlThese files may be available here:C:\Users\Robert Deichert\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_a4f0d2f6b2b416894fffa9eba2a3cd8b9f376a0_0840b30dAnalysis symbol: Rechecking for solution: 0Report Id: 0629da94-275c-11e0-9022-d8a25e8a8ba2Report Status: 0"And - "Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81dException code: 0xc0000005Fault offset: 0x00118301Faulting process id: 0x264Faulting application start time: 0x01cbbb4bc9bc8b98Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLLReport Id: 0629da94-275c-11e0-9022-d8a25e8a8ba2"After I got the error message, I also got this message/error: "This feature requires that {smart assembly} is available on this computer"My system specs are in my signature if you want them.Thanks for the help,Robert Deichert

Share this post


Link to post
Share on other sites

My flight yesterday crashed too this way. After all the crashes I had I suspect the MCDU waypoint sequencing code to hit a bug when certain conditions are met (very, very short trip, few waypoints, some degree of deviation from the lateral path etc.). I'll need to watch this further and collect some more details. Before the sim crashes, I can see the F-PLN page on the MCDU begin to flicker, waypoints are quickly sorted and re-sorted, then the crash occurs. If you ask me, something is buggy in waypoint sequencing. Unfortunately I haven't yet found a pattern how to avoid such crashes and I have to live with them until someone from the development team reviews the code...BTW, I can provoke a crash by simply constructing a traffic pattern at one airport with no further waypoint in between. The magenta line is nicely laid out, but during AUTOFLIGHT, the sim crashes 100% each time. Tried at different airports, occurs every time. Inserting one waypoint helps. But the new situation that I have now is that even with 6 waypoints, the sim crashes 100% in the vicinity of the first one. Maybe this happens only in one specific scenery area...Anyway, this shouldn't happen (and doesn't happen when flying the same route on full automatics or by hand e.g. in my Leonardo Maddog, the LDS 767 or the Fokker 100). There's hope that the MD-11 one day will see a final patch...

Share this post


Link to post
Share on other sites
Hi Guys,I was about to intercept the localizer at KTPA, and just after pressing the "NAV" button, FSX crashed with a fatal error message referencing "PMDG_MD11.dll" (in the gauges folder).Here are the error logs: "Fault bucket 1206006660, type 1Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: fsx.exeP2: 10.0.61637.0P3: 46fadb14P4: PMDG_MD11.DLLP5: 10.0.61355.62P6: 49b7c81dP7: c0000005P8: 00118301P9: P10: Attached files:C:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\fsx.CFG.txtC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\dxdiag.txtC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\scenery.cfgC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\fdr.datC:\Users\Robert Deichert\AppData\Roaming\Microsoft\FSX\dll.xmlC:\Users\Robert Deichert\AppData\Local\Temp\WER8C1C.tmp.WERInternalMetadata.xmlThese files may be available here:C:\Users\Robert Deichert\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_a4f0d2f6b2b416894fffa9eba2a3cd8b9f376a0_0840b30dAnalysis symbol: Rechecking for solution: 0Report Id: 0629da94-275c-11e0-9022-d8a25e8a8ba2Report Status: 0"And - "Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81dException code: 0xc0000005Fault offset: 0x00118301Faulting process id: 0x264Faulting application start time: 0x01cbbb4bc9bc8b98Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLLReport Id: 0629da94-275c-11e0-9022-d8a25e8a8ba2"After I got the error message, I also got this message/error: "This feature requires that {smart assembly} is available on this computer"My system specs are in my signature if you want them.Thanks for the help,Robert Deichert
Hi Robert,for me it seems that a remote NET framework application sends wrong data.first step i would take is to verify your Netframework installation. There is a helping tool for that:http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-99-90-04/netfx_5F00_setupverifier_5F00_new.zipNetframework is a programming environment which is the first time in W7 native included and called Netframework v4.0If any software or FS addon needs older versions and isn't compatible to this actual state of development, you have to verify older installed versions, too.Next step: open your program installation site in W7 and watch out if any automatism has updated your VC++ 2008 libraries both (x86 and x64), which you got with the PMDG installation. if you see any updates delete them!you can also download them here and reinstall:(x86)http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en(x64)http://www.microsoft.com/downloads/en/details.aspx?familyid=bd2a6171-e2d6-4230-b809-9a8d7548c1b6&displaylang=endisclaim of updating them in future .next step if your problems aren't solved meanwhile:make sure that your FS.exe doesn't run in compatibility mode.if this all does't help make sure to numerate your corresponding FS addons. (installed aircrafts, weatherengines, ATC tools for online flying, Flighttracker and so on.)If this would be a general problem, there would be a lot more posts like this.For myself i use: FSX@Sp2, ASE latest patched REXv2 (just the textures not the weather engine or the flight planer), FS2CREW MD-11 Edition, lots of airports all over the world, IVAP 1.98 (to connect to ivao) TOPCAT v2.70 and a latest patched W7 ultimate 64bit) and in this environment the PMDG 747 and the MD-11 works absolutely stable and i don't think PMDG sells different code to us customers.;-)hope you get your problems fixedregards

Share this post


Link to post
Share on other sites

What was the outcome ? What fixed the *gauges\pmdg_md11.dll* fsx crash ?

Share this post


Link to post
Share on other sites

×
×
  • Create New...