Just a report; not a big deal to me.

BOINC Manager says I have an S@H opencl_ati5_SoG_cat132 task running. Last night, it was reporting 7 hours + Elapsed and 3 hours + Remaining. This morning, it is reporting 3 hours 26 min Elapsed and 1 hour 21 min Remaining.

In the Event Log, the last download of an S@H task was
8/22/2016 7:05:20 PM | SETI@home | Starting task blc5_2bit_guppi_57403_69166_HIP11048_0004.4685.0.21.44.166.vlar_1,
the night before the first reporting above.

My mb_cmdline-8.12_windows_intel__opencl_ati5_SoG.txt file:
-sbs 192 -period_iterations_num 80

Between the two reports, I put the computer to sleep for the night.

Hoping this helps someone ...

Just noticed: This behavior is identical to a task I cancelled on Tue Aug 18. That one got stuck at roughly 30% completion for a day or two. This one got stuck at 71.728% for at least several hours. I've canceled this one.

Update: Recently, I received a task for opencl_ati5_SoG_cat132. These numbers are from BOINC Manager.

This morning, the task was 32.290% complete with 3:42 elapsed and 8:07 remaining.

Tonight, it is 32.290% complete with 12:09 elapsed and 1d 02:41 remaining.

I aborted.

Look into system event log - are thre any driver restart records?

Max compute units: 3

such GPU currently has -period_iterations_num 500as default.
You slowly increase value up to 100 on aborted task. Run with defaults and report in support thread if driver restarts occur.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

EDIT: delete.

EDIT: delete.

Look into system event log - are thre any driver restart records?

Max compute units: 3

such GPU currently has -period_iterations_num 500as default.
You slowly increase value up to 100 on aborted task. Run with defaults and report in support thread if driver restarts occur.

Raistmer:

Sorry; I wish I'd seen this before the most recent task started computing.

I scanned the Event Log. It includes an entry there for downloading the subject task. No later entry looks like a driver restart, unless I don't understand the wording of one of those.

I don't know what the "Max compute units" line means. There's no line like that in the Event Log.

Yesterday, I got a new task for application opencl_ati5_SoG_cat132. When I put the computer to sleep last night, BOINC Manager gave me these stats: 33.362%, 3:15 elapsed, 6:30 remaining. Today, as the computer booted up for the day, it initially showed those numbers, then changed to: 33.362%, 1:40 elapsed, 3:45 remaining.

I've suspended.

Before the above, the contents of mb_cmdline-8.12_windows_intel__opencl_ati5_SoG.txt was "-sbs 192 -period_iterations_num 100". Unless I hear another recommendation from you, I'll drop the 100 to 10, see what happens, and maybe build up slowly from there.

Will changes to that file take effect before the next such task starts?

Thanks for the answer! I'll move future posts to the support thread.

I scanned the Event Log. It includes an entry there for downloading the subject task. No later entry looks like a driver restart, unless I don't understand the wording of one of those.

System Event log, not BOINC's one.

Before the above, the contents of mb_cmdline-8.12_windows_intel__opencl_ati5_SoG.txt was "-sbs 192 -period_iterations_num 100". Unless I hear another recommendation from you, I'll drop the 100 to 10, see what happens, and maybe build up slowly from there.

I wrote that default is 500. You run at 100. And now you want to go to 10? Wrong direction.

Will changes to that file take effect before the next such task starts?

Change take place on app restart. Either same task or new one.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.