Sign in to follow this  
Chatefucio

v3.4 SimConnectP3D3.dll crash to desktop

Recommended Posts

Hi there,

 

well after fresh install of p3d.3.4 and all addons, there is time for testing. 3 tests without problem (average 7h duration, on PMDG738), then tongiht, 4th trial and baam - CTD. Checked the error log and that's what was there:

 

Faulting application name: Prepar3D.exe, version: 3.4.9.18400, time stamp: 0x57d9b14e
Faulting module name: SimConnectP3D3.dll_unloaded, version: 0.0.0.0, time stamp: 0x571e4e28
Exception code: 0xc0000005
Fault offset: 0x13d41eb0
Faulting process id: 0x21e4
Faulting application start time: 0x01d22fd9dc19f48f
Faulting application path: E:\Program Files\Lockheed Martin\Prepar3D.exe
Faulting module path: SimConnectP3D3.dll
Report Id: 117c0380-9c01-11e6-9f34-74d435e2a771
 
Now, what could cause that? I've the latest FSUIPC and fresh installs of next addons/programs:
AS16+softclouds, ORBX base+vector, ezdok, accufeel, rwy bumping effect, fscaptain, ivap and acars. The error occured after 7 hours of flight with PMDG738 on holding above LEPA (added aerosoft's airport). 
 
So, what to do?
 
Thanks for help..

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

The error occured after 7 hours of flight with PMDG738 on holding above LEPA (added aerosoft's airport).

 

How much VAS was available at or just before time of crash?

 

I downloaded the Avsim CTD Guide and used all the applications linked there.

 

http://www.avsim.com/files/file/65-avsim-crash-to-desktop-guide-for-fsx-fsx-se-and-p3d/

 

Appcrashview is excellent and provides more info, but you need task manager/FSUIPC/System Monitor open during the flights to see what's being run and how much VAS is available. You may see a flight sim application using more memory and perhaps spiking too high so the P3d memory smoothing control is unable to handle it?

 

Also one CTD out of four? I would check again with the monitors open.

 

Regards

 

David

Share this post


Link to post

 

 


Appcrashview is excellent and provides more info, but you need task manager/FSUIPC/System Monitor open during the flights to see what's being run and how much VAS is available. You may see a flight sim application using more memory and perhaps spiking too high so the P3d memory smoothing control is unable to handle it?

 

The OP's report provides sufficient information.  Looks like an Event Viewer report which is okay.  Not much more information can be gleaned with AppCrashView but you are correct, it does provide more information (but not necessarily with this crash).  I agree, one CTD after 4- 7 hour flights does not not mean much.  Using the process monitor to see what was loading at the time of the crash will not help in this case as his flights are 7 hours and running Process Monitor for just an hour would take over 8GB's of HDD space depending on what all was running.  But, if the crash is occurring exactly at 7 hours (in more than one crash), then maybe pausing P3D about 6 hours out and running Process Monitor would provide a clue.

 

 

 


So, what to do?

 

Most likely, after running P3D for over 7 hours, P3D was running low on VAS and getting ready to crash and the simconnect module was unloaded and, when it is unloaded, other apps (addons) cannot run.  Setting up P3D to monitor VAS using the FSUIPC.dll as explained in the AVSIM CTD Guide would let one know whether or not VAS was running low.  Anyone can bring P3D down to its knees where it cries uncle.  Move up the sliders to max or very high, run PMDG aircraft, along with AS16 weather, FTX/Orbx payware, with EZDOK (which is not compatible with P3D), FS Captain, IVAP, and ACARS and you have a recipe for total disaster.  Please do not expect P3D to run efficiently with all of those addons/high settings.  P3D was not developed to run addons with high P3D/Display Driver settings for any long period of time.  P3D runs great with high settings using default aircraft and scenery.  Throw in the addons and it is a crapshoot.... (or a roll of the dice).

 

Best regards,

Jim

Share this post


Link to post

Setting up P3D to monitor VAS using the FSUIPC.dll as explained in the AVSIM CTD Guide would let one know whether or not VAS was running low.

 

 

That's what I would do. My bets on VAS limit.

 

That CTD Guide is absolutely superb, a mine of information that's easy to understand, cant thank you guys enough.

 

Regards

 

David

Share this post


Link to post

 

 


That CTD Guide is absolutely superb, a mine of information that's easy to understand, cant thank you guys enough.

 

Thanks David for the kind words.

 

Best regards,

Jim

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this