But your comments that you had trouble getting the FSPassenger module to be trusted might be the issue. It could lead to a total corruption of the dll.xml and we do not know for sure it was FS Passengers that caused the problem (I have not heard about problems with the latest version). You will not be able to use any of the programs that were supposed to be loaded via the dll.xml but it will tell you whether there is a problem with one of the modules in the dll.xml.ĭo not try to delete the entry in the dll.xml and install FS Passengers again unless you know everything in the entry that has to be deleted. Again, my recommendation to move the whole dll.xml to a temporary folder and then restarting FSX-SE and see if this fixes the problem. You'll have to continue your investigation. If the crashes continue after disabling FS Passenger, then that program is not the problem. If the crashes stop, then you should reinstall FS Passengers and make sure you install it with Admin Rights. This is good for testing to see if this fixed the problem.

When it state true, the module will not load at startup and you will not be able to use FS Passengers.

When it states false, the module is not disabled. Should i dis.INstall FS passngers delete the entry in DLL:XML and install it again? to disable that line i should only put Flase instead of TRUE and only that line? I had a problem when i installed FSpassengers that when launching fsx-Se the prgramm asked me toacceft the dll when iclicked on it FSX-Se crashed and when i launched it again it didnt ask me to accept any DLL anymore. Fspassengers 2015 is uptodate to latest version of september 2015. Best to bring your BIOS back to the optimal default. The cpu voltages may be too high or too low. The ntdll.dll is a system dll and I have seen it crashing if the system is overclocked. It might have been fixed in the latest version. If this is the old version, it has caused a lot of issues for our members. My recommendation is to try to disable FSPassengers as I have indicated in red above. If it does fix the problem, then you would have to disable each and then enable them one by one until the culprit is found.

It will not be rebuilt but is not needed to run fsx-se. The best way to find out if your dll.xml is working or not is to move the dll.xml to a temporary directory or rename it to dll.orig.

Fspassengers x dll.xml