# Prepar3d V4 Crash

## Recommended Posts

Experienced the second crash so far with Prepar3d V4 (admittedly, after several weeks of use since release).  I really do find it ridiculous that we simmers are still suffering crashes from a decade old program (which is really all Prepar3d is along with a few updates and $60-$200 charges), but enough with my rant.  I realize this is a complex program and an infinite amount of complications that can be caused by addons and interactions etc.  Anyway, this one occurred 6 hours into my 11 hour KSEA-ZBAA flight.  I simply heard a stutter from the engines before seeing the sim screen go foggy and being greeted with the (Prepar3d is not responding) crash message, leaving me with only the option to close the program.  Nothing was being touched or used at the time of the crash
Addons Used: PMDG 777-200LR, Active Sky 2016 + ASCA, PTA 2.52 (newest), ReShade, GSX, Chaseplane, FTX Global, FSDreamteam KJFK and Imaginesim ZSPD (both not used in this flight since route was KSEA-ZBAA)

Any ideas?  Thanks

LOG

﻿Version=1
EventType=APPCRASH
EventTime=131448185166537334
ReportType=2
Consent=1
ReportStatus=268435456
ReportIdentifier=4a82f765-7e34-4062-b830-6ae51321b0be
IntegratorReportIdentifier=ba6994b2-af44-4d66-80e6-00ac2f5fc4f8
Wow64Host=34404
NsAppName=Prepar3D.exe
AppSessionGuid=00002c9c-0004-0013-9836-34b234ffd201
TargetAppId=W:0000866ac7dc4c86070bc5133136f5166e7300000904!0000604a7eba7010301df84834a470a2dc1946398e5a!Prepar3D.exe
TargetAppVer=2017//06//21:13:19:17!2dc5a4!Prepar3D.exe
BootId=4294967295
TargetAsId=6743
Response.BucketId=4a5c27c336271dea2231478d6c28ccf2
Response.BucketTable=4
Response.LegacyBucketId=120789136181
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=4.0.28.21686
Sig[2].Name=Application Timestamp
Sig[2].Value=594a7255
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_f04d
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.15063.447
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=a329d3a8
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.15063.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Value=f04d
DynamicSig[24].Value=4489
DynamicSig[25].Value=44897abb5047a399ff26860ff314661b
UI[2]=C:\Prepar3d V4\Prepar3D.exe
UI[3]=Prepar3D exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Prepar3d V4\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=01B0040EA8F9B196DE109F7E67B174D6

##### Share on other sites
 Help AVSIM continue to serve you!Please donate today!

It's not the "decades old program" (which is not even close, considering all the revisions to the graphics engine). As you stated clearly, it's far more likely that the combination of add-ons that you listed is the cause of the error, which is heap corruption. This means that something caused the sim to write to location in memory where it was not allowed to do so. Jim Young will probably be along to give you more detailed guidance, but suffice it to say that you will have to methodologically disable all the add-ons and then add them back one by one to see which one is causing the CTD. I would start with ChasePlane, Reshade, GSX and PTA, in that order.

We are all prisoners of the open architecture that's used in P3d.

• 1

##### Share on other sites

It's just over one month old, Prepar3d V4 is 64 bit, a completely new build. what settings did you have, is your system capable of high settings under 64 bit.

##### Share on other sites
3 hours ago, jabloomf1230 said:

It's not the "decades old program" (which is not even close, considering all the revisions to the graphics engine). As you stated clearly, it's far more likely that the combination of add-ons that you listed is the cause of the error, which is heap corruption. This means that something caused the sim to write to location in memory where it was not allowed to do so. Jim Young will probably be along to give you more detailed guidance, but suffice it to say that you will have to methodologically disable all the add-ons and then add them back one by one to see which one is causing the CTD. I would start with ChasePlane, Reshade, GSX and PTA, in that order.

We are all prisoners of the open architecture that's used in P3d.

I'll try that. The only issue is that the crashes do come sporadically, so this will take some time (the crash occurred 6 hours into the flight and I've successfully completed several long hauls before it). When I said "decade old program", I was referring to the fact that much of this is still FSX base code, but nonetheless the addons undoubtedly complicate things. Thanks and I'll see if I make any progress and determining the culprit

##### Share on other sites
16 minutes ago, JustanotherPilot said:

It's just over one month old, Prepar3d V4 is 64 bit, a completely new build. what settings did you have, is your system capable of high settings under 64 bit.

I realize that it's technically new, but much of the code is still FSX base code and crashes have plagued simmers in every build that has come. Prepar3d V3 also gave me its fair share of crashes throughout its life. I know that it's very complicated, but stability has never been the platform's strong suit. I mean, we only just got 64bit, so it's not entirely inaccuarate to say that Prepar3d has always been a very FSX based system. Regardless, my specs are as follows.

Cpu: i7 4930k @4.4GHZ

RAM: 16GB

GPU: GTX 1080

PSU: Corsair RM1000

My settings are mostly maxed out with a few exceptions, and normally get around 30FPS (worst case scenario in the low 20s if I have heavy weather, big city and airport scenery), so performance is never an issue. Thanks for the help and I'm not trying to bash the platform. It's a great sim...it's just that I do find it a bit frustrating that every iteration of Prepar3d seems to have stability issues once addons start coming in (which may very well be the culprit), and I can't help but think that a lot of it may be due to the underlying age of much it's code and the fact that brand new addon technology is trying to function with an otherwise older sim

##### Share on other sites

Btw, nothing in particular seems to trigger it. As I've said, I successfully completed several long hauls using the same addons as in this build. The crashes seem entirely random and unpredictable, so it may take a while for me to see which addon (if that's the case) is causing issues. It could take 10 flying hours...could take 60 :(  I'll post back if I find anything. It is worth mentioning that the last time it crash, app crash view did not even generate a crash log so I don't know what was the culprit of the first crash (file-wise)

##### Share on other sites

Page 33 of the AVSIM CTD Guide discusses a StackHash.  See my signature for the link to the guide or look to the right of this forum on the sidebar under Hot Topics.  Most likely your P3D settings are too high.  There are some other suggestions in the guide that worked for others but high settings is the most common.

##### Share on other sites
3 hours ago, Jim Young said:

Page 33 of the AVSIM CTD Guide discusses a StackHash.  See my signature for the link to the guide or look to the right of this forum on the sidebar under Hot Topics.  Most likely your P3D settings are too high.  There are some other suggestions in the guide that worked for others but high settings is the most common.

I'll check it out. Thanks!

##### Share on other sites

So I gave the CTD guide a look and I'll do some test flights to see how it goes.  Like I said, I completed several flights in the past without an issue, so perhaps this was a random occurrence (especially given that the stackhash error is so nonspecific).  Aside from that, I'll try updating GPU drivers and windows.  If none of that works, then I'll start removing addons one by one.  Thanks for the help everyone

##### Share on other sites
On 7/19/2017 at 2:40 AM, markjj said:

So I gave the CTD guide a look and I'll do some test flights to see how it goes.  Like I said, I completed several flights in the past without an issue, so perhaps this was a random occurrence (especially given that the stackhash error is so nonspecific).  Aside from that, I'll try updating GPU drivers and windows.  If none of that works, then I'll start removing addons one by one.  Thanks for the help everyone

How did things work out for you? I am getting this very error as well and like you, very sporadically. Also with PMDG 747 or 777 (have latest updates). Just got one today about 5 or 6 hours into my trans-Atlantic flight over open water and I was not even near the sim. I can do most flights just fine and then, bam.. this error again. I will try turning down some settings I guess. Don't know why the settings work most times but then this time it don't. In doing many searches via Google, the only common denominator I have found is PMDG 747 or 777 aircraft. Sooo frustrating!!

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f
Exception code: 0xc0000374
Fault offset: 0x00000000000f8283
Faulting process id: 0x1590
Faulting application start time: 0x01d30ec6c1941828
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2498b973-27c4-4c8f-973d-6af1691b6c4e
Faulting package full name:
Faulting package-relative application ID:

• 1
• 1

##### Share on other sites

If you have MyTrafficX installed, many of the aircraft are not compatible with V4 (or V3) so P3D crashes occasionally when these aircraft are called.  Many have succesffully stopped the crashes by renaming the trafficmil.bgl in the MyTraffic/Scenery folder.  Others have removed the old FS9 developed AI so that they can continue to use the trafficmil.bgl.  This fix is shown in the AVSIM CTD Guide under ntdll.dll.

Best regards,

Jim

##### Share on other sites
2 minutes ago, Jim Young said:

If you have MyTrafficX installed, many of the aircraft are not compatible with V4 (or V3) so P3D crashes occasionally when these aircraft are called.  Many have succesffully stopped the crashes by renaming the trafficmil.bgl in the MyTraffic/Scenery folder.  Others have removed the old FS9 developed AI so that they can continue to use the trafficmil.bgl.  This fix is shown in the AVSIM CTD Guide under ntdll.dll.

Best regards,

Jim

Don't have MyTraffic installed. I do have AI traffic for use online but I was over the Atlantic and not another aircraft in sight for a few hundred miles! So that is not it. I have been looking around the internet and see that the PMDG 747/777 are frequently mentioned with this ntdll.dll error and long haul flights.

##### Share on other sites

Best to go to the PMDG website and submit a trouble ticket then.

##### Share on other sites
16 hours ago, B777ER said:

Don't have MyTraffic installed. I do have AI traffic for use online but I was over the Atlantic and not another aircraft in sight for a few hundred miles! So that is not it. I have been looking around the internet and see that the PMDG 747/777 are frequently mentioned with this ntdll.dll error and long haul flights.

Just had another crash today despite my efforts (latest drivers, updates, turning addons off, etc). A few hours into a 12 hour flight from ZSPD-KDTW, the sim CTD with the same stackhash error. It's practically unusable for me and I'm considering downgrading to V3 as it was much more stable despite having its crashes every now and then. Even though CTDs have been an issue throughout the life of the P3D/FSX platform, it does seem to occur more often with this particular build so perhaps it needs a hotfix. Like I said, flying has become impossible in anything longer than a few hours and I can't pinpoint it to any addon

##### Share on other sites

Here was the log from my last crash...approximately 3 hours in

﻿Version=1
EventType=APPCRASH
EventTime=131465672505320586
ReportType=2
Consent=1
ReportStatus=268435456
ReportIdentifier=cdae9888-6396-4518-afd8-f6c406fdb70c
IntegratorReportIdentifier=1fc78262-ee84-41ca-b750-108478012564
Wow64Host=34404
NsAppName=Prepar3D.exe
AppSessionGuid=00000f18-0003-0022-1262-5f2e380fd301
TargetAppId=W:0000c84560c5817c3bd2b647f42bb21eb2d20000ffff!0000604a7eba7010301df84834a470a2dc1946398e5a!Prepar3D.exe
TargetAppVer=2017//06//21:13:19:17!2dc5a4!Prepar3D.exe
BootId=4294967295
TargetAsId=3671
Response.BucketId=4a5c27c336271dea2231478d6c28ccf2
Response.BucketTable=4
Response.LegacyBucketId=120789136181
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=4.0.28.21686
Sig[2].Name=Application Timestamp
Sig[2].Value=594a7255
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_f04d
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.15063.447
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=a329d3a8
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_44_FROM_ntdll+0x00000000000A5EF4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.15063.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Value=f04d
DynamicSig[24].Value=4489
DynamicSig[25].Value=44897abb5047a399ff26860ff314661b
UI[2]=C:\Prepar3d V4\Prepar3D.exe
UI[3]=Prepar3D exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Prepar3d V4\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=01B0040EA8F9B196DE109F7E67B174D6

##### Share on other sites

The AVSIM CTD Guide provides possible solutions for StackHash errors and NTDLL errors.  The fixes provided are from fellow members here at AVSIM and across the Internet at other FlightSim websites.  The fixes worked for them, including me, so I placed them in the CTD Guide.

It is definitely not the PMDG products causing these types of crashes.  High settings are more likely.  PMDG products have never caused a StackHash or NTDLL error in the life of all of their products.  StackHash and NTDLL errors began to surface soon after Sandy Bridge i7 CPU was released by Intel when CPU's were starting to be overclocked even by the novice computer users.  That was in January 2011.

Best regards,

Jim

##### Share on other sites
2 hours ago, Jim Young said:

The AVSIM CTD Guide provides possible solutions for StackHash errors and NTDLL errors.  The fixes provided are from fellow members here at AVSIM and across the Internet at other FlightSim websites.  The fixes worked for them, including me, so I placed them in the CTD Guide.

It is definitely not the PMDG products causing these types of crashes.  High settings are more likely.  PMDG products have never caused a StackHash or NTDLL error in the life of all of their products.  StackHash and NTDLL errors began to surface soon after Sandy Bridge i7 CPU was released by Intel when CPU's were starting to be overclocked even by the novice computer users.  That was in January 2011.

Best regards,

Jim

Thanks for the help. However, I am a little bit confused. If it really was the scenery settings being too high (for example) that was causing the stackhash errors, wouldn't that at least by partially reflected in my sim's performance? I consistently achieve FPS  in the high 30-40 range in small cities and mid 20-30 range in large cities/addon airports, leading me to believe (and I could be entirely wrong) that the settings aren't exceeding what my setup is comfortably capable of. Additionally, my CPU load never reaches 100% and seems to maintain relatively consistent levels throughout any session. Finally, x plane and other intensive programs do not give me any issues despite their power hungry nature, and several stress and temp tests have indicated that the overclock is indeed stable. With this in mind, is it still possible that stackhash errors are being caused by high settings or unstable overclocks, despite the evidence suggesting otherwise (perhaps P3D just isn't adequate at utilizing today's technology as well as some other programs)?  I am using a 4930k which is stable at 4.4GHz and running cool with sufficient voltage (again as indicated by numerous stress tests)

##### Share on other sites

P3D was never developed to set all of the settings to max (or near max).  Same goes with FSX, its predecessor.  Certainly you will not get a crash all of the time or immediately by having high settings but it will happen, somewhere, sometime and that's not a good way to enjoy flight simulation.  It is horrible, absolutely horrible to have a long flight over 2 hours in length only to see the sim crash at the end.  I get crashes occasionally with my system and it is extremely powerful (see specs in signature).  Most of the time it's caused by a bad overclock.  Stress tests mean absolutely nothing when it comes to FSX and P3D.  I have run several stress tests with my system after an overclock and it runs great for a couple of months and then it crashes.  I get the ntdll error and that means (in FSX/P3D terms) a bad overclock.  Either the CPU voltage is too high or too low.  So I return my system to the optimal default (which is 4.5GHz for my i7 7700K CPU).  Success!  Haven't seen a crash since.  I have been watching my temperatures too.  The CPU is not the only component you need to worry about.  The GPU gets hot too and especially after a long flight.

Go ahead and run P3D at the max or near max.  You are not going to enjoy this game very long.

But that is not the only reason for a StackHash.  Heck, I have had to reinstall Windows to get rid of a StackHash!  And it turned out to be a software addon to P3D.  Turned out I had AI that was being called but no flight plan.  The crash happened at exactly the same spot every time.  Other members here have found that objects being called by an AI program like MyTrafficX were incompatible and threw a StackHash.  This is why the AVSIM CTD Guide suggests you investigate your situation.  Rename your scenery.cfg and conduct the same flight.  Did you have a StackHash or NTDLL error?  If no, then rebuild your P3D.cfg and leave everything at the default (I know it will not look good) and fly the route.  If no crash, then it was something in the P3D.cfg.  It is the only way you are going to be able to resolve this issue as there is no known fix to a StackHash that works for everyone.

Best regards,

Jim

## Create an account

Register a new account

• Tom Allensworth,
Founder of AVSIM Online

• ### Hot Spots

• Flight Simulation's Premier Resource!

AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

$20,115.00 of$36,000.00 goal reached.