Author Topic: 5.1: "Just warp me" causes CTD  (Read 2138 times)

Julz8585

  • Newbie
  • *
  • Posts: 3
5.1: "Just warp me" causes CTD
« on: October 30, 2020, 01:24:52 am »
Hi everyone,

I don't want to blame GSX, but after updating to P3D 5.1 I can trigger and reproduce a CTD with the GSX-request "reposition/warp me there".
This happened in KDEN (Flightbeam) and KORD (V2 by FSDreamteam).

Is this a scenery problem?

The eventviewer recorded this:

Faulting application name: Prepar3D.exe, version: 5.1.8.26742, time stamp: 0x5f988752
Faulting module name: ucrtbase.dll, version: 10.0.18362.1110, time stamp: 0xb4cacc38
Exception code: 0xc0000409
Fault offset: 0x000000000006dace
Faulting process id: 0x1a20
Faulting application start time: 0x01d6ae4fb46ff44f
Faulting application path: P:\P3Dv5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: d92104a7-5bc4-438d-b7ad-170f6d1535e9
Faulting package full name:
Faulting package-relative application ID:

« Last Edit: October 30, 2020, 01:27:17 am by Julz8585 »

adamjpestridge@gmail.com

  • Newbie
  • *
  • Posts: 12
Re: 5.1: "Just warp me" causes CTD
« Reply #1 on: November 01, 2020, 12:28:51 pm »
Hi there!

The URCTBASE.DLL is the dynamic link library file associated with Microsoft Visual C++ redistributable package.

Please try these steps:

1. Try to repair all the Visual C++ files in control panel - program and features

2. Try to run Microsoft Visual Studio to repair all the C++ DLL files

3. Restart Machine

If all this doesn't help, please contact Microsoft to get the windows dll repair.

Hope this help!

LukeK

  • Full Member
  • ***
  • Posts: 108
Re: 5.1: "Just warp me" causes CTD
« Reply #2 on: November 01, 2020, 03:21:34 pm »
Why do you think the DLL is corrupt? 99.999% of the time these errors are because of passing in an invalid parameter to a Windows system call, not DLL corruption.

Cheers

Luke

BerndB

  • Newbie
  • *
  • Posts: 16
Re: 5.1: "Just warp me" causes CTD
« Reply #3 on: November 02, 2020, 05:08:01 pm »
It seems this issue is due to a SODE incompatibilty with V5.1

There are many threads in AVSIM and the LM forum which are about this specific crash.