Hi all,

I recently added a spare NVidia NVS 510 to my main computer to crunch out some extra data for Seti and others. I do already have an AMD R9 390, so mixing the 2 has proven interesting.

Currently on the NVidia card I am getting cuda42 and cuda50 jobs, both seem to take around an hour to complete. Seemed a bit slow to me, so I started investigating. According to GPU-Z, OpenCL is disabled or not present on the NVS 510, it should be. When it was in a stand-alone PC OpenCL showed up in GPU-Z.

So, two questions.
1. Is the 1hr mark for cuda42 and cuda50 seem fair on a NVS 510?
2. Is not having OpenCL limiting the jobs I can run? Am I missing out on SoG or NVidiaOpenCL?

Thanks :)

A quick thought - the AMD & nVidia versions of OpenCL might be having a fight (to your determent) - have you tried just the NVS510 in that PC to make sure it does get identified properly.

Also make sure that you don not let Windows install the nVidia drivers as they are often missing vital bits.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Hey,

I haven't tried it solo in this PC, but others yes.

I did make sure I installed the latest drivers from the NVidia website as well. I am able to locate the nvopencl.dll files in wow64 as well, so I can assume it was installed. Thanks.

The correct file used is opencl.dll, no other. It'll be in C:\Windows\system32\ or in C:\Windows\SysWow64\, depending on Windows bitness.

Windows 10 comes with a default opencl.dll file, one that will be overwritten by the GPU drivers. Having two different GPU brands, you may have to try the driver installation sequence, to see which works on your system. Other people on here have said that it's best to install the Nvidia drivers first, AMD drivers second, but YMMV.

---

The correct file used is opencl.dll, no other. It'll be in C:\Windows\system32\ or in C:\Windows\SysWow64\, depending on Windows bitness.

Windows 10 comes with a default opencl.dll file, one that will be overwritten by the GPU drivers. Having two different GPU brands, you may have to try the driver installation sequence, to see which works on your system. Other people on here have said that it's best to install the Nvidia drivers first, AMD drivers second, but YMMV.

I do see opencl.dll in both system32 and wow64, unsure who is the owner; AMD or NVidia.

I will try a driver wipe, and install the NVidia ones first.

Thanks.

The correct file used is opencl.dll, no other. It'll be in C:\Windows\system32\ or in C:\Windows\SysWow64\, depending on Windows bitness.

Windows 10 comes with a default opencl.dll file, one that will be overwritten by the GPU drivers. Having two different GPU brands, you may have to try the driver installation sequence, to see which works on your system. Other people on here have said that it's best to install the Nvidia drivers first, AMD drivers second, but YMMV.

Cheers. Removing all drivers and using a spare monitor on the 510 during install worked. I now have opencl 1.2 on the 510. Not sure if I'll get other jobs, but it's nice to know!