RAB.7682

More crash:

Some other crashes with the same symptom and exception, but different memory addresses:

All those updates and patches on 4-10-18, but you still haven't fixed this issue yet????? --> Crash <--Exception: c0000005 Memory at address 00000000`00000008 could not be readApp: Gw2-64.exePid: 79Cmdline: -maploadinfoBaseAddr: 0000000140000000ProgramId: 101Build: 87900When: 2018-04-11T13:09:38Z 2018-04-11T09:09:38-04:00Uptime: 0 days 0:26:26Flags: 0

I have gathered some more crash reports here:

Some more crash reports:

I run into the same issue and have been getting these freezes since last year at the same time of your original post. Only thing that I have found that seems to work 100% of the time is don't run the game windowed with a defined resolution. It seems setting it to full screen windowed vs full screened windowed xxxx-xxxx seems to prevent the crash. For a test I ran 30 days with it set one way and 30 days the other and had 0 freezes during the time without a defined resolution but when switching it back went back to crashes and freezes. This is without changing anything else of the PC to try and keep it apples to apples. Not sure what settings you are using but if you are running it with a defined resolution, try that and see if that works for you. Good gaming! I shouldn't have to do a workaround, the game should work properly in all modes.Also I tried this suggestion and the game still crashes.

Awesomium crashed often too, I can't see how it was any better.

Is Anet still looking into this issue, or have they forgotten about it?

Checking in to see if there has been any updates.

I updated the topic title to: "--> Crash <-- Exception: c0000005"which was previously:"Debug token '0x00000000000266FA': Lightning ran out of space for new bolts. Coherent host process crash"If this title is not any more fitting, an admin is welcome to change the title to something proper. Also I would like to thank ArenaNet and the forum members for their responses.

So this issue has been affecting people since launch, and no one has managed to track down its root cause and fix it yet? Or, it's a coding term that applies to many, many different aspects of the game. Just as the term 'bones' and 'orphan' don't specifically refer to bones or orphans in-game.OK, thank you for clearing up your post.

Also maybe worth noting: I see in reading other people's post, that many of the people that receive this crash, are unable to obtain crash information for this report, either due to their PC locking up, or more so their lack of technical skills. To a novice, the game may appear to have locked up the entire computer, however background processes still continue to run, so only the game has locked up. While I am unable to tab out or close the game normally, I am however able to SSH into my computer from my Android and use command-line to regain control over the PC, either by killing the Gw2 process, or using the "reboot" command, which is a much preferable way to reset the PC vs using a hard power reset, which doesn't allow files to properly close on the system, and can result in orphaned file stubs.

So this issue has been affecting people since launch, and no one has managed to track down its root cause and fix it yet?

I do not run MalwareBytes.

I found this thread with other's experiencing the same symptoms and crash errors. https://en-forum.guildwars2.com/discussion/15804/extremely-frustrating-freezes-and-crashing