Surely I have cuda 2.3

And I have always the same errors like other drivers sup than 182.5 ---->

14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_1 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_2 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_3 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent

I try the 190.62 and always these message. I return all my wus bad.

And now I cant work for this project with 182.5. they are incompatible.

You need at least 185, the error message is misleading.
g

I was on (and am again) running 186.06, I'll see gow things are tomorow when I sould get new WUs

Now you should be able to run again drivers 182.xx.
However, please confirm that 182.xx does work.
Also the error message should be now more appropriate.

gdf

The 186.08 (sorry not .06 I think I must need new glasses) are working fine now. No sign of the downclocking or crashed WUs the 190s were giving.

One guy (svol) from team "Russia" said that he's OK with 190.xx driver and GTX260. I'll try to get a couple Wus for testing...

---

From Siberia with love!

GDF,

I have a machine, 20013, that refused to run on anything in the 185.xx and higher series. It has an factory OC eVGA 260-216. I backed it off to 182.50 and so far, it appears to be working. I did this yesterday and will report how it runs for longer term. I originally had this on driver 182.06 and it ran fine there. I only moved it when it didn't work with 182.06 anymore. This machine went through the 2.2 upgrade with the old driver, during the period where you guys were still sending out work it could crunch.

I'm happy the Grid went back to allowing 182.xx machines back into the game. I was thinking I would have to drop off the Grid with this one...

I'm also having a side issue of the newer (185.xx and above) drivers not working through the KVM on my farm. They come up with a blank screen. Driver 182.50 works fine.

The farm is running a mix of 185.85, 190.38, and 190.62. I have a workaround which involves plugging the monitor directly into the machine during boot, then putting it back through the KVM when it's up. This is a PITA, but it works.

Let's hope that nVidia gets it together soon...

Regards,
Bob

One guy (svol) from team "Russia" said that he's OK with 190.xx driver and GTX260. I'll try to get a couple Wus for testing...

I have a GTX 260 with v190.62 drivers and BOINC v6.10.1 that's been running with no problems (14 WUs and counting). It's a clean install of WinXP32, so YMMV.

So, another one broken WU...

28.08.2009 4:42:29 GPUGRID Computation for task p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0 finished
28.08.2009 4:42:31 GPUGRID Output file p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0_1 for task p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0 absent
28.08.2009 4:42:31 GPUGRID Output file p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0_2 for task p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0 absent
28.08.2009 4:42:31 GPUGRID Output file p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0_3 for task p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0 absent
28.08.2009 4:42:34 GPUGRID Started upload of p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0_0
28.08.2009 4:42:44 GPUGRID Finished upload of p335000-IBUCH_r_pYEEI_us5xy1_2408-3-5-RND3015_0_0


But why it exited after 5+hours of computing?

I'll try now newest BM and drivers, if it applicable to Win 7 x64...

---

From Siberia with love!

This seem a case of instability in the hardware. Maybe you were playing a game that finished the available video RAM or again overclocking (don't know if this is your case).

gdf

Well, I have another error. now without gaming (and USING desktop at all!) while computing, without overclocking, with 85% of MAX GPU cooler speed, with 190.62 video driver (BM 6.6.37). As usually, Win 7 Ultimate x64.

Now I've got another WU, 'cause BM 6.10.1 is installed. Let's see, what will happen...

I'll make it work even if it will require a very old driver...

---

From Siberia with love!

I'll make it work even if it will require a very old driver...

OT:
That's what I'm doing with Milkyway@ATI right now. I can't get the newer drivers to work and am thus stuck with the rather old 8.12 (=last Nov) under Win 7 Prof. That kind of works, but rewards me with plenty of blue screens..
Sorry for the OT, it's just a little frustrating.

MrS

---

Scanning for our furry friends since Jan 2002

Now you should be able to run again drivers 182.xx.
However, please confirm that 182.xx does work.
Also the error message should be now more appropriate.

gdf

Indeed
I reinstalled 182.5, And it work again.

No, using BM 6.10.1 x64 did not help. Win 7 Ult., 190.62.

Old drivers are being loaded...

---

From Siberia with love!

An old driver is installed:

01.09.2009 8:51:12 NVIDIA GPU 0: GeForce GTX 260 (driver version 18581, CUDA version 2020, compute capability 1.3, 896MB, est. 96GFLOPS)
01.09.2009 8:51:12 No CAL Runtime Libraries installed.

---

From Siberia with love!