Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

ZY Chang

Members
  • Posts

    53
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I went to Intel Download Center and install the first one (was told the latest one) as below and it now it's working with AF 1.9. When I installed it, the system said the one on my computer was newer than the I was trying to install. But went ahead and replaced/installed anyway. Fortunately it's now working:
  2. How did you end up with Driver 2018? Did you keep uninstalling the driver until you saw it is 2018 by itself? Or you manually installed the 2018 version? Not sure if your solution applies to my computer.
  3. Did you un-installed the Intel latest driver and let the system install available driver or un-installed it first and manually installed OEM versions instead?
  4. My search of OpenCL in driver C is as below: Can you @Mark Ingram tell which one might be faulty?
  5. I ran the cltest directly within the Win + R window. I ran it again under the shell. Here are the output: Checking for OpenCL binaries: Found Querying OpenCL platform count: OpenCL tests failed to complete! This indicates a problem with one or more OpenCL drivers on your system. There are a lot of OpneCL.dll files at various places. Which ones does the test code check? Any idea as which OpenCL driver is faulty?
  6. You may need to pipe results if any to a file like: cltest.exe > cltest_result.txt. In my piped result, it says: OpenCL tests failed to complete! This indicates a problem with one or more OpenCL drivers on your system.
  7. When I ran it nothing happened except a cmd window appeared and then disappeared. When I piped result to a file. Here is what's inside: OpenCL tests failed to complete! This indicates a problem with one or more OpenCL drivers on your system.
  8. I just ran it, it seems nothing has happened except a term/win popped up for a couple of seconds and disappeared.
  9. Thanks Simono. For the latest beta version I did not do anything (including modification of the UseHardwareAcceleration entry). It crashed the first time, but started successfully in the second time. Did you mean that your released version (1.9) is working now? It did not work for me when I added <UseHardwareAcceleration>True</UseHardwareAcceleration>.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.