Maya 2016 - Fatal Error loading scene

[Anonymous]

Hi there, I currently creating two models for a university project both in Maya 2016. Each save of the scenes will not open on my home computer in Maya 2016, instead it is giving me a fatal error then tries to save it in temp folder but then says it couldn't. 

The scenes load in Maya 2017, however they are very bugged out and I cannot use them. 

The scenes load fine on the computers I use in university and the lecturer has suggested that I save them in both a .ma file and a .mb file but neither are working on my home computer.

The crash report quotes this ( I have attached the full report too ) : 

"Exception code: C0000005: ACCESS_VIOLATION - illegal write at address 0x18068F0C
Fault address: 5D0A037D in C:\Program Files\Autodesk\Maya2016\bin\PolyEngine.dll
0001:001AF37D Logical offset (see .map file for location)"

 This is also what appears when I try to load it.

Please let me know if you would like anymore information. 

I want to thank you in advance for any help, This is currently stressing me out as I cannot do any work at home. 

[elliotgascoigne]

Hello!

I've had this problem before, I pulled my hair out for weeks trying to work out what was going on but I didn't have sufficient knowladge to decode the crash log.

But  did find a solution to my issue so hopefully this can translate in the hope of assisting you in yours.

My fatal errors seemed to occur after optimizing the scene then saving it out.

There are various different things you could try. The one that I think might work is if you open a new scene and then import your scene file instead of trying to open it.

The worse answer I can give you is the classic 'do you have any increment saves that you can open' but I know this isn't always the case. But if you do you can back track to different version of your scene to try and find whats causing your issue.

Another thing you can try is if you download 2017 at home because your a student you can get the free student version of Maya 2017, try opening your scene file, if this works then it could be a conflict in versions. As opening a scene file that was made in 2016 to 2017 is easy. But opening a scene file from 2017 in 2016 is a very bad idea, the tools are set up differently and cause major problems, its not very backwards compatible from my experience.

Try these options and let me know how it goes!

I hope this helps, if not we will find a solution!