18-02-2017, 12:35 PM
(18-02-2017, 01:31 AM)Joeflyer Wrote: Teo, thanks for the informationYou didn't mention anything about your P3D settings. Are they still on default or do you have most sliders to the right of default? Also, are all of your hardware drivers up to date? When people have the ntdll.dll errors, it's usually driver related. Overclocking the CPU can certainly create the error as well but you have squashed that possibility.
At this point I can't really point to FsP as the problem...even though some of your flights it would appear to be the problem. I mention this because FsP doesn't create much "overhead" at all in terms of graphics, VAS usage,etc. There is usually one underlying issue that hasn't been uncovered until it is uncovered...via methodical steps to get there. Let me ask this. Are you using the mini display throughout the flight until the sim crashes?
Hi Joe,
All drivers up to date and it has happened with previous versions of FSP as well on Prepar3d. Also happens with the PMDG 737 after 6-7 hours.
Prepar3d sliders are almost all to max, except Level of detail, cloud distance, autogen which is set in the middle, etc. As I mentioned the VAS indicator from the projectFLY pilot tools show 71% VAS usage at the time of the crash.
Minidisplay is closed usually. I open it and close it throughout the flight so it's not necesarily showing on the screen at the time of the crash.
Regards,
Teo
Teo