Questions and Answers :
Windows :
GT 640 - "No CUDA-capable NVIDIA GPUs found" why?
Message board moderation
Author | Message |
---|---|
David Send message Joined: 17 Aug 10 Posts: 5 Credit: 11,983,709 RAC: 0 |
It's sad that SETI is not using my video cards capabilities. I tried running BOINC with elevated privelegs. I'm using only the latest NVIDIA drivers. |
Gatekeeper Send message Joined: 14 Jul 04 Posts: 887 Credit: 176,479,616 RAC: 0 |
It's sad that SETI is not using my video cards capabilities. I tried running BOINC with elevated privelegs. I'm using only the latest NVIDIA drivers. Since your computers are hidden, it's impossible for us to get any ideas of what might be wrong. Unhide them and also post the first 20 or so lines of your event log for the system. (CTRL+Shift+E from advanced view) |
David Send message Joined: 17 Aug 10 Posts: 5 Credit: 11,983,709 RAC: 0 |
I think I might have found the answer. According to: http://developer.nvidia.com/cuda-gpus GT 640 (GDDR5) GT 640 (GDDR3) GT 640M GT 640M LE are supported for CUBA. My card is a vanilla GT 640 w/ DDR3 memory. I wish the NVIDIA page has has these specifics back when I bought the card. :-( |
David Send message Joined: 17 Aug 10 Posts: 5 Credit: 11,983,709 RAC: 0 |
I decided to try one last thing. I removed BOINC from my machine. I used RevoUninstaller to make sure all traces were gone. It didn't find one of the directories so I manually removed it. Then I reinstalled Boinc, added Seti@home as a project, then added the lunatics installer. Now, for some reason, it's sees the video card and I'm good to go. |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
there are several apps for the nvidia GPU. the GDDR3 CUDA should work just fine. Please restart BOINC and show us the first 30 lines of your event log as requested before In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
What I think happened is that you first installed BOINC as a service. When BOINC is installed as a service, WINDOWS will separate the limited user account that BOINC created for itself from running in the same session as the drivers and services are run from. Therefore BOINC will be unable to detect the GPU. By uninstalling and completely removing all remnants of BOINC, you got rid of the registry entry that would've told BOINC that the last time you installed it, you did so as a service installation. Thus the next time you started the installer, it installed BOINC in its default form of not as a service, and therefore BOINC now found your GPU. Had you just simply posted the start-up log as was requested, someone would've seen this and given the simple answer to uninstall, reinstall and to click Advanced in the third screen in the installer, to then uncheck the "Service Install" option, before continuing the installation. Now you threw out a couple of hundred tasks that will have to time out and be resent, while the solution was so very simple. |
David Send message Joined: 17 Aug 10 Posts: 5 Credit: 11,983,709 RAC: 0 |
A couple hundred tasks is nothing compared to the thousands lost during the time this problem persisted (7+ months worth of work) till I checked on it. Or the millions of tasks not done from the thousands of computers out there that currently have the service installed and don't know that their machine is not being used to it's full potential. This just illustrates a problem with the installer. |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
we aren't talking about everyone else we're talking to you. We want to help everyone we can but it takes the user to provide info so problems can be solved. The Daemon problem exists and probably should be addressed with the installer with warnings etc about the use of GPU on a service install. In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Gatekeeper Send message Joined: 14 Jul 04 Posts: 887 Credit: 176,479,616 RAC: 0 |
A couple hundred tasks is nothing compared to the thousands lost during the time this problem persisted (7+ months worth of work) till I checked on it. Or the millions of tasks not done from the thousands of computers out there that currently have the service installed and don't know that their machine is not being used to it's full potential. It's a problem with the installer because you didn't read the instructions carefully? |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
You mean this? |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I was going to respond to you blaming the installer, but I think Jord's pic drives home the point nicely. Had you read, you would have known about this. It isn't the installer's fault for offering you a choice and clearly telling you that the service option doesn't work on Vista and newer. |
bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0 |
I was going to respond to you blaming the installer, but I think Jord's pic drives home the point nicely. Had you read, you would have known about this. It isn't the installer's fault for offering you a choice and clearly telling you that the service option doesn't work on Vista and newer. I thought he was referring to himself as the installer (self-deprecating humor). Maybe I was wrong? |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
That's certainly one interpretation of what he said. Somehow I doubt he was blaming himself, but I'll let him clarify. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
..on Vista and newer. Any Windows. When used on Windows XP, the GPU will also not be detected. But really, blaming something on the installer is too easy. By the time you've gotten to the installer, you've had two chances already to read all about the idiosyncrasies of GPUs and Service Installations: Going to http://boinc.berkeley.edu/download.php there is: 1. this link to the Release Notes, where it specifically says: Due to problems with up-to-date GPU drivers causing BOINC to crash or hang, it was decided that for all versions of Windows the GPU detection will no longer work when BOINC is installed as a service, or protected application execution. This may change in a future version, but only after the GPU manufacturers have adjusted their driver code. So even in Windows 2000 and XP you can now no longer install BOINC as a service yet still have it detect your GPU(s) and run work on it. This change is present from 6.12.38 onwards. 2. this link to GPU computing, where it says Warning: On Windows do not install BOINC in Protected Access Execution (PAE) mode aka service mode (6.4.5 - 7.0.28) or Service Install mode (7.0.64 and above). If you do, BOINC will not be able to detect or use your GPU. Earlier I added a bold warning and some version numbers for the different ways that the service install is called, but the rest of the text is as it has been for months. Not reading the documentation and then blaming things like this on something in the installer, is cheap. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
Oh, I wasn't aware that they changed it for all Windows OSes. Thanks for the info. |
David Send message Joined: 17 Aug 10 Posts: 5 Credit: 11,983,709 RAC: 0 |
It's sad and illogical. BOINC has a problem and people keep trying to find faults elsewhere. I've been working in the software business for over 20 years and people never seem to get their heads out of their asses. Lazy, short-sited mentality: "it's easy...just do this" or "or you just done X you won't have had this problem". Think about the software and what you can do to make it foolproof. That's what you should be spending your energy on. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
What problem does BOINC have? If you've truly spent 20 years in software development, you know there's no such thing as fool-proof. The problem is with the fact that Windows has moved the video driver out of Ring 0 (kernel) and into Ring 3 (user) space to reduce the number of driver crashes causing BSODs. Because of this, many newer drivers are designed to meet WHQL certification on newer OSes, and are simply back-ported to OSes that are going out of support (2000,XP). Because of this fundamental change in the way the video driver works, BOINC has been unable to reliably use service installs to allow GPU usage (in fact, it simply can't be done in Vista and newer). Perhaps fully understanding the scope of the problem might help you to understand why the software works the way it does. Stating that you've worked in software development for over 20 years means I have higher expectations on your part to know that any fundamental change in the OS can have an adverse affect on your application. In short, this is not a BOINC problem. Microsoft changed the way Windows works with drivers to increase stability, which requires a change in application that attempt to use functionality that is no longer there. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Think about the software and what you can do to make it foolproof. That's what you should be spending your energy on. I am voluntarily spending lots of my free time on the documentation and on testing the software. Since you think you can do better, please email David Anderson to get: 1. An alpha test account. 2. An account on the official BOINC Wiki to add to the documentation. Then show what you can do. I bet you won't email David. Not a peep. |
©2024 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.