V6 CTD while using VATSIM

[Badapp1e]

Windows 11 fully updated.
Nvidia drivers fully updated.
P3Dv6 updated with the latest update.

Whenever using VATSIM (specifically vPilot) after exactly 30 mintues of flight I will have a crash to desktop without warning, without hessitation.
On one second, off the next.

It does not matter if I am using scenery software or not. It is a time issue and something to do with vPilot in my opinion. But then I'm not a computer guru. Just a regular user.

Guess I'll have to go back to V5 if this is not addressed. If I run V5 in VATSIM and running vPilot there are no issues.

Please advise. (and I don't need some smart-ass telling me to get MSFS)

Thanks.

[JorgenSA]

Certainly I will not be telling you to use MSFS - that one stayed on my system for all of about 30 minutes.

But I will tell you that we need the error information for this CTD from Windows Event Viewer.

Note down the time of your crash (approximately).

Then right-click on your Windows Start button and select Event Viewer. Select Windows Logs, then Application. In the top center pane scroll down to the time of your crash, there should be one or two entries there titled Error.

Highlight those in turn, copy the information displayed in the bottom center pane and post it here. That will give us something to go on.

Jorgen

[Badapp1e]

Fault bucket 1426813838799039683, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 6.0.35.31017
P3: 65037d67
P4: Captain_Sim.glacs.dll
P5: 1.6.0.0
P6: 5f68c584
P7: c0000005
P8: 00000000000114ff
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b3cadb95-6614-4798-98ba-2ac63c07ec78.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f958a87d-c1b2-472d-afcc-6d5aef9dc7bc.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6c8af56-702c-4616-9d71-a648439e0703.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6fc04fbe-efe4-41ef-b826-aa18970faf1d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e08a1c62-e5e1-47da-9f33-b081e87c4ae7.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_ce6cc6ffe6b4241d14c68617a6e908df9b66e8_f62272dc_a6198afd-1067-4afb-a63c-9214067219ea

Analysis symbol:
Rechecking for solution: 0
Report Id: ab5f5149-7992-4c95-a809-5be2d6422281
Report Status: 268435456
Hashed bucket: fb307a63b1b3e4a943cd0fa0763a6cc3

[Badapp1e]

Faulting application name: Prepar3D.exe, version: 6.0.35.31017, time stamp: 0x65037d67
Faulting module name: Captain_Sim.glacs.dll, version: 1.6.0.0, time stamp: 0x5f68c584
Exception code: 0xc0000005
Fault offset: 0x00000000000114ff
Faulting process id: 0x3bbc
Faulting application start time: 0x01d9f28a7783a4dc
Faulting application path: D:\Lockheed Martin\Prepar3D v6\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v6\SimObjects\Airplanes\CS_B757-200-III_PW2037\panel\Captain_Sim.glacs.dll
Report Id: ab5f5149-7992-4c95-a809-5be2d6422281
Faulting package full name:
Faulting package-relative application ID:

[JorgenSA]

This is what we needed.

The exception code here:

Exception code: 0xc0000005

tells us that "something" attempted to write to an area of RAM where it had no access rights. There is nothing, however, that tells us directly what this "something" is or might be.

However, in this case this:

Captain_Sim.glacs.dll

gives us a clear pointer towards a Captain Sim add-on. It might not be the direct culprit, but it is certainly involved.

Let us know how it goes -

Jorgen

[Badapp1e]

Thank you for your reponse. I think I will disable the CptSim dll file. However, while waiting for your reply I got back on V5 and flew for 93 minutes and another CTD. This time the culprit was terrain.dll.

But! Before I flew this time I cleared out the Shaders and let it rejuevenate new ones. Maybe that was not a good idea?

[JorgenSA]

Clearing out the shaders is always a good idea.

What was the exception code for the CTD in v. 5?

Jorgen