Severe Issue with SoftTube AmpRoom that only affects Cubase 12, 13, 14 on my system

Cubase
1

Back in December, SoftTube Amp Room quit working proplerly on my system with all version of installed Cubase ( 12, 13, 14). It works fine in Reaper and Ardour.

What happens is that when I load the AmpRoom plugin in Cubase, it will start to load, wait a bit, windows starts to crash, then the PC freezes. I have to power-down to reboot.

I had cleared the user settings for Cubase 14, reinstalled SoftTube Amp Room (along with all the other plugins), and refreshed the iLok licenses as advised by SoftTube Support. I also disabled OpenGL. I had also removed all of the SoftTube plugins and reinstalled. Deleted User Presets. None of this fixes the problem. I sent them the crash logs, and they finally dropped me and said that they could not figure out the issue, as there was nothing of importance in the crash log that helped them figure out the issue.

I tried it in Cubase 12 and 13. The same issue occurs. I

It was working fine in Cubase 14 until one day it just decided to crap out….

It still works fine in Reaper.

Any Suggestions ?

2

Hi,

I don’t really understand this sequence. If Windows crashed, how can it freeze after?

Please, attach the *.dmp file(s):
Win: %userprofile%/Documents/Steinberg/Crash Dumps

If you cannot find any, create them manually.

Generate a DMP file and share it via Dropbox or a similar service, please.

Use the Microsoft ProcDump utility to generate a DMP file, please.

  1. Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.

  2. Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)

  3. Navigate (in the Command Prompt) to the folder with the extracted procdump file.
    For example:
    cd C:\ Users \ \ Downloads \ Procdump
    Note: the dmp file will be written into that folder.

  4. Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).

  5. Launch procdump64 via Command Prompt:
    Cubase:
    procdump64 -e -h -t Cubase

Nuendo:
procdump64 -e -h -t Nuendo

The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.

  1. Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.

ZIP and share the DMP file via Dropbox or a similar service, please.

3

Thank you for looking at this. I still can move the mouse, and move a window, but response is very slow. I am not able to pull up the task manager and see what is going on with processes, memory, and drive. Then eventually, I am unable to do anything. It seems like a memory leak type of thing.

What is the difference between a .dmp file that has ‘freezedump’ at the end and one that does not ?

Here is a link to the crashlogs

Will I get better crash logs using the ProcDump64 utility?

4

@Martin.Jirsak Have you had a chance to look at the .dmp files ?

5

No response ?

7

Hi,

The crashes are in the following…

The plug-in:

ntdll!NtWaitForSingleObject+0x14
KERNELBASE!WaitForSingleObjectEx+0x8e
KERNELBASE!GetOverlappedResult+0xc5
Amp_Room_DIS+0x1cb1c0f

Some Windows libraries:

ntdll!NtAlpcSendWaitReceivePort+0x14
rpcrt4!LRPC_BASE_CCALL::SendReceive+0x12f
rpcrt4!NdrpSendReceive+0x97
rpcrt4!NdrpClientCall2+0x5d0
rpcrt4!NdrClientCall2+0x1f
combase!CRpcResolver::RegisterWindowPropInterface+0x97
combase!InternalRegisterWindowPropInterface2+0xb4
ole32!AssignEndpointObject<CPrivDragDrop>+0x37
ole32!AssignDragDropEndpointProperty+0x5f
ole32!RegisterDragDropImpl+0xdb
ole32!RegisterDragDrop+0x47