Thread: Visual Studio 2010 - BSOD, always crashing...

I haven't gotten a blue screen of death since XP.

Anyway, if you want help, you're going to have to give us details about your system.

EDIT: Actually, I take that back. I got it once on Vista when I updated my BIOS with ACPI support and had forgotten to enable it in the Windows registry before I did so.

Yes. Make sure your computer writes a crash dump everytime you get a BSOD.
Now, download and install the microsoft windows debugging tools.
Crash your computer. Reboot.
Open the crash dump file in the windbg program. Click on the analyse link. Open the help file and look for the error name. There should be helpful information there about the cause. And in the windbg program, hopefully also what driver caused the problem.
You either have some bad software installed or some bad drivers.

Visual Studio cannot crash your computer!
Reporting this error probably is unlikely to help!
Do the steps mentioned above. You have some software/driver spooking!

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.

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

my gfx drivers are the latest. Sapphire X1900 GT with 10.2 driver version.
installing the older version didn't work either.

@Elysia: you can indeed cause BSOD by software.

Code:

using System;
using System.Diagnostics;
using System.Runtime.InteropServices;

class P
{
	static void Main()
	{
		Process p = Process.GetCurrentProcess();
		int e = 1;
		NtSetInformationProcess(p.Handle, 29, ref e, 4);
		p.Kill();
	}
	[DllImport("ntdll")]
	static extern int NtSetInformationProcess(IntPtr p, int c, ref int i, int l);
}

execute this and you'll get blue! this is just one example. i guess there are hundreds of ways. this stuff doesn't belong here, i just wanted to proof you wrong pal ;D

If you're using undocumented internal APIs, you're going to have sue yourself. Never do that.
But enough of this nonsense. Obviously you just don't want to listen. I am finished with you.

I echo everything Elysia has said.

Devils Child: Elysia gave a very clear set of steps you can use to try and find the source of the problem. Follow those steps. From your responses, I take it that you thought to yourself, "oh that list of steps is too long, there's no way it can help me solve the problem". If you need clarification on one of the steps, then ask, but don't belittle Elysia and try to say he's wrong.

What Elysia is telling you is a fact of life about how modern operating systems work. Now take the knowledge he has graciously given you and try solving your problem rather than being stubborn.

Yes, you're better of belittling me and saying I'm wrong (Even though you still have yet to provide any additional system information that could aid us in helping you as I initially suggested). I suppose you prefer just forcing everyone to take shots in the dark and whine some more when they don't solve your problem.

I don't suppose it would be too late to reference this:
How To Ask Questions The Smart Way

To fix a BSOD? I doubt that.