I am using GTX260 in Vista 32 system. GPUGRID tasks always meet "Calculation Error". But my another machine using GTX285 in Windows 7 does not have this problem. Is there any method to avoid this error?

I have tried several drivers before 190.XX, also had the same problem. Seems it is not my problem and what I can do is just wait.
Thanks for your helping.

I don't think it necessarily is the GTX260 at fault.

I run two computers with one each GTX260 (MSI N260STX T2D896 OCv3) without problems on W7RC 64-bit using the 190.38 Nvidia driver.

GTX 260 216 core and vista 32-bit, i'm at your service, just tell me what u need.... i haven't had any trouble with gpugrid since testing aqua cuda and gpugrid together back in may-june

190.38, 260 gtx, 216 cores, bfg tech foc.

Im running Windows 7 RC 64 bit, with two 216 core gtx 260's and 190.38 driver. No problems so far in running the CUDA 2.2 applications.

Anyone is able to run with some flavour of Windows 64?

gdf

Best bet is for all those with this problem to wait for 190.XX which will be out this week if nvidia holds true to monthly drivers

I am running 2 machines with Vista 64.
GTX 260 (192) will not run any driver above 182.xx - use on F@H
GTX 260 (216) runs GPUGrid fine under 190.38.

Both cards EVGA and at stock clocks.

I'm wondering: did any of you who's affected by the recent problems (error code 98, mostly GTX 260) get the problems without installing 190.38? I know in many cases the problems occured after the installation of 190.38 and were not reversible.
Did any of you try the "clean sweep" described by Zydor here?

MrS

My GTX260 is Zotec GTX2602 which has 216 cores. I have tried this card for several times and each time met "Calculation Error". Then the core frequency reduced to 2D mode. But my GTX285 does not have the problem.
BTW, what's the difference between the task with "(CUDA23)" and "(CUDA)"?

cuda = to current version cuda 2.2

cuda 23 = cuda app 2.3 based...

I found my GTX285 calculates CUDA23 much slower than CUDA. But GPU temperature is about 7 degrees lower.

rig: 2x gtx260's (evga 192), vista 64 ultimate, x48 MB. (ask if you want more)

Firstly I've tried 190.38 when they came out and I got errors on 6.6.36 and 37.

Now I have 190.62, 6.6.38 and although I have completed more today than ever before but still had the errors.

at one point I wanted to make a post so I went to that machine to double check the boinc version I moved the mouse and....bam "driver failed and recovered" and immediate error of 1 wu....this after some hours of running and I think 1 maybe 2 completions since moving to this configuration. there then followed over the next couple of hours further errors til all bar one of the daily quota failed...this last one continued and is I believe still running near 50% complete.

Are there any instructions for setting gpugrid up or perhaps I should ask any new instructions. I am new to this and am wondering if it is necessary to remove those parts of cuda installed for folding as grid includes all it needs (or so I understand)

Just wondering aloud here ...did I miss something?

just don't have folding and gpugrid running at the same time...

190.xx series of drivers is very, very, very picky and seems to only like certain systems(like me) and seems to be unstable for gamers, and cuda.

you name the a,b,c's and someone from each game app will tell you something that is messed up with 190.xx..

i've got one windows xp 32-bit in which a combo of 190.xx and flash/java don't work well together as i get flashy screen in the java...

I've been using BOINC for some time now, first only for Seti@home. Recently (late July) I joined GPUGRID. I've been running GPUGRID (and seti@home) only on the GPU (disabled CPU processing in preferences). I'm using a MSI GTX260 (192 cores) on Vista Home Premium x64 SP2.

When I first started I used drivers 186.18. I got "computation error" on every WU. A few days ago I switched to driver version 190.62. I still get "computation error" on all WUs. Seti@home works fine. I didn't bother to try 190.38 as many on the nvidia forums seemed to have problems with them.

System specs:
C2D E6750 2.66GHz, OC'ed 3.04GHz
Asus P5K-E Wifi/AP
8GB Corsair DDR2 800MHz, OC'ed 950MHz (5-5-5-15)
MSI GTX260, OC'ed
1x 500GB WD
4x 1TB WD GP (RAID 5)
620W Corsair HX620W
Creative X-FI XtremeMusic
Vista Home Premium x64

GPU-Grid is more demanding than seti, in terms of heat / power consumption, error detection and error tolerance. So it could be that you're a victim of the recent GTX260 / fft issues.. or that you'd have to lower your OC a bit.

MrS

I have nly errors with my 260-216 and I changed now to Collatz Conjecture.
I vera nice project and my card is now again stable and crunching hard.
Thx guys in this project, Auf Wiedersehen! (see again later {possible])