ucrtbase.dll crash. 5.1

[ItzZenTy]

Since I applied the SODE fix, I have not had an urctbase.dll crash. I rather doubt it's a Windows issue - I have 20H2 also.

Have you tried googling this:

urctbase.dll crash

Maybe you could post the full text from Windows Event Viewer next time you see the crash.

Sorry if I am repetitive -

Jorgen

I found out that I actually don't have 20H2, Windows just offered me an update to it. So I had 2004 all the time, I'll try to update it and see what will happen, probably there is some sort of issue that my windows has been outdated all the time.

[Arcavian]

Since I applied the SODE fix, I have not had an urctbase.dll crash. I rather doubt it's a Windows issue - I have 20H2 also.

Have you tried googling this:

urctbase.dll crash

Maybe you could post the full text from Windows Event Viewer next time you see the crash.

Sorry if I am repetitive -

Jorgen

Hello, im having this issue on v5.1 it happens from on ground -> cruise phase and i just cant figure it out. I also have 20H2, I turned off SODE in addon in manager.

Faulting application name: Prepar3D.exe, version: 5.1.12.26829, time stamp: 0x5fb44f72
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0xd0c
Faulting application start time: 0x01d7108a7702b822
Faulting application path: D:\Games\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 59234b6e-b612-49d3-8ec4-4cbb9f8d9dcc
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1885561169882050409, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 5.1.12.26829
P3: 5fb44f72
P4: ucrtbase.dll
P5: 10.0.19041.789
P6: 2bd748bf
P7: 0000000000071208
P8: c0000409
P9: 0000000000000005
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D90.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CC4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CD4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CD6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CF6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_ba5a7b5c6c6ecebcf0b5204cb2a2c8aa90c31ec_b489456f_7d38b573-96f0-453d-bed3-95c5c437121d

Analysis symbol:
Rechecking for solution: 0
Report Id: 59234b6e-b612-49d3-8ec4-4cbb9f8d9dcc
Report Status: 268435456
Hashed bucket: 1b58a0087d1d8eaada2adbe4d516ef69
Cab Guid: 0

[JorgenSA]

If you search the web for the exception code:

0xc0000409

you will get a whole lot of answers with articles on how to solve this. As an example, try reading and applying the fixes in this one:

https://www.minitool.com/news/0xc0000409.html

Jorgen

[lance74]

I have the same issue. This only happens in the FSLabs planes for me.

[JorgenSA]

If it only happens on FSLabs airplanes, then you need to contact FSLabs.

Jorgen

[SamuelRichards]

This problem STILL persists.