Try to rename (it is safer to rename instead of deleting) “C:\Users\(USER_NAME_HERE)\Documents\maya” and restore Maya back to the factory settings. Open Maya, let it rebuild, close it. Open it again, and import your troubled file.
If that fails, why don’t you try a re-install just to make sure it’s not a software corruption.
If all else fails you can upload the file here, or give it to a friend, and have them try it on a different machine. There is an off chance the problem is related to hardware or drivers. I save this step for last because you are giving access to potentially valuable file to strangers.
This is an alembic integration bug. Don’t know if it has been fixed in 2013 - someone should give it a try.
What happens is that for some reason, the moment an alembic cache is moved or renamed, maya crashes when the alembic node is trying to read an inexistent file. In theory, it should throw an error saying that it cannot find the file, but insted, it simply crashes.
There are two ways around it, and only one viable in your situation.
1) From now on, get used to saving in the ascii format, because it is in situations like these, that you will understand the huge benefit of being able to open the file in a text editor, and fixing the part of it that causes the crash. But since you are using .mb, there’s only step 2 left
2) Try to remember the name and the location of the cache, and create a new abc with the EXACT name in that EXACT location of the one you deleted. Now you will be able to open the file, and get rid of the alembic nodes that cause the problem.
Otherwise, you’re pretty much screwed.