Yesterday I installed a new Nvidia 1660TI GPU. I installed MB8_win_x86_SSE3_OpenCL_NV_SoG_r3557 app using the  Lunatics Win64 v0.45 beta6 installer. It all went well and the gpu started crunching. Cut to a couple of hour later when opened GPU-Z to look at the temperatures when I noticed that the CPU clock is down and GPU utilization is down to 0%. When I opened BOINC it looked like it was working ok, but the estimated time left on the current units was in the days - 4 or five, or something.

I killed everything and switched to r3584 app from Mikes world. Not sure if workunits were flushed. Cut to a couple of hours later and the GPU was again at 0% and the units were estimated at 95 days.

Switched to CUDA50 and have been crunching for more than 20h without issues.
Drivers are latest Game ready drivers from Nvidia.

Is this behavior familiar to anyone? Is there a point in trying to diagnose this? I would not even know where to start.

---

It's hard to say something with your computers hidden.

But i imagine is because you select the wrong app for your GPU, you need to select SoG not the CUDA on the Lunatics installer or maybe because the driver your use. FYI There are a incompatibility with the latest NVidia driver and SETI or other projects.

BTW Ask for help with the hosts hidden is like go to the doctor and not allow him to exam, is some kind of an impossible task.

---

A couple of other things to consider - first, "game ready" may not have everything required to do the computational work, and there is a "known problem" with at least one recent release see https://setiathome.berkeley.edu/forum_thread.php?id=84694
Second, it is not unusual t see very extended estimated run times when first installing optimised applications, but very unusual to see such a large wrong estimate (more normal would be a couple of hours).

However, as your computers are hidden it is very difficult to be more precise.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

This is the computer in question. I should reiterate that I successfully calculated multiple work units with both r3557 (e.g. this task) and r3584 (e.g. this task) SoG apps. It is just that they got stuck after a relatively short while.

[edit]rob smith, I just got into the thread you linked to and this very much feels like what I'm experiencing. I'll try to roll back my drivers and see what happens. Thanks!

---

This is the computer in question. I should reiterate that I successfully calculated multiple work units with both r3557 (e.g. this task) and r3584 (e.g. this task) SoG apps. It is just that they got stuck after a relatively short while.

As Rob stated, you are running incompatibile Windows drivers. Your mistake was installing the latest. The last known good drivers are the 431 series. Any later series drivers causes the extended run times you are seeing. Backlevel to 431 series and all will be well.

---

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

A proud member of the OFA (Old Farts Association)

Will do. Thank you all!

---

This is the computer in question. I should reiterate that I successfully calculated multiple work units with both r3557 (e.g. this task) and r3584 (e.g. this task) SoG apps. It is just that they got stuck after a relatively short while.

As Rob stated, you are running incompatibile Windows drivers. Your mistake was installing the latest. The last known good drivers are the 431 series. Any later series drivers causes the extended run times you are seeing. Backlevel to 431 series and all will be well.

Yes the driver is incompatible, but take a look at his crunched WU it said:

setiathome enhanced x41zi (baseline v8), Cuda 5.00

Was a long time i not use the Windows Lunatics apps but IIRC the fastest one are the SoG not the CUDA or that changes?

---

He was running the proper SoG app from the Lunatics installer and all was working well until he updated the drivers. He only switched to the old CUDA50 app when troubleshooting. Once he reverts to a 431 driver he can revert back to the proper SoG app.

---

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

A proud member of the OFA (Old Farts Association)

Why would I upgrade every time there is a new driver, when the old one works perfectly? Newer drivers will not make the GPU crunch faster, or better.

Well you may need to update due to security issues.

https://nvidia.custhelp.com/app/answers/detail/a_id/4841/~/security-bulletin%3A-nvidia-gpu-display-driver---august-2019

Anything prior to 431.60 is vulnerable.

But it is probably nothing to worry about.

I am a gamer and I do need the latest drivers, so I have stopped crunching on GPU's on my Windows machines.

nothing about being a gamer means you "need" the latest drivers. your systems would be perfectly fine running the 431.60 or 435 (sorry 435 must be linux only version) drivers. most people are not even at risk of the vulnerbilities without the security patches and the worst of them requires an attacker to have physical access to the system.

---

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

With 436.48 most but not all Arecibo tasks take a huge time on my GTX 1060, while all Green Bank tasks work perfectly. I had to abort a number of Arecibo tasks. Einstein@home tasks work perfectly.
Tullio

---

With 436.48 most but not all Arecibo tasks take a huge time on my GTX 1060, while all Green Bank tasks work perfectly. I had to abort a number of Arecibo tasks. Einstein@home tasks work perfectly.
Tullio

Why not just roll back to the 431.60 driver and avoid aborting work all together?

Cheers.

...and when "rolling back" to an earlier driver version do a "clean" installation - the option is in the "advanced" menu.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

From a post mortem view, most Arecibo tasks fail after a very short time, so I don't have to abort them. Also GPUGRID tasks work perfectly on 436.48 and they are the most demanding on a GPU according to GPU-Z.
Tullio

---

From a post mortem view, most Arecibo tasks fail after a very short time, so I don't have to abort them.

Sorry, but that doesn't make any sense.
Looking at your Task List, there are no WU's (Arecibo or otherwise) that have failed after a short time. All of the WUs that failed, failed due to the driver. All other errors, are because you aborted the WU.

---

Grant
Darwin NT

most Arecibo tasks fail after a very short time

Not 'most'. Most tasks run to completion, in a variable amount of time.

We do get occasional runs of 'noisy' tasks (which exit after a very few seconds), or VHAR tasks (which exit after a half or a third of the normal time), but neither of these are failures.

I am using the 436.48 driver because it works perfectly on Einstein@home and GPUGRID. A part of my SETI@home tasks are run as a ScienceUnited user, so I cannot see them since I don't have that password, only a general ScienceUnited password. All GreenBank tasks work flawlessly with that driver.
Tullio
PS
I have completed 426 SETI@home tasks on ScienceUnited with zero failures
GPU hours 107.95

---

I am using the 436.48 driver because it works perfectly on Einstein@home and GPUGRID. A part of my SETI@home tasks are run as a ScienceUnited user, so I cannot see them since I don't have that password, only a general ScienceUnited password. All GreenBank tasks work flawlessly with that driver.
Tullio
PS
I have completed 426 SETI@home tasks on ScienceUnited with zero failures
GPU hours 107.95

You have 44 Errored tasks on that host. All of the ones I could see info for were Arecibo VHAR tasks.

https://setiathome.berkeley.edu/results.php?hostid=8609032&offset=0&show_names=0&state=6&appid=

---

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

Thanks. The driver on that host is 436.30 not 436.48 like on the Windows 10 PC which is not enlisted in Science United.
Tullio

---

I am using the 436.48 driver because it works perfectly on Einstein@home and GPUGRID. A part of my SETI@home tasks are run as a ScienceUnited user, so I cannot see them since I don't have that password, only a general ScienceUnited password. All GreenBank tasks work flawlessly with that driver.
Tullio
PS
I have completed 426 SETI@home tasks on ScienceUnited with zero failures
GPU hours 107.95

If those numbers 426 tasks and 107.95 hours are linked then your computer is running slowly, on a 1060 the max time I see for Seti MB tasks is under 5mins/task, since I reverted to the 431.60 driver.