Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

OpenCL Error: Unknown error waiting for idle on GeForce GTX 1080 Ti (Device 0).

OpenCL Error: Unknown error waiting for idle on GeForce GTX 1080 Ti (Device 0).

Anonymous
Not applicable
22,307 Views
12 Replies
Message 1 of 13

OpenCL Error: Unknown error waiting for idle on GeForce GTX 1080 Ti (Device 0).

Anonymous
Not applicable

system: i7 7700k, GeForce GTX 1080 Ti  11GB , Asus Z270-A with intel Video disabled, 32GB Ram

Maya 2018 student version

when issue occurs: adjusting the position of controls on a rig.

issue Maya crashes - have to close Maya with task manager as mouse moves around in window but no click is recognized even after waiting over an hour or stalls for 5 min then can save and close, Quicktime is sometimes affected- picture freezes and can not move.

Changed drivers:one that came with m/b CD(378.78), then tried 382.33-desktop-win10-64bit-international-whql, and 385.69-desktop-win10-64bit-international-whql

, 361.75 might fix in Maya 2016 ver  according to this post -

https://forums.autodesk.com/t5/maya-forum/xgen-opencl-bug/m-p/6530237/highlight/true#M34795

- but is no longer available on nVidia website

Is anyone having this issue in 2018 version? (besides me) going by forum this was a problem 2 years ago, not seeing any related to Maya 2018 ver.

Tried with onboard intel video and 1080 card disabled- sort of. (all nVidia uninstalled- and MS generic driver active- monitors plugged into m/b). 😞 just lead to new error:

OpenCL Error: Out of device memory.
OpenCL Error: Out of resources.

 

will also try: driver 385.69 with :

Add the following line to your maya.env file:

 

MAYA_OPENCL_IGNORE_DRIVER_VERSION=1

but according to above post it does not work for all people.

 

my question: is there a quick fix for this , or can you suggest another avenue for solving the issue?

0 Likes
Accepted solutions (1)
22,308 Views
12 Replies
Replies (12)
Message 2 of 13

Anonymous
Not applicable

editing maya.env file seemed to make no difference.

 

to clarify the issue: not sure if this is totally random or not : Maya works fine for a variable amount of time, it does not always happen and seems less often if you save regularly.

 

 

0 Likes
Message 3 of 13

Anonymous
Not applicable
Accepted solution
resolved issue: was caused by not having the newest version of QuickTime 7 loading 7.7.9 solved problem.
0 Likes
Message 4 of 13

Anonymous
Not applicable

@Anonymous wrote:
resolved issue: was caused by not having the newest version of QuickTime 7 loading 7.7.9 solved problem.

Hello,

 

I'm not sure this is an issue related to Quicktime. I have the latest version and I'm still getting the crash on Maya 2018. I get this in the output window:

 

OpenCL Error: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 970 (Device 0).

OpenCL Error: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 970 (Device 0).

OpenCL Error: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 970 (Device 0).

OpenCL Error: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 970 (Device 0).

OpenCL Error: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 970 (Device 0).

OpenCL Error: CL_OUT_OF_RESOURCES error executing clFlush on GeForce GTX 970 (Device 0).

 

Is there any solution for this? Or maybe a setup we can tweak in the Settings?

 

Thanks in advance!

 

 

0 Likes
Message 5 of 13

stormstudios
Participant
Participant

I'm seeing this same error on Linux on a 1080 Ti card. We have two identical machines, with identical installs (exact same packages and configs), but have only seen the issue on one of them so far. Both are running Nvidia driver 384.90.

 

The machines have only been in use for a week or so, so it's possible that this error may be down to a faulty GPU.

0 Likes
Message 6 of 13

Anonymous
Not applicable

Hey i'm also having this issue, and i have tried updating quicktime with no result.

 

Anyone have any idea how to fix this?

0 Likes
Message 7 of 13

Anonymous
Not applicable

I have a GTX 1080 but was having the same problem. Crashing within 20mins of use or less when I clicked on a nurbs curve/animation controller. The outliner getting spammed with that message.

 

I changed a few settings, and it seems to have mitigated the crashing. These are the settings I changed in the preferences window:

 

Display -> Viewport 2.0

Rendering engine: DirectX 11 (I have a feeling this one isn't necessary, but I've kept it on)

 

Animation -> Evaluation

Uncheck "GPU Override" (this may be the critical one)

 

GPU Cache -> Hardware Information

 

Uncheck "Set All to Automatic"

 

GPU Cache -> OpenGL-Based Selection Options

OpenGL Selection Mode:

  • Uncheck "Automatic"
  • Select "Use Vertex Arrays"

 

Full disclosure, I'm not sure the full scope of what most of these options change. I more or less went through the settings and looked for anything that might use the GPU.

 

Hope that helps you or someone else.

Message 8 of 13

syrakoulisantonis
Community Visitor
Community Visitor

Thanks for the info the options you have shown in your post helped me with the open GL and the whole idle error think on my GTX 970 SC.

0 Likes
Message 9 of 13

Anonymous
Not applicable

This worked.   Thank you so much.  It's definitely not a quicktime issue... especially if you are in linux

 

Try it while leaving GPU override on because that is actually useful

 

 

Windows/Setting Preferences/Preferences/GPU Cache
 
 


GPU Cache -> Hardware Information

 

Uncheck "Set All to Automatic"

 

GPU Cache -> OpenGL-Based Selection Options

OpenGL Selection Mode:

  • Uncheck "Automatic"
  • Select "Use Vertex Arrays"
Message 10 of 13

onliiaj
Contributor
Contributor

@Anonymous @Anonymous okay i may be blind and I'm sorry for bringing back this topic but I can't find that GPU Cache? Help, I can't get 2 seconds of animation done 😞image.png

 

0 Likes
Message 12 of 13

onliiaj
Contributor
Contributor

Thank you!

0 Likes
Message 13 of 13

nightrue
Observer
Observer

Thank you! That seems to have cleared up the problem for me!

Nvidia 1080 

 

0 Likes