- This topic has 4 replies, 4 voices, and was last updated 11 years ago by
.
Viewing 5 posts - 1 through 5 (of 5 total)
-
Posts
-
I used Shelxview to filter non-Microsoft shell extension to find out WinCDEmu is causing Windows Explorer to stop working, anyone has a similar problem? 😳
Yes! I have this problem too, it’s very annoying!
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d6727a7 Faulting module name: mydocs.dll_unloaded, version: 0.0.0.0, time stamp: 0x4ce7b8fb Exception code: 0xc0000005 Fault offset: 0x6d77eb75 Faulting process id: 0x12cc Faulting application start time: 0x01cc9cc27abf117e Faulting application path: C:WindowsExplorer.EXE Faulting module path: mydocs.dll Report Id: 21f1374c-08b7-11e1-b2e3-00241d902f92@VGA wrote:
Weird. Which version and on which OS ?
Uninstall and reinstall last version as admin. :geek:
It happens on both Windows 7 and Windows Thin PC.
same here in window7 ultimate 64 bit.. it frequently crashes even not in use and (as far as i understand) it is about WinCDEmuContextMenu.dll. i ended up uninstalling wincdemu 🙁
if there is a solution for this please let us know; i want to use wincdemu since it is much more practical than any other auto-mount software that I’ve ever used.
log is here:
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: WinCDEmuContextMenu.dll_unloaded, version: 0.0.0.0, time stamp: 0x4e4026cb
Exception code: 0xc0000005
Fault offset: 0x000007fef8c4fdcc
Faulting process id: 0x958
Faulting application start time: 0x01cee2d13609a207
Faulting application path: C:WindowsExplorer.EXE
Faulting module path: WinCDEmuContextMenu.dll
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.