March 3, 201016 yr Hi folks,I bought my copie of PMGD's MD11X this week and installed it without error messages.But when I select this aircraft it causes a fatal error.Selecting a other aircraft works fine.I'm using FSX, Windows7 (64bit) on a AMD quad-core with 4GB RAM, ATI HD5750 (1GB).Does anyone have a idea what might be the cause of my problem?Thank you,Erwin de Vries
March 3, 201016 yr No idea Erwin, Have you checked the windows event logs to see what errors may be listed in application? If all your doing is selecting the aircraft and getting the crash the only thing that comes to mind is a corrupt install or untrusted dll.After you installed it did you get the prompt for the C++ runtime libraries to install? Did you also get the prompt to allow a few .dll's to run after trying to run it the first time? i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2 2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro Dan Prunier
March 3, 201016 yr Hi Dan,Thanks for responding.I'm not familiar with this event log your mentioning, so I have to do some surging.According to the installed programs list there are two C++ libraries installed with the same installation date.And when starting-up FSX I had to approve two (maybe three) times the use of a PMDG related item.I've also tried to copie the content of the DDL folder to the modules folder of FSX, but that didn't do the trick.Deactivating MYTRAFFIC didn't made a differance as well.What I did notice is that when selecting a other aircraft the add-on menu didn't show any of the PMDG options.Can that be a indication?Greetings,Erwin
March 3, 201016 yr Heya Erwin, What I mean is the installer should still prompt for installing these C++ runtimes even if you have it installed, so do you remember if it did?I wouldn't copy or move any contents around though. If you are running a PMDG aircraft then you should see the PMDG options in the file menu. If you're not, then it is most likely a trust issue or a write issue possibly too.If you installed your FSX installation to the default Program Files (x86) directory then maybe it's some kind of write issue, although I doubt it. You could try and run the installer as administrator by right clicking it and selecting "Run as administrator". You might also want to try and run FSX that way too. I think this may be going away from the actualy problem though.You mentioned that when your select the MD-11 aircraft it causes a fatal error so the first place we need to look is the event viewer. Follow these steps since your using windows 7.Click the windows button and in the "Search Programs and files" box at the bottom, type in event.You should see "Event Viewer" in the top "Programs" category; click it.On the left side of the window that opens click the > symbol to expand the branch for "Windows Logs", and then highlight "Application".Look here for errors after you get a crash. Sometimes there is useful information here, but then again, sometimes there may not be. i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2 2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro Dan Prunier
March 3, 201016 yr Hi Dan,I've had a peek in the event viewer and it showed a number of faults.The attached screenshot shows a faulty application path, apperently PMDG has a problem with that.But I can't tell what the other lines are telling me, are they a side effect of the wrong path or is there more?The other attached screenshot shows a number of C++ installation, the two marked came with this MD11 installation.I assume no problem there. although I'm starting to wonder why the already installed version couldn't do the trick. Sorry, just a thought popping up. http://forums1.avsim.net/style_emoticons/default/blush.gifBefore I start moving FSX to the "program files (x86)" I'll need to know if the event log shows more wrongs than I can make out.Hopefully you can.
March 3, 201016 yr Hold on, the most common reason is the fsx dll.xml file, when you crash first time after loading a pmdg aircraft in FSX. Search the pmdg kb for dll.xml and you will get this: http://support.precisionmanuals.com/Main/f....xml&type=0Hope it helps. Dan Downs KCRP
March 3, 201016 yr Check out the link Dan mentioned, but I didn't say to move FSX to Program Files (x86). I advise the oposite most of the time, haha. In fact just minutes ago, ole Microsoft deleted one of my posts in a microsoft thread on how pathetic they are about the Pin to task bar method they chose to use, they really are a bunch of clueless people... i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2 2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro Dan Prunier
March 3, 201016 yr Dan & Dan,Unfortunally repairing the DLL.XML didn't made a difference.The only thing changed here is that I got rid of the remains of the "Microsoft Flight Simulator X SDK" installation.So no harm done.Curently my XML-file looks as followed after reinstalling the MD-11 model.+++++++++++++++<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon></SimBase.Document>++++++++++++++During the installatie a got two messages stating that C++ redistrubutables where required, a 64 bit and a 32 bit version.These were removed earlier .After a reboot I started up FSX, no messeges here, I assumed because PMDG is already marked as trusted software. After selecting a few models (including a freeware model) I selected the MD-11 and FATAL ERROR. (breath in, breath out, breath in)I've attached a new screenshot of the event.log but other then the timestamp I see no change.I'm open for suggestions?Erwin de Vries
March 3, 201016 yr The faulting module in the event logs ntdll.dll doesn't really pin point anything unforunately. I did a good read at : http://support.microsoft.com/kb/303032and didn't find anything really except reference to SP2.You mentioned "During the installatie a got two messages stating that C++ redistrubutables where required, a 64 bit and a 32 bit version.These were removed earlier". Why were they "removed" earlier? They should be left as is, they are only a couple of dll's and don't worry about duplicate names.Personally, I would start with what we have then go deeper per reinstall. The next thing(s) I would try is to rename your fsx.cfg file to see if the problem remains. It will build a new file so you will have to reset all your display settings but more importantly, it will relaunch all the trusted windows for you to approve. Be sure to say yes, of course.The next thing I would try, is to uninstall and reinstall SP2. I have read a lot lately how this has fixed lots of strange problems, but up to this point there still really isn't much to go on.All we can do is process of elimination.Edit: Stupid question here, but you haven't tried relocating your FSX install,,, have you? i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2 2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro Dan Prunier
March 4, 201016 yr Removing the redistrubutables was done by me to check the messages during installation and to reinstall from scratch.I'll take it it's got nothing to do with this problem?About the FSX location, it's unchanged.To be honest I'm not that eager to move FSX to the c:-drive because that requires a extention of this drive.I've dedecated the D:-drive to everything related to flightsimming, moving FSX (and everthing else) to C: would make D: redundant.I'll start with renaming the fsx.cfg file this evening and see where that brings us.One more thing!There is no such thing as a stupid question! I'll keep you informed!
March 4, 201016 yr THE MODEL IS WORKING!!This evening I started with renaming the fsx.cfg.After selecting the MD-11 I got two messages asking for approval, which were "PMDG_MD11.DLL" and "PMDG_MD11_ACS.DLL".After that, a fatal error.Checked the gauge folder and notice no more than two PMDG-gauges, no problem there I would say.Next:Uninstalled PMDG MD11 and reinstalled by using the option "run as administrator".Long story short: reboot, run FSX, select MD-11, pressed OK, FATAL ERROR.I can see the model making 360's when I select "Details".I'm also able to move it (vertical axe and pitch).I saw the ntdll.dll being one of the faults in the event viewer so I checked it in C:\Windows\SysWOW64\ntdll.dll, it was there.Started up FSX setup.exe as administrator and selected the "repair" option.Reboot. and started up FSX and Immediately a FATAL ERROR AAAARRRGGG.At that point I thought "enough is enough", I just want to fly, no metter what.Uninstalled all flightsim software, extended the C: drive with 70GB.And started reinstalling FSX, but this time in the default folder.While that was running I got a brainwave and realized what I did wrong.I repaired FSX while SP2 was still installed, ......... fool that I am......... to late now.After FSX was installed, a reboot, and FSX was working.Next SP1, SP2, PMDG's MD-11 + 3 liveries, a reboot.Starting op FSX folowed by mesages for 3 PMDG.dll files (options, events, sounds.)so far no problem.Selecting the aircraft, accepted PMDG_MD11.DDL and there it is, something I haven't seen earlier.For about 1 second a pop-up, installing something I think, next PMDG_MD11_ACS.DLL.And there it was on the ramp, the magnificent MD11.Next thing to do is reading the operational manualDan,I still don't know what made the difference, the folder, reinstalation the lot, I really do not have a clue.Do you ?I put my money on this one second pop-up, but what did it do?
March 4, 201016 yr Glad you got it working Erwin, unfortunately I can't really say which was the problem. The only other thing I can think of was something wrong with the hard drive and was going to recommend a scan disk of your D:\ (I was also going to ask if it was an actual drive or just a partition based on a couple things you mentioned).I look forward to trouble shooting FS issues like I look forward to a root canal, but once I get going I hate to have to take steps that don't allow me to see exactly where the issue was. This sometimes can't be helped though and a complete reinstall ends up happening, thus I loose all of my invested investigation :'(At least your up and running. Hope it's smooth sailing ahead for you now. i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2 2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro Dan Prunier
March 5, 201016 yr Dan, In my line of work the very first issue reported of some sort rarely leads to the cause of it.In every report there is always a detail left out which in a later stage turned out to be the key.Anyway, I thank you for your time invested to solve this and I'm sorry that I became impatient.Erwin de Vries.
May 20, 201016 yr This exact same problem is happening to me! I just bought a brand new PC with windows7 64bit. Both my pmdg 747 and md-11 fail to load in FSX. I get an error message that the dlls can't be found. I've reinstalled as administrator to no avail. I'm stumped.
Create an account or sign in to comment