Sign in to follow this  
Nemo

Prepar3D. exe has stopped working - No OOM

Recommended Posts

Since some days I get P3Dv2.4 CTDs - mainly in ORBX FTX NA area. For example, at Lake Tahoe (FTX KTVL) with A2As C172 I can't fly much longer than 5 minutes then I get the message:

 

Prepar3D. exe has stopped working. A problem caused the program to stop working correctly ... CTD

 

App crash viewer says.

Prepar3D.exe - Stopped Working - Exception Code 0xc0000374 - Fault Module Version 6.3.9600.17278.

 

It is always the same Exception Code and Module version. Faul Module differs but mostly StackHash ... .

 

 

Any ideas?

 

 

Cheers,

Harry

 

Share this post


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

You would probably get a better response by posting in the AVSIM CTD Forum. What was the faulting module? Why are you not posting your complete AppCrashView crash report? If the faulting module was a StackHash, then there is no known one fix that fixes this problem for everyone. However, as indicated in the AVSIM CTD Guide, a possible solution for a StackHash is to disable MyTrafficX, 5.4c if installed as it is known to cause a StackHash if you have a bad schedule or object installed.

 

Best regards,

Share this post


Link to post

You would probably get a better response by posting in the AVSIM CTD Forum. What was the faulting module? Why are you not posting your complete AppCrashView crash report? If the faulting module was a StackHash, then there is no known one fix that fixes this problem for everyone. However, as indicated in the AVSIM CTD Guide, a possible solution for a StackHash is to disable MyTrafficX, 5.4c if installed as it is known to cause a StackHash if you have a bad schedule or object installed.

 

Best regards,

 

Jim,

 

Thank you so much. In deed, it looks like MT3D v5.4c was the culprit. I rebuilt my cfg and put in my usual settings  step by step. Everything run fine until I activated MT 54c. Again I got some heavy stutters when crossing a certain area (this Venice type village) and CTD followed short time afterwards.

 

I am just wondering why this happens in this particular area. There should not be so much traffic beeing injected from MT.  I had no problem so far with MT in other FTX regions, at least I did not suffer with CTDs (or can't remember). Are there any solutions?

 

If it is more appropriate this thread should better be moved to the CTD forum.

 

Thanks again,

Cheers,

 

Harry

Share this post


Link to post

You can't run MyT Pro 5.4c with the 2013 schedule. It has a known bug. Try the 2012 schedule.

Share this post


Link to post

You can't run MyT Pro 5.4c with the 2013 schedule. It has a known bug. Try the 2012 schedule.

 

From where can I get the 2012 schedule. MT configurator currently does not not run in P3Dv2/Win81.

 

Harry

Share this post


Link to post

From where can I get the 2012 schedule. MT configurator currently does not not run in P3Dv2/Win81. 

Harry

You do not need to download and install any of the schedules on his website. In fact, IMHO you get more AI traffic if you do not. The program has a schedule installed during installation and it works great with plenty of AI. If you are an expert aircraft spotter or want total perfection, then you might want to update to the 2013 schedule to have the latest but doubt most will see any difference. When MTX5.4c was released, I got the 2013 schedule as I wanted to have the most up-to-date stuff but it is just an option. Not mandatory and it is believed to be the cause of many StackHash/NTDLL.dll CTD's. I reinstalled MTX to 5.4b and will not upgrade again until maybe the next update or an update for P3DV2.

 

Best regards,

Share this post


Link to post

From where can I get the 2012 schedule. MT configurator currently does not not run in P3Dv2/Win81.

 

 

 

Click this file in your P3d 2.4 installation and it will install the 2012 schedule for you.

 

C:\Program Files (x86)\Lockheed Martin\Prepar3d v2\MyTraffic\Traffic2012.bat

 

In your MyTraffic folder you will see the other schedule years as BAT files and you can install any of them manually also.

 

Burkhard (the author of MyT Pro) is working on MyT Pro 6.0 which will be fully compatible with P3d 2.4.

Share this post


Link to post

OK. Problem solved. MT 54c with 2013 flightplan was the culprit. Changing the flightplan to 2012 as suggested from "jabloomf1230" and "firehawk" brought the solution.  I still get some stutters at exactly the same position (see my posts above) but P3Dv24 keeps now alive - no CTD anymore.

 

Thank you!

 

Harry

Share this post


Link to post

 

 


You can't run MyT Pro 5.4c with the 2013 schedule. It has a known bug. Try the 2012 schedule.

 

Oh my gosh, thank you so much! I've been looking all over the MyT support forums and was getting really frustrated with repetitive CTDs as I was already feeling hoodwinked by their product page that doesn't clearly state that it natively supports v1 which I of course figured out only AFTER buying it, then I find out that MyT6 will be released soon so I'm pretty sure that's going to be another $50. Well at least I know have a solution for this misleading software. With all the different versions of MyT out there it was confusing to begin with, then I finally figure out the 5.4c is the most recent and it says for Prepar3D on the product page and only if you scroll down past distracting ads and dropdowns does it say v1.4. 

Share this post


Link to post

Other than the well documented bug in the 2013 schedule, MyT Pro 5.4 works fine with P3d 2.4. The installer is designed only for P3d 1.4 and this also is clearly stated.

 

You should consider that no AI traffic add-on officially supports P3d 2.4 and some like UT 2 are barely supported at all.

 

At least Burkhard, the MyT developer, has promised a version for P3d 2.x. He's even released the airport upgrade package from the upcoming release.

Share this post


Link to post

At least Burkhard, the MyT developer, has promised a version for P3d 2.x. He's even released the airport upgrade package from the upcoming release

Agree. He has been working to find the right combination for P3D 2.x and it looks like he's getting close.

 

Vic

Share this post


Link to post

 

 


The installer is designed only for P3d 1.4 and this also is clearly stated.

 

Not sure where you bought it but it is not clearly stated over at simMarket, I will admit I should have read all the way down the page in the detailed dropdown box, but the fact that it says "for Prepar3D" in the title is a little misleading/ambiguous regardless of my oversight, it should say "for Prepar3D v1" that said I love Burkhard's product and am happy to support it despite feeling a little butthurt about the way simMarket presented the product. Honestly, most of the sim online stores feel a little 2nd rate like you're going to find your credit card has been used for Ray Bans in Zimbabwe two days later. 

Share this post


Link to post

Yeah, well, for some reason, AI Traffic doesn't seem to be a big attraction in P3d. It seems like most people who are using an AI traffic add-on are either fooling with either My Traffic Pro 5.4  or Ultimate Traffic 2, both of which do work if one is persistent enough. The good news is that it's very likely that MyT Pro 6 will be cheaper as an upgrade from version 5. Don't yell at me if it's not, though.  ;)

Share this post


Link to post

So I've been testing after the switch to 2012 traffic and I still got a "Prepar3D.exe has Stopped working" I'm going to uninstall MyT and see if I keep getting the same thing, now I'm getting frustrated.


Same behavior as described by OP, stutters then stops then just crashes

Share this post


Link to post

The schedule change only addresses the ntdll.dll error in P3d. You might want to check your Windows error event log to see what specific error that you are getting.

Share this post


Link to post

The best thing to do is to reinstall MyTrafficX 5.4b or c and do NOT go on the developers website and install the 2012 or 2013 AI schedule. Use the default that comes with MyTrafficX which is absolutely awesome and provides even more AI traffic. Once installed in FSX, copy the MyTrafficX folder to P3DV2, make the change in the P3D.cfg, and add the scenery to your Scenery Library and put it just above Propeller Objects. Go Fly.

 

I reinstalled mine to 5.4b and have not had any problems whatsoever with CTD's since then (about 8 months ago).

 

Best regards,

Share this post


Link to post

 

 


The schedule change only addresses the ntdll.dll error in P3d. You might want to check your Windows error event log to see what specific error that you are getting.

 

Good idea JaBoomBoom I will check my error log and see what the culprit was

 

 

 

 


Once installed in FSX, copy the MyTrafficX folder to P3DV2, make the change in the P3D.cfg, and add the scenery to your Scenery Library and put it just above Propeller Objects. Go Fly.

 

Unfortunately I have MyTraffic3D so I'm not sure if that solution will work but I do have FSX still installed so I'll give it a go, thanks for the tip! 


Here's what I'm getting out of the event log, it's all greek to me
 
Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xd46cef65
Faulting process id: 0x176c
Faulting application start time: 0x01d02ba275b50ecd
Faulting application path: F:\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: unknown
Report Id: d5047c77-979e-11e4-8e71-e0cb4ef9260d
 
Fault bucket 144596503, type 19
Event Name: BEX
Response: Not available
Cab Id: 0
 
Problem signature:
P1: Prepar3D.exe
P2: 2.4.11570.0
P3: 542314d3
P4: unknown
P5: 0.0.0.0
P6: 00000000
P7: d46cef65
P8: c0000005
P9: 00000008
P10: 
 
Attached files:
C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.cfg.txt
C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\dxdiag.txt
C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\scenery.cfg
C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\fdr.dat
C:\Users\Paul Cordogan\AppData\Roaming\Lockheed Martin\Prepar3D v2\DLL.XML
C:\Users\Paul Cordogan\AppData\Local\Temp\WER55CE.tmp.WERInternalMetadata.xml
 
These files may be available here:
C:\Users\Paul Cordogan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_126e3d69f0b07a16ff11188b5259669c73a2_08827649
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: d5047c77-979e-11e4-8e71-e0cb4ef9260d
Report Status: 0

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