Author |
Message |
|
Wish there were team forums here on GPUGRID...
Anyway.......
Just checking in.
The kitties have had this project queued in as their second project for just a bit as of late.
Not doing too bad, it would seem.
But, I have 25 errored tasks.
Most of them have come from a rig that I have now set to NNT for GPUGRID, because I don't have a clue what the problem with it is. Same vid cards as many other rigs, yet it was tossing errors more than the rest. A couple of 580s, which regardless of some conversation elsewhere on these forums, are a rather stalwart card....don't be too ready to toss off rigs that are not sporting the latest and greatest. I run some legacy stuff that serves very well.
Temps seemed OK, although kitty fur in the fans is a problem here at times.
Anyway, are some WUs here problematic, and should I be digging further?
I rebooted one rig that seemed to have tossed off more than it's share at one point, but nothing seems to have changed. Doing OK now, it seems.
Meow to all, I am a Seti guy, but thought this project about the most worthy of secondary consideration in scientific terms.
|
|
|
skgivenVolunteer moderator Volunteer tester
Send message
Joined: 23 Apr 09 Posts: 3968 Credit: 1,995,359,260 RAC: 0 Level
Scientific publications
|
Presumably this system,
http://www.gpugrid.net/show_host_detail.php?hostid=180888
It has 2 GTX580 GPU's. GPU0 seems a bit hotter than GPU1 (its likely closer to the CPU). It tends to get up to ~75C, so cooling might be the issue.
Increase the fan speed a bit - to keep it under 70C, if possible.
You might also want to install the latest (CUDA6.5 capable) drivers. You are using a CUDA6.0 driver on that system (as well as others, but not an issue there so don't need to change).
____________
FAQ's
HOW TO:
- Opt out of Beta Tests
- Ask for Help |
|
|
|
Presumably this system,
http://www.gpugrid.net/show_host_detail.php?hostid=180888
It has 2 GTX580 GPU's. GPU0 seems a bit hotter than GPU1 (its likely closer to the CPU). It tends to get up to ~75C, so cooling might be the issue.
Increase the fan speed a bit - to keep it under 70C, if possible.
You might also want to install the latest (CUDA6.5 capable) drivers. You are using a CUDA6.0 driver on that system (as well as others, but not an issue there so don't need to change).
That is the rig that I set to NNT for GPUGRID due to the errors. It crunches Seti just fine, no probs.
It is at floor level, so there could be some kitty fur buildup (I have 3 kitties, but the one that was long haired and used to brush by the rigs to fur them passed about a year ago), but the last time I yanked the cards, there was not much apparent in the fans. I plan on taking them out and pulling the covers off to inspect further this weekend.
And all GPU fans in all rigs are set to full speed via EVGA Precision.
I am leery about updating drivers...all my rigs are on 334.89 or 340.52, which should be sufficient to do all tasks here, if I am not mistaken. At least I am not running ATI, those folks are truly in driver hell....LOL.
Thanks for the kind reply. I'll try cleaning those cards again and give it another go.
Meow meow meow!
EDIT...
And I see that the kitties have just made the top 20 here after a week or so of hard crunching with my vintage hardware...LOL. |
|
|
|
Your cards in this host are overclocked ones. (1580MHz, 1620MHz)
The chips on these 580s are getting a bit old, so these cards might not tolerate as much overclocking as when they were new, especially with Windows XP (it has no WDDM overhead) and GPUGrid.
I suggest you that after cleaning the dust / kitty hair from the coolers, you should reduce the clocks on these cards by 100MHz (50MHz core).
If it doesn't help you should do it again, and check all power connectors (including the motherboard's 24 pin and the CPU's 4-8 pin connectors) inside this host.
A driver update is also suggested, but there's a negligible possibility that the old driver is causing these errors. |
|
|
|
Your cards in this host are overclocked ones. (1580MHz, 1620MHz)
The chips on these 580s are getting a bit old, so these cards might not tolerate as much overclocking as when they were new, especially with Windows XP (it has no WDDM overhead) and GPUGrid.
I suggest you that after cleaning the dust / kitty hair from the coolers, you should reduce the clocks on these cards by 100MHz (50MHz core).
If it doesn't help you should do it again, and check all power connectors (including the motherboard's 24 pin and the CPU's 4-8 pin connectors) inside this host.
A driver update is also suggested, but there's a negligible possibility that the old driver causing these errors.
It's not the drivers. I have identical cards on similar rigs doing fine with the same drivers.
And uhh, I had actually tried to downclock them.
I just reset the rig, rebooted, and set Precision to defaults.
Opened it back up to GPUGRID...
We shall see. |
|
|
|
Just wanted to pass this along....
If you are a Sams Club member or know somebody who is....
This is an amazing bargain. Less than 2 bucks a can for duster spray.
I don't believe I have ever seen it this cheap.
I go through a lot of it, what with 9 computers, 24 GPUs, and 3 cats.
Kitty fur removal is a fact of life here.
I scored a flat of 24 cans...
My gurl Lori has a membership and I cashed in on it....LOL. |
|
|
|
Kitties checking again.
This is something I find wonderful.
I have lived in alternative lives other than my own for many years.
Upon my passing, I just might live forever upon these boards.
Astrid...the kitty gurl.
I did not realize there was a Broadway show based on the flick.... |
|
|