I've been getting the Program Error dialog (0xC0000005) for the past several days, seemingly randomly when task-switching to an already open Directory Opus window without doing any actions in the program. The latest one happened where the current open folder contained only 1 folder and 2 zip files. No thumbnail view or side panel image viewer were active. Just plain list view. I click "Yes" on the error dialog to terminate the thread, and things seem OK to continue.
I did a Windows update 13 days ago, but I think this problem started 4 days ago (that's the earliest .dmp file I see). I checked the dmp files, read several past forum posts, and read through your forum article with common crash causes, but nothing seemed obvious from those. It would take hours to go through all of the steps in that article, so I'm hoping you can help me narrow it down based on the dmp files (I'll email them in 1 minute).
Version and OS info:
Directory Opus Pro 12.33 Build 8659 x64
OS 10.0 (B:19045 P:2 T:1) SP 0.0
Here's the dmp file excerpt:
Attempt to execute non-executable address 00007fff370b7750
PROCESS_NAME: dopus.exe
EXECUTE_ADDRESS: 7fff370b7750
FAILED_INSTRUCTION_ADDRESS:
+0
00007fff`370b7750 ?? ???
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 00007fff370b7750
MISSING_CLR_SYMBOL: 0
If you send the dmps to us we can take a look and see if it indicates the component which is crashing. It may be a shell extension something else has installed. It's probably not Opus as Opus 12.33 hasn't changed in a long time now and wouldn't suddenly start crashing on its own.
Do you use 123SyncCloud / 123CloudStorage? (Or something with a similar name; we couldn't find the actual product page for a definitive name but it started crashing Opus 2 or 3 weeks ago, with the crashes using pointing to combase.dll as the faulting module, although the real bug is in a DLL further up the stack which is calling combase.dll.)
The crash seems to be coming from the Windows CompressedFolder handler. Opus doesn't use this itself but something is triggering it to be loaded when Opus queries for file information.
You could try using ShellExView to disable the handler ({E88DCCE0-B7B3-11d1-A9F0-00AA0060FA31}) and see if that's really the problem. If so, leaving it disabled wouldn't affect Opus although it would stop you opening zip files with Explorer.
I found 4 entries for CompressedFolder / zipfldr.dll in ShellExView, although that specific CLSID you mentioned is not showing in ShellExView. I found it in the registry though. I'll try disabling the four lines in ShellExView first. I found another article about deleting the registry key to solve some people's issues with this Windows function, but I'll wait on that.
FYI below are the four relevant lines from ShellExView:
Thanks for that info. I don't use either of those tools or anything with a 123 name. I use several other common cloud/syncing tools though (Dropbox, OneDrive, Google Drive, etc.).
I did my latest set of Windows updates on Aug 12th, so that seems like it could be the culprit based on you finding out that it started happening 2-3 weeks ago (I couldn't remember clearly when the issues started). I see that the zipfldr.dll has an updated timestamp for that Windows update, so I wonder if something was changed in there that is now causing problems. I just replied to Jon with his suggestion related to that.