Hi,

Most of the Nathan's wu cancels after several hours of processing.
Can you have a look at this problem.

Running all my computers with windows-xp-pro and with gtx295 etc.

Good luck

---

Ton (ftpd) Netherlands

Hi I have also problems with these tasks, the Linux Ubuntu 11.10 + GTX295.

When done as I can that I have running, kill any discharge of this type of work, are a problem for my team.

If you find or report a solution will be appreciated. Greetings.

Hello: Problems continue with these tasks and it seems that no project manager cares, would be to please any comments about it or if we are the only ones affected...??

It is becoming impossible to work in GPUGRID unfortunately. Greetings. Greetings.

Nathan tasks are crunching OK here on Ubuntu 11.10 and GTX 570. I have crashed a few Nathan tasks lately but that is due to some testing I am doing on my computer. When I look at the list of results for each EU it appears many crunchers are having trouble with Nathan tasks.

Still not any answer from the team.

It is not correct to handle this way.

I still cancel all nathan-wu at any machine when downloaded.

Can i expect an answer before the end of this month???

---

Ton (ftpd) Netherlands

Gentleman, I apologize. I had just left for personal vacation for two weeks on Dec 22nd and did not see this thread when I returned. I will try to have some answer by the end of the week. Sorry for the delay.

I the same problem was here.
I had to underclock factory overclock from 800 to 790 (GTX560Ti), these tasks run with no problem now.

I had to underclock factory overclock from 800 to 790...

Bad numbers, from 900 to 890.

After a little investigation, here's what I have so far:

1) Looking at failed work units for both ftpd and Carl, "NATHAN" work units are not failing any more than other work units. If you look through failed wu's for your account, you'll see that all types of jobs are failing with similar errors. These wu's are all very different, so if it were a problem with one type we would see some correlation there. We do not.

2) I have showed the errors to the technical members of the team, and their first thought was that overclocking with the cards is the cause, even if it is a factory overclock. nenym also reports that decreasing the clock rate by 1% solved his problem of failures.

Considering all this, I suggest you attempt to decrease the clock frequency slightly and see if that helps with failed WUs. A 1% or 2% decrease is very small, and the time lost from slower computation will be made up from not spending hours computing for a WU that will fail. I will look at it some more, because I want to be sure I am not missing something. For now, it looks like it's caused by hardware, not a problem with the simulation itself. I will let you know if I find something that indicates otherwise. Please let me know if changing the clock speed helps the problem.

Nate

Thx for explaining the question.

On my GTX295 I never changed anything since five years.

I will try again.

---

Ton (ftpd) Netherlands