CTD on take off

[GeoffB]

For the first time with P3D I've suffered a CTD. The last 3 entries in Event Viewer show

Source ESENT
svchost
864,R,98
TILEREPOSITORYS-1-5-18:
C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log
-1023 (0xfffffc01)

Source Application Error
Prepar3D.exe
4.5.13.32097
5d8abf93
XAudio2_7.dll_unloaded
9.29.1962.0
4c0643cc
c0000005
0000000000032891
241c
01d5f8a6412ff902
E:\Lockheed Martin\P3Dv4\Prepar3D.exe
XAudio2_7.dll
23d1cb71-88e1-495b-ade1-0b367d637a83

Source Kernel event Tracing
SessionName PerfDiag Logger
FileName C:\WINDOWS\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl
ErrorCode 3221225864
LoggingMode 41943168
FailureReason 0


I had a problem last week when P3D crashed from the start up splash screen and decided to re-install the client (ver 4.5.13.32097)

Has anyone any ideas what I've encountered? There's been a recent Windows update; could that be responsible?

Thanks
Geoff

[Martyson]

Geoff,

Have you search for information on : XAudio2_7.dll ?

Just to verify if any of your past crashes mention XAudio2_7.dll as the Faulting Module Name.

Look in the Windows Event viewer for the "Faulting Module Name" (screenshot example).

[GeoffB]

Vaughan,

I've searched extensively and can only find this one instance where XAudio is identified.

Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: XAudio2_7.dll_unloaded, version: 9.29.1962.0, time stamp: 0x4c0643cc
Exception code: 0xc0000005
Fault offset: 0x0000000000032891
Faulting process ID: 0x241c
Faulting application start time: 0x01d5f8a6412ff902
Faulting application path: E:\Lockheed Martin\P3Dv4\Prepar3D.exe
Faulting module path: XAudio2_7.dll
Report ID: 23d1cb71-88e1-495b-ade1-0b367d637a83
Faulting package full name:
Faulting package-relative application ID:

Does it prove anything?

Geoff

[Martyson]

Geoff,

I like see Faulting Module Name as shown in the screenshot.

Have you searched the Internet and other places for XAudio2_7.dll problems?


Also, this topic is [CTD on takeoff] but you also mentioned "I had a problem last week when P3D crashed from the start up splash screen"

"Does it prove anything?"
So I wanted to verify all crashes in the Event viewer and was the Faulting Module Name the same in each?

[GeoffB]

I've been back to event viewer and can only find these logs identifying P3D...


14 Feb
Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: KERNELBASE.dll, version: 10.0.18362.628, time stamp: 0xf96f12ee
Exception code: 0xc0020001
Fault offset: 0x000000000003a839
Faulting process ID: 0x3390
Faulting application start time: 0x01d5e34b3dcb420f
Faulting application path: E:\Lockheed Martin\P3Dv4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: b9edbff8-3d8d-4253-bb52-e6468f32dd4b
Faulting package full name:
Faulting package-relative application ID:

12 Feb
Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a
Exception code: 0xc0020001
Fault offset: 0x000000000003a839
Faulting process ID: 0x33fc
Faulting application start time: 0x01d5e111df669339
Faulting application path: E:\Lockheed Martin\P3Dv4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 328dd054-c580-43b6-ac1e-dfc48f378f32
Faulting package full name:
Faulting package-relative application ID:

and one minute later

Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process ID: 0x1cdc
Faulting application start time: 0x01d5e11330c925d0
Faulting application path: E:\Lockheed Martin\P3Dv4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 6ebe6c51-355b-40b0-a601-d3c17f3cc5b1
Faulting package full name:
Faulting package-relative application ID:

Geoff

[JorgenSA]

The kernelbase.dll error is a Windows error, not a P3D error.

I found this thread over at AVSIM, take a look at the responses by Jim Young in this:

https://www.avsim.com/forums/topic/5110 ... elbasedll/

Jorgen

[Martyson]

@Geoffb,

Ok, you have a few different erros causing problems.

Your best bet at finding a cause is to run through all the General Debugging Steps:

viewtopic.php?f=6312&t=123246

[GeoffB]

Thank you both. Like lots of others I've now got time to focus on this.

G

[Martyson]

What were you doing / flying / Add-ons in use when you got this ucrtbase.dll error?

Faulting module name: ucrtbase.dll

Have you tested with the default P3D flight (F22 at KVPS)?

[GeoffB]

I've had another strring of crashes today all with the kernell error. I've installed the Lorby addon manager with the intenstion of disabling scenery packages and tryig to load P3D. I started with disabling ORBX PAcific north west. P3D loaded sucessfully :-)

Kernell errors appear to be linked to hardware memory from what I've read. Monitoring memeory use through task manager during P3D load up peaks at 47%. Not particularly high but maybe enough to trip P3D?

I'm back in the air and may have to manage the scenery according to where I'm flying.
Geoff