Game crashing due to memory could not be read/written.

I have had this problem for a long time now and seem to be getting worse. It's killing the joy of playing this game. The error I get is either memory could not be read or written. I play many games and none have issue's so I'm fairly sure this is related to Gw2 exclusively. I have ran memory test and every other system diagnostics available and all come out clean. Since I cannot ad the full log (too many characters) I'll post the first and last part:

--> Crash <--OOM: Heap, bytes=1048596,App: Gw2.exePid: 4068Cmdline:BaseAddr: 00400000ProgramId: 101Build: 29675When: 2014-02-14T14:28:36Z 2014-02-14T15:28:36+01:00Uptime: 0 days 2:15:06Flags: 0

--> Error Logs <--f space for new bolts.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Couldn't find missile launch point for gadget ''.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Model '0x080b24': Failed to resolve AimIK bone indices.Couldn't find missile launch point for gadget ''.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Model '0x08223a': Failed to resolve AimIK bone indices.Model '0x082239': Failed to resolve AimIK bone indices.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Couldn't find missile launch point for gadget ''.Model '0x080b24': Failed to resolve AimIK bone indices.Model '0x08223a': Failed to resolve AimIK bone indices.Model '0x082239': Failed to resolve AimIK bone indices.Model '0x08223f': Failed to resolve AimIK bone indices.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Couldn't find missile launch point for gadget ''.Model '0x08223a': Failed to resolve AimIK bone indices.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Model '0x080b24': Failed to resolve AimIK bone indices.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Model '0x080b24': Failed to resolve AimIK bone indices.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Model '0x08223f': Failed to resolve AimIK bone indices.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Model '0x080b24': Failed to resolve AimIK bone indices.Debug token '0x00000000000EB017': Lightning ran out of space for new bolts.Model '0x080b24': Failed to resolve AimIK bone indices.Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.

This last part always seem to be in the log and make me believe it has to do with Gw2. I'm not sure if it's a bug or not. I also like to point out that my system isn't on the low end . This problem seem to be consistent no matter the settings (low or ultra). I hope someone can actually help me with PoF around the corner.

Have you tried repairing your client? It looks like some of the files got corrupted.https://help.guildwars2.com/hc/en-us/articles/201863008-Repairing-the-Game-Client

I have tried this already yes. I actually repaired it a few times and did a full redownload a while back now.

You're running out of memory due to being 32-bit, which is no longer supported with PoF and this is why. If you're using Windows 7 or up, you can upgrade to 64-bit for free by either using the 64-bit version of the Windows installer or by upgrading to Windows 10, which is still available.

If you are not capable of upgrading to 64-bit, you can only try to prevent this crash. Model limit and quality should be lowest and you want to restart the game when you're planning on doing a big event, after a big event, or after an hour or two. The more stuff the game loads, the more fragmented your memory becomes and the higher your chances of crashing.

I'm in Windows 10 64-bit running the Gw2 64-bit client. My model limit is already set to low and so is the quality as I noticed it improves fps in zergs. The interesting thing is that when I monitor my memory it doesn't even go near full.

Just like to point out that I had this problem in the past and just realized you might be right and this is that nasty memory leak playing up again. It was fixed when I switched from 32 to 64 bit client. I'm currently using 8gb of memory which seemed to work just fine up until now.

well, when I play wvw, a couple of zerg battles are enough to push gw2 past 8gb of ram. I have 16, so it does not crash. What happens is worse, it slows down to a crawl...

@zarak.2314 said:I'm in Windows 10 64-bit running the Gw2 64-bit client.

Turns out the log you posted is from 2014.

Assuming a generic memory access violation, it can be caused by basically anything. Run a memory stress test to rule out failing hardware. On the software side, it'd be faster to clean install Windows.

Yea I just noticed the log is from all the way back to 2014. Here are two from recent with both error's:

--> Crash <--Exception: c0000005
Memory at address fffffda4`ce19d14b could not be writtenApp: Gw2-64.exePid: 5632Cmdline:BaseAddr: 00007FF788F00000ProgramId: 101Build: 82080Module: d3d9.dllWhen: 2017-09-14T10:39:50Z 2017-09-14T12:39:50+02:00Uptime: 0 days 0:09:16Flags: 0

--> Crash <--Exception: c0000005
Memory at address 00000000`000003cc could not be readApp: Gw2-64.exePid: 9364Cmdline: /clientport:80BaseAddr: 00007FF689BC0000ProgramId: 101Build: 81825When: 2017-09-12T19:24:59Z 2017-09-12T21:24:59+02:00Uptime: 0 days 0:03:54Flags: 0

Are you using any 3rd party programs/programs associated with your graphics cards? Those often give the d3d9.dll error.

Yes I am running sweetfx (or reshade) but I tried without it and got the same issue. The crash always seem to be the same issue with the "Debug token '0x00000000000F1059': Lightning ran out of space for new bolts.Couldn't.. etc" like listed earlier.

I like to thanks all the people trying to help me out so far. No solution yet (support or forums).

Sounds like a corrupt d3d9.dll if you get read and write errors in it (trying to read address space you are not allowed to read) usually when pointers are close to null (0x0).The best way is to try doing a complete uninstall of sweetfx (or reshade) - ie. by deleting the bin64 folder, or move it to another location, or by renaming it.This forces the client to download the files again.If this does not work either, it may work with running the redist for directx 9 again: https://www.microsoft.com/en-us/download/details.aspx?id=8109

I tried removing sweetfx/reshade before but not with deleting the bin64 folder. I will try that next and see what happens.

I removed sweetfx/reshade and deleted both bin/bin64 but the problem is still there sadly..

Any other programs, such as those that come with your graphics card? Win10 XBox programs? Things of that nature?

Can you run memtest? With what you've said I genuinely suspect that what you're describing is due to a hardware issue with your computer.

I already ran memtest took 4-5 hours and had zero errors. It's such a weird problem. The internet is full with this issue but I never seen one clear answer/fix.

@zarak.2314 said:The internet is full with this issue but I never seen one clear answer/fix.

That's because it's a generic problem and can be caused by basically anything. It'd be much faster to start with a clean install of Windows, which could be as easy as swapping in a spare drive.

Create a new Windows user account and use that. Open msconfig and disable all non-Microsoft services and all startup programs. Uninstall any security software that is still running. Check your drive for errors, including bad sectors. Open a command prompt as an administrator and run the command "sfc /scannow". Update your BIOS. Try different versions of your graphics drivers. If you have multiple GPUs, disable them. Set the compatibility for GW2 to Windows 7.

I never see reinstalling windows as an option. I'm actually having somewhat fun trying to figure out how to fix it. You gave me some suggestions that I haven't tried yet (compatibility mode, another version of gpu driver). Will see if anything helps! Cheers!

Do you run any overlay as well? That can be another reason for the crashes, as that also hooks into the dll in one way or another.

Alright it seems I have fixed the problem. It's a tiny issue that can be easily overlooked. It appears that my RAM was set to 1333mhz while it the RAM itself is 1600mhz. Now this shouldn't really cause a problem in most situations but in mine it did. Maybe my motherboard set the voltages faulty I don't know but when I changed this the problem appears to be gone. I hope this will help anyone in the future! Try everything because the things that look silly might fix your problem! Thanks to everyone trying to help!

Great that you found out and solved the issue. Never read about RAM being the issue tough. As a developer myself, it's quite good to know about :)