January 31, 201412 yr Author Hi Jim Clicking dll.xml brings up an explorer page, showing four (4) 'addons' sections. Three (3) are "true", with the last one "false". When I highlight "false", it does not allow me to change it to "true" in this explorer page. How else can I display dll.xml so that I can make the change required? I do not have MyTrafficX 5.4c installed, but I have just downloaded AppCrashView and now need to see how to use it. Ray Raymond Smyth
January 31, 201412 yr Author Sorry - have opened dll.xml in word pad and now I have chaned false to true . Will see how that goes. No - problem still there after ensuring all four (4) modules in dll.xml are set to 'true'. Event Viewer does not show this error. Where do I go from here? Thanks. Ray Raymond Smyth
January 31, 201412 yr Event Viewer does not show this error. Where do I go from here? In Post #13 you said the Event Viewer said the faulting module was ntdll.dll. This is a system module. It belongs to Windows and not to FSX. When it crashes it indicates you have a problem with computer memory. It is most likely corrupted. There is no fix that will make this problem go away for everyone. This is why you must investigate and try to find what is causing this memory corruption. Some people have fixed this problem by reinstalling Windows and then FSX. Some have fixed it by getting rid of all of the tweaks in their Fsx.cfg as these tweaks are "tweaking" memory components belonging to your computer system and FSX just does not like them. This is why a rebuild of the Fsx.cfg usually works for many but definitely not for all. You should reenable those modules in the dll.xml as your problem continues. Did you disable all of your addon scenery in the Scenery Library, run FSX and see if the problem persists? A bad texture in a scenery program could be causing your system to shut down FSX as it cannot render the texture properly. There are many actions you can take to troubleshoot a crash. The AVSIM CTD Guide as a specific section entitled "Actions to take after a crash is encountered". These are suggestions/recommendations taken from throughout the Flight Sim community. Hope this fixes the problem. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
February 1, 201412 yr Author Hi Jim, I have disabled all addon scenery in the scenery library and still get a "freeze", both with addon and default aircraft after about 10 minutes flight. All recent "freezes" do not show up in the Event Viewer or AppCrashView reports. I have not seen the "ntdll.dll" appearing during recent freezes. I've changed the "true" back to "false" in the dll.xml single module that originally was "false". The AVSIM CTD Guide, under "Freezing During Flight" suggests two things: "High FSX//display driver settings" and "Rebuild FSX.cfg". Are display "driver" settings, just the simulator display settings? I have adjusted these. How might I re-build FSX.cfg? Thanks again. Ray Raymond Smyth
February 1, 201412 yr Are display "driver" settings, just the simulator display settings? I have adjusted these. How might I re-build FSX.cfg? Display driver settings are not FSX display settings. These are the settings for your video card. Usually you right click your desktop and select your video cards control panel. If they are set at the default, they are okay. To rebuild the fsx.cfg, you rename or delete the fsx.cfg, restart fsx, and the config will be rebuilt. The fsx.cfg is in the same folder as the dll.xml. Just make sure you delete the config as there will also be a fsx.txt file there too that looks exactly like your config but it is not. Actually you can delete them both (fsx.txt and fsx.cfg). The fsx.txt document was put there back in the old days whenever you had a crash. The FSX developers were hoping this txt file could be sent to them and they could use it to find out what caused your crash. However, they no longer exist so that will never happen. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment