Crashing due to a "Invalid Character Motion"?

#1 - Aug. 13, 2014, 10:33 a.m.
Blizzard Post

I recently had to downgrade from my Radeon 7950 to my Radeon 5750 due to a VRAM failure. I dunno if that’s relevant or not, but I started experiencing my game crashing since then and it’s happening in faster and faster intervals now:

—> Crash <—
Assertion: CharMotion has invalid matrix
File: ..\..\..\Game\AgentView\AvCharMotion.cpp(237)
App: Gw2.exe
Pid: 11016
Cmdline: -repair
BaseAddr: 00020000
ProgramId: 101
Build: 37444
When: 2014-08-13T15:22:02Z 2014-08-13T11:22:02-04:00
Uptime: 0 days 0:52:45
Flags: 0

I already ran GW2 repair thinking that the “File:…” was a dead giveaway on it just telling me a file got corrupted so I went ahead and followed/ran the GW2 Repair the forums taught to make along with checking my 5750’s drivers just to make sure, and neither have solved the issue. Is this a common occurrence with a simple fix or is there something more to this?

#24 - Aug. 15, 2014, 1:46 p.m.
Blizzard Post

For all of you experiencing this issue, can you please post your crash logs as an attachment to the thread (click “More postinhg & formatting options…”) in addition to the following:

- Is this happening in specific areas or during certain instances in the game?

- System info: CPU, GPU, OS, and RAM

Your crash logs should be located in your appdata Roaming folder and you’ll want to find the ArenaNet.log file. The same log file should also be generated when you crash and clicking “Show details” on the prompt to send the report to us should show you the full report.

The more information that I’m able to gather the better idea we’ll have in regards to this particular error.

Thanks for your patience everyone and sorry for any frustration that this may have caused!

#76 - Aug. 18, 2014, 2:51 p.m.
Blizzard Post

We really appreciate the reports — you’ve provided very helpful information in the specs and log files that you’ve posted.

We hope to have information on this in the next few days. If you’re having this issue, please be sure to include the Error Code that you received when you crashed. (If you’re adding an error code and cannot edit your post, please mention that you previously provided system specs and a game log in this thread, so we can sort of merge the info.

Thank you for your help.

#85 - Aug. 19, 2014, 11:01 a.m.
Blizzard Post

I’m not seeing any commonalities here in regards to any specific system builds or areas in the game and so it’s possible this could just be a generic crash error that’s showing up in reports. At this time could anyone still experiencing this issue submit a support ticket so that we can better assist you one on one? This will give us a better idea in regards to the issue at hand here.
https://help.guildwars2.com/anonymous_requests/new

Thanks again for your patience!

#103 - Aug. 21, 2014, 6:13 p.m.
Blizzard Post

You shouldn’t be seeing this crash any more.

#113 - Aug. 25, 2014, 12:41 p.m.
Blizzard Post

You shouldn’t be seeing this crash any more.

Im still getting this crash, i even tried repairing my game but it hasnt made a difference :/

If you are still getting this crash you were probably in the old build (37,556). As of the build that went out on the 21st (37,900) we have received 0 crash reports in regards to this error.