NO can do? You mean CAN do? :\

Take a look here:

http://www.geekstogo.com/forum/topic/306333-blue-screen-of-death-code-0x00000050/

Oh and install the addons Adblock Plus and ScriptNo / Noscript. If your browser doesn't have these, or suitable alternatives then it's time to switch browsers.

Those will do a good job of protecting you from nasty online scripts that can infect your computer. It's a pain in the arse okaying everything at first, but as you now know, it's better than the alternatives.

"This problem may occur if there is a conflict between Windows XP SP1 and the display adapter drivers that are currently installed. "

Copied and pasted from a 10 seconds google search. :P

Edit: Whoops. Saw you had Vista. Well XP problems can follow to Vista...

booting safe mode...
Edited the post.

Another search led to this:

Typically, 0x00000050 is caused by corrupt registry, viruses (which also may affect the registry like is some example below), video adapter driver issues, memory faults (in different locations).

Also guys I recently upgraded to IE 9 (Chrome & firefox kept crashing) and I was browzing around and the crash may have happened because of a software change.

This link might help too.

http://ezinearticles.com/?How-to-Stop-Error-0x00000050-in-XP-and-Vista&id=2267681

Edit: There's even a video of some random dude having this problem on Youtube. :)
http://www.youtube.com/watch?v=df4h5QmxEHQ

Seems I need to clean the registry.

Alot of expert forums say to run chkdsk /f /r as I said earlier....as it can be due to data corruption on your HDD. If you can get to a command prompt i'd recommend running one at the c: prompt.

I'm always wary of that. Got some programs royally messed up that way. On the other hand there are people swearing it's the second best thing after defrag and does it all the time so it might just be me that's clumsy.

Also, try uninstalling any VCD drivers such as Alcohol 120%, Daemon Tools...

I do your guys' advice tomorrow (hitting my busy day scheduale now) or when I get

Also there's THIS MS hotfix that claims to fix the issue:

link
Click accept at the eula page, then on the next page:

At "step one: select hotfix", click show hotfixes for all platforms and languages, then tick the box next to the one corresponding to your windows version(x86 or x64...32 or 64 bit), and fill in your email in step 2 to get the hotfix sent to you.

Awww man, my eyes...I got hit by an EULA in Polish legalese. Ouch.