Nvidia just released new drivers

[Maik]

Oh WTF ?!?
First time i got a blue screen ....
All written down here.

[Raistmer]

Yes, as I said already new driver doesn't fix VLAR driver crash bug. Have strong considerations that this bug connected with 2-3 seconds limit for execution time for single CUDA kernel. This limitation exists in CUDA itself - OS just restart driver when there is no respond from it for few seconds. Probably the single way to eliminate this bug for now is to split affected kernel on few CUDA calls.

[Devaster]

its a watchdog problem on primary display  in windows core - it  happens on  devices where is a primary display extended .  windows core is waiting for device response in 5 seconds max intervals if nothing happens it crashed to BSOD in xp or restart devce driver in vista. so if kernel take more execution time as 5 secs this is problem for
windows core. on  devices without primary display u can run kernels with any execution times ....

[Raistmer]

its a watchdog problem on primary display  in windows core - it  happens on  devices where is a primary display extended .  windows core is waiting for device response in 5 seconds max intervals if nothing happens it crashed to BSOD in xp or restart devce driver in vista. so if kernel take more execution time as 5 secs this is problem for
windows core. on  devices without primary display u can run kernels with any execution times ....

Very likely, BUT there is too little number of such non-primarily devices available. And I personally have no one (actually have one PC with dual GeForce but it's x64 host and there are other troubles - it gives computational errors always it seems )
So, if you have such setup (CUDA GPU with no primarily display), please, try to redo VLAR tests from this thread: http://lunatics.kwsn.net/gpu-crunching/wus-that-cuda-mb-cant-do-correctly.0.html.
And report results. It would be helpfull for debugging I think.