NVIDIA's driver have problems, but instead of using real problems that are actually worth discussing you make up problems where there are none.
Well, shall we recap all the various discussions and issues and topics that have been coming up here?
1) NVIDIA added anisotropic filtering to the control panel for D3D (a very GOOD thing as it's loooong, loooong overdue), and by futzing around with the settings there, a user can wind up with "no af" settings wrongfully being in the registry as point sampling. The worst case scenario of this "bug" is there are bound to be websites reporting point-sampling benchmarks wrongfully as "application preference." All the GF4 users in the world are going to use RivaTuner or NVMax like they have since the days of the GF3, so it really doesnt effect them.
2) NVIDIA has, over the past several revisions, proceeded to slowly reduce the quality/effectiveness of 8x anisotropic filtering to improve performance. As 8x AF performance was the keypoint to be harped on from product release, as well as competition from other IHVs, it would make sense to find some way to get these benchmarks to improve. The little 4x/8x gallery I provided was at the 29.42 level (i.e. the "follow up to AF" drivers from the 28.32's that got so harped on this feature). It appears the 4x->8x transition has been reduced even further in the 40.xx drivers.
3) Some people believe that games like Flight Sim 2002, Motocross Madness 2, Motoracer or F1/racing sims are a good way to measure bandwidth/fillrate performance in order to try and prove superfluous points concerning AF. The rest of the community knows well enough that certain tests within 3dmark, as well as heavily CPU bottlenecked games dont make much sense nor are good methods to pinpoint anisotropic filtering performance, especially when combined with benchmark accuracy (say upto +/- 4% for lots of benchmarks with same settings can be yielded).
4) Many people have noted how it is interesting that the Nature test in 3dmark2001 seems to be the most dramatically effected by the 40.xx detonator drivers. To date, no one has found anything else to illustrate a performance edge with these new drivers so the pursuit continues.
You can make up your own motives for the above. Trying to determine motive isnt a cut and dry thing, regardless of how obvious or how much evidence there is in support of a given motive. It is much easier to instead simply assume it was a "lucky coincidence" or similar for issues to work in favor of one result or another.
Cheers,
-Shark