I am experiencing frequent crashes with Directory Opus 13.22.0.0 on Windows 11 Enterprise (Build 26100). The software has become unusable due to the frequency of these exits.
Symptoms:
The application crashes silently or with a Windows "Stopped Working" dialog.
I have checked %TEMP%\DOpus.Minidumps and used the "Submit Crash Logs" tool, but no minidumps are being generated.
System Environment:
Managed Environment: My system is running under Admin By Request overhead. I've noted that ShellHelper64.dll from this suite is loaded into the process.
Previous Troubleshooting: I have uninstalled DisplayFusion, which was previously suspected, but the crashes persist.
System Health: I have successfully run DISM /RestoreHealth and sfc /scannow. SFC reported no integrity violations.
That likely means whatever corrupted memory in the process took out so much that the crash reporter couldn't be triggered.
Have you looked at the suggestions in the FAQs about crashes? E.g. Does the problem happen when in certain folders (e.g. documents or cloud storage) or folders with certain file types (e.g. videos)?
FWIW memory corruptions are usually caused by shell extensions, video codecs, and similar DLLs that get loaded into our process. But it could also be a bug in our code.
If you have the GFlags.exe developer tool from Microsoft, you can turn on PageHeap which adds extra checks to memory allocation/free and buffer overruns. Those checks will slow things down a lot, but can result in earlier detection of the problem and a proper crash dump.
I use this command to turn on PageHeap for dopus.exe (you may have to adjust it depending on the location of gflags.exe):
Update:
After running DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow, the crashes have ceased. I enabled GFlags PageHeap as suggested and stress-tested the application with large OneDrive folders and thumbnail generation, but no crashes occurred. It appears the issue was rooted in corrupted Windows system files (ntdll.dll) rather than a direct software bug.