Assan122

Try this and see if it helps: Look for and open the WOT Game folder on your hard drive. Once in the game folder, look for and open the Win64 folder. Once in there, look for the World of Tanks Application/EXE file. Create a desktop shortcut using that file. I did that, and have no issues crashing it appears. Basically, it's bypassing the Wargaming Center altogether and doesn't even use it to launch the game. Hope it helps. It did for me.

Same here, but only when going through WGC. If I use the 64bit EXE shortcut I created on my desktop, it does not crash.

I usually just disable Data Protector for an hour and put it on during that time.

Thanks mate.....WG is helping me...for what it's worth..lol

Log attached. Still think it's a WG issue, but if you can just verify if possible. Aslains_WoT_Logs.zip

It just started this morning with me. Last night was fine during Advances/Skirms. I'm running WG check, repair, etc. now, and will send logs if it persists. I don't think it's mod related since I just ran vanilla with same thing....contact list won't highlight, general chat now works, but clan chat window won't even show up. It is constant.

Is anybody else having issues with the contact list not showing, general chat not connecting, and clan chat window not even showing now? I installed the latest update, and now I've got that going on. Thanks in advance

My clan chat window in garage stops connecting after I run a battle or 2. General chat and individual chat appears to work just fine. I can disconnect from the server, reconnect and it's fine for another battle or 2. This has been going on over a month now and I've sent a ticket to WG, and have gotten no positive results. They ran my account and said developers are working on it. They also said to run without mods and try it. Long story short, I've run it with Aslain's and XVM, with Aslain's and no XVM, and totally vanilla, with the same results. WG led me to believe it was the mod but I've heard there has been a similar problem with others. Wondering if anyone here has seen the same issue and maybe has a solution.