Regarding the issue- Cubase14 kernellbase.dll

Cubase
, ,
1

I am Japanese, and my English is not very good, but please bear with me.

In Cubase 14 Pro, launching certain third-party plug-ins causes an error attributed to KERNELBASE.dll,
rendering the affected plug-in unusable. There are definitely similar samples on Twitter as well, so I don’t think it’s caused by the plugin.

The pluguins

・Ozone 12

・Listento

I’ve tried most of the solutions described by others, like sfc/scannow and some DISM comand, but nothing worked.

Is reinstalling the OS the only option left?

If anyone knowledgeable is reading this, I’d really appreciate your advice.

HELP!

スクリーンショット 2025-09-06 235709
スクリーンショット 2025-09-06 235709770×822 54.5 KB

2

Hi and welcome to the forum,

Please attach the *.dmp file located at Documents/Steinberg/CrashDumps/ folder.

Then we can have a look, where the crash really happened.

3

Thank you.
The Crushdump directory is empty; there are no dmp files.

Instead, a log file with the .json extension is being output. Is that something different?

For now, I can fully reproduce the error, so if a dmp can be generated, that would also be possible.

4

It didn’t work after all…
I tried crashing it again, but as you can see, no DMP file was generated…

スクリーンショット 2025-09-07 174710
スクリーンショット 2025-09-07 1747101531×1245 199 KB

5

You could try to use procdump to generate a crash dump as described by Paul here:

1 Like
6

Hi,

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.

1 Like
8

My apologies, I jumped the gun!
This is the problematic dmp file.

10

Hi,

The crash is in Cubase. Reported to Stienberg. Thank you.

Could you please explain more in detail, what exactly do you mean by this:

What do you mean by launching? Do you add the plug-in as an Insert to an Audio Track? Or to any Output Channel? Or do you use it as the Direct Offline Process Plug-in?

Could you maby make a short video?

Can you always replicate the issue? Do you have the latest version of the plug-ins installed?

1 Like
11

This occurs when inserting a plugin.
Both the plugin and Cubase are up to date.

As shown in the video.

(Perhaps due to the video, performance is slower than usual. Normally, the error occurs much more quickly.)

12

The correct link for the video is here.