Advanced search

Message boards : Graphics cards (GPUs) : WU's computation error, all of them!

Author Message
Profile medictom
Avatar
Send message
Joined: 8 Mar 09
Posts: 3
Credit: 19,341,276
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwatwatwat
Message 10973 - Posted: 6 Jul 2009 | 3:04:41 UTC
Last modified: 6 Jul 2009 | 3:14:04 UTC

Hey all, maybe someone can look at my computations and let me know if I am doing something wrong, or what I can do to fix this, everytime I do a GPU Grid WU as of late, they all have computation errors.

Used to have a 8600gt Nvidia card in my AMD Dual core,and it was happening, and I now even upgraded to a GTX 260, newest drivers, current boinc, and they are still failing...any suggestions, ideas?

Thanks in advance...
____________

zpm
Avatar
Send message
Joined: 2 Mar 09
Posts: 159
Credit: 13,639,818
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 10975 - Posted: 6 Jul 2009 | 3:44:28 UTC - in response to Message 10973.
Last modified: 6 Jul 2009 | 3:45:02 UTC

try installing driver 185.85... 186.xx has given me trouble.... try that...
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/

Profile medictom
Avatar
Send message
Joined: 8 Mar 09
Posts: 3
Credit: 19,341,276
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwatwatwat
Message 11243 - Posted: 22 Jul 2009 | 10:52:12 UTC

Finished 2 more work units, both computation errors...any other suggestions, what can be going wrong...I have checked my drivers, I have a GTX 250 why is it always failing?

Thanks to everyone in advance for your time...

ideas?

medictom
____________

Profile GDF
Volunteer moderator
Project administrator
Project developer
Project tester
Volunteer developer
Volunteer tester
Project scientist
Send message
Joined: 14 Mar 07
Posts: 1947
Credit: 629,356
RAC: 0
Level
Gly
Scientific publications
watwatwatwatwat
Message 11270 - Posted: 23 Jul 2009 | 9:10:05 UTC - in response to Message 11243.

On Windows 32bit, it seems that you need drivers 181.xx.
The new drivers don't work.
gdf

Profile medictom
Avatar
Send message
Joined: 8 Mar 09
Posts: 3
Credit: 19,341,276
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwatwatwat
Message 11283 - Posted: 24 Jul 2009 | 9:08:56 UTC

Frustrated. Two more computation errors...
____________

Profile Steve Dodd
Send message
Joined: 26 Dec 08
Posts: 17
Credit: 513,971,727
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 11286 - Posted: 24 Jul 2009 | 13:09:23 UTC

Still no success. Using driver 181.22 and still failing all wus. Same error -
7/24/2009 6:02:48 AM GPUGRID Computation for task 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0 finished
7/24/2009 6:02:48 AM GPUGRID Output file 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0_1 for task 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0 absent
7/24/2009 6:02:48 AM GPUGRID Output file 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0_2 for task 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0 absent
7/24/2009 6:02:48 AM GPUGRID Output file 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0_3 for task 8-KASHIF_HIVPR_sub_so_ba1-9-100-RND9354_0 absent

Setting NNT until this is sorted out. (Windows XP 32 bit, GTX 260 Core 216)

Profile Logan
Send message
Joined: 14 Jul 09
Posts: 5
Credit: 41,378,172
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 11287 - Posted: 24 Jul 2009 | 13:32:46 UTC - in response to Message 11283.
Last modified: 24 Jul 2009 | 13:34:32 UTC

Frustrated. Two more computation errors...


190 works fine for me in a GTX260 in a Q6600 with Win XP 32 bits.

I think, could be your BOINC version... yo're using 6.6.36.

Do you remember what BOINC version you used when all worked fine?

OldChap
Send message
Joined: 5 Jul 09
Posts: 14
Credit: 28,617,272
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwat
Message 11291 - Posted: 24 Jul 2009 | 19:14:00 UTC

Mine: 260 (192) 190 drivers qx9650 x48 vista64

I get driver nvlddmkm failed and recovered which in turn causes computation error running stock clocks.

Other machine on xp and 98gtx and 182.08 no errors

using 6.6.36 as it was advised in the messages file

Thoughts anyone?

Profile BOINC*Zappattazz*Synergy
Send message
Joined: 17 Jul 09
Posts: 1
Credit: 0
RAC: 0
Level

Scientific publications
wat
Message 11293 - Posted: 24 Jul 2009 | 22:37:49 UTC
Last modified: 24 Jul 2009 | 22:42:29 UTC

I'm having this exact same problem -- all WUs end in "Computational error" from the very first WU I downloaded.

Here is my first WU result:

<core_client_version>6.6.36</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1350000 kilohertz
# Total amount of global memory: 939524096 bytes
# Number of multiprocessors: 27
# Number of cores: 216
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [fft_data_swizzle_in] failed in file 'c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu' in line 44 : unknown error.

I'm running a single EVGA GTX 260 Superclocked Edition (190.xx driver) on a EVGA NForce 750i SLI FTW motherboard, Intel Q9300 cpu, 8Gb DDR2-800 memory. Everything is running at stock -- nothing is tweeked! OS: Vista64 Premium SP2
____________

Profile Logan
Send message
Joined: 14 Jul 09
Posts: 5
Credit: 41,378,172
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 11295 - Posted: 24 Jul 2009 | 22:47:05 UTC - in response to Message 11293.
Last modified: 24 Jul 2009 | 23:06:19 UTC

Let me think...

What thing I did different than you...?

Uhmmm.... I installed CUDA 2.2 Toolkit.


Try it.

Post to thread

Message boards : Graphics cards (GPUs) : WU's computation error, all of them!

//