Sorry that's happening. This is a really tricky issue to figure out, we're still working on it. It seems we've narrowed things down that this is potentially a graphics driver related bug, we just need now to figure out how to work around it when it comes up.
For now though, if you try the troubleshooting steps
here, you should be able to get things up and running again.