Debugging :: Windows 8 - Right Click On Local Disk Produces Crash

Here is what I wanted to do: right click in File Explorer on a local disk, so I can share it, so I can access that drive from my laptop. Attached a picture, I want to share "Local Disk (E:)", underlined with red, with my mad paint skills. You can see a snippet from my task bar as well, it is important.

Here is the problem: after right clicking, the OS seems to think about 1-2 seconds, then it closes the File Explorer, then kills my task bar, every icon disappears for a few seconds, then everything loads back, tho File Explorer won't open again automatically. Back in Windows7 and XP etc. days this was typically something like an "explorer.exe" crash. Attached another picture, how my taskbar looks exactly, at the moment of restarting. Note: the taskbar flashes before reappearing - still without icons - with dark blue color for a brief moment, then it loads my icons, as I mentioned above. Dark blue is the color of my "Start screen", or however it is officialy called, not sure. The pic:

Also, you can see at the right side, the clock does not show as well.

My setup is like this: I have a 500GB hard drive: C: is the system partition, D: is the data partition. E: is a completely separate 320GB hard drive, another data partition. I have a fully legal Windows 8 Professional, with updates installed(perfectly up to date, I just did an update check, everything is installed) provided by MSDNAA (or Dreamspark nowadays, if I am right) for university students. Every hardware works good, so something went wrong with Windows 8. I am not completly sure, but I think I could right click the drives a while ago, it started just now. Also, I can right click everything else without error, just not the disks. I don't want to roll back to Windows7, since I really like 8, but if this won't get sorted out, I may have to.

Here is what I did: It was obvious that something 3rd party context menu extension (shell extension) caused the problem. I did try to disable extensions 1 by 1, to see if it solves it. Finally, disabling "NVIDIA CPL Context Menu Extension" solved my problem.