I'm not really sure whats the problem here. Actually everytime I use a shader(even if just a simple one) my explorer keeps crashing. I have to manually restart my computer and there's no error message.

has anyone had this problem before?

You have to actually restart your computer? Could be a graphics driver issue then. Are they up to date?

You have to actually restart your computer? Could be a graphics driver issue then. Are they up to date?

Yes they are. I already update my driver. Still having the same problem. I have no clue whats the problem without showing the error.

What operating system are you running? What's your Video Card? There may be an incompatibility with those and MonoDevelop.

There are a few things you can try.

Run Event Viewer and check out Windows Logs\Application or System Log and check around the time you crashed. There's a small chance it might tell you something.

If you're running in full screen exclusive mode, try running in windowed mode. You might be blue screening, or you might have an error window popping up that you don't get to see.

Google how to analyze blue screen dumps and start digging into it.

Have you tried your code on a different computer?

- Eck

What operating system are you running? What's your Video Card? There may be an incompatibility with those and MonoDevelop.

There are a few things you can try.

Run Event Viewer and check out Windows Logs\Application or System Log and check around the time you crashed. There's a small chance it might tell you something.

If you're running in full screen exclusive mode, try running in windowed mode. You might be blue screening, or you might have an error window popping up that you don't get to see.

Google how to analyze blue screen dumps and start digging into it.

Have you tried your code on a different computer?

- Eck

Wow this is embarassing.

I really was running on full screen when my application is running and caught the error.

graphics.IsFullScreen = true;

Never thought that VS would not show any error when your application is on fullscreen.

I set it now to false.

Thanks.

Just an additional info on fullscreen debugging in VS:

VS does show an error message, which is the actual problem. It displays the "debug or abort" dialog, which cannot be shown in full screen modes (because the main window of an app that goes fullscreen usually gets topmost set)

In such cases press Escape and then try to abort debugging (Shift-F5 is the default debug cancel key AFAIR)

Just an additional info on fullscreen debugging in VS:

VS does show an error message, which is the actual problem. It displays the "debug or abort" dialog, which cannot be shown in full screen modes (because the main window of an app that goes fullscreen usually gets topmost set)

In such cases press Escape and then try to abort debugging (Shift-F5 is the default debug cancel key AFAIR)

Thanks. Ill keep that in mind.

Wow this is embarassing.

I really was running on full screen when my application is running and caught the error.
graphics.IsFullScreen = true;
Never thought that VS would not show any error when your application is on fullscreen.

I set it now to false.
Thanks.

Don't swe

...

If you're running in full screen exclusive mode, try running in windowed mode. You might be blue screening, or you might have an error window popping up that you don't get to see.

...

Wow this is embarassing.

I really was running on full screen when my application is running and caught the error.

graphics.IsFullScreen = true;

Never thought that VS would not show any error when your application is on fullscreen.

I set it now to false.

Thanks.

Don't sweat it man. The reason why we ask "Is it plugged in." is because 9 times out of 10, that's the problem. I ran into the same thing early in my career on Windows 95 and DirectX 3. At that time, I don't think we could get windowed mode working correctly with our game so we had to get dual monitors setup back in the olden days in order to debug stuff. :)

I'm happy I could save you some time.

- Eck