Guru3D.com Forums

Go Back   Guru3D.com Forums > General Chat > Folding@Home - Join Team Guru3D !
Folding@Home - Join Team Guru3D ! Please join the Folding@Home Research Program, join team Guru3D. Let's rank the charts high and fight disease !


Reply
 
Thread Tools Display Modes
Guide For GPU3 BETA Client {Windows & Linux}
Old
  (#1)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Arrow Guide For GPU3 BETA Client {Windows & Linux} - 05-27-2010, 20:47 | posts: 1,205

The most up-to-date guide will be available here.
Quote:
  • Officially Supported Operating Systems

Windows XP/Vista/7 (32 bit & 64 bit)
Quote:
  • UNOFFICIALLY Supported Operating System

Linux (32 bit & 64 bit)

Step-by-Step Installation: <Click>

Quick Wrapper Installation: <Click>

WIKI: <Click>

GPU3 (FahCore_15) & Linux discussion Thread: <Click>

Nvidia GPU3 Linux/Wine Headless Install Guide Thread: <Click>


THIS IS UNSUPPORTED BY STANDFORD AS OFFICIALLY THERE ISN'T A LINUX GPU CLIENT YET. SUPPORT IS PROVIDED BY 3RD PARTY, NOT STANDFORD.
Quote:
Legend:
Red Text -> Specifically For AMD/ATI GPUs
Green Text -> Specifically For Nvidia GPUs
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Supported Hardware
This is a brief list of commonly used GPUs running GPU3 BETA Client:

AMD/ATI GPUs:
Radeon HD 6000 Series
Radeon HD 5000 Series (ATI_R800)
Mobility Radeon HD 5000 Series (ATI_R800)
Radeon HD 4000 Series (ATI_R700)
Mobility Radeon HD 4000 Series (ATI_R700)
Radeon HD 3000 Series (ATI_R600)
Mobility Radeon HD 3000 Series (ATI_R600)
Radeon HD 2000 Series (ATI_R520)
Mobility Radeon HD 2000 Series (ATI_R520)


Nvidia GPUs:
GeForce 500 Series (Fermi GPU)
GeForce 400 Series (Fermi GPU)
GeForce 400M Series (Fermi GPU)
GeForce 300 Series (Non-Fermi GPU)
GeForce 300M Series (Non-Fermi GPU)
GeForce 200 Series (Non-Fermi GPU)
GeForce 200M Series (Non-Fermi GPU)
GeForce 100 Series (Non-Fermi GPU)
GeForce 100M Series (Non-Fermi GPU)
GeForce 9 Series (Non-Fermi GPU)
GeForce 9M Series (Non-Fermi GPU)
GeForce 8 Series (Non-Fermi GPU) {Read Note 5}
GeForce 8M Series (Non-Fermi GPU)



The GPU3 BETA Client identifies the GPU type and reports it in the FAHlog like this "Gpu type=X species=Y." Below is the list of what your FAHlog would show depending on the GPU Type and the Driver installed:

Gpu type=1 species=1. -> "Gpu type=1" indicates an ATI GPU; "species=1" means ATI_R520.

Gpu type=1 species=2. -> "Gpu type=1" indicates an ATI GPU; "species=2" means ATI_R600.

Gpu type=1 species=3. -> "Gpu type=1" indicates an ATI GPU; "species=3" means ATI_R700.

Gpu type=1 species=4. -> "Gpu type=1" indicates an ATI GPU; "species=4" means ATI_R800.



The GPU detection messages below is specific to v6.3X of the GPU3 Beta Client:
Quote:
Originally Posted by v6.3X
The GPU3 BETA Client identifies the GPU type and reports it in the FAHlog like this "Gpu type=X species=Y." For Nvidia GPUs, the "species=Y" is based on the CUDA runtime file found. Below is the list of what your FAHlog would show depending on the GPU Type and the Driver installed:

Gpu type=2 species=0. -> "Gpu type=2" indicates a Nvidia Non-Fermi GPU; "species=0" means CUDA 2.1 or earlier. It can also mean that no CUDA runtime file found.

Gpu type=2 species=22. -> "Gpu type=2" indicates a Nvidia Non-Fermi GPU; "species=22" means CUDA 2.2 is available.

Gpu type=2 species=23. -> "Gpu type=2" indicates a Nvidia Non-Fermi GPU; "species=23" means CUDA 2.3 is available.

Gpu type=2 species=30. -> "Gpu type=2" indicates a Nvidia Non-Fermi GPU; "species=30" means CUDA 3.0 is available.

Gpu type=3 species=0. -> "Gpu type=3" indicates a Nvidia Fermi GPU; "species=0" means CUDA 2.1 or earlier. It can also mean that no CUDA runtime file found.

Gpu type=3 species=22. -> "Gpu type=3" indicates a Nvidia Fermi GPU; "species=22" means CUDA 2.2 is available.

Gpu type=3 species=23. -> "Gpu type=3" indicates a Nvidia Fermi GPU; "species=23" means CUDA 2.3 is available.

Gpu type=3 species=30. -> "Gpu type=3" indicates a Nvidia Fermi GPU; "species=30" means CUDA 3.0 is available.

The GPU detection messages below is specific to v6.4X of the GPU3 Beta Client:
Quote:
Originally Posted by v6.4X
The GPU3 BETA Client identifies the GPU type and reports it in the FAHlog like this "Gpu type=X species=Y." For Nvidia GPUs, the "species=Y" is based on the compute capability of the installed GPU. Below is the list of what your FAHlog would show depending on the GPU Type and the Driver installed:

Gpu type=2 species=0. -> "Gpu type=2" indicates a Non-Fermi GPU; "species=0" means unknown compute capability

Gpu type=2 species=10. -> "Gpu type=2" indicates a Non-Fermi GPU; "species=10" means compute capability 1.0 is available {Read Note 5}

Gpu type=2 species=11. -> "Gpu type=2" indicates a Non-Fermi GPU; "species=11" means compute capability 1.1 is available.

Gpu type=2 species=12. -> "Gpu type=2" indicates a Non-Fermi GPU; "species=12" means compute capability 1.2 is available.

Gpu type=2 species=13. -> "Gpu type=2" indicates a Non-Fermi GPU; "species=13" means compute capability 1.3 is available.

Gpu type=3 species=0. -> "Gpu type=3" indicates a Fermi GPU; "species=0" means unknown compute capability

Gpu type=3 species=20. -> "Gpu type=3" indicates a Fermi GPU; "species=20" means compute capability 2.0 is available.

Gpu type=3 species=21. -> "Gpu type=3" indicates a Fermi GPU; "species=21" means compute capability 2.1 is available.
Under some conditions, your GPU will not be recognized so it will display this message "Gpu species not recognized." The common reasons are:

1) You haven't installed the correct Driver. Check what Driver is recommended for Folding or try the latest ones by your GPU Vendor.

2) You may have stubborn files from the previous driver that is causing this error. Please use Driver Sweeper and try again.

3) You might be using a recently launched GPU Model that isn't recognized by the GPU3 BETA Client. If this happens, by using this method, an appropriate flag may be added which would allow your GPU to fold. The flag will only work if the GPU architecture is similar to the previous one. It is advised to search the Forum for the GPU in question to see which flag is required for it to work:

-forcegpu ati_r600 -> It bypasses the Clients' auto detect feature and instructs it to treat the GPU as a 3000 Series one

-forcegpu ati_r700 -> It bypasses the Clients' auto detect feature and instructs it to treat the GPU as a 4000 Series one

-forcegpu ati_r800 -> It bypasses the Clients' auto detect feature and instructs it to treat the GPU as a 5000 Series one


The meanings of the -forcegpu flags are specific to v6.3X of the GPU3 Beta Client:
Quote:
Originally Posted by v6.3X
-forcegpu nvidia_fermi -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU as a Fermi architecture, i.e. the GPU is a 400 Series one

-forcegpu nvidia_g80 -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU as a G80 architecture, i.e. the GPU is a 8/9/200 Series one {Read Note 5}

The meanings of the -forcegpu flags are specific to v6.4X of the GPU3 Beta Client:
Quote:
Originally Posted by v6.4X
-forcegpu nvidia_fermi -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU having compute capability 2.0

-forcegpu nvidia_g80 -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU having compute capability 1.1 {Read Note 5}

-forcegpu nvidia_g80_1.0 -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU having compute capability 1.0 {Read Note 5}



4) You may be trying to run the GPU3 BETA Client on the GPU Model that is too old hence isn't supported by F@h.


Note 1: Using the -forcegpu flag with the wrong GPU will mess things up. It may invalidate the scientific results produced. DO NOT MISUSE THESE FLAGS. (Details)

Note 2: Please remember that officially, Overclocking is discouraged. (Details)

Note 3: If you are using 8800 Series GPU or 9800 series GPU, you may encounter bugs. The Development Team is aware of it and are working on a fix: <Click>

Note 4: On some GPUs, when it is folding, a high pitched whine noise is emitted from the GPU. This is called Capacitor Whine and doesn't pose any serious threat to the GPU in use.

Note 5: Please note that the following GPUs MUST NOT USE the -forcegpu nvidia_g80 since they will be assigned FahCore_15 WUs which they cannot process. This is due to the compute capability limitation hence they have to use the -forcegpu nvidia_g80_1.0 flag:
Nvidia GeForce 8800 GTS
Nvidia GeForce 8800 GTX
Nvidia GeForce 8800 Ultra


Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read

  • Before Using GPU3 BETA Client

Users of GPU2 Client, wanting to check out GPU3 BETA Client, are advised to use the -oneunit flag. After the Client exits, proceed with the installation of GPU3 BETA Client. It is recommended to upgrade the Client after the WU has been completed to avoid any potential problems that you may experience from incompatibilities between the FahCore and the WU. Also it won't cause loss of points if any problems does occur that causes the WU to be lost.

Please ensure that you are meeting the
minimum requirements for running the GPU3 BETA Client. Usage of Nvidia 258.96 WHQL Driver is recommended. If you use drivers prior to this, it may or may not work. Note that GPU2 Client will not use the FahCore_15 to process the WU. As the Client is in BETA Stage users can expect instability so if you have such an experience, please report it.

Some users complain that after they installed the recommended driver, they are having problem(s) when running F@H GPU3 BETA Client. Most of this can be avoided by making a clean installation of the driver. However, you can use this freeware application
Driver Sweeper to remove any stubborn file(s) which may be causing problem(s).


Note 1: Please refrain form folding on non-recommended Drivers. The reason is that you may be producing scientifically invalid results which may have a negative effect on the Project. (Details)

Note 2: Please refrain form folding on BETA Drivers and reporting any issues with them. The reason is that if you are using BETA Drivers, if a problem appears, F@H developers can't differentiate if it is the Drivers fault (GPU Vendors' bug) or something in their software (F@H bug). Hence please wait for the WHQL Driver release which will be tested by the F@H developers and once it is verified to produce scientifically valid results, you can update your Drivers if necessary. (Details)
Quote:
  • GPU3 BETA Client Download Locations

Refer to Official Forum Thread.
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Installation Of Systray Version
The Client by default is installed in C:\Program Files\Folding@Home and you may have to start the application from there. This will cause a screen to appear where you can configure the Client. Restart the Client and if everything is properly configured, it will then download an appropriate WU along with the required FahCore.

Official Installation Guide: <Click>


Note 1: Make sure that you have the correct paths in the shortcut. By default, everything should work without any issue:
Windows All Versions (32 bit) -> Target: C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe
Windows All Versions (64 bit) -> Target: C:\Program Files (x86)\Folding@home\Folding@home-gpu\Folding@home.exe

Windows XP (32 bit & 64 bit) -> C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu
Windows Vista (32 bit & 64 bit) -> C:\Users\[username]\AppData\Roaming\Folding@Home-gpu
Windows 7 (32 bit & 64 bit) -> C:\Users\[username]\AppData\Roaming\Folding@Home-gpu
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Installation Of Console Version

The installation requires you to simply unzip the file in the folder of your liking and run "Folding@home-Win32-GPU" OR "Folding@home-Win32-GPU.exe" (depending on your Windows settings) which will allow you to configure the Client. Rest
art the Client (by using "Ctrl + C" to exit) and if everything is properly configured, it will then download an appropriate WU along with the required FahCore.

Official Installation Guide:
<Click>


Note 1: To a layman, using "Ctrl + C" OR "X Button" to exit the Client may appear to be the same but there is a technical difference between them. Using "Ctrl + C" informs the console application to send a wm_close message to all child threads, while pressing the "X Button" on the console triggers the onclose function of the console application and if this doesn't handle closing all child threads, you may get into trouble (not necessarily, but the possibility does exist). Thus we prefer to use "Ctrl + C" to minimize the possibility of any error.

Note 2: Make sure that the F@H Folder isn't located in the Program Files. If it is, it is advised to change it to a simpler location like C:\F@H due to the UAC implemented in Windows Vista and Windows 7 which may conflict with the Client and may cause unexpected results.
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Upgrading The Console Version

Download the correct GPU3 BETA Client version and after you unzip the file, copy/paste the files into the pre-existing GPU2 Client folder. If asked to overwrite the file(s), answer "Yes". The already created shortcuts should work fine.


Note 1: Users of GPU2 Client, upgrading to GPU3 BETA Client, are advised to use the -oneunit flag. After the Client exits, proceed with the upgrade.
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Installation Of Multiple Instances
Initially install the first Client and make sure that it is running smoothly before installing multiple instances.

Detailed Installation Guide: <Click>

Quick Installation Guide: <Click>


Note 1: To find information about the GPUs installed in your system along with the driver information, you can use GPU-Z. For obtaining the X value in -gpu X, you should use CUDA-Z.
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Upgrading From A Non-Fermi GPU To A Nvidia Fermi GPU
If you are removing a Non-Fermi GPU and replacing it with a Nvidia Fermi GPU, there are some steps that you have to take to ensure a smooth transition and continue folding without much hassle. Please note that this isn't for running a Nvidia Fermi and Non-Fermi GPU in one system, that is covered in another section.

Step 1: Use the -oneunit flag on the GPU Client
Step 2: Once the Client exit, uninstall the F@h GPU Client and delete anything that is related to it*
Step 3: Power down the system and swap the Non-Fermi GPU with the Nvidia Fermi GPU
Step 4: Install the GPU3 BETA Client and run it
*Depending on whether you installed the Systray Version or the Console Version, you may have to do the following:

For Console Version:
Step A: Locate the folder in which you have installed the GPU Client
Step B: Delete it and any shortcuts you made to it

For Systray Version:
Step A: Press Windows Key + R to open Run window
Step B: Type this %APPDATA% (with the % sign) and press enter
Step C: A window will appear (C:\Users\[username]\AppData\Roaming\ OR C:\Documents and Settings\[username]\Application Data\) and there you have to delete a folder called "Folding@Home-gpu"
Step D: Delete any shortcuts you have made


Note 1: Make sure that you delete the FahCore_xx, queue.dat and work folder as incorrect version\type will cause problems and won't allow your F@h GPU3 BETA Client to function normally
Quote:
Legend:
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Using A Nvidia Fermi GPU & A Nvidia Non-Fermi GPU In One System
When combining a Nvidia Fermi GPU with a Nvidia Non-Fermi GPU, the Nvidia Fermi GPU will fold FahCore_15 WUs while the Nvidia Non-Fermi GPU will fold FahCore_11 WUs. However, if the Nvidia Non-Fermi GPU attempts to fold a FahCore_15 WU, it will result in an error if the Clients aren't properly configured. In certain situations, this setup may not work. Nonetheless, you have the following options:

Option 1: Make sure that there are separate folders for each GPU. After that, use these flags with the correct GPU:
Nvidia Fermi GPU: -forcegpu nvidia_fermi
Nvidia Non-Fermi GPU: -forcegpu nvidia_g80
You may use one or both flags to see if your GPUs can fold FahCore_15 WUs without any issue.

Option 2: Run one instance of GPU2 Client for the Nvidia Non-Fermi one and one instance of the GPU3 BETA Client for the Nvidia Fermi one. IMO, you may want to use the Console Version of both Clients as all the files are included in it and it is a no-nonsense version which makes it easier to set-up and reduces the possibility of errors.

Option 3: Takeout the Nvidia Non-Fermi GPU from your current system and place it in another system (should also contain Nvidia Non-Fermi GPUs only) so that it can fold FahCore_11 WUs and FahCore_15 WUs without any issue.


Note 1: Using the -forcegpu flag with the wrong GPU will mess things up. It may invalidate the scientific results produced. DO NOT MISUSE THESE FLAGS. (Details)

Note 2: Since there are different versions of FahCore_15 for the Nvidia Fermi GPUs and Nvidia Non-Fermi GPUs, plesae make sure that you have the correct FahCore_15 version by checking your FAHlog. Haven't the latest version isn't required since the Client will automatically upgrade FahCore_15 if the WU needs it:

FahCore_15 For Nvidia Fermi GPUs:
Version 2.15 (Tue Nov 16 09:05:18 PST 2010)
Version 2.14 (Thu Nov 11 10:05:53 PST 2010)
Version 2.13 (Mon Nov 8 13:19:45 PST 2010)
Version 2.11 (Fri Nov 5 12:50:40 PDT 2010)
Version 2.09 (Thu May 20 11:58:42 PDT 2010)

FahCore_15 For Nvidia Non-Fermi GPUs:
Version 2.15 (Tue Nov 16 08:44:57 PST 2010)
Version 2.13 (Mon Nov 8 13:20:33 PST 2010)
Version 2.12 (Mon Nov 8 11:24:19 PST 2010)
Version 2.11 (Fri Nov 5 12:37:29 PDT 2010)
Version 2.09 (Thu May 20 11:51:02 PDT 2010)

Quote:
  • Using Multiple Fermi GPUs In One System
If the F@h GPU3 BETA Client isn't getting enough CPU Cycles, the drop in PPD is significant especially if you have multiple Nvidia Fermi GPUs installed in one system. The reason is that the GPU is waiting for the CPU to give it data to process thus it causes a delay in the processing of the WU which is reflected negatively in your PPD.

A rough estimate is 1 Nvidia Fermi GPU = 1/2 CPU free. Thus systems with Dual Nvidia Fermi GPUs would need 1 free CPU. Triple and Quad Nvidia Fermi GPU systems would need ~2 CPUs free (Results taken from Q9550 @ 2.83) It will vary depending on CPU Model, CPU Speed and other factors, hence you must experiment with your system to find the highest PPD possible. You may also want to experiment with the F@h Core Priority to optimize your F@h Clients. Do not use Task Manager to change this, use the F@h Clients' settings only.
Quote:
Legend:
Red Text -> Specifically For AMD/ATI GPUs
Green Text -> Specifically For Nvidia GPUs
Blue Text -> Important Note(s) That You Must Read
Black Text -> Applicable To Both GPU Vendors

  • Changing From One GPU Brand To Another
When you replace your existing GPU from an ATI/AMD one to a Nvidia one OR from Nvidia one to an ATI/AMD one, you should prepare your system for the new GPU to ensure that you won't have problems when running the F@h Client. Please note that this isn't for running an ATI/AMD and Nvidia GPU in one box/rig/system. Below is the procedure that you must follow to ensure a smooth transition from one GPU brand to another GPU brand:

Replacing an ATI/AMD GPU with Nvidia GPU:
Step 1: Use the -oneunit flag and wait for the Client to upload the wuresult and exit
Step 2: Uninstall the F@h GPU Client and delete anything that is related to it* (you may want to remove the Environment Variables if you have set them up)
Step 3: Uninstall ATI/AMD Drivers using its uninstaller
Step 4: Install Driver Sweeper (Don't run it)
Step 5: Switch off system and swap the ATI GPU for Nvidia one
Step 6: Boot into Safe Mode and run Driver Sweeper to remove any remnants of ATI Drivers if they exist
Step 7: Boot into Windows (normal) and install the appropriate Nvidia Driver
Step 8: Reboot the system and download the F@h GPU Client for Nvidia
Step 9: Install the Nvidia F@h GPU Client and run it

*Please read Note 1

Replacing a Nvidia GPU with an ATI/AMD GPU:
Step 1: Use the -oneunit flag and wait for the Client to upload the wuresult and exit
Step 2: Uninstall the F@h GPU Client and delete anything that is related to it*
Step 3: Uninstall Nvidia Drivers using its uninstaller
Step 4: Install Driver Sweeper (Don't run it)
Step 5: Switch off system and swap the Nvidia GPU for an ATI/AMD one
Step 6: Boot into Safe Mode and run Driver Sweeper to remove any remnants of Nvidia Drivers if they exist
Step 7: Boot into Windows (normal) and install the appropriate ATI/AMD Driver
Step 8: Reboot the system and download the F@h GPU Client for ATI/AMD
Step 9: Install the ATI/AMD F@h GPU Client and run it
Note: If you want to make folding more efficient, please use Environment Variables; Guide 1, Guide 2.

*Please read Note 1

Please remember that the above method is for a single GPU brand in a single system. While it is possible to fold on an ATI and Nvidia GPUs in one system, it is complex and doesn't necessarily work for everyone.


Note 1: Depending on whether you installed the Systray Version or the Console Version, you may have to do the following:

For Console Version:
Step A: Locate the folder in which you have installed the GPU3 BETA Client
Step B: Delete it and any shortcuts you made to it
Note: Make sure that you delete the FahCore_xx, queue.dat and work folder as incorrect version\type will cause problems and won't allow your F@h GPU Client to function normally

For Systray Version:
Step A: Press Windows Key + R to open Run window
Step B: Type this %APPDATA% (with the % sign) and press enter
Step C: A window will appear (C:\Users\[username]\AppData\Roaming\ OR C:\Documents and Settings\[username]\Application Data\) and there you have to delete a folder called "Folding@Home-gpu"
Step D: Delete any shortcuts you have made
Note: Make sure that you delete the FahCore_xx, queue.dat and work folder as incorrect version\type will cause problems and won't allow your F@h GPU Client to function normally
Quote:
Legend:
Green Text -> Specifically For Nvidia GPUs
Black Text -> Applicable To Both GPU Vendors

  • Notes Regarding GPU3 BETA Client

1) Distribution of WUs are like this:
GTX 400 Series GPU, GTX 500 Series (Fermi) = Uses only FahCore_15
8000 Series GPU, 9000 Series GPU, GTX 200 Series GPU (Non-Fermi) = Uses FahCore_11 & FahCore_15


2) The GPU3 Client uses new Project and won't be porting any of the GPU2 Project.

3) The Viewer that is present in the Systray Version is known to be buggy/resource hog. You don't have to run the viewer for the Client to fold and it isn't used to monitor the Client. To monitor the Client, please visit the tools list and download an appropriate application.

4) Please note that when using the passkey with the GPU3 BETA Client (also for GPU2 Client), some of the WUs (GPU ONLY) will not be credited under the passkey/username combination BUT will be credited under the username only. However, in the future, this will change so that the WUs will be credited under the passkey/username combination (Details)

5) The GPU3 is in BETA stage so the Credits may change: <Click>

6) In the FAHlog file, the version is represented as 6.30r2 and it is the same as 6.32. It's just a different way of representing the same information. Here are some more examples:
A) 6.30 R2
B) 6.3 R2
C) 6.3R2
D) 6.32
Quote:
Legend:
Green Text -> Specifically For Nvidia GPUs
Black Text -> Applicable To Both GPU Vendors

  • Troubleshooting The GPU3 BETA Client
Despite reading all the above notes, if for some reason, your Client still gives you errors, then you may want to first check the F@h Forum for that WU as some WUs in a Project can be faulty/bad (Details). If it is present, add your report to the preexisting thread along with your FAHlog by using the Code Button (Details) If it isn't present, you may create a new thread in this sub-forum -> Issues with a specific WU and post your FAHlog/FAHlog-Prev (Details) and an Admin/Mod will look it up in the database. If multiple errors are reported, then it will be marked as bad and you need not worry about your system. If it was able to complete successfully, then it is worth reading these suggestions (Some suggestions may not apply to you):

1) Have you overclocked your GPUs? If yes, then I suggest that you return them to stock settings and then see if the EUE error occurs. Please note that F@h stress your system in a different way when compared to different stress softwares hence a stable setting in stress program A might be unstable in F@h GPU Client or vice-versa.

2) If you are using a Nvidia Fermi GPU and received "CoreStatus = 63 (99)" message, consider the following:
A) If you were initially tweaking the system for CUDA apps, you may have added this Environment Variable "CUDA_FORCE_PTX_JIT=1" Deleting this will allow the GPU3 Client to work: <Click>
B) Check if the GPU is completely securely fixed inside the PCI-E Slot: <Click>


3A) [Nvidia] Can you run MemtestG80 without any errors at default? If yes, then repeat the test by increasing the number of runs and memory used by this method:
Code:
Step  1: Start up a command prompt (start -> run -> cmd OR Win key+R  -> type cmd OR Windows 7 users can browse to the directory and  Shift+Right Click -> "Open command window here")

Step 2: Change to the directory where the memtest executable is located

Step 3: Type this:
memtestG80 128 1000

Step 4: The first value is the value of GPU RAM to be used while the second value is the number of times the test will run.

NOTE  - If errors occurs and the value is 4 Billion (Exact number is:  4,294,967,284), then it is a time out so ensure that you are running the  latest version. If this occurs even with the latest version, please  contact ihaque who is a Member of Pande Group and the developer of this  application.
If the error value is not the previously mentioned one, then the GPU is faulty. Consider returning your GPU frequencies to stock or even even lower to see if the error stops. If it doesn't then the GPU isn't producing scientifically valid data so consider changing the GPU or stop the F@h GPU Client on that GPU. (Discussion Thread)


3B) [ATI - 9.12 or higher Driver + ATI Stream SDK & Nvidia - 195 or higher Driver] Can you run MemtestCL without any errors at default? If yes, then repeat the test by increasing the number of runs and memory used by this method:
Code:
Step  1: Start up a command prompt (start -> run -> cmd OR Win key+R  -> type cmd OR Windows 7 users can browse to the directory and  Shift+Right Click -> "Open command window here")

Step 2: Change to the directory where the MemtestCL executable is located

Step 3: Type this:
memtestCL 128 1000

Step  4: The first value is the value of GPU RAM to be used while the second  value is the number of times the test will run, both can be changed so  you can check your GPU

Step 5: Once it completes the test, it  will show you the Final error count. 0 will indicate everything is fine  while a non-zero digit may indicate instabilities.
If the error value is not zero (0), then the GPU is faulty. Consider returning your GPU frequencies to stock or even even lower to see if the error stops. If it doesn't then the GPU isn't producing scientifically valid data so consider changing the GPU or stop the F@h GPU Client on that GPU. (Discussion Thread)

4) It could be possible that the error is heat related so I suggest that you monitor the GPU temperature(s) by using GPU-Z or HWMonitor to ensure that it is at a safe level. If it isn't, then you have the following options:
Option 1: Manually increase the fan speed of your GPU(s) to ensure that the temperature falls to the safe level. (Please note that the safe level of temperature will vary due to personal choice. Personally, I like my GPU <75C when fully stressed while others prefer <80C and some don't mind <90C. However, if the temperature is too high, thermal protection will be activated and will automatically reduce the GPU frequencies to reduce its temperature in order to avoid hardware damage)
Option 2: Use this Nvidia Environment Variable: FAH_GPU_IDLE with a value between 5 and 10 (Guide 1, Guide 2) which might help in reducing the GPU temperature.

5) Some users complain about desktop lagging when performing basic tasks. Possible solutions are:
A) Enable Aero if you are using Windows Vista or Windows 7.
B) Use this Nvidia Environment Variable; FAH_GPU_IDLE and use a value between 5 and 10 (Guide 1, Guide 2)

6) If you are noticing a less GPU Usage and if you have a Classic/SMP2 Client installed, make sure that you set the GPU3's priority to low and the Classic/SMP2 to idle. With this method, the GPU3 will have a constant data stream to process and won't have to wait for the CPU thus it will keep the GPU at maximum load.

7) If you are experiencing FILE_IO_ERROR, you should do the following:
A) Run CHKDSK to ensure that the hard disk drive isn't faulty.
B) Make sure that the folder isn't being "shared" by another Client. If you have multiple Clients, please use separate folders for each.
C) Some Anti-Virus programs can interfere with the folding files. Make sure you add the folding file to the exception list.
D) You may not have write permission for that folder so check your permission level.
E) The driver may be full so consider freeing up some space.

8) Make sure that you are using correct flags. Incorrect ones may cause unexpected results. Here are some of the commonly used flags:
  • -verbosity 9 = Makes the FAHlog more detailed which helps in troubleshooting the Client.
    -advmethods = Grants you access to WUs that are in the late BETA Stage. Your probability of a WU EUEing increases.
    -configonly = The Client will read/write the configurations and exit. No WU processing is done even if it is present in the queue.
    -send all = The Client will try to upload the wuresult file (if found) to the Server. Once it does so, it will exit and won't process any WU even if it is present in the queue.
    -oneunit = The Client will process the current WU and once it uploads the wuresult to the Server, it will exit without downloading a new WU.
9) If you suspect that it is your motherboard's fault, I suggest that you run the GPU in different PCI-E Slots and monitor its progress, if it gives errors on all PCI-E Slots, then you can assume it is the motherboard (you need to switch the GPU to ensure that it is the motherboards' problem and not your GPU)

10) What drivers are you using? If you are using BETA Drives, uninstall them and try the recommended ones or search the Forum to find out what Drivers are working.

11) Is your Power Supply Unit working properly? A faulty PSU can cause hardware failure so always use a branded one and not a nameless one as F@h stresses your GPU.

12) Have you tweaked unknown variables in your motherboards' BIOS? If yes, then restore everything to default and try again.

13) If you are using Windows Remote Desktop Connection on the system, it will crash the GPU Client. If you have to access the system, you can use these freeware applications, Ultra VNC or TightVNC, so that it won't crash the GPU Client.

14) Under some circumstances, you may get an error about cudart.dll so you may want to post your FAHlog here so we can figure out the problem. Coping the file(s) may or may not work.

Last edited by PantherX; 01-29-2011 at 09:17. Reason: Updated & Edited Guide
   
Reply With Quote
 
Old
  (#2)
IPlayNaked
Banned
 
Videocard: XFire 7950 1200/1850
Processor: Intel i5 2500k 5 Ghz
Mainboard: MSI Z77A-GD55
Memory: 8GB Corsair Dominator
Soundcard: Logitech G930
PSU: Corsair 650w
Default 06-07-2010, 17:44 | posts: 6,559

[15:26:36] Gpu type=3 species=30.
[15:26:36] Loaded queue successfully.
[15:26:36] Initialization complete
[15:26:36]
[15:26:36] + Processing work unit
[15:26:36] Core required: FahCore_15.exe
[15:26:36] Core found.
[15:26:36] Working on queue slot 01 [June 7 15:26:36 UTC]
[15:26:36] + Working ...
[15:28:21] CoreStatus = C0000135 (-1073741515)
[15:28:21] Client-core communications error: ERROR 0xc0000135
[15:28:21] This is a sign of more serious problems, shutting down.

Got that cudart.dll error or whatever. I am using the 257 beta drivers, for gaming, is this incompatible or what? I think what I posted is the relevant portion, and you'll have to forgive my complete ignorance. I've had ATI cards for quite a while, so I haven't done any folding, plus I'm new to CUDA, so it's all a blur.
   
Reply With Quote
Old
  (#3)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-07-2010, 23:56 | posts: 1,205

I will start off with some dumb questions so please have some patience
If your current system had ATI GPU, you might have some stubborn files so sure Drive Sweeper.
I guess that you are using the Systray Client, if so then I too get that error (http://foldingforum.org/viewtopic.ph...=14680#p144545) and regardless of what I did, it wouldn't work so in the end, I simply uninstalled the Systray Client and used the Console Version which worked on the first attempt and since then, never gave me any problems so far.
   
Reply With Quote
Old
  (#4)
IPlayNaked
Banned
 
Videocard: XFire 7950 1200/1850
Processor: Intel i5 2500k 5 Ghz
Mainboard: MSI Z77A-GD55
Memory: 8GB Corsair Dominator
Soundcard: Logitech G930
PSU: Corsair 650w
Default 06-08-2010, 02:08 | posts: 6,559

Quote:
Originally Posted by PantherX View Post
I will start off with some dumb questions so please have some patience
If your current system had ATI GPU, you might have some stubborn files so sure Drive Sweeper.
I guess that you are using the Systray Client, if so then I too get that error (http://foldingforum.org/viewtopic.ph...=14680#p144545) and regardless of what I did, it wouldn't work so in the end, I simply uninstalled the Systray Client and used the Console Version which worked on the first attempt and since then, never gave me any problems so far.
The thread you linked to fixed it. Just take the files from the Roaming/Folding@home-gpu folder and put them in the program files/folding@home folder. Works now, thanks.

EDIT: Yikes. So I won't be folding because even at stock clocks and voltages my 470 is squealing like a pig.

Last edited by IPlayNaked; 06-08-2010 at 02:17.
   
Reply With Quote
 
Old
  (#5)
Athlonite
Maha Guru
 
Athlonite's Avatar
 
Videocard: 2 HD7850 1GHz/1300MHz
Processor: FX8320 / 3700MHz
Mainboard: ASUS Crosshair V Formula
Memory: DDR3 Corsair Vengence LP
Soundcard: SB XFi Audio PCIe
PSU: SilverStone ST75F-P 750W
Default 06-08-2010, 05:21 | posts: 855 | Location: Hawkes Bay

What sort of Temps are you seeing on the 470 IPLay
   
Reply With Quote
Old
  (#6)
IPlayNaked
Banned
 
Videocard: XFire 7950 1200/1850
Processor: Intel i5 2500k 5 Ghz
Mainboard: MSI Z77A-GD55
Memory: 8GB Corsair Dominator
Soundcard: Logitech G930
PSU: Corsair 650w
Default 06-08-2010, 16:13 | posts: 6,559

Quote:
Originally Posted by Athlonite View Post
What sort of Temps are you seeing on the 470 IPLay
I'm watercooled so nowhere above 50c.
   
Reply With Quote
Old
  (#7)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-08-2010, 17:37 | posts: 1,205

Have you tried to reduce the OC to see if the squealing stops or reduces?
   
Reply With Quote
Old
  (#8)
IPlayNaked
Banned
 
Videocard: XFire 7950 1200/1850
Processor: Intel i5 2500k 5 Ghz
Mainboard: MSI Z77A-GD55
Memory: 8GB Corsair Dominator
Soundcard: Logitech G930
PSU: Corsair 650w
Default 06-08-2010, 18:46 | posts: 6,559

Quote:
Originally Posted by PantherX View Post
Have you tried to reduce the OC to see if the squealing stops or reduces?
Yeah, as I said, it does it even at stock. Only when folding, no game does it. Reducing voltage does make it slightly less annoying, but only barely, certainly not enough to leave it running all day.

http://www.evga.com/forums/tm.aspx?m=400534&mpage=1

Looks like some people get it, some don't.
   
Reply With Quote
Old
  (#9)
k3vst3r
Ancient Guru
 
k3vst3r's Avatar
 
Videocard: Tri-fire 290x Qnix 120Hz
Processor: i7 4770k 4.6
Mainboard: Asus Maximus Hero VI
Memory: 4x4GB 2400
Soundcard: SB X-FI Titanium
PSU: Corsair AX1200i
Default 06-08-2010, 18:52 | posts: 3,016 | Location: Sheffield UK

Weird mine don't squeal during fah at 800 core.
   
Reply With Quote
Old
  (#10)
davido6
Maha Guru
 
davido6's Avatar
 
Videocard: GV-R795WF3-3GD
Processor: i5 3750k @4.9ghz 1.2v
Mainboard: asrock z77 extreme6
Memory: 16 gig corsair vengeance
Soundcard: Sound Blaster X-Fi Fatal1
PSU: Adata HM 1200W
Default 06-08-2010, 21:12 | posts: 1,220 | Location: uk sheffield

Quote:
Originally Posted by IPlayNaked View Post
Yeah, as I said, it does it even at stock. Only when folding, no game does it. Reducing voltage does make it slightly less annoying, but only barely, certainly not enough to leave it running all day.

http://www.evga.com/forums/tm.aspx?m=400534&mpage=1

Looks like some people get it, some don't.
kinder make u wonder if its u vrms saying ffs cool meeeeeeeeeeeee lol
   
Reply With Quote
 
Old
  (#11)
iancook221188
Maha Guru
 
Videocard: GTX 670 SLI / GTX 460 SLI
Processor: 2600k4.5 / i7 970 4.4 WC
Mainboard: X68 UD4 / X58A UD5
Memory: 16GB / 24GB
Soundcard:
PSU: TX850 / AX850
Default 06-08-2010, 22:55 | posts: 1,451 | Location: uk

i sometime hear my 260 squeal very weird at frist but i only here it on low fan rpm it took me a while to find out what it was
   
Reply With Quote
Old
  (#12)
Kaktus
Master Guru
 
Kaktus's Avatar
 
Videocard: Gigabyte 785O OC 2GB
Processor: I5 3570K @4.6 +EVO 212
Mainboard: Asrock Z77 Extreme 4
Memory: Corsair Vengeance 1600mhz
Soundcard:
PSU: Corsair cx600
Default 06-12-2010, 23:02 | posts: 307 | Location: South Africa

hi Guys.
Can i use GPU3 on a 4670?
   
Reply With Quote
Old
  (#13)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-12-2010, 23:22 | posts: 1,205

You can but it isn't really recommended. So far from what I have read, there aren't any problems but it hasn't been tested as this release is specific to Nvidia only.
   
Reply With Quote
Old
  (#14)
Kaktus
Master Guru
 
Kaktus's Avatar
 
Videocard: Gigabyte 785O OC 2GB
Processor: I5 3570K @4.6 +EVO 212
Mainboard: Asrock Z77 Extreme 4
Memory: Corsair Vengeance 1600mhz
Soundcard:
PSU: Corsair cx600
Default 06-13-2010, 09:37 | posts: 307 | Location: South Africa

Thanks.
I'll give it a skip for know then.
   
Reply With Quote
Old
  (#15)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-17-2010, 04:32 | posts: 1,205

Updated the Guide to include the NVIDIA GeForce Forceware 257.21 WHQL + GPU3 BETA Results Section. Will add more information as and when I receive them.
   
Reply With Quote
Old
  (#16)
deltatux
Ancient Guru
 
deltatux's Avatar
 
Videocard: GIGABYTE Radeon R9 280
Processor: Intel Core i5 3570K @4.5
Mainboard: GIGABYTE GA-Z77X-UD5H
Memory: Patriot 4 x 4GB DDR3-1600
Soundcard: Auzentech X-Raider 7.1
PSU: OCZ ModXStream Pro 500W
Default 06-17-2010, 05:04 | posts: 19,055 | Location: Toronto, Canada

Ye, I'm just gonna stick to GPU2 right now as well. It's doing quite well so why fix something that ain't broke?

deltatux
   
Reply With Quote
Old
  (#17)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-17-2010, 05:21 | posts: 1,205

deltatux: That is true but once the FAHCore_11 WUs run out, you will have to upgrade to GPU3 Client. If you want more details, read this: (http://folding.typepad.com/news/2010...st-update.html)
BTW in your sig, you have an ATI Card so this particular version isn't for ATI yet. Hopefully in the future there will be an ATI release where you may want to join.
   
Reply With Quote
Old
  (#18)
arcon
Newbie
 
arcon's Avatar
 
Videocard: EVGA GTX 465 & 8800 GT
Processor: Intel Pentium CPU G6950
Mainboard: Gigabyte H55M-UD2H
Memory: 8 GB G.Skill
Soundcard: Onboard
PSU: be quiet Pure Power 530W
Default 06-18-2010, 18:23 | posts: 42 | Location: Germany

what about that?

http://www.stanford.edu/%7Efriedrim/GPU3Review-2010.zip
   
Reply With Quote
Old
  (#19)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 06-18-2010, 19:26 | posts: 1,205

Quote:
Originally Posted by arcon View Post
I have reported it in the official forum. Will update when I get any updates.

UPDATE-
It isn't a Client, rather a benchmarking one that doesn't do any actual folding. More info here: (http://foldingforum.org/viewtopic.php?f=59&t=14986)

Last edited by PantherX; 06-18-2010 at 20:21.
   
Reply With Quote
Old
  (#20)
arcon
Newbie
 
arcon's Avatar
 
Videocard: EVGA GTX 465 & 8800 GT
Processor: Intel Pentium CPU G6950
Mainboard: Gigabyte H55M-UD2H
Memory: 8 GB G.Skill
Soundcard: Onboard
PSU: be quiet Pure Power 530W
Default 06-18-2010, 20:36 | posts: 42 | Location: Germany

thx for the info!
   
Reply With Quote
Old
  (#21)
Svein_Skogen
Maha Guru
 
Svein_Skogen's Avatar
 
Videocard: 2x GTX570, ASUS+eVGA
Processor: Intel i7-950
Mainboard: Asus P6X58D-E
Memory: KVR1333D3N9K3, 24GB
Soundcard: Creative X-FI Titanium
PSU: Chieftec CFT-1200G-DF
Default 08-12-2010, 23:44 | posts: 1,284 | Location: Skedsmokorset, Norway

Does this mean those daring of us running ATI should consider installing the GPU3 software, or should we stick to GPU2 a little longer?

//Svein

Post moved to appropriate thread. {F@HTL}

Last edited by PantherX; 08-13-2010 at 02:10.
   
Reply With Quote
Old
  (#22)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 08-13-2010, 02:21 | posts: 1,205

TBH, the choice is yours. Technically, the GPU3 BETA Client is for Nvidia as it adds the support for FahCore_15 which can run on Fermi and Non-Fermi GPUs. However, on the ATI side, there isn't any performance improvement. You will still be using the same FahCore_11 that was available on GPU2 Client. The only difference is that the whitelist has been updated so there isn't any need to use the -forcegpu ati_r600 -forcegpu ati_r700, -forcegpu ati_r800 flags which makes it slightly easier to install. However, if new ATI GPUs are released, then you might be needing the -forcegpu flag. Simply put:

GPU3 BETA Client (Nvidia):
Support for new FahCore_15 which can run on Fermi and Non-Fermi
Support for existing FahCore_11 which runs on Non-Fermi only

GPU3 BETA Client (ATI):
Updated whitelist for GPUs

FYI, the "little longer" part is kinda vague as PG (Pande Group) never gives ETA on anything. They will release it when its ready. I do know that there is a new FahCore_16 being developed but not sure if it is for ATI or Nvidia.

IMO if you already have the GPU2 Client installed, don't bother. If you are new to F@H, then you might want to consider GPU3 BETA Client as it removes the need to use the -forcegpu flag which simplifies the installation procedure slightly.
   
Reply With Quote
Old
  (#23)
Svein_Skogen
Maha Guru
 
Svein_Skogen's Avatar
 
Videocard: 2x GTX570, ASUS+eVGA
Processor: Intel i7-950
Mainboard: Asus P6X58D-E
Memory: KVR1333D3N9K3, 24GB
Soundcard: Creative X-FI Titanium
PSU: Chieftec CFT-1200G-DF
Default 08-17-2010, 11:31 | posts: 1,284 | Location: Skedsmokorset, Norway

Will adding four sessions of the cpu client (quad core) help on the machine chewing three gpu-clients (5970+5850), or will it just slow down the gpu clients?

//Svein

Post moved to appropriate thread. {F@HTL}

Last edited by PantherX; 08-17-2010 at 12:49.
   
Reply With Quote
Old
  (#24)
PantherX
Folding@Home Team Leader
 
Videocard: EVGA GTX 650 & GTX 660 Ti
Processor: i7-860 @ 3800 {1.33125V}
Mainboard: Gigabyte P55-UD5
Memory: Kingstston HyperX 8 GB
Soundcard: What's that?
PSU: Zalman 750 Watts
Default 08-17-2010, 12:54 | posts: 1,205

While folding with 3 ATI GPUs, what is your CPU Usage? If it is high (75%) then you may want to use Environment Variables to make it more efficient.

Technically, if you set the GPU Client's priority to low/Slightly Higher (from the F@H Options), and the CPU to idle, it won't matter.

However, for ATI GPUs, you will need a free Core to constantly feed the GPUs data while Nvidia GPUs doesn't need a free CPU as they are very efficient.
   
Reply With Quote
Old
  (#25)
Svein_Skogen
Maha Guru
 
Svein_Skogen's Avatar
 
Videocard: 2x GTX570, ASUS+eVGA
Processor: Intel i7-950
Mainboard: Asus P6X58D-E
Memory: KVR1333D3N9K3, 24GB
Soundcard: Creative X-FI Titanium
PSU: Chieftec CFT-1200G-DF
Default 08-17-2010, 12:58 | posts: 1,284 | Location: Skedsmokorset, Norway

So, adding three cpu clients (with affinity 1,2,4 hex) and running the gpu clients with affinity 8 should be ... adequate?

//Svein
   
Reply With Quote
Reply

Tags
gpu3 client

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



Powered by vBulletin®
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
vBulletin Skin developed by: vBStyles.com
Copyright (c) 1995-2014, All Rights Reserved. The Guru of 3D, the Hardware Guru, and 3D Guru are trademarks owned by Hilbert Hagedoorn.