General Category > General Discussion
P3D v3.3.5 CTDs (ntdll) after KDFW install
kikigey89:
Hey guys,
In preparation for Cross the Pond on VATSIM I bought KDFW, installed it and first everything was working flawlessly.
Yesterday I started some long haul tests, just to be sure I won't expect some weird issues during CTP.
After a few hours of flight I experienced a CTD with a problem in ntdll.dll. I restarted the sim and tried again. Again a CTD after some time.
I did a lot of testing (closing apps, deactivating modules in P3D) and found out that if I delete the couatl entry from exe.xml I do not get CTDs. If I include that entry. the CTDs reappear.
I already reinstalled Addon Manager (standalone), Couatl (via Live Update) and reinstalled GSX - No success :(
Do you have any ideas?
Best regards,
Chris
virtuali:
Couatl.exe, by itself, cannot cause a crash in the sim, since it's an external executable so, by definition, it doesn't have any chance to affect the simulator.
However, there's a longstanding issue in P3D, which has been reported many times to LM, that P3D is "leaking" Simconnect exceptions caused by OTHER addons, into other addons that don't have anything to do with the original exception error.
See a description here, coming from SODE's author who experienced the same issue: another module caused errors, and they were leaking into SODE, so it looked like SODE was the cause, but it wasn't:
http://www.fsdreamteam.com/forum/index.php/topic,13668.msg105608.html#msg105608
So, it's possible that, after a long flight, all these exceptions might eventually cause an OOM, which is usually what a crash in ntdll.dll means.
Could you try ANOTHER test ? Disable ALL other 3rd party modules *except* the FSDT ones in the DLL/EXE XML files ?
kikigey89:
--- Quote from: virtuali on October 13, 2016, 02:13:39 pm ---Could you try ANOTHER test ? Disable ALL other 3rd party modules *except* the FSDT ones in the DLL/EXE XML files ?
--- End quote ---
I did, still the same :( Only bglmanx.dll in dll.xml and couatl.exe in exe.xml.
What I forgot to say: FSUIPC automatically saves a scenario every 5 minutes. I'm currently always testing with the last scenario it saved this morning before the CTD. It is completely reproducible.
So usually I get a CTD with that scenario within 5 minutes.
virtuali:
--- Quote from: kikigey89 on October 13, 2016, 03:01:14 pm ---I did, still the same :( Only bglmanx.dll in dll.xml and couatl.exe in exe.xml.
--- End quote ---
P3D V3 has two set of XML files: some addons use the ones in %APPDATA%, other use the ones in %PROGRAMDATA%. Be sure you disable everything else (except our modules) from BOTH locations.
--- Quote ---What I forgot to say: FSUIPC automatically saves a scenario every 5 minutes. I'm currently always testing with the last scenario it saved this morning before the CTD. It is completely reproducible. So usually I get a CTD with that scenario within 5 minutes.
--- End quote ---
You should disable everything for the test, which includes FSUIPC.
kikigey89:
--- Quote from: virtuali on October 13, 2016, 03:23:21 pm ---P3D V3 has two set of XML files: some addons use the ones in %APPDATA%, other use the ones in %PROGRAMDATA%. Be sure you disable everything else (except our modules) from BOTH locations.
You should disable everything for the test, which includes FSUIPC.
--- End quote ---
Good point, I forgot of the other set. Now FSUIPC is also disabled but still the same, still CTD.
Navigation
[0] Message Index
[#] Next page
Go to full version