Hello all,

I have had the problem for a few days that the sim crashes whenever I am trying to either load or save a flight. I am not confronted with any kind of error message, the sim just quits.

I looked on the common boards but there is no answer to be found. Although other users have reported similar problems in the past there doesn't seem to be a solution to it.

P3d runs in Admin mode and is perfectly fine, until it comes to loading a saved flight or saving one. Interestingly the autosave function from FSUIPC works flawlessly (the files are all in their respective folders) and also to load a saved panel state from a file directly through the addon (i.e. PMDG) works without problems.

 

I have below what error message "appcrashview" shows me:

 

Quote

Version=1
EventType=APPCRASH
EventTime=131575533063585645
ReportType=2
Consent=1
UploadTime=131575533081532012
ReportStatus=268435456
ReportIdentifier=9da60408-49e3-4fcd-a879-82b29df3e57f
IntegratorReportIdentifier=41b46724-eeff-4aba-9a1d-6c234d210f22
Wow64Host=34404
NsAppName=Prepar3D.exe
AppSessionGuid=000027b4-0001-0002-eee4-dc153f73d301
TargetAppId=W:0000f0e3cd7a622a9f58f96eda9e904fcd8500000904!0000fe4ba4844cdbd482c25c2fa58f1644d0a18615dd!Prepar3D.exe
TargetAppVer=2017//10//05:18:48:53!2d051c!Prepar3D.exe
BootId=4294967295
TargetAsId=1840
UserImpactVector=321925936
Response.BucketId=0c2f7aa650a720d034acc364ba1124b3
Response.BucketTable=4
Response.LegacyBucketId=120849934265
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=4.1.7.22841
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=59d67e95
Sig[3].Name=Fehlermodulname
Sig[3].Value=terrain.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=4.1.7.22841
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=59d67e0c
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=0000000000009ad3
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.16299.2.0.0.768.101
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=2a45
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=2a456c18b0a947b98ec016566e57f29d
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=8b91
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=8b914dde7014d56a03b4e5b3543505d0

The event viewer has no record of the error interestingly.

What I did try so far:

- Change the folder location of the saved flights (i.e. change the document folder target)

- Run as admin

- remove installed aircraft (to avoid corrupt cfg)

- Rebuild p3d.cfg.

- delete all the saved flights

 

While this problem is not too serious it would still be nice to save and load flights again.

 

Please let me know your thoughts.

 

Many thanks and best regards,

 

Tom

Delete you're scenery.cfg (back it up) and let it rebuild.  This is usually my last step if all else fails and has always eliminated the issue.  You may have to re-add scenery to the scenery library if individual scenery installations  haven't been added via the .xml method.

Hi Erich,

I tried your recommendation. Without the cfg the sim rebuilds it but then eventually crashes before even reaching the opening screen blaming "ucrtbase.dll" (see below).

Is this a hint that there is something wrong with my sceneries?

 

Quote

Version=1
EventType=BEX64
EventTime=131577475567922031
ReportType=2
Consent=1
UploadTime=131577475576100215
ReportStatus=268435456
ReportIdentifier=39827c00-9f5f-40cd-8330-13d2609a88c9
IntegratorReportIdentifier=edda62d8-7e80-49b5-93ea-f10d6e8a450f
Wow64Host=34404
NsAppName=Prepar3D.exe
AppSessionGuid=0000149c-0001-0003-48bd-43c40375d301
TargetAppId=W:00068873457899e441d3c402f022211b1ca000000904!0000fe4ba4844cdbd482c25c2fa58f1644d0a18615dd!Prepar3D.exe
TargetAppVer=2017//10//05:18:48:53!2d051c!Prepar3D.exe
BootId=4294967295
TargetAsId=956
UserImpactVector=319828240
Response.BucketId=44556d43e9bdfc1a5e9b55074d90081b
Response.BucketTable=5
Response.LegacyBucketId=2205449932382406683
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=4.1.7.22841
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=59d67e95
Sig[3].Name=Fehlermodulname
Sig[3].Value=ucrtbase.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=10.0.16299.125
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=70f70cc4
Sig[6].Name=Ausnahmeoffset
Sig[6].Value=000000000006b70e
Sig[7].Name=Ausnahmecode
Sig[7].Value=c0000409
Sig[8].Name=Ausnahmedaten
Sig[8].Value=0000000000000007

 

I've seen instances where the Nvidia HD Audio driver caused this error when there is/was another audio driver active.

Have you recently updated the Nvidia driver? If so, reinstall - do a custom, clean install and do not enable the hd audio driver.

Obviously, if you are not using Nvidia - ignore my suggestion.

Vic

Did that, no success unfortunately. Any other ideas?

It is almost as though the UI is not finding the folder or whatever it is looking for - since the crash occurs before the list is even loaded...

There is a good trouble shooting guide for this in the LM P3D forum; basically, remove all your addons until you are crash free.  The crash on loading can be caused by anything that is being loaded that has a problem, even a misplaced new line character in an add-on.xml file.  You simply have to find the offending addon in most cases.

I have had that problem some time ago and it was causes by a corrupt AI model.

 

98% of all terrain.dll errors are caused by high P3DV4 settings, especially display driver settings.  Your settings are so high when you load the sim it is having major issues.  You can turn up the settings to the max for the default aircraft but the payware stuff you need to compromise.  When you shutdown, the sim is still continuing to run trying to load the resources and crashes because it shutdown too soon before completing all of its tasks.

The ucrtbase.dll is a fairly new "faulting module" and the cause for this module to crash P3Dv4 is probably based on a corrupted add-on.xml.  That's what I have found anyway.  When I get this error, I immediately check my Addon Organizer from Lorby_Si and run the encoding check in the upper right hand corner of the module.  If an xml or scenery.cfg is not encoded properly I fix it. Restart P3D and the problems go away.  I have also seen this error with improperly installed navdata.  In both cases, the sim closes without explanation but the AppCrashView or Event Viewer will show the faulting module.  I have done a lot of research trying to find out what the module ucrtbase.dll does.  It has shown up many times since P3Dv1 was first released so it is not just inherent with P3Dv4.  The key to investigating this issue is to determine what you were doing when it happened.  Were you programming the FMC of any aircraft where navdata would come into play?  Did you just add a new add-on?  Are there duplicates in the Addon Organizer?  Are there encoding errors? 

Best regards,

Jim

Are you using Spadd Next? Had a similar problem some time ago. Cant remember the exact fix but had something to do with a registry entry made by Spadd Next. Think I found the fix on the forums there.