Originally Posted by
Nusquam
And yes, I can give an update on that (not sure this is the appropriate thread).
QA were/have been unable to reproduce it.
The coders were unable to fix the problem.
Nvidia were unable to reproduce it.
We have received a troubleshooting program from Nvidia which we are running beside some of our clients and which will find any errors that may (or may not) cause the problem.
All of the above was done over the course of roughly the last 5 months, so it has been an ongoing process. And unfortunately the answer is not "It's fixed", yet.