Page 1 of 1

Win 10, ATI R7 not working

Posted: Tue Jan 08, 2019 9:56 pm
by sergiopa
Here is the log.

What should i do?

Code: Select all

C:\Users\Sergio\AppData\Roaming\FAHClient>fahclient
21:48:20:INFO(1):Read GPUs.txt
21:48:20:************************* Folding@home Client *************************
21:48:20:      Website: https://foldingathome.org/
21:48:20:    Copyright: (c) 2009-2018 foldingathome.org
21:48:20:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
21:48:20:         Args:
21:48:20:       Config: <none>
21:48:20:******************************** Build ********************************
21:48:20:      Version: 7.5.1
21:48:20:         Date: May 11 2018
21:48:20:         Time: 13:06:32
21:48:20:   Repository: Git
21:48:20:     Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
21:48:20:       Branch: master
21:48:20:     Compiler: Visual C++ 2008
21:48:20:      Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
21:48:20:     Platform: win32 10
21:48:20:         Bits: 32
21:48:20:         Mode: Release
21:48:20:******************************* System ********************************
21:48:20:          CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
21:48:20:       CPU ID: GenuineIntel Family 6 Model 158 Stepping 9
21:48:20:         CPUs: 8
21:48:20:       Memory: 15.94GiB
21:48:20:  Free Memory: 13.31GiB
21:48:20:      Threads: WINDOWS_THREADS
21:48:20:   OS Version: 6.2
21:48:20:  Has Battery: false
21:48:20:   On Battery: false
21:48:20:   UTC Offset: -2
21:48:20:          PID: 10172
21:48:20:          CWD: C:\Users\Sergio\AppData\Roaming\FAHClient
21:48:20:           OS: Windows 10 Enterprise
21:48:20:      OS Arch: AMD64
21:48:20:         GPUs: 1
21:48:20:        GPU 0: Bus:1 Slot:0 Func:0 AMD:5 Hawaii [Radeon R7 200 Series]
21:48:20:         CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': Não
21:48:20:               foi possível encontrar o módulo especificado.
21:48:20:
21:48:20:       OpenCL: Not detected: Win32: 0xc0000005: Exception access violation
21:48:20:Win32 Service: false
21:48:20:***********************************************************************
21:48:20:<config>
21:48:20:  <!-- Folding Slots -->
21:48:20:</config>
21:48:20:Trying to access database...
21:48:20:Successfully acquired database lock
21:48:20:Enabled folding slot 00: PAUSED cpu:6 (not configured)

Re: Win 10, ATI R7 not working

Posted: Wed Jan 09, 2019 1:20 pm
by JimboPalmer
Welcome to the F@H Support forum, I hope your day gets better!

You have a R7 2x0 with the Hawaii architecture (Graphics Core next, gen 2) https://en.wikipedia.org/wiki/Graphics_ ... generation
That is a supported GPU that should be able to fold if the driver came from AMD, not Microsoft. MS does not include OpenCL, and your log indicates it is missing: OpenCL: Not detected

AMD makes it hard to link to the download, here is as close as I can get:
https://www.amd.com/en/support/graphics ... eon-r7-260

Re: Win 10, ATI R7 not working

Posted: Wed Jan 09, 2019 3:05 pm
by sergiopa
Ok, but i wnat to use my CPU, not the GPU.

What should i do?

Re: Win 10, ATI R7 not working

Posted: Wed Jan 09, 2019 4:06 pm
by ProDigit
CPU folding is not very effective.
About 10x less efficient than mid range graphics cards, and about 100x less efficient than top tier graphics cards.
If you only want to fold from CPU, remove the GPU slot in fah control settings, or fold from the native client from a chrome browser:
http://nacl.foldingathome.org

Re: Win 10, ATI R7 not working

Posted: Wed Jan 09, 2019 5:11 pm
by bruce
The fundamental problem is something that happened during the installation. Ordinarily, the installation script asks you what name/team/passkey you want to use and then it completes the installation process. Obviously that didn't happen.
21:48:20:<config>
21:48:20: <!-- Folding Slots -->
21:48:20:</config>
21:48:20:Trying to access database...
21:48:20:Successfully acquired database lock
21:48:20:Enabled folding slot 00: PAUSED cpu:6 (not configured)
I'm not sure how you did that but if you remember, let us know so we can help others avoid doing the same thing.

Second: FAHClient is designed to run either as a Windows service (for CPU folding, only) or as something very much like a Windows service (which can also fold on a GPU). Either way, you can manage the client with FAHControl or with Webcontrol.

While I can give you instructions on how to fix this problem, the simplest option is to re-install -- and if you really do not want to use your GPU, choose to install as a service. If you later decide you want to use your GPU, download the drivers from AMD/Ati per JimboPalmer's instructions above and reinstall again.

Re: Win 10, ATI R7 not working

Posted: Thu Jan 10, 2019 9:44 pm
by sergiopa
Ok Guys


I did a cleanup on amd drivers(with amd unistall tool ) and installed the most recent from amd website

but still i got OpenCL not detected.

what should i do?

Re: Win 10, ATI R7 not working

Posted: Thu Jan 10, 2019 11:38 pm
by bruce
Well, apparently they're no longer packaging OpenCL with their graphics drivers. Try https://www.amd.com/en-us/solutions/pro ... hpc/opencl

Re: Win 10, ATI R7 not working

Posted: Mon Apr 22, 2019 9:54 pm
by Athlonite
Your using the Windows Update installed driver more often than not the Windows Update installed versions do not come with OpenCl drivers included as it's just a basic AMD Catalyst or Adrenalin driver

What you need to do is grab the driver from AMD themselves from here https://www.amd.com/en/support

install it restart windows and restart F@H

Re: Win 10, ATI R7 not working

Posted: Mon Apr 22, 2019 10:04 pm
by JimboPalmer
The OpenCL driver should only be used for GPU folding, so it may be a red herring.

Re: Win 10, ATI R7 not working

Posted: Mon Apr 06, 2020 12:46 pm
by HyMa
Hi, i've similar problem with my GPU, it seems its recognized by client, but no jobs for it? GPU is AMD Radeon R7 350X :(

Re: Win 10, ATI R7 not working

Posted: Tue Apr 07, 2020 1:50 am
by PantherX
Welcome to the F@H Forum HyMa,

Can you please post your log file. Ensure that you have copied the System configuration which is present at the start of the log file (viewtopic.php?f=2&t=26036). Once we have that information, we will be better able to help you out :)