Problem running GPU

[tontod]

This is extremely frustrating, has happened twice. 1st time the GPU client ran till 76%, then I got an error saying there was a problem with the ati driver and that it had recovered, that killed that run. Just earlier, I was away all day, came back to an error message saying that there was a problem with the fah executable and got the option to close it. I was at 79%, with a slow GPU (Radeon 3450), its taken me like 3 days to get to this point, and to lose all those WU's is frustrating :frown:

I'm surprised it dosent save a history and continue from there after restarting. Is there an issue with the driver? I downloaded the ATI drivers fairly recently, do I need to reinstall them?

 

[dajeepster]

reboot... it's what i've always done when i run into a problem.

 

[salvorhardin]

I've been having the same problem, but I've been getting it about once a week. F@H usually resumes the WU when I restart the service. This is happening with windows 7 on a 4830 using catalyst drivers 9.8. I used to run it on vista with catalyst 9.4 and never had any problems. You might try using an older driver.

 

[tontod]

Well, after rebooting my cpu client refused to come up. So after uninstalling and re-installing a couple of times, I'm up and running again. Why is this software so flaky?

My GPU client is also up and running again, so got both going finally :thumbsup:

 

[Assimilator1]

Don't use cat drivers 9.1-9.3 for F@H , they are super flaky!

I've found that Cat 9.4 with the beta dlls from F@H GPU forum & the latest GPU client (now 1-2mths old?) made a huge improvment to stabilty, VPU recoveries are now extremely rare & I can close the client now without losing it's work .

Btw what temp is your GPU running at?

 

[tontod]

Originally posted by: Assimilator1
Don't use cat drivers 9.1-9.3 for F@H , they are super flaky!

I've found that Cat 9.4 with the beta dlls from F@H GPU forum & the latest GPU client (now 1-2mths old?) made a huge improvment to stabilty, VPU recoveries are now extremely rare & I can close the client now without losing it's work .

Btw what temp is your GPU running at?

Thanks for the info. How do I find out the GPU temp? Is it in CPUID somewhere?

 

[PCTC2]

Originally posted by: tontod

Originally posted by: Assimilator1
Don't use cat drivers 9.1-9.3 for F@H , they are super flaky!

I've found that Cat 9.4 with the beta dlls from F@H GPU forum & the latest GPU client (now 1-2mths old?) made a huge improvment to stabilty, VPU recoveries are now extremely rare & I can close the client now without losing it's work .

Btw what temp is your GPU running at?

Thanks for the info. How do I find out the GPU temp? Is it in CPUID somewhere?

You can use hardware monitor, offered by CPUID. It might be the drivers, but also watch for temperature. And if you're OC'ing your card, back it down to stock, or even below stock.

 

[Assimilator1]

You can use Speedfan(possibly),GPU-Z, ATITool or the ATI drivers via CCC to monitor GPU temps.
To do it via the Cat Ctrl Ctr go to the ATI Overdrive section (assuming you have it).

Whilst the latest version of CPU-Z does indeed have GPU info now it does not monitor temps.

Oh I forgot I also adjusted the 'flush interval' to cut back on CPU useage for the GPU client, let us know if you want to play with that.

 

[tontod]

Originally posted by: Assimilator1
You can use Speedfan(possibly),GPU-Z, ATITool or the ATI drivers via CCC to monitor GPU temps.
To do it via the Cat Ctrl Ctr go to the ATI Overdrive section (assuming you have it).

Whilst the latest version of CPU-Z does indeed have GPU info now it does not monitor temps.

Oh I forgot I also adjusted the 'flush interval' to cut back on CPU useage for the GPU client, let us know if you want to play with that.

The GPU is currently at 65 deg. C - checked through ATI Overdrive. Everything on that screen is grayed out, not sure how to change any of the settings. I think I left the flush interval at the default, should I change that? And I'm using Catalyst ver 9.7

 

[salvorhardin]

To unlock ATI Overdrive you need to click on the lock to unlock it. I think you only need to unlock it if you want to OC the video card. The three dials on the right side show the temp, % used and fan speed. When running F@H what % of the GPU is being used? What percentage of your CPU is being used? What OS are you using? The flush interval allows you to free up CPU power that is used to feed the GPU at the cost of ppd. It would be better to make sure the GPU client is stable on your system before messing with any of the environment variables (flush interval, cal pre flush, cal no flush and brook yield).

 

[tontod]

Originally posted by: salvorhardin
To unlock ATI Overdrive you need to click on the lock to unlock it. I think you only need to unlock it if you want to OC the video card. The three dials on the right side show the temp, % used and fan speed. When running F@H what % of the GPU is being used? What percentage of your CPU is being used? What OS are you using? The flush interval allows you to free up CPU power that is used to feed the GPU at the cost of ppd. It would be better to make sure the GPU client is stable on your system before messing with any of the environment variables (flush interval, cal pre flush, cal no flush and brook yield).

GPU temp is at 66 deg. C and GPU usage is at 95%. All 4 CPU's are at 100%.

 

[salvorhardin]

What OS and drivers are you running? I think the drivers are what's causing the problems. From what I've seen, when the GPU is overloaded (consistently at 99% usage) or there are problems with the dll files you get error messages in the F@H log.

 

[tontod]

Originally posted by: salvorhardin
What OS and drivers are you running? I think the drivers are what's causing the problems. From what I've seen, when the GPU is overloaded (consistently at 99% usage) or there are problems with the dll files you get error messages in the F@H log.

I'm running Vista. I downloaded the latest (at the time 9.8) Catalyst drivers a few days ago. It seems to be behaving much better, after rebooting earlier today it restarted which it wasnt doing before.