Send a Tell, Receive a Crash - EVERY time.

Well, this is new as of about an hour ago. Been sending and receiving tells fine all night. Now all of a sudden, after the last quit to select ONCE AGAIN dumped me to login instead, the second I send a tell on any character, I get to enjoy a crash.
Correction: on ALMOST all of my characters. So far I've found two that don't crash. Of course, it's loads of fun to test when 9 out of 10 times "Character Select" takes me to Login. And doesn't change the fact that most of them are insta-crash thus making them unplayable.

Yes. The game crashes. When I send a tell.

Besides the fact that this obviously is absolutely ridiculous, that's the long and short of it. Repair tool? Nothing wrong. Firewall? Well I might agree if, you know, I wasn't able to log in or it was globals or it was local/broadcast/etc. But it's not. It is, to wit, send a tell, receive a crash. Period. Added bonus, I'm not logging anything, so it's not some hung file handle. Bad enough this insultingly awful NCsoft "Launcher" is continually chucking bad parameters at cityofheroes.exe AND I can't launch it directly for no legitimate reason other than to make us suffer. But how the hell am I supposed to play when I can't send a tell to anyone?

CoH Helper and HijackThis logs pls.

There's also the possibility that your connection has gone bad for some reason or there's a bug in chat following maintenance.

Also, try verifying your files. Just in case one is corrupted.

Clicking on the linked image above will take you off the City of Heroes site. However, the guides will be linked back here.

Character Select's always been an issue. It seems only to work when there's fewer people logged in, and there's still a good chance the login server doesn't respond in time. Which is why you get kicked to the login screen.

There is an option to create a shortcut to City of Heros. Right click and that should bring up the context menu.

And another, in the NCSoft Launcher's File - Settings menu, to close the launcher so that it doesn't eat up memory while resident. There's a memory leak.

Other than that, it could be server-side corruption of the character database entries for your characters. In which case, I hope that the developers/customer service have the tools to repair individual characters.

This information is irrelevant and pointless. If it were any of these things, I would A) not have a CLIENT crash which popped up crash dump, B) it would affect ALL characters, whereas it does not. Only MOST characters.

This is a server-side problem. I have opened a support request. Support has now gone through FIVE different people, who have all confirmed that there is NOTHING wrong with my system, but have refused to examine submitted crash reports which contain the ticket identifier, have NOT properly escalated the ticket as evidenced by it bouncing between pointless canned answers like "disable all your startup programs including antivirus" - bad advice any way you slice it - and "try safe mode."

This is clearly a server side issue, specific to the affected characters. This is clearly something that needs to be addressed by somebody at NCsoft who comprehends troubleshooting and doesn't think that means "cut and paste." Somebody who is going to actually do their job. Frankly, if developers have time to hang around in Pocket D as a seagull, they certainly have time to look at crash reports that should've been forwarded to them.

Are you logging tells? Maybe some sort of chat log buffer overflow?

Edit: And the seagull was Zwillinger. He isn't tech support.