After posting here that I was happy with the 196.75 drivers after the fan issue was announced and I would only rollback to the 191.xx drivers if I had issues, I relented and decided that I couldn't afford to cook my cards :-/
I may well leave it a month or so before I decide to test these new ones, nVidia seem to have lost the address of their QA team recently and are releaseing drivers that maybe should have spent some more time with the Dev and QA team

I'm not sure what the issues are with the GTX295 are, but according to the change notice for the release, it does address the fan speed issue.

It has to do with Seti Crunching on more than one GTX295 in Windows 7 and Nvidia wanting users to crunch with Tesla card and Quadro cards and of course with the new toys Nvidia has made(the 470 and 480), I'm slowly working on getting two used GTX295 cards as I use XP x64 which does not have a problem doing Seti with 3 or 4 GTX295 cards as MS went to a WDDM driver with Vista and Win7 and Nvidia won't properly support cuda on more than 1 or 2 GTX295 cards as We're a small minority of users, In other words We've been dumped and led by the nose, Being told that Nvidia supports Cuda, When in reality Nvidia only supports cuda where It meshes with how they see consumers using a card or cards, No other way they said as they'd tested the driver with 1 GTX295, 2 Tesla cards($$$$$x2) and 1 Quadro card($$$$$x1) and the driver they(Who else) said worked fine(Tesla and Quadro cards cost a small fortune and most avoid them as a result as their loaded w/a single gpu and about 4GB of ram per card, instead of dual gpus like on the GTX295), And more than one(or two?) GTX295('s) isn't supported under Win7 for Cuda(forget about Vista cause of something MS did in Vista, What MS did, I have No idea[this was from an Nvidia rep on the board there]), So I'm staying with what I have as Win7 looks nice, But doesn't support Seti@Home like XP x64 does(See the thread link below on Nvidia's own forum and read from the start).

Apart from the fact they've stolen some of my memory (are both GB cards) seems to be going well so far, only had one BSOD which was on the first reboot immediately after install.
Haven't tested coming out of sleep mode to see if the fans kick in yet. Think I may leave that till I'm feeling a bit braver
Crunch times don't seem to be affected either, but I need to run through a few wu's still to compare them

Both these "errors" seem to be a "feature" of Raistmer's modification (VLARkill or VLARnoKill). They are just about the only error types I get these days; Sutaru has posted a number of times on this topic. The choice seems to be to accept that they will occur or to revert to Stock CUDA.

Both these "errors" seem to be a "feature" of Raistmer's modification (VLARkill or VLARnoKill). They are just about the only error types I get these days; Sutaru has posted a number of times on this topic. The choice seems to be to accept that they will occur or to revert to Stock CUDA.

F.

The -12 error is reported by the stock CUDA application too - see WU 582294218, where we've all done it (I'm the anonymous platform, but I'm running the stock app for CUDA). Apart, that is, from the CPU at the top, and the overheated or generally sulky CUDA23 card at the bottom, which is STILL blowing away a false overflow every 20 seconds, 11 days later: no wonder it has 10,225 tasks clogging up the database.

Outcome -12 is a programming issue internal to the SETI CUDA application (all versions) - no external factors are involved.

The -12 error is reported by the stock CUDA application too - see WU 582294218, where we've all done it (I'm the anonymous platform, but I'm running the stock app for CUDA). Apart, that is, from the CPU at the top, and the overheated or generally sulky CUDA23 card at the bottom, which is STILL blowing away a false overflow every 20 seconds, 11 days later: no wonder it has 10,225 tasks clogging up the database.

Outcome -12 is a programming issue internal to the SETI CUDA application (all versions) - no external factors are involved.

Thanks for the clarification, Richard. So the only effect of Raistmer's mod is the occasional generation of a "cudamemcopy" type error, perhaps by translation from a -12 I seem to recall Sutaru suggesting.

Well, with two GTX 295 and driver 197.13 (so we're on topic ;-) ), probably only one core is blowing, and the others are delivering good work. I hope it's not really an "enterprise server", because if it is, he may be reluctant to do the necessary reboot. Might be something for the multi-card crunchers to check: not only are all the cores working, but are they all working properly?

On the total credit - he must have merged a previous incarnation. The ID matches the birthday, according to the IDs on either side.