TLDR: Cause- Character being relocated (usually to Orison) after a character repair or 30K black screen. Fix - Wait until your character is no longer shard-locked, change regions until you spawn in bed. Notes - Region is not the problem, it's the particular shard you're connecting to, so you might have to try the same region multiple times. Don't give up after trying each region once. - Remember, once you break through this error by spawning in a 'good shard', you're good to go back to any server region you like UPDATE : As far as I'm aware the hottfix build 4.0.0-live-9490545 for the 4.0 Preview fixed the Orison CTD issue. If you still run in to the problem(hope not), you're still welcome to try this out. I ran to the good old EXCEPTION_ACCESS_VIOLATION (0xC0000005) a couple of weeks ago on the 4.0 Preview. It was my understanding that it is a common issue related to hardware. I tried the workarounds/fixes posted on Spectrum with no luck. I tried one workaround at a time to rule out the culprit. The only thing I did not do is changing server regions. I finally tried waiting until my character is no longer active in PU, and selecting a different server region. Voilà! I spawned in. I've come across many people who had the same issue in the #helpdesk-volunteers channel. I've been asking them the lead up to this event and helping them to get out of it, and this workaround seem to work for many of them. It is my understanding that this error can happen when your character get relocated to Orison after a character repair or a 30K black screen. Perhaps the particular servers have some entities at Orison that can cause these memory issues. So, if your game worked just fine beforehand, and you start seeing the CTD with 3221225477, perhaps try changing server regions first. You will have to wait till your avatar is no longer active in the PU.