1) Message boards : Number crunching : Need to quit (Message 45008) Posted 15 Dec 2010 by mdawson Post: I tried to detach but the detach button is grayed out. Same for Einstein, although with Collatz it will light up.

2) Message boards : Number crunching : cuda_opend failed (Message 44975) Posted 13 Dec 2010 by mdawson Post: I changed the value from 1 to 0 and that didn't help on "use all gpu's" in the cc_config.xml file. Is there a different way to word this so that the 8600 doesn't grab more WU's?

3) Message boards : Number crunching : cuda_opend failed (Message 44973) Posted 13 Dec 2010 by mdawson Post: I don't suppose there is a fix for this, is there? I've got 3 monitors hooked up so I can't just yank the card out, and I'm not going to buy a new card to get around this, so maybe I should be looking for a new project? I'm sure it's going to clog things on your end with all of my computation errors being returned.

4) Message boards : Number crunching : cuda_opend failed (Message 44965) Posted 12 Dec 2010 by mdawson Post: Correction, GPU-Z indicates that the video engine load for both cards is 0%, but one of them (device 0) is crunching. I don't know, maybe that's the 260, maybe not. I've got a cold and I am not seeing clearly.

5) Message boards : Number crunching : cuda_opend failed (Message 44964) Posted 12 Dec 2010 by mdawson Post: I'm already running the current version of BOINC, but did load the newer nVidia driver today. I'm still getting massive computation errors. Oddly, my older 8600 GT is working fine. My newer GTX 260 is not.

6) Message boards : Number crunching : Interesting thing happened this weekend (NOT!) (Message 42749) Posted 11 Oct 2010 by mdawson Post: Actually no, I didn't have that file in my working recently reinstalled directory. However, I went looking in the backups that Windows made and I found it. Copied it over and restarted BOINC. Voila! She's flying now! Thank you. That was just what I needed.

7) Message boards : Number crunching : Interesting thing happened this weekend (NOT!) (Message 42732) Posted 10 Oct 2010 by mdawson Post: Somehow my registry got trashed on Win 7 x64. Restores wouldn't work, nor did repairs. I had to reinstall completely. One thing I've noticed now that most everything is backup and running, is that BOINC Mangaer is refusing to run CUDA code on my 2nd video card. 10/10/2010 1:25:02 PM NVIDIA GPU 1 (not used): GeForce 8600 GT (driver version 19713, CUDA version 3000, compute capability 1.1, 496MB, 38 GFLOPS peak) It's not a big producer, but it did contribute before the crash. How can I get it back?

8) Message boards : Number crunching : GPU Credit Question (Message 42004) Posted 9 Sep 2010 by mdawson Post: Kashi, I read your reply and it got me to wondering about my cards. GPU-Z indicates that my "little" card has a 0% load. My "big" card is at 89%. Both of my cards (nVidia) have two outputs. The "big" card, a GTX 260 has both outputs connected to 2 physical monitors. The "little" card, an 8600GT has only one output connected to the secondary input of the right monitor. (The left monitor has only one input, the right monitor has two inputs connected, but only one in use at any given time). If I were to follow your reasoning, the fact that the 2nd card is plugged into the 2nd input of the monitor, and is generally never activated, would be the reason why I have 0% load on the "little" card, correct? I have my desktop spread across all 3 monitor inputs. That was the only way to get the card recognized. I'm thinking that I should invest in dummy connectors as well. You say you made them? Are there directions anywhere, or can they be purchased from Fry's or somebody like that? Oddly, BOINC seems to indicate that both cards are operational.

9) Message boards : Number crunching : GPU wu's on GTX260 (Message 41802) Posted 28 Aug 2010 by mdawson Post: Alexander, I'm running 2 nVidia equipped cards. I initially went thru the same angst that you are currently having. The problem is the gpu app for E@H. It has very little need for gpu crunching and as a result, just sits there idle most of the time, tying up not only the gpu, but a cpu core as well. The solution is to run a different app on your gpu and E@H on your cpu. I'm running MW@H on both of my gpu's, and E@H on each core of my quad. As long as I have supply, this machine just hums right along @ full bore.

10) Message boards : Number crunching : Am I the guilty party? (Message 37997) Posted 4 Apr 2010 by mdawson Post: I figured out how to regulate who gets what. I'm now set up to run Einstein on the cpu's, and MW on the gpu's. Both apps seem to favor the cruncher they're destined for.

11) Message boards : Number crunching : Am I the guilty party? (Message 37996) Posted 4 Apr 2010 by mdawson Post: I do run SETI as well, although I haven't found a reliable way of saying MW use gpu only and SETI use cpu only. I'm not sure how I did it, but before I got back in here, I was crunching Einstein on the cpu's, and SETI on the gpu's. Now, I've dropped Einstein and it seems there's a fair amount of MW cpu wu's running with the occasional SETI wu sneaking into the cpu's and gpu's. I wish there was a better way of managing this.

12) Message boards : Number crunching : Am I the guilty party? (Message 37989) Posted 3 Apr 2010 by mdawson Post: That kinda' takes the fun out of it, doesn't it? I was just curious. I seem to be blowing through most MW cpu wu's in less than 8 hrs, and the CUDA wu's in about 30 mins or less. That was the only one I'm aware of that took that long. Thanks for all the responses.

13) Message boards : Number crunching : Am I the guilty party? (Message 37977) Posted 3 Apr 2010 by mdawson Post: There's a note about a server shutdown on the main page, and in that note it is written that single precision GPU users are not wanted here. I've recently picked up with MW and started receiving GPU wu's and have processed an enormous amount of them. The trouble is, I have an Nvidia card, and I was led to believe that it was only single precision. Imagine my surprise when I was able to d/l wu's for the Nvidia gpu's and then imagine more surprise when I found out that this work may be interfering with the normal operation of this project. I'm not trying to scam anybody. In fact, I've done nothing out of malice, so I need a determination. Can I use my Nvidia gpu's for this project or not? I've been with SETI for years, as well as Einstein and I was looking for a change. I can always take my compute cycles somewhere else if that is what is called for. Someone please let me know. On a side note: I had a CPU wu that took just over 21 hrs. I haven't had a wu from anybody in nearly a decade that took that long. My 486 used to take that long, but I'm running a quad core now with loads of ram in 64 bit mode. What happened?

©2026 Astroinformatics Group