The Feb 09, 2012 driver is performing the exact same problem that was present with the Feb 29, 2012 one. You probably need to keep rolling back or use one of the beta/RC drivers they have available and see if that fixes everything up.
another BSOD with DV on using NVIDIA driver 285 (3rd one from the newest release). I cant believe im 3 drivers back and still having the same problems
I'm finding it very suspicious too. This also doing the same thing, despite being from Oct 2011.
Have you been rolling back by simply installing the old driver over the new, using the rollback driver feature, or completely uninstalling and installing the older drivers? I'd prefer the last option.
If you wish, you can test your video card using MemtestCL. Run a few passes of it. Note that it does not cover all functionality of the graphics card, primarily just the VRAM and some of the GPU functions. But it's a good solid test.
You may also run a couple more hardware tests just to make sure we aren't suffering a problem with some other hardware here for whatever reason:
RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
Of course it also goes without saying, if the video card or anything is overclocked, you will wanna reset it to factory defaults for the time being.
To be honest, given how utterly consistent these crashes are that are reported by DV, I can't see why it would be anything other than the NVidia drivers bugging out. Maybe you have some software installed recently that's causing the bug to manifest in the NVidia drivers. I'm not sure. One can't really analyze this much without at least a kernel dump to work with, as minidumps are too small and retain very little info. I just can't tell without more information right now.
ive been uninstalling the driver, going into safe mode, running driver sweeper, rebooting, installing new driver.
That's definitely the best way at going at it. I recommend doing those aforementioned hardware tests, and if nothing shows up, just simply keep rolling back, perhaps by a good amount then if that driver works then start moving upwards with earlier drivers until you find the culprit.
Or, you can send us a kernel dump (MEMORY.DMP in your Windows directory). If the latest crash is from Driver Verifier, send us the resulting MEMORY.DMP file. You'll obviously have to compress it and upload to a filesharing site, since it is much too big here.
I cannot guarantee that my current debugging skills will be able to determine a definitive answer from the kernel dump, but it's definitely a lot better to work with than the minidumps.
Quote