I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.

With your computers hidden, it's hard to offer any useful suggestions, not having any idea of what we're dealing with.
There have been issues with any driver later than 431.60 on some Work Units, so I would suggest downloading driver v 431.60 from Nvidia (not Microsoft or any other 3rd party site), suspend crunching in BOINC, install the driver (selecting the clean install option), re-boot, wait a bit & check that the driver has installed OK (use Nvidia Control Panel) and then exit BOINC (if it starts automatically), then wait a bit, restart it, check in the Event log that your video card(s) has (have) been detected correctly, then unsuspend processing.
If it's working again, excellent. If not, unhide your system(s), and post the first 30 lines or so of the event log from after BOINC has started & we'll see what we can do.

---

Grant
Darwin NT

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.

With your computers hidden, it's hard to offer any useful suggestions, not having any idea of what we're dealing with.
There have been issues with any driver later than 431.60 on some Work Units, so I would suggest downloading driver v 431.60 from Nvidia (not Microsoft or any other 3rd party site), suspend crunching in BOINC, install the driver (selecting the clean install option), re-boot, wait a bit & check that the driver has installed OK (use Nvidia Control Panel) and then exit BOINC (if it starts automatically), then wait a bit, restart it, check in the Event log that your video card(s) has (have) been detected correctly, then unsuspend processing.
If it's working again, excellent. If not, unhide your system(s), and post the first 30 lines or so of the event log from after BOINC has started & we'll see what we can do.

Thanks, Grant! Much appreciated. Still can't get the system to recognize the GPU's even though they are working perfectly fine. Will contact Dell for a reset maybe, it should still be under warranty.

---

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.

Does the BOINC Manager Tools>Event log show them on start-up? Should be in the first 10 lines or so right after start-up.

---

The clue to your problem may be that this started just after a Windows update. Windows updates are notorious for updating drivers with ones that are lacking everything needed to do computation. While the GPU(s) will continue to display properly they cannot do work for SETI as BOINC won't detect them as being there. The solution is do get a fresh set of drivers from the nvidia website - don't go for the latest as they appear to have an issue, but for the 430.x family, do a "clean" installation (option is in the "advanced" or "custom" menu), and make sure you turn off Windows Driver up dates.

---

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

Well recently my 2 Windows 10 PC's and my laptop all updated to Windows 1903.

And surprise, all of them had the correct driver still in place afterwards, with Open CL, detected correctly by Boinc, pity I don't crunch on GPU anymore ;-)

Well recently my 2 Windows 10 PC's and my laptop all updated to Windows 1903.
And surprise, all of them had the correct driver still in place afterwards, with Open CL, detected correctly by Boinc, pity I don't crunch on GPU anymore ;-)

. . Any particular reason for stopping the GPUs from crunching? That is a lot of processing power sitting idle ...

Stephen

? ?

. Any particular reason for stopping the GPUs from crunching? That is a lot of processing power sitting idle ...

I have got used to using GeForce Experience as my "in game" video and screenshot recorder, much better than FRAPS, also it "optimises" games so you get the best playing experience for your GPU, and as such I also use the latest drivers (I let GFE update them as required). So as the latest drivers don't play well with SETI@Home I have stopped GPU crunching till there is a resolution.

It is my personal preference to have the latest drivers, I have done for years. I currently have two Linux machines I run as and when, that more than make up for the loss of the two Windows ones. I suspect as the weather gets colder I may even break out a couple of the "WOW" machines just for heat ;-)

. Any particular reason for stopping the GPUs from crunching? That is a lot of processing power sitting idle ...

(I let GFE update them as required). So as the latest drivers don't play well with SETI@Home I have stopped GPU crunching till there is a resolution.
I currently have two Linux machines I run , that more than make up for the loss of the two Windows ones. I suspect as the weather gets colder I may even break out a couple of the "WOW" machines just for heat ;-)

. . OK, curiosity satisfied ... :)

. . I was afraid you were stopping it across the board ...

Stephen

:)

Finally got a taste of secret switch sauce. Sure took long enough but thank you Mr. you know who you are. I suspect most of the ones I was given are diagnostic related and of not much use to a cruncher none the less interesting... o the drama... a few of the dozens I now have are -rtp -ffa_thresh_mult and -sync_iter and -persistent_threads. I put a few of them in my cmd file and I can confirm -persistent_threads works according to stderr. Why its not in the documentation that comes with boinc and or seti? Practically every other file in the 2 seti directories has got its own readme, copyright, gpl liscence and who knows what else.
it said: "Kernels with persistent threads will be used where possible"

look here https://setiathome.berkeley.edu/result.php?resultid=8176672587

One of the PrimeGrid applications does not play well with the 436 Nvidia driver, but works with the 431 driver and the current 440 driver. So if the Windows computers have Nvidia-based graphics and a 436 driver, you might check if installing either the 431 driver or the 440 driver fixes the problem.

Also, make sure that you get any replacement driver directly from Nvidia. Microsoft often tries to install a slightly different version that leave out support for CUDA and OpenCL, and therefore will not work for GPU computing.

I have a machine with a Nvidia GTX 1660ti and another with a Nvidia GTX 1060 the following versions of the drivers including the latest all fail to get past 0.603% completion when crunching Seti units.
for me at least 436.48 DCH, 440.97DCH, 441.08DCH, 441.66DCH wont work on either machine.

When I use 431.60DCH all works fine. Some of the latest "Super" cards need later drivers and I guess may struggle with Seti with these GPU's :(

On a different note on Radeon based Machines (580X and 590X) running windows 10 drivers crash with computation errors for me when running many Versions above 19.7.5

This happens on 3 seperate machines so its not a hardware fault.

I hope this may help with people getting frustrated like me...

---

This is a well known issue look at: https://setiathome.berkeley.edu/forum_thread.php?id=84694

You updated the video drivers to 436 and up drivers which are known to cause issues.

Revert to the 431.60 driver and your issues should go away.

---

Hi folks,
just so you know, I installed successfully on 2 computers, but on third, nothing worked... Until I found out the LIBEAY32.DLL BUG - the supplied library caused crashes. Anyhow - that was after I even installed the (7.16.3) beta. After solving the issue (upgraded LIBEAY32.DLL from C:\Program Files\Microsoft Office\root\Office16\ODBC Drivers\Redshift\lib directory!), I ran the beta for a while, but thought I downgrade to the official version, since it seemed to run slow (or somehow got fewer points than I thought it should have...?!).

But now I don't seem to be able to get the GPU reckognized (it says "GPU missing") in the official version. It seemed ok in the beta...

So - where is the latest official LIBEAY32.DLL that I "should" use?

Should I switch back to the beta 7.16.3 or stay with 7.14.2?

Any tips on how to get GPU running on my Windows 10 machine (Dell-XPS)?

with a smile
prifre

Any tips on how to get GPU running on my Windows 10 machine (Dell-XPS)?

You need to have a video card capable of processing work. Then you need to install the driver that supports that video card so it can process work.
Exit, then restart BOINC.
If everything is good, then it will find the supported devices, and start downloading work.

At present, none of your computer system have a video card capable of processing work, if they do, then you need to go to the web site (Nvidia or AMD) and download & install the appropriate driver.

Should I switch back to the beta 7.16.3 or stay with 7.14.2?

Stay with the release version. The Beta version is just that- Beta. It will still have issues.

---

Grant
Darwin NT

A few things.
First, BOINC version 7.16.3 (Beta) is not intended for general use, and probably has a bug list that is quite extensive, so you are best staying the the released 7.14.2.
as while there are a few bugs, most of them do not affect the average user.
Next - you have a couple of laptops neither of which is showing a GPU being installed, and the Dell XPS description overs a whole range of laptops, so can you be more specific?
Getting your GPU working. If you are talking about the Intel built-in one, don't bother as they are generally better at producing heat than work, if it has a "third party" GPU (from either nVidia or AMD) then you need to have the correct drivers installed, which are generally not those that MS provides.

As far as I'm aware the problems with libeay32.dll are somewhat operating system version dependent, so you need one that the OS talks to and thus can be very machine specific - it sounds as if you have found the one that works for you (but it may not work for others).

---

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

Gee responses on this forum are fast ;-)
I got GPU working by ... uninstalling and installing 32-bit version (never tried that yet - didn't have to replace LIBEAY32.DLL then, but...- that didn't get GPU working). But switching to the 64-bit version (and updating LIBEAY32.DLL with the MS office version) somehow got GPU working fine this time!! (Probably due to real restart!? :-)
So everything works great now. Big thanks for all (fast!) help!

I got GPU working by

Do you have another account, as none of the systems on this one show any suitable GPU.

Computer ID                                   CPU                                                               GPU
ID: 8873527     Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz     [Family 6 Model 158 Stepping 13] (16 processors)    --- 
ID: 8873866     Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz   [Family 6 Model 126 Stepping 5] (8 processors)      --- 
ID: 8872958     Intel(R) Core(TM)2 Duo CPU E8235 @ 2.80GHz  [x86 Family 6 Model 23 Stepping 6] (2 processors)   --- 

---

Grant
Darwin NT

ID: 8873866 is now showing (and using) the built-in Intel GPU, it just took a bit of time for the host details to update to reflect.

---

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

ID: 8873866 is now showing (and using) the built-in Intel GPU, it just took a bit of time for the host details to update to reflect.

. . If the Intel GPU is the only one in the machine then I must echo your sentiments. The CPU alone will be more productive than using the GPU.

Stephen

:(

Dear All
I got -6 error with v8.22, my nividia driver version is already downgraded to 431.60.
I'm just wondering that anyone have any ideas?
Cheers


https://setiathome.berkeley.edu/result.php?resultid=8378163220

Name blc56_2bit_guppi_58692_60105_HIP22741_0027.5876.818.21.44.34.vlar_0
Workunit 3809574761
Created 27 Dec 2019, 11:17:15 UTC
Sent 27 Dec 2019, 16:12:03 UTC
Report deadline 18 Feb 2020, 21:11:45 UTC
Received 28 Dec 2019, 2:09:27 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -6 (0xFFFFFFFA) Unknown error code
Computer ID 8862418
Run time

CPU time

Validate state Invalid
Credit 0.00
Device peak FLOPS 1,993.50 GFLOPS
Application version SETI@home v8 v8.22 (opencl_nvidia_SoG)
windows_intelx86

Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -6 (0xfffffffa)</message>
<stderr_txt>
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided OpenCL device ID used

Build features: SETI8 Non-graphics OpenCL USE_OPENCL_NV OCL_ZERO_COPY SIGNALS_ON_GPU OCL_CHIRP3 FFTW USE_SSE3 x86
CPUID: Intel(R) Core(TM) i7-9700KF CPU @ 3.60GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 FMA3 SSE4.1 SSE4.2 AVX
OpenCL-kernels filename : MultiBeam_Kernels_r3584.cl
CL file build log on device GeForce RTX 2070


INFO: can't build program from binary kernels, code 0 , recompiling from source...
Error : Building Program (binary, clBuildProgram):main kernels: not OK code -5
CL file build log on device GeForce RTX 2070


Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided OpenCL device ID used
SETI@home error -6 Bad workunit header
!swi.data_type || !found || !swi.nsamples
File: ..\seti_header.cpp
Line: 216


</stderr_txt>
]]>