I tried to open the Recycle Bin. It did not open; instead, Windows
prevented itself from working:
http://img33.imageshack.us/img33/8618/dataexecutionprevention.gif
DEP exceptions are Windows letting you know it feels threatened by
some program and will not allow it to run.
One popular "solution" is to just disable DEP, but I would rather
figure out what it is and fix it since something is wrong unless you
can explain the message some other way.
Are you double clicking RB or right clicking, Open?
If it is just the Recycle Bin, then we can work to fix that, but
please do this part first:
If it is Windows Explorer that is reporting the Data Execution
Protection error, suspect a non Microsoft
Explorer Shell Extension. Shell Extensions help make up the Right
Click menu for files you see in Explorer.
You can download ShellExView from here to see which ones you have
loaded:
http://www.nirsoft.net/utils/shexview.html
ShellExView doesn't install anything on your computer, it just runs
and displays.
When you launch it, the non MS extensions will be in light pink, but
on some systems that is a
hard color to see, so click View, Choose Columns and move the
Microsoft column closer to the
top so you can see it on your screen without having to scroll left and
right.
Sort the display by clicking the Microsoft column so all the "No"s are
at the top and easy to see.
I am not a trial and error advocate, but I can't think of another way
to do this...
Right click and disable the non Microsoft extensions one at a time
keeping a list so you can enable
them again later if desired. The result of the change is immediate and
no reboot is required. Test your
failure condition.
If you recognize any extensions that may have been added or downloaded
recently, start with those. The
Extensions are not uninstalled, just disabled.
The hope is that you will find the one Extension that causes the error
and then you can figure out
what to do about it.
I don't have your issue but I can see that the Extension is
immediately disabled, so disabling one
does not require a reboot but if you find the culprit, I would reboot
anyway to really be sure.
See if that gets you going...