No, there is no existing way to save and restore V8's state at arbitrary times. Sven has already explained why it's impossible to implement one. Assuming that V8 (or a Chrome renderer process) is single-threaded doesn't help, because it *isn't* single-threaded.
But even if what you're suggesting were possible, how would it help? Chances are, if you reset a given application to a state right before it crashed, it would just crash again, because the reason for the crash is already part of the application's state.
A much more robust approach is to save relevant high-level state on the application layer, e.g. like GMail saves drafts on the server while you type.