General Category > General Discussion
P3D v3.3.5 CTDs (ntdll) after KDFW install
kikigey89:
I attached my save file, I just climb to 37000 ft, heading 300 and speed 270. Should occur within 5 minutes, if nothing happens after 10-15 minutes then you do not have that issue.
I'm not sure, but I had the feeling yesterday that it appears when coming closer to the coast. The first time it happened south of Greenland and the second time 93 NM off the coast of Newfoundland.
kikigey89:
Just a quick update as my tests continue: I deactivated my RAM disk and now it seems to be stable. Couatl is usually also on the RAM disk (the entire fsdreamteam folder) and maybe some part of the RAM is corrupted. As I installed KDFW my FSDT folder size increased which may forced Couatl to be written in a corrupted section.
kikigey89:
Ok, I did a lot more tests. Memtest (6 passes) could not find any RAM problem.
Now I reactivated everything in exe.xml and dll.xml and the only thing which is different now, is that Couatl is NOT running on the RAM disk anymore. However all my FSDT sceneries are on the RAM disk. No problem anymore.
Do you have an idea what's wrong? I had Couatl on the RAM disk for 2 years now, without any issue. However after KDFW install it doesn't like the RAM disk anymore.
virtuali:
--- Quote from: kikigey89 on October 16, 2016, 11:00:37 pm ---Do you have an idea what's wrong? I had Couatl on the RAM disk for 2 years now, without any issue. However after KDFW install it doesn't like the RAM disk anymore
--- End quote ---
No idea but, it's clear from your tests the RAM disk configuration was a problem, and now you removed it, the problems went away
KDFW installation cannot have anything to do with this, since they just install the scenery and don't make any change to your system configuration, let alone something that might affect a RAM disk ( like a driver, for example ) so, fact you noticed it only after installing it, was only a coincidence.
In any case, using a RAM disk for Couatl doesn't make much sense, since the only thing that you might gain would be a slight decrease in loading time, but once it's in memory, it will be the same, since it's not a disk-intensive program. Its files are also very small, you can probably fit the whole GSX code in less space than a single 1024x1024 scenery texture...
Couatl it's a Python interpreter and, all the Python files that makes up for a program like GSX or the script that handles the scenery, for example, or the scripts that generates the scenery, are first loaded in memory, and then executed from there. A proof for this, is that you can even *remove* a program file, and the program will still continue to work, until you restart it. If the program execution at run time was in some way dependent on the filesystem it's stored on, you wouldn't be able to remove it so easily, and you would see an "access denied" error, like when you try to remove an active .BGL while the sim is running.
So, by running it from a RAM disk, you don't really gain anything, perhaps a *slightly* faster loading time (but it won't be probably noticeable compared to a fast M2 drive), but no actual performance gains.
kikigey89:
The only reason why Couatl was on the RAM disk was that it was much easier just writing one line of batch script, copying just the entire FSDT folder instead of each single scenery :-)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version