And... What is the verdict? Is the CUDA bug fixed, or still there?I'm very tempted to install it, but since I use DVI, and blank my screen, I will probably very susceptible to the bug occurring (and ruining Seti work at the same time).Regards, Patrick.
Quote from: PatrickV2 on 10 Apr 2012, 12:55:12 pmAnd... What is the verdict? Is the CUDA bug fixed, or still there?I'm very tempted to install it, but since I use DVI, and blank my screen, I will probably very susceptible to the bug occurring (and ruining Seti work at the same time).Regards, Patrick.Yes, it is fixed, i even downgraded to 295.73 to double check, now crunching on 301.24 again, it did a few Einstein BRP4Cuda tasks this morning no problem,and has done ~40 odd Seti Cuda tasks late this afternoon with the monitor asleep no problem,Claggy
Any improvement in performance ?
when arrived home just updated to the latest official NVidida (296.10 x64) driver and really a nightmare no work could be done to the end in Collatz and Primegrid all CUDA work was ruined I revert to (285.62 x64) and work is running smoothly on a GTX460.
I am starting to see a few users in 'top computers' on Seti using 301.10, 301.24, and 301.32....Has anybody had the time to run any valid speed comparisons against 290.53, which has been my trusty standby so far?