Sign in to follow this  
citroene

Prepar3D 3.3.5 Crash

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

I read your thread.

 

Can you provide more information.

 

You seem to be running a lot addons... I'd start by turning your sliders a bit to the left.  You might be pushing your system past the breaking point.

Share this post


Link to post
Share on other sites

all the sliders are in the middle or to the left. my proccesor use is around 85/90% and my graphics card around 40/50%

FPS lock @ 25 with Vsync on

 

I also use the FS2CREW 737 reboot Edition and I have no problem with that.

 

Kind regards

Share this post


Link to post
Share on other sites

I'm sorry, it's hard to guess.  We have 1000s of 777 users.  Crash reports are extremely rare.

 

The 737 Reboot and 777 share the same system, so your results should be identical.

 

What does the error report say?

 

You can use Event Viewer to get more info.

 

Also, try flying between default airports as a test.

 

Cheers,

Share this post


Link to post
Share on other sites
Foutbucket 933228502, type 25
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: Prepar3D.exe
P2: 3.3.5.17625
P3: 5758bb31
P4: ntdll.dll
P5: 6.1.7601.23418
P6: 5708a73e
P7: c0000005
P8: 00032751
P9:
P10:

Bijgevoegde bestanden:
C:\Users\Olivier\AppData\Local\Temp\WER4A90.tmp.WERInternalMetadata.xml

Deze bestanden zijn mogelijk hier beschikbaar:
C:\Users\Olivier\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_dfb94ff02d16e88d74748d1cb7b64a82b6bd4110_13c1ecc9

Analysesymbool:
Opnieuw zoeken naar oplossing: 0nRapport-id: 1e7bea14-53b0-11e6-80b6-d05099267141
Rapportstatus: 0

This is what i get from the event viewer

 

I did last night a testflight without FS2crew and no crash

Yesterday 2 times the same flight with FS2CREW and both crashes.

Share this post


Link to post
Share on other sites

I have the same issue, Bryan. It all started after the most recent FS2C update for the 777. Prior to the update I had zero issues.

 

Todd

Share this post


Link to post
Share on other sites

Google "P3D ntdll.dll" and try everything you can find.

 

I'm afraid I can't fix what I can't reproduce.

Share this post


Link to post
Share on other sites

Strange thread. I've runned into a ntdll.dll error early this week using P3D 3.3.5 and the T7, 15 minutes after take off a freeware scenery airport (LFST for instance, which is rock stable).

That was the first time in maybe 15 years using FS-based simulators that I encountered this particular ntdll CTD.

 

And I am not a FS2CREW user at all so I guess they're not to blame here.

 

Isn't some underlying recent Windows-update stuff here kicking in ?

Share this post


Link to post
Share on other sites

 

 


And I am not a FS2CREW user at all so I guess they're not to blame here.
 
Isn't some underlying recent Windows-update stuff here kicking in ?

 

Sometimes it's a just big who knows, since everyone's system is different.

 

But if it was a Windows update, I would expect to be hearing from very large numbers of users all reporting the same thing.

Share this post


Link to post
Share on other sites

I didn't instal windows updates in the last 2 weeks

 

I did today four short flights

 

2 with FS2CREW and 2 Without

 

The 2 flights with FS2CREW my Prepar3D crashes, the 2 other flights I was able to finish.

Share this post


Link to post
Share on other sites

Hi Olivier,

 

Can you locate a reproducible trigger.

 

If I can reproduce it, I can fix it.

 

Cheers,

Share this post


Link to post
Share on other sites

I unfortunately can not :(, the errors are completely random. Sometimes I get an error when I try to do the approach briefing or somthing else, and other times I just get an error if I do nothing and see how everything goes.

Share this post


Link to post
Share on other sites

I unfortunately can not :sad:, the errors are completely random. Sometimes I get an error when I try to do the approach briefing or somthing else, and other times I just get an error if I do nothing and see how everything goes.

 

As a test, try moving your sliders more to the left, just to see if that helps, especially the LOD slider.

Share this post


Link to post
Share on other sites

Try making a flight in Africa to be away from any 3rd party scenery, AI, etc.

 

It's a process of elimination.

 

 

Cheers,

Share this post


Link to post
Share on other sites

Apologies for my late response

I did yesterday a flight
without any add-on scenery from  EHAM Schiphol to FACT Cape Town

 

And still crash :(

Share this post


Link to post
Share on other sites

Bryan,

 

Sorry, I didn't bail on this thread. I just moved and we are still unpacking. I still need to set up my computer. I'll try a flight once I get it set up and see if I get another crash. For me, it's just strange it all happened after the latest update. Before that, zero issues.

 

Thinks for the link in your most recent post. I'll need to investigate that one further.

 

Todd

Share this post


Link to post
Share on other sites

Todd, I think you may have double entries in your DLL.XML and/or EXE.XML. Check programdata/lockheed Martin/P3Dv3 folder and %APP%/user/roaming/LM/P3Dv3

If using ASN, make sure it is the last entry, and FSUIPC should also be last entry. Compare both xmls in both folders.

This is the most common fix for ntdll errors in P3D. And they are random.

Share this post


Link to post
Share on other sites

Todd, I think you may have double entries in your DLL.XML and/or EXE.DLL. Check programdata/lockheed Martin/P3Dv3 folder and %APP%/user/roaming/LM/P3Dv3

If using ASN, make sure it is the last entry, and FSUIPC should also be last entry. Compare both xmls in both folders.

This is the most common fix for ntdll errors in P3D. And they are random.

 

 

Thanks for sharing that.

 

In the good old days before FSX we could just drop DLLs in the module folder.  Easy peasy.

 

And then they came up with the DLL.xml idea, and a million FS developer voices cried out in terror...

Share this post


Link to post
Share on other sites

Thanks for sharing that.

 

In the good old days before FSX we could just drop DLLs in the module folder.  Easy peasy.

 

And then they came up with the DLL.xml idea, and a million FS developer voices cried out in terror...

Yes Bryan, things were so much easier. Now when I install a new addon, I have to check the integrity of the xml files to ensure everything is in correct order, and no double entries, in two different locations.

 

I got caught out on this one, was having random ntdll errors, and after checking the xml's found double entries, as some older software gets confused, and so does P3D :)

Share this post


Link to post
Share on other sites

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