MJH (et. al):

I have concluded my exhaustive Cuda 8.0 SDK testing. On my Win10 x64 Build 16184 PC (with GTX970, GTX660Ti, GTX660Ti), I installed VS2015 Community, installed the Cuda 8.0 Toolkit and samples, installed the DirectX SDK, then built all of the Cuda solutions.

There are 155 Cuda samples that I was able to compile and test with. And I went through them, 2 times:
1) 381.89 - GTX970, GTX660Ti, GTX660Ti
2) 381.89 - GTX660Ti, GTX660Ti (I pulled the GTX970 out of the system)

Out of the 155 samples, they all passed on both runs.. except VFlockingD3D10 did not look correct on my GTX660Ti but looked fine on my GTX970. All other calculations and samples worked fine, even on a GTX660Ti.

This leads me to believe that the GPUGrid problem with the "9.18 (cuda80)" app, where it errors out immediately on a system that has a CC3.0/SM3 GPU .... might not be an NVIDIA problem. It might be a problem with your app.

Is it possible you are calling some method or function, that isn't supported by CC3.0/SM3?

I'm desperately wanting you to provide more info. I'm spending considerable effort to help you solve this, yet my questions to you go on unanswered. I hope you're making progress with a fix - please consider chiming in with your findings.

Jacob Klein

It's beginning to look as if there might be a problem with that 381.89 driver, isn't it?

A user on the BOINC message boards says that BSOD problems with driver 381.89 stopped after updating to 382.05

(he also says he's upgraded from BOINC v7.6.33 to v7.7.2, but I'd caution against that - v7.7.2 was a highly experimental test build. v7.6.33 has been around for a long time, and is very unlikely to be implicated in recent changes to GPU behaviour)

That same guy posts a ton in the NVIDIA Driver Feedback threads on their forums, about GPU apps crashing whenever he closes BOINC. I've tried to help him a few times before, but it seems he doesn't know how to isolate problems and troubleshoot them very well. I don't think he tries very hard to reliably reproduce the problems that he has.

So ... I'd be cautious about his words being more "noise", instead of confirmations of problems or solutions.