A little bit of clarification:
- If your Nvidia Gforce GPU is PRE 4xx then it is NOT a Fermi processor, and you will have the problems outlined by Raistmer unless you stick with the older drivers.

(I've not looked to see what of the "Nxxx" or other families of Nvidia GPU are affected - perhaps someone else could fill in the blanks)Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Or the new plan class opencl_nvidia_cc1 Eric made over on Beta that resolves this issue could be implemented here.
The decision may have been made not to worry about doing it for AP v6 and just add it when AP v7 is rolled out.SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today!

Looks as though the Quadro FX cards are affected also. Seems to be the same problem, not detecting any single pulses, http://setiathome.berkeley.edu/workunit.php?wuid=1601147878
If the task doesn't have any single pulses it will validate. I've even seen cases where the WingPerson found 1 single pulse and the effected card that didn't find the single pulse still validated.

Looks as though the Quadro FX cards are affected also. Seems to be the same problem, not detecting any single pulses, http://setiathome.berkeley.edu/workunit.php?wuid=1601147878
If the task doesn't have any single pulses it will validate. I've even seen cases where the WingPerson found 1 single pulse and the effected card that didn't find the single pulse still validated.

Seeing as the Quadro FX 1800 is based on the same G94 core as the 9xxx series cards it's to be expected. ;-)

Looks as though the Quadro FX cards are affected also. Seems to be the same problem, not detecting any single pulses, http://setiathome.berkeley.edu/workunit.php?wuid=1601147878
If the task doesn't have any single pulses it will validate. I've even seen cases where the WingPerson found 1 single pulse and the effected card that didn't find the single pulse still validated.

Seeing as the Quadro FX 1800 is based on the same G94 core as the 9xxx series cards it's to be expected. ;-)

Cheers.

Since you seem to be well versed in that class of cards, care to list other affected cards?

I remember someone being 'concerned' about me running a Beta App on TWO tasks on main. Now we have HUNDREDS of tasks being run by cards KNOWN to produce Incorrect results...yet there doesn't seem to be much concern.

Looks as though the Quadro FX cards are affected also. Seems to be the same problem, not detecting any single pulses, http://setiathome.berkeley.edu/workunit.php?wuid=1601147878
If the task doesn't have any single pulses it will validate. I've even seen cases where the WingPerson found 1 single pulse and the effected card that didn't find the single pulse still validated.

Seeing as the Quadro FX 1800 is based on the same G94 core as the 9xxx series cards it's to be expected. ;-)

Cheers.

Since you seem to be well versed in that class of cards, care to list other affected cards?

I remember someone being 'concerned' about me running a Beta App on TWO tasks on main. Now we have HUNDREDS of tasks being run by cards KNOWN to produce Incorrect results...yet there doesn't seem to be much concern.

hmmmm....

It'd be easier to say that any cards not based on the GFxxx/GKxxx/GMxxx core code names are affected.

That's probably still too vague for most people. Let's see, how about;

Attention, if you have a nVidia card that's 4 years old or older, and have updated to Driver 340.xx,
you are now Flooding SETI with Bad AstroPulse Science. This includes just about any nVidia
card that's not at least a 400 series or around 4 years old or newer.

That's probably still too vague for most people. Let's see, how about;

Attention, if you have a nVidia card that's 4 years old or older, and have updated to Driver 340.xx,
you are now Flooding SETI with Bad AstroPulse Science. This includes just about any nVidia
card that's not at least a 400 series or around 4 years old or newer.

How about that?

Actually the thread title is the best description for the hardware effected IMO. ;-)

That's probably still too vague for most people. Let's see, how about;

Attention, if you have a nVidia card that's 4 years old or older, and have updated to Driver 340.xx,
you are now Flooding SETI with Bad AstroPulse Science. This includes just about any nVidia
card that's not at least a 400 series or around 4 years old or newer.

How about that?

Actually the thread title is the best description for the hardware effected IMO. ;-)

Cheers.

Except many people don't have a clue about 'FERMI' and the title doesn't mention a thing about Flooding SETI with BAD SCIENCE. To make matters worse, there is a thread about this New Driver, with over 1000 views, without a mention about it causing the older cards to Flood SETI with BAD SCIENCE.

Except many people don't have a clue about 'FERMI' and the title doesn't mention a thing about Flooding SETI with BAD SCIENCE. To make matters worse, there is a thread about this New Driver, with over 1000 views, without a mention about it causing the older cards to Flood SETI with BAD SCIENCE.

Not good.

It's really no different to all those AMD/ATi cards out there currently and over the years that are/have been doing bad science due to the wrong drivers being used either is it?

Except many people don't have a clue about 'FERMI' and the title doesn't mention a thing about Flooding SETI with BAD SCIENCE. To make matters worse, there is a thread about this New Driver, with over 1000 views, without a mention about it causing the older cards to Flood SETI with BAD SCIENCE.

Not good.

It's really no different to all those AMD/ATi cards out there currently and over the years that are/have been doing bad science due to the wrong drivers being used either is it?

Cheers.

The bad/wrong ATI drivers cause the App to NOT run or Error out. Much different than completing a task Incorrectly.

Why does that have any bearing with the current known software problem producing KNOWN BAD RESULTS?
These are Not Errors, they are being Submitted as Successful Results.