Whats wrong with GPU Grid and Nvidia Drivers 190.x on the GTX 260 with 192 SP´s ?

Author	Message
Daniel.Ahlborn Send message Joined: 12 Jan 09 Posts: 5 Credit: 3,359,168 RAC: 0 Level Scientific publications	Message 12456 - Posted: 11 Sep 2009, 16:09:20 UTC Its frustrating, on my System is every single WU abordet with errors. Usually immedatly when it starts the calculation, it aborts. my system: Win Vista 64 bit ultimate SP2, Forceware 190.62. Primary Graphics Card is a Geforce GTX 260 with 192 Streaming Processors and secondary a Geforce GTS 250. This Issue appears only in GPU Grid, other Cuda releated boinc projects are not affected. in so far i dont think that this is a driver problem, more i believe that this Bug is releated to the GPU Grid application. here is my question, does anyone run a system with a GTX 260 with 192 SP´s and Forceware 190.62 without any issues on a 64 Bit windows? Thx in advance ID: 12456 · Rating: 0 · rate: / Reply Quote

pa3fge Send message Joined: 11 Sep 09 Posts: 1 Credit: 3,309,708 RAC: 0 Level Scientific publications	Message 12461 - Posted: 11 Sep 2009, 19:41:45 UTC - in response to Message 12456. Works fine here on a Intel quadcore Windows 7 64 bit system with a GTX295 and a 190.62 driver. Only in BOINC V6.6.36, you have to put a mark at "use GPU when computer is in use". The "run always" override does not work for GPU which I think is a bug in BOINC. ID: 12461 · Rating: 0 · rate: / Reply Quote

Daniel.Ahlborn Send message Joined: 12 Jan 09 Posts: 5 Credit: 3,359,168 RAC: 0 Level Scientific publications	Message 12462 - Posted: 11 Sep 2009, 20:43:45 UTC - in response to Message 12461. Works fine here on a Intel quadcore Windows 7 64 bit system with a GTX295 and a 190.62 driver. Only in BOINC V6.6.36, you have to put a mark at "use GPU when computer is in use". The "run always" override does not work for GPU which I think is a bug in BOINC. "Use GPU when Computer is is use" was checked all the time. and, by the way, i have asked for GTX 260´s with 192 shading processors. i suspect that with this specific series is something wrong in that matter because i have heard several other people complaining the same issue. ID: 12462 · Rating: 0 · rate: / Reply Quote

chumbucket843 Send message Joined: 22 Jul 09 Posts: 21 Credit: 195 RAC: 0 Level Scientific publications	Message 12465 - Posted: 12 Sep 2009, 0:06:38 UTC i have the same problem. vista 64 sp1 and 190.XX. its probably something with cuda if it is bugging out on one card. ID: 12465 · Rating: 0 · rate: / Reply Quote

MarkJ Volunteer moderator Volunteer tester Send message Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level Scientific publications	Message 12466 - Posted: 12 Sep 2009, 2:41:13 UTC If you read this message thread it will explain some things. The GTX260 basically broke after the nvidia 182.50 drivers. Unfortunately cuda 2.2 and cuda 2.3 versions haven't solved it. This is shown by the fft bug as mention in the message thread above. This bug seems specific to the GTX260 cards. Our options seem to be: 1. Run cuda 2.1 with the 182.50 drivers 2. Use a different graphics card 3. Wait for the next driver release from nvidia Personally my GTX260's are running Seti cuda work now while I wait for nvidia to get things sorted out. They tend to release new drivers around the 21st of each month. BOINC blog ID: 12466 · Rating: 0 · rate: / Reply Quote