Pingulicious.8270 Posted October 8, 2018 Share Posted October 8, 2018 Hey, Since the patch I've started to experience regular crashes after arpox. 5-15 minutes of gameplay. They behave rather strange however - the game continues to run while the "Crash report dialog box" opens up. If I don't internact with the dialog box, the game continues to run (I get credit from events after the dialog box appears). New boxes open up however, overlaping the previous one. In the end I ususally just quit. Crash report mentions unable to write memory (I intended to post the log, it seems it didnt copy however). Anyone else experience this? Link to comment Share on other sites More sharing options...
TheQuickFox.3826 Posted October 8, 2018 Share Posted October 8, 2018 I hardly ever have crashes here, but when the game is unable to write to it's memory, it will be unpredictable if you continue to run it. Generally, crashes like these are not caused by bad memory but by game bugs, add-on bugs or driver problems. I would first disable any add-ons if you use them, [checkdisk the drive](https://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/ "checkdisk the drive") where you installed the game, then try a [client repair](https://help.guildwars2.com/hc/en-us/articles/201863008-Repairing-the-Game-Client "client repair"), then try to update your graphics driver (if available), and if nothing helped: Try a [memory check](https://technet.microsoft.com/en-us/library/ff700221.aspx "memory check"). Link to comment Share on other sites More sharing options...
Pingulicious.8270 Posted October 8, 2018 Author Share Posted October 8, 2018 Tried to reinstall the game, got a crash still. Though I noted I dont have the latest graphics card driver, so I will try with that. Copy paste from the first part of crash report: *--> Crash <--* Exception: c0000005 Memory at address 00000000`000be33f could not be written App: Gw2-64.exe Pid: 2840 Cmdline: -allowInstall BaseAddr: 00007FF66E060000 ProgramId: 101 Build: 92773 When: 2018-10-08T12:30:54Z 2018-10-08T14:30:54+02:00 Uptime: 0 days 3:36:42 Flags: 0 Link to comment Share on other sites More sharing options...
TheQuickFox.3826 Posted October 8, 2018 Share Posted October 8, 2018 And did you do the disk check and memory check? You will have to verify first if your computer is running stable. Link to comment Share on other sites More sharing options...
Pingulicious.8270 Posted October 8, 2018 Author Share Posted October 8, 2018 Yeah, I ran both, neither found any errors. Link to comment Share on other sites More sharing options...
Healix.5819 Posted October 8, 2018 Share Posted October 8, 2018 c0000005 means GW2 tried to use a section of memory it wasn't allowed to. It could be caused by anything listed under the DLL list of the crash log, or anything else that is interacting with GW2's memory access. Also, the log says you're running GW2 with the -allowInstall option, which is something that should only be there if you're running Gw2Setup. Link to comment Share on other sites More sharing options...
Pingulicious.8270 Posted October 8, 2018 Author Share Posted October 8, 2018 Well arent I lucky, now I got two in a row.With different exceptions: *--> Crash <--* Exception: c000001d App: Gw2-64.exe Pid: 8004 Cmdline: BaseAddr: 00007FF6FEF10000 ProgramId: 101 Build: 92773 When: 2018-10-08T19:16:27Z 2018-10-08T21:16:27+02:00 Uptime: 0 days 0:04:23 Flags: 0 Followed by *--> Crash <--* Exception: c0000005 Memory at address 00000000`0016cdd3 could not be written App: Gw2-64.exe Pid: 8004 Cmdline: BaseAddr: 00007FF6FEF10000 ProgramId: 101 Build: 92773 When: 2018-10-08T19:16:39Z 2018-10-08T21:16:39+02:00 Uptime: 0 days 0:04:35 Flags: 0 Any ideas? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now