Green Text -> Specifically For Nvidia GPUs
Black Text -> Applicable To Both GPU Vendors
- Troubleshooting The GPU3 BETA Client
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>
C) Make sure that the installed Drivers work with the F@H GPU Clients.
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: Select all
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.
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: Select all
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.
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 drive 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.
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, since they 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.
15) If you are folding in Windows XP and experience slow clocks, please disable the screensaver (Discussion Thread).
