Install Directory Opus Causing System Crashes and App Failures

After installing Directory Opus, the software itself generally opens and functions correctly most of the time. However, many other programs are either unable to open or don't work properly anymore.
For example, Quicker displays an error message saying "Attempted to read or write protected memory. This usually indicates that other memory is corrupt." ‘Everything’ doesn't open at all—there’s no response when I try to launch it.

Additionally, when I try to open some built-in system functions, like launching a browser from the taskbar or accessing network settings, the screen goes completely black (no icons or taskbar). Pressing Ctrl, Alt, and Del brings up the screen, but selecting Task Manager doesn’t show it properly and instead returns to the black screen. The only way to recover is to restart the computer. After rebooting, everything returns to normal, but the issue recurs if I try to open those system functions again.

Sometimes, Directory Opus itself crashes, with the crash report indicating that shell32.dll is the cause.

Uninstalling Directory Opus and rebooting solves all these issues.

Moreover, when I choose to submit a crash report, Directory Opus continues to crash repeatedly. I’m wondering if this could be due to some changes made to registry-related items during the installation, causing all related functions to malfunction.

If possible, is there another way for me to send you the crash report?

1 Like

See the steps for Opus 12 in Automatic crash logs (for bug reports) for how to manually send in crash reports. Those also work with Opus 13 if the built-in reporter isn't working.

But I think there is probably something outside of Opus which is wrong, especially if it's affecting Everything. A huge number of us use Everything and Opus together without problems, and if basic tasks like opening a browser from the taskbar were affected by Opus, especially to the extent that the whole screen and taskbar stopped working, we would have thousands of threads about it every day. :slight_smile:

2 Likes

Yes, I agree with your statement. I suspect that some of the existing settings on my computer are conflicting with the settings of Directory Opus, causing issues immediately after installation. I have already sent the error report to the corresponding email, which includes three consecutive crash reports that occurred during the 'Submit Crash Report' process :smiling_face_with_tear:. I hope these can help in finding a solution to the problem.

By the way, your response speed is impressive, and commend you for the excellent service quality! :heart:

The crashes are caused by AudioDevProps2.dll, which is part of Sonic Studio (and possibly other audio drivers/software that comes with motherboards, including Asus and MSI ones), and is known to cause crashes in a lot of games and some other applications, just after they launch: audiodevprops2.dll - Google Search

1 Like