my client is bizzy with 22ap11ae.21036.6611.6.33.88_0 ( opencl_nvidia_SoG) and it's starting to fail.
remaining time says 2 minute 9 but after 2 minute 9 nothing changed and remaining time starts to add up till deadline is reached and block is aborted , this been going on for the past few numbers that i've been watching whats going on in this serie of blocks.

My systems processed all those WUs using SoG with no issues.

---

Grant
Darwin NT

my client is bizzy with 22ap11ae.21036.6611.6.33.88_0 ( opencl_nvidia_SoG) and it's starting to fail.
remaining time says 2 minute 9 but after 2 minute 9 nothing changed and remaining time starts to add up till deadline is reached and block is aborted , this been going on for the past few numbers that i've been watching whats going on in this serie of blocks.

Timminator2 first reported this problem, then Robert Miles reported the same problem on a different series of tasks. Might I question that you are running on Windows 10 with the latest Nvidia 436 drivers? This is the common factor in these tasks. All the problem tasks are Arecibo VHARS of angle range 2.7. All tasks error out because of exceeding the compute time limit. The host can process other types of task with no problems.

https://setiathome.berkeley.edu/forum_thread.php?id=80859&postid=2009430

I have suggested rolling back to earlier drivers as a fix.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Such symptoms usually mean video driver restart. App doesn't get informed about such event, last OpenCL runtime call just never returns. Hence abortion by deadline reaching.
To change driver is good advice provided app worked OK with another driver version. And to narrow area where to find issue I would recommend to add (temporarily) -v 2 option.
Also there was special debug build that reports each OpenCL call into stderr - that would be ideal to see where exactly problem occurs.
From OS side-check system log to see if driver restart events had place.

---

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

Same problem here with Aricebo GPU tasks only.

Windows 10 Pro, GTX1660Ti, Stock apps.

Problem occurs with nvidia drivers released in August 2019. (436 series).
All Aricebo CPU tasks and all Green Bank tasks run fine.

All tasks run fine with nvidia drivers released in July 2019. (431.36)

---

Same problem here with Aricebo GPU tasks only.

Windows 10 Pro, GTX1660Ti, Stock apps.

Problem occurs with nvidia drivers released in August 2019. (436 series).
All Aricebo CPU tasks and all Green Bank tasks run fine.

All tasks run fine with nvidia drivers released in July 2019. (431.36)

Forgot to mention that it did not matter if it was a SoG or cuda application.

---

Found myself going back to previous driver 430.86 as new driver 436.15 was stopping and restarting the same Aricebo GPU task.. (nothing was aborted, just kept restarting from scratch) Everything running fine again..

Update :
436.15 driver has troubles with SoG
436.02 driver has troubles with SoG
431.60 driver is OK for my system Win10 pro - Gtx1080Ti

if you have troubles to get the 431.60 installed due to system check failing when installing the driver.
then use DDU ( google it ) and uninstall GPU drivers without restart ( also turn off internet ) , when finished install the 431.60 driver and it will succeed. turn on internet and happy crunching times are back..

I'm having the exact same issues. Hoping the next NVIDIA driver release fixes things.

---

SETI@home classic workunits 103,576
SETI@home classic CPU time 655,753 hours

4 units of the 22ap11ae serie done, so it's working again

Btw Keith Thanks for the tip :D

Happy crunching.

Going back to an earlier version driver (431.60) appears to have solved the issue.
This is the first time that I remember an Nvidia update causing a problem.
Thanks to the suggestions here I was able to install the older driver successfully.

Deductive reasoning indicated the driver was likely the cause of the issues. Simple fix to prove the case. Pretty sure it is the new integer scaling function in the driver. Nvidia likely didn't test the features outside of testing on the old pixel mapped games. Probably didn't even consider people use their cards for numerical crunching too besides just gaming.

Anybody report this problem to Nvidia yet?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Deductive reasoning indicated the driver was likely the cause of the issues. Simple fix to prove the case. Pretty sure it is the new integer scaling function in the driver. Nvidia likely didn't test the features outside of testing on the old pixel mapped games. Probably didn't even consider people use their cards for numerical crunching too besides just gaming.

Anybody report this problem to Nvidia yet?

yes i did :) told em to contact the people from seti@home and or Boinc

Thanks for the reminder!
Nvidia will not do anything if they are unaware of the problem.
I did report the issue originally but will follow up with reports on the new driver.
I think you are correct that no one at Nvidia thought that anyone would be using their cards for anything other than video games and cryptomining.
It is important that everyone who encounters this issue report it to Nvidia through their feedback page. Hopefully, it will be resolved soon.
(But after the second flawed release I am not holding my breath.)

Version 436.30 is out today. I wonder if nVidia fixed things....

Version 436.30 is out today. I wonder if nVidia fixed things....

Be the guinea pig and report back.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Version 436.30 is out today. I wonder if nVidia fixed things....

Be the guinea pig and report back.

No mention of it being fixed in the release notes, but there's also no mention of it in the existing issues notes either.

---

Grant
Darwin NT

I doubt seriously if they even consider any use other than graphics. Unless there is a specific note addressing the failure of the driver with compute loads, I would avoid the drivers.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I doubt seriously if they even consider any use other than graphics. Unless there is a specific note addressing the failure of the driver with compute loads, I would avoid the drivers.

Remind me, weren't they trying to do real time analysis of data coming in? Hopefully no one updates the drivers....

I doubt seriously if they even consider any use other than graphics. Unless there is a specific note addressing the failure of the driver with compute loads, I would avoid the drivers.

Remind me, weren't they trying to do real time analysis of data coming in? Hopefully no one updates the drivers....

Not sure I understand the question. I believe the problem with the 436 drivers is the experimental integer scaling that is implemented. That feature is to make the bit mapped arcade games of the past look good on 4K monitors. It has nothing to do with compute. Except I think it is messing up compute somehow.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)