OpenCL failed to initialize after 15 seconds!
#1
Hello all,

I’m hoping it's ok to post this here and someone much smarter than myself can help me with this issue. I’ve recently built a new rig and have been having some weird issues. Everything will run well for a long time (a few days even), and then at some point everything starts to slow down and hang up. I’ve done extensive tests on all the hardware and it has all passed, and I took it in to get it looked at at microcenter. They thought the issue was my cpu temps so we installed better cooling and it does seem to be a lot more responsive when it locks up, but it’s still happening.

When I open max I get the following OpenCL error message from Tyflow:

https://imgur.com/iitZhTZ

This message only appears when the lockups start happening. I have checked to make sure OpenCL is installed- when the program starts up I have my gpus listed in the openCL options, and I don't have any openCL.dll files in my max root folder so I am assuming it's a symptom of my system problem. It also takes an eternity to load max- yes, longer than usual Wink


I was hoping someone here could clue me into what exactly this message means because it may help me understand what could be going wrong with my system.

Much appreciated!
  Reply
#2
It means the detached thread that does the OpenCL loading never rejoined, so OpenCL never finished loading. OpenCL loads by querying the GPU, so if it doesn't load you have a GPU/driver issue.
  Reply
#3
(06-29-2020, 08:33 PM)tyFlow Wrote: It means the detached thread that does the OpenCL loading never rejoined, so OpenCL never finished loading. OpenCL loads by querying the GPU, so if it doesn't load you have a GPU/driver issue.

I can't thank you enough for this- I know it may seem simple but this helped me pinpoint the issue that's been driving me crazy for the last few weeks. Turns out I had been using the nvidia game drivers instead of the studio drivers which was giving me those crazy hangups, for some reason. Never had issues with them before but maybe system incompatibility or something. Anyways, it seems to be fixed now and I am not having any more error messages.

Cheers!
  Reply


Forum Jump: