Hi,
It's bin a while since i ran seti.
I started some things up again and installed the optimised apps from lunatis (0.34b).

I ran this for a few weeks and now i hit some problems.
Maybe someone has encounterd the same?
(Tried to search for "ati driver not responing", but didn't find anything.)

And that's what happens with some tasks (seti@home v7) that run on my ATI 5870.
The task begins and at some point it stops and the catalyst driver pops up from the systemtray showing that message.
Result is a task that stopped blocking the other ati tasks in setiathome que.
I have to suspend and restart setiahome to restart.
The task will continue for a little while resulting in the same state of the driver.
after i cancel that task the next will start crunching and ends without error.
So it's not every task that locks up the driver.
Is this a known issue for the app in the lunatics .43b installer?
Or could it still be my ati card/driver. Or do i have to tweak the configfile?
Newest catalyst installed v15.7.2.
Thanks

Do you have a CPU core free ?
The OpenCL apps need some free CPU cycles to work properly.
You can also try to add -hp in your mb_cmdline_win_x86_SSE2_OpenCL_ATi_HD5.txt file.

I also suggest to add -sbs 256 to use more VRAM for the buffers.

---

With each crime and every kindness we birth our future.

Yes. That was the first thing that i thought about and you mentioned it once before.
It even happens with more than enough cores free (50 % used or just 1 core in use(=75% cores free)

The options for the app are new for me, so i will try
thanks

If that doesn`t help add -no_cpu_lock to disable cpu affinity mode.
This way the app is not bound to a specific CPU core.

---

With each crime and every kindness we birth our future.

Hi,
It's bin a while since i ran seti.
I started some things up again and installed the optimised apps from lunatis (0.34b).

I ran this for a few weeks and now i hit some problems.
Maybe someone has encounterd the same?
(Tried to search for "ati driver not responing", but didn't find anything.)

And that's what happens with some tasks (seti@home v7) that run on my ATI 5870.
The task begins and at some point it stops and the catalyst driver pops up from the systemtray showing that message.
Result is a task that stopped blocking the other ati tasks in setiathome que.
I have to suspend and restart setiahome to restart.
The task will continue for a little while resulting in the same state of the driver.
after i cancel that task the next will start crunching and ends without error.
So it's not every task that locks up the driver.
Is this a known issue for the app in the lunatics .43b installer?
Or could it still be my ati card/driver. Or do i have to tweak the configfile?
Newest catalyst installed v15.7.2.
Thanks

I did have issues with my 6950, though I don't think I got that particular error. It started after upgrading my video driver. I found going back to 13.12 cured my issues. Might be worth a looksee.

P.

---

Hi Mike, Phil,

Sorry for the late responce.

@Mike: I added -hp and -sb 256 and that seems to work.
I didn't add -no_cpu_lock (yet).
But won't it make more sense to add this option "as a standard feature"?

@Phil: Going back to an older driver .. If i encounter this problem again I will do that. I use this Pc no only for crunching.

After downloading new tasks, Boinc will give a predicted run time. I have two different ones for the GPU. (both v7) one with a run time of about 9 minutes and 1 with a runtime of about 20 minutes.
It occured with the ones with a runtime of about 20 minutes.

Thanks to you both!

@Mike: I added -hp and -sb 256 and that seems to work.
I didn't add -no_cpu_lock (yet).
But won't it make more sense to add this option "as a standard feature"?

I will talk to Raistmer about it.

Your driver should be fine for your card.
HD 6xxx cards are different architecture.
Those cards always were tricky.

---

With each crime and every kindness we birth our future.

@Mike: I added -hp and -sb 256 and that seems to work.
I didn't add -no_cpu_lock (yet).
But won't it make more sense to add this option "as a standard feature"?

No it doesn't. It was that way before and much more cards experience lags and processing stalls when Window$ allowed to do CPU scheduling. So from last versions CPUlock is default computation mode.