[GW2 keeps crashing after cutscenes in meta events]

On 11/5/2023 at 4:53 PM, Tashigi.3159 said:

First, make sure you are not running Blish, for some reason several guildies had problems with Amnytas  meta like you but as soon as they uninstalled it and other addons, it began to work without any issues.

The only addon I can confirm personally that works, is the Unofficial All in one Addon with arcDPS.

Secondly, try clearing your cache, it can greatly improve your performance and also gets rid of old junk: 

 

Thanks for these suggestions, I do appreciate them.

But I don't have BLISH nor arcdps running. Tried clearing the cache and attempted Amnytas today: crashed again at start of cinematic.

[GW2 keeps crashing after cutscenes in meta events]

Dear GW2 community,

As of the Halloween update, my GW2 client keeps crashing each time a cut scene pops up in a map meta event (i.e. think of the one at the end of Dragonstorm and the Defense of Amnytas).
Never had any GW2 crashes in the past (as I have been playing since launch).
Now it's withholding me from participating in such events, as in some cases you don't get the event rewards due to the crash and you are not able to rejoin these (public) instances (i.e. Dragonstorm).

Potentially relevant information:

OS: Windows 10 Pro N (22H2) build 19045.3570.
In-game settings: low ( personal preference )
Event viewer log (indicating it's conflicting with a Windows 10 core DLL file)

Quote

Faulting application name: Gw2-64.exe, version: 1.0.0.1, time stamp: 0x65382a73
Faulting module name: ntdll.dll, version: 10.0.19041.3570, time stamp: 0x3be1c500
Exception code: 0xc0000374
Fault offset: 0x00000000000ff279
Faulting process id: 0x844
Faulting application start time: 0x01da0fdc73c39a9f
Faulting application path: R:\Guild Wars 2\Gw2-64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 10bea001-add6-4e5b-b03d-325b5f04ea94
Faulting package full name:
Faulting package-relative application ID:

// Similar errors on earlier crashes (exception code and fault offset), but different faulting process id and faulting application start time - uncertain if this is relevant or not //
.....
Faulting process id: 0x34d4
Faulting application start time: 0x01da0a864d4f83b0
....

//

.....
Faulting process id: 0x3bbc
Faulting application start time: 0x01da0919fb522b59
.....
 

Actions performed on my end:
- Ensured that my Windows 10 is up-to-date.
- Ensured that my local windows files are not corrupt (by running both `sfc` and `dism`)
- Removed GW2 and reinstalled from scratch

Anything else that can be tried?

 

//edit
Grammar fixes