Maya 2017 "Fatal Error. Attempting to save in [temp folder]"

Maya 2017 "Fatal Error. Attempting to save in [temp folder]"

nathanbells
Explorer Explorer
9,579 Views
8 Replies
Message 1 of 9

Maya 2017 "Fatal Error. Attempting to save in [temp folder]"

nathanbells
Explorer
Explorer

I get this error after working on my scene for a few minutes (usually happens right after I select my rig's controllers). 

I've used Maya 2016 and 2015 without this issue but I've been using 2017 for 2 days and this error started today.

I've updated my graphics card driver.

 

Any ideas?

9,580 Views
8 Replies
Replies (8)
Message 2 of 9

matthew.d
Alumni
Alumni

Hi @nathanbells,

 

Welcome to the community!

Apologies for the fatal error message. Could you give us more information about your setup? What graphics card are you using, do you have more then one card? Are you running a Scalable Link Interface (SLI)? Could you please try re-installing your graphics driver and select "clean install" in the options.  In your Hypershade close out the material viewer to ease up on the VP2 display? Are you running update 2 for Maya 2017?



Matt DiMichele
Autodesk Product Blogs | @ADSKCommunity Twitter

Likes are greatly appreciated. Everyone enjoys a thumbs up!

Please Accept As Solution if this resolves your issue, to help others benefit and locate it.
0 Likes
Message 3 of 9

nathanbells
Explorer
Explorer

GeForce GTX 960 Driver 378.92 (just completed clean reinstall)

Just the 1 card. I'm not sure what a SLI is but I'm pretty sure I'm not running one...

I just installed update 3 (I skipped 1 & 2) for Maya 2017

 

Unfortunately I don't know a quick way to trigger the error. I just have to start animating and it usually happens in a few minutes

 

 

0 Likes
Message 4 of 9

Anonymous
Not applicable

I have the same issue, but can reproduce the error quite frequently.

 

Maya 2017, single GTX980TI, 378.92 driver

 

it happens when I add ( I can smell the respone here) a fumefx node, which simply triggers a temp save. 

0 Likes
Message 5 of 9

Cody1712
Community Visitor
Community Visitor

Hi that VIdeo helped me solving the error https://www.youtube.com/watch?v=tH5ohNTymxQ

0 Likes
Message 6 of 9

Anonymous
Not applicable

It took me a while to figure this one out, and it's a different solution in every case.

What you have to do is look for the maya crash report log in your system temp folder (or wherever maya drops those logs), and look for the fault adress, module or file. In my case it was a techsmith camtasia codec that was f*cking stuff up. Completely unrelated to anything.

Once you fix the source, everything works fine. (fumefx node was crashing the app in my case).

 

Here's the fault line from my log:

 

Exception code: C0000005: ACCESS_VIOLATION - illegal read at address 0x8636E670
Fault address: D15522FE in C:\Windows\SysWOW64\tsc2_codec64.dll
0001:000012FE Logical offset (see .map file for location)

 

Good luck.

 

 

0 Likes
Message 7 of 9

c_g_wyatt
Community Visitor
Community Visitor

Hi all, 

 

I am also getting this error too. It  only started happening once I changed the driver for my Arnold AOV's from the default <exr> to .exr.

I was doing this as merge AOV's was not working. This crashed Maya and now it will not open and the errors I am getting are:

 

Fatal Error. Attempting to save in C:/Users/Chris/AppData/Local/Temp/Chris.20180319.1311.ma

 

I was also running camtasia studio recording at the time if that has anything to do with it.

 

I will try the error log search to try and find the problem but any advice would be welcome.

 

thanks

 

chris

0 Likes
Message 8 of 9

c_g_wyatt
Community Visitor
Community Visitor

Hi All,

 

I have followed the suggestions form OKTO (Thanks Okto) and I have found my error:

 

Exception code: C0000005: ACCESS_VIOLATION - illegal read at address 0x00000020
Fault address: 66D5B404 in C:\Program Files\Autodesk\Maya2017\bin\Qt5Core.dll
0001:001AA404 Logical offset (see .map file for location)

 

Now I have located this file can anyone assist me in fixing the problem?

 

thanks

 

chris

0 Likes
Message 9 of 9

Anonymous
Not applicable

I have exactly the same issue and crash dump has the same "access_violation" code in it. I had a similar problem with zBrush Core, in that scenario a windows update corrupted the licencing file. A full re-install ''should'' fix, will confirm shortly 🙂

0 Likes