- Jul 18, 2003
- 12,400
- 1,076
- 126
I've been trying to figure out why Explorer.exe has been crashing a bunch lately on me under WinXP Pro 32bit (Vista 64bit had no issues, as I did not install Mass Effect under this OS. I dual boot my system). I narrowed it down to the fact that when I right-click on files or desktop items, it seemed to cause memory errors and crashes.
A quick Google search led me to taking a look at Context Menus using a little program called ShellExView v1.23 (Downloadable Here), which other users had used to disable some old Divx menus that were causing a similar issue to mine.
I ended my journey for a resolution here.
Here is the culprit on my system...
How to disable the right-click Securom context menu.
Disabling this Securom context menu (which isn't even visable on non-game files the context menu isn't assocated with mind you) solved my problem. You have to understand I even considered rebuilding my machine and have spent a ton of time (several hours) diagnosing what the problem was (it's not like a million other things couldn't crash Explorer.exe). I'm so fuming pissed right now I could just scream! Seriously, where has quality control gone in the software industry? Is it really too much to ask to beta test like 10 systems, where this bug would have been easily found out?
:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|
Update: This was apparently caused by the Bring Down the Sky expansion I installed for Mass Effect or the 1.01 patch (I installed this and then 1.01a once it was available), which subsequently updated the Securom version.
Here is apparently what the right-click context menu for Securom is used for.
A quick Google search led me to taking a look at Context Menus using a little program called ShellExView v1.23 (Downloadable Here), which other users had used to disable some old Divx menus that were causing a similar issue to mine.
I ended my journey for a resolution here.
Cause
These problems are caused by a bad context menu handler. A context menu handler is a shell extension handler that adds commands to an existing context menu (Example: cut, copy, paste, print, Scan with Norton etc). A poorly coded (edit: oh boy, what an understatement) context menu handler may be causing any of the above symptoms. As context menu handlers can be added in different areas (file class, folder, allfilesystemobjects, HKCR\* registry keys), it's a difficult task for an end-user to pinpoint which shell extension is causing the problem.
Here is the culprit on my system...
How to disable the right-click Securom context menu.
Disabling this Securom context menu (which isn't even visable on non-game files the context menu isn't assocated with mind you) solved my problem. You have to understand I even considered rebuilding my machine and have spent a ton of time (several hours) diagnosing what the problem was (it's not like a million other things couldn't crash Explorer.exe). I'm so fuming pissed right now I could just scream! Seriously, where has quality control gone in the software industry? Is it really too much to ask to beta test like 10 systems, where this bug would have been easily found out?
:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|:|
Update: This was apparently caused by the Bring Down the Sky expansion I installed for Mass Effect or the 1.01 patch (I installed this and then 1.01a once it was available), which subsequently updated the Securom version.
Here is apparently what the right-click context menu for Securom is used for.