Posted by Wade Walker on Apr 02, 2016; 5:08pm
URL: https://forum.jogamp.org/CL-DEVICE-NOT-AVAILABLE-when-creating-CLContext-with-64-bit-Java-on-GTX-970-tp4036560p4036583.html

For the DLLs, I was interested in what path they're loaded from -- if they come from a different path in the working vs. non-working version, that would be a smoking gun. Dependencies between DLLs should be automatically loaded by Windows, but if you've got a bad version of some DLL out there on your system, loading jocl.dll could cause it to load an incompatible version of some other DLL that might cause the kind of weird behavior you're seeing.

Also, another thing you can try is setting some Jogamp debug flags on the command line, and comparing the dumps of your working vs. non-working versions. Try setting

-Dnewt.debugl -Dnativewindow.debug -Djogl.debug -Djocl.debug

on your command line, and this should produce logs with tons of info in them. Then post the logs here, and I'll take a look (if you can't see any obvious difference). You might start with just

-Djocl.debug

 to see if there's something obvious, then add more if not.