Please note that this guide is no longer being updated as V7 has superseded GPU3.

This is the index to my GPU Guide. You will find the links to the various sections of my guide. A mini description of what that section covers is provided to ease navigation. If in doubt, please read all sections or ask in this Forum.

1 - Officially Supported Operating Systems -> The GPU3 BETA Client is Officially tested on these Operating Systems. Since the Client is still in BETA Stage, you may encounter some bugs. If you come across one, please report it in this Forum.

2 - UNOFFICIALLY Supported Operating System -> The GPU3 BETA Client is NOT Officially tested on these Operating Systems. If you encounter bugs, support is provided by 3rd party NOT Standford/Pande Group.

17 - Changelog -> A list of recent changes that I have done. If I have made new changes, I will be deleting the last post and making a new one. Hence it will appear in the "new posts" so that users can be informed when I have made updates to the Guide.

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:

The GPU detection messages below is specific to v6.3X of the GPU3 Beta Client:

v6.3X wrote: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:

The GPU detection messages below is specific to v6.4X of the GPU3 Beta Client:

v6.4X wrote: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:

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:

v6.3X wrote:-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:

v6.4X wrote:-forcegpu nvidia_fermi -> It bypasses the Clients' auto detect feature and instructs the Client to treat the GPU having compute capability 2.0

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, and 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)

Last edited by PantherX on Mon Nov 01, 2010 7:46 am, edited 5 times in total.

Note 1: Please make sure that you rename the Drop-in file for the latest Drop-in Console version (6.41) from "Folding@home.exe_console_6.41" to "Folding@home.exe" (remove "_console_6.41")

Note 2: Please note the the latest Drop-in Console version (6.41) comes in an executable file replacement form. That means you should already have GPU3 Beta Client Console version 6.31 on your system so you just replace the .exe file. It is preferred to use the -oneunit flag before upgrade to minimize WU loss.

Legend:Blue Text -> Important Note(s) That You Must ReadBlack 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.

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.exeWindows All Versions (64 bit) -> Target: C:\Program Files (x86)\Folding@home\Folding@home-gpu\Folding@home.exe

Legend:Blue Text -> Important Note(s) That You Must ReadBlack 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. Restart 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.

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.

Last edited by PantherX on Tue Nov 30, 2010 4:58 pm, edited 5 times in total.

Legend:Blue Text -> Important Note(s) That You Must ReadBlack 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 before upgrading. After the Client exits, proceed with the upgrade.

Last edited by PantherX on Sun Sep 26, 2010 1:39 pm, edited 5 times in total.

Legend:Blue Text -> Important Note(s) That You Must ReadBlack 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 ClientStep 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 GPUStep 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 ClientStep B: Delete it and any shortcuts you made to it

For Systray Version:Step A: Press Windows Key + R to open Run windowStep B: Type this %APPDATA% (with the % sign) and press enterStep 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

Last edited by PantherX on Fri Jan 28, 2011 12:29 am, edited 2 times in total.

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_fermiNvidia Non-Fermi GPU: -forcegpu nvidia_g80You 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:

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.

Last edited by PantherX on Fri Jan 28, 2011 12:32 am, edited 1 time in total.

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 exitStep 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 uninstallerStep 4: Install Driver Sweeper (Don't run it)Step 5: Switch off system and swap the ATI GPU for Nvidia oneStep 6: Boot into Safe Mode and run Driver Sweeper to remove any remnants of ATI Drivers if they existStep 7: Boot into Windows (normal) and install the appropriate Nvidia DriverStep 8: Reboot the system and download the F@h GPU Client for NvidiaStep 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 exitStep 2: Uninstall the F@h GPU Client and delete anything that is related to it*Step 3: Uninstall Nvidia Drivers using its uninstallerStep 4: Install Driver Sweeper (Don't run it)Step 5: Switch off system and swap the Nvidia GPU for an ATI/AMD oneStep 6: Boot into Safe Mode and run Driver Sweeper to remove any remnants of Nvidia Drivers if they existStep 7: Boot into Windows (normal) and install the appropriate ATI/AMD DriverStep 8: Reboot the system and download the F@h GPU Client for ATI/AMDStep 9: Install the ATI/AMD F@h GPU Client and run itNote: 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 ClientStep B: Delete it and any shortcuts you made to itNote: 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 windowStep B: Type this %APPDATA% (with the % sign) and press enterStep 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 madeNote: 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

Last edited by PantherX on Tue Nov 30, 2010 5:00 pm, edited 1 time in total.

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 combinationBUTwill 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)

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 R2B) 6.3 R2C) 6.3R2D) 6.32

Last edited by PantherX on Tue Nov 30, 2010 5:01 pm, edited 1 time in total.