Why do you continue to be difficult? A software-mode application cannot, and I repeat, cannot cause a BSOD.
ONLY driver-mode applications/drivers can.
So do us all a favor, and do the research steps above. Find the culprit instead of coming here and making up excuses.
Clearly, Visual Studio is the trigger that causes this driver-mode code to cause a BSOD, but VS itself is not the culprit.
Originally Posted by Adak
Update your graphics driver. VS2010's Editor works with WPF internally, which means that ancient drivers will sometimes BSOD. I've had that with all WPF applications I wrote in VS2008 and now that the VS editor itself is in WPF, even VS itself will maker your older gfx driver scream
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
Which is a flawed theory. Consider a function xyz(), which when called BSODs. VS2010 (a software-mode application) calls this kernel-mode xyz() function. Boom, BSOD. By any definition, VS2010 initiated (and thus caused) the BSOD. And we all know Microsoft and their undocumented functions...
Last edited by zacs7; 07-08-2010 at 04:46 PM.
