GTX295 CUDA Issues

[madmac]

Can't wait that long as my machine isn't doing anything at the moment..
Will see what I can pick up off the bay then - cheers

[efmer (fred)]

The GTX 295 by faaar.

[efmer (fred)]

A GTX295 should give a better RAC than a GTX470 or 480. You could also wait, don't know how long, for the dual fermi cards to come out.

The dual fermi card looks read bad, a heavily underclocked dual 470.

[sunu]

We don't even know yet if it will be a dual 470 or other fermi iteration like for example GF104.

[madmac]

Posted on Seti and got this reply...

Depends whether you are interested in instantaneous results, or whether you are planning for the long term.

A 295 is mature technology, perhaps even obsolescent. It will have peaked already - there won't be much new development for it, and in due course there will be new developments which it can't keep up with.

A 470 is new technology, and won't be giving of its best yet. But it should be the focus of development effort for longer into the future, and you will be able to gain from those efforts.

Now or later? Dead-end or progress? Your choice.

He has a point, so Im going for a fermi :-)

[Richard Haselgrove]

Posted on Seti and got this reply...

From me. Flames to the usual address......

[SciManStev]

It's somewhat comforting to know that others have had similar problems with their 295's. Mine played games great, and worked perfectly with the standard apps. Every time I switched to the optimized apps, all it did was crash work units left and right. This happened on multiple motherboards, PSU's and processors. Heat was never even close to being an issue. It is nice to learn that my card was most likely an older one that was made with this error. I didn't know that before I read this thread. My two GTX 480's are crunching like mad now, and with the faulty 295 out of the picture, all my problems went away.

 One other symptom I was getting was that every time I tried to use a Killawatt meter to measurre power levels, the system crashed. I did upgrade my PSU, and it got a little better, but still during one of the regular screen blanking caused by the 295, it crashed me again. Now with the 480's, and an OC'ed CPU 980 at 4.2339 GHz, the system is very stable with the Killawatt meter running all the time.

Steve

[Pizzadude]

It's somewhat comforting to know that others have had similar problems with their 295's. Mine played games great, and worked perfectly with the standard apps. Every time I switched to the optimized apps, all it did was crash work units left and right. This happened on multiple motherboards, PSU's and processors. Heat was never even close to being an issue. It is nice to learn that my card was most likely an older one that was made with this error. I didn't know that before I read this thread. My two GTX 480's are crunching like mad now, and with the faulty 295 out of the picture, all my problems went away.

 One other symptom I was getting was that every time I tried to use a Killawatt meter to measurre power levels, the system crashed. I did upgrade my PSU, and it got a little better, but still during one of the regular screen blanking caused by the 295, it crashed me again. Now with the 480's, and an OC'ed CPU 980 at 4.2339 GHz, the system is very stable with the Killawatt meter running all the time.

Steve

Hi Steve, which Seti App. are you running and whats the average crunch time per work unit with your setup ?

[SciManStev]

I am running SSSE3, and the larger units are completing in just over 9 minutes, with shorties completing in 2 minutes and maybe a few seconds. There seem to be several interim units that are completed in just over 7 minutes. Rarely I will get a unit that takes 10 minutes. With the 295, it was 11 to 14 minutes, and full of errors, regardless of overclocking either GPU or CPU. Current CPU clock speed is for the CPU 980, 4.2339 GHz, with GPU shaders at 1510, and memory at 1890. Temps are i46°C for GPU, and 49°C for CPU. There is a long way I can keep going as far as over clocking is concerned.

Steve

[Raistmer]

Looks like you mix CPU and GPU apps.
There is no SSSE3-based GPU app. Akv8 SSSE3 is CPU app, and I hardly belive it can do task for only 9 mins even on i7.
On my Q9450 long task take ~2h of CPU while short one ~30min.

[SciManStev]

Sorry about that. I'm still coming up to speed, and learning what I can, while still making mistakes. I tried to look at the app_info file for the answer, and as it was a copy of Todd's, I am still learning to read and decipher it. Over the next few weeks, I will make a huge effort to learn more, and be more useful. My CPU WU's are completing in about 1 hour. I am running 95% of six cores, with hyperthreading disabled. The fermi app is setiathome_6.09_windows_intelx86__cuda_fermi.exe, as it was directly coppied from Todd. I truley want to learn to edit and create files. I have a book coming that should help.

Steve

[Pepi]

Current CPU clock speed is for the CPU 980, 4.2339 GHz, with GPU shaders at 1510, and memory at 1890. Temps are i46°C for GPU, and 49°C for CPU. There is a long way I can keep going as far as over clocking is concerned.

Steve

Lower your CPU to stock frequency, and then also lower your shaders to let say 1400 MHz, and also memory to 1700, and then try. I have problems with my GTX260 ( shaders not working well) After I put shaders to stock frequency there is 15 days without any error. I uset OCCT test with error counting for GPU testing. If you have even one error on 1 hour test you must lower your shaders clocks, until you get it stable. I can bet that your card will fail on this test, and give you errors in first few minutes.

[SciManStev]

Now that I am running the 480's, I have no errors, and my system is very stable. The 295, gave me nothing but headaches. I tried stock speeds, undercllocking the memory, everything I could think of or read on the SETI boards. As soon as I converted to the 480's, my problems vanished.

Steve

[Raistmer]

Quite enough data to return it to seller IMO

[Pepi]

Try OCCT test, you have nothing to loose. If I am right, you have bad card, use EVGA Precision to change shaders frequency ( without flashing) and test it.