Hi all.

Been having a very recent problem with QW787, when I open up the chart page it leads to an automatic CTD of P3D 5.3 HF2. After some testing I have been able to narrow this down to the navigraph charts only, as non navigraph charts don't lead to this issue. I've made sure they're activated (using the QW navigraph verification directly). Reinstalled QW 787. Reinstalled the C++ 86 and 64, and used SFC check via the command prompt. None of them have fixed the issue or lead to improvement.

I do luckily have a crash log.

Spoiler

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFC610611C6

Spoiler

Faulting application name: Prepar3D.exe, version: 5.3.17.28160, time stamp: 0x61e6ab02
Faulting module name: VCRUNTIME140.dll, version: 14.38.33135.0, time stamp: 0xe2e02087
Exception code: 0xc0000005
Fault offset: 0x00000000000111c6
Faulting process id: 0x0x3308
Faulting application start time: 0x0x1DA75329B089ED9
Faulting application path: C:\P3Dv5\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: bfed62e9-0ffe-4fa5-907b-23edfcb5eed1
Faulting package full name:
Faulting package-relative application ID:

Signed John.

VCRUNTIME140.dll is part from visuel studio 2015.

Try to install or reinstall this one.

Yves

6 hours ago, yvesamuel said:

VCRUNTIME140.dll is part from visuel studio 2015.

Try to install or reinstall this one.

Yves

Already had it installed but reinstalled it. Crashed again with this error.

Spoiler

Faulting application name: Prepar3D.exe, version: 5.3.17.28160, time stamp: 0x61e6ab02
Faulting module name: qw787.gau, version: 0.0.0.0, time stamp: 0x60450501
Exception code: 0xc0000005
Fault offset: 0x00000000002f2c05
Faulting process id: 0x0x58CC
Faulting application start time: 0x0x1DA75A713BB998B
Faulting application path: C:\P3Dv5\Prepar3D.exe
Faulting module path: C:\P3Dv5\Gauges\qw787.gau
Report Id: 9beb916a-8a96-474e-929d-db1135af587a
Faulting package full name:
Faulting package-relative application ID:

Afterwards tried again removing the hires panel entry in the CFG. And this time had this crash log.

Spoiler

Faulting application name: Prepar3D.exe, version: 5.3.17.28160, time stamp: 0x61e6ab02
Faulting module name: VCRUNTIME140.dll, version: 14.38.33135.0, time stamp: 0xe2e02087
Exception code: 0xc0000005
Fault offset: 0x00000000000111c6
Faulting process id: 0x0x21FC
Faulting application start time: 0x0x1DA75A8B33991F4
Faulting application path: C:\P3Dv5\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: b06338ad-2e11-4a0a-a2bc-328bb7235dca
Faulting package full name:
Faulting package-relative application ID:

John.

How about the VC registributable version itself ?

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

I was also reading about a CTD in the iFly 737 relating to a Navigraph update, it was last year though, something to think about perhaps ?

https://ifly.flight1.net/forums/navigraph-airac-2310-crash-to-desktop_topic21174&FID=13&PR=3.html

Cheers

On 3/14/2024 at 1:01 AM, Rogen said:

How about the VC registributable version itself ?

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

I was also reading about a CTD in the iFly 737 relating to a Navigraph update, it was last year though, something to think about perhaps ?

https://ifly.flight1.net/forums/navigraph-airac-2310-crash-to-desktop_topic21174&FID=13&PR=3.html

Cheers

What do you mean by the VC registributable version itself?

The CTD in the iFLY is interesting. And is very likely related, cause I noticed it only started after I updated the data for the FMS manager.

However QW haven't updated their 787 in years despite some bugs still existing (the controls only moving halfway during control checks to name one). So I doubt they'll update it.

Signed John.

On 3/15/2024 at 7:38 PM, FSXCYYZEGLL said:

What do you mean by the VC registributable version itself?

The CTD in the iFLY is interesting. And is very likely related, cause I noticed it only started after I updated the data for the FMS manager.

I mean was the latest Visual Studio 2015 redistibutable installed ?

The link is MS's main landing point to downloading the most current VS redistributables.

The iFly issue related to a count of lines where Navigraph supplied a file with less lines prior to ifly releasing an update, potentially you could trial something similar to narrow down the issue.

I don't have either navigraph or the 787, so please take my suggestions with a grain of salt.

Cheers

 

Ok so here goes, I hope this helps those having this problem. It's not the QW787 aircraft or the VC redistributable either. I've been trying to figure this out for hours, simple, what changed? It's the Navigraph file itself, so in the end I reinstalled the QW787, after cleaning all I could relating to QW, perfect everything working as it should, with no CTDs.

So I now have everything stock.

I downloaded a manual update from navigraph for the qw787 only, I installed and kept a backup of the original nav files as asked at the install prompt, it creates a backup folder in the navdata folder. I renamed the newly updated apps.txt file to appsoff.txt, so it wouldn't read when I loaded the aircraft. I put the original apps.txt file back in from the backup folder, opened both the apps.txt and the new data appsoff.txt with Notepad, searched for in my case, WSSS and YBBN, copied and pasted from new data appsoff.txt back into apps.txt and saved. I only copied the airports I wanted, there are just too many to go one by one, I did try to control all, but there is a bug in the file somewhere, which copied as well, so take only the information you need, not a perfect solution but works for me.