Unity crashes with Access Violation

I don't believe you can make use of that information in a helpful way. If you can, I certainly haven't discovered how to do so.

Is the address the same each time? I would be surprised... I actually asked a similar question very recently and never got a response. In my case, I have a suspicion that the OS throttled the maximum memory allocated to the game and the error was a result of some memory-intensive operation or combination of operations.

Luckily for you, you mentioned identifying a specific action which brings about this crash, right? That gives you a place to start looking. Trace your logic (use debug mode, debug statements, break points, the profiler, whatever you can) to identify what's causing the problem.

See also: http://blogs.msdn.com/b/jasone/archive/2014/11/12/what-is-an-access-violation.aspx

I feel like out-of-memory is it's own specific error. An access violation is more like a NullReferenceException. Are you using unmanaged code, or a .dll? I'm not sure how vanilla C# can even get an Access violation.