Reboot.4562

Back to report my findings...So I found my root cause,but not what I thought it was.Having GW2 crash when setting textures above low was a red herring, turns out I had a stick of ram go bad. I am surprised that pcmark/3dmark and other games did not crash in my testing. Only app that found it was memtest86. Pulled the bad stick and I have not had one issue since. I highly doubt everyone has bad memory,but may be worth checking as well. Thought I was on to something with the textures,but it was all smoke and mirrors. Hopefully the other issues have solutions soon. Not that it helps main but I did not want to leave the post without an update.

Yeah its not just you!Well what ever that was updated last night or today has made my problem 100% worse. Client crashes at log in/char select screen. Even running the data repair crashes. Every crash I have sent off to Anet. Waiting on ticket reply as I am out of ideas now. When the client did work I could play 2+ hours at low no issue. bump textures to med,load into LA and had a raptor mount spawn up and crash. This machine had no problems until the end of Winter's day. Going to fully remove the game and re-install (AGAIN) and see if I can get back to just crashing when I bump textures up. Hopefully this issue can be tracked and a solution found and implemented.

I just did the same with swiching from full to window so I don't have to sign out of my desktop. I will be sending a report every time it happens. Has anyone else dropped the texture settings and have the issue go away? I am still testing this.

Just throwing this in the mix, if you're running RTSS and MSI Afterburner, disable them if dropping textures and shaders to low doesn't seem to help. Now I haven't tested this but worth bringing up as I had a CTD with Nier when an older version of RTSS was running. I think I saw an old post on reddit and made me remember this. I don't think that's the issue but worth putting the info out there. I plan on doing some deep testing tonight and will report what I find

Fyi not that it matters but I typoed my cpu. I am running an i5 7600k (kaby lake)

I agree with you on that comment. Lines up to what I am seeing when I bump textures up and crash. I fogot that I sometimes see texture corruption/swapped textures on myself and npcs before crashing. Hasn't happened since the last client update, but I am also running the game at low now. Any other game I am running is using dx11 or better and not one problem. Other than opening a ticket, is there a way to report this? I haven't gotten a response yet, and I know this is a f2p but I've bought both expansions as well as some gems here and there, so it would be nice to receive even a "we are looking into it" I really enjoy this game but it's frustrating to be crashing like this and having to run at low, when my rig can handle much better. Anyone seeing this crash try dropping your textures and shaders to low and report back. I'm going to test tonight and leave those to low and log some hours.

Put me down as in the same boat. In my case I have found dropping textures to low as well as sharers to low seems to fix the problem. I have not had the game crash since changing this(Played about 3 hours today no issues running AB meta). As soon as I bump those up to med I can sometimes go an hour or two with no crashes or crash right off the bat. Started for me around Winter's day. Another machine of mine with an older i5 and 660 card does not have this problem. I have done everything short of a full reload,but no other game,benchmark,stress test has problems,so it has to be GW2. I looked at my crash log and its the same as the other posts. I have a ticket open but no reply yet. I also found in my AppData\Roaming\Guild Wars 2\ folder a ton of "Corrupt-XXXXX.dat" files. these seem to show up after the crashes. SystemAll drivers/updates/firmware up to dateMobo RoG MaxVIII HeroI5 6700K (No over-clock currently,did have the same crashes with and without my over-clock)16 GB DDR4 2133MhzGTX 970 superclockedGW2 on SSDWin10 1709 I hope a fix is found. I will update if I hear back from Anet or figure something out