Richard, do we need any 432.00 validation? I'm not going to redo any of my testing.

No, I think we've done that already: message 2030385.

The next testing milestone will come when Microsoft start distribution of their next driver after 432.00 - which you suggested is likely to happen with the 2003 feature update. But perhaps we should keep an eye on the February and March security rollups, in case they sneak one out early.

Hope the majority of people running Win 10 and the SoG app have updated their drivers to the latest. We are currently processing a cr*p-ton of old Arecibo VHAR tasks of angle range = 2.7
The 05dc14aa file seems to be the main culprit.

---

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

A proud member of the OFA (Old Farts Association)

We are currently processing a cr*p-ton of old Arecibo VHAR tasks of angle range = 2.7
The 05dc14aa file seems to be the main culprit.

Add 22dc09ac to that, and it looks like it's got quite a few noise bombs in there with the shorties.

---

Grant
Darwin NT

I think 442.19 has definitely fixed it!

In my testing of the 442.19 drivers, I had no problems processing VHAR work items, on my main rig (RTX 2080, GTX 980 Ti, GTX 980) using Windows 10.
All 3 GPUs acted correctly.

I can second this. Yes, I recently installed the 442.19 driver (game-ready) and started running BOINC again in the last few days and have not seen any problems running the SETI@Home SoG tasks. They have all been completing within 2-4 minutes for me (RTX 2070 Super) on Windows 10.

---

Seti@Home is working quite well with Nvidia Whql driver version 442.37 for Windows 10 Professional 64-bit. Everything seems to be ok with this release.
At least on my end, I haven't had any problems with it. Knock on wood.

i have just installed nvidia driver 442.50 and it looks like it is
working good on seti home

i just updated my driver to 445.75 and it is now not working

i just updated my driver to 445.75 and it is now not working

Because of the replica database delay, we won't be able to find/see the error messages from your tasks for another three days or more.

Please help us understand the 'not workingness of it'. Any symptoms? Any error messages / error numbers you can post?

Yuck.

I think I am noticing R475 driver 445.75 fail my OpenCL test for my 2080.

I guess I will be testing all my GPUs against:
- R440 driver versions: 442.37, 442.50, 442.59, 442.74
- R445 driver version: 445.75
... in the coming days.

Maybe run a task against the offline benchmark tool with the suspect driver to get instant error logs.

---

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

A proud member of the OFA (Old Farts Association)

445 driver is repeating the Open CL problem of several months ago. Had 1 WU run for 40 min, got comp error. Rolled back to 442 driver and all is ok.

Looks like the changes they put in place for 442.19 to fix the original problem got dropped by the development team. Or a different team was unaware of the code changes that fixed that to include it in their release build.

Someone needs to remind Nvidia again to put the code patch back in.

---

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

A proud member of the OFA (Old Farts Association)

Someone needs to remind Nvidia again to put the code patch back in.

Or they heard Seti was shutting down & decided they didn't need it in there anymore...

---

Grant
Darwin NT

Someone needs to remind Nvidia again to put the code patch back in.

Or they heard Seti was shutting down & decided they didn't need it in there anymore...

That's a pessimistic view. FYI, the tasks on other projects were failing too with the older drivers without the fix for the "Seti" tasks. Einstein for one.
It would be a shame if they pulled the code fix thinking it only applied to Seti and Seti shutting down led them to believe it was only needed for this project.

---

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

A proud member of the OFA (Old Farts Association)

That's a pessimistic view. FYI, the tasks on other projects were failing too with the older drivers without the fix for the "Seti" tasks. Einstein for one.
It would be a shame if they pulled the code fix thinking it only applied to Seti and Seti shutting down led them to believe it was only needed for this project.

I was just being facetious. Most likely the left had not knowing about the right hand and different code paths etc.
Never attribute to malice that which can adequately be explained by stupidity (i have to remind myself of this daily due to the crap going on at work at present. The Virus is a good excuse for management to do all sorts of things they never could do otherwise, and they are trying to do it all at once. If there were somewhere to go, the rats would all be jumping ship. But there isn't. So they can't. We're all just trapped rats).

---

Grant
Darwin NT

Someone needs to remind Nvidia again to put the code patch back in.

Or they heard Seti was shutting down & decided they didn't need it in there anymore...

I told them last night, although probably without enough details. We probably need many more such messages to them.

I would hope they don't require the extensive documentation and user input that the first logged complaint needed to effect a fix.

---

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

A proud member of the OFA (Old Farts Association)

I would hope they don't require the extensive documentation and user input that the first logged complaint needed to effect a fix.

Hopefully, they can try the same OpenCL section that was in the 442 drivers, then ask a few SETI@Home users to test how well that works. If it works, they might even get it fixed in the later 445 drivers.

Someone needs to remind Nvidia again to put the code patch back in.

Or they heard Seti was shutting down & decided they didn't need it in there anymore...

That's a pessimistic view. FYI, the tasks on other projects were failing too with the older drivers without the fix for the "Seti" tasks. Einstein for one.
It would be a shame if they pulled the code fix thinking it only applied to Seti and Seti shutting down led them to believe it was only needed for this project.

I know Einstein had issues with the AMD driver on RX 5700 cards, but wasn't aware that they had issues with Nvidia drivers that correlated with the same SETI fix. Can you confirm?

If it only affects SETI, and again only one WU type on one app on one OS, then really it's not worth the effort to fix again. SETI will be done in a week.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Such pessimism and defeatism!

If there's a bug in these R445 drivers, which it seems likely to be, then ...
... I for one will push for them to fix the bug.

I have not yet fully characterized the behavior that I'm seeing, and may not have time until the weekend.