Intel Graphics 630 cuda stopped working

Questions and Answers : Windows : Intel Graphics 630 cuda stopped working
Message board moderation

To post messages, you must log in.

AuthorMessage
tkelley@alum.mit.edu

Send message
Joined: 3 Oct 19
Posts: 2
Credit: 5,816
RAC: 0
United States
Message 2025146 - Posted: 27 Dec 2019, 3:35:24 UTC

I've been happily running GPU tasks on my Win10 desktop until the Intel graphics drivers stopped being compatible with SETI@home. The last driver that worked properly on Intel Graphics 630 was 25.20.100.6471; I've tested nearly every one since and BOINC Manager shows "missing GPU" for all GPU tasks.

I've been willing to forgo updating the graphics driver since then, but now I have a new problem: my brand new laptop won't install that version of the driver; apparently it's too old. So even though the computer is perfectly capable of running GPU tasks, the driver won't let it.

Any ideas? The Intel site doesn't have any way I could find to log a bug. Was there some deliberate change in the API and SETI or BOINC just hasn't caught up?
ID: 2025146 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2025160 - Posted: 27 Dec 2019, 8:42:19 UTC - in response to Message 2025146.  

A couple of things:

1. Intel GPU don't do CUDA, that's something that only Nvidia GPUs do.
2. You have at least two accounts. The one you post with at present holds an Android device only. The one you talk about is this one.
3. The task list for one of your systems shows it has an Intel 630 GPU and that until 27 Dec 2019, 5:59:40 UTC, it's returning work in a normal fashion.
4. The task list for another system shows it never had its Intel 630 GPU detected.

As for general trouble shooting GPU problems, do check you didn't inadvertently install BOINC as a service (daemon) because then it won't be able to detect GPU drivers either.
It's not so much that the driver stopped being compatible with Seti, or with BOINC. It's more that the driver stopped being compatible with your hardware, or that Windows 10 updated it and those drivers can lack specific parts required, like the OpenCL part of the driver.

Is something keeping you from returning to the previous working drivers?
Or does Windows then auto-update them? Because then you'll have to tell Windows to stop auto-updating your drivers for you. Which I understand on Home versions is notoriously impossible to do, but you have Pro, so shouldn't be a problem (until the next Windows update). In case you can't find a download link anymore for your preferred drivers, it's https://downloadcenter.intel.com/download/29274?v=t
ID: 2025160 · Report as offensive
tkelley@alum.mit.edu

Send message
Joined: 3 Oct 19
Posts: 2
Credit: 5,816
RAC: 0
United States
Message 2026163 - Posted: 3 Jan 2020, 20:31:49 UTC - in response to Message 2025160.  

It's the one that's never had its Intel 630 detected that's the issue. The driver version with working opencl predates the machine by a long enough time that it won't let me install it. I've suspended updates to the older Intel 630 machine so that I can continue to run GPU tasks.

So, if opencl suddenly stopped working on this driver after a certain version, I guess I'll just keep the one machine on the older driver, but my new laptop will never be able to run GPU tasks. I was hoping there was some way to log a bug with Intel letting them know that they broke opencl in these drivers, but I haven't been able to find it.

Thanks for your help.
ID: 2026163 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2026170 - Posted: 3 Jan 2020, 21:23:05 UTC - in response to Message 2026163.  

ID: 2026170 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2026181 - Posted: 3 Jan 2020, 23:28:31 UTC

This could be one where the DCH version of the drivers has outgrown the space allocated in BOINC for all the features. The next version of BOINC (now overdue by some 6 months) will have #3183.
ID: 2026181 · Report as offensive

Questions and Answers : Windows : Intel Graphics 630 cuda stopped working


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.