Guild Wars 2

Hi there. Whenever I start the game, I got an error message saying something important crashed.

I can still play, but at max 30 fps (while I was usually at 60), no sound, and there is this error message at the middle of the screen that won’t move away…

Message logs says:

—> Crash <—
Exception: c0000005
Memory at address ffffffff`ffffffff could not be read
App: Gw2-64.exe
Pid: 8060
Cmdline:
BaseAddr: 00007FF7FCEA0000
ProgramId: 101
Build: 73863
When: 2017-03-18T13:43:42Z 2017-03-18T14:43:42+01:00
Uptime: 0 days 0:00:41
Flags: 0

…yeah, that’s not good. Try removing any DPS meters, graphical enhancements like reshade or gemfx, overlays like overwold, etc.

Disable video card monitoring or recording things, such as AMD Afterburner, RivaStatisticsServer, NVIDIA ShadowPlay, which have been known to cause various oddities.

Ensure drivers are up to date.

Reboot; at least one person had crashes due to a partial LavaSoft uninstallation or upgrade resolved by that.

Consider saving your gw2.dat file, delete the rest of the content of the directory, do the install thing again, cancel when it gets to downloading files, and put gw2.dat back. That should give you a clean, uncorrupted exe to work with.

Check your GPU has a PCIe 16x connection using GPU-Z; poor connections have cause a wide range of extremely strange errors for other players.

best of luck.

Wait there is DPS metters for GW2 ? :o
What are reshade and gemfx ?

I’ll try all of those solutions, thanks

Fixed it by updating Nvidia drivers and restarting the PC. Thanks a lot !

Kehlian.4380:

Wait there is DPS metters for GW2 ? :o
What are reshade and gemfx ?

Yeah, memory-reading DPS meters are tolerated by the developers, so you can use them if you would really like to. It’s a bit contentious, and it is absolutely “at your own risk”, and since they hook into low level code, and use internal data structures, they can definitely cause crashes.

reshade and gemfx are tools that hook into the graphics presentation pipeline and let you apply additional filters to what is displayed. (As far as I can tell, mostly to make things look terribly garish, but I guess some people like over-saturated or whatever? Anyway, that’s just snark, and they can do more or less anything graphically.)

Since those all hook into the graphics pipeline and/or client code, if they are out of date they are potential causes of crashes. (reshade and such are much less likely to be at fault, because of what and when they do, but it’s not impossible, and it’s an easy test to eliminate them, so…)