# P3D Crashing Midflight

## Recommended Posts

Hi Guys,

I have been continuously having problems. Just haven't posted anything as of now. It's a mix of freezing upon minimizing P3D and coming back to it, but the latest log from AppCrashView is that it froze midflight and the "P3d has stopped working" notification has come on. Hope that helps.

﻿Version=1
EventType=APPCRASH
EventTime=131245698446128221
ReportType=2
Consent=1
ReportIdentifier=afb908c4-b337-11e6-a261-848f69f5bd65
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=00002668-0005-0011-e463-f40a3547d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=bf7929587c496433b6078a5c4c1214d2
Response.BucketTable=1
Response.LegacyBucketId=108555517198
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400
Sig[2].Name=Application Timestamp
Sig[2].Value=57d9b14e
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_26ba
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.447
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5819be95
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_69_FROM_ntdll+0x0006E2CC
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Value=26ba
DynamicSig[24].Value=369a
DynamicSig[25].Value=369aefd63ea4b29b82a58bd2040a6cde
UI[2]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\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
LoadedModule[180]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=CF1BD4FB76FA39D9D3E874A8D6DB162A

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

You have P3D installed in the default folder which is okay but there will be permission issues.  The computer experts say this is not the preferred location for installing any flight simulator (FSX, FSX-SE, or P3D).  Make sure UAC is disabled (page 24, AVSIM CTD Guide) and exclude any anti-virus/malware program from scanning the P3D directory (also on Page 24).  AVSIM has an excellent Prepar3D Guide for setting up P3D and running it.

The AVSIM CTD Guide provides excellent instructions on how to fix most freezes/crashes in P3D starting on page 10.  Basically, you rename or move your P3D.cfg to a temporary folder, restart P3D and let the file rebuild.  Still get crashes, then move or rename your dll.xml (there are two locations for this file, one where the P3D.cfg is located and one where the scenery.cfg is located.  The latter is the current default location but many developers still use the previous location).  It is probably best to simply rename the dll.xml to dll.off in both locations.  None of your modules will load then and you will not have access to the programs that need the modules.  Currently I have seen the ObjectFlow for P3D module causing many crashes.  It is not needed except to see some things on the ground like windsocks moving, etc.  The CTD Guide explains how to disable these modules one by one on page 13 and 14.

The faulting module for your crash was a StackHash (not really a module or file).  Page 36 of the CTD Guide provides information about a StackHash... (okay, it says there is no known solution to a StackHash).  I get StackHash crashes occasionally.  They just happen then they go away or the faulting module will move to the ntdll.dll.  Both are related to memory (not VAS).  Maybe you configured your page file wrong (see page 23 of the CTD Guide).  Most times I have seen this error because P3D does not like a module loading.  It can happen if an overclock is bad or a setting in the bios is bad.  I guess when you opened up AppCrashView you saw many P3D crashes?  Were any NTDLL.dll errors?  We have some things to check if you get an ntdll.dll error too.

So, bottom line, your only option is to investigate your crash and figure out what caused it yourself.  The CTD Guide shows you how to investigate it starting on page 10.  See my signature for links to the guides.

Best regards,

Jim

##### Share on other sites

Hi Callegro,

For what it's worth I've had crashes and VAS problems since I upgraded to v3.4, as we speak I've just changed all of my settings to the minimum in an attempt to retain some semblance of realism, yet complete a whole flight. I'm doing EGSS-EGNM in the 737NGX, which I completed many times in v3.3 without the slightest problem. I have made no hardware/software changes since upgrading but VAS memory has become a major headache. If I can't sort it out this weekend, I'm seriously considering a roll back to v3.3.

steve

##### Share on other sites

Thank you guys for the replies. Just did another flight. Carenado Phenom in SW USA. On climb out, I had another CTD. Jim, I disabled UAC and turned off my anti-virus software...haven't done the other options...yet. Here is the appcrashview report:

﻿Version=1
EventType=APPCRASH
EventTime=131245848713481255
ReportType=2
Consent=1
ReportIdentifier=ac72c7ee-b35a-11e6-a261-848f69f5bd65
IntegratorReportIdentifier=19f9a140-d56c-4e31-a77f-075708093fd9
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=00000c28-0005-0011-0fa9-bd775c47d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=d89f89894400cd36d81f158688ac51ff
Response.BucketTable=1
Response.LegacyBucketId=108555926818
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400
Sig[2].Name=Application Timestamp
Sig[2].Value=57d9b14e
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_263d
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.447
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5819be95
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_69_FROM_ntdll+0x0006E2CC
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Value=263d
DynamicSig[23].Value=263d2375729d8dc7c707f6266d226f68
DynamicSig[24].Value=64c0
DynamicSig[25].Value=64c005235335edf1e96759ac6e439aae
UI[2]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\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
LoadedModule[174]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=CF1BD4FB76FA39D9D3E874A8D6DB162A

##### Share on other sites

Nothing new in this crash report.  A stackhash is so serious about the only way to eliminate it is to reformat your hard drive, reinstall Windows, and then P3D and all of your addons.  That's what I did a couple of times as I just could not get rid of it.  But I have learned since then that rebuilding the p3d.cfg, moving my dll.xml and moving my scenery.cfg to a temporary directory and letting P3D rebuild my p3d.cfg and scenery.cfg (to the default), fixes it.  I think I had MyTrafficX installed once and disabled that in the scenery.cfg and that fixed it.  One time it was my overclock and reset it to the default.  If there was a known solution to your StackHash, I would definitely be telling you.

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!

$17,895.00 of$36,000.00 goal reached.