Constant Crashing Since Win 10 Update (1803) - Exception: c0000005

[Lost Ninja.1809]

About every ten minutes my client crashes with a serious error (Memory at address XXXXX Could not be read.) It doesn't seem to happen in all areas but especially in HoT areas it makes the game all but unplayable. Mission areas (instanted) so far don't seem to be having an issue. I've only noticed these crashes in the last day or so and the only thing that I know (for sure) that has changed on my PC was a big Windows 10 update (Feature Update version 1803).

* I have repaired my game.

* I have updated my GPU driver.

* The physical components of my PC are all under 1 year old (built the PC last Aug/Sept) with the exception off the GPU.

* I'm not using any overlays, and while I was using the Radial menu the issue persists when this is removed.

 

DX-Diag Results: https://pastebin.com/bkMuyRtx

Latest Crash: https://pastebin.com/an6zLBXZ

[SlippyCheeze.5483]

There isn't anything terribly informative in that crash, to the outsider, though the GW2 devs may be able to determine more.

 

I do notice that `C:\Program Files\Logitech Gaming Software\SDK\LCD\x64\LgLcdApi.dll` is loading into the process; it may be worth disabling the feature and seeing if things improve. (I doubt it, but hey, worth checking.)

 

Beyond that, I'd check for memory related issues with http://www.thewindowsclub.com/windows-memory-diagnostics-tool-in-windows-7

 

[Ray Koopa.2354]

I also don't think that DisplayFusion might dork around with the game that hard that it causes a MAV, but try turning it off aswell for a test.

Are 2GB of video memory alright for GW2 nowadays? I never checked how much it takes.

[Inculpatus cedo.9234]

I only have 512MB of video memory, and I very rarely (maybe twice in the nearly 6 years) crash. Thus, I would expect 2GB is fine.

[Lost Ninja.1809]

Did a clean boot and disabled some extra stuff (mostly motherboard .dlls (I assume as they were ASUS things)), since when I haven't crashed so I can only hope that that fixed everything. :)

 

To be pointed out that neither the logitech applet or Display Fusion were the culprit though.

[Ray Koopa.2354]

Weren't they disabled too with a "clean boot"?