P3D V.4 Crash

[RakGongYoo 0]

Hi, I just bought a new A320 Prof.. In my case, it seems around 30 mins or just before TOC, the P3D crashed (the program shutdown with out any error popup) I have other A/Cs like PMDG B777, which are working normally.  Prepar3D.exe

4.5.14.34698

5e94b5c2

ucrtbase.dll

10.0.19041.3636

81cf5d89

c0000409

0000000000071208

528c

01daea1d39095c88

C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe

C:\Windows\System32\ucrtbase.dll

2cbb9ec1-1490-4aa7-a310-4e9250dd0828

 

 

my P3D version 4.5, and I also attached the log from AS Version info with this post.

 

Anyone please help.
 

Regards,
Rak.

ASVersionInfo.TXT

[mopperle 4178]

The mentioned dll (ucrtbase.dll) is a Windows system file. A crash of this dll can be caused by everything. So the A320 might not be the reason, but just be affected by this.

What I see:

- you are on Windows 10, make sure that it got all updates

- your graphics driver is totally outdated

- how much dedicated RAM does your graphic card have?

- how much Ram does your Notebook have?

- your .NET frameworks is also a bit outdated

[RakGongYoo 0]

15 hours ago, mopperle said:

The mentioned dll (ucrtbase.dll) is a Windows system file. A crash of this dll can be caused by everything. So the A320 might not be the reason, but just be affected by this.

What I see:

- you are on Windows 10, make sure that it got all updates

- your graphics driver is totally outdated

- how much dedicated RAM does your graphic card have?

- how much Ram does your Notebook have?

- your .NET frameworks is also a bit outdated

I have tried to update all Windows updates, GPU drivers, and also .NET, but I still face crashes.

My GPU RAM : 4GB

My Laptop RAM : 16GB

 

One more thing, the crash always happens when the flight approaches the CRZ level.

 

Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x5608
Faulting application start time: 0x01daead374490f2f
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 88c13bfe-5685-4d10-884a-231810fcd72e
Faulting package full name: 
Faulting package-relative application ID: 

 

Any idea?

 

[mopperle 4178]

Hard to tell. In the past there where several reports about the ucrtbase.dll crash. In none of them the A320 was the problem, but other software or a somehow broken Windows installation. I remember that an add-on called RAASPro caused problems in some cases. Uninstalling it solved the Problem. Also a fresh Windows installation solved the problem.

If you search the web for "P3D ucrtbase.dll" you'll find tons of post not related to the Bus, but even with newer versions of P3D and other add-ons.

[RakGongYoo 0]

4 hours ago, mopperle said:

P3D ucrtbase.dl

I still have some questions like,

   - Why only when I'm flying A320?

   - Why did it happen only when approaching the CRZ level (I have tried multiple CRZ levels)? Is anything related to CRZ?

[RakGongYoo 0]

More finding

   - Set CRZ level in FMC 10,000' and also FCU CLB to 10,000'   ->  CTD on approaching 10,000' (9,640', ATL*)
   - Set CRZ level in FMC 10,000' and set FCU CLB to 9,000' -> Good, not crash

      - After maintaining 9,000' for a while, set FCU to 10,000' -> CTD on approaching 10,000'

   - 1 flight test done:

        Plan FL340, set FCU FL340, set MCDU FL350 (Higher than FCU level).

        Then CLB to CRZ at FL340 as set by FCU, then after CRZ. update MCDU to FL340.
        the flight can continue without crashing till parking. 

[mopperle 4178]

The ucrtbase.dll is a very wired one, as it is a system file and it is extremely hard to track down the reason.

As I told you, this error appears also in other constellations and even with add-os, which do not crash on your specific system.

That means something else in a specific constellation is causing the crash and the A320 is not the reason, but affected by the crash and shows that something is wrong in a specific (your) environment.

If there would be a bug in the A320 code causing the crash, there would be thousands of reports. But this is not the case and the A320 in its current version is now out for several years.

 

I‘m sure, when you have a vanilla Windows 11 with a vanilla P3D and the A320 only, you will not see the crash.

[RakGongYoo 0]

As I tried with the flight test in the previous post, I don't think it's 100% non-related to the A320.

Since the flight can continue, by just to avoid the first ALT* to capture.

 

I understood that the DLL can be caused by wide things, but other aircraft just work perfectly at expected except A320.

Thank you for your help, but this problem can be considered as Don't know how to fix this CTD.